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-k.git
The following commit(s) were added to refs/heads/main by this push:
new 5dbafc998 Fix docs for website build
5dbafc998 is described below
commit 5dbafc998e133544f9eebbe4a4e26524e101f1fc
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Apr 17 19:40:04 2024 +0200
Fix docs for website build
---
docs/modules/ROOT/pages/installation/upgrade.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/installation/upgrade.adoc
b/docs/modules/ROOT/pages/installation/upgrade.adoc
index a601385b3..a04ed6448 100644
--- a/docs/modules/ROOT/pages/installation/upgrade.adoc
+++ b/docs/modules/ROOT/pages/installation/upgrade.adoc
@@ -13,7 +13,7 @@ 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.
[[helms-crds]]
-=== CRD Upgrades (Helm upgrade)
+== CRD Upgrades (Helm upgrade)
Generally, when upgrading a patch or a minor version, we may introduce slight
non-breaking compatibility changes in CRDs. These changes should be onboarded
with the installation procedure you're using (CLI, OLM). However, you may want
to control the upgrade of CRDs (for instance, upgrading in Helm, which, does
not support CRDs upgrade out of the box). In this case, before doing the
upgrade, you'll need to manually upgrade the CRDs, in order to use the new
parameters expected by the new o [...]
