Skip to content
This repository was archived by the owner on Jun 24, 2020. It is now read-only.
This repository was archived by the owner on Jun 24, 2020. It is now read-only.

The operator should probably never delete CRD's #307

@jcrossley3

Description

@jcrossley3

Problem
When the KnativeServing CR is deleted, the operator deletes all the resources in its manifests, including all the *.knative.dev CRD's it originally installed. As long as no instances of the CRD's exist, that's fine. But if they do exist, they will be deleted right along with their associated CRD's; a resource can't exist without its type.

This certainly violates "the principle of least surprise". If the KS is deleted, thereby triggering the removal of knative-serving, I don't think it'll surprise anyone that their *.knative.dev resources will be broken. But I doubt they'd expect them all to be completely obliterated. I think they would expect their ksvcs to work when knative-serving is reinstalled.

Persona:
Any user creating Knative Services

Exit Criteria
Their Knative Services aren't removed when knative-serving is uninstalled.

Time Estimate (optional):
<1 day

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions