This is an automated email from the ASF dual-hosted git repository. squakez pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 6f7fe65aff597966fa5ccf3702a7414d4c91c3ba Author: harshilv17 <[email protected]> AuthorDate: Mon Sep 21 20:38:26 2026 +0530 docs(trait): stop documenting a kit the operator no longer creates --- docs/modules/ROOT/partials/apis/camel-k-crds.adoc | 4 +-- docs/modules/traits/pages/container.adoc | 4 +-- helm/camel-k/crds/camel-k-crds.yaml | 32 +++++++++++----------- pkg/apis/camel/v1/trait/container.go | 4 +-- .../camel.apache.org_integrationplatforms.yaml | 8 +++--- .../camel.apache.org_integrationprofiles.yaml | 8 +++--- .../crd/bases/camel.apache.org_integrations.yaml | 8 +++--- .../config/crd/bases/camel.apache.org_pipes.yaml | 8 +++--- 8 files changed, 38 insertions(+), 38 deletions(-) diff --git a/docs/modules/ROOT/partials/apis/camel-k-crds.adoc b/docs/modules/ROOT/partials/apis/camel-k-crds.adoc index 087e47370..a53be7ad1 100644 --- a/docs/modules/ROOT/partials/apis/camel-k-crds.adoc +++ b/docs/modules/ROOT/partials/apis/camel-k-crds.adoc @@ -6977,8 +6977,8 @@ string | -The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which -won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead +The main container image to use for the Integration. When using this parameter, any trait requiring a +CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. |`imagePullPolicy` + diff --git a/docs/modules/traits/pages/container.adoc b/docs/modules/traits/pages/container.adoc index 4e9f910b0..e632f27ea 100755 --- a/docs/modules/traits/pages/container.adoc +++ b/docs/modules/traits/pages/container.adoc @@ -85,8 +85,8 @@ It defaults to `http` only when the `expose` parameter is true. | container.image | string -| The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which -won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead +| The main container image to use for the Integration. When using this parameter, any trait requiring a +CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. | container.imagePullPolicy diff --git a/helm/camel-k/crds/camel-k-crds.yaml b/helm/camel-k/crds/camel-k-crds.yaml index 8b9adc18a..72eff8bd7 100644 --- a/helm/camel-k/crds/camel-k-crds.yaml +++ b/helm/camel-k/crds/camel-k-crds.yaml @@ -4102,8 +4102,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -6673,8 +6673,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -9205,8 +9205,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -11725,8 +11725,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -21307,8 +21307,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -23715,8 +23715,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -34660,8 +34660,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -36990,8 +36990,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: diff --git a/pkg/apis/camel/v1/trait/container.go b/pkg/apis/camel/v1/trait/container.go index 3fd117213..9ac0ec41b 100644 --- a/pkg/apis/camel/v1/trait/container.go +++ b/pkg/apis/camel/v1/trait/container.go @@ -57,8 +57,8 @@ type ContainerTrait struct { ServicePortName string `json:"servicePortName,omitempty" property:"service-port-name"` // The main container name. It's named `integration` by default. Name string `json:"name,omitempty" property:"name"` - // The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - // won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + // The main container image to use for the Integration. When using this parameter, any trait requiring a + // CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead // Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. Image string `json:"image,omitempty" property:"image"` // The pull policy: Always|Never|IfNotPresent diff --git a/pkg/resources/config/crd/bases/camel.apache.org_integrationplatforms.yaml b/pkg/resources/config/crd/bases/camel.apache.org_integrationplatforms.yaml index edbbc905b..3b318a775 100644 --- a/pkg/resources/config/crd/bases/camel.apache.org_integrationplatforms.yaml +++ b/pkg/resources/config/crd/bases/camel.apache.org_integrationplatforms.yaml @@ -794,8 +794,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -3365,8 +3365,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: diff --git a/pkg/resources/config/crd/bases/camel.apache.org_integrationprofiles.yaml b/pkg/resources/config/crd/bases/camel.apache.org_integrationprofiles.yaml index d5ae4f001..66a0aa2a2 100644 --- a/pkg/resources/config/crd/bases/camel.apache.org_integrationprofiles.yaml +++ b/pkg/resources/config/crd/bases/camel.apache.org_integrationprofiles.yaml @@ -719,8 +719,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -3239,8 +3239,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: diff --git a/pkg/resources/config/crd/bases/camel.apache.org_integrations.yaml b/pkg/resources/config/crd/bases/camel.apache.org_integrations.yaml index 355240ae0..5154f6f11 100644 --- a/pkg/resources/config/crd/bases/camel.apache.org_integrations.yaml +++ b/pkg/resources/config/crd/bases/camel.apache.org_integrations.yaml @@ -7772,8 +7772,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -10180,8 +10180,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: diff --git a/pkg/resources/config/crd/bases/camel.apache.org_pipes.yaml b/pkg/resources/config/crd/bases/camel.apache.org_pipes.yaml index c7584b72c..93c1730a2 100644 --- a/pkg/resources/config/crd/bases/camel.apache.org_pipes.yaml +++ b/pkg/resources/config/crd/bases/camel.apache.org_pipes.yaml @@ -7827,8 +7827,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy: @@ -10157,8 +10157,8 @@ spec: type: boolean image: description: |- - The main container image to use for the Integration. When using this parameter the operator will create an IntegrationKit which - won't be able to execute traits requiring CamelCatalog. If the container image you're using is coming from an IntegrationKit, use instead + The main container image to use for the Integration. When using this parameter, any trait requiring a + CamelCatalog won't be able to execute. If the container image you're using is coming from an IntegrationKit, use instead Integration `.spec.integrationKit` parameter. If you're moving the Integration across environments, you will also need to create an "external" IntegrationKit. type: string imagePullPolicy:
