You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/12/13 20:52:08 UTC

[GitHub] [pulsar] juliohm1978 opened a new issue #5858: Helm chart does not allow ingress TLS to be enabled without a secretName

juliohm1978 opened a new issue #5858: Helm chart does not allow ingress TLS to be enabled without a secretName
URL: https://github.com/apache/pulsar/issues/5858
 
 
   **Describe the bug**
   The provided helm chart can create an Ingress with TLS, but it requires a `secretName` to be added. This is not an Ingress requirement and, in some cases, the ingress controller can provide a default certificate when the Ingress object does not declare one.
   
   **To Reproduce**
   Deploy the helm chart with an Ingress enabled and an empty tls `secretName`.
   
   **Expected behavior**
   I expect to be able to configure the Ingress TLS without the need to give it a `secretName`. My Ingress controller will use a default certificate.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services