-
Notifications
You must be signed in to change notification settings - Fork 0
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
*: Add repo update steps #4
base: main
Are you sure you want to change the base?
Conversation
This PR adds the first sample of the main.yaml workflow
This commit adds the ability to specify a namespace for the service account used to authenticate to Vault. This is useful when you want to use a service account in a different namespace than the one the secret (vaultStaticSecret, vaultDynamicSecret) is located. This change is backwards compatible, so if no namespace is specified, the service account will be looked up in the same namespace as the secret. Example: Here the service account that will be used to authenticate to Vault is the service account `default` that it is in the namespace "vault-secrets-operator-system". ```yaml apiVersion: secrets.hashicorp.com/v1beta1 kind: VaultAuth metadata: name: static-auth namespace: app spec: vaultConnectionRef: vault-connection allowedNamespaces: - "*" method: kubernetes mount: demo-auth-mount kubernetes: role: role1 serviceAccount: vault-secrets-operator-system/default ``` Closes hashicorp#336
We can include the commit sha or the revision tag to the backup branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see the step in which we point to the specific version before rebasing?
e2d3ee0
to
125d57a
Compare
Updated |
To avoid future problems with the repo, we need to add the steps to update the repo with the new changes from the upstream repo.
125d57a
to
403fc35
Compare
➜ vault-secrets-operator git:(main) git tag -d v0.4.3 |
To avoid future problems with the repo, we need to add the steps to update the repo with the new changes from the upstream repo.