Skip to content

customizable in hashicorp vault field#6

Open
metanovii wants to merge 1 commit into
vinted:masterfrom
metanovii:vso_fix
Open

customizable in hashicorp vault field#6
metanovii wants to merge 1 commit into
vinted:masterfrom
metanovii:vso_fix

Conversation

@metanovii

Copy link
Copy Markdown

hi, I added the ability to set field names in the hashicorp vault key via environment variables CERTIFICATE_FIELD_NAME, PRIVATE_KEY_FIELD_NAME, ISSUER_CERTIFICATE_FIELD_NAME. This is necessary for the vault secrets operator.

Below is the log from the vault secrets operator to understand the context.

Name:         vault-static-secret-v3
Namespace:    nginx-ingress
API Version:  secrets.hashicorp.com/v1beta1
Kind:         VaultStaticSecret
Creation Timestamp:  2025-04-10T10:36:40Z
Spec:
  Destination:
    Create:          true
    Name:            static-secret2
    Overwrite:       false
    Type:            kubernetes.io/tls
  Hmac Secret Data:  true
  Mount:             kv
  Path:              azaza/infra/security/x.509/certificates/k8s-qa-test.azaza.space
  Refresh After:     60s
  Type:              kv-v2
  Vault Auth Ref:    vault-auth
  Version:           2
Events:
  Warning  Unrecoverable           Failed to get cacheKey from obj, err=ServiceAccount "vault" not found
  Warning  VaultClientConfigError  Failed to get Vault auth login: ServiceAccount "vault" not found
  Warning  SecretSyncError         Failed to update k8s secret: Secret "static-secret2" is invalid: [data[tls.crt]: Required value, data[tls.key]: Required value]

@metanovii

Copy link
Copy Markdown
Author

@rlebedys Can you check that?

@rlebedys

rlebedys commented Sep 8, 2025

Copy link
Copy Markdown
Contributor

@metanovii I am sorry, somehow I missed the notifications. Is this still relevant?

@metanovii

Copy link
Copy Markdown
Author

@rlebedys
Hi, no problem. Yes, it's still relevant.

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