Skip to content

Commit

Permalink
Update eso.mdx
Browse files Browse the repository at this point in the history 
Make it clear that the integration first copies the `ExternalSecret` to the host cluster where the External Secrets Operator with generate the Kubernetes `Secret`
  • Loading branch information
@kmadel @deniseschannon
kmadel authored and deniseschannon committed Oct 6, 2024
1 parent 35ccf78 commit e0727c9
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions vcluster/_fragments/eso.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -76,8 +76,8 @@ spec:
version: v1beta1
```

Once that external secret is created in the virtual cluster, the integration will take care or creating a corresponding secret inside the host cluster,
the external secret operator running in the host will take care of creating the corresponding kubernetes secret, and the integration will import this
secret in the virtual cluster. Running `kubectl get secrets` in the virtual cluster should now include the `secret-to-be-created` in its output.
Once that external secret is created in the virtual cluster, the integration will take care or creating a corresponding external secret inside the host cluster,
the external secret operator running in the host will take care of creating the corresponding Kubernetes secret, and the integration will import this
Kubernetes secret into the virtual cluster. Running `kubectl get secrets` in the virtual cluster should now include the `secret-to-be-created` in its output.


0 comments on commit e0727c9

Please sign in to comment.