Geoserver Cloud in a nutshell

Description

The chart deploys GSCloud with enabled PGConfig capabilities, resulting in the storage of the Geoserver Catalog in a PostgreSQL database. This necessitates a dependency on the bitnami/postgres Helm chart. In order to handle database pool connections in a better way, between Geoserver components and Postgres, there is a PgBouncer setup.

Additionally, GSCloud relies on RabbitMQ as the event bus handler to facilitate communication among various GSCloud components and services. The chart specifically enables WMS, WFS, WebUI, and Rest services, incorporating the Gateway to establish a unified entry point for these services.

Given that PostgreSQL requires a persistent location for catalog definition storage, the associated bitnami chart generates a Persistent Volume Claim (PVC) that persists even after uninstalling the chart. This approach ensures continuity across different executions and deployments. If there is a need to cleanse the GSCloud catalog, including layers configurations, removing the corresponding PVC (named: data-gs-cloud-pgconfig-postgresql-0) achieves this objective. Refer to the how-tos section for guidance.

Furthermore, for the creation of distinct datastores linking to databases, shapefiles, TIFFs, or other resources, it becomes imperative to establish a mechanism for mapping these resources within the context of the PODs. This may involve enabling network policies or mapping Persistent Volumes, such as granting access to an AWS bucket, a PostgreSQL database, or simply an NFS folder.

Requirements

You need a Kubernetes cluster ! You need kubectl ! You need helm !

Check how to do that here

Running it

If you already fulfill requirements (installed tools and cluster), then it's just a matter of deploying the chart in your cluster.

helm upgrade --install gs-cloud-pgconfig .

In the How-tos section you have some other useful commands (checking your deployment, accessing the WebUI, etc)

How-To

Note: how-tos are based on local execution using a K3s cluster under the default namespace.

Download helm dependencies (optional)

No need to do it really, since charts/ folder is included in the repository (just to make it easier for those that want to get a zip file with everything inside)

helm dependency update

Deploy chart in your cluster

helm upgrade --install gs-cloud-pgconfig .

Check your deploy

kubectl get po

Then you will get something like this:

NAME                                             READY   STATUS    RESTARTS   AGE
gs-cloud-pgconfig-gsc-wms-d7f7f5dc6-rwp5k        0/1     Running   0          8s
gs-cloud-pgconfig-gsc-rest-797858fd8-7m54p       0/1     Running   0          8s
gs-cloud-pgconfig-gsc-webui-7bd45586-67wfh       0/1     Running   0          8s
gs-cloud-pgconfig-postgresql-0                   0/1     Running   0          8s
gs-cloud-pgconfig-gsc-wfs-76656dfdcd-j46gk       0/1     Running   0          8s
gs-cloud-pgconfig-pgbouncer-58b9f5f744-ztxkg     0/1     Running   0          8s
gs-cloud-pgconfig-rabbitmq-0                     0/1     Running   0          8s
gs-cloud-pgconfig-gsc-gateway-86468b8758-8m49q   1/1     Running   0          8s

Note: your deploy will be ready once all the pods are in 1/1 in ready column and status = running

Access the WebUI

kubectl port-forward svc/gs-cloud-pgconfig-gsc-gateway 9000:8080

Then open a browser and navegate to http://localhost:9000/geoserver/web/ , user: admin / pass: geoserver and you are in ! Enjoy it.

Uninstall chart

helm uninstall gs-cloud-pgconfig

Clean the catalog

kubectl delete pvc data-gs-cloud-pgconfig-postgresql-0