-
Notifications
You must be signed in to change notification settings - Fork 663
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
Why manifests/base/service.yaml does not include webhook server port (443) in version 1.7.0~1.5.0? #2080
Comments
Same problem. Edit) I deleted my minikube cluster and restarted. Then seems like working again. |
Thanks for sharing :) It may not be a big issue with missing the webhook server port in previous versions. I`m now just using a master version that does not cause any problems. |
@yeonhooy @show981111 Hi, thank you for creating this issue. |
@tenzen-y Right. I tried to use this command I'm now using master version without ValidatingWebhookConfiguration. |
It's curious. In v1.7.0, the training-operator doesn't have any webhook validations. So, the above error should not happen. |
In other words, we never provided the manifests for the |
I see. May be I performed the master version before performing version v1.7. Thanks!! |
I wonder why manifests/base/service.yaml does not include webhook server port (443) in version 1.7.0~1.4.0?
I tried to use training-operator version 1.7.0 or 1.5.0 (stable version) instead of master version.
However, I found that there is no webhook port for training operator, which seems to cause this error:
Internal error occurred: failed calling webhook "validator.tfjob.training-operator.kubeflow.org": Post "https://training-operator.kubeflow.svc:443/validate-kubeflow-org-v1-tfjob?timeout=10s": no service port 443 found for service "training-operator"
Thanks
The text was updated successfully, but these errors were encountered: