Introduce OperatorConditions doc #83
Conversation
|
|
||
| ## OperatorConditions | ||
|
|
||
| OLM introduced a new [CustomResourceDefinition](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) called the [OperatorCondition](https://github.com/operator-framework/api/blob/master/crds/operators.coreos.com_operatorconditions.yaml) allowing operators to communicate conditions to OLM. There are a set of "OLM Supported Conditions" which influence OLM's management of the operator when present in the OperatorCondition's [Status.Conditions](https://github.com/operator-framework/api/blob/b55a341f6560db4adec39d69aab1ff3092ea202a/pkg/operators/v1/operatorcondition_types.go#L22) array. |
There was a problem hiding this comment.
We should probably include the CRD here instead of pointing to the codebase.
There was a problem hiding this comment.
nit: There are a set of "OLM Supported Conditions": did you mean for the OLM Supported Conditions to be in bold?
There was a problem hiding this comment.
nit: There are a set of "OLM Supported Conditions": did you mean for the OLM Supported Conditions to be in bold?
No, I'm using it as a term to refer to a subset of conditions
There was a problem hiding this comment.
We should probably include the CRD here instead of pointing to the codebase.
Done.
awgreene
force-pushed
the
operator-conditions
branch
from
4498095 to
f1cde2e
Compare
|
/lgtm |
|
I don't see the doc here: https://deploy-preview-83--operator-lifecycle-manager.netlify.app/docs/advanced-tasks/ or here: https://olm.operatorframework.io/docs/advanced-tasks/ |
|
|
||
| ```yaml | ||
| apiVersion: operators.coreos.com/v1 | ||
| kind: Condition |
There was a problem hiding this comment.
the operatorcondition?
|
/QE-approved |
No description provided.