Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
a62708e2
Commit
a62708e2
authored
Jun 22, 2015
by
Robert Bailey
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Replace kubectl.sh with kubectl in the liveness example.
parent
ebeb1044
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
README.md
examples/liveness/README.md
+7
-7
No files found.
examples/liveness/README.md
View file @
a62708e2
...
...
@@ -37,26 +37,26 @@ This [guide](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examp
To show the health check is actually working, first create the pods:
```
# kubectl create -f exec-liveness.yaml
#
cluster/kbuectl.sh
create -f http-liveness.yaml
#
kubectl
create -f http-liveness.yaml
```
Check the status of the pods once they are created:
```
# kubectl get pods
POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS CREATED MESSAGE
liveness-exec 10.244.3.7 kubernetes-minion-f08h/130.211.122.180 test=liveness Running 3 seconds
liveness gcr.io/google_containers/busybox Running 2 seconds
liveness-http 10.244.0.8 kubernetes-minion-0bks/104.197.10.10 test=liveness Running 3 seconds
liveness gcr.io/google_containers/liveness Running 2 seconds
liveness-exec 10.244.3.7 kubernetes-minion-f08h/130.211.122.180 test=liveness Running 3 seconds
liveness gcr.io/google_containers/busybox Running 2 seconds
liveness-http 10.244.0.8 kubernetes-minion-0bks/104.197.10.10 test=liveness Running 3 seconds
liveness gcr.io/google_containers/liveness Running 2 seconds
```
Check the status half a minute later, you will see the termination messages:
```
# kubectl get pods
POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS CREATED MESSAGE
liveness-exec 10.244.3.7 kubernetes-minion-f08h/130.211.122.180 test=liveness Running 34 seconds
liveness-exec 10.244.3.7 kubernetes-minion-f08h/130.211.122.180 test=liveness Running 34 seconds
liveness gcr.io/google_containers/busybox Running 3 seconds last termination: exit code 137
liveness-http 10.244.0.8 kubernetes-minion-0bks/104.197.10.10 test=liveness Running 34 seconds
liveness-http 10.244.0.8 kubernetes-minion-0bks/104.197.10.10 test=liveness Running 34 seconds
liveness gcr.io/google_containers/liveness Running 13 seconds last termination: exit code 2
```
The termination messages indicate that the liveness probes have failed, and the containers have been killed and recreated.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment