Checkout how to deploy and configure Harbor and Contour as Supervisor Services on your vSphere IaaS control plane environment. Harbor is an open source cloud-native registry that you can use with your workloads running on vSphere IaaS control plane. 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.
You can use Contour as a Supervisor Service as an Ingress controller for your applications. Contour is also a requirement for running the Harbor Supervisor Service.
Note:
Supervisor Services are supported on single-cluster
Supervisors that run on either VDS or NSX networking stacks. You cannot deploy
Supervisor Services on three-zone
Supervisors.
Harbor as a
Supervisor Service provides the following capabilities and features:
- The latest version of the Harbor open -source registry.
- Access to Harbor with the admin and root accounts.
- Full feature-parity with the upstream Harbor registry.
- Access to Harbor through Ingress (Contour) using DNS.
Note: When deployed, both Harbor and Contour
Supervisor Services create
vSphere Pods in the
vSphere Namespaces created for these services. These
vSphere Pods are required by the services to operate. You cannot deploy
vSphere Pods outside of
Supervisor Services on a
Supervisor running on the VDS networking stack or a three-zone
Supervisor. You can only deploy
vSphere Pods for generic use on a single-cluster
Supervisor deployed with NSX.
