ugns / boundary-chart Goto Github PK

Using EKS, the version of k8s is 23+ so this fails when trying to download bitnami/kubectl:1.23+ image

Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.7-eks-4721010", GitCommit:"b77d9473a02fbfa834afa67d677fd12d690b195f", GitTreeState:"clean", BuildDate:"2022-06-27T22:19:07Z", GoVersion:"go1.17.10", Compiler:"gc", Platform:"linux/amd64"}

I'm looking to try boundary and found your chart. Do you intend to apply an oss license to this and are you open to contributions? (I know you just committed this recently, and I don't want to assume its available for use)

cheers!

Hashicorp released 0.9.0 so need to update the chart and test upgrade functionality.

Currently, setup to handle AEAD, Vault Transit, and AWS KMS keys only.

Add support for the additional KMS keys supported by Boundary

• AliCloud
• GCP
• Azure
• OCI

seems that in the README and the docs you mention this block of settings but templates does not include an ingress template

Currently setting up main branch as a submodule in ugns/helm-charts repo to publish. This was meant as a stop-gap until release workflow could be worked out on this repo.

Ideally should handle triggering new version release when pushed to main branch from develop.
Maintain signed chart release pushed to ugns/helm-charts.

I am trying the helm chart you provided in EKS and it hangs at the boundary-init job. any idea why would that would be?
job Logs:
Error creating: pods “boundary-init-” is forbidden: error looking up service account boundary/boundary: serviceaccount “boundary” not found.
EKS Version: 1.26