11.2 Ingress Controller lab issue

Hi, I am trying to use helm to deploy the ingress controller as indicated on step 5, but I get this error:
~/ingress-nginx$ helm install myingress .
Error: rendered manifests contain a resource that already exists. Unable to continue with install: IngressClass "nginx" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "myingress"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"
I've checked all the resources out and haven't found such a resource. What can I do?
Answers
-
Hi @paristiz,
It seem that the installation process found one of its defined resource already installed in the cluster. Was the
helm install
step executed earlier? Did it produce any errors then?You can use the
helm uninstall
command to remove a prior release.Regards,
-Chris0 -
Hi Chris, thank you for your answer. I followed the instructions, specifically steps 4 and 5 regarding modify the values.yaml file and try to install the myingress. The issue raised after try to install it and nothing remains in helm:
pablo@pablo-VirtualBox:~/ingress-nginx$ helm install myingress .
Error: rendered manifests contain a resource that already exists. Unable to continue with install: IngressClass "nginx" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "myingress"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"pablo@pablo-VirtualBox:~/ingress-nginx$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
pablo@pablo-VirtualBox:~/ingress-nginx$As there isn't anything under helm, I can't use helm uninstall.
Best regards,
Pablo A.
0 -
Hello,
I'm unaware of what the issue is in particular, perhaps we can do some troubleshooting. What version of helm are you using? Had you run this lab before, perhaps removed helm and re-added it? Do you have an ingress controller running in any namespace?
Regards,
0 -
Found another issue related with that LAB that I will post on a separate entry.
0 -
Hi,
Thank you all for the answers. I am sorry about the lack of feedback but I was on vacation for some weeks. After I came back, I read the other 11.2 post and used the solution proposed by Proliant:"The problem is solved after pulling an older version: helm fetch --version 3.36.0 ingress/ingress-nginx"
Indeed, now after try of install the deployment is not showing the previous error, but after some time failed:
pablo@pablo-VirtualBox:~/ingress-nginx$ helm install myingress .
Error: failed pre-install: timed out waiting for the condition
pablo@pablo-VirtualBox:~/ingress-nginx$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
myingress default 1 2021-10-17 23:10:43.034228936 -0300 -03 failed ingress-nginx-3.36.0 0.49.0These are the pods in all the namespaces:
pablo@pablo-VirtualBox:~/ingress-nginx$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default myingress-ingress-nginx-admission-create-bjc2l 0/1 CrashLoopBackOff 5 7m36s
default myingress-ingress-nginx-admission-patch-ccvq6 0/1 Completed 0 126m
default web-one-fb4bdb45d-99hpn 1/1 Running 0 35m
default web-one-fb4bdb45d-jsbbc 0/1 NodeAffinity 0 33h
default web-two-fb4bdb45d-jfctd 1/1 Running 0 35m
default web-two-fb4bdb45d-sk46h 0/1 NodeAffinity 0 33h
kube-system calico-kube-controllers-7dbc97f587-855rq 1/1 Running 27 197d
kube-system calico-node-stgg9 1/1 Running 30 203d
kube-system calico-node-xpzpf 1/1 Running 12 203d
kube-system coredns-f9fd979d6-hltnx 1/1 Running 13 98d
kube-system coredns-f9fd979d6-wppvr 1/1 Running 13 98d
kube-system etcd-pablo-virtualbox 1/1 Running 34 203d
kube-system kube-apiserver-pablo-virtualbox 1/1 Running 37 203d
kube-system kube-controller-manager-pablo-virtualbox 1/1 Running 56 203d
kube-system kube-proxy-2hmfn 1/1 Running 30 203d
kube-system kube-proxy-gbqtf 1/1 Running 12 203d
kube-system kube-scheduler-pablo-virtualbox 1/1 Running 55 203d
linkerd-viz grafana-b48ddb5d8-4njb7 1/1 Running 0 35m
linkerd-viz grafana-b48ddb5d8-sn6wd 0/1 NodeAffinity 0 117m
linkerd-viz metrics-api-9d86bf5f7-4nprg 0/1 CrashLoopBackOff 13 35m
linkerd-viz metrics-api-9d86bf5f7-gvgdr 0/1 NodeAffinity 0 114m
linkerd-viz prometheus-5b49dcd6bf-7mncz 0/1 NodeAffinity 0 114m
linkerd-viz prometheus-5b49dcd6bf-bthvd 1/1 Running 0 35m
linkerd-viz tap-77c87d66f4-95wv8 0/1 NodeAffinity 0 117m
linkerd-viz tap-77c87d66f4-s2fsc 0/1 Running 13 35m
linkerd-viz tap-injector-54d45cb47-btk7d 0/1 NodeAffinity 0 114m
linkerd-viz tap-injector-54d45cb47-h6n5s 0/1 Running 13 35m
linkerd-viz web-74c6bbd948-5ln9m 0/1 NodeAffinity 0 113m
linkerd-viz web-74c6bbd948-rv77l 0/1 CrashLoopBackOff 13 35m
linkerd linkerd-controller-75d67d694c-4j5rt 0/2 NodeAffinity 0 114m
linkerd linkerd-controller-75d67d694c-qvzwn 2/2 Running 1 35m
linkerd linkerd-destination-85894f6879-r9zll 0/2 NodeAffinity 0 114m
linkerd linkerd-destination-85894f6879-vx2md 1/2 CrashLoopBackOff 13 35m
linkerd linkerd-identity-c685df5b-fj6rb 0/2 NodeAffinity 0 114m
linkerd linkerd-identity-c685df5b-nhpr2 2/2 Running 0 35m
linkerd linkerd-proxy-injector-55977c4876-c689j 2/2 Running 0 35m
linkerd linkerd-proxy-injector-55977c4876-kp9dl 0/2 NodeAffinity 0 115m
linkerd linkerd-sp-validator-c9d67fc88-dmvg5 2/2 Running 1 35m
linkerd linkerd-sp-validator-c9d67fc88-h94pt 0/2 NodeAffinity 0 114mI don't know how to move on with this new error. Any help will be appreciated.
Pablo A.
0 -
to complement previous post, these are the last events of the pod relating to "my-ingress" (myingress-ingress-nginx-admission-patch-ccvq6):
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 122m (x18 over 129m) default-scheduler 0/2 nodes are available: 1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate, 1 node(s) had taint {node.kubernetes.io/unreachable: }, that the pod didn't tolerate.
Normal Scheduled 121m default-scheduler Successfully assigned default/myingress-ingress-nginx-admission-patch-ccvq6 to pablo-virtualbox
Warning FailedMount 121m kubelet, pablo-virtualbox MountVolume.SetUp failed for volume "myingress-ingress-nginx-admission-token-xg8zf" : failed to sync secret cache: timed out waiting for the condition
Normal Pulling 121m kubelet, pablo-virtualbox Pulling image "docker.io/jettech/kube-webhook-certgen:v1.5.1"
Normal Pulled 119m kubelet, pablo-virtualbox Successfully pulled image "docker.io/jettech/kube-webhook-certgen:v1.5.1" in 1m8.115190027s
Normal Created 119m kubelet, pablo-virtualbox Created container patch
Normal Started 119m kubelet, pablo-virtualbox Started container patch
Normal SandboxChanged 119m kubelet, pablo-virtualbox Pod sandbox changed, it will be killed and re-created.
Warning FailedCreatePodSandBox 119m kubelet, pablo-virtualbox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "myingress-ingress-nginx-admission-patch-ccvq6": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"\"": unknown0 -
Hi @paristiz,
It seems one of your nodes is not accepting workload because of
disk-pressure
andunreachable
. Is one of your nodes running low on disk space? How is vbox managing the virtual disk space for your nodes - statically or dynamically?The Events of the pods with
CrashLoopBackOff
andNodeAffinity
statuses may provide more helpful details about the failure causes and error messages.What do you see with
kubectl get nodes
andkubectl describe node <node-name>
?Regards,
-Chris0
Categories
- All Categories
- 232 LFX Mentorship
- 232 LFX Mentorship: Linux Kernel
- 812 Linux Foundation IT Professional Programs
- 365 Cloud Engineer IT Professional Program
- 183 Advanced Cloud Engineer IT Professional Program
- 82 DevOps Engineer IT Professional Program
- 151 Cloud Native Developer IT Professional Program
- 138 Express Training Courses & Microlearning
- 138 Express Courses - Discussion Forum
- Microlearning - Discussion Forum
- 6.4K Training Courses
- 48 LFC110 Class Forum - Discontinued
- 71 LFC131 Class Forum
- 44 LFD102 Class Forum
- 228 LFD103 Class Forum
- 19 LFD110 Class Forum
- 42 LFD121 Class Forum
- 18 LFD133 Class Forum
- 8 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 5 LFD210 Class Forum
- 5 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 702 LFD259 Class Forum
- 111 LFD272 Class Forum - Discontinued
- 4 LFD272-JP クラス フォーラム
- 13 LFD273 Class Forum
- 186 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 3 LFS116 Class Forum
- 7 LFS118 Class Forum
- LFS120 Class Forum
- 9 LFS142 Class Forum
- 8 LFS144 Class Forum
- 4 LFS145 Class Forum
- 3 LFS146 Class Forum
- 2 LFS148 Class Forum
- 15 LFS151 Class Forum
- 4 LFS157 Class Forum
- 45 LFS158 Class Forum
- LFS158-JP クラス フォーラム
- 10 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 32 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム - Discontinued
- 19 LFS203 Class Forum
- 135 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 52 LFS241 Class Forum
- 48 LFS242 Class Forum
- 38 LFS243 Class Forum
- 15 LFS244 Class Forum
- 5 LFS245 Class Forum
- LFS246 Class Forum
- LFS248 Class Forum
- 52 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 156 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 9 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.3K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 132 LFS260 Class Forum
- 160 LFS261 Class Forum
- 43 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 25 LFS268 Class Forum
- 32 LFS269 Class Forum
- 6 LFS270 Class Forum
- 202 LFS272 Class Forum - Discontinued
- 2 LFS272-JP クラス フォーラム
- 4 LFS147 Class Forum
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 12 LFW111 Class Forum
- 262 LFW211 Class Forum
- 184 LFW212 Class Forum
- 15 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 797 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 104 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 759 Linux Distributions
- 82 Debian
- 67 Fedora
- 17 Linux Mint
- 13 Mageia
- 23 openSUSE
- 148 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 354 Ubuntu
- 470 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 69 Mobile Computing
- 18 Android
- 38 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 375 Off Topic
- 115 Introductions
- 175 Small Talk
- 24 Study Material
- 807 Programming and Development
- 304 Kernel Development
- 485 Software Development
- 1.8K Software
- 263 Applications
- 183 Command Line
- 3 Compiling/Installing
- 987 Games
- 317 Installation
- 103 All In Program
- 103 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)