sincecutoff.com
← all changes

gcloud network-management connectivity-tests supports GKE Pod endpoints

Introduced 2026-02-03 · score 0.95

HOW TO USE IT

When debugging connectivity to or from a GKE Pod, create a Connectivity Test with the Pod URI in `--source-gke-pod` or `--destination-gke-pod`.

gcloud network-management connectivity-tests create <test-name> --protocol=<protocol> --source-gke-pod=<source-pod-uri> --destination-gke-pod=<destination-pod-uri> --destination-port=<port> --round-trip

WHY THIS HELPS

Run a Connectivity Test to or from a GKE Pod while debugging repository connectivity.

REQUIREMENTS AND LIMITATIONS

  • <test-name> (required): Connectivity Test name.
  • --source-gke-pod=<source-pod-uri>: GKE Pod URI for the source endpoint. Required when the source is a Pod; at least one endpoint flag must be specified.
  • --destination-gke-pod=<destination-pod-uri>: GKE Pod URI for the destination endpoint. Required when the destination is a Pod; at least one endpoint flag must be specified.
  • --protocol=<protocol>: Protocol for the test; defaults to TCP.
  • --destination-port=<port>: Destination port; specify only for TCP or UDP tests.
  • --round-trip: Also calculate return traces if the packet reaches the destination.
  • Prerequisite: Use the Google Cloud CLI. The caller needs permission to create Connectivity Tests and at least `roles/compute.networkViewer` to read the tested network configuration.
  • The Pod flags apply to Connectivity Tests to or from GKE Pods.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card