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
Health probes #206
Health probes #206
Conversation
If any of the options in Advanced Configurations are filled, we should have the dropdowns auto-opened, so the person is aware it's not empty. |
I can add auto open in a secondary PR |
|
||
|
||
|
||
{/* <Grid item xs={12}> */} |
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.
I will remove this huge comment block.
@amoskyler According to the kubernetes docs (https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/), |
The default values are handled in kubernetes. The zero is simply to
represent an empty setting.
On Jul 20, 2018 11:25 AM, "Shreyas Jaganmohan" <notifications@github.com> wrote:
@amoskyler <https://github.com/amoskyler> According to the kubernetes docs (
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/),
successThresholds and failureThresholds have a min of 1. Should we add that
in our validation logic on the frontend or will it default to 1 even if 0
is inputted?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#206 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFHKxRySGkwqzrMcIxSbH_h4q1iwwShgks5uIiCPgaJpZM4VW25M>
.
|
Implements front end for health probes