Loading...

XML

Word

Printable

Regression:
No
Story Points:
2
Sprint:
uShift Sprint 250, uShift Sprint 251, uShift Sprint 252
sprint_count:
3
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
Previously, the MicroShift load balancer controller tried to update the IP addresses of every `LoadBalancer` service in the cluster. Some of these services, like the ones having a defined `loadBalancerClass`, have their own update procedures for external IPs. This conflicted with the MicroShift controller. Now, MicroShift filters services that have a `loadBalancerClass` and does not attempt to update IP addresses owned by other load balancer services.

Show
Previously, the MicroShift load balancer controller tried to update the IP addresses of every `LoadBalancer` service in the cluster. Some of these services, like the ones having a defined `loadBalancerClass`, have their own update procedures for external IPs. This conflicted with the MicroShift controller. Now, MicroShift filters services that have a `loadBalancerClass` and does not attempt to update IP addresses owned by other load balancer services.
Release Note Type:
Bug Fix
Release Note Status:
Done
Documentation Type:

Release Notes
Target Version:

4.16.0
Target Backport Versions:

4.16.0

Description of problem:

    The load balancer controller in MicroShift tries to process all Service Cos, even those owned by another load balancer implementation.

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

    4.16

How reproducible:

    Always

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

links to

RHSA-2024:0043 OpenShift Container Platform 4.16.z security update