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
The following commit(s) were added to refs/heads/main by this push:
new e77172672 chore(doc): operator config clarification note
e77172672 is described below
commit e77172672b6ffdb9acab88801199a17bb2ceef36
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Tue Sep 15 09:16:57 2026 +0200
chore(doc): operator config clarification note
---
docs/modules/ROOT/pages/installation/installation.adoc | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/docs/modules/ROOT/pages/installation/installation.adoc
b/docs/modules/ROOT/pages/installation/installation.adoc
index 13dba2dd0..b0fd3cd56 100644
--- a/docs/modules/ROOT/pages/installation/installation.adoc
+++ b/docs/modules/ROOT/pages/installation/installation.adoc
@@ -9,11 +9,16 @@ Camel K allows us to run Camel integrations directly on a
Kubernetes cluster. To
You will need a container registry available in order to push and pull the
generated Camel applications. The easiest way to configure it is to store the
configuration on a Configmap which will be used by the operator:
```
-kubectl create configmap camel-k-operator-configmap-configuration \
+$ kubectl create ns camel-k
+
+$ kubectl create configmap camel-k-operator-configmap-configuration \
--from-literal=REGISTRY_ADDRESS="docker.io" \
--from-literal=REGISTRY_SECRET="my-docker-secret"
+ -n camel-k
```
+NOTE: the configuration needs to be available in the namespace where the
operator will run.
+
Have a further look at the xref:installation/registry.adoc[production ready
registry configuration documentation].
You can now install and run the Camel K operator. You can do it via any of the
following methodologies:
@@ -25,7 +30,6 @@ https://kustomize.io[Kustomize] provides a declarative
approach to the configura
[subs=attributes+]
----
-$ kubectl create ns camel-k
$ kubectl apply -k
github.com/apache/camel-k/install/overlays/all-namespaces?ref=v{last-released-version}
--server-side
----
