-
Notifications
You must be signed in to change notification settings - Fork 296
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
HOSTEDCP-1570: remove liveness and readiness probes using metrics endpoint #4001
base: main
Are you sure you want to change the base?
HOSTEDCP-1570: remove liveness and readiness probes using metrics endpoint #4001
Conversation
Hi @jared-hayes-dev. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
/ok-to-test |
@jared-hayes-dev looks good - hate to ask for paperwork, but I think we need a Jira to track this change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@stevekuznetsov Here is Jira, I couldn't find any documentation about how to best create this issue if any changes are needed for the ticket please let me know. |
/retitle HOSTEDCP-1570: remove liveness and readiness probes using metrics endpoint |
@jared-hayes-dev: This pull request references HOSTEDCP-1570 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 bug to target the "4.16.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. |
/jira refresh |
@jeffnowicki: This pull request references HOSTEDCP-1570 which is a valid jira issue. 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. |
ab095af
to
3e19eae
Compare
/test e2e-azure |
1 similar comment
/test e2e-azure |
/lgtm |
/retest |
/test e2e-kubevirt-aws-ovn |
/hold Revision 3e19eae was retested 3 times: holding |
/test e2e-kubevirt-aws-ovn |
3 similar comments
/test e2e-kubevirt-aws-ovn |
/test e2e-kubevirt-aws-ovn |
/test e2e-kubevirt-aws-ovn |
/retest-required |
2 similar comments
/retest-required |
/retest-required |
/test e2e-kubevirt-aws-ovn |
1 similar comment
/test e2e-kubevirt-aws-ovn |
…om ingress and registry operators
3e19eae
to
511ae86
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bryan-cox, jared-hayes-dev, rtheis 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:
Approvers can indicate their approval by writing |
/retest-required |
/remove-hold |
/retest-required |
3 similar comments
/retest-required |
/retest-required |
/retest-required |
@jared-hayes-dev: 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-sigs/prow repository. I understand the commands that are listed here. |
What this PR does / why we need it:
Removes liveness and readiness probes from
cluster-image-registry-operator
andingress-operator
This change was discussed in the project-hypershift slack channel. Should probes be desired, upstream operator teams should introduce health endpoints for their respective components. Hypershift should not rely on metrics endpoint as a stop gap for the probes endpoints.Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist