Create the "internal" firewall rule for kubemark master.

This is equivalent to the "internal" firewall rule that is created for the regular masters. The main reason for doing it is to allow prometheus scraping metrics from various kubemark master components, e.g. kubelet. Ref. https://github.com/kubernetes/perf-tests/issues/503

Create the "internal" firewall rule for kubemark master.
02f28218 · Matt Matejczyk · 18b4e1b8 · 02f28218
Commit 02f28218 authored Apr 18, 2019 by Matt Matejczyk
Hide whitespace changes
Inline Side-by-side

Showing with 11 additions and 0 deletions

util.sh test/kubemark/gce/util.sh +11 -0

No files found.
--- a/test/kubemark/gce/util.sh
+++ b/test/kubemark/gce/util.sh
@@ -102,6 +102,13 @@ function create-master-instance-with-resources {
    --target-tags "${MASTER_TAG}" \
    --allow "tcp:443" &

+  run-gcloud-compute-with-retries firewall-rules create "${MASTER_NAME}-internal" \
+    --project "${PROJECT}" \
+    --network "${NETWORK}" \
+    --source-ranges "10.0.0.0/8" \
+    --target-tags "${MASTER_TAG}" \
+    --allow "tcp:1-2379,tcp:2382-65535,udp:1-65535,icmp" &
+
  wait
 }

@@ -136,6 +143,10 @@ function delete-master-instance-and-resources {
 	  --project "${PROJECT}" \
 	  --quiet || true

+  gcloud compute firewall-rules delete "${MASTER_NAME}-internal" \
+	  --project "${PROJECT}" \
+	  --quiet || true
+
  if [ "${SEPARATE_EVENT_MACHINE:-false}" == "true" ]; then
 	  gcloud compute instances delete "${EVENT_STORE_NAME}" \
    	  "${GCLOUD_COMMON_ARGS[@]}" || true