-
Notifications
You must be signed in to change notification settings - Fork 822
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
tf/k8s-infra-prow-build: add ExternalSecrets #2858
tf/k8s-infra-prow-build: add ExternalSecrets #2858
Conversation
Turns out the k8s secret has two fields: ssh-private and ssh-public, so we'll instead make a GSM secret per field
I have already run |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chaodaiG, spiffxp 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 |
This appears to have caused kubernetes/kubernetes#105381 |
|
Found a test pod running a node-e2e job
I think that should have an extra newline at the end of it Updated secret value for prow-build-ssh-key-secret-ssh-private |
There's now a newline at the end of the the private key
|
I'll post future updates over in kubernetes/kubernetes#105381 |
Related:
Turns out the k8s secret has two fields: ssh-private and ssh-public, so we'll instead make a GSM secret per field
I populated the GSM secrets, and have added ExternalSecret CRDs to sync the values back to the Kubernetes secrets