github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/saltbase
History
k8s-merge-robot 9aff7d9e8b Merge pull request #27652 from girishkalele/kubedns_healthz 
Automatic merge from submit-queue

Enhance kubedns pod health checks to cover kubedns container

The existing health check hits port 53, the dnsmasq container, with the same domain name every time. Since dnsmasq looks up and caches results from the kubedns container, running on port 10053, the health check is not covering the kubedns container after the first query (and once every TTL expiration).

This PR enhances the health check to directly hit port 10053 (kubedns) in addition to port 53.
 		2016-06-29 14:58:17 -07:00
..
pillar AWS kube-up: Add support for wily 2016-02-17 10:45:21 -05:00
reactor Add ga-beacon analytics to gendocs scripts 2015-05-15 18:56:38 -07:00
salt Merge pull request #27652 from girishkalele/kubedns_healthz 2016-06-29 14:58:17 -07:00
README.md Implement Azure cloud provider scripts 2016-06-17 23:46:03 -07:00
install.sh Copy and display source location prominently on Kubernetes instances 2016-06-23 15:27:38 -07:00

README.md

SaltStack configuration

This is the root of the SaltStack configuration for Kubernetes. A high level overview for the Kubernetes SaltStack configuration can be found in the docs tree.

This SaltStack configuration currently applies to default configurations for Debian-on-GCE, Fedora-on-Vagrant, Ubuntu-on-AWS and Ubuntu-on-Azure. (That doesn't mean it can't be made to apply to an arbitrary configuration, but those are only the in-tree OS/IaaS combinations supported today.) As you peruse the configuration, these are shorthanded as gce, vagrant, aws, azure-legacy in grains.cloud; the documentation in this tree uses this same shorthand for convenience.

See more:

Analytics