node-feature-discovery/label-nodes.sh

#!/usr/bin/env bash
# Get the node count 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.json.template > node-feature-discovery-job.json
kubectl create -f node-feature-discovery-job.json
Added more logging. Changed formatting. 2016-07-14 14:56:43 +00:00			`#!/usr/bin/env bash`
			`# Get the node count in the Kubernetes cluster`
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			`NumNodes=$(kubectl get nodes \| grep -i ready \| wc -l)`

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.`
Replayed commit history. 2016-08-31 00:04:43 +00:00			`sed -e "s/COMPLETION_COUNT/$NumNodes/" -e "s/PARALLELISM_COUNT/$NumNodes/" node-feature-discovery-job.json.template > node-feature-discovery-job.json`
			`kubectl create -f node-feature-discovery-job.json`