Running an Application with Shared Nothing Persistence on Enterprise PKS
After uploading your TIBCO BusinessEvents application Docker image with shared nothing persistence to Google Container Registry and creating the Kubernetes cluster, deploy and run your application on the Kubernetes cluster. The cluster manages the availability and connectivity of the application.
For shared nothing persistence, create a Storage Class of GCP persistent disk in the Kubernetes cluster. The StorageClass is configured in the manifest.yaml file. You can use this StorageClass to provision persistent volumes for the cache and inference agents. For more information, see "Storage Classes" in Kubernetes Documentation.
To run the Dockerized FraudDetectionStore application with shared nothing persistence, follow the instructions in the readme.html file at BE_HOME\cloud\kubernetes\PKS\cache. Typically, sample YAML files are provided to run the application. For this deployment, the sample YAML files are available at BE_HOME\cloud\kubernetes\PKS\cache\shared-nothing. For details about these sample YAML files, see Sample Kubernetes YAML Files for Applications with Shared Nothing Persistence.
Prerequisites
- The Kubernetes cluster must be deployed on Enterprise PKS. See Setting Up a Kubernetes Cluster with Enterprise PKS.
- Your TIBCO BusinessEvents application Docker image must be uploaded to the Google Container Registry. See Setting up Google Container Registry.
Procedure
What to do next
Test the application by using the external IP obtained. For example, if you have deployed the FraudDetectionStore example application with the shared nothing persistence, you can use the sample readme.html file at BE_HOME\cloud\kubernetes\PKS\cache to test the application. Use the obtained external IP in the readme.html file and follow the instructions in it to run the application.
However, if you have deployed any other sample application then update its readme.html file to test the application. Update the server address in the application readme.html file from localhost to the external IP obtained. Now, follow the instructions in the readme.html file for testing the application.