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 1bd9f6e7 fix: ck links cleaning
1bd9f6e7 is described below
commit 1bd9f6e753307e474c1519133c9e52b1a56c693b
Author: Pasquale Congiusti <pasquale.congiu...@gmail.com>
AuthorDate: Wed Sep 4 16:51:14 2024 +0200
fix: ck links cleaning
---
content/blog/2021/04/camel-k-140-Whatsnew/index.md | 6 +++---
content/blog/2021/07/camel-k-properties-refactoring/index.md | 2 +-
content/blog/2022/11/camel-k-jbang/index.md | 2 +-
content/blog/2023/07/camel-k-2-0/index.md | 6 +++---
content/blog/2024/01/camel-k-2-2/index.md | 2 +-
content/blog/2024/04/sourceless-ck-springboot/index.md | 4 ++--
6 files changed, 11 insertions(+), 11 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 e2d1cf1d..bf9c19b3 100644
--- a/content/blog/2021/04/camel-k-140-Whatsnew/index.md
+++ b/content/blog/2021/04/camel-k-140-Whatsnew/index.md
@@ -54,7 +54,7 @@ And the command will create a binding that just prints to the
log the JSON data
## Kamel dump command
-When users have issues understanding why Camel K is not behaving as expected,
they often need to provide useful information
+When users have issues understanding why Camel K is not behaving as expected,
they often need to provide useful information
about the current state of their cluster, to let Camel K developers
investigate the issue and provide a solution or a quick workaround (e.g. in a
Github issue, or in the Zulip chat).
Usually, to identify the root cause of an issue, developers need to know
things like:
@@ -72,7 +72,7 @@ kamel dump status.log
```
This simple command will store in a text file all the information needed to
investigate a possible issue in the cluster.
-The user can now *edit the file to remove sensitive information* (which the
command may not be able to tell apart), then
+The user can now *edit the file to remove sensitive information* (which the
command may not be able to tell apart), then
share it with developers to have much better insights.
## Stability and compatibility
@@ -84,7 +84,7 @@ to be present for the same service. We've also changed the
way channels and brok
to bind integrations to multiple channels and even create sequences of
integrations attached to channels without any issue (e.g.
[#2190](https://github.com/apache/camel-k/pull/2190),
[#2115](https://github.com/apache/camel-k/pull/2115)).
We've improved **installation options**, letting you configure things that may
be important in a production environment, like [setting
toleration](https://github.com/apache/camel-k/pull/2114) or using a [secured
maven repository](https://github.com/apache/camel-k/pull/2180).
-At the same time, we've fixed compatibility with recent dev environments, e.g.
letting you [smoothly install Camel K in
K3S](/camel-k/next/installation/registry/k3s.html).
+At the same time, we've fixed compatibility with recent dev environments, e.g.
letting you smoothly install Camel K in K3S.
We also kept doing changes to continuously improve speed. On the runtime side
of Camel K, we now use the [Quarkus fast-jar
format](https://github.com/apache/camel-k/pull/1931) to reduce boot times. And
last but not least on the operator side, it's possible to install Camel K
globally in a cluster and have much faster build times by [sharing base images
across the cluster](https://github.com/apache/camel-k/pull/2058).
diff --git a/content/blog/2021/07/camel-k-properties-refactoring/index.md
b/content/blog/2021/07/camel-k-properties-refactoring/index.md
index 51ceeb2a..266f0537 100644
--- a/content/blog/2021/07/camel-k-properties-refactoring/index.md
+++ b/content/blog/2021/07/camel-k-properties-refactoring/index.md
@@ -25,7 +25,7 @@ Through this blog you will learn about:
If you're an experienced Camel K developer, you are certainly familiar with
the `--property` (abbreviated `--p`) and `--property-file` flags of the `kamel
run` command. Through these flags you are instructing the runtime `Integration`
to include properties configuration that will be used during the application
execution. Within version 1.5 we made a slight change on how to provide a
property file. We have deprecated the `--property-file` flag and favoured the
new syntax `--property file: [...]
Since this version we're also starting to distinguish between **runtime**
properties and **build-time** properties. `--property` will be used to identify
runtime properties.
-Learn more in the [runtime properties documentation
page](/camel-k/next/configuration/runtime-properties.html).
+Learn more in the runtime properties documentation page.
## Build-time properties
diff --git a/content/blog/2022/11/camel-k-jbang/index.md
b/content/blog/2022/11/camel-k-jbang/index.md
index 0f7b1e7f..2dd98732 100644
--- a/content/blog/2022/11/camel-k-jbang/index.md
+++ b/content/blog/2022/11/camel-k-jbang/index.md
@@ -146,7 +146,7 @@ The Integration started correctly, but, wait a minute: we
are using a file syste
Probably it's not what we wanted. So, now it's turn to configure our
application for the cloud. Cloud Native development should take in
consideration a series of challenges that are implicit in the way how this new
paradigm works (as a reference see the [12 factors](https://12factor.net/)).
-Kubernetes could be sometimes a bit difficult to fine tune. Many resources to
edit and check. Camel K provide a user friendly way to apply most of the tuning
your application will need directly in the `kamel run` command (or in the
[modeline](/camel-k/next/cli/modeline.html)). Most of the time you will need to
get familiar with [Camel K Traits](/camel-k/next/traits/traits.html).
+Kubernetes could be sometimes a bit difficult to fine tune. Many resources to
edit and check. Camel K provide a user friendly way to apply most of the tuning
your application will need directly in the `kamel run` command (or in the
modeline). Most of the time you will need to get familiar with [Camel K
Traits](/camel-k/next/traits/traits.html).
In this case we want to use certain volumes we had made available in our
cluster. We can use the `--volume` option (syntactic sugar of [mount
trait](/camel-k/next/traits/mount.html)) and enable them easily. We can read
and write on those volumes from some other `Pod`: it depends on the
architecture of our Integration process.
diff --git a/content/blog/2023/07/camel-k-2-0/index.md
b/content/blog/2023/07/camel-k-2-0/index.md
index 626f259f..ae742fb1 100644
--- a/content/blog/2023/07/camel-k-2-0/index.md
+++ b/content/blog/2023/07/camel-k-2-0/index.md
@@ -35,7 +35,7 @@ WARNING: make sure not to downgrade to Camel K version 1 once
you have upgraded
The old `v1alpha1.KameletBinding` will still be supported in this release in
order to give you the time to make the needed change and move all your
KameletBindings to
[`v1.Pipe`](/camel-k/next/apis/camel-k.html#_camel_apache_org_v1_Pipe). Try to
give priority to this operation because the `v1alpha1` is now deprecated and
will be removed within the next versions of Camel K.
-There is no other important concern about the compatibility with the previous
Camel K version.
+There is no other important concern about the compatibility with the previous
Camel K version.
We suggest to take the opportunity of this major upgrade to detect any usage
of deprecated parameters in the [Camel K API](/camel-k/next/apis/camel-k.html)
and do the switch accordingly.
@@ -57,7 +57,7 @@ The build process is now partially decoupled from the runtime
process. We have i
In order to enable this feature, you will notice that the `CamelCatalog`
Custom Resource is now a dynamic resource which is reconciled by the operator.
It is the one in charge to dynamically create any new runtime catalog required.
This work was a big design change and we're confident it will help use reaching
the longer term goal which is to **onboard any Camel runtime** (main,
springboot, quarkus).
-Have a look at the official documentation and learn more about the new [Camel
K Runtime builder design](/camel-k/next/running/runtime-version.html).
+Have a look at the official documentation and learn more about the new Camel K
Runtime builder design.
## Transform the build into a pipeline
@@ -67,7 +67,7 @@ The first immediate result of this change is that you have
available a [simple C
## Camel K Tekton tasks
-We also know that many companies already adopts some richer **CICD
technology**. For this reason we have introduced the [Camel K Tekton
task](/camel-k/next/pipeline/tekton.html) which we're willing to support in
order to simplify the onboarding of Camel K in Tekton pipeline.
+We also know that many companies already adopts some richer **CICD
technology**. For this reason we have introduced the Camel K Tekton task which
we're willing to support in order to simplify the onboarding of Camel K in
Tekton pipeline.
We have chosen to support Tekton because it's one of the most mature and
widespread used CICD technology. However, if you're using any other pipeline
technology it should not be difficult to transform the action we are supporting
in Tekton task with the one required by your pipeline technology.
diff --git a/content/blog/2024/01/camel-k-2-2/index.md
b/content/blog/2024/01/camel-k-2-2/index.md
index d69c0a2b..c1913429 100644
--- a/content/blog/2024/01/camel-k-2-2/index.md
+++ b/content/blog/2024/01/camel-k-2-2/index.md
@@ -26,7 +26,7 @@ spec:
image: docker.io/my-org/my-camel-app:1.0.0
```
-See more detail in the official [Camel K runtimes
documentation](/camel-k/next/running/camel-runtimes.html). The nice thing is
that with this approach you will be able to run **Camel Quarkus**, **Camel
Springboot** and **Camel Main** runtimes from Camel K operator.
+See more detail in the official Camel K runtimes documentation. The nice thing
is that with this approach you will be able to run **Camel Quarkus**, **Camel
Springboot** and **Camel Main** runtimes from Camel K operator.
## Show root image hierarchy in IntegrationKits
diff --git a/content/blog/2024/04/sourceless-ck-springboot/index.md
b/content/blog/2024/04/sourceless-ck-springboot/index.md
index 5119fba5..f2849523 100644
--- a/content/blog/2024/04/sourceless-ck-springboot/index.md
+++ b/content/blog/2024/04/sourceless-ck-springboot/index.md
@@ -26,13 +26,13 @@ spec:
image: docker.io/my-org/my-camel-app:1.0.0
```
-See more detail in the official [Camel K runtimes
documentation](/camel-k/next/running/camel-runtimes.html). The nice thing is
that with this approach you will be able to run **Camel Quarkus**, **Camel
Spring Boot** and **Camel Main** runtimes from Camel K operator.
+See more detail in the official Camel K runtimes documentation. The nice thing
is that with this approach you will be able to run **Camel Quarkus**, **Camel
Spring Boot** and **Camel Main** runtimes from Camel K operator.
As we mentioned at the beginning, there are certain limitations you need to
take in consideration. In the linked documentation you can see there is a
matrix of traits and at what lifecycle stage of an Integration they are
executed. A sourceless Integration will only be able to use "deployment" traits
out of the box, that means, those aspects that are executed when the
Integration is deployed to Kubernetes.
## How to run it
-A **sourceless Integration** is built by the user. The operator does not care
how this is built. What it needs to know is the final container image. Let's
see an example in action in order to show how the Camel K operator will be able
to leverage at least "deployment" traits and simplify certain operational
aspects on Kubernetes. The list of trait you can use is available in [Camel K
runtimes documentation](/camel-k/next/running/camel-runtimes.html).
+A **sourceless Integration** is built by the user. The operator does not care
how this is built. What it needs to know is the final container image. Let's
see an example in action in order to show how the Camel K operator will be able
to leverage at least "deployment" traits and simplify certain operational
aspects on Kubernetes. The list of trait you can use is available in Camel K
runtimes documentation.
We will build a simple REST Camel application and we want to leverage
**Knative** in order to **scale to 0** if no traffic happens on the route.
Without the Camel K operator, you'd be needed to manage all the Knative
resources on your own. The operator will instead do all the heavy lift for you.
