Skip to content
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

Add liveness/readiness probes #79

Merged

Conversation

Danil-Grigorev
Copy link

@Danil-Grigorev Danil-Grigorev commented Jun 19, 2020

  • Introducing simple readiness probes for controller-runtime, checking the manager container could respond to HTTP requests.

Depends on openshift/machine-api-operator#602
Close #78

@enxebre
Copy link
Member

enxebre commented Jun 19, 2020

/lgtm
needs to merge this to not be broken by openshift/machine-api-operator#602 (comment)

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 19, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 19, 2020
@dhellmann
Copy link

/test e2e-metal-ipi

@Danil-Grigorev
Copy link
Author

/retest

@@ -106,6 +109,14 @@ func main() {
os.Exit(1)
}

if err := mgr.AddReadyzCheck("ping", healthz.Ping); err != nil {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like these health and readiness checks will always return "ready" or "healthy". They don't actually check anything, other than verifying that the process can respond to an HTTP request. Is that the intent? It would be a good idea to document the criteria either way, both in the commit message, and also in the README or similar documentation.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@mhrivnak
Copy link
Member

/hold

Would like to get thoughts on my doc request.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 19, 2020
@openshift-ci-robot openshift-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed lgtm Indicates that a PR is ready to be merged. labels Jun 23, 2020
@Danil-Grigorev
Copy link
Author

@mhrivnak I added a small doc file to the PR. This is the intent for probes right now.

@Danil-Grigorev Danil-Grigorev force-pushed the add-health-check branch 2 times, most recently from 1b8d07f to 999eddd Compare June 23, 2020 10:00
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 23, 2020
Copy link
Member

@mhrivnak mhrivnak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To alleviate any ambiguity or assumptions people might make about what controller-runtime probes do, I suggest a very direct statement such as: "The process will be considered ready and healthy by kubernetes based solely on whether it can respond to an HTTP request."

docs/probes.md Outdated
@@ -0,0 +1,30 @@
# Baremetal Machine Controller readiness

For the perpouse of integration with MAO, baremethal provider is leveraging controller-runtime readiness and liveness probes, checking ability to serve HTTP requests in the manager process, to encrease robustness for cluster operator status reporting.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/perpouse/purpose/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/baremethal/baremetal/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/encrease/increase/

- Introducing simple readiness probes for controller-runtime, checking the manager container could respond to HTTP requests.
@mhrivnak
Copy link
Member

/unhold

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 23, 2020
@mhrivnak
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 23, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Danil-Grigorev, dhellmann, enxebre, mhrivnak

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 657bc27 into openshift:master Jun 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add liveness/readiness probes
7 participants