-
Notifications
You must be signed in to change notification settings - Fork 4
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
testing in air-gapped: TLS handshake error #107
Comments
tested with the simple poddefault example in /tests/integration in an air-gapped environment, the poddefault was applied as expected in spite of the TLS errors.
It seems that the TLS error does not affect the functionality of the webhook operator. |
tried creating a notebook in air-gapped, the pod-default wasn't applied as expected
I still need to investigate what is causing this, whether it's related to the TLS handshake error. |
This issue is possibly related to kubeflow/kubeflow#6708 |
Bug Description
when deploying admission-webhook charm in an air-gapped environment, the charm goes to active, but the workload container has logs of TLS handshake errors. This indicates that the certificates configured in the
MutatingWebhookConfiguration
cannot be verified, and the charm will not act as expected in the bundle.To Reproduce
After setting up the air-gapped environment, go the directory where the charm file is, and deploy the charm with
--resource oci-image
set to the image in the local registry.juju deploy ./admission-webhook_98aac65.charm --resource oci-image=172.17.0.2:5000/kubeflownotebookswg/poddefaults-webhook:v1.7.0 --trust
Environment
following the script in canonical/bundle-kubeflow#682 (comment)
Relevant Log Output
The text was updated successfully, but these errors were encountered: