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-k.git
The following commit(s) were added to refs/heads/main by this push:
new de3b71177 doc: upgrade deployment procedure
de3b71177 is described below
commit de3b71177d3f004763e66d36e58669e0a8624853
Author: Pasquale Congiusti <pasquale.congiu...@gmail.com>
AuthorDate: Thu May 16 15:24:32 2024 +0200
doc: upgrade deployment procedure
Ref #5491
---
docs/modules/ROOT/pages/installation/upgrade.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/modules/ROOT/pages/installation/upgrade.adoc
b/docs/modules/ROOT/pages/installation/upgrade.adoc
index a04ed6448..eb5cf6a18 100644
--- a/docs/modules/ROOT/pages/installation/upgrade.adoc
+++ b/docs/modules/ROOT/pages/installation/upgrade.adoc
@@ -12,6 +12,8 @@ kamel install --force --olm=false
This operation will install all the required configuration for the new
operator version, replacing the previous one. Mind that the `Integration`
resources running won't be affected, so they will keep running with the default
runtime details provided in the previous operator version.
+However you must notice that the deployment resources linked to an Integration
(ie, Deployment, Knative-Service or CronJob) can change, if the new operator is
setting any new configuration. This would lead to a transparent Pod rollout for
all the existing Integrations at their very first reconciliation loop cycle
(when the new operator will takeover from the previous one).
+
[[helms-crds]]
== CRD Upgrades (Helm upgrade)
