That is great! A question, is the standalone also built? We use it in the
miniops and we need that too...
Unless we can instead go with the standard controller with an appropriate
configuration.

Michele Sciabarra | CEO

m: +44 747 984 8388
e:  [email protected]
l:   https://linkedin.com/in/msciab
Nuvolaris Inc | 1209 Orange Street, 19801Wilmington DE - US
www.nuvolaris.io linkedin.com/in/msciab


On Fri, 1 May 2026 at 20:27, Francesco Timperi Tiberi <[email protected]>
wrote:

> Hi Michele,
>
> Briefly, the OpenWhisk 2 images I built are these:
>
> registry.hub.docker.com/apache/openserverless-wsk-controller
> registry.hub.docker.com/apache/openserverless-wsk-invoker
>
> both with the same tag: 2.0.0-incubating.2512132233
>
> Since these are OpenWhisk 2 images, they expect the scheduler to be
> present as well (which does exist with the same tag).
>
> However, the openserverless-operator does not deploy the scheduler.
>
> I created this PR on the operator project
> https://github.com/apache/openserverless-operator/pull/80, which shows
> how to use OpenWhisk 2 images in an OpenWhisk 1–style mode (let’s call it
> that), and also fixes a couple of bugs related to the controller and
> invoker image versions when they are specified in the wsk file.
>
> To reproduce the build, you need to use the project
> https://github.com/apache/openserverless-build, but:
>
> This PR must be accepted in the OpenWhisk project
> https://github.com/apache/openwhisk/pull/5565, which updates the version
> of the Zookeeper dependencies.
>
> Without it, OpenWhisk 2 images in controller+invoker mode are not working.
> Nobody has paid attention to it, but you should be able to approve it. I
> suspect that since everyone is using version 2 with the scheduler, the
> Zookeeper issue hasn’t surfaced.
>
> Once the PR in OpenWhisk is accepted, you just need to align the openwhisk
> submodule in the openserverless-build project. The GitHub Action that
> performs the build is triggered as usual by a tag.
>
> There is also a devcontainer and a Taskfile with the relevant commands to
> build the images locally.
>
> The current images I used were built and tested from my forks of the three
> projects. My user is authorized to push to Docker under Apache, which is
> why they are already there.
>
> On 2026/05/01 18:36:26 Michele Sciabarra wrote:
> > Hello everyone next step is to build from sources the Operator and the
> > OpenWhisk components. I remember Francesco worked on it, can you please
> > write your recommendations?
> >
> >
> > Michele Sciabarra | CEO
> >
> > m: +44 747 984 8388
> > e:  [email protected]
> > l:   https://linkedin.com/in/msciab
> > Nuvolaris Inc | 1209 Orange Street, 19801Wilmington DE - US
> > www.nuvolaris.io linkedin.com/in/msciab
> >
>

Reply via email to