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

Document the guide for SecretManagerSecretVersion API (Legacy to Direct) #3322

Open
3 tasks done
yuwenma opened this issue Dec 5, 2024 · 0 comments
Open
3 tasks done
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@yuwenma
Copy link
Collaborator

yuwenma commented Dec 5, 2024

Checklist

  • I did not find a related open enhancement request.
  • I understand that enhancement requests filed in the GitHub repository are by default low priority.
  • If this request is time-sensitive, I have submitted a corresponding issue with GCP support.

Describe the feature or resource

We should give clear user guide on the expected behavior for the stale, legacy and deprecated SecretManagerSecretVersion APIs.
spec.deletionPolicy --> delete-policy annotation
spec.IsSecretDataBase64 --> This is encrypted in k8s already
status.version --> Correct the doc because this is a status field and no deprecation.

Additional information

No response

Importance

No response

@yuwenma yuwenma added the enhancement New feature or request label Dec 5, 2024
@yuwenma yuwenma added this to the 1.127 milestone Dec 5, 2024
@yuwenma yuwenma self-assigned this Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant