vouch / helm-charts

Vouch Helm Charts

Usage

Helm must be installed to use the charts. Please refer to Helm's documentation to get started.

Once Helm is set up properly, add the repo as follows:

helm repo add vouch https://vouch.github.io/helm-charts/

You can then run helm search repo vouch to see the charts.

Chart documentation is available in helm-charts directory.

Contributing

We'd love to have you contribute! Please refer to our contribution guidelines for details.

License

Chart documentation is available in helm-charts licencse.

helm-charts's Issues

README is missing

https://artifacthub.io/packages/helm/vouch/vouch

I used helm-docs to generate the readme, which is why there's a gotmpl, github actions needs to be updated to do the same thing, or replace the tmpl with a real readme (maybe make generating the readme a manual step?)

Add ability to use secrets

Hi there, thanks so much for providing this Helm chart!

I have a feature request: it would be awesome if there was some way to pass SealedSecrets to the Vouch helm chart, so that I can take mine out of plain text. Specifically,

• config.vouch.jwt.secret - https://github.com/halkeye-helm-charts/vouch/blob/master/values.yaml#L59
• config.oauth.client_id & .client_secret - https://github.com/halkeye-helm-charts/vouch/blob/master/values.yaml#L66:L67

e.g. how the MongoDB Replica Set Helm Chart implements auth.existingKeySecret, auth.existingMetricsSecret, and auth.existingAdminSecret.

I could maybe take a stab at a PR in a couple of weeks, if you're open to that.

Cheers!

Update plan for the helm charts with respect to the app version changes

Appreciate you offering your time to enable this helm chart. Currently I see the app version is lacking behind. How are you planning on keeping up with the app changes here? Are you open for PR's or can you quickly update this to support the latest versions?

Helm repo publication does not work

A merge should trigger publishing the chart to the gh-pages branch but it does not appear to work.

extraEnvVars valueFrom

Right now the deployments.yaml file process the extraEnvVars like this:

            {{- range .Values.extraEnvVars }}
            - name: {{ .name }}
              value: {{ .value | quote }}
            {{- end }}

So it only contemplates a hardcoded value.
I would like to load the values from a secret like this:

    extraEnvVars:
      - name: OAUTH_CLIENT_ID
        valueFrom:
          secretKeyRef:
            name: vouch-okta
            key: OAUTH_CLIENT_ID
      - name: OAUTH_CLIENT_SECRET
        valueFrom:
          secretKeyRef:
            name: vouch-okta
            key: OAUTH_CLIENT_SECRET

However if I do this the deployment ends like this

        - name: OAUTH_CLIENT_ID
        - name: OAUTH_CLIENT_SECRET

With no values, because there is no .value in the structure.

So maybe in the deployment.yaml code the env vars should be handled as (indent 12 referencial only I haven't really counted):

            {{- if .Values.extraEnvVars }}
            {{- toYaml .Values.extraEnvVars | indent 12 }}
            {{- end }}

handling it that way allows the user setting the env vars in any way they need.

Updating from version 0.3.1 to version 1.0.0 fails with conflict error

Updating from version 0.3.1 to version 1.0.0 of the helm chart gives me the following error.

Unable to continue with update: existing resource conflict: namespace: default, name: default-vouch, existing_kind: networking.k8s.io/v1beta1, Kind=Ingress, new_kind: networking.k8s.io/v1beta1, Kind=Ingress

I am happy to provide more information or help fix this if I can.

Enabling ingress seems to generate a YAML parse error

When running the following:
helm install vouch vouch/vouch --version 3.0.0 --set config.vouch.jwt.secret='foo' --set ingress.enabled=true
I am seeing the following error:
Error: YAML parse error on vouch/templates/ingress.yaml: error converting YAML to JSON: yaml: line 18: mapping values are not allowed in this context

Vouch not running via Helm

When running Vouch-Proxy (version 0.19.2 and 0.23.1 tested) using Helm Charts, I'm getting the following exception:

{"level":"fatal","ts":1618323472.0185509,"msg":"envconfig.Process: assigning VOUCH_PORT to Port: converting 'tcp://10.xx.xx.xx:9090' to type int. details: strconv.ParseInt: parsing \"tcp://10.xx.xx.xx:9090\": invalid syntax"}

Missing JWT token

I'm trying to upgrade from version 1.0.0 and it's giving me an error. I think all it needs is a random string to be the secret but for unenlightened like me, this takes some googling to figure out that would be great to include in some docs :)

maintainers

I'd like to help maintain this chart, as right now it seems you're a little short on hands and I have some time to donate. Please let me know if you'd like help keeping this chart up to date and processing pull requests. Right now the time to response is around a month or two, and I'd love to help you get that to a week or under.

replicaCount parameter issue

Hi,
I'm using this helm chart to deploy vouch on a Kubernetes cluster.

Everything works with the authentication backend system that I'm using, and I'm able to authenticate stuff. If I try to scale up the deployment to have high availability service, doesn't work anymore, and I'm not able anymore to log in into my application.

Is this a known design implementation, or it should work in every case?