Skip to content

docs: note on activation condition #2220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 29, 2024
Merged

docs: note on activation condition #2220

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8e9cd2a
docs: note on activation condition
csviri Jan 26, 2024
128da26
improve
csviri Jan 26, 2024
148ee73
update
csviri Jan 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/documentation/workflows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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, 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.

## Defining Workflows

Expand Down