-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
3
-
None
-
None
-
NI&D Sprint 283
Followup on NE-2374
Given the behavior of annotation replication is being tested, we now want to add a specific platform test for internal loadbalancer provisioning.
- Given a cloud platform (AWS, GCP, etc)
- And given the annotations of these platforms to provision an internal LoadBalancer (https://github.com/openshift/cluster-ingress-operator/blob/56e29778bc2168c324e55ddecd2d838a3ea287bf/pkg/operator/controller/ingress/load_balancer_service.go#L147)
- Execute a test on these platforms that will:
- Create a Gateway with the proper annotations on infrastructure.annotations to provision an internal LoadBalancer
- Verify that the provisioned Gateway uses internal identification per cloud platform (eg.: On AWS they have the name internal-*, on GCP they may have a private IP address, etc)
- (optional) Execute connectivity test, if build cluster can reach the LoadBalancer IP
[From Miciah] It is kind of like the "TestInternalLoadBalancer" test in cluster-ingress-operator, except the test needs to specify the annotation in `Gateway.spec.infrastructure.annotation` in addition to checking for it on the service: https://github.com/openshift/cluster-ingress-operator/blob/1ea51fcc3ce39c6f8a2e2c74921fc1584478b0f5/test/e2e/operator_test.go#L1179-L1267`