-
Notifications
You must be signed in to change notification settings - Fork 79
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
Add service to expose DC nodes in the control plane (fixes #1382) #1390
Conversation
Spec: corev1.ServiceSpec{ | ||
Type: corev1.ServiceTypeClusterIP, | ||
Ports: ports, | ||
// We don't provide a selector since the operator manages the Endpoints directly |
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.
I'm not sure if this service should be headless (currently it is not), it seems convenient to use the service name the contact point if a component wants to connect to "any node" in the DC.
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.
Actually, I think the service must be headless if we want to be able to resolve individual pod addresses.
5f759b9
to
30846ac
Compare
30846ac
to
0be32c0
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.
I could not get my 2-dc multi-context kind cluster change the IP of a pod, but adding and removing pods worked as intended.
d25111e
to
011c197
Compare
Quality Gate failedFailed conditions |
What this PR does:
Which issue(s) this PR fixes:
Fixes #1382
Checklist