Helm Chart - Multiple kong releases - ingress classes overrides

[MostefaKamalLala]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I have a helm release of kong version 2.6.3 already deployed.
I also have another need, which is deploying another kong release in the same cluster.
I am aware of the configuration that create a specific ingress class name for each.
I left the first release with default value for the ingress class name which is ingressController.ingressClass: "kong" and the second release I changed the value to ingressController.ingressClass: "kong-2".
However the issue is that when I check the ingressClasses in Lens, I see only one ingressClass, the last one that I deployed.
I validated the with functional tests that the right ingress class is being used successfully.
I am currently testing it in non-production environment but I am not keen on deploying it in production environment yet until I make sure that it is not a helm chart bug or Lens bug. Unfortuantly there is no kubectl command to list directly the ingress classes, and using kubectl get ingress --all-namespaces -o jsonpath='{.items[*].spec.ingressClassName}' | tr ' ' '\n' | sort -u
shows only kong-2 ingress class.

Expected Behavior

Two ingressClasses

Steps To Reproduce

Deploy two helm releases. One with default ingressClassName and the other with a custom name.

Kong Ingress Controller version

v2.0

Kubernetes version

AKS v1.27.7

Anything else?

I have noticed a changed in the template for ingressClass in the version 2.7.0 Would it fixe my issue?

Also the previous ingress with the default helm release are still working.

[randmonkey]

@MostefaKamalLala What was your Kong charts version? The latest version of kong/kong charts (2.38.0) will not remove your existing ingressClass. charts 2.6.3 and KIC 2.0 is quite old now and has reached the end of support.

[MostefaKamalLala]

@randmonkey I am using chart version 2.6.3. So I tryied to gradually update I reallized that the issue is fixed in subsequent versions but I faced another issue. For some reason, even if I follow the update guide, the KIC doesnt spin up.
I get an error saying: error=“resource not yet configured in the data-plane” logger=controllers.Ingress.netv1

Also it is not a big deal if it's overriden I can always add it manually without affecting the exising binding of IngressClass and other K8s objects.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.