charts
charts copied to clipboard
Feature: opportunity to set TLS easily by default with ca-certs autogeneration if needed
This PR partly solves issue(#69). It addes opportunity to easily set TLS settings using values.yaml file by default.
@YarikRevich Thank you for the PR. Is this in a state where we can test this out?
@YarikRevich are you still working on this?
Yes, I'm still working on this.
@vishnu-narayanan Please, test my PR out
@YarikRevich Could you please share instructions on how I can test this out?
@vishnu-narayanan Sure, test is devidid into two parts. Before all use should set "ingress.enabled" to "true" in values.yaml. 1.(Test TLS with own certificates) Uncomment rows from 76 to 81 and then put to "ingress.tls[0].key" your own key and to "ingress.tls[0].crt" your own crt. Then run "helm install . --timeout 30m" being in charts directory. Afterwards, you'll be able to access resource with "https://chart-example.local/" 2.(Test TLS with certificate autogeneration) Uncomment rows from 76 to 81 and then delete "ingress.tls[0].key" and "ingress.tls[0].crt" items. If though one of them is not present, autogeneration will be used. Afterwards, you'll be able to access resource with "https://chart-example.local/" and you can check, that TLS certificate is generated by Kubernetes certificate generator
@YarikRevich I am not able to test this.
- Are you expecting an
ingress-controller
to be present? - At which point is the user expected to point DNS?
@vishnu-narayanan User should specify DNS name via values.yaml
https://github.com/chatwoot/charts/blob/b5328fbe03ba6f9010def98a22789c0cd7a09d5d/charts/chatwoot/values.yaml#L63-L81
@vishnu-narayanan can we look into the next steps for this PR ?
@YarikRevich Sorry for the delay here. This got left behind due to other priorites. Will pick this up once the team has enough bandwidth.