Modify the Cloud Native Configuration to Use Domain Names

Before migrating from a bare metal deployment, configure qualified domain names (FQDNs) that reflect the virtual IPs (VIPs) of the MATRIXX Engines in the cloud native deployment so that they can communicate while in a hybrid environment.

About this task

Cloud Native VIP Domain Names lists domain names (prefixes) that are needed for the deployment. Use domain names with these prefixes in the following procedure.

Table 1. Cloud Native VIP Domain Names
Engine Domain Names
E1 vip3.proc.domain_name

vip3.pub.domain_name

E2 vip4.proc.domain_name

vip4.pub.domain_name

Procedure

  1. Stop the cloud native deployment by deleting the services and the namespace with commands similar to the following:
    kubectl delete service proc-cls-s1e2-udp --namespace matrixx
    kubectl delete service publ-cls-s1e2-udp --namespace matrixx
    kubectl delete service proc-cls-s1e2-tcp --namespace matrixx
    kubectl delete service publ-cls-s1e2-tcp --namespace matrixx
    kubectl delete ns matrixx
  2. In the Helm values file for the cloud native deployment, specify the domain names for the first cloud native engine (E1) with the global.topology.domains[m].subdomains[n].engines[x].processing.externalAddress property:
    engines:
            # Engine 1
            - id: 1
              useDynamicIPs: false
              external: true
              processing:
                externalAddress: vip3.proc.domain_name
              publishing:
                externalAddress: vip3.pub.domain_name
  3. Also specify the domain names for the second cloud native engine (E2) with the global.topology.domains[m].subdomains[n].engines[x].processing.externalAddress property:
    engines:
            # Engine 2
            - id: 2
              useDynamicIPs: false
              external: true
              processing:
                externalAddress: vip4.proc.domain_name
              publishing:
                externalAddress: vip4.pub.domain_name
  4. Save and close the Helm values file.
  5. Apply the configuration with a helm install command similar to the following:
    helm install ag1 your_repository_domain/matrixx --version mtx_version -f values.yaml --namespace matrixx