-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
minio: Set secure=true to enable TLS by default #3168
minio: Set secure=true to enable TLS by default #3168
Conversation
Not using TLS is a security concern, especially if using cloud storage like S3. This should be set to secure to avoid people unknowingly not using TLS. To make the bundled minio still work, I've submitted kubeflow/manifests#950 to set secure=false in this case explicitly.
Not sure how to read the test response. Is it failing because the python dependencies? If so, I'll put this on hold and try to get #3161 in first. |
2 similar comments
Not sure how to read the test response. Is it failing because the python dependencies? If so, I'll put this on hold and try to get #3161 in first. |
Not sure how to read the test response. Is it failing because the python dependencies? If so, I'll put this on hold and try to get #3161 in first. |
Hi @discordianfish , sorry for the noisy test log. Usually we'll need to click into For this specific question I think it's more likely to be caused by backend server init failure. |
@numerology This makes sense, it probably can't connect to minion using TLS. I'm still haven't been able to figure out which manifests revision it uses though. If it's current master, merging kubeflow/manifests#950 should fix this test. |
Ah great, okay it looks like updating the manifests here fixed the test errors. Should be ready to get merged now. |
/assign @IronPan |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: IronPan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Co-authored-by: renmingu <[email protected]>
@Bobgy Why was this reverted? |
We found a bug in recent release. |
@Bobgy Can you be more specific? Maybe next time you revert a commit, you can mention the reason in the commit log, then I could already go ahead and look into fixing it. |
@discordianfish I mentioned the reason in #3192 (comment) (Referenced comment) |
…flow#3168)" (kubeflow#3192)" This reverts commit 743746b.
* minio: Set secure=true to enable TLS by default Not using TLS is a security concern, especially if using cloud storage like S3. This should be set to secure to avoid people unknowingly not using TLS. To make the bundled minio still work, I've submitted kubeflow/manifests#950 to set secure=false in this case explicitly. * minio: secure=false in GCP & standalone manifests
…" (kubeflow#3192) This reverts commit 5cb158d.
…flow#3191) Co-authored-by: renmingu <[email protected]>
…rvability (kubeflow#3217) * Revert "Revert "minio: Set secure=true to enable TLS by default (kubeflow#3168)" (kubeflow#3192)" This reverts commit 743746b. * Fix managed storage specific manifest * Update pipeline.yaml * Update client_manager.go
Not using TLS is a security concern, especially if using cloud storage
like S3. This should be set to secure to avoid people unknowingly not
using TLS.
To make the bundled minio still work, I've submitted
kubeflow/manifests#950 to set secure=false in
this case explicitly.
This change is