Managing Operator conditions

As a cluster administrator, you can manage Operator conditions by using Operator Lifecycle Manager (OLM).

Overriding Operator conditions

As a cluster administrator, you might want to ignore a supported Operator condition reported by an Operator. When present, Operator conditions in the Spec.Overrides array override the conditions in the Status.Conditions array, allowing cluster administrators to deal with situations where an Operator is incorrectly reporting a state to Operator Lifecycle Manager (OLM).

For example, consider a known version of an Operator that always communicates that it is not upgradeable. In this instance, you might want to upgrade the Operator despite the Operator communicating that it is not upgradeable. This could be accomplished by overriding the Operator condition by adding the condition type and status to the Spec.Overrides array in the OperatorCondition resource.

Prerequisites

  • An Operator with an OperatorCondition resource, installed using OLM.

Procedure

  1. Edit the OperatorCondition resource for the Operator:

    1. $ oc edit operatorcondition <name>

  2. Add a Spec.Overrides array to the object:

    Example Operator condition override

    1. apiVersion: operators.coreos.com/v1
    2. kind: OperatorCondition
    3. metadata:
    4.   name: my-operator
    5.   namespace: operators
    6. spec:
    7.   overrides:
    8.   - type: Upgradeable (1)
    9.     status: "True"
    10.     reason: "upgradeIsSafe"
    11.     message: "This is a known issue with the Operator where it always reports that it cannot be upgraded."
    12. status:
    13.   conditions:
    14.   - type: Upgradeable
    15.     status: "False"
    16.     reason: "migration"
    17.     message: "The operator is performing a migration."
    18.     lastTransitionTime: "2020-08-24T23:15:55Z"
    1Allows the cluster administrator to change the upgrade readiness to True.

Updating your Operator to use Operator conditions

Operator Lifecycle Manager (OLM) automatically creates an OperatorCondition resource for each ClusterServiceVersion resource that it reconciles. All service accounts in the CSV are granted the RBAC to interact with the OperatorCondition owned by the Operator.

An Operator author can develop their Operator to use the operator-lib library such that, after the Operator has been deployed by OLM, it can set its own conditions. For more on writing logic to set Operator conditions as an Operator author, see the Operator SDK documentation.

Setting defaults

In an effort to remain backwards compatible, OLM treats the absence of an OperatorCondition resource as opting out of the condition. Therefore, an Operator that opts in to using Operator conditions should set default conditions before the ready probe for the pod is set to true. This provides the Operator with a grace period to update the condition to the correct state.

Additional resources