CNF-14833: E2E: metrics exposed securely

[rbaturov]

This is a follow-up PR for #1106 and #1107, adding e2e tests to test their functionality.
The tests verify that secured metrics fetching can be established, for both the manager pod and rte workers.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@rbaturov: This pull request references CNF-14833 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

This is a follow-up PR for #1007 and #1035, adding e2e tests to test their functionality.
The tests verify that secured metrics fetching can be established using kube-rbac-proxy, for both the manager pod and rte workers.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rbaturov: This pull request references CNF-14833 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

This is a follow-up PR for #1106 and #1107, adding e2e tests to test their functionality.
The tests verify that secured metrics fetching can be established using kube-rbac-proxy, for both the manager pod and rte workers.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rbaturov: This pull request references CNF-14833 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

This is a follow-up PR for #1106 and #1107, adding e2e tests to test their functionality.
The tests verify that secured metrics fetching can be established, for both the manager pod and rte workers.

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 openshift-eng/jira-lifecycle-plugin repository.

[rbaturov]

/retest-required

[Tal-or]

@rbaturov are those tests running as part of u/s CI?

[rbaturov]

@rbaturov are those tests running as part of u/s CI?

Yes, they should as they are part of the serial e2e suite

[Tal-or]

@rbaturov are those tests running as part of u/s CI?

Yes, they should as they are part of the serial e2e suite

The serial suite is not running u/s

don't you prefer these tests will run as part of ci-e2e?

[rbaturov]

@rbaturov are those tests running as part of u/s CI?

Yes, they should as they are part of the serial e2e suite

The serial suite is not running u/s

don't you prefer these tests will run as part of ci-e2e?

I'm not sure what the purpose of each of them is. I was just following @ffromani request.
Is the difference that the serial suite includes more intensive and broader coverage?

[rbaturov]

@ffromani Waiting for your review when you have time

[ffromani]

LGTM, only some minor nits, please address and we will merge

[rbaturov]

@ffromani This has not been tested in d/s. Maybe we should do a pre-merge test?

[ffromani]

/approve

yes let's do a pre-merge testing please

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, rbaturov

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 [ffromani]

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

[ffromani]

/hold

for pre-merge testing

[ffromani]

/lgtm

[rbaturov]

/hold

for pre-merge testing

@rshemtov13 will handle this

[rshemtov13]

I've tested both test cases in the d/s CI and both passed

[ffromani]

/unhold

ok, thanks! let's move on

[rbaturov]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@rbaturov: new pull request created: #1150

In response to this:

/cherry-pick release-4.18

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-sigs/prow repository.