You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by as...@apache.org on 2021/03/17 11:52:57 UTC
[camel-k] branch master updated: doc: added documentation about
deploying Camel K on k3s
This is an automated email from the ASF dual-hosted git repository.
astefanutti pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/master by this push:
new 2ac21c4 doc: added documentation about deploying Camel K on k3s
2ac21c4 is described below
commit 2ac21c46494cceb075c36b2c1df50c3347013c45
Author: Otavio Rodolfo Piske <op...@redhat.com>
AuthorDate: Wed Mar 17 10:59:57 2021 +0100
doc: added documentation about deploying Camel K on k3s
---
.../ROOT/pages/installation/installation.adoc | 1 +
docs/modules/ROOT/pages/installation/k3s.adoc | 4 ++
.../ROOT/pages/installation/registry/k3s.adoc | 52 ++++++++++++++++++++++
3 files changed, 57 insertions(+)
diff --git a/docs/modules/ROOT/pages/installation/installation.adoc b/docs/modules/ROOT/pages/installation/installation.adoc
index 4b22499..a2b5781 100644
--- a/docs/modules/ROOT/pages/installation/installation.adoc
+++ b/docs/modules/ROOT/pages/installation/installation.adoc
@@ -16,6 +16,7 @@ before installing it. Customized instructions are needed for the following clust
- xref:installation/gke.adoc[Google Kubernetes Engine (GKE)]
- xref:installation/openshift.adoc[OpenShift]
- xref:installation/iks.adoc[IBM Kubernetes Services (IKS)]
+- xref:installation/k3s.adoc[K3s]
Other cluster types (such as OpenShift clusters) should *not need* prior configuration.
diff --git a/docs/modules/ROOT/pages/installation/k3s.adoc b/docs/modules/ROOT/pages/installation/k3s.adoc
new file mode 100644
index 0000000..8d45d1a
--- /dev/null
+++ b/docs/modules/ROOT/pages/installation/k3s.adoc
@@ -0,0 +1,4 @@
+[[installation-on-k3s]]
+= Installing Camel K on K3s
+
+Because K3s does not come with a builtin registry, you should follow the steps described on xref:installation/registry/k3s.adoc[Installing Camel K on K3s] to deploy it configure it to use a public or a private registry.
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/installation/registry/k3s.adoc b/docs/modules/ROOT/pages/installation/registry/k3s.adoc
new file mode 100644
index 0000000..8b38aeb
--- /dev/null
+++ b/docs/modules/ROOT/pages/installation/registry/k3s.adoc
@@ -0,0 +1,52 @@
+[[installation-on-k3s]]
+= Installing Camel K on K3s
+
+This guide assumes you've already deployed a https://k3s.io[K3s] cluster and have installed and configured the kubectl command to manage the cluster.
+
+You can create a namespace to install Camel K on:
+
+```
+kubectl create namespace camel-k-test || true
+```
+
+Camel K needs a xref:installation/registry/registry.adoc[registry] to push the integrations it builds. For K3s you have to possibilities:
+
+* You can configure Camel K installation to use the Docker registry, Quay.io or a similar publicly available registry, or;
+* You can deploy your own private repository in the cluster or on your network.
+
+[[public-registry]]
+== Using a Public Registry
+
+Most of the those registries require authentication to push images. Therefore, we have to create a secret the namespace that will contain the credentials to access it. To do so, you can execute:
+
+*Note*: before running the command below, please make sure that you are logged in to the registry you are planning to use.
+
+```
+kubectl -n camel-k-test create secret generic my-registry-secret --from-file=$HOME/.docker/config.json
+```
+
+You can follow the steps described in the xref:installation/registry/registry.adoc[registry] documentation if you are deploying using a public registry, such as the https://hub.docker.com[DockerHub] or https://quay.io[Quay].
+
+
+[[private-registry]]
+== Using a Private Registry
+
+Although K3s does not come with a private registry, one can be installed by following the steps described in the https://rancher.com/docs/k3s/latest/en/installation/private-registry/[K3s' private registry] documentation.
+
+*Note*: installing your own registry gives you more flexibility to define how the registry should run, including the level of security required for it to run. More specifically, you can configure your registry to require or not credentials, to use HTTP instead of HTTPS, and so on. For the purpose of this guide and to present how Camel K can be installed on a seamless way, this guide demonstrates the installation using an insecure registry (unencrypted and without authentication).
+
+[[installation]]
+=== Installing Camel K on K3s with Private Registry
+
+With the secret created on the cluster, we can install Camel K and tell it to use those credentials when pushing the integrations.
+
+You can now download *kamel* CLI tool from https://github.com/apache/camel-k/releases[release page]
+and put it on your system path.
+
+After configure *kamel* CLI, you can execute the following command to install it on the namespace and configured to use your private registry:
+
+```
+kamel install -n camel-k-test --force --olm=false --registry address-of-the-registry --organization your-user-id-or-org --registry-insecure true
+```
+
+After doing that, you'll be ready to play with Camel K. Enjoy!
\ No newline at end of file