-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
k8s.io/client-go@v0.20.2/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress #7448
Comments
@sysnet4admin: This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
I see this in version 0.43 also |
If your kubernetes version is 1.22, can you try the beta release of the controller and provide feedback https://github.com/kubernetes/ingress-nginx/releases/download/helm-chart-4.0.0/ingress-nginx-4.0.0.tgz /remove-kind bug |
@longwuyuan Thank you for your advice. I am afraid to say that I can't use helm in my environment. |
Ok. Can you try this one and give feedback. https://github.com/kubernetes/ingress-nginx/blob/3c0bfc1ca3eb48246b12e77d40bde1162633efae/deploy/static/provider/baremetal/deploy.yaml |
Oh...it fixed and a little remained error(due to probably uptime) but it looks good.
For your reference (webhook)
|
And ingrss.yaml is worked after removing
#7418 is related issue in my view. **File: ingress.yaml **
|
And then it won't work..
|
Yes, please create/use ingressClass |
@longwuyuan Thank you for your very kindness.
|
From your ingress, can you please remove the annotation "nginx.ingress.kubernetes.io/rewrite-target: /" and add the annotation for the ingressclass. Then update here with result .
|
Remove from Ingress (metadata is remained)
Add in ingressclass
And revitalize nodeport (i.e. remove and create)
But it failed.
|
So for ingress v1, some things have changed with Ingress Class:
Thanks! |
@rikatz I appropriate your help.
|
1st options is worked on properly too. but it should(?) remove Here is the result of 1st option. Check before run
Actual run
|
I am following the test here using helm with v1.0.0-beta.2 but helm doesn't return from the install command and in the ingress controller pods I see
Also the pod |
weird, will test the helm here. About the migration, we are starting to document, and as you are brave users already helping us on this, wdyt? #7441 (review) |
By disabling the admission hook in the yaml values I got the ingress working again. Will check #7441 if we can help |
@muka I tested beta3 and it works without disabling admission hook, I only have to add |
Has this something to do with ? EDIT: Beta version fixed the issue for me. |
I was facing the same issue on Kubernetes version 1.22, this helm release worked for me. However, I had to disable "ValidatingWebhookConfiguration". |
we have improved the validation webhook container as well. I'm closing this, as apparently the v1 beta3 solves what was described here but feel free to reopen! |
/close |
@rikatz: Closing this issue. In response to this:
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/test-infra repository. |
I am on Minikube version 1.23 and am seeing the same problem. Should I still need to use the beta version? |
NGINX Ingress controller version:
Kubernetes version (use
kubectl version
):Environment:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
uname -a
):Install tools:
Others:
What happened:
I have encountered
reflector
still point out v1beta1.ingress even I follow compatible procedure for newest 1.22.Support Versions table
What you expected to happen:
properly deployed without error :)
How to reproduce it:
Download this bundle pack
https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.0.0-alpha.2
deploy this location's manifest deploy/static/provider/baremetal/deploy.yaml
And check above
/kind bug
The text was updated successfully, but these errors were encountered: