You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dev/operators.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,10 +20,9 @@ a time.
20
20
During upgrades, the contents of `/release-manifests` are applied in order, exactly as `ls` would
21
21
return on a standard Linux or Unix derivative. The CVO supports the idea of "run levels" by
22
22
defining a convention for how operators that wish to run before other operators should name
23
-
their manifests. A run level is of the form `0000_\d\d_[a-z0-9\-]+_<filename>` where the first
24
-
digits are the level (see [below for a list of assigned levels](#how-do-i-get-added-as-a-special-run-level)), the second chunk is the component name that
25
-
usually matches your operator name (e.g. `kube-apiserver` or `cluster-monitoring-operator`)
26
-
and the filename is a local name.
23
+
their manifests. Manifest files are of the form `0000_<runlevel>_<dash-separated-component>_<manifest_filename>`, declaring the run level (see [below for a list of assigned levels](#how-do-i-get-added-as-a-special-run-level)), the component name that
24
+
usually matches your operator name (e.g. `kube-apiserver` or `cluster-monitoring-operator`),
25
+
and a local name to order manifests within a given runlevel/component block.
27
26
28
27
A few special optimizations are applied above linear ordering - if the CVO sees two different
29
28
components that have the same run level - for instance, `0000_70_cluster-monitoring-operator_*` and
@@ -109,7 +108,7 @@ To do this, you can set .metadata.annotations["release.openshift.io/create-only"
109
108
110
109
Some operators need to run at a specific time in the release process (OLM, kube, openshift core operators, network, service CA). These components can ensure they run in a specific order across operators by prefixing their manifests with:
0 commit comments