1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
You could either use one approach or the other. We have a new EKS v2 workshop that goes into Sealed Secrets.
_----------
I saw this online which is a 3rd party blog, but have not tested it. It is not official though (https://www.arthurkoziel.com/sync-aws-secrets-manager-to-k8s-secrets/).
beantwortet vor einem Jahr
Thanks Roly for your reply. Actually what you suggested is implemented in my current setup. SSCSID creates the k8s secret in this way and that is easily readable. I want to know if we can have secret which will not contain the actual data in k8s secret - It should contain the the place holder for the data.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Is this article helping or is basically what you already tried? https://aws.amazon.com/blogs/containers/leverage-aws-secrets-stores-from-eks-fargate-with-external-secrets-operator/