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

rook: zap and values fixes #304

Merged
merged 1 commit into from
Aug 30, 2023
Merged

rook: zap and values fixes #304

merged 1 commit into from
Aug 30, 2023

Conversation

robinAwallace
Copy link
Contributor

What this PR does / why we need it:

Found two issues when trying it out.

Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #

Public facing documentation PR (if applicable)

Special notes for reviewer:

Checklist:

  • Proper commit message prefix on all commits
  • Updated the public facing documentation
  • Is this changeset backwards compatible for existing clusters? Applying:
    • is completely transparent, will not impact the workload in any way.
    • requires running a migration script.
    • requires draining and/or replacing nodes.
    • will break the cluster.
      I.e. full cluster migration is required.

@robinAwallace robinAwallace merged commit 5245720 into main Aug 30, 2023
1 check passed
@robinAwallace robinAwallace deleted the rw/rook-fixes branch August 30, 2023 11:56
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.

4 participants