To get support for Google Distributed Cloud connected, see the following resources.
Get a Google support package
Google Cloud offers different support packages to meet different needs, such as 24/7 coverage, phone support, and access to a technical support manager. For more information, see Google Cloud Customer Care support.
Get support from the community
Visit the Google Cloud
Slack community to discuss
Distributed Cloud connected and other Google Cloud products. If you haven't
already joined,
use this form to sign up.
For Distributed Cloud connected, join the
#networking
channel.
File bugs or feature requests
From the Distributed Cloud connected documentation, click Send feedback at the top or bottom of the page. This opens a feedback form. Your comments are reviewed by the Distributed Cloud connected team.
Distributed Cloud connected support policy
The Distributed Cloud connected support policy applies to Distributed Cloud connected software running on both Google-owned and customer-sourced hardware. The support policy has the following constraints:
Customer-sourced hardware. Google does not provide support for customer-sourced hardware.
Third-party marketplace services. Marketplace services that use third-party software are supported based on your agreement with the third-party vendor.
Customer-installed software. Google does not provide support for third-party software you install on your Distributed Cloud connected deployment. The interactions of any installed third-party software with Distributed Cloud connected must adhere to the Distributed Cloud connected deprecation policy.
Hardware support and refresh. To learn about about how Google supports and refreshes Google-owned Distributed Cloud connected hardware, contact your Google representative.
Customer-specific exceptions. Google makes no exceptions to its support policy for Distributed Cloud connected based on individual customer needs.
Supported Distributed Cloud connected releases
At the time of publication of this page, the supported minor releases of Distributed Cloud connected software are 1.10, 1.11, and 1.12.
Glossary
Automatic software update. A Distributed Cloud connected software update performed automatically on a fleet of clusters, one at a time, according to user-defined maintenance windows and maintenance exclusion windows.
Breaking change. A change in the behavior of Distributed Cloud connected software that requires user action to maintain functionality. This includes changes in the behavior of existing Distributed Cloud connected features as well as the removal of Distributed Cloud connected features that are no longer supported. A breaking change can render a workload deployed on Distributed Cloud connected inoperable.
Defect. A behavior other than the intended design behavior of any aspect of the Distributed Cloud connected software. this includes bugs, security vulnerabilities, as well as reliability and stability issues that consistently prevent Distributed Cloud connected from fulfilling its Service-Level Objective (SLO). A single SLO incident on its own does not immediately imply a defect.
End-of-support (EOS) date. The date on which the support for a given Distributed Cloud connected software release concludes. This means no further maintenance on that software release will be performed, including security mitigations, defect fixes, and on-call assistance. Product documentation for an EOS Distributed Cloud connected software release is available in archived form for historical reference.
First-party software. Google Cloud features and services that Distributed Cloud connected can integrate to extend its functionality.
Fleet. A logical grouping of Distributed Cloud connected clusters. Distributed Cloud connected clusters in a fleet are managed together.
Hotfix release. A Distributed Cloud connected software release made available on-demand that addresses specific critical issues that pose security risks or cause severe service disruptions. A hotfix release typically has a three-day qualification turnaround time.
Maintenance window. A user-defined schedule that determines when Distributed Cloud connected software updates can occur.
Maintenance exclusion window. A user-defined schedule that determines when Distributed Cloud connected software updates must not occur to prevent workload disruptions.
Management software bundle. The internal management layer of the Distributed Cloud connected stack that lets Google monitor and manage your Distributed Cloud connected deployment. Google automatically updates the management software bundle.
Manual software update. A Distributed Cloud connected software update performed manually through the Google Cloud CLI or Google Cloud console on a single Distributed Cloud connected cluster.
Minor release. A Distributed Cloud connected software release that introduces new features, changes the behavior of existing features, and removes features that are no longer supported. A minor release can also contain software component upgrades and security mitigations. Changes introduced in a minor release are backwards-compatible, except breaking changes. A minor release version increments the secondary version number, for example from 1.10.0 to 1.11.0.
Patch release. A Distributed Cloud connected software release that resolves issues discovered in its corresponding minor release. A patch release does not introduce new features, change the behavior of existing features, or remove features that are no longer supported. A patch release increments the tertiary version number, for example from 1.11.0 to 1.11.1.
Product software bundle. The core of the Distributed Cloud connected software stack, such as machine firmware, the EdgeOS operating system, and the Kubernetes workload management layer, including control planes and worker nodes. You can upgrade the product software bundle manually or automatically.
Release stabilization phase. A phase in a Distributed Cloud connected software release life cycle in which no new features are introduced or the behavior of existing features changed; instead, development focus shifts to improving the security and stability of that Distributed Cloud connected software release.
Service level objective (SLO). A commitment by Google to meet agreed-upon Distributed Cloud connected performance and availability metrics.
Service level agreement (SLA). An agreement between you and Google that defines the terms and conditions of Distributed Cloud connected's operation, including service level objectives.
Distributed Cloud connected software update. Replacing the installed release of Distributed Cloud connected software with a newer release.
Support. The ongoing maintenance of the Distributed Cloud connected software and product documentation that resolves defects, improves, the security, reliability, and stability of the Distributed Cloud connected software, and updates product documentation where necessary. Support also provides compatibility with evolving hardware and software ecosystems. Support does not include the handling and resolution of user inquiries.
Third-party software. Software solutions not provided by Google.
Turnup. Google provisioning a Distributed Cloud connected machine for remote management and configuring it so that it can accept an installation of Distributed Cloud connected software.
Software updates
The following table describes the software update policy for Distributed Cloud connected:
| Component | Update policy |
|---|---|
| Platform software bundle | You can schedule a maintenance window and a maintenance exclusion window for each Distributed Cloud connected fleet. If you don't specify a maintenance window, Google updates the product software bundle on your Distributed Cloud connected clusters automatically. |
| Management software bundle | Google updates the management software bundle automatically. |
| Services | You are responsible for updating your first-party and third-party services running on your your Distributed Cloud connected clusters. |
Your Distributed Cloud connected administrator is responsible for updating the Distributed Cloud connected product bundle on your Distributed Cloud connected clusters. Google strongly recommends that you update the Distributed Cloud connected software as soon as a new release is available, ideally within forty five (45) days.
You must configure a minimum of three (3) maintenance windows, as described in Configure a maintenance window for a cluster, with a total length of at least fifteen (15) hours, which is the minimum required to perform Distributed Cloud connected product bundle and management bundle updates, as well as apply hotfixes.
If your Distributed Cloud connected deployment is more than one minor or patch software release behind, you must update it sequentially until you reach the target release, which might take more than fifteen (15) hours. Skipping releases is not supported. Google might automatically update your Distributed Cloud connected product bundle to a supported release if the deployed release is within one (1) month of end of support.
Google might automatically update your Distributed Cloud connected deployment if an emergency hotfix is necessary to maintain the security posture or stability of Distributed Cloud connected.
Release cadence
The release cadence for Distributed Cloud connected software is as follows:
A minor release of the Distributed Cloud connected product bundle every four months. Once a minor release is rolled out, it enters the stabilization phase.
One more patch releases per each minor release of the Distributed Cloud connected product bundle as Google determines necessary.
All updates, improvements, and security mitigations are cumulative, except where noted. This cadence is subject to change.
Support timelines
Google supports up to two minor Distributed Cloud connected product bundle software releases, in addition to the latest release, or all minor Distributed Cloud connected product bundle software releases for a period of twelve (12) months from release, whichever is greater. You must update all of your Distributed Cloud connected clusters within this timeframe. This support period includes Root Cause Analysis (RCA). During the support period, the Distributed Cloud connected minor software release receives security mitigations, improvements to stability and reliability, and updates that maintain or improve compatibility with evolving software and hardware dependencies. Updates to Distributed Cloud connected management software bundle updates are automatic and mandatory.
Google implements security mitigations as per industry-standard timelines for Common Vulnerabilities and Exposures (CVEs) High-rated CVEs are mitigated within thirty (30) days; moderate-rated CVEs are mitigated within ninety (90) days; low-rated CVEs are mitigated with one hundred and eighty (180) days. If a security mitigation can't be implemented in a supported release of Distributed Cloud connected older than the latest, Google reserves the right to require you to update your Distributed Cloud connected software to a version in which the mitigation is implemented to maintain support.
When a Distributed Cloud connected feature is deprecated, it first enters a 12-month deprecation period, during which it remains available. Upon the conclusion of the deprecation period, the feature reaches end-of-life (EOL) and is scheduled for removal from Distributed Cloud connected.
Defects
Google provides workarounds in product documentation for all defects identified in a minor Distributed Cloud connected software release. Critical defects the severely impair the functionality, security, or reliability of Distributed Cloud connected are addressed as hotfix or patch releases, depending on their severity. These fixes are backported to all supported Distributed Cloud connected software releases. In extraordinary circumstances, Google might release, at their discretion, a hotfix for every active patch release of Distributed Cloud connected. These circumstances include zero-day vulnerabilities, broken upgrade paths, or SLO violations.
End of support (EOS)
A minor Distributed Cloud connected product bundle software release reaches end of support after it has been rolled out for twelve (12) consecutive months, or when two successive minor Distributed Cloud connected product bundle software releases have been rolled out after it, whichever is later. You are responsible for keeping your Distributed Cloud connected deployments up to date with the most recent minor and patch release of the Distributed Cloud connected product bundle you've deployed. Google won't be held liable for any incidents resulting from your failure or refusal to update your Distributed Cloud connected deployments. If you are running an unsupported release of the Distributed Cloud connected software, Google won't provide any assistance with operating or maintaining that software release except for updating to a supported release.
If you are running an unsupported release of the Distributed Cloud connected software and Google discovers a critical security vulnerability in that release that, at Google's sole discretion, is determined to threaten the security or integrity of Google's or your own infrastructure, Google might disable, disconnect, shut down, or force-update the affected Distributed Cloud connected deployment to protect Google's and your assets.
Preview-level features
Distributed Cloud connected pre-GA or "preview" features might be changed or removed without notice; backwards compatibility for pre-GA features is not guaranteed. Pre-GA features are exempt from any Distributed Cloud connected service-level agreements (SLAs) and any support commitments. Google provides security mitigations for pre-GA features on the same basis as for GA-level features.
Notification and communication
The Distributed Cloud connected public documentation and release notes denote the end of support timelines for each Distributed Cloud connected software release. Distributed Cloud connected clusters approaching end of support as well as those scheduled for automatic software updates are marked accordingly in Google Cloud console; you also receive notifications for such clusters through Cloud Logging.
Turnup and deployment
oogle completes the turnup of your Distributed Cloud connected machines to a state that lets create your Distributed Cloud connected clusters. Past this point, you are responsible for setting up any additional infrastructure, creating your Distributed Cloud connected clusters, and deploying your workloads.
Services
Distributed Cloud connected integrates with a number of Google Cloud services, as described in Manage Google services. These services operate under their own dedicated support, update, and deprecation policies independent of those for Distributed Cloud connected. Google provides an advance notice twelve (12) months before a Google Cloud service that integrates with Distributed Cloud connected reaches end of support or another end-of-life event. You must monitor, understand, and plan against such events for each Google Cloud service you're deploying on Distributed Cloud connected. You are wholly responsible for deploying and maintaining any third-party software solutions on Distributed Cloud connected.