🌱Added WatchDeploymentLogsByLabelSelector function

[adilGhaffarDev]

What this PR does / why we need it:
Adds WatchDeploymentLogsByLabelSelector function. Now we can call a function in e2e tests to stream logs of deployments, selected by a label selector, for not requiring to know the exact name of the deployment in the test implementation.

Which issue(s) this PR fixes(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)*:
Fixes #6965

[k8s-ci-robot]

@adilGhaffarDev: This issue is currently awaiting triage.

If CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Hi @adilGhaffarDev. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[killianmuldoon]

Looks like a very good idea!

/ok-to-test

[adilGhaffarDev]

/retest

[chrischdi]

Some further improvement recommendations:-)

[fabriziopandini]

Change lgtm to me.
Please resolve pending comment above and also add a note about this change in https://main.cluster-api.sigs.k8s.io/developer/providers/v1.3-to-v1.4.html#api-changes (we are renaming a public func that providers might be using in their test)

[adilGhaffarDev]

Please resolve pending comment above and also add a note about this change in https://main.cluster-api.sigs.k8s.io/developer/providers/v1.3-to-v1.4.html#api-changes (we are renaming a public func that providers might be using in their test)

Should I create a separate PR for notes or just add it to this PR.

[sbueringer]

@adilGhaffarDev Please add them to this PR

[adilGhaffarDev]

/test pull-cluster-api-test-main

[sbueringer]

Found two other ones. Apart from that it should be really fine now (I also verified the resulting log folder structure and it looks good)

[sbueringer]

/retest

[sbueringer]

Thank you very much!

/lgtm

I'll merge through after the tests.

Not sure why they weren't triggered. Some GitHub or Prow issue I assume.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2388aa10023fffcacbb32d77a2ee85ecbf6c8859

[sbueringer]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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:

• OWNERS [sbueringer]

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