You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
Problem
The function named deleteObsoleteResources can delete the resources by verifying if the the value matches the operand's version for the label eventing.knative.dev/release.
Instead of deleting the obsolete resource on a release basis. Let's make it more general and intelligent.
Exit Criteria
Tests can be added to confirm that the resources have the label eventing.knative.dev/release, and the value matches the current operand version.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered:
This is a possible option; one challenge (which may not be too much of a problem here) is that it's hard to perform a label search across multiple Kinds.
For the operator case, this seems feasible by maintaining a list of all Kinds which have been previously used by Knative, which (ignoring downstream packaging) should allow finding the complete set of previous resources.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
The function named
deleteObsoleteResources
can delete the resources by verifying if the the value matches the operand's version for the labeleventing.knative.dev/release
.Instead of deleting the obsolete resource on a release basis. Let's make it more general and intelligent.
Persona:
This is for regular users of operator.
Exit Criteria
Tests can be added to confirm that the resources have the label
eventing.knative.dev/release
, and the value matches the current operand version.Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: