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

Quickstart installation fails on runtimes installation step [main branch] #370

Closed
mzegla opened this issue May 9, 2023 · 2 comments · Fixed by #364
Closed

Quickstart installation fails on runtimes installation step [main branch] #370

mzegla opened this issue May 9, 2023 · 2 comments · Fixed by #364
Assignees
Labels
bug Something isn't working

Comments

@mzegla
Copy link

mzegla commented May 9, 2023

Hi,

Some time ago I used quickstart guide to quickly install ModelMesh on my K8S cluster and it all went smoothly.
In that guide there's a part with:

RELEASE=release-0.10
git clone -b $RELEASE --depth 1 --single-branch https://github.com/kserve/modelmesh-serving.git
cd modelmesh-serving

Today I wanted to install ModelMesh from the main branch (with --enable-self-signed-ca in installation options), but failed on servingruntimes installation step with error:

Installing ModelMesh Serving built-in runtimes
# Warning: 'bases' is deprecated. Please use 'resources' instead. Run 'kustomize edit fix' to update your Kustomization automatically.
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "servingruntime.modelmesh-webhook-server.default": failed to call webhook: Post "https://modelmesh-webhook-server-service.modelmesh-serving.svc:9443/validate-serving-modelmesh-io-v1alpha1-servingruntime?timeout=10s": Service Unavailable
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "servingruntime.modelmesh-webhook-server.default": failed to call webhook: Post "https://modelmesh-webhook-server-service.modelmesh-serving.svc:9443/validate-serving-modelmesh-io-v1alpha1-servingruntime?timeout=10s": Service Unavailable
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "servingruntime.modelmesh-webhook-server.default": failed to call webhook: Post "https://modelmesh-webhook-server-service.modelmesh-serving.svc:9443/validate-serving-modelmesh-io-v1alpha1-servingruntime?timeout=10s": Service Unavailable
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "servingruntime.modelmesh-webhook-server.default": failed to call webhook: Post "https://modelmesh-webhook-server-service.modelmesh-serving.svc:9443/validate-serving-modelmesh-io-v1alpha1-servingruntime?timeout=10s": Service Unavailable

I suppose this may be related to the changes regarding certificates and cert manager introduced since the 0.10 release am I right?
Have you seen such errors?

I've seen similar issue mentioned in cert-manager docs: https://cert-manager.io/docs/troubleshooting/webhook/#error-service-unavailable and the cause seem to be unknown.
I'd appreciate any help or guidance on how to solve this.

@mzegla mzegla added the bug Something isn't working label May 9, 2023
@ckadner ckadner linked a pull request May 9, 2023 that will close this issue
ckadner pushed a commit that referenced this issue May 9, 2023
Remove the `--enable-self-signed-ca` option from the quickstart guide
and webhook information. The quickstart instructions explicitly install the
latest release `v0.10` which does not include the recently added
`--enable-self-signed-ca`. Following the document as-is results in an
`Unknown option` error.

Resolves #370

Signed-off-by: Rafael Vasquez <raf.vasquez@ibm.com>
@ckadner
Copy link
Member

ckadner commented May 9, 2023

Sorry for the inconvenience Miłosz. @rafvasq fixed the docs removing the self-signed certificate option until we have the v0.11.0 release ready.

@mzegla
Copy link
Author

mzegla commented May 10, 2023

Thanks Christian, so I guess that if I wanted to work with the latest ModelMesh (assuming I'd like to contribute at some point and want to test with the latest changes) I should have cert manager set up on my cluster?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants