[GitHub] [openwhisk-deploy-kube] s294547 commented on issue #712: Cron triggers not firing; EPROTO error in alarmprovider pod

["s294547 (via GitHub)" <gi...@apache.org>]

s294547 commented on issue #712:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/712#issuecomment-1531505696

   I have recently faced the problem and solved it. In my case, the problem was that in *utils.js* in the *provider* folder the uri of the apiHost is created in this way: *this.uriHost ='https://' + this.routerHost;*.
   I have deployed openwhisk using [this helm chart](https://github.com/apache/openwhisk-deploy-kube/tree/master/helm/openwhisk), and if you look at the yaml of the alarm provider deployment ([here](https://github.com/apache/openwhisk-deploy-kube/blob/master/helm/openwhisk/templates/provider-alarm-pod.yaml)) the *ROUTER_HOST* and *ENDPOINT_AUTH* environment variables are using the INTERNAL api host name and port. 
   This is a problem, since the internal port is 80 and does not provide any security option, but we are using https in the uri. 
   The code should be patched in order to check if the provided port is a secure one, if it is not the used protocol should be http.


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