Embedded Harbor Registry

[nachogonzalez]

Hello, hope all is well.
We are planning implementing Kubernetes and I have to analyze different vendors.
One of them is tanzu.

The application which we are going to run has the following requirements:
- Harbor Image Registry
- Jenkins CI/CD
- Nginx Ingress controller.

Now, I don't have NSX-T nor vSAN in that environment and I don't think I'm going to get it.
I was reading that we can use Tanzu Kubernetes Cluster on vSphere with the basic tanzu license and it doesn't require NSX-T nor vSAN but a plugin.

When it comes to harbor this article says "Note:To use the embedded Harbor Registry, you must deploy the Supervisor Cluster with NSX-T Data Center as the networking solution."

If I don't have NSX-T, is there any other way I can deploy harbor?

[reynolds73501]

Once the embedded Harbor Registry is enabled on the Supervisor Cluster, the Tanzu Kubernetes Grid Service will install onto the Tanzu Kubernetes cluster nodes the root CA certificate for the registry instance. This certificate is installed on both new clusters and on existing clusters (by way of a reconciliation loop). From there you can run images on the cluster by specifying the private registry in the workload YAML. Mi Ocado

[simonemorellato]

You can deploy Open Source Harbor via Helm https://goharbor.io/docs/2.5.0/install-config/harbor-ha-helm/

[DCasota]

Hi @simonemorellato,

Question about your advice.

In reference to https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-5B0373CA-5379-47AF-9284... "The embedded Harbor Registry requires that the Supervisor Cluster is configured to use NSX-T networking. As an alternative to the embedded Harbor Registry, or in addition to, you can configure Tanzu Kubernetes clusters to use an external private container registry."
Hence, without NSX-T, embedded Harbor Registry is not an option at all.

Customers with vSphere Enterprise Plus And Tanzu Basic per-CPU licensing use the open source flavor of Harbor to provision a private container registry, right?
Now, in doc https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.4.3/rn/vmware-tanzu-kubernetes-grid-143-re... the embedded harbor registry version supported is 2.2.3. 
Are there interoperability checks planned? e.g. https://interopmatrix.vmware.com/Interoperability would be nice.