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 was archived by the owner on Jun 24, 2020. It is now read-only.
Problem
This issue applies to eventing-operator as well. If knative has experienced some significant changes, which can lead to key resource deletion, but it has not released this version yet, how can operator catch the latest change and implement based this change in time?
For example, eventing dropped sources-controller knative/eventing#2448, we know we need to add logic removing the sources-controller deployment in the reconcile loop, but how can we pull the latest manifest and test with operator code? I do not think we should wait until the next version is released for operator development and test.
Problem
This issue applies to eventing-operator as well. If knative has experienced some significant changes, which can lead to key resource deletion, but it has not released this version yet, how can operator catch the latest change and implement based this change in time?
For example, eventing dropped sources-controller knative/eventing#2448, we know we need to add logic removing the sources-controller deployment in the reconcile loop, but how can we pull the latest manifest and test with operator code? I do not think we should wait until the next version is released for operator development and test.
Persona:
Developers
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
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.