Skip to content

Commit 8a8a719

Browse files
committed
Clarify the explanation a bit
1 parent 60f62a7 commit 8a8a719

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

content/blog/2024-08-30-push-secrets.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,21 @@ secrets across a distributed environment.
2727
## How It Works
2828

2929
To illustrate how this feature works, let’s walk through a simple example where
30-
we push a secret using a PushSecret resource.
30+
we push an existing kubernetes secret called `existing-secret` into the Vault
31+
using a PushSecret resource. The existing secret could be the following:
32+
```yaml
33+
apiVersion: v1
34+
kind: Secret
35+
metadata:
36+
name: existing-secret
37+
namespace: hello-world
38+
data:
39+
bar: YmFyCg== # The secret field we are interested in pushing into the vault
40+
foo: ....
41+
```
3142
43+
And here is the `PushSecret` resource that will fetch the `bar` key from the existing
44+
secret above and push it into the vault.
3245
```yaml
3346
apiVersion: external-secrets.io/v1alpha1
3447
kind: PushSecret
@@ -42,7 +55,7 @@ spec:
4255
remoteRef:
4356
remoteKey: pushsecrets/testme # the remote vault path
4457
property: baz # the key in the path defined above inside the vault
45-
secretKey: bar # The property of the local secret that will be pushed to `baz` in the vault
58+
secretKey: bar # The property of the local `existing-secret` secret that will be pushed to `pushsecrets/testme/baz` in the vault
4659
deletionPolicy: Delete
4760
refreshInterval: 10s
4861
secretStoreRefs:

0 commit comments

Comments
 (0)