pin_upstream_images

To pin upstream multigres image tags, you run a script-driven digest lookup that maps main SHAs to sha-* tags and automatically updates image_defaults.go. This aligns DefaultPostgresImage, DefaultMultiAdminImage, and other operator images with the release SHA.

Comparing upstream multigres changes between the current and new SHA highlights breaking changes and new features before pinning image tags. This informs release decisions and ensures the updated sha-* tags in image_defaults.go reflect stable, validated deployment behavior.

Automating multigres image tag consistency involves running fetch_latest_tags.py to identify the latest sha-* tags and update image_defaults.go. This script-driven approach maps operator release SHAs to the correct image tags for all default deployment images.

Updating multigres image constants requires modifying DefaultPostgresImage, DefaultMultiAdminImage, DefaultMultiAdminWebImage, DefaultMultiOrchImage, DefaultMultiPoolerImage, and DefaultMultiGatewayImage in api/v1alpha1/image_defaults.go to reflect the pinned sha-* tags.

You need to pin multigres image tags to a specific SHA during release preparation workflows, cross-version upgrades, and validation of image tag consistency. This ensures deployment behavior remains stable and reproducible across different operator releases.

Pinning upstream images does not require manual edits because the process automates updates to api/v1alpha1/image_defaults.go. The script performs a digest lookup, maps main SHAs to sha-* tags, and applies the changes directly to the file.