2020-05-01 17:04:06 UTC - Bilal: Hey everyone, getting 413 error, entity too large? Anywhere I can change this? My Zipped action is only 4mb https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588352646198100 ---- 2020-05-01 17:08:51 UTC - Rodric Rabbah: The default is 48mb https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588352931198500 ---- 2020-05-01 17:09:02 UTC - Rodric Rabbah: Are you getting in action create? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588352942198900 ---- 2020-05-01 17:09:38 UTC - Bilal: ```wsk action create omni_qa --kind python:3 ovqa_actions.zip -i -v``` Yup in action create, I am on a on-prem Kube deployment https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588352978199300 ---- 2020-05-01 17:09:50 UTC - Bilal: ```error: Unable to create action 'omni_qa': The connection failed, or timed out. (HTTP status code 413)``` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588352990199500 ---- 2020-05-01 17:10:06 UTC - Bilal: ```$ ls -sh ovqa_actions.zip 4.0M ovqa_actions.zip``` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588353006199700 ---- 2020-05-01 17:14:12 UTC - Rodric Rabbah: Checked the controller logs? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588353252200300 ---- 2020-05-01 17:14:28 UTC - Rodric Rabbah: There should be code in your error response. Grep for it. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588353268200800?thread_ts=1588353268.200800&cid=C3TPCAQG1 ---- 2020-05-01 17:14:48 UTC - Bilal: will do https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588353288201000 ---- 2020-05-01 17:15:03 UTC - Bilal: I should note that I am also using the elastic-search change done a while back https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588353303201500 ---- 2020-05-01 17:39:57 UTC - Bilal: Yup, I'm having elastic search errors which are causing other errors I believe https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588354797201900?thread_ts=1588354797.201900&cid=C3TPCAQG1 ---- 2020-05-01 17:41:48 UTC - Rodric Rabbah: Seems like an issue with that https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588354908202500?thread_ts=1588354797.201900&cid=C3TPCAQG1 ---- 2020-05-01 17:42:13 UTC - Bilal: Yea, my elastic search containers are having errors as well https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588354933202700?thread_ts=1588354797.201900&cid=C3TPCAQG1 ---- 2020-05-01 17:42:23 UTC - Bilal: Time to sort that out :sweat_smile: https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588354943202900?thread_ts=1588354797.201900&cid=C3TPCAQG1 ---- 2020-05-01 20:48:12 UTC - Bilal: Only error code I get is 413, but I can't find it in the controller logs https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588366092203100?thread_ts=1588353268.200800&cid=C3TPCAQG1 ---- 2020-05-01 22:03:48 UTC - Bilal: ```Custom runtime images must be available on Docker Hub. Docker Hub is the only container registry currently supported. This means all custom runtime images will need to be publicly available.``` Is this still strictly true? Or can I use an internal/private docker repo https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588370628203600?thread_ts=1588370628.203600&cid=C3TPCAQG1 ---- 2020-05-01 22:04:46 UTC - Bilal: <https://github.com/apache/openwhisk/pull/4791> Looks this merged https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588370686203800 ---- 2020-05-01 22:05:55 UTC - Bilal: <https://github.com/apache/openwhisk-deploy-kube/issues/528> Still open, so I'm guessing the answer is no https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588370755204100 ---- 2020-05-01 22:20:05 UTC - Bilal: @Jiang PengCheng Any tips on first glance here? These are controller logs getting socket timeouts when putting to elasticsearch https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588371605204200?thread_ts=1588354797.201900&cid=C3TPCAQG1 ---- 2020-05-01 22:27:11 UTC - Brendan Doyle: we use custom runtimes off a private repo so you should be able to although we're not using the kubernetes container factory https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588372031204400?thread_ts=1588370628.203600&cid=C3TPCAQG1 ---- 2020-05-01 22:30:08 UTC - Bilal: Are you using the Docker container factory? <https://github.com/apache/openwhisk-deploy-kube/blob/master/docs/configurationChoices.md#invoker-container-factory> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588372208204600?thread_ts=1588370628.203600&cid=C3TPCAQG1 ---- 2020-05-01 22:37:49 UTC - Rodric Rabbah: @Dave Grove ^^ https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588372669205200 ---- 2020-05-01 22:48:13 UTC - Dave Grove: I suspect the pieces are in place. You should be able to use the ability to customize the pod template to inject image pull secrets. but it would be a per-cluster thing, not a per action or per namespace. its certainly not documented what would would need to do, but if you know how to get a Kubernetes pod running on your cluster (ignoring openwhisk) to pull an image from a private repo, you should be able to add the same `imagePullSecret` to the pods created by the KubernetesContainerFactory to run user actions https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588373293208500 ----
