This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch release-2.0.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/release-2.0.x by this push:
new 37e6fe7fe fix(doc): Add openshift builder image re-creation as known
issue
37e6fe7fe is described below
commit 37e6fe7feb6b970b8cabee0b2a68f2fa9cf333cd
Author: Gaelle Fournier <gaelle.fournier.w...@gmail.com>
AuthorDate: Wed Jul 26 11:49:15 2023 +0200
fix(doc): Add openshift builder image re-creation as known issue
Ref #4569
---
docs/modules/ROOT/pages/troubleshooting/known-issues.adoc | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/docs/modules/ROOT/pages/troubleshooting/known-issues.adoc
b/docs/modules/ROOT/pages/troubleshooting/known-issues.adoc
index 7b0330243..d4e422833 100644
--- a/docs/modules/ROOT/pages/troubleshooting/known-issues.adoc
+++ b/docs/modules/ROOT/pages/troubleshooting/known-issues.adoc
@@ -30,3 +30,16 @@ Or by patching your `IntegrationPlatform` resource directly
if you have Camel K
----
$ kubectl patch ip camel-k --type='merge' -p
'{"spec":{"build":{"publishStrategy":"kaniko"}}}'
----
+
+
+== `[Openshift] Repeated install/uninstall and removal of CamelCatalog leads
to re-creation of builder image`
+
+Openshift's internal container image registry operates on image streams
instead of directly on images. As a side effect in a non production usage it
can lead to an increase of the container image storage. This is because the
`uninstall` command will remove the CamelCatalog but can't remove the actual
container image.
+
+In case you don't need any change in the CamelCatalog, the solutions is to use
the following flag when uninstalling if you plan to install again after:
+
+[source,console]
+----
+kamel uninstall --skip-camel-catalogs
+----
+
