Skip to content

proxycfg: init WatchedLocalGWEndpoints map for Ingress and API gateways#16238

Closed
mikemorris wants to merge 1 commit intomainfrom
proxycfg/init-local-gateways-map
Closed

proxycfg: init WatchedLocalGWEndpoints map for Ingress and API gateways#16238
mikemorris wants to merge 1 commit intomainfrom
proxycfg/init-local-gateways-map

Conversation

@mikemorris
Copy link
Contributor

Description

Initialize the WatchedLocalGWEndpoints snapshot map for Ingress and API gateways.

Testing & Reproduction steps

We don't support setting peer upstreams on Ingress gateways yet, but if an ingress has been configured to point to a service with a cross-peer failover configured, a watch may be attempted to be set up on the local mesh gateway at https://github.com/hashicorp/consul-enterprise/blob/main/agent/proxycfg/upstreams.go#L345, resulting in a panic when https://github.com/hashicorp/consul-enterprise/blob/main/agent/proxycfg/upstreams.go#L622 is called because the map has not been initialized.

This needs testing and this area of the codebase could likely benefit from a panic handler to avoid errors like this from bringing down the server in a state from which it can be difficult to recover.

PR Checklist

  • updated test coverage
  • external facing docs updated
  • not a security concern

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant