docs/dev/operators: Drop docs for the CVO approach #733
Conversation
That approach should be documented in the CVO itself, since it's not installer-specific and moving it gets the docs and implementation for that approach into the same repository. I've filed [1] to land dynamic-object docs in the CVO repo (based on some of the content I'm removing here). Naming files, etc. are already covered by the existing CVO documentation. [1]: openshift/cluster-version-operator#59
openshift-ci-robot
added
size/M
|
CVO is a consumer for the update payload and doesn't drive these. So these cannot exist in CVO. I would keep them in installer as people come to installer to ask how do I install my operator?. |
Who does drive these? If a new release image rolls out, someone will be reading and pushing its manifests into existing clusters, and that won't be the installer. With this PR and openshift/cluster-version-operator#59, all the "usual way" docs are collected in one place. If that place should be some third location (not the installer, and maybe not the CVO either?), point me at it and I'll move the "usual way" docs there.
I'm still prominently linking the CVO docs, so folks who come here first and then realize the don't need instal;er coupling can find the "usual way" docs. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rajatchopra, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
5 participants
That approach should be documented in the CVO itself, since it's not installer-specific and moving it gets the docs and implementation for that approach into the same repository. I've filed openshift/cluster-version-operator#59 to land dynamic-object docs in the CVO repo (based on some of the content I'm removing here). Naming files, etc. are already covered by the existing CVO documentation.
CC @rajatchopra, since this is a follow-up to #377 and openshift/cluster-version-operator#34.