mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-03 09:22:44 +00:00
Merge pull request #13072 from mikaelh/master
Elastic IP need to be assigned after the instance is in running state
This commit is contained in:
commit
1b8727ada1
@ -851,13 +851,13 @@ function kube-up {
|
|||||||
exit 1
|
exit 1
|
||||||
fi
|
fi
|
||||||
else
|
else
|
||||||
|
# We are not able to add an elastic ip, a route or volume to the instance until that instance is in "running" state.
|
||||||
|
wait-for-instance-running $master_id
|
||||||
|
|
||||||
KUBE_MASTER=${MASTER_NAME}
|
KUBE_MASTER=${MASTER_NAME}
|
||||||
KUBE_MASTER_IP=$(assign-elastic-ip $ip $master_id)
|
KUBE_MASTER_IP=$(assign-elastic-ip $ip $master_id)
|
||||||
echo -e " ${color_green}[master running @${KUBE_MASTER_IP}]${color_norm}"
|
echo -e " ${color_green}[master running @${KUBE_MASTER_IP}]${color_norm}"
|
||||||
|
|
||||||
# We are not able to add a route or volume to the instance until that instance is in "running" state.
|
|
||||||
wait-for-instance-running $master_id
|
|
||||||
|
|
||||||
# This is a race between instance start and volume attachment. There appears to be no way to start an AWS instance with a volume attached.
|
# This is a race between instance start and volume attachment. There appears to be no way to start an AWS instance with a volume attached.
|
||||||
# To work around this, we wait for volume to be ready in setup-master-pd.sh
|
# To work around this, we wait for volume to be ready in setup-master-pd.sh
|
||||||
echo "Attaching persistent data volume (${MASTER_DISK_ID}) to master"
|
echo "Attaching persistent data volume (${MASTER_DISK_ID}) to master"
|
||||||
|
Loading…
Reference in New Issue
Block a user