Page History

...

Next, Persistent Volumes and Persistent Volume claims for database configuration and exports storage are needed. They should be provisioned with around 1GB (for the database configuration) to 10GB (for exports storage) of space (this can be increased or decreased according to your needs) and ReadWriteOnce access mode is recommended. This space will be used for the workspace of the for the CTP server.

You must have a well-formatted db_config.xml present in the volume you are mounting. See the db_config.xml below for an example of one that is well-formatted. You can copy the example below into the volume you are mounting if you prefer; whatever configuration you need to do will be done within the application itself. Note that if the URL JDBC string is for MariaDB, MySQL, or Oracle, then your CTP deployment/pod should be configured with the correct JDBC adapter; if the URL JDBC string is for HyperSQL, it should start up regardless of your CTP deployment/pod configuration.

...

Create the service that can be used to access the CTP server in Kubernetes. The example shown below exposes it using a node port, which provides a stable endpoint for applications to access Virtual Assets.

apiVersion: v1
kind: Service
metadata:
  name: ctp-service
  namespace: parasoft-ctp-namespace
spec:
  selector:
    app: ctp
  type: NodePort
  ports:
  - name: http
    protocol: TCP
    port: 8080
    targetPort: 8080
    nodePort: 30000
  - name: https
    protocol: TCP
    port: 8443
    targetPort: 8443
    nodePort: 30083

Volume Mount Security Policies (Optional)

If your security policy requires applications to only write to mounted volumes, then you will need to mount the following locations:

/usr/local/parasoft/exports
/usr/local/parasoft/ctp/hsqldb
/usr/local/parasoft/ctp/logs
/usr/local/parasoft/ctp/temp
/usr/local/parasoft/ctp/webapps/em/apifiles
/usr/local/parasoft/ctp/webapps/em/backups
/usr/local/parasoft/ctp/webapps/em/license
/usr/local/parasoft/ctp/work/Catalina/localhost/em