kubernetes/argocd
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update format

Browse Source
This commit is contained in:
Melvin
2026-01-22 22:15:16 +01:00
parent f04abdcf62
commit acf740ff46
2 changed files with 16 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
helm/cert-manager-webhook-ovh/ops/README.md
View File

@@ -93,12 +93,18 @@ EOF
Stockez les credentials OVH dans Vault :
```bash
# Pour Vault KV v2, utilisez cette commande :
vault kv put secret/ovh \
application-key="VOTRE_APPLICATION_KEY" \
application-secret="VOTRE_APPLICATION_SECRET" \
consumer-key="VOTRE_CONSUMER_KEY"
# Vérifiez que le secret est bien stocké :
vault kv get secret/ovh
```
**Important** : Le format du chemin dans `remoteRef` pour External Secrets est `ovh#application-key` (sans le préfixe `secret/data/`), car le mount path `secret` est déjà défini dans le ClusterSecretStore.
#### Configuration dans values.yaml
Activez External Secrets dans `values.yaml` :
@@ -109,9 +115,9 @@ externalSecret:
refreshInterval: "1h"
secretName: "cert-manager-webhook-ovh"
remoteRef:
applicationKey: "secret/data/ovh#application-key"
applicationSecret: "secret/data/ovh#application-secret"
consumerKey: "secret/data/ovh#consumer-key"
applicationKey: "ovh#application-key"
applicationSecret: "ovh#application-secret"
consumerKey: "ovh#consumer-key"
vault:
secretStoreName: "vault-backend"
server: "https://vault.example.com:8200"