APPLICATION POD SETUP (CD PHASE)
NOTE:
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:
-
The vsp_vdt_cd tool is downloaded to the directory (vsp/cms) created during CMS installation:
-
cd <Application_yamlDirectory>
-
Copy the file: vsp_vdt_cd from the directory: vsp/cms to the directory: Application_yamlDirectory
-
chmod +x vsp_vdt_cd
-
Copy the required SKU fragment file from the directory that stores CMS yaml files.
cp ../vsp_sidecar/vsp_sidecar_frag.yaml
-
-
Modify the application yaml file to integrate the required VSP configurations into the application yaml file:
-
For help on the tool usage:
./vsp_vdt_cd -h
-
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>
-
--alpine (Optional) - This parameter is used if VSP Host is enabled on an alpine-based application container
-
<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
-
<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)
-
<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)
-
-
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
-
-
Proceed to Section Application Deployment With VSP Components