This section explains the steps for minor upgrade of a container image.
Before upgrading each container version, please refer to "Chapter 3 Operator Installation" to update your operators. Also, please refer to RedHat's ecosystem catalog for updated information on each container.
You can upgrade the container image by changing the parameters of the FEPCluster custom resource.
Parameter | Description |
|---|---|
spec.fep.image.image | Update the FEP container image. |
spec.fepChildCrVal.backup.image.image | Update the backup container image. |
spec.fep.feputils.image | Update the container image responsible for cloud secret management feature. |
spec.fep.remoteLogging.image | Update the container image that handles the Log Collection feature. |
After changing the custom resource parameters, if you have multiple FEPPods, restart the Pods one by one from the replica server to upgrade the container image. Once all replica servers are upgraded, one of them will be promoted to master server. The old master server's Pods are then restarted and the container images are upgraded.
These rolling upgrades allow you to upgrade all container images with minimal disruption to your business.
Note
The upgrade process will cause an outage on the cluster for the duration to upgrade both Master and Sync Replica. If there is no Sync Replica in the cluster, the outage is limited to the length of time to upgrade the Master (or actually the failover time required to take another replica been promoted by patroni).
