Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-7731

OLM cleans up Operator workloads

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • openshift-4.8
    • None
    • None
    • None

      Goal: OLM should provide the option to clean up Operator workload, that would otherwise become orphaned.

      Benefit hypothesis: Operator users have a reliable way to cleanly remove resources that have been created on their behalf.

      Why is this important: Today OLM when uninstalling an Operator its CRDs are left intact. That means that workloads are not deleted. Without the Operator around to process deletion events of custom resources it may become hard to cleanly remove deployed resources, especially when it's resource that are outside of the cluster. This is especially important during deletion of the whole cluster it is desired to remove all off-cluster managed resource before the cluster is destroyed.

      Acceptance criteria:

      • OLM can delete Operands upon Operator removal
      • OLM cleans up Operands upon Cluster destruction

            [OCPPLAN-7731] OLM cleans up Operator workloads

            Daniel Messer added a comment -

            amisevskThe default will likely be to not delete the provisioned workloads to reduce the probability of accidental data loss.

            Daniel Messer added a comment - amisevsk The default will likely be to not delete the provisioned workloads to reduce the probability of accidental data loss.

            Angel Misevski (Inactive) added a comment -

            I have a question about how this option will be implemented: the description presents the feature as an option to the user uninstalling the operator. Will this always be an opt-in choice, or will it be possible for the operator to specify that Operator workloads must be removed when uninstalling the operator?

            Angel Misevski (Inactive) added a comment - I have a question about how this option will be implemented: the description presents the feature as an option to the user uninstalling the operator. Will this always be an opt-in choice, or will it be possible for the operator to specify that Operator workloads must be removed when uninstalling the operator?

              Unassigned Unassigned
              DanielMesser Daniel Messer
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: