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.