This is an automated email from the ASF dual-hosted git repository.
davsclaus 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 702f5e36 chore: remove EOL CK and Kamelets (#954)
702f5e36 is described below
commit 702f5e36e4d94f4b36bbc9d98dd2241c153c7fec
Author: Claus Ibsen <[email protected]>
AuthorDate: Fri Dec 23 15:39:46 2022 +0100
chore: remove EOL CK and Kamelets (#954)
---
content/blog/2022/04/camel-k-release-1-9/index.md | 2 +-
.../2022/06/Optimizing-Camel-K-Integration-Build-Time/index.md | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/blog/2022/04/camel-k-release-1-9/index.md
b/content/blog/2022/04/camel-k-release-1-9/index.md
index 6c2e50ec..4f509914 100644
--- a/content/blog/2022/04/camel-k-release-1-9/index.md
+++ b/content/blog/2022/04/camel-k-release-1-9/index.md
@@ -48,7 +48,7 @@ Another little improvement was to redirect all the warning
output to the `stderr
## Removed specialized builder configuration
-We decided to deprecate the Kaniko settings which were directly exposed in the
generic `IntegrationPlatform.build.spec` (see the
[API](/camel-k/1.9.x/apis/camel-k.html#_camel_apache_org_v1_IntegrationPlatformBuildSpec)).
We've moved them in some more general purpose
`.build.spec.PublishStrategyOptions`. From now on, we'll have a cleaner
configuration which does not define any implementation detail. And we'll have a
place where to hold any future Builder specialized options too!
+We decided to deprecate the Kaniko settings which were directly exposed in the
generic `IntegrationPlatform.build.spec`. We've moved them in some more general
purpose `.build.spec.PublishStrategyOptions`. From now on, we'll have a cleaner
configuration which does not define any implementation detail. And we'll have a
place where to hold any future Builder specialized options too!
## Kamel bind trait option
diff --git
a/content/blog/2022/06/Optimizing-Camel-K-Integration-Build-Time/index.md
b/content/blog/2022/06/Optimizing-Camel-K-Integration-Build-Time/index.md
index 86a6ab4b..36d54ddb 100644
--- a/content/blog/2022/06/Optimizing-Camel-K-Integration-Build-Time/index.md
+++ b/content/blog/2022/06/Optimizing-Camel-K-Integration-Build-Time/index.md
@@ -19,9 +19,9 @@ The effect of faster build times may be seen in the benchmark
comparisons below.
### System Configuration
-| Device | Chip | Total Number of Cores | Memory |
-| ------- | ----- | -------- |--------|
-|MacBook Air (M1)| Apple Sillicon M1 | 8 core CPU (4 performance and 4
efficiency), 7 Core GPU | 8GB
+| Device | Chip | Total Number of Cores
| Memory |
+|------------------|-------------------|---------------------------------------------------------|--------|
+| MacBook Air (M1) | Apple Sillicon M1 | 8 core CPU (4 performance and 4
efficiency), 7 Core GPU | 8GB |
### Environment Configuration
@@ -89,7 +89,7 @@ It is clear that the build time has decreased significantly;
with more powerful
### Leveraging the benefit
-To utilise this newly available functionality and apply CPU constraints on
operator deployment, select from the following example measures or consult the
[Resource
Management](/camel-k/1.9.x/installation/advanced/resources.html#scheduling-infra-pod-resources)
guide to modify it about their own needs.
+To utilise this newly available functionality and apply CPU constraints on
operator deployment, select from the following example measures or consult the
[Resource
Management](/camel-k/next/installation/advanced/resources.html#scheduling-infra-pod-resources)
guide to modify it about their own needs.
```shell
kamel install --operator-resources requests.cpu=256m --operator-resources
limits.cpu=500m --operator-resources limits.memory=512Mi ...
