diff --git a/cluster/juju/layers/kubernetes-worker/README.md b/cluster/juju/layers/kubernetes-worker/README.md index 9194394c52b..b086bcba6f4 100644 --- a/cluster/juju/layers/kubernetes-worker/README.md +++ b/cluster/juju/layers/kubernetes-worker/README.md @@ -43,7 +43,7 @@ Resuming the workload will [uncordon](http://kubernetes.io/docs/user-guide/kubec ## Known Limitations -Kubernetes workers currently only support 'phaux' HA scenarios. Even when configured with an HA cluster string, they will only ever contact the first unit in the cluster map. To enalbe a proper HA story, kubernetes-worker units are encouraged to proxy through a [kubeapi-load-balancer](https://jujucharms.com/kubeapi-load-balancer) +Kubernetes workers currently only support 'phaux' HA scenarios. Even when configured with an HA cluster string, they will only ever contact the first unit in the cluster map. To enable a proper HA story, kubernetes-worker units are encouraged to proxy through a [kubeapi-load-balancer](https://jujucharms.com/kubeapi-load-balancer) application. This enables a HA deployment without the need to re-render configuration and disrupt the worker services. diff --git a/examples/storage/redis/image/redis-master.conf b/examples/storage/redis/image/redis-master.conf index 2e7f054fae5..29ae1bb4127 100644 --- a/examples/storage/redis/image/redis-master.conf +++ b/examples/storage/redis/image/redis-master.conf @@ -656,7 +656,7 @@ slowlog-max-len 128 # By default latency monitoring is disabled since it is mostly not needed # if you don't have latency issues, and collecting data has a performance # impact, that while very small, can be measured under big load. Latency -# monitoring can easily be enalbed at runtime using the command +# monitoring can easily be enabled at runtime using the command # "CONFIG SET latency-monitor-threshold " if needed. latency-monitor-threshold 0 diff --git a/examples/storage/redis/image/redis-slave.conf b/examples/storage/redis/image/redis-slave.conf index ed3918dab82..afd0a45fd43 100644 --- a/examples/storage/redis/image/redis-slave.conf +++ b/examples/storage/redis/image/redis-slave.conf @@ -656,7 +656,7 @@ slowlog-max-len 128 # By default latency monitoring is disabled since it is mostly not needed # if you don't have latency issues, and collecting data has a performance # impact, that while very small, can be measured under big load. Latency -# monitoring can easily be enalbed at runtime using the command +# monitoring can easily be enabled at runtime using the command # "CONFIG SET latency-monitor-threshold " if needed. latency-monitor-threshold 0