Zeebe Kubernetes Helm Deployment failed

We are using minikube in Linux server. We are facing some issue in ingress-controller and ingress-admin while executing below helm command, I am getting ingress issue. Please help?

helm install zee-full-helm

Results:
helm install zeebe ./zeebe-full-helm-1.1.2
W1008 00:26:52.363630 1282315 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
W1008 00:26:55.509204 1282315 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
Error: failed post-install: timed out waiting for the condition

[root@master-node jbaji-s]# kubectl get pods
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 1/1 Running 0 7m4s
elasticsearch-master-1 1/1 Running 0 7m4s
elasticsearch-master-2 1/1 Running 0 7m4s
zeebe-ingress-nginx-controller-788b8f5967-sdnsv 0/1 Running 5 (43s ago) 7m4s
zeebe-zeebe-0 0/1 Running 0 7m4s
zeebe-zeebe-1 1/1 Running 0 7m4s
zeebe-zeebe-2 1/1 Running 0 7m4s
zeebe-zeebe-gateway-5cf7fd7cf9-r2pgf 1/1 Running 0 7m4s
zeebe-zeebe-operate-helm-59f76db6dc-drtpt 1/1 Running 0 7m4s

kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
elasticsearch-master ClusterIP 108.101.97.209 9200/TCP,9300/TCP 24m
elasticsearch-master-headless ClusterIP None 9200/TCP,9300/TCP 24m
zeebe-ingress-nginx-controller LoadBalancer 108.100.185.162 80:30713/TCP,443:30230/TCP 24m
zeebe-ingress-nginx-controller-admission ClusterIP 108.105.28.81 443/TCP 24m
zeebe-zeebe ClusterIP None 9600/TCP,26502/TCP,26501/TCP 24m
zeebe-zeebe-gateway ClusterIP 108.108.46.108 9600/TCP,26500/TCP 24m
jbzeebe-zeebe-operate-helm ClusterIP 108.103.12.82 80/TCP 24m
kubernetes ClusterIP 108.96.0.1 443/TCP 25m

Ingress-admin error:
kubectl logs -f jbzeebe-ingress-nginx-admission-patch–1-nn5kt
W1008 04:27:53.014407 1 client_config.go:608] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
{“level”:“info”,“msg”:“patching webhook configurations ‘jbzeebe-ingress-nginx-admission’ mutating=false, validating=true, failurePolicy=Fail”,“source”:“k8s/k8s.go:39”,“time”:“2021-10-08T04:27:53Z”}
{“err”:“the server could not find the requested resource”,“level”:“fatal”,“msg”:“failed getting validating webhook”,“source”:“k8s/k8s.go:48”,“time”:“2021-10-08T04:27:53Z”}

Ingress-controller Error:
kubectl logs -f zeebe-ingress-nginx-controller-788b8f5967-sdnsv



7 nginx.go:254] “Starting NGINX Ingress controller”
I1008 04:47:07.548544 7 event.go:282] Event(v1.ObjectReference{Kind:“ConfigMap”, Namespace:“default”, Name:“jbzeebe-ingress-nginx-controller”, UID:“546933db-c064-47cb-a9f0-9c1992507266”, APIVersion:“v1”, ResourceVersion:“573”, FieldPath:""}): type: ‘Normal’ reason: ‘CREATE’ ConfigMap default/jbzeebe-ingress-nginx-controller
E1008 04:47:08.643633 7 reflector.go:138] k8s.io/client-go@v0.20.0/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource
E1008 04:47:10.124456 7 reflector.go:138] k8s.io/client-go@v0.20.0/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource
E1008 04:47:12.300144 7 reflector.go:138] k8s.io/client-go@v0.20.0/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource
E1008 04:47:17.178634 7 reflector.go:138] k8s.io/client-go@v0.20.0/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource
E1008 04:47:29.620445 7 reflector.go:138] k8s.io/client-go@v0.20.0/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource
E1008 04:47:44.615587 7 reflector.go:138] k8s.io/client-go@v0.20.0/tools/cache/reflector.go:167: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource
I1008 04:48:05.771933 7 main.go:187] “Received SIGTERM, shutting down”
I1008 04:48:05.771960 7 nginx.go:370] “Shutting down controller queues”
E1008 04:48:05.772044 7 store.go:178] timed out waiting for caches to sync


Please help on this issue (or) there any steps when I can deploy zeebe+elasticsearch+operate +tasklist in minikube (linux pc)… ?

Hey @jpcamunda

sorry for the late response. I’m not that familiar with minikube nor kube, but I think it is not easily possible to run the helm charts with these tools, since the services all need a lot of resources. I see also there some questions on SO regarding this, might be that the ingress configuration needs to be changed for that use case kubernetes - Minikube with ingress example not working - Stack Overflow but could be wrong.

Would be interesting what kind of k8 version do you use inside minikube? Which version of the charts you’re using?

Greets
Chris