Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

specify longer timeout for readiness probe #10

Merged
merged 1 commit into from
Feb 14, 2022

Conversation

vincentfretin
Copy link
Contributor

I was on Kapsule 1.20.x, I just upgraded to Kapsule 1.21.x, and now when I redeploy my helm chart, I get this error:

helm upgrade --install -f env/preprod.yaml infra helm/infra/
Error: UPGRADE FAILED: cannot patch "wildcard-cert" with kind Certificate: Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": context deadline exceeded

Looking at scaleway-webhook pod, there is an issue with the readiness probe:

kubectl describe pod/scaleway-webhook-587b778874-m5q74
  Normal   Started    104s  kubelet            Started container scaleway-webhook
  Warning  Unhealthy  102s  kubelet            Readiness probe failed: Get "https://100.64.2.134:443/healthz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Reading https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes
It appears that the default timeout is 1s, I had to change the helm chart to use

readinessProbe:
  timeoutSeconds: 5

(I didn't test lower than 5s)

and redeploy:

helm upgrade scaleway-webhook deploy/scaleway-webhook --set secret.accessKey=$SCW_ACCESS_KEY --set secret.secretKey=$SCW_SECRET_KEY

to fix the issue.

Copy link
Contributor

@Sh4d1 Sh4d1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG, thanks!

@Sh4d1 Sh4d1 merged commit 7368253 into scaleway:main Feb 14, 2022
@vincentfretin vincentfretin deleted the patch-1 branch February 14, 2022 10:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants