I think it's a "normal" warning.
Consider that the global option will watch for those namespaces where you
eventually install an IntegrationPlatform, see:
--global Configure the operator to watch
all namespaces. No integration platform is created. You can run
integrations in a namespace by installing an integration platform: 'kamel
install --skip-operator-setup -n my-namespace'
Cheers,
Pasquale.
On Thu, Mar 17, 2022 at 5:21 AM Tadayoshi Sato <sato.tadayo...@gmail.com>
wrote:
> Hi,
>
> It's just a false alarm. You can ignore it for the global operator.
> I think kamel cli should be changed to also look for an operator globally,
> not only within its namespace.
>
> On Thu, Mar 17, 2022 at 5:05 AM Roberto Camelk <
> betonetotbo.cam...@gmail.com>
> wrote:
>
> > I recently installed the camel-k 1.8.2. During the process I passed
> > the arg --global to enable camel-k-operator to manage all namespaces.
> >
> > Now, when I query the integrations running in a specific namespace via
> > "kamel get -n my-namespace" I got this output:
> >
> > > No IntegrationPlatform resource in my-space namespace
> > > NAME PHASE KIT
> > > metrics Running default/kit-c8p3npidnv2c738t0erg
> >
> > The CLI is working as expected, listing my running integrations, but
> > this message "No IntegrationPlatform resource in my-space namespace".
> >
> > Do I need to worry about it? How can I fix it? What means it?
> >
>
>
> --
> Tadayoshi Sato
>
