You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "squakez (via GitHub)" <gi...@apache.org> on 2023/10/18 10:25:25 UTC
[PR] feat(blog): Camel K version 2.1.0 [camel-website]
squakez opened a new pull request, #1076:
URL: https://github.com/apache/camel-website/pull/1076
To be merged once the vote close and the release can be announced.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "gansheer (via GitHub)" <gi...@apache.org>.
gansheer commented on code in PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#discussion_r1363673043
##########
content/blog/2023/10/camel-k-2-1/index.md:
##########
@@ -0,0 +1,107 @@
+---
+title: "Camel K 2.1"
+date: 2023-10-20
+draft: false
+authors: [squakez]
+categories: ["Releases", "Camel K", "Roadmap"]
+preview: "What's new in Camel K 2.1!"
+---
+
+Apache Camel community is happy to announce the general availability of **Camel K 2.1**. We have worked on the introduction of a lot of new exciting feature that will further **simplify the deployment and management of Camel application on Kubernetes**. Let's see what you should expect from this release.
+
+## Default Camel 4 runtime
+
+As **Camel 4** is out since some time already, we've moved our default runtime to Camel K Runtime version 3.2.0, which is based on Camel Quarkus 3.2.0 and Camel 4. From now on, by default you will use this runtime version.
+
+## More enterprise ready build
+
+One of the main goal of 2023 roadmap was to make our **build system "enterprise ready"**. In this release we've worked a lot in that direction.
+
+The pipeline concept we have introduced in version 2.0 is now more complete with the split of the build tasks into a proper `build` and a `package` which is in charge to prepare the context for a following publish with one of the strategies chosen by the user. The result is illustrated in the following diagram:
+
+
+_Camel K Pipeline tasks_
+
+This gives you more flexibility by letting you customize the build before the binaries are taken by the package task. Beside this change we have introduced a lot of advanced configuration in the Builder trait. Each custom task you will define, can be configured with limits and requests resources: `builder.tasks-request-cpu`, `builder.tasks-request-memory`, `builder.tasks-limit-cpu`, `builder.tasks-limit-memory`.
+Another interesting option we have introduced, was to let the user disable the Incremental Image Build option via `builder.incremental-image-build`. It is not advisable, but there could be situations were you don't want your Integration inherit from existing IntegrationKits.
+
+Always related to the builder, you will find now the presence of `builder.maven-profile` option. With this one you can provide a customized [Maven profile](https://maven.apache.org/guides/introduction/introduction-to-profiles.html#profiles-in-poms) to your build. This is cool if you want to influence the build phase in any manner.
Review Comment:
This one got changed to a multi-valued field `builder.maven-profiles`. That mean you can provide multiple maven profiles
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#issuecomment-1774885139
🚀 Preview is available at https://pr-1076--camel.netlify.app
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#issuecomment-1768242613
🚀 Preview is available at https://pr-1076--camel.netlify.app
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez merged PR #1076:
URL: https://github.com/apache/camel-website/pull/1076
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd commented on PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#issuecomment-1768216755
Looks good to me. I think the security context might require a separated blog post with some example of how/why it's important.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus commented on PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#issuecomment-1768397783
Nice to see soo much progress since 2.0 release
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#issuecomment-1768512239
🚀 Preview is available at https://pr-1076--camel.netlify.app
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#issuecomment-1768148783
cc @gansheer @oscerd @christophd
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "gansheer (via GitHub)" <gi...@apache.org>.
gansheer commented on code in PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#discussion_r1363676063
##########
content/blog/2023/10/camel-k-2-1/index.md:
##########
@@ -0,0 +1,107 @@
+---
+title: "Camel K 2.1"
+date: 2023-10-20
+draft: false
+authors: [squakez]
+categories: ["Releases", "Camel K", "Roadmap"]
+preview: "What's new in Camel K 2.1!"
+---
+
+Apache Camel community is happy to announce the general availability of **Camel K 2.1**. We have worked on the introduction of a lot of new exciting feature that will further **simplify the deployment and management of Camel application on Kubernetes**. Let's see what you should expect from this release.
+
+## Default Camel 4 runtime
+
+As **Camel 4** is out since some time already, we've moved our default runtime to Camel K Runtime version 3.2.0, which is based on Camel Quarkus 3.2.0 and Camel 4. From now on, by default you will use this runtime version.
+
+## More enterprise ready build
+
+One of the main goal of 2023 roadmap was to make our **build system "enterprise ready"**. In this release we've worked a lot in that direction.
+
+The pipeline concept we have introduced in version 2.0 is now more complete with the split of the build tasks into a proper `build` and a `package` which is in charge to prepare the context for a following publish with one of the strategies chosen by the user. The result is illustrated in the following diagram:
+
+
+_Camel K Pipeline tasks_
+
+This gives you more flexibility by letting you customize the build before the binaries are taken by the package task. Beside this change we have introduced a lot of advanced configuration in the Builder trait. Each custom task you will define, can be configured with limits and requests resources: `builder.tasks-request-cpu`, `builder.tasks-request-memory`, `builder.tasks-limit-cpu`, `builder.tasks-limit-memory`.
+Another interesting option we have introduced, was to let the user disable the Incremental Image Build option via `builder.incremental-image-build`. It is not advisable, but there could be situations were you don't want your Integration inherit from existing IntegrationKits.
+
+Always related to the builder, you will find now the presence of `builder.maven-profile` option. With this one you can provide a customized [Maven profile](https://maven.apache.org/guides/introduction/introduction-to-profiles.html#profiles-in-poms) to your build. This is cool if you want to influence the build phase in any manner.
+
+Next thing, we have removed the dynamic builder catalog which will give the operator more stability, getting rid off one moving part (which may always fail for any reason). It was part of a more general Quarkus Native refactoring where we have also introduced a series of advanced configurations. From now on, in the Quarkus trait you can specify the `quarkus.native-builder-image` and the `quarkus.native-base-image` to respectively override which is the container image you want to use for the native build and which is the one you want to use in your Native integration.
+We have also simplified the configuration required to run either a JVM or Native Quarkus application by introducing the trait parameter `quarkus.build-mode` which simply accept `jvm` or `native` values. The previous `quarkus.package-type` (now deprecated) was exposing implementation details not really user friendly (who of you can tell what a `fast-jar` is!?).
+
+Our friends at Tekton have onboarded the [Camel K task in the Tekton Catalog](https://hub.tekton.dev/tekton/task/kamel-run). From now on, Camel K is a first class citizen in Tekton and we do support the task. Feel free to start using it in your CICD pipelines. Our internal pipeline may be limited when you're dealing with complex CICDs.
+
+More on the builder side it is the introduction of **JIB as an additional builder strategy** and the deprecation of Buildah and Kaniko. As you may understand, we cannot really provide support for all existing technologies. In the future we may even deprecate Spectrum, letting Jib being the default choice. In any case, the flexibility of the pipeline will give you the possibility to use any custom publishing strategy on your own.
+
+## Restricted security context
+
+Security is something we have at hearth. From now on, by default, the operator and the Integration Pods will run with a **restricted security context**.
Review Comment:
```suggestion
Security is something we have at heart. From now on, by default, the operator and the Integration Pods will run with a **restricted security context**.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(blog): Camel K version 2.1.0 [camel-website]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #1076:
URL: https://github.com/apache/camel-website/pull/1076#issuecomment-1768515681
🚀 Preview is available at https://pr-1076--camel.netlify.app
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org