🌱 Set manager TLS default back to unset#3153
Conversation
Signed-off-by: peppi-lotta <peppi-lotta.saari@est.tech>
2e2f63e to
fcf14ba
Compare
kashifest
left a comment
There was a problem hiding this comment.
whats the reason behind the unsetting? Can you put some context in the description?
I updated the description. |
There was a problem hiding this comment.
It is ok for me and my downstream.
/hold
But let's ask other users too @zaneb @dtantsur @diconico07 @pierrecregut
/approved
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Rozzii The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
no problem with that change on my side 👍 |
|
We don't use these manifests downstream, so no objections here. |
|
@Rozzii Lets unhold this, since we have enough response. |
|
fine with me too |
|
/unhold |
I'm removing tls flag from manager so that the project is not forcing any selection but we rely on the actual default.
In CAPM3 I'm adding overlays that apply the flag when e2e test are run: metal3-io/cluster-api-provider-metal3#3187
What this PR does / why we need it:
Fixes #
Checklist: