-
Notifications
You must be signed in to change notification settings - Fork 4k
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
magnum: add an option to create insecure TLS connections #5210
magnum: add an option to create insecure TLS connections #5210
Conversation
We use self-signed certificates in the openstack for test purposes. It is not always easy to bring a CA certificate. And so we ran into the problem that there is no option to not check the validity of the certificate in the autoscaler. This patch adds a new option for the magnum plugin: tls-insecure Signed-off-by: Anton Kurbatov <[email protected]>
|
Welcome @antonkurbatov! |
/easycla |
/assign @aleksandra-malinowska |
cc: @tghartland |
Hi @mwielgus On reading the code diff, this looks fine to me. I'm not working at CERN any more and while I do have access to another openstack cloud, magnum isn't a major service in it (kubernetes 1.15 is the highest version available). I'm happy to keep reviewing for small changes like this, but if there were any big magnum API changes that needed autoscaler work then at that point I'd ask someone at CERN to step up. I hope that arrangement is acceptable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: antonkurbatov, mwielgus 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 |
…ls-insecure magnum: add an option to create insecure TLS connections
We use self-signed certificates in the openstack for test purposes. It is not always easy to bring a CA certificate. And so we ran into the problem that there is no option to not check the validity of the certificate in the autoscaler.
This patch adds a new option for the magnum plugin: tls-insecure
Signed-off-by: Anton Kurbatov [email protected]
Which component this PR applies to?
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: