Skip to content
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

Merged
merged 5 commits into from
Sep 11, 2024

Conversation

olim7t
Copy link
Contributor

@olim7t olim7t commented Aug 22, 2024

What this PR does:

Which issue(s) this PR fixes:
Fixes #1382

Checklist

  • Changes manually tested
  • Automated Tests added/updated
  • Documentation added/updated
  • CHANGELOG.md updated (not required for documentation PRs)
  • CLA Signed: DataStax CLA

apis/k8ssandra/v1alpha1/constants.go Outdated Show resolved Hide resolved
Spec: corev1.ServiceSpec{
Type: corev1.ServiceTypeClusterIP,
Ports: ports,
// We don't provide a selector since the operator manages the Endpoints directly
Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

@olim7t olim7t mentioned this pull request Aug 30, 2024
5 tasks
@olim7t olim7t marked this pull request as ready for review August 30, 2024 18:11
@olim7t olim7t requested a review from a team as a code owner August 30, 2024 18:11
Copy link
Contributor

@rzvoncek rzvoncek left a 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.

Copy link

sonarcloud bot commented Sep 10, 2024

Quality Gate Failed Quality Gate failed

Failed conditions
6 Security Hotspots
7.9% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

@adejanovski adejanovski merged commit f9502fc into k8ssandra:main Sep 11, 2024
60 of 61 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create a new ClusterIP service in the CP per CassDc
3 participants