Open RunningJon opened 3 years ago
@RunningJon Can you check with our current customer base on how often this use case has come up?
I saw it become a more common request from enterprise customers. When working with Greenplum, it was a requirement to repave monthly. I've heard many customers say that "yum update" is not an acceptable way to patch. They want to deploy the patched VM with a new image instead.
I will take this and #7466 to research. We need some mechanism to update OS for the cloud.
Enterprise customers often use a standard AMI/Image for all VMs in their environment and periodically apply patches to all VMs by replacing VMs with a new AMI. It is common for these customers to explicitly not allow
yum update
and instead replace VMs.Replacing VMs with a new AMI is tedious process in each cloud provider and if performed incorrectly, it could lead to data loss.
Additionally, software installed on the root volume like the Yugabyte binaries, will need to be installed in the new VM.
Automate this process in Platform so that a customer can pick a new AMI/Image they have perform a rolling restart/patch.
For each node: