HELM deployments do not work
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- helm, kubernetes, yaml
- Domain
- devops, infrastructure
Research direction
Start with deploy/helm/templates/chatbot/config.yaml and inspect the other individual templates for the same configuration pattern. Run the reported helm upgrade --install command with values.yaml; done means CrAPI deploys successfully when values such as apiGatewayServiceUrl and ports are changed.
Written by the indexing model from the issue text.
Description
Describe the bug
Deployments through helm templates do not work.
To Reproduce
Steps to reproduce the behavior.
Deploy CrAPI with Helm. The script that I used was:
- helm upgrade --install crapi ./deploy/helm --namespace $KUBE_NAMESPACE --create-namespace -f ./deploy/helm/values.yaml
Expected behavior
Deployments should work with usual changes in values.yml like: apiGatewayServiceUrl and ports.
Runtime Environment
Ubuntu 22.04, Docker 27.1.1
Reason
In the individual helm templates within /deploy/helm/templates; some of the attributes in the config.yaml of each template, some attributes are missing quotes. For instance:
deploy/helm/templates/chatbot/config.yaml
data:
DB_USER: {{ .Values.postgresdb.config.postgresUser }}
DB_PASSWORD: {{ .Values.postgresdb.config.postgresPassword }}
Here username and password are missing quotes. This should be:
data:
DB_USER: {{ .Values.postgresdb.config.postgresUser | quote}}
DB_PASSWORD: {{ .Values.postgresdb.config.postgresPassword | quote }}
I will create a pull request with working changes. Please let me know if this would be ok
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 645
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OWASP/crAPI
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 1/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
inu-appcenter/memorIN-backend#288 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
frontend maui-pilot pilot-ask question
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area/plugin
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kestra-io/plugin-kestra#190 ·