github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Handle breaking change in 'gcloud compute routes create' with version check.

pull/6/head
Joe Beda 2014-06-08 08:07:34 -07:00
parent 156ebe2ce2
commit 81629733e1
1 changed files with 16 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
cluster/kube-up.sh
View File

@ -82,6 +82,8 @@ gcloud compute instances create ${MASTER_NAME}\
--restart-on-failure \
--metadata-from-file startup-script=${KUBE_TEMP}/master-start.sh &
GCLOUD_VERSION=$(gcloud version | grep compute | cut -f 2 -d ' ')
for (( i=0; i<${#MINION_NAMES[@]}; i++)); do
(
echo "#! /bin/bash"
@ -101,10 +103,20 @@ for (( i=0; i<${#MINION_NAMES[@]}; i++)); do
--can-ip-forward \
--metadata-from-file startup-script=${KUBE_TEMP}/minion-start-${i}.sh &
# 'gcloud compute' past 2014.06.08 breaks the way we are specifying
# --next-hop-instance and there is no way to be compatible with both versions.
if [[ $GCLOUD_VERSION < "2014.06.08" ]]; then
gcloud compute routes create ${MINION_NAMES[$i]} \
--project ${PROJECT} \
--destination-range ${MINION_IP_RANGES[$i]} \
--next-hop-instance ${ZONE}/instances/${MINION_NAMES[$i]} &
else
gcloud compute routes create ${MINION_NAMES[$i]} \
--project ${PROJECT} \
--destination-range ${MINION_IP_RANGES[$i]} \
--next-hop-instance ${MINION_NAMES[$i]} \
--next-hop-instance-zone ${ZONE} &
fi
done
FAIL=0