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

*: Add repo update steps #4

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

*: Add repo update steps #4

wants to merge 3 commits into from

Conversation

inigohu
Copy link

@inigohu inigohu commented Jan 10, 2024

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.

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
@inigohu
Copy link
Author

inigohu commented Jan 11, 2024

We can include the commit sha or the revision tag to the backup branch.

Copy link

@glerchundi glerchundi left a 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?

@inigohu inigohu force-pushed the feature/add-repo-update branch from e2d3ee0 to 125d57a Compare January 11, 2024 11:48
@inigohu
Copy link
Author

inigohu commented Jan 11, 2024

I don't see the step in which we point to the specific version before rebasing?

Updated

@inigohu inigohu requested a review from glerchundi January 11, 2024 12:23
UPDATE.md Show resolved Hide resolved
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.
@glerchundi
Copy link

glerchundi commented Jan 26, 2024

➜ vault-secrets-operator git:(main) git tag -d v0.4.3
➜ vault-secrets-operator git:(main) git tag v0.4.3 a61e79f
➜ vault-secrets-operator git:(main) git push origin v0.4.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants