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

Error no Route matched with those values #9476

Open
whizyrel opened this issue Sep 22, 2024 · 5 comments
Open

Error no Route matched with those values #9476

whizyrel opened this issue Sep 22, 2024 · 5 comments
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@whizyrel
Copy link

What happened?

I installed kubernetes dashboard using helm from here https://github.com/kubernetes/dashboard/blob/master/README.md and passed in a few values set in a bid to expose kubernetes dashboard using ingress.

When I visit the domain, I get the error

Error

no Route matched with those values.

request_id: ...
...
kong:
  ingressController:
    enabled: true
  proxy:
    type: ClusterIP
    http:
      enabled: true
app:
  ingress:
    enabled: true
    hosts:
    - domain-name
    ingressClassName: nginx
    useDefaultIngressClass: false
    useDefaultAnnotations: true
    pathType: ImplementationSpecific
    path: /
    issuer:
      name: ...
      scope: cluster
    tls:
      enabled: true
...

What did you expect to happen?

Kubernetes Dashboard should be accessible on the domain specififed.

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

Add kubernetes-dashboard repository

helm repo add kubernetes-dashboard https://kubernetes.github.io/dashboard/

Deploy a Helm Release named "kubernetes-dashboard" using the kubernetes-dashboard chart

helm upgrade --install kubernetes-dashboard kubernetes-dashboard/kubernetes-dashboard --create-namespace --namespace kubernetes-dashboard

Anything else we need to know?

I set up kubernetes in a raw vm with

  • Metallb
  • Flannel
  • Ingress
  • CertManager
  • Helm

Other services and ingress work just fine

What browsers are you seeing the problem on?

Chrome, Firefox

Kubernetes Dashboard version

7.6.1

Kubernetes version

1.31.0

Dev environment

No response

@whizyrel whizyrel added the kind/bug Categorizes issue or PR as related to a bug. label Sep 22, 2024
@whizyrel
Copy link
Author

Hello community and maintainers,
Anyone wanna help?
Regards

@whizyrel
Copy link
Author

@floreks like #8964

@floreks
Copy link
Member

floreks commented Sep 25, 2024

You shouldn't really have to touch kong configuration if you want to enable ingress. This looks like a configuration issue.

@whizyrel
Copy link
Author

whizyrel commented Sep 25, 2024

Alright, I would take Kong configuration out and revert.
Thanks

@whizyrel
Copy link
Author

whizyrel commented Sep 25, 2024

This was the result and the behaviour before kong's configuration was fiddled with
The current configuration now is

...
app:
  ingress:
    enabled: true
    hosts:
    - domain-name
    ingressClassName: nginx
    useDefaultIngressClass: false
    useDefaultAnnotations: true
    pathType: ImplementationSpecific
    path: /
    issuer:
      name: ...
      scope: cluster
    tls:
      enabled: true
...

image

@floreks

@floreks floreks added kind/support Categorizes issue or PR as a support question. and removed kind/bug Categorizes issue or PR as related to a bug. labels Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

2 participants