2.2.3.3. Known issues
- LeaderWorkerSet pods update sequentially by default
If you have integrated Leader Worker Set Operator with your Red Hat build of Kueue installation and you are using the rollout strategy option for updating LeaderWorkerSet pods, be aware that the
MaxUnavailablefeature gate in OpenShift Container Platform is disabled by default.When any change is made to LeaderWorkerSet pods, a rolling update is triggered. This action gradually replaces the old pods of a deployment with new ones, keeping as many pods alive as possible to avoid downtime. If
MaxUnavailableis disabled, which is the OpenShift Container Platform default setting, the pods are updated one at a time.If you want to run updates in parallel instead of running them sequentially,
MaxUnavailablefeature gate must be enabled. For more information, see Enabling feature sets at installation and Rollout Strategy.