This is an automated email from the ASF dual-hosted git repository.
acosentino 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 5a9092ad Removed old fragment
5a9092ad is described below
commit 5a9092ad8d87d44744cac74cc21264c916828652
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Tue Apr 30 12:45:10 2024 +0200
Removed old fragment
Signed-off-by: Andrea Cosentino <anco...@gmail.com>
---
content/blog/2021/04/camel-k-140-Whatsnew/index.md | 2 --
1 file changed, 2 deletions(-)
diff --git a/content/blog/2021/04/camel-k-140-Whatsnew/index.md
b/content/blog/2021/04/camel-k-140-Whatsnew/index.md
index e5932040..e2d1cf1d 100644
--- a/content/blog/2021/04/camel-k-140-Whatsnew/index.md
+++ b/content/blog/2021/04/camel-k-140-Whatsnew/index.md
@@ -19,8 +19,6 @@ Camel K 1.4.0 comes with an embedded [Kamelet
catalog](/camel-kamelets/next/) co
When installing the operator into a namespace (but also globally in the
cluster), the operator installs all the kamelets from the catalog ([version
0.2.1](https://github.com/apache/camel-kamelets/tree/v0.2.1)), so that any
integration can use them directly.
-Users can bind them to a specific destination by writing a YAML binding file,
as explained in the [specific documentation related to each
Kamelet](/camel-kamelets/next/aws-sqs-source.html#_knative_source).
-
Or, you can use the new `kamel bind` command (see below).
**Note:** it's easy to write your own Kamelet and publish it to the Apache
Catalog. Take a look at the [Kamelets developer
guide](/camel-k/next/kamelets/kamelets-dev.html).
