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
Bug 1822720: Configure TLS for OVN metrics endpoints #581
Bug 1822720: Configure TLS for OVN metrics endpoints #581
Conversation
3188da5
to
68e7b15
Compare
68e7b15
to
e5fa853
Compare
We may need to undo this too -- openshift/origin#24853 |
e5fa853
to
d5241bc
Compare
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retitle Bug 1822720: Configure TLS for OVN metrics endpoints |
@juanluisvaladas: This pull request references Bugzilla bug 1822720, which is invalid:
Comment 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 kubernetes/test-infra repository. |
/bugzilla refresh |
@dcbw: This pull request references Bugzilla bug 1822720, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
/retest None of these seem related to the patch. |
Actually they are, see https://github.com/openshift/cluster-network-operator/pull/583/files#diff-8bba3a1a9729e2d9c47dcb736aded81dR48 and https://github.com/openshift/cluster-network-operator/pull/583/files#diff-87698f12b12a4457428207bf20f52393R75 |
/retest Please review the full test history for this PR and help us cut down flakes. |
18 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@juanluisvaladas: The following tests 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/test-infra repository. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@juanluisvaladas: Some pull requests linked via external trackers have merged: . The following pull requests linked via external trackers have not merged:
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 kubernetes/test-infra repository. |
Following the change in PR openshift#581 the job name should be renamed to "ovnkube-master-metrics" Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com>
Following the change in PR openshift#581 the job name should be renamed to "ovnkube-master-metrics". Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com>
Following the change in PR openshift#581 the labels in the servicemonitor should be renamed to "ovnkube-master". Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com>
Following the change in PR openshift#581 the job name in the alert rule should be renamed to "ovnkube-master-metrics". Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com>
/bugzilla refresh |
@juanluisvaladas: All pull requests linked via external trackers have merged: openshift/cluster-network-operator#581. Bugzilla bug 1822720 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
This is a quick workaround for getting OVN metrics using TLS to unblock us...
I will modify OVN kubernetes to be capable to expose HTTPS directly in the near future.
https://issues.redhat.com/browse/SDN-912