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 23098d4f Add IntegrationProfile to "What's new in Camel K 2.3.0"
23098d4f is described below
commit 23098d4ffaa86e9e9ef2262ee534c6e0cd3df50e
Author: Christoph Deppisch <cdeppi...@redhat.com>
AuthorDate: Mon Apr 8 11:34:40 2024 +0200
Add IntegrationProfile to "What's new in Camel K 2.3.0"
---
content/blog/2024/04/camel-k-2-3/index.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/content/blog/2024/04/camel-k-2-3/index.md
b/content/blog/2024/04/camel-k-2-3/index.md
index 1561b742..b8380815 100644
--- a/content/blog/2024/04/camel-k-2-3/index.md
+++ b/content/blog/2024/04/camel-k-2-3/index.md
@@ -49,6 +49,9 @@ In the previous Camel K versions we had deprecated certain
supported publishing
Mind that the [Spectrum](https://github.com/container-tools/spectrum) strategy
will be very likely deprecated in future version of Camel K, leaving Jib as the
only publishing strategy available out of the box. If you're still using it,
you may think to start migrating to Jib as soon as possible.
+## Introduce IntegrationProfile custom resource
+The new IntegrationProfile custom resource allows users overwrite settings
(e.g. trait configurations) for multiple integrations that all reference the
same profile. The IntegrationProfile resource is keen to replace the namespace
local IntegrationPlatform as well as the secondary platform. In contrast to the
IntegrationPlatform resource the IntegrationProfile only exposes a subset of
settings that are eligible to be controlled on a user namespace level. In
upcoming releases the Integrat [...]
+
## Deprecated features
While working on several optimizations, we've decided to deprecate a few
features. In this version we've deprecated the `kamel run -d file:xyz` feature
(plus the related Registry trait) and we've introduced a flag to control a
potential dangerous behavior which was happening by default in Kamelets. The
`mount.scan-kamelets-implicit-label-secrets` is deprecated and still enabled by
default in this version.
