From 57e9a24c34d1200ffec33f11a30f9d07f51cff25 Mon Sep 17 00:00:00 2001 From: Julian Simioni Date: Sat, 23 Sep 2017 17:13:42 -0400 Subject: [PATCH] Fix a few typos and clean up hooks section The hooks section in the cluster spec documentation had a few typos and other rough spots. This should make it read a little more smoothly. --- docs/cluster_spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cluster_spec.md b/docs/cluster_spec.md index 062d4ec031..3c3ef5598a 100644 --- a/docs/cluster_spec.md +++ b/docs/cluster_spec.md @@ -213,7 +213,7 @@ More information about running in an existing VPC is [here](run_in_existing_vpc. ### hooks -Hooks allow for the execution of an action before the installation of Kubernetes on every node in a cluster. For instance you can install nvidia drivers for using GPUs. This hooks can be in the form on docker images or manifest files (systemd units). Hooks can be place in either then cluster spec, meaning the will be globally deployed, or they can be placed into the instanceGroup specification. Note, service names on the instanceGroup which overlap with the cluster spec take precedence and ignore the cluster spec definition, i.e. if you have a unit file 'myunit.service' in cluster and then one in the instanceGroup, only the instanceGroup is applied. +Hooks allow for the execution of an action before the installation of Kubernetes on every node in a cluster. For instance you can install Nvidia drivers for using GPUs. This hooks can be in the form of Docker images or manifest files (systemd units). Hooks can be placed in either the cluster spec, meaning they will be globally deployed, or they can be placed into the instanceGroup specification. Note: service names on the instanceGroup which overlap with the cluster spec take precedence and ignore the cluster spec definition, i.e. if you have a unit file 'myunit.service' in cluster and then one in the instanceGroup, only the instanceGroup is applied. ``` spec: