Skip to content

v1.2.0

Choose a tag to compare

@sk9-devops sk9-devops released this 14 Aug 16:04
· 5 commits to main since this release
b42c5b4

Highlights

v1.2.0 adds ALB IngressGroup-based maintenance targeting for AWS Load Balancer Controller users. You can now put an entire ALB IngressGroup into maintenance with spec.albGroupName, while direct Ingress-name targeting through spec.targetIngress remains supported for users who want to target one existing Ingress.

Added

  • Added ALB IngressGroup maintenance targeting with spec.albGroupName.
  • Added generated maintenance Ingress overlays that join the requested ALB IngressGroup with alb.ingress.kubernetes.io/group.order: "-1000".
  • Added listener-port discovery from same-namespace ALB IngressGroup members, including HTTPS listener support when group members declare HTTPS listener ports.
  • Added namespace-scoped and global-scoped documentation updates for the new targeting model.
  • Added direct Ingress-name samples for enable, disable, and scheduled maintenance.

Changed

  • Updated README and configuration docs to present two supported targeting options: ALB IngressGroup name or Ingress name.
  • Updated samples to make ALB IngressGroup targeting the default AWS ALB path.
  • Updated generated install manifests and Kustomize release references for v1.2.0.
  • Clarified that ALB IngressGroup targeting does not mutate or back up existing application Ingresses.

Security

  • Included the approved high-priority Dependabot update for github.com/google/cel-go from v0.26.0 to v0.29.0.

Upgrade Notes

No breaking API changes are included. Existing spec.targetIngress resources continue to work. For AWS Load Balancer Controller users, prefer spec.albGroupName when the operational boundary is the ALB IngressGroup.

Pinned install:

kubectl apply -f https://raw.githubusercontent.com/k8s-operators-devops/app-maintenance-operator/v1.2.0/deploy/install.yaml

Namespace-scoped install:

kubectl apply -k https://github.com/k8s-operators-devops/app-maintenance-operator/config/namespaced?ref=v1.2.0

Operational Notes

  • The v1.2.0 image is published to GHCR as ghcr.io/k8s-operators-devops/app-maintenance-operator:v1.2.0.
  • The image publish workflow builds linux/amd64 and linux/arm64 images.
  • Always pin production installs to immutable release tags instead of tracking :latest.

Known Limitations

  • Only AWS ALB fixed-response mode is currently supported.
  • Fixed-response HTML must stay within the AWS ALB 1024-byte body limit.
  • CRDs remain cluster-scoped Kubernetes resources, even when the manager runs with namespace-scoped watch/RBAC.
  • Central platform-team control across multiple application namespaces remains future roadmap work.

Full Changelog: v1.1.1...v1.2.0