-
Notifications
You must be signed in to change notification settings - Fork 125
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
Allow customizing conductor hostname #449
Conversation
/test-ubuntu-integration-main |
/test-centos-integration-main |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elfosardo 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 |
In a distributed setup, conductor hostnames will be used for RPC. Currently, the IP address is used which may make TLS configuration much harder. With this change, certain tricks are possible, e.g. using pod DNS names (`<ip>.<namespace>.pod.cluster.local`) combined with a wildcard certificate (`*.<namespace>.pod.cluster.local`). See also metal3-io/ironic-standalone-operator#3 Signed-off-by: Dmitry Tantsur <[email protected]>
8c48f30
to
a4f5ae5
Compare
/test-ubuntu-integration-main |
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
/test-centos-integration-main |
METAL-850: Update packages for OCP 4.16
In a distributed setup, conductor hostnames will be used for RPC.
Currently, the IP address is used which may make TLS configuration
much harder. With this change, certain tricks are possible, e.g. using
pod DNS names (
<ip>.<namespace>.pod.cluster.local
) combined witha wildcard certificate (
*.<namespace>.pod.cluster.local
).See also metal3-io/ironic-standalone-operator#3
Signed-off-by: Dmitry Tantsur [email protected]