This is an automated email from the ASF dual-hosted git repository. pcongiusti pushed a commit to branch squakez-patch-1 in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 75389cd2f907c124b7a06ba3971d3d2d0e97244d Author: Pasquale Congiusti <[email protected]> AuthorDate: Fri Jan 13 16:02:40 2023 +0100 chore(doc): cannot use build pod strategy in local operator. --- docs/modules/ROOT/pages/contributing/local-development.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/modules/ROOT/pages/contributing/local-development.adoc b/docs/modules/ROOT/pages/contributing/local-development.adoc index 548acb987..82d61e8a7 100644 --- a/docs/modules/ROOT/pages/contributing/local-development.adoc +++ b/docs/modules/ROOT/pages/contributing/local-development.adoc @@ -59,6 +59,8 @@ kubectl port-forward --namespace kube-system registry-fttbv 5000:5000 A similar procedure may work if you use other local environments. The idea is to expose the docker registry and be able to use it from your local operator. +IMPORTANT: using build strategy as `Pod` won't probably work as it will expect the registry to be available at a URL not possible to reach from a local machine. + === Local Camel K runtime 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`:
