Thank you for putting the helm chart together. It's awesome.

I don't see WPS service anywhere , when it's loaded. How do you configure or enable it in the chart?

Hello @sbrunner ,
I had to disable the Prettier check because it fails with the README.md file. In general I would like to keep prettier active for yaml files, but disable for README.md, is this possible?

Thanks in advance

Enable use of the spring.rabbitmq.virtual-host parameter while defining RabbitMQ config.

That is modifying the file geoserver_spring.yml and adding the virtual-host option.

https://github.com/geoserver/geoserver-cloud-config/blob/ccd5fbcb60d4138fe4d2bb91b434a6757d85dcd7/geoserver_spring.yml#L19-L24

For reference:
https://docs.spring.io/spring-boot/docs/current/reference/html/application-properties.html#application-properties.integration.spring.rabbitmq.virtual-host

I tried installing the geoservercloud chart at version 0.1.1, but no postgres pod/database was created. I checked the computed values with helm get values -a ... and postgres seemed to be enabled.

Downgraded the chart version to 0.0.49 with the same values input, and a postgres pod is created.

Hi!, I've found today this excellent repo, and first of all, thank you for your work and passion!
I just also installed it in my local machine by following your readme instructions, and it works. (I had problems with Minikube, but it works well with k3d for me).

Context:
I need to deploy a GeoServer in GKE to serve custom WFS layers stored in a PostGIS db that I want to deploy in GKE also.

0. Do you have some documentation about how to use this Helm in real PROD env?

1. I've noticed you already have a PostgreSQL, what is it used for? Should I create another Postgres to enable it as PostGIS and put my custom data there, or do I have to use the same PostgreSQL (enabling Geospatial) as you are providing here in order to save resources?

2. What are the PVs that should I have to add to make the data permanent in my PROD env? I guess that you have at least one PV for the Postgresql, and may another PV for Geoserver or RabbitMQ?

3. Some advice from you about the PROD security that I have to consider to use your helm project correctly?

Thank you for your answers.

Hey,

First of all thanks for creating this, we're hoping it can be usefull for what we're wanting.

I've created the below basic chart, here's the values yaml

geoservercloud:
  global:
    profile: standalone,jdbcconfig,datadir,catalog
  geoserver:
    services:
      webui:
        service:
          type: "LoadBalancer"

When we go and try to do anything like reload the Configuration and catalog we get the error 'java.lang.NullPointerException: Cannot invoke "org.geoserver.config.GeoServerLoaderProxy.reload()" because "loader" is null' also when we try to connect to the database it's complaining about postgis not being installed. That's less of a problem though because looking at it, it looks focused on just config so we'll likely create an external for our needs

Error matching the condition value name for rabbitmq dependency.

Should be user rabbitmq.enabled instead of rabbit.enabled.

add a test that adds a functional integration test with k3d

• test chart fresh install
• test chart upgrade from previous release
• test gwc get tiles with cache
• test wms TILED=true is getting tiles from GWC in the cache
• test that JDBC-config is working
• test that datadir is working with NFS server
• test DB layer creation, getCap, getMap, deletion
• test gwc layer creation, getCap, getTile, deletion

Enable template service_and_deployment.yaml file to set

• failureThreshold
• periodSeconds

on

• StartupProbe
• LivenessProbe
• ReadinessProbe

The reason behind: in some cases where the catalog takes longer than those 10 seconds, then startupProbe conditions are causing some services to fail (in our case it was caused by lots of rasters layers, so WCS and WMS-related services were failing. A change on those values allowed the services to start without troubles).

Hi, I am trying to deploy it on AKS via argo using Helm, and I occur this problem that it awaits for database(there is no value regarding database in values.yaml or possibility to add external endpoint for azure postgres instance).

In the other configuration with datadir it returns java error

(Rabbit mq is added as a dependency running in the same namespace)

apiVersion: v2
dependencies:
 - alias: geoserver
   name: custom-pod
   repository: https://camptocamp.github.io/helm-custom-pod/
   version: 0.6.2
 - name: 'rabbitmq'
   version: 11.3.0
   repository: 'https://charts.bitnami.com/bitnami'
   condition: rabbitmq.enabled
# - name: common
#   repository: https://camptocamp.github.io/helm-common
#   version: 0.7.2
 - name: postgresql
   version: 13.2.24
   repository: https://charts.bitnami.com/bitnami
   condition: postgresql.enabled
 - name: geoservercloud
   repository: https://camptocamp.github.io/helm-geoserver-cloud
   version: 0.6.2
description: A Helm chart for Geoserver-cloud
name: geoservercloud
version: 0.6.4

In both cases it looks like it cannot get a configfile from weird urls.

(I have used many variations with dependencies adding rabbitmq,postgres,custom-pod, and can not make it running. Idea behind helm should be that it contains all the dependencies. Can we get more detailed documentation for deployment on kubernetes cluster or add all necessary dependencies in to the chart?

Best regards

in the title

Hi there,

I'm investigating migrating from geoserver to geoserver-cloud for stability & customisation reasons, and am currently trying to test using the helm-geoserver-cloud.

The docs list the below values as how to configure for an external config db:

But upon populating the relevant .value elements (as well as setting postgresql.enabled : false) I can see from the logs of the web-gui container that these settings are not being used. When I dug into the repo I can see that the template file is actually expecting a .configVariables array, with the same KVP's as what is hardcoded for an internal postgres server.

geoservercloud:
  geoserver:
    jdbc:
      external: true
      configVariables:
        - name: "JDBCCONFIG_DATABASE"
          value: "geoserver_cloud_config" 
        - name: "JDBCCONFIG_HOST"
          value: "TEST_HOST"
        - name: "JDBCCONFIG_USERNAME"
          value: "TEST_USER"
        - name: "JDBCCONFIG_PASSWORD"
          value: "SOME_PASSWORD"
        - name: "JDBCCONFIG_PORT"
          value: "5432"

I'm now debugging through further issues, but wanted to know if this is expected behaviour?

To setup into Kubernetes, I ran the following commands:

helm dependency update
helm install geoserver .

Upgrade the chart to use gscloud version 1.7.1 and ACL version 2.1.0

geoserver-cloud 1.7.1

• As requested, the gateway routes the acl service to ${geoserver.base-path}/acl instead of /acl

ACL 2.1.1

• ACL actuator port is 8081, but path changes from /acl/actuator to /actuator. Update liveness/readiness
• Fixes the swagger ui to work behind a reverse proxy

Caused by: org.postgresql.util.PSQLException: ERROR: no schema has been selected to create in
Position: 14
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2675) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2365) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:355) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:490) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:408) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:329) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:315) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:291) ~[postgresql-42.3.8.jar:42.3.8]
at org.postgresql.jdbc.PgStatement.executeUpdate(PgStatement.java:265) ~[postgresql-42.3.8.jar:42.3.8]
at com.zaxxer.hikari.pool.ProxyStatement.executeUpdate(ProxyStatement.java:119) ~[HikariCP-4.0.3.jar:na]
at com.zaxxer.hikari.pool.HikariProxyStatement.executeUpdate(HikariProxyStatement.java) ~[HikariCP-4.0.3.jar:na]
at org.springframework.jdbc.core.JdbcTemplate$1UpdateStatementCallback.doInStatement(JdbcTemplate.java:547) ~[spring-jdbc-5.3.31.jar:5.3.31]
at org.springframework.jdbc.core.JdbcTemplate$1UpdateStatementCallback.doInStatement(JdbcTemplate.java:544) ~[spring-jdbc-5.3.31.jar:5.3.31]
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:383) ~[spring-jdbc-5.3.31.jar:5.3.31]
... 190 common frames omitted

This error is raised while using schema other than public with newly created db. This works fine if postgres db is used.

Hi,

I'm trying to deploy your Helm chart in a K8S cluster.

And For all services pod (webui, wms, ...), except gateway, I got this error:

APPLICATION FAILED TO START

Description:

A component required a bean named 'geoServerLoaderImpl' that could not be found.

Action:

Consider defining a bean named 'geoServerLoaderImpl' in your configuration.

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'geoServerLoader' defined in class path resource [org/geoserver/cloud/config/catalog/CoreBackendConfiguration.class]: 'geoServerLoader' depends on missing bean 'geoServerLoaderImpl'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'geoServerLoaderImpl' available
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:325)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213)
at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:270)
at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:762)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:567)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:740)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:415)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1312)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1301)
at org.geoserver.cloud.web.app.WebUIApplication.main(WebUIApplication.java:20)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:65)
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'geoServerLoaderImpl' available
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:872)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1344)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:283)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322)
... 19 more

Same result with 1.0-RC21 and 1.0-RC-22

Please help !

probes have been lost with the refactoring.

Steps to reproduce:

• Try checking the option "Enable direct integration with GeoServer WMS" under Tile Caching, Caching Defaults for the very first time.
• Under Layers select a layer and Check "Create a cached layer for this layer" under Tile Caching tab for the particular layer
• Try to access the layer using the WMS endpoint from the browser
• Check for a folder with the name similar to the layer name under cache directory/persistent volume mount in any of the pod where the cache volume is mounted (It might have not created)
• Try deleting the WMS pod which automatically creates a new pod with the updated configurations.
• Try to access the layer again and now you will notice a new folder gets created and the layers start to cache the tiles.

Possible Reason: The WMS spring microservice loads the configuration when it initially starts and not being refreshed for every configuration changes until it restarts or starts again.

Hello,

I get the majority pods being CrashLoopBackOff

kubectl get pods

NAME                                                READY   STATUS             RESTARTS         AGE
geoserver-postgresql-0                              1/1     Running            0                61m
geoserver-rabbitmq-0                                1/1     Running            0                61m
geoserver-geoservercloud-gateway-7c7b6d8dc9-l29t6   1/1     Running            0                61m
geoserver-geoservercloud-wfs-747bc6554b-6rwj4       0/1     CrashLoopBackOff   15 (5m3s ago)    61m
geoserver-geoservercloud-gwc-f8f96cb86-tvpct        0/1     CrashLoopBackOff   15 (4m55s ago)   61m
geoserver-geoservercloud-wcs-5cbbfc9b8-tdc9j        0/1     CrashLoopBackOff   15 (4m45s ago)   61m
geoserver-geoservercloud-webui-6998c8fd4-x7pp4      0/1     CrashLoopBackOff   13 (4m26s ago)   61m
geoserver-geoservercloud-wms-55bfbb6886-hh5cb       0/1     CrashLoopBackOff   15 (4m20s ago)   61m
geoserver-geoservercloud-rest-6fc974cc65-zrdd7      0/1     ImagePullBackOff   0                61m
geoserver-geoservercloud-wcs-6775b5d7db-vslh4       0/1     CrashLoopBackOff   6 (22s ago)      6m35s

And the reason being below, ( kubectl logs --previous --tail 10 geoserver-geoservercloud-wcs-6775b5d7db-vslh4)

at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
     at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'geoServerLoaderImpl' available
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:872)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1344)
     at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
     at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:283)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
     at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322)
     ... 19 more

Thanks,

Hi,

First of all, I'm not sure if this is related to the Chart itself or the Geoserver service itself.
When installing the Chart following the instructions in the README, all the services ends up in error or CrashLoopBackOff - apparently caused by a configuration issue.

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.geoserver.platform.GeoServerResourceLoader' available: expected at least 1 bean which qualifies as autowire candidate. 

We installed the chart on a k3d cluster but also on a GCP one with the same results.

$ kubectl create namespace geoserver
namespace/geoserver created

$helm dependency update

# install the chart in the namespace geoserver
$ helm install -n geoserver geoserver .

NAME: geoserver
LAST DEPLOYED: Fri Feb 17 09:48:13 2023
NAMESPACE: geoserver
STATUS: deployed
REVISION: 1
TEST SUITE: None


$ kubectl get pods -n geoserver
NAME                                               READY   STATUS             RESTARTS      AGE
geoserver-geoservercloud-gateway-c44998964-ss4g5   1/1     Running            0             86s
geoserver-geoservercloud-gwc-679549787-kf4dn       0/1     CrashLoopBackOff   3 (15s ago)   86s
geoserver-geoservercloud-rest-659544779f-nx98p     0/1     CrashLoopBackOff   3 (17s ago)   86s
geoserver-geoservercloud-wcs-694467fdc-d8m6h       0/1     CrashLoopBackOff   3 (12s ago)   86s
geoserver-geoservercloud-webui-698d599646-ff975    0/1     Error              3 (35s ago)   86s
geoserver-geoservercloud-wfs-68f95c45b-2gx7l       0/1     CrashLoopBackOff   3 (14s ago)   86s
geoserver-geoservercloud-wms-b59445c58-2lk2b       0/1     CrashLoopBackOff   3 (16s ago)   86s
geoserver-postgresql-0                             1/1     Running            0             86s
geoserver-rabbitmq-0                               

example backtraces :

# for wms
$ kubectl logs -f geoserver-geoservercloud-wms-b59445c58-2lk2b -n geoserver
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.geoserver.platform.GeoServerResourceLoader' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:1801)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1357)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1311)
        at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:887)
        at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:791)
        ... 137 more


# for wfs
$ kubectl logs -f geoserver-geoservercloud-wfs-68f95c45b-2gx7l -n geoserver
***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of method dataDirectory in org.geoserver.cloud.config.catalog.backend.core.CoreBackendConfiguration required a bean of type 'org.geoserver.platform.GeoServerResourceLoader' that could not be found.


Action:

Consider defining a bean of type 'org.geoserver.platform.GeoServerResourceLoader' in your configuration.

I'm not sure how to fix the problem. What could be the root cause ?

Thanks in advance

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Update CI dependencies (patch) (python-jsonschema/check-jsonschema, sirwart/ripsecrets)
• Update pre-commit hook pre-commit/pre-commit-hooks to v4.6.0
• Update Helm release custom-pod to v2
• Update pre-commit hook camptocamp/helm-common to v2
• Lock file maintenance

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository