(camel-website) branch main updated: fix(blog): note with certain version not supporting

[pc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/main by this push:
     new d441b592 fix(blog): note with certain version not supporting
d441b592 is described below

commit d441b592283c0e7bc8a50c49e12a016bff62cfb9
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Thu Oct 31 18:28:22 2024 +0100

    fix(blog): note with certain version not supporting
    
    Closes https://github.com/squakez/camelk-gitops-example/issues/1
---
 content/blog/2023/07/camel-k-gitops/index.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/blog/2023/07/camel-k-gitops/index.md b/content/blog/2023/07/camel-k-gitops/index.md
index e0cfd3f6..1aff2bfe 100644
--- a/content/blog/2023/07/camel-k-gitops/index.md
+++ b/content/blog/2023/07/camel-k-gitops/index.md
@@ -65,6 +65,8 @@ We've used the generic approach suggested in this [GitOps promotion model articl
 
 ## Prepare development Integration
 
+NOTE: this example was originally developed for Camel K operator version 1.12.x and won't work out of the box with Camel K operator version 2.3.x and 2.4.x. We suggest to try this example with other available versions or adjust it to include the IntegrationKit resource which was needed by those operator versions. From version 2.5 onward, however, the example shown here should work out of the box.
+
 You can do the development according your company strategy, using [Camel JBang](/blog/2022/11/camel-k-jbang/), a [pipeline](https://github.com/apache/camel-k/tree/main/cicd/tekton/kamel-run/0.1) or directly the `kamel` CLI. As we want to just focus on the GitOps part, we're using `kamel` CLI which results more self-explainatory for the blog purpose.
 
 Everything starts with some kind of prototype. We can create a `my-route.yaml` route which we'll populate with some YAML DSL. The YAML route we're creating is using some configmap in order to show how we can apply configuration dynamically based on the environment we run. You can image the same when applied to databases, services, etcetera.