Dave Protasowski
Dave Protasowski
Still flaky - another run https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_serving/15400/unit-tests_serving_main/1815342425837670400
> Is there any reason why we don't allow the resources to adopt the orphaned child resources? It seems Kubernetes does this for the native resources We specifically have these...
> The corresponding flag to be used with the 'velero backup' command is '--include-resources service.serving.knative.dev'. This will only work to restore the 'latest' revision. If you have a Knative Service...
I was fooling around with a backup poc tool that does owner reference restoration. https://github.com/dprotaso/knative-backup-poc I notice when restoring the configuration the generation gets reset and the knative controllers don't...
Closing this out as the question has been answered.
/unassign @asr2003 the issue is already assigned to @NightFury742
@NightFury742 can you comment if you're still working on this issue?
/unassign @NightFury742 /assign @EraKin575