v1.0.0
v1.0.0
First stable release of app-maintenance-operator, a Kubernetes operator for application maintenance mode on AWS Load Balancer Controller ALB IngressGroups.
This is application traffic maintenance, not node maintenance. The operator creates a temporary higher-priority ALB IngressGroup overlay and leaves the original application Ingress unchanged.
Install
Pinned install from this release tag:
kubectl apply -f https://raw.githubusercontent.com/k8s-operators-devops/app-maintenance-operator/v1.0.0/deploy/install.yamlOr download the attached release asset:
kubectl apply -f app-maintenance-operator-v1.0.0-install.yamlContainer Image
ghcr.io/k8s-operators-devops/app-maintenance-operator:v1.0.0
The release workflow also publishes the latest convenience tag.
Runtime Names
- Namespace:
alb-maintenance-operator - Deployment:
alb-maintenance - ServiceAccount:
alb-maintenance - Metrics Service:
alb-maintenance-metrics
The operator pod includes:
app.kubernetes.io/version: v1.0.0OPERATOR_VERSION=v1.0.0
API Highlights
spec.maintenanceModeis the master switch.maintenanceMode: falseor omitted disables maintenance and ignoresschedule.maintenanceMode: trueenables maintenance immediately unlessschedulenarrows the window.schedule.startandschedule.enduse RFC3339 timestamps, includingZor explicit timezone offsets.
Attached Assets
app-maintenance-operator-v1.0.0-install.yaml- complete install manifestmaintenance-enable.yaml- sample immediate maintenance CRmaintenance-disable.yaml- sample disable CRmaintenance-scheduled.yaml- sample scheduled maintenance CRSHA256SUMS- checksums for attached YAML assets
Verify
kubectl get pods -n alb-maintenance-operator
kubectl logs -n alb-maintenance-operator deployment/alb-maintenance -c manager
kubectl get crd maintenances.k8smaintenance.ioNotes
The target Ingress must be AWS ALB-managed and must define alb.ingress.kubernetes.io/group.name. The Maintenance resource must be created in the same namespace as the target application Ingress.