C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fix some typos

Browse source 
Signed-off-by: Rui Cao <ruicao@alauda.io>
This commit is contained in:
Rui Cao 2018-10-30 20:07:52 +08:00
parent 6e192d487b
commit 0d3beb4e5a
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/netcheck.md
View file

@ -5,7 +5,7 @@ With the ``deploy_netchecker`` var enabled (defaults to false), Kubespray deploy
Network Checker Application from the 3rd side `l23network/k8s-netchecker` docker Network Checker Application from the 3rd side `l23network/k8s-netchecker` docker
images. It consists of the server and agents trying to reach the server by usual images. It consists of the server and agents trying to reach the server by usual
for Kubernetes applications network connectivity meanings. Therefore, this for Kubernetes applications network connectivity meanings. Therefore, this
automagically verifies a pod to pod connectivity via the cluster IP and checks automatically verifies a pod to pod connectivity via the cluster IP and checks
if DNS resolve is functioning as well. if DNS resolve is functioning as well.
The checks are run by agents on a periodic basis and cover standard and host network The checks are run by agents on a periodic basis and cover standard and host network
@ -20,7 +20,7 @@ curl http://localhost:31081/api/v1/connectivity_check
Note that Kubespray does not invoke the check but only deploys the application, if Note that Kubespray does not invoke the check but only deploys the application, if
requested. requested.
There are related application specifc variables: There are related application specific variables:
``` ```
netchecker_port: 31081 netchecker_port: 31081
agent_report_interval: 15 agent_report_interval: 15