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

Issue with /docs/user-guide/liveness/ #1909

Closed
1 of 2 tasks
timstoop opened this issue Dec 9, 2016 · 2 comments
Closed
1 of 2 tasks

Issue with /docs/user-guide/liveness/ #1909

timstoop opened this issue Dec 9, 2016 · 2 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@timstoop
Copy link

timstoop commented Dec 9, 2016

This is a...

  • Feature Request
  • Bug Report

Problem:
I'm trying to find an example of using the tcp socket action as a liveness probe. This page only describes http and exec types of checks.

Proposed Solution:
Please provide an example for the tcp socket request as well.

Page to Update:
http://kubernetes.io/docs/user-guide/liveness/

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 20, 2017
@tengqm
Copy link
Contributor

tengqm commented Dec 22, 2017

This issue has been solved properly in #3494.

@tengqm tengqm closed this as completed Dec 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants