2021-01-11 08:46:35 UTC - Pavel Kravchenko: I'm trying to setup Openwhisk on Kubernetes multiple nodes with NFS persistent storage following the blog post below which can be outdated. The PVs and PVCs get created, but openwhisk pods fail to start. Fail to understand the reason why the pods fail to start hanging in CrashLoop. NFS export is available from all the K8S nodes.:
<https://gist.github.com/kpavel/307a760063edc12920f82de2bf54eb25> <https://blog.zhaw.ch/splab/2019/02/28/reliable-openwhisk-deployment-on-kubernetes-with-persistent-storage/> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610354795460000 ---- 2021-01-11 14:01:57 UTC - Rob Allen: Morning all. Should I aim to make the default runtime container as small as reasonably possible? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610373717461100 ---- 2021-01-11 14:02:04 UTC - Rob Allen: i.e. is there a tangible benefit to do so? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610373724461400 ---- 2021-01-11 14:04:14 UTC - Rob Allen: `action-php-v7.4` is `1.01GB` (as reported by `docker images`). `action-php-v8.0` started at 1.2GB, which seemed really big to me. I’ve been whittling it down and am at `478MB` now and am wondering if it’s worth putting in time to get it down more. +1 : Dominic Kim, Rodric Rabbah, Ben Carver https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610373854463500 ---- 2021-01-11 14:14:47 UTC - Dominic Kim: I believe so. In the k8s world if you don’t pull the runtime images on all nodes in advance, image pulling time would be included in the activation path for the first run. In case of blackbox action it would be worse. Keeping images as small as possible would alleviate this. +1 : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610374487466800 ---- 2021-01-11 14:37:35 UTC - Rob Allen: Useful to know. Thanks. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610375855467300 ---- 2021-01-11 15:58:55 UTC - Ben Carver: I am trying to use a fairly large (48MB) JAR file when creating an OpenWhisk action. I get an HTTP 413 (Payload Too Large) error in response. Is there any way I can increase this error? I've tried messing around with the Helm chart, specifically the NGINX and ingress sections (I've tried adding an annotation of the form `<http://nginx.org/client_max_body_size|nginx.org/client_max_body_size>: "100m"` but with no success). Is there any way I can increase this size limit? I was reading thru the docs and see that I could also use a Docker image instead. Could I package my JAR file directly into the image as an alternative? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610380735470700?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 16:16:50 UTC - Rodric Rabbah: hi Ben - 48MB is right at the limit likely it’s larger after base64 encoding https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610381810470900?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 16:17:01 UTC - Rodric Rabbah: you can increase the size but it’s not a single deployment configuration https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610381821471100?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 16:18:06 UTC - Rodric Rabbah: <https://github.com/apache/openwhisk/pull/3757> for reference - needs some TLC to be able to accept this https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610381886471300?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 16:23:25 UTC - Ben Carver: > hi Ben - 48MB is right at the limit likely it’s larger after base64 encoding Right, I figured as much. > you can increase the size but it’s not a single deployment configuration So the `limit_action_blob_size` hasn't been implemented yet? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610382205471500?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 17:53:46 UTC - Ben Carver: Or is there an actual `codeSize` parameter I can change, perhaps in the Helm chart? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610387626473100?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 17:59:20 UTC - Rodric Rabbah: There’s isn’t a single parameter at this time iirc https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610387960473700?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 18:12:24 UTC - Ben Carver: Is it just a matter of modifying various configuration parameters as listed in that Github issue, or do I also need to make changes to the code? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610388744473900?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 18:12:45 UTC - Rodric Rabbah: the ones in the issue i think are sufficient https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610388765474100?thread_ts=1610380735.470700&cid=C3TPCAQG1 ---- 2021-01-11 18:51:17 UTC - Ben Carver: Hmm. That includes modifying the code to remove the hard-coded limit though, doesn't it? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1610391077474300?thread_ts=1610380735.470700&cid=C3TPCAQG1 ----
