Here we are at the fifth post in our blog series. In this post, I’ll discuss how to download and prepare TMC Self-Managed artifacts for installation in a harbor registry.
If you have landed on this post directly by mistake, I encourage you to read the previous blog posts of this series using the below links:
1: TMC Self-Managed – Introduction & Architecture
2: Configure DNS for TMC Self-Managed
3: Configure OIDC Complaint Identity Provider (Okta)
4: Install Cluster Issuer for TLS Certificates
Tanzu/Kubernetes supports a wide variety of image registry solutions including JFrog, Docker Hub, Amazon Elastic Container Registry, VMware Harbor, etc. for storing the application images that you deploy on the workload clusters. However, TMC Self-Managed only supports the Harbor image registry at the time of writing this post. The harbor registry must meet the following requirements:
- A minimum storage of 20 GB is recommended for Harbor.
- Authenticated registries are not supported. A public project on Harbor is required
In my lab, I have deployed a Harbor registry on a CentOS-7 VM following the instructions outlined in this article. I have a project dedicated to storing TKG installation binaries and Tanzu packages.
To configure the Harbor registry to be used for TMC Self-managed, follow the instructions outlined below.
Step 1: Download the TMC Self-managed installation bundle from here. Upload the installation bundle on your bootstrap machine.
Step 2: Create a public project in your image repository. Your image repository must have at least 10 GB of quota to accommodate the TMC-SM installation images.
Step 3: Extract the TMC Self-Managed installation bundle.
|
1 2 3 |
# mkdir tmcsm # tar -xvf bundle-1.0.1.tar -C ./tmcsm |
Step 4: Add the root CA certificate for Harbor to the /etc/ssl/certs path of the bootstrap machine. This enables the image push to the Harbor repository.
Note: When you install Harbor, you generate a self-signed CA certificate to be used with Harbor. Copy this certificate from the Harbor VM to your bootstrap VM using scp or a similar utility.
Step 5: Push the TMC Self-managed installation images to the project that you created in Step 2.
|
1 2 3 4 5 |
# cd tmcsm # ./tmc-sm push-images harbor --project {{harbor-instance}}/{{harbor-project}} --username {{username}} --password {{password}} Example: ./tmc-sm push-images harbor --project registry.vstellar.lab/tmcsm101 --username admin --password VMware1! |
Note: If your image registry uses self-signed certificates, then ensure that you have configured docker running on your bootstrap machine to trust the certificate. Instructions for importing the certificate are outlined here.
When the images are being pushed to the Harbor registry, the screen will show you the progress of the upload.
After the artifacts have been uploaded, the installer provides you with the commands that you need to execute to begin the installation of TMC Self-Managed.
And that’s it for this post. You are now ready to install TMC Self-Managed. I will cover the installation steps in the next post of this series. Stay tuned!!!
I hope you enjoyed reading this post. Feel free to share this on social media if it is worth sharing.