gcr.io transition...

[trent-s]

There may be issues using gcr.io after March 18, 2025, but it looks like it might continue to work for simple image pulls...

• https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr
• https://book.kubebuilder.io/reference/metrics#important-if-you-are-using-kube-rbac-proxy

Currently SusQL Operator uses gcr.io as follows:

• Dockerfile:FROM gcr.io/distroless/static-debian12:nonroot
• config/default/manager_auth_proxy_patch.yaml: image: gcr.io/kubebuilder/kube-rbac-proxy:v0.14.1

[trent-s]

Received the following announcement. Looks like it is just about time to take action on this:

redhat-openshift-ecosystem/community-operators-prod#5625

[trent-s]

Looks like updating operator-sdk from 1.36.1 to 1.38 and applying the migration steps below seems to be a good approach:

https://v1-38-x.sdk.operatorframework.io/docs/upgrading-sdk-version/v1.38.0/