-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for api gateway + consul namespaces #1024
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from the API Gateway side, would appreciate a final review from @hc-github-team-consul-ecosystem before merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
Co-authored-by: Iryna Shustava <ishustava@users.noreply.github.com>
… is offline (hashicorp#1024) * Fail scheduling all pods that are not part of consul when the webhook is unhealthy. Co-authored-by: Iryna Shustava <ishustava@users.noreply.github.com>
This PR, coinciding with the corresponding PR in the api gateway codebase adds support for namespace mapping of deployed gateways.
More context around the usage envisioned is in that PR, but for the most part this copies the same configuration as used in the connect injection and catalog sync helm configuration.
Tested via
bats
: