I am still learning Kubernetes clustering and I have got this problem:
I have kubernetes cluster with 3 nodes on OpenSuse 15.4 and attempting to install Rancher, but helm is failing to get and install cert-manager..
helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace -- version v1.7.1 --set startupapicheck.timeout=10m --set webhook.timeoutSeconds=30 --debug
install.go:194: [debug] Original chart version: "v1.7.1"
install.go:211: [debug] CHART PATH: /home/<cut>/.cache/helm/repository/cert-manager-v1.7.1.tgz
client.go:133: [debug] creating 1 resource(s)
client.go:133: [debug] creating 39 resource(s)
client.go:477: [debug] Starting delete for "cert-manager-startupapicheck" ServiceAccount
client.go:481: [debug] Ignoring delete failure for "cert-manager-startupapicheck" /v1, Kind=ServiceAccount: serviceaccounts "cert- manager-startupapicheck" not found
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "cert-manager-startupapicheck:create-cert" Role
client.go:481: [debug] Ignoring delete failure for "cert-manager-startupapicheck:create-cert" rbac.authorization.k8s.io/v1, Kind=R ole: roles.rbac.authorization.k8s.io "cert-manager-startupapicheck:create-cert" not found
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "cert-manager-startupapicheck:create-cert" RoleBinding
client.go:481: [debug] Ignoring delete failure for "cert-manager-startupapicheck:create-cert" rbac.authorization.k8s.io/v1, Kind=R oleBinding: rolebindings.rbac.authorization.k8s.io "cert-manager-startupapicheck:create-cert" not found
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "cert-manager-startupapicheck" Job
client.go:481: [debug] Ignoring delete failure for "cert-manager-startupapicheck" batch/v1, Kind=Job: jobs.batch "cert-manager-sta rtupapicheck" not found
client.go:133: [debug] creating 1 resource(s)
client.go:703: [debug] Watching for changes to Job cert-manager-startupapicheck with timeout of 5m0s
client.go:731: [debug] Add/Modify event for cert-manager-startupapicheck: ADDED
client.go:770: [debug] cert-manager-startupapicheck: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:731: [debug] Add/Modify event for cert-manager-startupapicheck: MODIFIED
client.go:770: [debug] cert-manager-startupapicheck: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condition
helm.go:84: [debug] failed post-install: timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
/home/abuild/rpmbuild/BUILD/helm-3.11.1/cmd/helm/install.go:141
github.com/spf13/cobra.(*Command).execute
/home/abuild/rpmbuild/BUILD/helm-3.11.1/vendor/github.com/spf13/cobra/command.go:916
github.com/spf13/cobra.(*Command).ExecuteC
/home/abuild/rpmbuild/BUILD/helm-3.11.1/vendor/github.com/spf13/cobra/command.go:1044
github.com/spf13/cobra.(*Command).Execute
/home/abuild/rpmbuild/BUILD/helm-3.11.1/vendor/github.com/spf13/cobra/command.go:968
main.main
/home/abuild/rpmbuild/BUILD/helm-3.11.1/cmd/helm/helm.go:83
runtime.main
/usr/lib64/go/1.18/src/runtime/proc.go:250
runtime.goexit
/usr/lib64/go/1.18/src/runtime/asm_amd64.s:1571
Any help would be greatly appreciated.
I was trying to reinstall whole cluster, but no joy.
Based on the evidence found in the comments, it would appear that something went wrong while configuring the network plugin.
Is it possible that you installed Flannel before finishing the cluster setup? Maybe before the kubeadm init.
I suggest doing a clean installation of the CNI and your applications.
Here a problem very similar to yours: kubernetes installation and kube-dns: open /run/flannel/subnet.env: no such file or directory