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

feat: Add StorageID field to secrets and use it for replication ID #259

Merged
merged 1 commit into from
Feb 13, 2025

Conversation

vbnrh
Copy link
Member

@vbnrh vbnrh commented Feb 12, 2025

Adds a new StorageID field to blue/green secrets and updates the replication ID generation to use storage IDs instead of FSIDs. Key changes:

  • Add storage_id field to all secret types (blue/green/hub)
  • Update secret handlers to properly propagate storage IDs between secrets
  • Add helper functions to get storage IDs from different secret types
  • Update replication ID generation to use storage IDs instead of FSIDs
  • Add tests for storage ID handling and verification
  • Update labelCephClusters to use storage IDs for replication ID

@vbnrh vbnrh force-pushed the fix-replication-id branch 2 times, most recently from d6d2e52 to ee4a201 Compare February 13, 2025 02:35
@vbnrh
Copy link
Member Author

vbnrh commented Feb 13, 2025

/assign @umangachapagain

@vbnrh
Copy link
Member Author

vbnrh commented Feb 13, 2025

/test integration-test

Adds a new StorageID field to blue/green secrets and updates the replication ID
generation to use storage IDs instead of FSIDs. Key changes:

- Add storage_id field to all secret types (blue/green/hub)
- Update secret handlers to properly propagate storage IDs between secrets
- Add helper functions to get storage IDs from different secret types
- Update replication ID generation to use storage IDs instead of FSIDs
- Add tests for storage ID handling and verification
- Update labelCephClusters to use storage IDs for replication ID

Signed-off-by: vbadrina <[email protected]>
@vbnrh vbnrh force-pushed the fix-replication-id branch from ee4a201 to 774d763 Compare February 13, 2025 05:41
@openshift-ci openshift-ci bot added the lgtm label Feb 13, 2025
Copy link
Contributor

openshift-ci bot commented Feb 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umangachapagain, vbnrh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [umangachapagain,vbnrh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vbnrh
Copy link
Member Author

vbnrh commented Feb 13, 2025

/test integration-test

@openshift-merge-bot openshift-merge-bot bot merged commit ec76c39 into red-hat-storage:main Feb 13, 2025
11 checks passed
@vbnrh
Copy link
Member Author

vbnrh commented Feb 13, 2025

/cherrypick release-4.18

@openshift-cherrypick-robot

@vbnrh: new pull request created: #260

In response to this:

/cherrypick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants