Push Artifacts to Registry

To push artifacts to the Harbor registry, run the script from $TCSA_WORK_SPACE/tcx-deployer/clis.

For Self-signed certificates for Harbor, follow the below procedure:

• Copy the Harbor Certs file in /etc/ssl/certs directory.
• If you do not have permission to the directory /etc/ssl/certs, then put the Harbor Cert in any other location where you have access, and run the below command:

  trust anchor <path-to-cert>

  • If trust command is not available, then install p11-kit-trust package which contains trust command.

Note: If you are using secure Harbor registry, ensure that you perform the steps mentioned in Secure Harbor Registry for public or self-signed certificates.

If you do not want to specify the registry username and password in the installation script, perform Docker login. To login to Docker, run the following command:

docker login <harbor-fqdn>

Ensure that the --registry-password does not have the comma character in it. If the comma is used, escape it using the backslash.

• Set the following variable to false so that the charts are pushed with the OCI compliant in VMware Telco Cloud Service Assurance 2.3. By default, PUSH_TO_CHART_REPO=false. If PUSH_TO_CHART_REPO=true, you must set it to false before deployment.

  PUSH_TO_CHART_REPO=false

  Note: If the Harbor registry is OCI compliant, then set PUSH_TO_CHART_REPO=false, otherwise, set PUSH_TO_CHART_REPO=true to push the charts in the non-OCI format.
• Run the following script to push artifacts to registry.

  root [ ~/base/tcx-deployer/ ]# ./tcxctl push --artifacts-path $TCSA_WORK_SPACE/tcx-deployer/ --registry <harbor-registry-fqdn>/<project-name> --registry-password <your-registry-password> --registry-username <your-registry-username> --registry-cert <path-to-your-registry-ca-certificate-file>

  Note: The --registry-cert is an optional parameter. If you are using a private certification-based Harbor, you must pass a certificate path value to it.