helm-charts icon indicating copy to clipboard operation
helm-charts copied to clipboard

Helm packages for Kubernetes

Results 23 helm-charts issues
Sort by recently updated
recently updated
newest added

### Subject of the issue In templates/ca.yaml volumes spec, `{{ include "step-certificates.fullname" . }}-secrets` is always mounted as a secret or configmap and cause secret doesn't exists when using `inject.enabled=true`...

bug
needs triage

### Description This update to the helm template for step-certificates allows the optional creation of NetworkPolicy rules. For users who have a Default-Deny policy rule on their kubernetes cluster (as...

needs triage

### Description This is a feature preview of how backup/restore of Badger could be implemented. See also https://github.com/smallstep/helm-charts/issues/97

needs triage

Dear smallstep team, I was missing the functionality to set my custom CA certificate. Here is the proposal how it could be done. Looking forward to your comments.

### Subject of the issue I'm using Linked CA deployment. Recently, upgrade the helm chart version to the latest but since then getting this error on start and crashlooped. ```...

bug
needs triage

### What would you like to be added on ca.yaml line 88 , there is only HTTPS port configuration. Can you add an option to set another port or just...

enhancement
needs triage

Hello, ### What would you like to be added Set database dataSource as a kubernetes secret ### Why this is needed I'm trying to deploy StepCA helm chart via ArgoCD....

enhancement
needs triage

Hi guys, I want to add this step in the helm chart: "step ca provisioner add acme --type ACME". Is it simply adding at the field: postInitHook: "step ca provisioner...

After installing the chart on minishift . I've got "error opening /home/step/config/ca.json: open /home/step/config/ca.json: no such file or directory" and the pods are not able run ![image](https://user-images.githubusercontent.com/40110880/103445990-2b8cb300-4c83-11eb-9913-307cc62bd154.png) ![image](https://user-images.githubusercontent.com/40110880/103445995-3f381980-4c83-11eb-84e6-30748f5fa6c5.png) ![image](https://user-images.githubusercontent.com/40110880/103446006-58d96100-4c83-11eb-8ff0-4f9becbcd667.png)

Because private root keys must be "securely" stored, it is most convenient to store them inside a `secret` instead of a simple `configmaps`. Futhermore, this allows us to use some...