-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Probes are not updated #2320
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
Comments
I assume it has to do with the patch type you use (JSON patch v.s. SMP). Could you turn on DEBUG logging and share more on the patch you sent? You may also check https://github.com/kubernetes-client/python/tree/master/examples for examples of patching resources. |
@roycaihw Hey, thanks for response, how can I enable debug logging for the kubernetes module? Is there any config of |
Here is an example for enabling debug logging. |
@roycaihw Thanks, I have done that and I can see that the probes in the PATCH request do not exist if I remove them manually before sending a body request, yet it still isn't removed from GCP. I cannot share the body request itself unfortunately. I am doing PATCH |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What happened (please include outputs or screenshots):
I have a deployment in GCP in a k8s cluster.
I am trying to remove
LivenessProbe
,ReadnessProbe
&&StartupProbe
, however the deployment does not get updated at all.What you expected to happen:
The probes to be removed
How to reproduce it (as minimally and precisely as possible):
V1Deployment
object.Environment:
kubectl version
):python --version
) python 3.12pip list | grep kubernetes
) 29.0.0The text was updated successfully, but these errors were encountered: