Jeremy Cowan

@clintkitson is this being worked on?

@artazar I don't know if there is a good way to guarantee that the secret sidecar starts before other init containers. Ordinarily, init containers are started in the order in...

That's right. There is a fork of this project that supports multiple secrets.

See the aws-samples:multi-secret branch. There are no plans to merge it at the moment.

@bjethwan @adriantaut The cost of polling is pretty negligible ($0.05 per 10,000 API calls) and you can configure the polling interval or disable it all together. We are not supporting...

We can update the readme @dsaydon90 with instructions for creating a serviceAccount, IAM policy, etc, but I'm hesitant to include code to automatically creates an IAM role since that is...

@allamand When I say "re-write the application" I mean writing the application to re-read the secret from disk when an error occurs using the old secret. I think that's an...

Our current plan is to use a CRD/operator to patch the pods in a deployment that references a secret from AWS Secrets Manager when the secret is rotated. The CRD...

@anguslees We were purposely trying to avoid polling because a) there could be a long wait between polling intervals causing the app to break and b) excessive polling could get...

@amit0701 didn't you already update the code to inject secrets into init containers? From what I recall, you iterate through and patch all of the init containers if the length...