The steps in this section are required for Kubernetes-based environments only


For Kubernetes-based deployments, follow the below steps to integrate deployment of VSP components in the CD phase and set up the Application Pod:

  1. The vsp_vdt_cd tool is downloaded to the directory (vsp/cms) created during CMS installation:

    1. cd <Application_yamlDirectory>



    2. Copy the file: vsp_vdt_cd from the directory: vsp/cms to the directory: Application_yamlDirectory

    3. chmod +x vsp_vdt_cd



    4. Copy the required SKU fragment file from  the directory that stores CMS yaml files.

      cp ../vsp_sidecar/vsp_sidecar_frag.yaml



  2. Modify the application yaml file to integrate the required VSP configurations into the application yaml file:

    1. For help on the tool usage:

      ./vsp_vdt_cd -h



    2. Execute the script using the below command:

      ./vsp_vdt_cd [--alpine] <Application_yaml_filename> <VSP Sidecar YAML fragment filename> <Customer_BaseContainerName> <vRule Engine Configuration> <vsp-host-configmap>


      1. --alpine  (Optional) - This parameter is used if VSP Host is enabled on an alpine-based application container

      2. <VSP Sidecar YAML fragment filename> -  This parameter is not required if VSP Controller is deployed as In-Application Container. Provide a single '-' (dash) in such cases

      3. <vRule Engine Configuration> -  Provide “0” for Embedded vRule Engine and “1” for Remote vRule Engine (Refer vRule Engine Configuration of VSP Architecture for more information)

      4. <vsp-host-configmap> -  kubernetes configmap filename generated in Step 2 above. If application has gone through the VSP_VDT_CI tool, then, provide a single '-' (dash)

      Picture 16

    3. vsp_vdt_cd tool produces a modified version of the application yaml file with the required configurations for VSP Controller and other required environment variables.

      The file name is <Application_yaml_filename>-vsp.yaml

  3. Proceed to Section Application Deployment With VSP Components