You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2022/05/18 07:40:24 UTC
[camel-k] branch release-1.9.x updated (2395dff39 -> 46289bfaf)
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch release-1.9.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git
from 2395dff39 Fix #3271: Prepend Organization/Namespace in HTTP path when uploading to the image registry from the command line
new 7b47c9cfc Adding the option of using docker registry
new a9174758d Using a variable for the version.
new 46289bfaf docs: Adding a link instead of explaining how to add another registry
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/modules/ROOT/pages/contributing/local-development.adoc | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
[camel-k] 02/03: Using a variable for the version.
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch release-1.9.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit a9174758ddc90be951b9e0d218b159a074368275
Author: María Arias de Reyna <de...@gmail.com>
AuthorDate: Tue May 17 09:44:07 2022 +0200
Using a variable for the version.
---
docs/modules/ROOT/pages/contributing/local-development.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributing/local-development.adoc b/docs/modules/ROOT/pages/contributing/local-development.adoc
index 78f56aa72..38926ac90 100644
--- a/docs/modules/ROOT/pages/contributing/local-development.adoc
+++ b/docs/modules/ROOT/pages/contributing/local-development.adoc
@@ -62,23 +62,23 @@ A similar procedure may work if you use other local environments. The idea is to
Camel K integrations are based on https://github.com/apache/camel-k-runtime[Camel K runtime], generally paired with the operator release. If you need to specify a different runtime, or you have a local Camel K runtime that you want to test, then you will need to specify it in the `Integration Platform`:
----
-./kamel install --skip-operator-setup -n operator-test --registry localhost:5000 --force --runtime-version 1.7.0-SNAPSHOT
+./kamel install --skip-operator-setup -n operator-test --registry localhost:5000 --force --runtime-version $version
----
-With the above instructions, the operator will pick up and use the snapshot version you have released locally.
+The `$version` variable must be replaced with the version you are building. For example, `1.3.1-SNAPSHOT`. With these instructions, the operator will pick up and use the snapshot version you have released locally.
==== Using a Docker registry
Alternatively, if no local registry is available, you can use a docker registry. First, create a secret with your registry username and password:
```
-kubectl -n default create secret docker-registry external-registry-secret --docker-username my-user --docker-password "password"
+kubectl -n default create secret docker-registry external-registry-secret --docker-username $my-user --docker-password "$password"
```
And then you can run the installation of Camel K operator:
```
-./kamel install --skip-operator-setup -n operator-test --force --runtime-version 1.7.0-SNAPSHOT --registry docker.io --organization my-org-or-username --registry-secret external-registry-secret
+./kamel install --skip-operator-setup -n operator-test --force --runtime-version $version --registry docker.io --organization $my-org-or-username --registry-secret external-registry-secret
```
-Make sure to replace the `my-org-or-username` with your actual username or organization used to host the images.
+Make sure to replace the `$my-org-or-username` with your actual username or organization used to host the images and the `$version` with the appropiate version number.
[camel-k] 01/03: Adding the option of using docker registry
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch release-1.9.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 7b47c9cfcd0d87c55dd1907e76db5af02557cab8
Author: María Arias de Reyna <de...@gmail.com>
AuthorDate: Tue May 17 09:35:12 2022 +0200
Adding the option of using docker registry
As described in https://camel.apache.org/camel-k/1.9.x/installation/platform/kind.html
---
.../ROOT/pages/contributing/local-development.adoc | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/contributing/local-development.adoc b/docs/modules/ROOT/pages/contributing/local-development.adoc
index 4bd0316d4..78f56aa72 100644
--- a/docs/modules/ROOT/pages/contributing/local-development.adoc
+++ b/docs/modules/ROOT/pages/contributing/local-development.adoc
@@ -65,4 +65,20 @@ Camel K integrations are based on https://github.com/apache/camel-k-runtime[Came
./kamel install --skip-operator-setup -n operator-test --registry localhost:5000 --force --runtime-version 1.7.0-SNAPSHOT
----
-With the above instructions, the operator will pick up and use the snapshot version you have released locally.
\ No newline at end of file
+With the above instructions, the operator will pick up and use the snapshot version you have released locally.
+
+==== Using a Docker registry
+
+Alternatively, if no local registry is available, you can use a docker registry. First, create a secret with your registry username and password:
+
+```
+kubectl -n default create secret docker-registry external-registry-secret --docker-username my-user --docker-password "password"
+```
+
+And then you can run the installation of Camel K operator:
+
+```
+./kamel install --skip-operator-setup -n operator-test --force --runtime-version 1.7.0-SNAPSHOT --registry docker.io --organization my-org-or-username --registry-secret external-registry-secret
+```
+
+Make sure to replace the `my-org-or-username` with your actual username or organization used to host the images.
[camel-k] 03/03: docs: Adding a link instead of explaining how to add another registry
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch release-1.9.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 46289bfafa2813b7e8b691a573b0a1da811558ea
Author: María Arias de Reyna <de...@gmail.com>
AuthorDate: Wed May 18 09:14:44 2022 +0200
docs: Adding a link instead of explaining how to add another registry
---
.../ROOT/pages/contributing/local-development.adoc | 16 +---------------
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributing/local-development.adoc b/docs/modules/ROOT/pages/contributing/local-development.adoc
index 38926ac90..547b2295b 100644
--- a/docs/modules/ROOT/pages/contributing/local-development.adoc
+++ b/docs/modules/ROOT/pages/contributing/local-development.adoc
@@ -67,18 +67,4 @@ Camel K integrations are based on https://github.com/apache/camel-k-runtime[Came
The `$version` variable must be replaced with the version you are building. For example, `1.3.1-SNAPSHOT`. With these instructions, the operator will pick up and use the snapshot version you have released locally.
-==== Using a Docker registry
-
-Alternatively, if no local registry is available, you can use a docker registry. First, create a secret with your registry username and password:
-
-```
-kubectl -n default create secret docker-registry external-registry-secret --docker-username $my-user --docker-password "$password"
-```
-
-And then you can run the installation of Camel K operator:
-
-```
-./kamel install --skip-operator-setup -n operator-test --force --runtime-version $version --registry docker.io --organization $my-org-or-username --registry-secret external-registry-secret
-```
-
-Make sure to replace the `$my-org-or-username` with your actual username or organization used to host the images and the `$version` with the appropiate version number.
+Alternatively, if no local registry is available, you can use another type of registry as explained in xref:installation/registry/registry.adoc[the Registry section].