Loading...

XML

Word

Printable

Severity:
Moderate
Regression:
No
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
Previously on Hypershift clusters, pods were not always being scheduled on separate zones. With this update, the `multus-admission-controller` deployment now uses a `PodAntiAffinity` spec for Hypershift to operate in the proper zone. (link:https://issues.redhat.com/browse/OCPBUGS-15220[*~~OCPBUGS-15220~~*])

Show
Previously on Hypershift clusters, pods were not always being scheduled on separate zones. With this update, the `multus-admission-controller` deployment now uses a `PodAntiAffinity` spec for Hypershift to operate in the proper zone. (link: https://issues.redhat.com/browse/OCPBUGS-15220 [* OCPBUGS-15220 *])
Release Note Type:
Enhancement
Release Note Status:
In Progress
Target Version:

4.15.0

Description of problem:

To ensure pods run in separate zone for a hypershift cluster, a PodAntiAffinity spec should be provided.

Version-Release number of selected component (if applicable):

4.12, 4.13, 4.14

How reproducible:

Always

Steps to Reproduce:

1. Create a hypershift control plane in ha mode.
2. Observe the multus admission controller pods.
3.

Actual results:

Not all pods scheduled on separate zones.

Expected results:

Pods scheduled on separate zones.

Additional info:

links to