You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then used the katib python SDK as per the example in the docs.
Creating an experiment fails with:
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: failed calling webhook \"defaulter.experiment.katib.kubeflow.org\": could not get REST client: unable to load root certificates: unable to parse bytes as PEM block","reason":"InternalError","details":{"causes":[{"message":"failed calling webhook \"defaulter.experiment.katib.kubeflow.org\": could not get REST client: unable to load root certificates: unable to parse bytes as PEM block"}]},"code":500}
From some related thread on Slack I gather that the MutatingWebhookConfiguration having empty caBundle may be related:
kubectl get MutatingWebhookConfiguration katib.kubeflow.org -o yaml
It seems that the certification was not set to webhook configurations appropriately.
Could you check the controller state with kubectl get pods -n kubeflow?
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedMount 3m11s (x527 over 17h) kubelet MountVolume.SetUp failed for volume "cert" : secret "katib-webhook-cert" not found
So it seems a secret needs to be created. Is it possible for the katib-standalone kube configs can handle this? If not then I guess instructions need to be added as to how the user can do this on their own before applying the kube configs.
What happened?
Installed as per the instructions from the docs:
kubectl apply -k "github.com/kubeflow/katib.git/manifests/v1beta1/installs/katib-standalone?ref=v0.17.0"
Then used the katib python SDK as per the example in the docs.
Creating an experiment fails with:
From some related thread on Slack I gather that the MutatingWebhookConfiguration having empty caBundle may be related:
Outputs:
What did you expect to happen?
I expect to be able to use the Python SDK after installing Katib standalone.
Environment
Kubernetes version:
Katib controller version: 0.17.0
Katib Python SDK version: 0.17.0
Impacted by this bug?
Give it a 👍 We prioritize the issues with most 👍
The text was updated successfully, but these errors were encountered: