Stay organized with collections
Save and categorize content based on your preferences.
Learn about Workflows changes such as backward
incompatible API changes, product or feature deprecations, mandatory migrations,
or potentially disruptive maintenance.
Date published
Description
Instructions
January 28, 2025
Announcement of requirement to access Google Kubernetes Engine clusters through
DNS-based endpoints. See
release note.
If you don't use Workflows to access GKE
clusters, no action is required from you. For more information, in this
document, see the January 28, 2025 section.
January 28, 2025
Effective May 2, 2025, Workflows will not support
HTTP requests to the
IP-based endpoints
of Google Kubernetes Engine (GKE) cluster control planes. To ensure that your
workflow functions as expected, you must access the
DNS-based endpoints.
As a best practice, we recommend that instead of making a direct HTTP call, you
use the Kubernetes API connector in a
workflow.
Scope and impact
If you don't use Workflows to access GKE clusters,
no action is required from you.
As of May 2, 2025, new workflows are impacted; however, existing
workflows will continue to function.
By August 1, 2025, any workflows that continue to make HTTP requests to the
IP-based endpoints of GKE clusters might not function as expected.
Required action
Ensure that any workflows that access the IP-based endpoints of GKE
clusters are modified to use the DNS-based endpoints instead by July 21, 2025.
For more information, see
HTTP requests to GKE.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Service announcements\n\nLearn about Workflows changes such as backward\nincompatible API changes, product or feature deprecations, mandatory migrations,\nor potentially disruptive maintenance.\n\nJanuary 28, 2025\n----------------\n\nEffective **May 2, 2025** , Workflows will not support\n[HTTP requests](/workflows/docs/http-requests) to the\n[IP-based endpoints](/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#ipendpointsconfig)\nof Google Kubernetes Engine (GKE) cluster control planes. To ensure that your\nworkflow functions as expected, you must access the\n[DNS-based endpoints](/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#dnsendpointconfig).\nAs a best practice, we recommend that instead of making a direct HTTP call, you\nuse the [Kubernetes API connector](/workflows/docs/access-kubernetes-api) in a\nworkflow.\n\n### Scope and impact\n\nIf you don't use Workflows to access GKE clusters,\nno action is required from you.\n\nAs of **May 2, 2025**, new workflows are impacted; however, existing\nworkflows will continue to function.\n\nBy **August 1, 2025**, any workflows that continue to make HTTP requests to the\nIP-based endpoints of GKE clusters might not function as expected.\n\n### Required action\n\nEnsure that any workflows that access the IP-based endpoints of GKE\nclusters are modified to use the DNS-based endpoints instead by **July 21, 2025** .\nFor more information, see\n[HTTP requests to GKE](/workflows/docs/issues#gke-calls)."]]
