-
Notifications
You must be signed in to change notification settings - Fork 68
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
Enable tls #893
Enable tls #893
Conversation
@gabo1208: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov Report
@@ Coverage Diff @@
## main #893 +/- ##
==========================================
+ Coverage 71.11% 71.64% +0.53%
==========================================
Files 43 43
Lines 2970 2984 +14
==========================================
+ Hits 2112 2138 +26
+ Misses 779 766 -13
- Partials 79 80 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
…user custom configurations to rabbitmq connections + added to docs and finishing mtls sample files
…ady in later commits
d854543
to
b8e5151
Compare
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.
Just did a quick pass. There are a few things that stand out:
- I don't think we should have a flag to say "ssl". When it's a RabbitMQCluster, we could get the tls config from that reference. So the ssl field is only useful for the
Secret
reference. It might be okay to do what messaging-topology-operator does which is just rely on the uri to have anhttp
orhttps
. - I see us switching the protocol based on the ssl flag, but not doing loading any of the system certs which may be required for self-sigend certs.
- self-signed certs process would need to be documented (can be punted to followup)
- This would be a feature to add some e2e tests for
For the |
If the self-signed bits aren't in then we should remove those from the release notes and the "Fixes". You'd need to add the ca certs when making the amqp call so it can be trusted. |
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.
Just some minor docs readability things. If you can remove the self-signed bits from the description, this is good to go
I think we should test the |
maybe test the rabbitmqurl method in a following pr? |
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
/override codecov/patch |
@gabo1208: gabo1208 unauthorized: /override is restricted to Repo administrators. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gab-satchi, gabo1208 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 |
/override codecov/patch |
@dprotaso: Overrode contexts on behalf of dprotaso: codecov/patch In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Changes
port
param (if you are not using the RabbitMQ Topology Operator)/kind enhancement
Fixes #818 #566
Release Note
Docs