TCA Features that have either been deprecated or discontinued
Environment
TCA: 3.4
TCP: 5.1
Resolution
Deprecated (final supported version):
Legacy Workflow Schemas: Retiring older v1 and v2 schemas used for Network Function and Network Service workflows in favor of modern, updated schema versions.
Legacy Resource Management (cgroupv1): Deprecating the older cgroupv1 Linux resource control mechanism as the platform transitions to modern standards.
Discontinued (no longer supported):
Older Kubernetes Versions (v1.24.10, 1.25, and 1.26) including PhotonOS 3 BYOI templates: Phasing out support to align with modern, secure releases. Existing deployments remain supported until their respective end-of-general-support dates.
ChartMuseum Helm Management: Transitioning away from legacy ChartMuseum-based Helm charts in favor of the modern Open Container Initiative (OCI) registries.
Enter Airgap repository detail directly in CaaS: Retiring the manual entry of repository details directly within the Container-as-a-Service (CaaS) interface.
Direct CaaS Harbor Integration: Centralizing registry administration by phasing out the ability to add new Harbor instances directly through the CaaS UI.
VMware NSX-v Manager (all versions)
Direct Internet Deployments (Non-Airgap): Phasing out support for environments that pull deployment artifacts directly from the public internet, shifting focus toward airgap-only deployment architectures.
Using VMware Integrated OpenStack (VIO) as a VIM in TCA
Stretched Workload Clusters: Deprecating support for standard workload clusters that span across multiple vCenter Server instances.
Public Cloud Deployments & VIM Registration: Removing support for Telco Cloud Automation deployments on public cloud services (Azure AKS, Amazon EKS), including use as VIMs for Network Function Lifecycle Management.
Management Cluster Debugging Tool (KBSCTL): Retiring the legacy KBSCTL command-line utility previously used for troubleshooting management clusters.
Third-Party Container Registries: Deprecating direct partner system integration for external registries such as Azure Container Registry (ACR) and Amazon Elastic Container Registry (ECR).
Network Slicing: Phasing out native network slicing orchestration capabilities.
Performance Management (PM) Reporting: Retiring the built-in generation of Network Function Performance Management reports.