luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Fix missed letter in the documentation (#5281)

This commit is contained in:
Ilya Pavlov 2019-01-29 01:25:56 +03:00 committed by kaitlincarter-hc
parent ffab5f55a6
commit 9cb766a8de
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/docs/platform/k8s/run.html.md
View File

@ -27,7 +27,7 @@ chart, you can have a full Consul deployment up and running in seconds.
While the Helm chart exposes dozens of useful configurations and automatically
sets up complex resources, it **does not automatically operate Consul.**
You are still reponsible for learning how to monitor, backup,
You are still responsible for learning how to monitor, backup,
upgrade, etc. the Consul cluster.
The Helm chart has no required configuration and will install a Consul
@ -320,5 +320,5 @@ node equivalence in Consul. Service registration should be handled via the
catalog syncing feature with Services rather than pods.
-> **Note:** Due to a limitation of anti-affinity rules with DaemonSets,
a client-mode agent runs alongide server-mode agents in Kubernetes. This
a client-mode agent runs alongside server-mode agents in Kubernetes. This
duplication wastes some resources, but otherwise functions perfectly fine.