Closed joekendal closed 4 years ago
@joekendal I cannot reproduce this problem
kind create cluster --image kindest/node:v1.16.9
Creating cluster "kind" ...
✓ Ensuring node image (kindest/node:v1.16.9) 🖼
✓ Preparing nodes 📦
✓ Writing configuration 📜
✓ Starting control-plane 🕹️
✓ Installing CNI 🔌
✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:
kubectl cluster-info --context kind-kind
Thanks for using kind! 😊
aledbf@me ~ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.34.0/deploy/static/provider/cloud/deploy.yaml
namespace/ingress-nginx created
serviceaccount/ingress-nginx created
configmap/ingress-nginx-controller created
clusterrole.rbac.authorization.k8s.io/ingress-nginx created
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx created
role.rbac.authorization.k8s.io/ingress-nginx created
rolebinding.rbac.authorization.k8s.io/ingress-nginx created
service/ingress-nginx-controller-admission created
service/ingress-nginx-controller created
deployment.apps/ingress-nginx-controller created
validatingwebhookconfiguration.admissionregistration.k8s.io/ingress-nginx-admission created
clusterrole.rbac.authorization.k8s.io/ingress-nginx-admission created
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created
job.batch/ingress-nginx-admission-create created
job.batch/ingress-nginx-admission-patch created
role.rbac.authorization.k8s.io/ingress-nginx-admission created
rolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created
serviceaccount/ingress-nginx-admission created
aledbf@me ~ k get pods -n ingress-nginx
NAME READY STATUS RESTARTS AGE
ingress-nginx-admission-create-g74pb 0/1 Completed 0 80s
ingress-nginx-admission-patch-p25jx 0/1 Completed 2 80s
ingress-nginx-controller-68679c6884-xwlmh 0/1 Running 0 90s
This was caused by my attempts to resolve this issue with namespace deletion hanging https://github.com/kubernetes/kubernetes/issues/19317 and in following those suggestions was still unable to resolve it and left my kubernetes in a dsyfunctional, corrupted state of which i could not be bothered to spend hours trying to fix.
Solved it only by deleting all kubernetes data and resetting to factory settings. Which is less than ideal, but didn't matter in my case.
I had the same issue. I had another nginx ingress already installed while I was trying to run
kubectl apply -f <doployment_file_location>
I solved it by running
kubectl delete -f <doployment_file_location>
then
kubectl apply -f <doployment_file_location>
For anyone who finds this.
kubectl delete job nginx-admission-create -n ingress-nginx
When upgrading vom 1.6.4 to 1.7.0 I came to success after manually executing:
kubectl delete job ingress-nginx-admission-create -n ingress-nginx
kubectl delete job ingress-nginx-admission-patch -n ingress-nginx
Is anyone able to explain why this is necessary?
Do you still have the webhook ?
On Tue, 18 Apr, 2023, 5:17 pm Dirk Steinkopf, @.***> wrote:
When upgrading vom 1.6.4 to 1.7.0 I came to success after manually executing:
kubectl delete job ingress-nginx-admission-create -n ingress-nginx kubectl delete job ingress-nginx-admission-patch -n ingress-nginx
Is anyone able to explain why this is necessary?
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/ingress-nginx/issues/5884#issuecomment-1512941027, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGZVWUKTB7XAE2KIEPRE5DXBZ5OBANCNFSM4OXZ7BDA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
When upgrading vom 1.6.4 to 1.7.0 I came to success after manually executing:
kubectl delete job ingress-nginx-admission-create -n ingress-nginx kubectl delete job ingress-nginx-admission-patch -n ingress-nginx
Is anyone able to explain why this is necessary?
This work for me!
NGINX Ingress controller version:
Kubernetes version (use
kubectl version
):Environment:
What happened: