Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ingress not allowed when kong is disabled #8972

Closed
kajov opened this issue Apr 26, 2024 · 4 comments · May be fixed by #9317
Closed

Ingress not allowed when kong is disabled #8972

kajov opened this issue Apr 26, 2024 · 4 comments · May be fixed by #9317
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@kajov
Copy link

kajov commented Apr 26, 2024

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

@kajov kajov added the kind/bug Categorizes issue or PR as related to a bug. label Apr 26, 2024
@floreks
Copy link
Member

floreks commented May 9, 2024

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.

@floreks floreks added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/bug Categorizes issue or PR as related to a bug. labels May 27, 2024
@floreks
Copy link
Member

floreks commented Jun 3, 2024

Closing as stale. No response for ~1 month.

/close

@k8s-ci-robot
Copy link
Contributor

@floreks: Closing this issue.

In response to this:

Closing as stale. No response for ~1 month.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@tbernacchi
Copy link

Is there a way to turn off TLS on kubernetes-dashboard-kong-proxy? I was able to make it work setting --insecure-port on my kubernetes-dashboard-web deployment and then setting the certificate on my Ingress. What's the point to have this kubernetes-dashboard-kong-proxy?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants