This short video will demonstrate how to deploy the embedded Harbor Image Registry in vSphere with Kubernetes. It will highlight the different PodVMs used for Harbor, as well as the Persistent Volumes required by some of the PodVMs. The demo will look at the integration between namespaces created in vSphere with Kubernetes and the Harbor projects. I will also show how to download the CA certificate to a client to enable remote access to Harbor. Finally, I will show how to tag and push some images up to the image registry.
This short video will demonstrate how to create a new namespace in vSphere with Kubernetes, including Permissions, Storage and Resource Limits. This namespace concept allows vSphere with Kubernetes to implement a type of multi-tenancy, where vSphere resources can be divided up and allocated to individual developers or teams of developers. Thus it is quite a bit different to a native Kubernetes namespace. The video also looks at Harbor Image Registry integration, where a new Harbor project is created per namespace. It also shows where to find details about Kubernetes Compute, Storage and Network artifacts associated with the namespace.
I’m sure most readers will be somewhat familiar with VMware’s Project Pacific at this point. It really is the buzz of VMworld 2019. If I had to describe Project Pacific in as few words as possible, it is a merging of vSphere and Kubernetes (K8s) with the goal of enabling our customers to deploy new, next-gen, distributed, modern applications which may be comprised of container workloads or combined container and virtual machine workloads. Not only that, we also need to provide our customers with a consistent way of managing, monitoring and securing these new modern applications. This is where Project…