You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Roberto Camelk <be...@gmail.com> on 2022/03/16 20:05:34 UTC
kamel install --global vs kamel get -n
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?
Re: kamel install --global vs kamel get -n
Posted by Pasquale Congiusti <pa...@gmail.com>.
We have some documentation explaining that:
https://camel.apache.org/camel-k/next/architecture/cr/integration-platform.html
Also, the API describes its purpose:
https://camel.apache.org/camel-k/next/apis/camel-k.html#_camel_apache_org_v1_IntegrationPlatform
With the IntegrationPlatform you're marking those namespaces where you want
the operator to execute your Camel K integrations. We recently included the
possibility to have 2 operators watching for the same namespace, just for
the sake of knowledge, this is the documentation related to that feature:
https://camel.apache.org/camel-k/next/installation/advanced/multi.html
On Thu, Mar 17, 2022 at 12:46 PM Roberto Camelk <
betonetotbo.camelk@gmail.com> wrote:
> What is the purpose of the PlatformIntegration? Why do I eventually
> need to install it?
>
> On Thu, Mar 17, 2022 at 5:37 AM Pasquale Congiusti
> <pa...@gmail.com> wrote:
> >
> > 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.tadayoshi@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.camelk@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
> > >
>
Re: kamel install --global vs kamel get -n
Posted by Roberto Camelk <be...@gmail.com>.
What is the purpose of the PlatformIntegration? Why do I eventually
need to install it?
On Thu, Mar 17, 2022 at 5:37 AM Pasquale Congiusti
<pa...@gmail.com> wrote:
>
> 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 <sa...@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.camelk@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
> >
Re: kamel install --global vs kamel get -n
Posted by Pasquale Congiusti <pa...@gmail.com>.
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 <sa...@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.camelk@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
>
Re: kamel install --global vs kamel get -n
Posted by Tadayoshi Sato <sa...@gmail.com>.
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 <be...@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