Issues with Multi-Version Upgrades and ksvc Resource Restoration in Knative

[hzkornel]

Hi,
I'm experiencing challenges with Knative Serving upgrades, I had to upgrade multiple minor versions, which proved complicated, leading me to completely remove Knative Serving and the Operator, as well as all related custom resource definitions (CRDs) from my Kubernetes cluster.

Context

• I am using Knative Serving with the Knative Operator.
• I needed to perform upgrades across multiple minor versions, affecting both the Operator and Serving components.
• To avoid the complexity of incremental version upgrades, I removed all Knative Serving and Operator resources, including all CRDs, from the cluster.
• Attempting to reapply the previously backed-up ksvc resources results in a RevisionMissing status, even though I backed up and reapplied all resources related to ksvcs.

Primary Questions

• Is there a recommended or reasonable workaround for upgrading through multiple minor versions?
• How can I effectively back up and restore ksvc resources? Is there a specific order or dependency that needs to be maintained when reapplying ksvc and it's related resources?
• Can Knative be run with two different versions on the same cluster? For example, can older resources continue using the older Knative version while new resources are deployed on the updated version? My intention is to delete the old version once no resources depend on it.

Any guidance on this would be greatly appreciated! Thank you for your support!

[skonto]

Hi @hzkornel I think this should be opened at the knative/operator side.
cc @houshengbo could you assist here?

Attempting to reapply the previously backed-up ksvc resources results in a RevisionMissing status, even though I backed up and reapplied all resources related to ksvcs.

Pls take a look at #10926

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.