Tadayoshi Sato

> but camel-k-runtime doesn't have any reason to live without camel-k Yes, right, but my point is that if we release camel-k-runtime separately users could serve themselves for upgrading the...

cc @phantomjinx

Related issues: #213 #214 #3134 To reuse the existing e2e tests as-is, we are required to resolve those issues above first to make build work on Windows. Another approach might...

One idea might be just run workflows that don't require a Kind cluster, such as `build` and `local-it` for the time being.

Ah I see. Then maybe we can start small from only running `build` on Windows. The `build` runs unit tests so it should be still worth running on Windows.

Let's mark this as never-stale.

Hi, there is one more important step left to run your integration. It is: ``` kamel run Example.java ```

@michaeljmcd Ah ok, then if you chose `kamel install --global` method, run the following command in your namespace before creating an integration: ``` kamel install --skip-operator-setup -n $NS ```

What are the events when you see the related `k describe ik` and `k describe ikb`?

Hi, Sorry, my bad. When you installed operator with `kamel install --global` you shouldn't need to run the following. My previous instruction was wrong. ``` kamel install --skip-operator-setup -n $NS...