The following items are examples of tasks which are covered by VMware Support:
In Scope | |
---|---|
Installation | Yes |
Usage & Configuration | Yes |
Kubernetes Set Up & Configuration | Yes [1] |
Diagnosis of Build Problems | Yes [2] |
Tanzu Stack Images | Yes |
Installation, configuration and usage of the Stack operator | Yes [3] |
Bug reporting | Yes |
Bug Fix | Yes [4] |
The following items are examples of tasks which are not covered by VMware Support:
In Scope | |
---|---|
Debugging custom code/applications | No |
Load/Performance/Stress Testing of Tanzu Build Service | No |
Third-party products and add-ons | No |
Community and custom buildpacks | No |
Forked, modified or custom compiled versions of Tanzu Cloud Native Buildpacks | No |
Best Practices for Application architecture, design, guidance | No [5] |
[1] - Yes, but only when VMware Tanzu Kubernetes Grid is being used. If the Kubernetes cluster being used was installed using another vendor's tools, then it is out of scope and not supported.
[2] - VMware Support will assist in troubleshooting failed builds but is not responsible for resolving failed build issues, unless the problem is within Tanzu Build Service, kpack or a supported Cloud Native Buildpack.
[3] - VMware Support will support the Stack operator and process of creating stack images. Customer may reach out to the VMware Tanzu Services team if they need more help creating custom stacks.
[4] - Bug fixes are prioritized by VMware Tanzu Engineering with input from VMware Support and our customers. There is no guarantee of an immediate fix & VMware Support retains the right to close out support tickets if a fix is not immediate.
[5] - VMware Support can help to troubleshoot specific installation issues or answer questions. It is out of scope for VMware Support to provide guidance around your environment, design and installation architecture. Please reach out to the VMware Tanzu Services team for help in these areas.
The Information in this FAQ is not promised or guaranteed to be correct, current, or complete and this FAQ may contain technical inaccuracies or typographical errors. VMware by Broadcom assumes no responsibility (and expressly disclaims responsibility) for updating this FAQ to maintain current information or to ensure the accuracy or completeness of any posted information. Accordingly, you should confirm the accuracy and completeness of all posted information before making any decision related to any products, services or other matters described in this FAQ. VMware provides no assurances that any reported problems will be resolved by VMware, even if VMware elects to provide information with the goal of addressing a problem. ALL INFORMATION, SOFTWARE, PRODUCTS, MATERIALS, AND SERVICES PROVIDED IN THIS FAQ ARE PROVIDED “AS IS” AND “WITH ALL FAULTS” WITH NO WARRANTIES OR GUARANTEES OF ANY KIND. VMWARE EXPRESSLY DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW ALL EXPRESS, IMPLIED, STATUTORY OR OTHER WARRANTIES, GUARANTEES AND REPRESENTATIONS, INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR USE OR PURPOSE, TITLE AND NON-INFRINGEMENT OF PROPRIETARY AND INTELLECTUAL PROPERTY RIGHTS, AND WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, VMWARE MAKES NO WARRANTY THAT THE INFORMATION IN THIS FAQ WILL MEET YOUR REQUIREMENTS OR THAT THIS FAQ WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR FREE OR THAT THE SERVICES WILL MEET (OR ARE DESIGNED TO MEET) YOUR BUSINESS REQUIREMENTS.