[FEATURE] Run Version Migration Job on Upgrade

[adambkaplan]

Is there an existing feature request for this?

• I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

In shipwright-io/build#1603, a version migration script was added to the install/upgrade instructions. This script launches a kubernetes Job that ensures all existing Shipwright Build objects use the v1beta1 API.

Describe the solution that you would like.

The operator should implement the script's logic within a controller. It should do the following:

• (optional) Determine if this is a new installation, or an upgrade.
• On upgrade (or always?), start the Job to initiate the migration
• Reconcile and report status of the version migration Job.

Describe alternatives you have considered.

Keep as "manual instructions" when upgrading. This is not desired for an operator.

Anything else?

Question regarding the migration job - is this idempotent? Will it always succeed, even if there are no objects to update?

[adambkaplan]

Moving to 0.15.0 - this won't make the 0.14 release.

[adambkaplan]

Kubernetes has two related projects with APIs that solve the problem for us:

1. Kubernetes-sigs storage version migrator. Some kubernetes distros like OpenShift come packaged with this (I think)
2. The StorageVersionMigrator feature gate - alpha in k8s 1.30: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/storage-version-migration/

[adambkaplan]

From refinement - we will "codify" the approach in shipwright-io/build#1603, utilizing the knative storage migrator. This ensures we don't rely on external dependencies or alpha Kubernetes features.

Once StorageVersionMigrator reaches beta, we can consider removing this job for future CRD version migrations (and switch to the Kubernetes-native solution)

[adambkaplan]

Moving to release-v0.16.0 - no progress has been made on this for v0.15.0, and adding this puts the release at risk of missing the deadline.