-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.22
Description of problem:
This is an upstream tracking issue to validate changes in downstream CCM caused by annotation "service.beta.kubernetes.io/aws-load-balancer-type" updates:
Issue: https://github.com/kubernetes/cloud-provider-aws/issues/1254
Fix; https://github.com/kubernetes/cloud-provider-aws/pull/1158 (included in 1.35: https://github.com/kubernetes/cloud-provider-aws/releases/tag/v1.35.0)
Version-Release number of selected component (if applicable):
TBD (tested in 1.34, but looks like it exists on controller for a while)
How reproducible:
always
Steps to Reproduce:
1. Create a Service type loadbalancer CLB (or NLB)
2. Update/add the annotation service.beta.kubernetes.io/aws-load-balancer-type" to NLB (or CLB, different than creation)
3. With the fix, the controller must return an error
Actual results:
A new load balancer is created and the old one is leak
Expected results:
Service not allow to update the load balancer type
Additional info:
Refereces to upstream issue: https://github.com/kubernetes/cloud-provider-aws/issues/1254 Similar issue in ingress: https://issues.redhat.com/browse/OCPBUGS-16728
- depends on
-
OCPCLOUD-3276 Rebase/update to K8s 1.35 for Cloud Provider AWS
-
- To Do
-
- is caused by
-
SPLAT-2486 CCM-AWS upstream bug tracking - <https://github.com/kubernetes/cloud-provider-aws/issues/1254> (leak LB when annotation lb-type updated)
-
- Closed
-
- links to