Skip to content

v0.1.1

Choose a tag to compare

View all tags
@case-88 case-88 released this 04 Jul 02:40
v0.1.1
efeae3b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

  • Operators now claim each PgBouncerAurora CR before running discovery, monitor, metadata refresh, status updates, or child-resource writes.
  • Removed spec.topologyPolicy.writerChangeConnectionHandling; Writer changes now always roll the old/new Writer PgBouncer Deployments through role-based Pod template labels.
  • Reader fallback now uses fresh confirmed Reader health, so preserved or missing Readers do not block Writer fallback when no Reader is confirmed.
  • Reader Service traffic membership now follows monitor health thresholds. Confirmed unhealthy Readers are removed from the Reader Service even if topology still reports them as Readers.
  • Role labels no longer revive Reader traffic membership by themselves.
  • PgBouncer Pods now render terminationGracePeriodSeconds with a default of 30 seconds.
  • Monitor unhealthy observations are logged as state changes instead of repeated error stack traces when cached health is carried.

Image

  • quay.io/case-88/pgbouncer-aurora-operator:v0.1.1
  • Multi-arch digest: sha256:d485005af4489c42d953d3ee392634594c7123e2702e4099d5b10147012f8252
  • Platforms: linux/amd64, linux/arm64

Helm

The v0.1.1 charts were already published on the Quay OCI chart registry:

  • oci://quay.io/case-88/charts/pgbouncer-aurora-crds --version 0.1.1
  • oci://quay.io/case-88/charts/pgbouncer-aurora-operator --version 0.1.1
  • oci://quay.io/case-88/charts/pgbouncer-aurora --version 0.1.1

Migration Notes

  • Remove spec.topologyPolicy.writerChangeConnectionHandling from existing manifests. Strict validation or GitOps pipelines can reject the removed field.
  • Review readerEmptyFallback.enabled and application Reader target settings. In two-member Aurora clusters, Reader clients that use role checks should usually use preferSecondary or any targets when fallback is enabled.
  • Use at least two PgBouncer replicas per Aurora instance for production rollouts.
  • Review PgBouncer rollout drain expectations before lowering spec.pgbouncer.terminationGracePeriodSeconds.

Validation

  • go test ./...
  • helm lint charts/pgbouncer-aurora-crds charts/pgbouncer-aurora-operator charts/pgbouncer-aurora
  • helm template for CRD, operator, and CR charts
  • Quay image manifest inspection for v0.1.1
Assets 2
Loading