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

Pipeline run in error with http: server gave HTTP response to HTTPS client #146

Closed
NohaIhab opened this issue Oct 18, 2023 · 1 comment · Fixed by #148
Closed

Pipeline run in error with http: server gave HTTP response to HTTPS client #146

NohaIhab opened this issue Oct 18, 2023 · 1 comment · Fixed by #148
Labels
bug Something isn't working

Comments

@NohaIhab
Copy link
Contributor

NohaIhab commented Oct 18, 2023

Bug Description

When running the pipeline [Tutorial] DSL - Control structures, the Pipeline fails with the error:

This step is in Error state with this message: Error (exit code 1): failed to put file: Get "https://minio.kubeflow:9000/mlpipeline/?location=": http: server gave HTTP response to HTTPS client

That is due to a discrepancy between our configuration of argo-controller and upstream where in the minio configmap we are setting insecure: false, that value is set by the juju config kubelet-insecure.
The default of kubelet-insecure should be changed to true.

Environment

microk8s 1.25-strict/stable
juju 3.1/stable

Additional Context

No response

@NohaIhab
Copy link
Contributor Author

NohaIhab commented Oct 25, 2023

from the argo docs on configuring minio:

If MinIO is configured to use TLS you need to set the parameter insecure to false.

in Charmed Kubeflow, minio does not use TLS, so we should set insecure to true.

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.

1 participant