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 suffix for external ceph client secret name during gRPC response #2512

Merged

Conversation

leelavg
Copy link
Contributor

@leelavg leelavg commented Mar 18, 2024

when provider & client are running in same namespace the cephclient secret name clashes and as the contents will be different we'll add a suffix ".csi" to the secret which wll be managed by client.

Part of [RHSTOR-5487]

@leelavg leelavg force-pushed the 5487-change-secret branch from 84ff31b to b58aa8c Compare March 18, 2024 07:47
@leelavg
Copy link
Contributor Author

leelavg commented Mar 19, 2024

Testing

Initial: (client ns)

# kc get storageclient,storageclaim 
NAME                                           PHASE       CONSUMER
storageclient.ocs.openshift.io/storageclient   Connected   5a061036-e38a-4358-86bc-4ca4e66f34c8

NAME                                                        STORAGETYPE        STORAGEPROFILE   STORAGECLIENTNAME   STORAGECLIENTNAMESPACE     PHASE
storageclaim.ocs.openshift.io/ocs-storagecluster-ceph-rbd   blockpool                           storageclient       openshift-storage-client   Ready
storageclaim.ocs.openshift.io/ocs-storagecluster-cephfs     sharedfilesystem                    storageclient       openshift-storage-client   Ready

# kc get secret | grep rook-ceph
rook-ceph-client-00ec15f6f5c2de4b7d8cfd534ec2c971               Opaque                                2      74s
rook-ceph-client-16d8eae5f3ac71dd1a5efab411e5a537               Opaque                                2      74s
rook-ceph-client-51110512b46636a1ae4ab74dbdaa8cff               Opaque                                2      74s
rook-ceph-client-55cc825bad4b195b90e7b062f1356fad               Opaque                                2      74s

w/ PR content: 

--- deletion and recreation of storageclaims creates below

# kc get storageclient,storageclaim 
NAME                                           PHASE       CONSUMER
storageclient.ocs.openshift.io/storageclient   Connected   5a061036-e38a-4358-86bc-4ca4e66f34c8

NAME                                                        STORAGETYPE        STORAGEPROFILE   STORAGECLIENTNAME   STORAGECLIENTNAMESPACE     PHASE
storageclaim.ocs.openshift.io/ocs-storagecluster-ceph-rbd   blockpool                           storageclient       openshift-storage-client   Ready
storageclaim.ocs.openshift.io/ocs-storagecluster-cephfs     sharedfilesystem                    storageclient       openshift-storage-client   Ready

--- in client ns
# kc get secret | grep rook-ceph
rook-ceph-client-00ec15f6f5c2de4b7d8cfd534ec2c971.csi           Opaque                                2      12m
rook-ceph-client-16d8eae5f3ac71dd1a5efab411e5a537.csi           Opaque                                2      12m
rook-ceph-client-51110512b46636a1ae4ab74dbdaa8cff.csi           Opaque                                2      6m21s
rook-ceph-client-55cc825bad4b195b90e7b062f1356fad.csi           Opaque                                2      6m21s


--- in provider ns
# ko get secret | grep rook-ceph | grep -E '971|537|cff|fad'
rook-ceph-client-00ec15f6f5c2de4b7d8cfd534ec2c971                                                 kubernetes.io/rook                    5      13m
rook-ceph-client-16d8eae5f3ac71dd1a5efab411e5a537                                                 kubernetes.io/rook                    5      13m
rook-ceph-client-51110512b46636a1ae4ab74dbdaa8cff                                                 kubernetes.io/rook                    5      7m30s
rook-ceph-client-55cc825bad4b195b90e7b062f1356fad                                                 kubernetes.io/rook                    5      7m26s

Based on above both operators can exist in same namespace

@nb-ohad
Copy link
Contributor

nb-ohad commented Mar 20, 2024

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 20, 2024
@nb-ohad
Copy link
Contributor

nb-ohad commented Mar 20, 2024

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 20, 2024
@Madhu-1
Copy link
Member

Madhu-1 commented Mar 20, 2024

@nb-ohad we can remove the hold and address #2512 (comment) in a different PR?

@leelavg
Copy link
Contributor Author

leelavg commented Mar 20, 2024

/retest-required

when provider & client are running in same namespace the cephclient
secret name clashes and as the contents will be different we'll add a
suffix ".csi" to the secret which wll be managed by client.

Signed-off-by: Leela Venkaiah G <[email protected]>
@leelavg leelavg force-pushed the 5487-change-secret branch from b58aa8c to a88b7be Compare March 20, 2024 12:57
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2024
@leelavg
Copy link
Contributor Author

leelavg commented Mar 20, 2024

rebased to pull in latest changes for CI.

@leelavg
Copy link
Contributor Author

leelavg commented Mar 20, 2024

/retest

@leelavg
Copy link
Contributor Author

leelavg commented Mar 21, 2024

/test ocs-operator-bundle-e2e-aws

@nb-ohad
Copy link
Contributor

nb-ohad commented Mar 21, 2024

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 21, 2024
@nb-ohad
Copy link
Contributor

nb-ohad commented Mar 21, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 21, 2024
Copy link
Contributor

openshift-ci bot commented Mar 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, nb-ohad

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:

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

@openshift-merge-bot openshift-merge-bot bot merged commit 45e1370 into red-hat-storage:main Mar 21, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants