You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by "Peperud (via GitHub)" <gi...@apache.org> on 2024/07/23 05:34:00 UTC

[I] How to set a custom certificate for the helm install? [openwhisk]

Peperud opened a new issue, #5499:
URL: https://github.com/apache/openwhisk/issues/5499

   There is this:
   ```yaml
   whisk:
     # Ingress defines how to access OpenWhisk from outside the Kubernetes cluster.
     # Only a subset of the values are actually used on any specific type of cluster.
     # See the "Configuring OpenWhisk section" of the docs/k8s-*.md that matches
     # your cluster type for details on what values to provide and how to get them.
     ingress:
       awsSSL: "false"
       apiHostName: ""
       apiHostPort: 31001
       apiHostProto: "https"
       type: NodePort
       annotations:
         nginx.ingress.kubernetes.io/proxy-body-size: "50m"
       domain: "domain"
       tls:
         enabled: false
         secretenabled: false
         createsecret: false
         secretname: "ow-ingress-tls-secret"
         secrettype: "type"
         crt: "crt"
         key: "key"
   ```
   I have generated my own certificate. 
   But no matter what I set ```crt``` ,```key``` and ```enabled``` to, I still end up with the dreaded ```*.localhost"```.
   
   
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org