8df33bc1a7
separated from the apiserver running locally on the master node so that it can be optionally enabled or disabled as needed. Also, fix the healthchecking configuration for the master components, which was previously only working by coincidence: If a kubelet doesn't register with a master, it never bothers to figure out what its local address is. In which case it ends up constructing a URL like http://:8080/healthz for the http probe. This happens to work on the master because all of the pods are using host networking and explicitly binding to 127.0.0.1. Once the kubelet is registered with the master and it determines the local node address, it tries to healthcheck on an address where the pod isn't listening and the kubelet periodically restarts each master component when the liveness probe fails. |
||
|---|---|---|
| .. | ||
| aws_ebs | ||
| blog-logging | ||
| cassandra | ||
| celery-rabbitmq | ||
| cluster-dns | ||
| elasticsearch | ||
| explorer | ||
| glusterfs | ||
| guestbook | ||
| guestbook-go | ||
| hazelcast | ||
| high-availability | ||
| https-nginx | ||
| iscsi | ||
| k8petstore | ||
| kubectl-container | ||
| meteor | ||
| mysql-wordpress-pd | ||
| nfs | ||
| openshift-origin | ||
| phabricator | ||
| rbd | ||
| redis | ||
| rethinkdb | ||
| spark | ||
| storm | ||
| doc.go | ||
| examples_test.go | ||
| pod | ||
| README.md | ||
| scheduler-policy-config.json | ||
| simple-nginx.md | ||
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest 1.0.x release of this document can be found [here](http://releases.k8s.io/release-1.0/examples/README.md).Documentation for other releases can be found at releases.k8s.io.
Kubernetes Examples: releases.k8s.io/HEAD
This directory contains a number of different examples of how to run applications with Kubernetes.