Skip to content

Commit

Permalink
CO status controller: Add clusterOperator manifest
Browse files Browse the repository at this point in the history
The payload build process replace "0.0.1-snapshot" in the manifest with the targeted version.
This manifests is then used by the CVO to compare targeted version against the one in the living clusterOperator object.
The controller is responsible for setting the targeted one in the living clusterOperator object during an upgrade.

https://github.com/openshift/cluster-version-operator/blob/ed67bf413cc1765f36c31da22a72950bf9f3b7eb/docs/dev/clusteroperator.md#how-should-i-include-clusteroperator-custom-resource-in-manifests
  • Loading branch information
enxebre committed Apr 24, 2020
1 parent 197ee3a commit 75b34e1
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions manifests/05-clusteroperator.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
name: machine-approver
annotations:
exclude.release.openshift.io/internal-openshift-hosted: "true"
spec: {}
status:
versions:
- name: operator
version: "0.0.1-snapshot"

0 comments on commit 75b34e1

Please sign in to comment.