You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am using the latest version of KONG ingress controller.
I am trying to use it with AWS EKS + NLB + ACM Certificate via annotation in proxy.
steps to reproduce:
helm upgrade --install kong-public . -f values.yaml -n kong --create-namespace
The initial installation will create Class LoadBalancer therefore I need NLB so I am using these values.yaml
After that, you will notice that annotations are not used nor nameOverride in the final template.
Also second BUG: Without this is almost not possible to test the chart
helm template kong . -n kong > out
Error: template: kong-ingress/templates/tests/test-resources.yaml:1:15: executing "kong-ingress/templates/tests/test-resources.yaml" at <.Values.deployment.test.enabled>: nil pointer evaluating interface {}.test
Facing the same issue here, and I've been scratching my head over this. Did you manage to find a solution to this @tkcontiant ?
It could be related to this known helm issue with aliases: helm/helm#7093 ? But the workaround to that problem is by putting a version: ">=0.0.0" or any relevant version with the alias, which this chart does have. I'm thinking of manually deploying 2 different versions of the kong chart with values similar to this chart, to get this working.
Hello, I am using the latest version of KONG ingress controller.
I am trying to use it with AWS EKS + NLB + ACM Certificate via annotation in proxy.
steps to reproduce:
helm upgrade --install kong-public . -f values.yaml -n kong --create-namespace
The initial installation will create Class LoadBalancer therefore I need NLB so I am using these values.yaml
After that, you will notice that annotations are not used nor nameOverride in the final template.
Also second BUG: Without this is almost not possible to test the chart
This is how the helm chart structure look's like
The text was updated successfully, but these errors were encountered: