Envoy Configuration Dashboard ⚙️

The in-memory cache and the persistent database are out of sync. Please choose a resolution strategy.

Inconsistency Details:

Paste the YAML configuration for the new filter chain below.

Need help composing a valid configuration? Use the external: Envoy Filter Chain Composer ↗

Paste the full YAML configuration for the new listener(s) below and submit. You can provide a single listener object, or a list of listeners under the resources key to load multiple at once:

resources:
  - <listener 1>
  - <listener 2>

Make sure every listener includes the required type identifier: "@type": type.googleapis.com/envoy.config.listener.v3.Listener, which allows the parser to recognize your configuration.

Paste the full YAML configuration for the new cluster(s) below and submit. You can provide a single cluster object, or a list of clusters under the resources key to load multiple at once:

resources:
  - <cluster 1>
  - <cluster 2>

Or:

<cluster 1>

Make sure every cluster includes the required type identifier: "@type": type.googleapis.com/envoy.config.cluster.v3.Cluster, which allows the parser to recognize your configuration.

Paste the full YAML configuration for the new secret(s) below and submit. You can provide a single secret object, or a list of secrets under the resources key to load multiple at once:

resources:
  - <secret 1>
  - <secret 2>

Make sure every secret includes the required type identifier: "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret , which allows the parser to recognize your configuration.

Configure automatic certificate rotation for secret: