1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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/).
답변함 일 년 전
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.
관련 콘텐츠
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 9달 전
- AWS 공식업데이트됨 2년 전
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/