-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug]: Unable to apply v4.0 CRDs: Invalid value: "v1alpha1": must appear in spec.versions #7010
Comments
Hi @kyrofa thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
Hi @kyrofa , i ran an upgrade from v3.7.2 to v4.0.0 and not observing the same behaviour:
can you please post outputs of |
Of course! Maybe this is an odd artifact of updating the CRDs for several years before now? Here's what I've got:
|
yep those two you've posted seems different from 3.7.2 CRDs. see https://github.com/nginxinc/kubernetes-ingress/blob/v3.7.2/config/crd/bases/k8s.nginx.org_transportservers.yaml#L330 and https://github.com/nginxinc/kubernetes-ingress/blob/v3.7.2/config/crd/bases/k8s.nginx.org_globalconfigurations.yaml#L110
in 3.7.2 |
Okay interesting, I ran |
Hi @kyrofa it does looks like an issue when coming from earlier releases, going from 3.3.2 to 3.4.0 (which added v1 for TS and GC), we're looking into this. |
@kyrofa If you don't have any v1alpha1 resources, please run:
this should fix the issue. |
Version
3.7.2
What Kubernetes platforms are you running on?
DigitalOcean k8s
Steps to reproduce
I have the ingress controller installed via helm chart (v1.4.2 specifically, which contains v3.7.2 of the controller). I still need to manage the CRDs manually though (as documented in the installation instructions), so I have a standard practice of applying them before I upgrade the chart. I've been following the deprecation notices, so I don't have any v1alpha1 resources. Today I decided to upgrade the chart to v2.0.0 (v4.0.0 of the controller). The first step was to apply the CRDs, but I got this:
I'm not sure what to make of it. Any help would be appreciated!
The text was updated successfully, but these errors were encountered: