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

Health probes #206

Merged
merged 9 commits into from Jul 23, 2018
Merged

Health probes #206

merged 9 commits into from Jul 23, 2018

Conversation

amoskyler
Copy link
Contributor

@amoskyler amoskyler commented Jul 19, 2018

Implements front end for health probes
screen shot 2018-07-20 at 11 01 25 am

@amoskyler amoskyler self-assigned this Jul 19, 2018
@drshrey
Copy link
Contributor

drshrey commented Jul 20, 2018

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.

@amoskyler
Copy link
Contributor Author

I can add auto open in a secondary PR




{/* <Grid item xs={12}> */}
Copy link
Contributor Author

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.

@drshrey
Copy link
Contributor

drshrey commented Jul 20, 2018

@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?

@amoskyler
Copy link
Contributor Author

amoskyler commented Jul 20, 2018 via email

@amoskyler amoskyler merged commit c0f91a5 into master Jul 23, 2018
@aballman aballman deleted the health-probes branch December 4, 2018 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants