Support for VMware Tanzu Mission Control Self-Managed
This document is a practical guide to help you understand the scope of VMware Support for VMware Tanzu Mission Control (TMC) Self-Managed. This document provides a basic outline and covers some common examples of services that are in and out of the scope of support provided by VMware. This is not a legal document. For terms of service, see VMware Terms of Service.
About Tanzu Mission Control Self-Managed
Tanzu Mission Control (TMC) Self-Managed provides customers with a consistent Kubernetes management experience. Tanzu Mission Control (TMC) Self-Managed provides a packaged, self-managed, non-SaaS deployment strategy for TMC that customers can deploy in infrastructure environments where using TMC SaaS is not an option.
In scope
The following items are examples of tasks that are covered by VMware Support for TMC Self-Managed.
| Tasks | In Scope |
|---|---|
| Troubleshooting failures when deploying TMC Self-Managed | Yes |
| Bug reporting | Yes |
| Bug fixing | Yes [1] |
| Enhancement requests | Yes [1] |
| Debugging failures when using Generally Available(GA) features of TMC Self-Managed | Yes [2] |
| Troubleshooting Issues when using API and CLI | Yes [3] |
[1] Bug fixes and enhancement requests are prioritized by VMware Engineering with input from VMware Support and our customers. There is no guarantee of an immediate fix and VMware Support retains the right to close out support tickets if a fix is not immediate.
[2] For the exact list and versions of the product, see Preparing your cluster for Tanzu Mission Control Self-Managed.
[3] The API, CLI and GUI are supported however VMware support can not assist with writing or debugging custom code that leverages these components. Also, writing or troubleshooting custom wrappers modifications or automation are out of scope of support.
Out of scope
The following items are examples of tasks that are not covered by VMware Support.
| Tasks | In Scope |
|---|---|
| Troubleshooting custom configuration and overlays | No [1] |
| Troubleshooting modified code, scripts, artifacts and utilities shipped initially with the product | No [2] |
| Experimental features | No [3] |
| Assistance with Load/performance/stress testing of TMC Self-Managed | No |
| Modified packages, templates and files shipped with TMC Self-Managed | No [2] |
| Customer built images and components which substitute components shipped with the product | No [4] |
[1] VMware Support cannot assist with reviewing customer or third-party application code or troubleshooting issues related to it. VMware can provide assistance through your solution engineer or account team representatives.
[2] Any modification to the code, scripts, artifacts and utilities shipped with TMC Self-Managed will result in an unsupported deployment. VMware recommends submitting enhancement requests if a particular functionality is needed.
[3] VMware Support will provide best effort support for beta/experiment features that are shipped in a generally available product. The goal in this case is to find and report bugs so that the feature works correctly when it is generally available. A fix for any bugs uncovered may not be available until the feature is generally available. Production and Severity 1 support are not available for beta/experimental features.
[4] Any customer built images and components that substitute a TMC Self-Managed component is out of scope of support. If it is not shipped as part of the official VMware product it is out of scope of VMware support.
