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
Liveness / Readiness probes for PythonWatchManager
#38
Comments
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 22, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 22, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 22, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 22, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 22, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 22, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 22, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
Previously, the hasattr call would use MRO to find _instance on the parent so if the parent were instantiated before the child, the child would reuse the parent's instance. IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
gabe-l-hart
added a commit
to gabe-l-hart/oper8
that referenced
this issue
Jan 23, 2024
This script can be used in operator images as a exec probe IBM#38 Signed-off-by: Gabe Goodhart <ghart@us.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
As an operator maintainer in an application, I need to be able to probe the
liveness
/readiness
of the operator. With theAnsibleWatchManager
, the native/healthz
and/readyz
HTTP endpoints were accessible, but there's no equivalent with PWM.Describe the solution you'd like
Add a
heartbeat_thread
to the PWM's group of managed threads. This thread will periodically dump the current time to a file if enabled.Describe alternatives you've considered
procps
in their docker builds and run aps aux | grep ...
style check to ensure the operator is running. This has the downside of requiring a potentially dangerous tool (ps
can be used to probe running processes), and it is also a bad approximation for the state of the running operator code.The text was updated successfully, but these errors were encountered: