Google's primary support objective is to resolve production incidents as quickly as possible. We do this by understanding your configuration, analyzing logs and metrics, and collaborating with partners to solve incidents quickly.
Google Cloud offers a variety of support packages to accommodate your support needs. All Google Cloud Support packages include support for Anthos and Anthos clusters on VMware (GKE on-prem). If you have an existing Google Cloud Support package, then you already have support for Anthos and Anthos clusters on VMware.
For more information, see the Google Cloud Support documentation.
Requirements for Anthos clusters on VMware Support
To effectively troubleshoot business-critical incidents, you must:
- Check that the environment is current with the published end-of-support timeframes (see Version Support Policy below).
- Enable Cloud Logging and Cloud Monitoring for system components (for more details, see the Support tools section).
- When you open a support case, provide a configuration snapshot using the
gkectl diagnose snapshotcommand.
To troubleshoot a Anthos clusters on VMware incident, Google Cloud Support relies on three pieces of information:
- Your environment's configuration
- Logs from your admin and user clusters
- Metrics from your admin and user clusters
When you open a support case, you are asked to run the
gkectl diagnose snapshot --seed-config command and attach the resulting
tarball to the support case.
gkectl diagnose snapshot --seed-config captures
information about Kubernetes and your nodes.
The tool is highly configurable and includes several predefined scenarios. You can also pass a YAML file with a customized set of information to gather. To learn more, refer to Diagnosing Clusters.
You can add an
excludeWords field to your configuration file to omit
sensitive or confidential information. Be sure to carefully review the
information captured by the tool. Highly confidential or sensitive information
should not be attached to your support case.
When you create a new Anthos clusters on VMware cluster, Cloud Logging agents are enabled by default and scoped only to system-level components. This replicates system-level logs into the Google Cloud project associated with the cluster. System-level logs are from Kubernetes pods running in one of five namespaces:
Logs can be queried from the Cloud Logging console.
For more details, see Logging and Monitoring.
In addition to logs, metrics are also captured by the Cloud Monitoring agent. This replicates system-level metrics into the Google Cloud project associated with the cluster. System-level metrics are from Kubernetes pods running in the same namespaces listed in Logs.
For more details, see Logging and Monitoring.
How we troubleshoot your environment
Here is an example of a typical support incident:
- Someone—for example, the cluster administrator—opens a support case via
Cloud Console or the Google Cloud Support Center, and selects
Anthos and Anthos clusters on VMware as Category and Component,
respectively. They enter the information required and attach the output of
gkectl diagnose snapshotto the case.
- The support case is routed to a Technical Support Engineer specializing in Anthos clusters on VMware.
- The support engineer examines the contents of the snapshot to gain context of the environment.
- The support engineer examines the logs and metrics in the Google Cloud project, entering the support case ID as the business justification, which is logged internally.
- The support engineer responds to the case with an assessment and recommendation. The support engineer and the user continue troubleshooting until they come to a resolution.
Collaborative Support Partners
Google maintains collaborative support relationships with select partners to deliver a more seamless support experience for Anthos clusters on VMware. With these relationships, Google is able to collaborate closely with that partner on behalf of our shared customers.
To benefit from Collaborative Support, you must maintain support agreements with both Google and the partner in question.
Google currently has a collaborative support relationship in place with the partners specified on the Collaborative Support Partners page.
Data about support issues may be shared with Collaborative Support Partners, as described in Google's Technical Support Services Guidelines.
What does Google support?
Generally, the Cloud Support team supports all software components shipped as part of Anthos clusters on VMware. The table below details this further:
|GCP Support||Collaborative Support||Not Supported|
|Kubernetes and the container runtime
||VMware vSphere (vCenter Server and ESXi)
||VMware products beyond vSphere
|Canonical Ubuntu for guest/node OS
||F5 BIG-IP load balancers
||Customer code (see Developer Support below)
||Hardware and hyper-converged infrastructure solutions as listed in the Collaborative Support Partners page
||Customer choice of host OS
||Physical server, storage, and network
|Calico and related network policies
||External DNS, DHCP, and identity systems
||Calico Enterprise Edition
|Prometheus and Grafana
|Stackdriver Monitoring, Stackdriver Logging, and Stackdriver agents
|Identity federation with OIDC compliant providers
|Hub, Connect, and the Connect Agent
|Cloud Run / Knative
|Bundled LoadBalancer (Seesaw)
Version Support Policy
To learn about the overall version support policy, see the Anthos support page
Shared Responsibility Model
Running a business-critical production application on Anthos clusters on VMware requires multiple parties to carry different responsibilities. These responsibilities are described at Anthos shared responsibility.
Google does not provide support for application workloads running on Anthos clusters on VMware. However, we do provide best-effort developer support to ensure your developers can easily run applications on Anthos clusters on VMware. We believe that engaging earlier during development can prevent critical incidents later in the deployment.
This Developer Support is available to customers with a paid support package and is treated at a priority level 3 for an issue blocking a launch, or at priority level 4 for general consultation. In this classification, priority level 0 is the highest priority.