Ingress not allowed when kong is disabled

[kajov]

What happened?

setting kong to enabled: false causes error: template: kubernetes-dashboard/templates/networking/ingress.yaml:73:34: executing "kubernetes-dashboard/templates/networking/ingress.yaml" at <{{template "kong.fullname" (index $.Subcharts "kong")}}>: template "kong.fullname" not defined
while app.ingress.enabled: true

The reason having this config:
Running oAuth2-proxy with NGINX Ingress controller and external-dns to register new ingress targets created on Route53 for ALB to resolve

When kong and ingress are enabled and the ingress class has been created, ingress is causing too many redirects with 308 and cannot resolve into the target.

Request:
When ingress is enabled, allow disabling Kong without relying on ingress enabled feature.
Create missing k8s dashboard certificate as in previous versions for ingress tls as before

What did you expect to happen?

Disabling Kong wont interrupt deployment while having ingress enabled with external NGINX Ingress controller

How can we reproduce it (as minimally and precisely as possible)?

Due to complicated setup will only provide when necessary

Anything else we need to know?

Deployed using Helm Chart

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.3.2

Kubernetes version

EKS 1.29

Dev environment

No response

[floreks]

I don't think that it makes much sense to disable kong and keep our ingress enabled. You'd need to completely overhaul the ingress configuration to make it work without kong. Are you sure you want to disable kong? You will need to match its functionality with something else.