<#3894 [Housekeeping] TLS options for ingress on H...
# flyte-github
a
#3894 [Housekeeping] TLS options for ingress on Helm Charts Issue created by EternalDeiwos Describe the issue Currently neither of the two Helm charts support adding TLS options to the ingress resources generated. This means those ingresses cannot serve traffic over TLS which is problematic for various reasons. The current workaround for this is to set
Values.ingress.create
to
false
and create the ingresses manually. Ideally we could have an option like:
Copy code
ingress:
  tls:
    enable: true

    # ... other options?
What if we do not do this? Maintenance becomes more painful if the endpoints are ever expanded or changed; they would need to be updated manually as opposed to just relying on the Helm chart to do it for you. Related component(s) Helm:
flyte-core
,
flyte-binary
Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte