github geoserver/geoserver-cloud v1.0-RC6

latest releases: v1.9.1, v1.9.0, v1.9-RC3...
2 years ago

First release candidate after upgrading to spring-cloud:2021.0.0 / spring-boot:2.6.1

Upgrade from 1.0-RC5

If you're using the provided docker-compose.yml files (either for shared data direcory or jdbcconfig backend deployments), you can just download them, or change the docker image tags to v1.0-RC6 and set the following environment variable to the config service:

SPRING_CLOUD_CONFIG_SERVER_GIT_DEFAULT_LABEL: v1.0-RC6

So it downloads the proper set of config files from the repository.

If you've set up a separate config (for example, a helm chart for Kubernetes), there are some configuration changes to apply:

  • Rename the property geoserver.backend.jdbcconfig.datasource.jdbcUrl as geoserver.backend.jdbcconfig.datasource.url
  • Rename all spring.profiles: entries as spring.config.activate.on-profile:

That should be it.

Here're the full changes applied to the config repository:

geoserver/geoserver-cloud-config@v1.0-RC5...v1.0-RC6

Set up liveness and readiness probes in Kubernetes

Proceed as explained in Spring Boot's Kubernetes Probes documentation:

livenessProbe:
  httpGet:
    path: "/actuator/health/liveness"
    port: <actuator-port>
  failureThreshold: ...
  periodSeconds: ...

readinessProbe:
  httpGet:
    path: "/actuator/health/readiness"
    port: <actuator-port>
  failureThreshold: ...
  periodSeconds: ...

The ports are:

  • 8080 for the admin, config, discovery, and gateway services (i.e. all "support" microservices)
  • 8081 for the rest, wcs, webui, wfs, and wms services (i.e. all GeoServer microservices)

What's Changed

  • Upgrade to spring-cloud:2021.0.0 / spring-boot:2.6.1 by @groldan in #127
  • specify user:group in docker-compose.yml for each service by @groldan in #145
  • Change GeoServer microservices management port to 8081 and add liveness and readiness probes by @groldan in #146
  • GeoServerSecurityManager startup configuration improvements by @groldan in #147
  • jdbc resource store cache causes startup failures due to stale resource metadata by @groldan in #148

New Contributors

Full Changelog: v1.0-RC5...v1.0-RC6

Don't miss a new geoserver-cloud release

NewReleases is sending notifications on new releases.