Closed rzvoncek closed 2 months ago
Attention: Patch coverage is 78.73563%
with 37 lines
in your changes missing coverage. Please review.
Project coverage is 59.14%. Comparing base (
8804770
) to head (6dc5aaf
). Report is 20 commits behind head on main.:exclamation: Current head 6dc5aaf differs from pull request most recent head af184aa
Please upload reports for the commit af184aa to get more accurate results.
Files | Patch % | Lines |
---|---|---|
pkg/reaper/deployment.go | 85.81% | 19 Missing and 1 partial :warning: |
controllers/reaper/reaper_controller.go | 43.33% | 16 Missing and 1 partial :warning: |
@burmanm , I've resolved all the comments you had, plus I've amended Reaper's e2e tests to cover deployment as a STS. I chose this instead of creating a brand new e2e test. I hope it's okay. Could you please have another look?
Issues
5 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Tests passed, merging.
What this PR does: This PR adds the option to configure Reaper to use a memory sotrage backend. If this storage type is used, Reaper will be deployed as a Stateful Set instead of a Deployment. It will also get a new volume to store the data on. This volume is not being cleared up after Reaper's parent k8ssandra cluster object gets deleted. This is intentional - we want to keep that data, plus it's a pre-work for deploying reaper individually (w/o the k8ssandra cluster).
Which issue(s) this PR fixes: Fixes #1275
Checklist