Looking to deploy this onto Kubernetes inside of AWS, have been excited to test this for a good minute, will there be a helm chart available?
Should I wait for the Official Helm Chart? Or should I go-ahead and roll my own?
Amazing work by the way.
2 Likes
Hi @Bioblaze - Kubernetes is on our road map. We encourage you to experiment here however since we don’t have a steadfast timeline for delivery just yet. Thanks for reaching out and trying Boundary! Please let us know if there are any other questions you have around the product and road map.
Hi @malnick - this question is now almost 1 year old, and I have to ask - is there a Helm Chart for Boundary coming anywhere soon?
2 Likes
I couldn’t find any. So I’ve created my own. Only confusing thing is that the worker need a public ip address, which we’ll get only after the first helm installation. So we’ve to update the worker ip, and redeploy again to get a working boundary installation.
Hey @curiouspanda, super nice you created a Helm chart! It would be fantastic if you could share the Helm chart with us 
Only confusing thing is that the worker need a public ip address, which we’ll get only after the first helm installation. So we’ve to update the worker ip, and redeploy again to get a working boundary installation.
It might be possible to work around this by using/creating a predetermined DNS name in the Boundary worker config (using public_addr), then registering the worker IP under that name after it’s known.
Another community initiative just popped up in Dec.
Can you put DNS names in this configuration value? The docs did not make this clear.
Yep, you should be able to.
I’ve been working on a Helm chart deployment as well myself. Still pretty early and have not yet pushed a release out to any repository yet other than the GitHub repo I’m working out of. While I’m targeting my environment to deploy, I am attempting to add as many capabilities as possible that others should easily use. Started with AEAD and Vault Transit KMS initially, I’ve added means to configure AWS KMS that I do intend to use but haven’t tested yet.
1 Like
Thanks for putting this helm chart together. I have been testing it in EKS for a while but still not able to get the workers to work as intended as by default it registers with localhost. Any help how to get the public ip or even ingress setup for workers would be great!