-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
[Cluster Infrastructure] Trace non-feature testing work/e2e failures/ci issues
-
Quality / Stability / Reliability
-
75% To Do, 25% In Progress, 0% Done
-
False
-
-
False
-
None
-
None
-
None
I want to use this to trace some testing works not related to epic features to increase our coverage and improve the rate of QE bug reporting.
Here are some things that come to mind right now.
- Add new CCM cases, some cases can be run in rosa/aro/osd
- For the old bugs: bug analysis https://docs.google.com/spreadsheets/d/15ypnAjHqmOa8-nxtJLBejftHBGue6IW739i8I36GVrA/edit#gid=0 Done
- For the new bugs: add cases if needed once verified
- Basic cases of creating service, type is LoadBalancer
- Add cases for all kinks of annotations
- aws https://github.com/openshift/cloud-provider-aws/blob/master/docs/service_controller.md
- https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/service/annotations/
- gcp https://github.com/openshift/cloud-provider-gcp/blob/master/providers/gce/gce_annotations.go
- azure https://cloud-provider-azure.sigs.k8s.io/topics/loadbalancer/
CAPI regression testingRun all the features mapi supported and raised bugs for capi not supportedResearch the upstream features capi supported but mapi doesn't support and check if also works well on ocp, if yes, we need to raise bug to hide it.
Doc review