Helm installation fails with timeout on k8s 1.16.x

Describe the bug Helm chart installation gets timed out waiting for readiness probe on k8s 1.16.x Readiness probe fails maybe because MutatingWebhookConfigurations is not created at all in k8s 1.16.x

works fine on k8s 1.18.x as expected on the same setup.

Expected behavior Helm chart installation succeeds and all 3 pods of the deployment are in ready state

Optional: To reproduce

Minikube

cd connaisseur/
sudo minikube start --driver=none --kubernetes-version=v1.16.15
sudo chown -R $USER $HOME/.kube $HOME/.minikube
make install
sudo minikube delete

sudo minikube start --driver=none --kubernetes-version=v1.18.0
sudo chown -R $USER $HOME/.kube $HOME/.minikube
make install
sudo minikube delete

Microk8s

cd connaisseur/
sudo snap refresh microk8s --classic --channel=1.16/stable
sudo microk8s start
sudo microk8s enable dns
sudo microk8s config > ~/.kube/config
make install
sudo microk8s stop

sudo snap refresh microk8s --classic --channel=1.18/stable
sudo microk8s start
sudo microk8s enable dns
sudo microk8s config > ~/.kube/config
make install
sudo microk8s stop

Optional: Versions (please complete the following information as relevant):

• OS: Ubuntu-18.04 on wsl2
• Kubernetes Cluster: microk8s-1.16/stable OR minikube-1.14(k8s-1.16.15, vm-driver=none)
• Notary Server: notary.docker.io
• Container registry: registry.docker.io
• Connaisseur: master
• Other:

Optional: Additional context <Add any other context or screenshots about the bug here.>

[Starkteetje]

Hi @akuma5157

I tried setting up Connaisseur on kubernetes 1.16 with minikube (docker driver, driver none does not work with my setup) and that worked. Maybe pulling of the Connaisseur image took longer than the Bootstrap Sentinel Timeout, which can be changed here. Tldr of the ADR: To ensure Connaisseur Pods dont show ready, when the webhook does not exist, they need to check for it. Its existence would block deployment of Connaisseur though, so we have a special Pod to solve this chicken-egg problem that lives for 60s by default

If increasing the timeout solves your problem, we’d be interest to get that feedback and might decide to increase the default.

I’ll also try the microK8s setup just to be sure, but wanted to give you quick feedback

[Starkteetje]

Hey @akuma5157 since you did not come back to us, I’ll assume your issue was resolved. Feel free to reopen if you have additional questions.