-
Notifications
You must be signed in to change notification settings - Fork 827
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
Migrate all Opaque kubernetes Secrets on k8s-infra clusters to ExternalSecrets #2220
Comments
/wg k8s-infra |
#2219 is a first attempt at migrating a secret for k8s-infra-prow-build-trusted |
cc @chaodaiG |
/milestone v1.23 |
Ref: kubernetes#2220 Add a GCP secret that store the Github token used by publishing-bot Signed-off-by: Arnaud Meukam <[email protected]>
Related: - Ref: kubernetes#2220 - Followup of : kubernetes#2825 Signed-off-by: Arnaud Meukam <[email protected]>
/close We could use some docs updates here, and kubernetes-public is still managed via bash instead of terraform. Will continue to track that work under #1731 |
@spiffxp: Closing this issue. In response to this:
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/test-infra repository. |
Clusters that need kubernetes-external-secrets installed:
Secrets that need to be migrated over for k8s-infra-prow-build/prow-build:
$ k --context=prow-build get secrets -A | grep Opaque | awk '{print "- [ ] "$1"/"$2}';
Secrets that need to be migrated over for k8s-infra-prow-build-trusted/prow-build-trusted:
$ k --context=prow-build-trusted get secrets -A | grep Opaque | awk '{print "- [ ] "$1"/"$2}'
Secrets that need to be migrated over for kubernetes-public/aaa
$ k --context=aaa get secrets -A | grep Opaque | awk '{print "- [ ] "$1"/"$2}'
cert-manager/letencrypt-prod-account-key(generated by cert-manager)* new secret, not a migration, but tracking here anyway
The text was updated successfully, but these errors were encountered: