Closed BenTheElder closed 2 years ago
SIG Testing notice / consensus thread: https://groups.google.com/g/kubernetes-sig-testing/c/Y1raklkjFYw
Will also raise this in #sig-testing slack.
+1
+1
There is also the Kubernetes Secrets Store CSI Driver project that provides an alternate solution if you don't like Kubernetes External Secrets(KES).
https://github.com/kubernetes-sigs/secrets-store-csi-driver
https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp
On a sidenote, KES has been deprecated in favour of External Secrets Operator(a go rewrite of KES). I'll log a separate issue in k/k8s.io repo to track that migration as it will impact k8s-infra in the future.
+1 from me.
There's already a test-infra issue tracking that migration, the state of those projects is not a blocker for archiving this incomplete, inactive, and unused project though.
Thanks
Still only +1, this is ready to move forward. Will ping admins.
Repo has been archived: kubernetes-retired/k8s-gsm-tools Teams removal: https://github.com/kubernetes/org/pull/3514 sigs.yaml updated: https://github.com/kubernetes/community/pull/6712 Notice sent to sig-testing: https://groups.google.com/g/kubernetes-sig-testing/c/Y1raklkjFYw/m/8SJI5yZ6AwAJ
If you have any questions please feel free to reopen.
Thank you!
/close
@ameukam: Closing this issue.
Thank you!
Repository to archive
https://github.com/kubernetes-sigs/k8s-gsm-tools
Repository and/or sig subproject owners that are approving this archival
@BenTheElder (repo root approval OWNER, SIG Testing Chair + TL)
When should this be done
whenever is convenient, following lazy consensus
Additional context for request
This project didn't quite ship to production, and since then we've adopted an ecosystem project "Kubernetes External Secrets" instead:
https://github.com/kubernetes/test-infra/blob/d16a6c88145bc62fafc1fa4bf6d571c46d64bc27/prow/prow_secrets.md#prow-secrets-management
With nobody actively developing it, and no usage in the Kubernetes project, we should archive it.
I'm going to forward this request to our mailinglist for lazy consensus, I think we should give some additional time given many folks are busy with KubeCon right now, I just didn't want to forget to file this.
Let's move forward after say, June 1st, if there are no objections before then.
/sig testing