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

Cannot enable ingress add-on with K8s v1.18.20 and Minikube v1.23.2 #12636

Closed
AlexIoannides opened this issue Sep 30, 2021 · 3 comments · Fixed by #12794
Closed

Cannot enable ingress add-on with K8s v1.18.20 and Minikube v1.23.2 #12636

AlexIoannides opened this issue Sep 30, 2021 · 3 comments · Fixed by #12794
Assignees
Labels
addon/ingress kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@AlexIoannides
Copy link

With Minikube v1.23.2 running on macOS v11.6 installed via homebrew (commit: 0a0ad76), I get the following error when I try to enable the ingress add-on with an old version of Kubernetes:

  1. minikube start --kubernetes-version=v1.18.20
  2. minikube addons enable ingress
error: unable to recognize "/etc/kubernetes/addons/ingress-deploy.yaml": no matches for kind "IngressClass" in version "networking.k8s.io/v1"

I don't think that networking.k8s.io/v1 is part of the v1.18.2 k8s API, which may be the source of the issue?

@sharifelgamal
Copy link
Collaborator

Yep, that's definitely the issue. We switched to networking.k8s.io/v1 to support k8s 1.22 and beyond, and that has inadvertently broken ingress for older versions of k8s.

We do want to support older k8s versions for ingress (I think we might even have some code that attempts it), but for now the best workaround is to either downgrade your version of minikube or upgrade your version of k8s.

@sharifelgamal sharifelgamal added addon/ingress kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 2, 2021
@sharifelgamal sharifelgamal added this to the 1.24.0 milestone Oct 2, 2021
@AlexIoannides
Copy link
Author

Thanks Sharif - appreciated.

The problem we have is that the Kubernetes Python client is currently at v1.18. I'll look into downgrading Minikube.

@prezha
Copy link
Contributor

prezha commented Oct 27, 2021

@AlexIoannides thank you for reporting this issue, maybe there's still a hope there ;)

we've made some changes in the meantime and updated ingress (also trying to support k8s versions before v1.19) - can you please try to checkout pr: #12794 and retry, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addon/ingress kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants