You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
reduce runtimes and set slim as the defalt for devcluster #141
First, ops setup devcluster should enable slim by default
Second, in current runtimes.json we have the old legacy openwhisk non multiplatform runtime. Just limit to python,node,php, the ones we support
also it is better to preload only the default runtimes (those with default in the runtimes.json)
Ⅱ. Describe what happened
Error when setup the slim inside an arm vm
Ⅲ. Describe what you expected to happen
should work
Ⅳ. How to reproduce it (as minimally and precisely as possible)
ops setup kubernetes create
in an arm vm
you get errors in runtime preloade
Regarding the first part: "ops setup devcluster should enable slim by default"
Actually ops setup devcluster presuppose that the user has already configured the system with ops config minimal (or, from the slim, ops config slim).
So, devcluster doesn't call automatically an ops config.
I think is better not to change this behaviour.
Regarding the second part: "is better to preload only the default runtimes"
I've changed the preload-runtime behaviour in the operator and changed the tasks accordly (see PR apache/openserverless-task#106)
Activity
chore: updated operator to 0.1.0-incubating.2506220931
chore: updated operator to 0.1.0-incubating.2506220931
d4rkstar commentedon Jun 22, 2025
Hello @sciabarracom.
Regarding the first part: "ops setup devcluster should enable slim by default"
Actually
ops setup devclusterpresuppose that the user has already configured the system withops config minimal(or, from the slim,ops config slim).So,
devclusterdoesn't call automatically anops config.I think is better not to change this behaviour.
Regarding the second part: "is better to preload only the default runtimes"
I've changed the preload-runtime behaviour in the operator and changed the tasks accordly (see PR apache/openserverless-task#106)
The new operator was tested with a k3s-arm vm.