Open akoshok1 opened 11 months ago
The ingress classes becomes inconsistent after https://github.com/Kong/charts/commit/da4889ffde4792cb44ace9e81bfc525313c700c3. We should use the same ingress class: all use default
(the original value) or all use kong
.
Perhaps kong is a better choice, as there is a good chance default may already be used in clusters we install to.
Per chat, @mheap said he wanted to review this guide overall as part of fixing this, so assigning to him.
While at it, let us please remove the two hostport settings which cause issues in EKS w/ Fargate and we do not use in other examples.
When trying https://raw.githubusercontent.com/Kong/charts/main/charts/kong/example-values/doc-examples/quickstart-enterprise-licensed-aio.yaml
We get:
This makes sense. We set ingressController.ingressClass to default, and not kong. And then in manager.ingressClassName portal.ingressClassName and portalapi.manager.ingressClassName we refer to kong, and not default.
May I suggest we: 1-alter ingressController.ingressClass to kong 2-For consistency, also set admin.ingressClassName to kong