Error no Route matched with those values

[whizyrel]

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]

Hello community and maintainers, Anyone wanna help? Regards

[whizyrel]

@floreks like #8964

[floreks]

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

[whizyrel]

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

[whizyrel]

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
...

@floreks

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.