-
Feature
-
Resolution: Obsolete
-
Critical
-
None
-
False
-
None
-
False
-
0
-
0%
-
Todo
Instead of releasing the Camel K operator image and bundle at the same time as we do today we may switch to a more gradual approach. The idea is to first release the operator image and if this is proven to be ok by a final sanity check (e.g. verified upgrade/install on some staging environment) then we kick off the bundle release for that particular operator image.
This gives us the opportunity to avoid having a broken operator image being part of a bundle already published. Avoid users to start install and upgrade based on the bundle with a potential broken image.
As long as the bundle has not been published we can still go back and fix the operator image. We finally want to be sure that the operator image and bundle is fully verified before reaching out to the public.
- is triggered by
-
ENTESB-19495 Camel-K 1.6.8 Operator Referencing release 2 image - can not pull / start
- Closed
- relates to
-
ENTESB-19609 Conduct checks to verify bundle image metadata for replace & skipRange are correct
- Closed
- links to