node-feature-discovery/label-nodes.sh

#!/usr/bin/env bash
# Get the number of nodes in Ready state in the Kubernetes cluster
NumNodes=$(kubectl get nodes | grep -i ' ready ' | wc -l)

# We set the .spec.completions and .spec.parallelism to the node count
# We request a specific hostPort in the job spec to limit the number of pods
# that run on a node to one. As a result, one pod runs on each node in parallel
# We set the NODE_NAME environemnt variable to get the Kubernetes node object.
sed -e "s/COMPLETION_COUNT/$NumNodes/" -e "s/PARALLELISM_COUNT/$NumNodes/" node-feature-discovery-job.yaml.template > node-feature-discovery-job.yaml
kubectl create -f node-feature-discovery-job.yaml
Added more logging. Changed formatting. 2016-07-14 14:56:43 +00:00			`#!/usr/bin/env bash`
Add, correct some notes in documentation A "newbie style" deployment attempt was made on a recent cluster, and some added notes in README and in label-nodes.sh could help someone who just started with node-feature-discovery. Correcting also description of label-nodes.sh which does not deal with unlabeled nodes as was promised in README. 2018-02-23 10:53:22 +00:00			`# Get the number of nodes in Ready state in the Kubernetes cluster`
label-nodes.sh: match Ready without side-strings (#151) Counting nodes in Ready state was too fragile, matching entries like: Ready,SchedulingDisabled NotReady By requiring whitespace on both side, we accept only clean Ready. 2018-07-26 12:20:57 +00:00			`NumNodes=$(kubectl get nodes \| grep -i ' ready ' \| wc -l)`
1. Enabled RDT discovery. 2. Updated the ds to a job for node labelling. 3. Added script to run a job in each node. 4. Updated Readme. 2016-07-12 00:30:49 +00:00
Added more logging. Changed formatting. 2016-07-14 14:56:43 +00:00			`# We set the .spec.completions and .spec.parallelism to the node count`
			`# We request a specific hostPort in the job spec to limit the number of pods`
			`# that run on a node to one. As a result, one pod runs on each node in parallel`
Get node name from spec.nodeName instead of indirectly from pod. (#93) spec.nodeName allows to get node name directly, without using pod and podnamespace as intermediate steps. 2018-03-12 16:04:37 +00:00			`# We set the NODE_NAME environemnt variable to get the Kubernetes node object.`
Convert templates and examples from json to yaml (#108) Convert resource templates from json to yaml Yaml is easier and less error prone to modify by hand. It also allows comments which can be especially useful in the templates. 2018-09-27 11:54:45 +00:00			`sed -e "s/COMPLETION_COUNT/$NumNodes/" -e "s/PARALLELISM_COUNT/$NumNodes/" node-feature-discovery-job.yaml.template > node-feature-discovery-job.yaml`
			`kubectl create -f node-feature-discovery-job.yaml`