Discover current Supervisor Services offered to support modern applications through vSphere Services. New services will be added over time with the goal to continue to empower your DevOps communities.
Prior to vSphere 8 Update 1, the Supervisor Services are only available with Supervisor Clusters enabled using VMware NSX-T. With vSphere 8 U1, Supervisor Services are also supported when using the vSphere Distributed Switch (VDS) networking stack.
Supervisor Service | vSphere 7 | vSphere 8 |
---|---|---|
vSphere Kubernetes Service | ❌ * | ✅ requires vSphere 8.0 Update 3 or later |
Consumption Interface | ❌ | ✅ requires vSphere 8.0 Update 3 or later |
vSAN Data Persistence Platform Services - MinIO | ✅ | ✅ |
Backup & Recovery Service - Velero | ✅ | ✅ |
Certificate Management Service - cert-manager | ❌ | ✅ |
Cloud Native Registry Service - Harbor | ❌ * | ✅ |
Kubernetes Ingress Controller Service - Contour | ❌ | ✅ |
External DNS Service - ExternalDNS | ❌ | ✅ |
NSX Management Proxy | ❌ | ✅ requires vSphere 8.0 Update 3 or later with Supervisor Clusters enabled using VMware NSX-T |
Data Services Manager Consumption Operator | ❌ | ✅ requires vSphere 8.0 Update 3 or later with additional configuration. Please contact Global Support Services (GSS) for the additional configuration |
* The embedded Harbor Registry and vSphere Kubernetes Service features are still available and supported on vSphere 7 and onwards. |
Log in to support.broadcom.com, Go to Enterprice Sofware.
Select My Downloads on the left hand side navigation.
If you are looking to download VMware Private AI Services search that term, alternatively search for vSphere Supervisor Services.
Next navigate to the service of choice and version you are looking to install.
Click on the download icon on the service definition as well as any additional files (such as values.yaml files, etc.)
You can now proceed to install your service.
Please check Interoperability Matrix to find out which version is compatible with which Supervisor version.
VMware vSphere Kubernetes Service (VKS, formerly known as the VMware Tanzu Kubernetes Grid Service or TKG Service) lets you deploy Kubernetes workload clusters on the vSphere Supervisor (formerly known as the vSphere IaaS control plane). Starting with vSphere 8.0 Update 3, VKS is installed as a Supervisor Service. This architectural change decouples VKS from Supervisor releases and lets you upgrade VKS independently of vCenter Server and Supervisor.
The Interoperability Matrix shows each VKS version below, including compatible Kubernetes releases and the vCenter Server versions containing compatible Supervisor versions. Note that some compatible Kubernetes releases may have reached End of Service; refer to the Product Lifecycle tool (Division: "VMware Cloud Foundation", Product Name: "vSphere Kubernetes releases") to view End of Service dates for Kubernetes releases.
Provides the Local Consumption Interface (LCI) for Namespaces within vSphere Client. This also includes the Single Sign On (SSO) component required by the Cloud Consumption Interface (CCI) in Aria Automation within VMware Cloud Foundation.
The minimum required version for using this interface is vSphere 8 Update 3.
Installation instructions can be found here in VMware documentation.
IMPORTANT NOTICE: Occasionally, the plug-in may fail to load on the initial attempt. To check if the plug-in has loaded correctly, click the vSphere Client menu icon, then to Administration -> Client -> Plug-ins. Check the Status column of the Namespace UI plug-in, and in case you see a "Plug-in configuration with Reverse Proxy failed." Message, reinstall the plug-in.
SSO OSS Refer to the Open Source Tab
vSphere with Tanzu offers the vSAN Data Persistence platform. The platform provides a framework that enables third parties to integrate their cloud native service applications with underlying vSphere infrastructure, so that third-party software can run on vSphere with Tanzu optimally.
Available vDPP Services
Velero vSphere Operator helps users install Velero and its vSphere plugin on a vSphere with Kubernetes Supervisor cluster. Velero is an open source tool to safely backup and restore, perform disaster recovery, and migrate Kubernetes cluster resources and persistent volumes.
This is a prerequisite for a cluster admin install.
ClusterIssuers are Kubernetes resources that represent certificate authorities (CAs) that are able to generate signed certificates by honoring certificate signing requests. All cert-manager certificates require a referenced issuer that is in a ready condition to attempt to honor the request.
CA Cluster Issuer Sample values.yaml
Harbor is an open source trusted cloud native registry project that stores, signs, and scans content. Harbor extends the open source Docker Distribution by adding the functionalities usually required by users such as security, identity and management. Having a registry closer to the build and run environment can improve the image transfer efficiency. Harbor supports replication of images between registries, and also offers advanced security features such as user management, access control and activity auditing.
Harbor Sample values.yaml
Sample values can be downloaded from the same location as Service yamls.
Contour is an Ingress controller for Kubernetes that works by deploying the Envoy proxy as a reverse proxy and load balancer. Contour supports dynamic configuration updates out of the box while maintaining a lightweight profile.
Contour Sample values.yaml
ExternalDNS publishes DNS records for applications to DNS servers, using a declarative, Kubernetes-native interface. This operator connects to your DNS server (not included here). For a list of supported DNS providers and their corresponding configuration settings, see the upstream external-dns project.
ExternalDNS data values.yaml
source=contour-httpproxy
in the configuration values. An incomplete example of the service configuration is included below. Make sure to setup API access to your DNS server and include authentication details with the service configuration.deployment:
args:
- --source=contour-httpproxy
- --source=service
- --log-level=debug
Validated Supported DNS Server Example:
NSX Management Proxy is for Antrea-NSX adapter in Kubernetes clusters deployed by VKS to reach NSX manager. We recommend to use NSX Management Proxy when there is isolation between management network and workload network and the Kubernetes clusters cannot reach NSX manager.
NSX Management Proxy Sample values.yaml
nsxManagers
with your NSX Manager IP(s).Note: NSX Management Proxy is supported in vSphere 8.0 Update 3 when Supervisor Clusters are enabled using VMware NSX-T networking stack under following configurations:
The Data Services Manager(DSM) Consumption Operator facilitates native, self-service access to DSM within a Kubernetes environment. It exposes a selection of resources supported by the DSM provider, allowing customers to connect to the DSM provider from Kubernetes. Although the DSM provider does not currently support tenancy natively, the DSM Consumption Operator enables customers to seamlessly integrate their existing tenancy model, effectively introducing tenancy into the DSM provider.
Data Services Manager Consumption Operator Sample values. yaml
Sample values can be found at the same location as service yaml
v9.0.0.0: For details about each of the required properties, see the configuration details page.
v2.2.1 For details about each of the required properties, see the configuration details page.
v2.2.0 For details about each of the required properties, see the configuration details page.
v1.2.0 For details about each of the required properties, see the configuration details page.
Installation Note:
Upgrade Note:
Secret Store Service is a comprehensive solution for managing secrets in vSphere, ensuring the security and integrity of the environment and providing a robust and scalable solution for securely injecting secrets into workloads.
Secret Store Service sample values.yaml
storageClassName
with storage policy name.The following Supervisor Services Labs catalog is only provided for testing and educational purposes. Please do not use these services in a production environment. These services are intended to demonstrate Supervisor Services' capabilities and usability. VMware will strive to provide regular updates to these services. The Labs services have been tested starting from vSphere 8.0. Over time, depending on usage and customer needs, some of these services may be included in the core product.
WARNING - By downloading and using these solutions from the Supervisor Services Labs catalog, you explicitly agree to the conditional use license agreement.
The Argo CD Operator manages the entire lifecycle of Argo CD and its components. The operator aims to automate the tasks required to operate an Argo CD deployment. Beyond installation, the operator helps automate the process of upgrading, backing up, and restoring as needed and removes the human toil as much as possible. For a detailed description of how to consume the ArgoCD Operator, see the ArgoCD Operator project.
ArgoCD Operator Sample values.yaml
for v0.12.0 - values.yaml
ArgoCD Operator Sample values.yaml
for v0.8.0 - None
values.yaml
for the latest version has been provided above. This operator requires minimal configurations, and the necessary pods get deployed in the svc-argocd-operator-domain-xxx
namespace.External Secrets Operator is a Kubernetes operator that integrates external secret management systems like AWS Secrets Manager, HashiCorp Vault, Google Secrets Manager, Azure Key Vault, IBM Cloud Secrets Manager, CyberArk Conjur, etc. The operator reads information from external APIs and automatically injects the values into a Kubernetes Secret. For a detailed description of how to consume External Secrets Operator, visit External Secrets Operator project
External Secrets Operator Sample values.yaml
- None
values.yaml
. This operator requires minimal configurations, and the necessary pods get deployed in the svc-external-secrets-operator-domain-xxx
namespace.The RabbitMQ Cluster Kubernetes Operator provides a consistent and easy way to deploy RabbitMQ clusters to Kubernetes and run them, including "day two" (continuous) operations. RabbitMQ clusters deployed using the Operator can be used by applications running on or outside Kubernetes. For a detailed description of how to consume the RabbitMQ Cluster Kubernetes Operator, see the RabbitMQ Cluster Kubernetes Operator project.
RabbitMQ Cluster Kubernetes Operator Sample values.yaml
-
svc-rabbitmq-operator-domain-xx
namespace.A Golang-based Redis operator that oversees Redis standalone/cluster/replication/sentinel mode setup on top of Kubernetes. It can create a Redis cluster setup using best practices. It also provides an in-built monitoring capability using Redis-exporter. For a detailed description of how to consume the Redis Operator, see the Redis Operator project.
Redis Operator Sample values.yaml
-
values.yaml
. This operator requires minimal configurations, and the necessary pods get deployed in the svc-redis-operator-domain-xxx
namespace.KEDA is a single-purpose and lightweight component that can be added into any Kubernetes cluster. KEDA works alongside standard Kubernetes components like the Horizontal Pod Autoscaler and can extend functionality without overwriting or duplication. With KEDA you can explicitly map the apps you want to use event-driven scale, with other apps continuing to function. This makes KEDA a flexible and safe option to run alongside any number of any other Kubernetes applications or frameworks. For a detailed description of how to use KEDA, see the Keda project.
KEDA Sample values.yaml
-
values.yaml
. This operator requires minimal configurations, and the necessary pods get deployed in the svc-kedaxxx
namespace.ScaledObject
to scale an NGINX deployment here.