-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CNF-14833: E2E: metrics exposed securely #1037
base: main
Are you sure you want to change the base?
Conversation
Skipping CI for Draft Pull Request. |
7422d1d
to
d0beb3b
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rbaturov The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Added two test to verify that secured metrics fetching can be established using kube-rbac-proxy, for both the manager pod and rte workers. Signed-off-by: Ronny Baturov <[email protected]>
d0beb3b
to
9f47d67
Compare
@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:
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: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
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.