Skip to content

Conversation

@andfasano
Copy link
Contributor

It looks like that a small portion of the documentation was not yet updated due the changes introduced in #318. Thanks @sdodson for pointing it out

@sdodson
Copy link
Member

sdodson commented Oct 30, 2020

/approve
/lgtm

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, sdodson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 30, 2020
@sdodson
Copy link
Member

sdodson commented Oct 30, 2020

docs only, don't waste CI cycles on this

@sdodson sdodson merged commit 3c62269 into openshift:master Oct 30, 2020
wking added a commit to wking/cluster-version-operator that referenced this pull request Oct 31, 2020
This snuck in with be09d1e (Doc fix for cluster operator creation
step, 2020-10-30, openshift#478).

Re: "or recreate if deleted", the CVO (if it is running) will
eventually get around to recreating the ClusterOperator, as described
in the text added in be09d1e.  But it's still the operator's job to
recreate it if the ClusterOperator is missing, as part of the
"properly update" responsibility.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants