🌱 Debug deployment coordinator e2e

[davidfestal]

Summary

Add a check in the Deployment Coordinator e2e test, that will try to list deployment, to validate they are correctly exposed by the root compute APIExport URL, before starting the deployment coordinator.

Related issue(s)

This should help debugging the flake recorded in issue #2501

[davidfestal]

This check is useful because of the following messages found several times in failing test runs:

deployment-coordinator: W0105 15:26:29.720029   13015 reflector.go:324] k8s.io/client-go@v0.0.0-20221221132345-4bcc0e78af51/tools/cache/reflector.go:167: failed to list *v1.Deployment: the server could not find the requested resource (get deployments.apps)
deployment-coordinator: E0105 15:26:29.720089   13015 reflector.go:138] k8s.io/client-go@v0.0.0-20221221132345-4bcc0e78af51/tools/cache/reflector.go:167: Failed to watch *v1.Deployment: failed to list *v1.Deployment: the server could not find the requested resource (get deployments.apps)
deployment-coordinator: W0105 15:26:30.733178   13015 reflector.go:324] k8s.io/client-go@v0.0.0-20221221132345-4bcc0e78af51/tools/cache/reflector.go:167: failed to list *v1.Deployment: the server could not find the requested resource (get deployments.apps)

[vincepri]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncdc, vincepri

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/OWNERS [ncdc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment