You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.
Lastly, the purpose of this Poc is to demonstrate the type of integration that can be achieved between AWS Secrets Manager and Kubernetes. It is not meant to be used in production.
why is this sample not meant to be used in production?
@pbn4 This was really meant be to a reference implementation. The reason it is not for production use is because a) it is not directly supported by AWS b) it has not been tested at scale and c) there's no SLA for fixing bugs. Of course you can use it in production, but you would do so at your own risk. While we think the overall risk is minimal, we don't want to blamed for causing a production outage, e.g. if an application can't retrieve a secret for a system in the critical path. I hope that makes sense.
Hello,
why is this sample not meant to be used in production?
AWS Secrets Controller PoC: integrating AWS Secrets Manager with Kubernetes
The text was updated successfully, but these errors were encountered: