Instantiate TPS Container Network Function

The section provides procedure to instantiate applications in
VMware Telco Cloud Service Assurance
using
tps.csar
file.
  1. Launch
    VMware Telco Cloud Automation
    and navigate to
    Catalog
    Network Function
    .
  2. Select
    TPS CNF
    , click the vertical ellipsis (⋮) and then click
    Instantiate
    .
  3. Under
    Inventory Detail
    , enter
    Name
    and select the
    VMware Tanzu Kubernetes Grid
    workload cluster on which you want to deploy it.
  4. Under
    Helm Charts
    , enter the
    Namespace
    as
    tps-system
    and select
    Repository URL
    as
    <oci://<registryRootUrl>>
    .
    Use the same
    registryRootUrl
    as specified during the
    push artifacts to registry
    step.
  5. Click
    Next
    .
  6. Under
    Network Function Properties
    , click
    Next
    .
  7. In the
    Inputs
    section, update the following parameters:
    1. Set
      registryRootUrl
      to the same value as the
      --registry-url
      parameter of the installer script in the Push Artifacts to Registry topic.
    2. For the
      imagePullSecret (Optional)
      field, do not change the default value.
    3. Set cloud as
      tkg
      .
    4. You need not update the following optional parameters:
      • domainName (Optional)
      • clusterName (Optional)
      • storageClass (Optional)
    5. Set product as
      tcsa
      .
    6. Generate the
      values-merged.yaml
      file by performing the following steps.
      1. Configure the
        values-user-overrides.yaml
        file for the production footprint. For more information, see Configuration Production Footprint for TCA.
      2. Generate the
        values-merged.yaml
        file by running the command mentioned in the Run tcxctl merge Command section.
      3. Copy the
        values-merged.yaml
        file that is generated in the previous step to your local machine used to access
        VMware Telco Cloud Automation
        .
      4. Update the
        postgres.helmOverrides.updateNamespace.enabled
        to true in the
        values-merged.yaml
        file downloaded to your local machine.
        The following example is a code snippet from the
        values-merged.yaml
        file.
        postgres: enabled: true helmOverrides: updateNamespace:
        enabled: true
        (set namespace to true before upgrade) oldNamespace: default
    7. Upload the
      values-merged.yaml
      file generated to
      VMware Telco Cloud Automation
      by using the
      Browse
      option in the
      Input
      tab of the Instantiation wizard.
    DemoInputs
  8. Under
    Review
    , click
    Next
    .DemoReview
  9. Click
    Instantiate
    .
  10. Once the Instantiation is successful, check the VMware TCx platform services (TPS) status by running the following command from deployment VM:
    root [ ~/upgrade/tcx-deployer/scripts ]# kubectl get tcxproduct -A
    OR
    root [ ~/upgrade/tcx-deployer/scripts ]# kubectl get apps -A
    For all the apps, the reconciliation status must be successful.
    root [ ~/upgrade/tcx-deployer/scripts ]# kubectl get tcxproduct -A NAMESPACE NAME STATUS READY MESSAGE AGE tps-system tcx-platfor-9dfce-goibb-tcx-platform-services updateCompleted True All App CRs reconciled successfully 34h
    After successful deployment, you can launch the VMware Telco Cloud Service Assurance UI. For more information, see Accessing UI topic.