CNE GCP Ready: Configuring the Cloud Native Experience
After bootstrapping the Cloud Native Experience (CNE) environment, configure the platform components required for your deployment.
CNE follows a GitOps approach. Infrastructure and application settings are defined in your GitOps repository, and changes committed to the repository are automatically synchronized to the cluster through Argo CD.
Configuration typically involves exposing services through domains and TLS certificates, managing secrets, configuring backups, configuring overlays, and operating the platform through GitOps workflows.
Key configuration topics include:
-
Accessing the Kubernetes Cluster – Connect to private GKE clusters through Google Cloud Connect Gateway.
-
Adding OSGi Modules or Client Extensions With Overlays – Apply OSGi modules, client extensions, and other customizations without rebuilding the Liferay image.
-
Cleaning Up the Environment – Remove the CNE deployment and reclaim GCP resources.
-
Configuring Argo CD Domain and TLS – Expose the Argo CD server through a custom domain and configure TLS certificates for secure access.
-
Configuring Liferay Domains and TLS – Configure public access to the Liferay environment and manage TLS certificates.
-
Incremental Backup and Restore – Configure scheduled backups and restore environments using GitOps-managed workflows.
-
Managing Secrets and Licenses – Store GitOps credentials, TLS certificates, and Liferay license files.
-
Migration Paths – Choose migration approaches for moving databases and document libraries into GCP environments.
- Using Elasticsearch – Configure Elasticsearch clusters for Liferay search workloads.