VMware Telco Cloud Automation version 2.3 onwards, the Open Container Initiative (OCI) repositories are supported. In the previous releases, if you have deployed the CNF instances using Chartmuseum charts, you can update the CNF instances to OCI repositories.
Note:
- If your CNF is using Chartmuesum, and Harbor is upgraded to a version that does not support Chartmuesum, then the CNF LCM operations fail. In such a scenario, you are alerted with the message, “CNF is not upgraded to OCI-based helm charts, all consecutive CNF LCM operations may fail.”
- After the Chartmuesum Helm charts are migrated to OCI, you can update the CNF Helm repository.
Before updating the CNF repository from Chartmuseum to OCI, you must perform the following:
- Convert the ChartMuseum charts to the OCI format.
- Upload the OCI charts to a Harbor.
- Define one or more partner systems in TCA for OCI repositories.
To update the CNF repository from Chartmuseum to OCI, perform one of the following:
- Reconfigure the CNF to point to the OCI repository instead of ChartMuseum. See Reconfigure a Container Network Function.
- Upgrade the CNF to point to the OCI registry. See Upgrade a CNF.
Note: Harbor with OCI repositories is listed in
oci:// URI and the Harbor with ChartMuseum repositories is listed in
https:// URI.
After updating the CNF repository from Chartmuseum to OCI, ensure the following:
- The CNF reconfigure or upgrade operation is successful.
- The alarm is cleared on the TCA instance, which indicates that all the CNF charts are pointing to the OCI repositories.
Recommendations:
- If Harbor is upgraded in place, reconfigure or upgrade the CNF when chartmuseum is still supported for the Harbor. This ensures that the charts are available both in Chartmuseum and OCI repositories so that auto rollback can be executed in case of CNF upgrade or reconfigure failures.
- If Harbor is upgraded by creating a new Harbor instance, retain the existing Harbor version until the CNF migration is completed.
