-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Nginx Plus Load Balancers to Ubuntu Jammy #5670
Labels
Operations
pulls issues into the Operations ZenHub board
Comments
I think we can safely decommission the old hardware now. |
Working on decommissioning the servers:
Grant access to both Out of Band VMs to allow iDrac interaction.
|
Both servers have been powered down and the disks will be formated in two weeks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This ticket outlines the plan to upgrade our two Nginx Plus load balancers (lib-adc1 and lib-adc2) from Ubuntu Focal (20.04) to Ubuntu Jammy (22.04) with zero downtime.
Background:
Ubuntu Focal is nearing its end of life. Upgrading to Jammy will provide security updates and new features.
Nginx Plus is critical for our infrastructure, so the upgrade must be performed with zero downtime.
Goals:
Upgrade both lib-adc1 and lib-adc2 to Ubuntu Jammy.
Maintain high availability throughout the upgrade process.
Minimize any disruption to services.
Runbook details
We will use a blue-green deployment strategy to ensure zero downtime:
Provision new servers: Spin up two new servers (adc-prod1 and adc-prod2) with Ubuntu Jammy and the latest version of Nginx Plus.
Configure new load balancers: Replicate the configuration from lib-adc1 and lib-adc2 to adc-prod1 and adc-prod2, ensuring all settings, certificates, and configurations are identical.
Test new load balancers: Thoroughly test adc-prod1 and adc-prod2 to ensure they function correctly and handle traffic as expected.
Redirect traffic to new load balancers: Gradually redirect traffic from lib-adc1 and lib-adc2 to adc-prod1 and adc-prod2. This will be done using DNS changes, VRRP and keepalived in front of the load balancers.
Monitor: Closely monitor the new load balancers for any issues during the traffic transition.
Decommission old load balancers:
Once traffic is fully migrated and the new load balancers are stable, decommission lib-adc1 and lib-adc2.
Rollback Plan:
In case of any issues during the upgrade, we will immediately redirect traffic back to the original load balancers (lib-adc1 and lib-adc2).
Tasks:
The text was updated successfully, but these errors were encountered: