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

[FEATURE]: Add A cluster identifier thats human readable in the "Description" field of the created NFS Export #1412

Open
ergonzalezn opened this issue Jul 31, 2024 · 2 comments
Labels
needs-triage Issue requires triage. type/feature-request New feature request. This is the default label associated with a feature request issue.

Comments

@ergonzalezn
Copy link

Describe the solution you'd like
when you have multiple Kubernetes clusters but want to keep everything under an access zone, customer wants to be able to either automically add the Kubernetes cluster name or even better, to customize from deployment the "Description" field of the NFS export thats getting created with the CSI deployment

Describe alternatives you've considered
Alternative is to do it manually, but when the description gets updated with something not humaly readable like this from my customer:

CSI_QUOTA_ID:aSxhGQEAAAAAAAAAAAAAQEMAAAAAAAAA

its hard for an powerscale Admin to actually change it but pointing to which cluster owns which export becomes a huge challenge if you do it manually.

Additional context
Add any other context or screenshots about the feature request here.

Current View from a real environment

isi nfs exports view --zone=risess --id=26

                 ID: 26
               Zone: risess
              Paths: /ifs/dvtcisln0004/risess/csi/csivol-6e5d903254
        **Description: CSI_QUOTA_ID:aSxhGQEAAAAAAAAAAAAAQEMAAAAAAAAA**

Desired View

isi nfs exports view --zone=risess --id=26

                 ID: 26
               Zone: risess
              Paths: /ifs/dvtcisln0004/risess/csi/csivol-6e5d903254
        **Description: Openshift Cluster: Cluster01 App: User-App-01**
@ergonzalezn ergonzalezn added needs-triage Issue requires triage. type/feature-request New feature request. This is the default label associated with a feature request issue. labels Jul 31, 2024
@csmbot
Copy link
Collaborator

csmbot commented Jul 31, 2024

@ergonzalezn: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.


We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].

@vyshakav-dell
Copy link

Thanks for submitting the feature request, @ergonzalezn. We will evaluate the request and add it to our backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Issue requires triage. type/feature-request New feature request. This is the default label associated with a feature request issue.
Projects
None yet
Development

No branches or pull requests

3 participants