From 8e9cd2ab1fd71319137d05fd7cb3b9011773013a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Attila=20M=C3=A9sz=C3=A1ros?= Date: Fri, 26 Jan 2024 11:01:23 +0100 Subject: [PATCH 1/3] docs: note on activation condition MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Attila Mészáros --- docs/documentation/workflows.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/documentation/workflows.md b/docs/documentation/workflows.md index 27cd2f4274..2ba642afb2 100644 --- a/docs/documentation/workflows.md +++ b/docs/documentation/workflows.md @@ -43,6 +43,10 @@ reconciliation process. condition holds or not. This is a very useful feature when your operator needs to handle different flavors of the platform (e.g. OpenShift vs plain Kubernetes) and/or change its behavior based on the availability of optional resources / features (e.g. CertManager, a specific Ingress controller, etc.). + + Activation condition is semi-experimental at the moment, it is fully supported, but it has its limitations. + For example event sources cannot be shared between multiple managed dependent resources. The intention is + to further improve and explore the possibilities with this approach. ## Defining Workflows From 128da26533a65b60e2c5d32202901d28e20065bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Attila=20M=C3=A9sz=C3=A1ros?= Date: Fri, 26 Jan 2024 11:02:37 +0100 Subject: [PATCH 2/3] improve MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Attila Mészáros --- docs/documentation/workflows.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/documentation/workflows.md b/docs/documentation/workflows.md index 2ba642afb2..ef6a387756 100644 --- a/docs/documentation/workflows.md +++ b/docs/documentation/workflows.md @@ -45,8 +45,8 @@ reconciliation process. resources / features (e.g. CertManager, a specific Ingress controller, etc.). Activation condition is semi-experimental at the moment, it is fully supported, but it has its limitations. - For example event sources cannot be shared between multiple managed dependent resources. The intention is - to further improve and explore the possibilities with this approach. + For example event sources cannot be shared between multiple managed dependent resources which use activation condition. + The intention is to further improve and explore the possibilities with this approach. ## Defining Workflows From 148ee73458bb9b4416878f7540b487ff732c08d4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Attila=20M=C3=A9sz=C3=A1ros?= Date: Fri, 26 Jan 2024 11:04:37 +0100 Subject: [PATCH 3/3] update MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Attila Mészáros --- docs/documentation/workflows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/workflows.md b/docs/documentation/workflows.md index ef6a387756..7190f8e8e3 100644 --- a/docs/documentation/workflows.md +++ b/docs/documentation/workflows.md @@ -44,7 +44,7 @@ reconciliation process. platform (e.g. OpenShift vs plain Kubernetes) and/or change its behavior based on the availability of optional resources / features (e.g. CertManager, a specific Ingress controller, etc.). - Activation condition is semi-experimental at the moment, it is fully supported, but it has its limitations. + Activation condition is semi-experimental at the moment, and it has its limitations. For example event sources cannot be shared between multiple managed dependent resources which use activation condition. The intention is to further improve and explore the possibilities with this approach.