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

Update name of service routed to by reaper ingress rule #432

Merged
merged 2 commits into from
Feb 25, 2021

Conversation

jdonenine
Copy link
Contributor

What this PR does:

  • Talked with @jsanda about this one and he explained that the recent changes in reaper-operator necessitated a change to the structure of the service name deployed
  • This brings the name in-line with what reaper-operator produces and updates the tests

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

Checklist

  • Changes manually tested
  • Chart versions updated (if necessary)
  • Automated Tests added/updated
  • Documentation added/updated
  • CLA Signed: DataStax CLA

* Talked with @jsanda about this one and he explained that the recent changes in reaper-operator necessitated a change to the structure of the service name deployed
* This brings the name in-line with what reaper-operator produces and updates the tests
K8ssandra automation moved this from In progress to Reviewer approved Feb 25, 2021
@jdonenine jdonenine marked this pull request as ready for review February 25, 2021 13:14
@jdonenine
Copy link
Contributor Author

This isn't the final fix for the overall problem, there is another issue related to release name vs cluster name with reaper, @burmanm is looking at that quickly. But this should fix the problem when release name == cluster name.

@jdonenine jdonenine merged commit ecdc4f1 into main Feb 25, 2021
K8ssandra automation moved this from Reviewer approved to Done Feb 25, 2021
@jdonenine jdonenine deleted the bugfix/reaper-ingress branch February 25, 2021 13:15
jeffreyscarpenter pushed a commit to jeffreyscarpenter/k8ssandra that referenced this pull request Mar 10, 2021
* Update name of service routed to by reaper ingress rule
* Talked with @jsanda about this one and he explained that the recent changes in reaper-operator necessitated a change to the structure of the service name deployed
* This brings the name in-line with what reaper-operator produces and updates the tests

* Bump chart version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
K8ssandra
  
Done
Development

Successfully merging this pull request may close these issues.

Reaper ingress is not working
2 participants