Populating the Volume with required user inputs file

After you have created a Persistent Volume, create a volume directory hierarchy on the NFS drive.

Follow the guidelines below to prepare the Volume:
  • If your stateful set deployment name is cc-app, create a directory with pod name, cc-app-0 for first pod, cc-app-1 for second and so on inside the NFS volume drive.
  • Inside each pod directory create a user_inputs sub-directory.
  • Place the following artifacts into the user_inputs directory created above:
    • JDBC driver file(s)
    • JRE certificates file(s) if secure connection is a requirement
    • configCC.properties file declaring all applicable configuration parameters described below:
      • When using SELinux, be aware that the host has no knowledge of container SELinux policy. Therefore, if SELinux policy is enforced, the host/persistence volume directory is not writable to the container. A 'Permission Denied' message will be display.
        As a work around, execute the following command to run for a proper SELinux policy type label to be attached to the host/persistence volume directory:
        $ chcon -Rt svirt_sandbox_file_t <mounted host directory>

        Populating the Volume is complete and ready to be claimed.