curl -4 ifconfig.co

Author: Mathieu Benoit

content/config-controller/create-config-controller.md

@@ -16,7 +16,7 @@ echo "export RANDOM_SUFFIX=${RANDOM_SUFFIX}" >> ~/acm-workshop-variables.sh
 echo "export CONFIG_CONTROLLER_PROJECT_ID=acm-workshop-${RANDOM_SUFFIX}" >> ~/acm-workshop-variables.sh
 echo "export BILLING_ACCOUNT_ID=${BILLING_ACCOUNT_ID}" >> ~/acm-workshop-variables.sh
 echo "export ORG_OR_FOLDER_ID=${ORG_OR_FOLDER_ID}" >> ~/acm-workshop-variables.sh
-echo "export LOCAL_IP_ADDRESS=$(curl ifconfig.co)" >> ~/acm-workshop-variables.sh
+echo "export LOCAL_IP_ADDRESS=$(curl -4 ifconfig.co)" >> ~/acm-workshop-variables.sh
 echo "export CONFIG_CONTROLLER_NAME=configcontroller" >> ~/acm-workshop-variables.sh
 echo "export CONFIG_CONTROLLER_LOCATION=us-east1" >> ~/acm-workshop-variables.sh
 source ~/acm-workshop-variables.sh

content/gke-cluster/extras.md

@@ -40,7 +40,7 @@ Currently, you can't access the GKE cluster via `kubectl` commands because it's
     - cidrBlock: FIXME_YOUR_LOCAL_IP_ADDRESS/32
       displayName: local
 ```
-As an example, you could get your local IP address by running this command: `curl ifconfig.co`.
+As an example, you could get your local IP address by running this command: `curl -4 ifconfig.co`.
 
 The associated file to update manually is here: `~/$GKE_PROJECT_DIR_NAME/config-sync/gke-cluster.yaml`, and you could then run this command to actually deploy this change in Config Controller:
 ```Bash