[Helm Chart] Change Kong Pod annotations to work out-of-the-box with Kuma and Istio #10377
+5
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default Kong Chart we rely on sets these two annotations, by default, on its Pods.
Source: https://github.com/Kong/charts/blob/5c2eb33076061e90f49ac05c9b26e2b961a8bc4a/charts/kong/values.yaml#L986-L988
This prevents service meshes from correctly intercepting incoming traffic to the Kong Pod, for example when we want to expose the Dashboard using an Ingress or Gateway.
For more details, see #10376 .
This PR modifies the Kubernetes Dashboard's Chart default values to set these values as suggested in the Kong Proxy's Chart README, in the case we want to use it as an internal proxy rather than an external gateway (which is the default configuration).