Skip to content

Commit 3401029

Browse files
Merge pull request #439 from wking/fix-component-regexp-docs
docs/dev/operators: Replace stale manifest filename regexp with generic discussion
2 parents 247ab9a + a0f1164 commit 3401029

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

docs/dev/operators.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,9 @@ a time.
2020
During upgrades, the contents of `/release-manifests` are applied in order, exactly as `ls` would
2121
return on a standard Linux or Unix derivative. The CVO supports the idea of "run levels" by
2222
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.
2726

2827
A few special optimizations are applied above linear ordering - if the CVO sees two different
2928
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"
109108

110109
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:
111110

112-
0000_<runlevel>_<dash-separated_component>-<manifest_filename>
111+
0000_<runlevel>_<dash-separated-component>_<manifest_filename>
113112

114113
For example, the Kube core operators run in runlevel 10-19 and have filenames like
115114

0 commit comments

Comments
 (0)