Hacker News Reader

I was reluctant to use Garnet as I always had a traditional approach with managing secrets. It wasn't until I accidentally deleted my sensitive and critical data that I started to look out for a better way of doing things. That's where Garnet came in. Very easy to install and getting started to use it's features. Definitely recommended for everyone before it's too late and you have to spend a couple of days trying to re-register your keys and stuff

View on HN

How does this work in production environments like k8s or aws?

I've been using Garnet with my k8s setup. They don't have native kube api integration and I suggest developing a controller. But right now you can use the CLI to append any commands or scripts in your docker containers to supply them env variables at build or run time.

E.g. in a Dockerfile … RUN garnet run --service-key=$GARNET_SERVICE_KEY -- npm start

If this container is running on k8s, you can supply $GARNET_SERVICE_KEY as a k8s secret mounted on the pod

Reply on news.ycombinator.com