You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2021/12/07 08:04:50 UTC

[GitHub] [openwhisk-deploy-kube] hawtkey commented on issue #711: What is correct way to use self-signed certs in ow install?

hawtkey commented on issue #711:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/711#issuecomment-987666777


   I'm no k8s/Helm pro but FWIW: the Helm Nginx template `nginx-pod.yaml` does a volumeMount of a TLS-secret named `owdev-nginx` containing a generated base64-encoded self-signed certificate/key that nginx uses at `/etc/nginx/certs`. I generated the base64 versions of my own chained-cert/decoded-key using IE: `cat my-chained-cert.crt | base64 -w 0` and used the outputs to replace the generated cert/key in the `owdev-nginx` secret using IE: `kubectl edit secret owdev-nginx --namespace openwhisk` and the API works fine with no errors. here are [some other methods](https://stackoverflow.com/questions/45879498/how-can-i-update-a-secret-on-kubernetes-when-it-is-generated-from-a-file) for updating a secret.


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

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