-
Notifications
You must be signed in to change notification settings - Fork 90
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
[400] admission webhook "soft-validate-cr.kubedirector.hpe.com" does not support dry run #568
Comments
|
deleting it solved the issue.
|
LGTM, but worth updating the make teardown script. |
PR #563 happens to include an update to make teardown, which will fix things for those K8s versions where that owner-ref-to-cluster-scope has stopped working. However we probably won't put that PR into the very next KD release so maybe I'll pull in just that particular makefile modification for the next release. |
Or support dry run... |
That should be addressed by PR #563 as well, in that we explicitly set sideEffects to None for the webhook as part of moving it from the v1beta1 MutatingWebhook API to v1. I'm curious about the situation where you're seeing this though. What version of K8s and Kubeflow for example? |
Going to reopen this to consider setting sideEffects to None for the 0.9.0 release (before PR #563 is merged). |
Hi,
Installed k8s cluster.
Deployed Kubeflow - I can create / delete KF notebooks ( Jupyter/Rstudio/Vscode) without any problem
Then Deployed Kubedirector -> but when I try to create KF notebooks, I get :
[400] admission webhook "soft-validate-cr.kubedirector.hpe.com" does not support dry run https://kubeflow.gpu02.lysdemolab.fr/jupyter/api/namespaces/kubeflow-user-example-com/notebooks
Then removed Kubedirector ( make teardown )
But still the same error in KF :-(
So seems that the KD mutating webhook is still there after removal.
The text was updated successfully, but these errors were encountered: