-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Labels
bugSomething isn't working or it has wrong behavior on a Mojaloop Core serviceSomething isn't working or it has wrong behavior on a Mojaloop Core servicecore-dev-squadoss-ttkRelated to the Mojaloop testing toolkitRelated to the Mojaloop testing toolkittest-bugThis is a bug in tests or test automation framework, not a code or functionality issueThis is a bug in tests or test automation framework, not a code or functionality issue
Description
Summary:
When I specify TLS configuration in helm values file while trying to install TTK helm chart, I am getting the following error.
Error: YAML parse error on mojaloop-payment-manager/charts/ttk/charts/ml-testing-toolkit-backend/templates/ingress.yaml: error converting YAML to JSON: yaml: line 38: did not find expected key
This issue is happening for both TTK backend and frontend.
Observations:
This can be fixed by changing the following line in the ingress.yaml file of both frontend and backend.
tls:
{{ toYaml .Values.ingress.tls | indent 4 }}
to
tls:
{{ toYaml .Values.ingress.tls | nindent 4 }}
Severity:
High
Expected Behavior
TTK should be deployed even if we specify ingress.tls config parameter in the values file.
Steps to Reproduce
- Provide the following config in the values file
ml-testing-toolkit-backend:
ingress:
tls:
- secretName: chart-example-tls
hosts:
- chart-example.local
- Try in deploy TTK helm chart using the values file
Specifications
- Component (if known): TTK Helm chart
- Version: v15.0.0
- Bug found/raised by: @vijayg10
Pull Requests
- fix: some changes in tls ingress config helm#498 (This is WIP PR contains some fixes, not sure if this works. Need to test)
Metadata
Metadata
Assignees
Labels
bugSomething isn't working or it has wrong behavior on a Mojaloop Core serviceSomething isn't working or it has wrong behavior on a Mojaloop Core servicecore-dev-squadoss-ttkRelated to the Mojaloop testing toolkitRelated to the Mojaloop testing toolkittest-bugThis is a bug in tests or test automation framework, not a code or functionality issueThis is a bug in tests or test automation framework, not a code or functionality issue