v0.7.3

What's Changed

• Add CREATEROLE privilege to pgstac user by @emmanuelmathot in #236

Full Changelog: v0.7.2...v0.7.3

v0.7.2

What's Changed

• Make 0.7.0 db upgrade run in ArgoCD. by @pantierra in #232

Full Changelog: v0.7.1...v0.7.2

eoapi-0.7.3

Create a full Earth Observation API with Metadata, Raster and Vector services

eoapi-0.7.2

Create a full Earth Observation API with Metadata, Raster and Vector services

v0.7.1

Release v0.7.1

We are pleased to announce the release of eoAPI-k8s v0.7.1. This release brings important improvements to ingress configuration, database management, and upgrade processes.

Highlights

• 🔄 Seamless upgrade path from pre-0.7.0 versions
• 🛣️ Simplified ingress configuration
• 🎯 Better STAC browser integration
• 🔐 Enhanced PostgreSQL cluster management

Important Notice for Pre-0.7.0 Users

If you're upgrading from a version prior to 0.7.0, please note that this version includes significant changes to database permissions and ingress configuration:

1. Database Permissions: In v0.7.0, we changed how database permissions are handled. When upgrading from pre-0.7.0:

   • Use --set previousVersion=<your-current-version> during upgrade
   • The upgrade process will automatically handle permission migrations
   • External database users should follow the manual steps in our upgrade guide

2. Ingress Changes: The v0.7.0 release introduced a unified ingress configuration which has been further improved in v0.7.1:

   • Remove any pathType and pathSuffix configurations
   • Controller-specific optimizations are now automatic
   • STAC browser has a dedicated ingress configuration

What's New in 0.7.1

Breaking Changes

• Removed pathType and pathSuffix configurations in favor of smart defaults
• Ingress configuration is now controller-aware (NGINX/Traefik)

New Features

1. Database Upgrades

   • Automated permission handling for pre-0.7.0 upgrades
   • Support for custom PostgreSQL cluster naming
   • Better secret handling with cluster name flexibility

2. Ingress Improvements

   • Separate STAC browser ingress configuration
   • Optimized path handling for both NGINX and Traefik
   • Automatic regex configuration for NGINX

3. Reliability

   • Increased bootstrap job retry limit to 3 attempts
   • Enhanced error handling during upgrades
   • Improved secret management

Quick Start

1. Update your Helm repository:

helm repo update

2. Upgrade your installation:

# For new installations
helm upgrade --install eoapi devseed/eoapi

# For upgrades from pre-0.7.0
helm upgrade eoapi devseed/eoapi --set previousVersion=<your-current-version>

Migration Guide

From v0.7.0

• Remove pathType and pathSuffix from your values.yaml
• Review browser-specific ingress settings if using STAC browser
• Consider using the new PostgreSQL cluster naming feature

From Pre-0.7.0 Versions

1. Read the upgrade guide
2. Ensure you specify your current version during upgrade
3. For external databases, follow the manual SQL upgrade steps
4. Update your ingress configuration to the new format

Breaking Changes from v0.7.0

For a complete list of breaking changes introduced in v0.7.0, please refer to:

• v0.7.0 Release Notes
• Migration Guide

Support

If you encounter any issues or need assistance:

1. Check our documentation
2. Open an issue on GitHub

eoapi-0.7.1

Release v0.7.1

We are pleased to announce the release of eoAPI-k8s v0.7.1. This release brings important improvements to ingress configuration, database management, and upgrade processes.

Highlights

• 🔄 Seamless upgrade path from pre-0.7.0 versions
• 🛣️ Simplified ingress configuration
• 🎯 Better STAC browser integration
• 🔐 Enhanced PostgreSQL cluster management

Important Notice for Pre-0.7.0 Users

If you're upgrading from a version prior to 0.7.0, please note that this version includes significant changes to database permissions and ingress configuration:

1. Database Permissions: In v0.7.0, we changed how database permissions are handled. When upgrading from pre-0.7.0:

   • Use --set previousVersion=<your-current-version> during upgrade
   • The upgrade process will automatically handle permission migrations
   • External database users should follow the manual steps in our upgrade guide

2. Ingress Changes: The v0.7.0 release introduced a unified ingress configuration which has been further improved in v0.7.1:

   • Remove any pathType and pathSuffix configurations
   • Controller-specific optimizations are now automatic
   • STAC browser has a dedicated ingress configuration

What's New in 0.7.1

Breaking Changes

• Removed pathType and pathSuffix configurations in favor of smart defaults
• Ingress configuration is now controller-aware (NGINX/Traefik)

New Features

1. Database Upgrades

   • Automated permission handling for pre-0.7.0 upgrades
   • Support for custom PostgreSQL cluster naming
   • Better secret handling with cluster name flexibility

2. Ingress Improvements

   • Separate STAC browser ingress configuration
   • Optimized path handling for both NGINX and Traefik
   • Automatic regex configuration for NGINX

3. Reliability

   • Increased bootstrap job retry limit to 3 attempts
   • Enhanced error handling during upgrades
   • Improved secret management

Quick Start

1. Update your Helm repository:

helm repo update

2. Upgrade your installation:

# For new installations
helm upgrade --install eoapi devseed/eoapi

# For upgrades from pre-0.7.0
helm upgrade eoapi devseed/eoapi --set previousVersion=<your-current-version>

Migration Guide

From v0.7.0

• Remove pathType and pathSuffix from your values.yaml
• Review browser-specific ingress settings if using STAC browser
• Consider using the new PostgreSQL cluster naming feature

From Pre-0.7.0 Versions

1. Read the upgrade guide
2. Ensure you specify your current version during upgrade
3. For external databases, follow the manual SQL upgrade steps
4. Update your ingress configuration to the new format

Breaking Changes from v0.7.0

For a complete list of breaking changes introduced in v0.7.0, please refer to:

• v0.7.0 Release Notes
• Migration Guide

Support

If you encounter any issues or need assistance:

1. Check our documentation
2. Open an issue on GitHub

v0.7.0

The v0.7.0 release introduces a unified database deployment strategy, redesigned ingress system, modernized service architecture, and several new integrations that make the platform more adaptable to different deployment scenarios while maintaining robust operational standards.

Major Changes

1. Unified Database Architecture

   • Flexible PostgreSQL deployment supporting both integrated PGO operator and self-managed deployments
   • Enhanced PgSTAC bootstrap process using Helm hooks for reliable database initialization

2. Ingress System Improvements

   • New controller-agnostic ingress configuration that works seamlessly with both NGINX and Traefik
   • Streamlined path management and routing that reduces configuration complexity

3. Service Architecture Enhancements

   • Refactored service-specific templates for better modularity and maintenance
   • Improved service organization and dependency management

4. New Features

   • Integrated STAC Browser for intuitive data exploration and visualization
   • Azure Secret Vault integration enabling secure credential management
   • ArtifactHub.io integration for simplified package discovery and installation
   • Upgraded stac-fastapi-pgstac to v5.0.2 with latest STAC improvements

Breaking Changes Notice

Users upgrading from previous versions should note several breaking changes:

• PostgreSQL configuration has been refactored to support both PGO operator and self-managed deployments
• The ingress configuration system has been completely restructured
• Database setup procedures have been modernized with removal of deprecated configurations

Please refer to our migration guides in the documentation for detailed upgrade instructions. These changes, while requiring some migration effort, provide a more robust and maintainable foundation for your Earth Observation API deployments.

What's Changed

• Upgrade stac-fastapi-pgstac to v5.0.2 by @sunu in #204
• Refactor pgstacbootstrap job and ConfigMaps to use Helm hooks for execution order by @emmanuelmathot in #207
• Simplify PgSTAC Bootstrap Process by @emmanuelmathot in #208
• Add and reorganize changelog for EOAPI Kubernetes deployment by @emmanuelmathot in #214
• Fix: Add Artifacthub.io Integration (Issue #16) by @emmanuelmathot in #216
• Refactor PostgreSQL configuration and remove deprecated database setup by @emmanuelmathot in #215
• allow creation of pg-stac secrets from azure secret vault, refs #186 by @batpad in #187
• Unified Ingress Implementation - Fixes #205 by @emmanuelmathot in #219
• Refactor Helm Chart to Service-Specific Templates by @emmanuelmathot in #220
• Add stac-browser by @alekzvik in #168
• eoAPI Kubernetes v0.7.0 Release by @emmanuelmathot in #221

New Contributors

• @emmanuelmathot made their first contribution in #207
• @batpad made their first contribution in #187
• @alekzvik made their first contribution in #168

Full Changelog: v0.6.0...v0.7.0

eoapi-0.7.0

The v0.7.0 release introduces a unified database deployment strategy, redesigned ingress system, modernized service architecture, and several new integrations that make the platform more adaptable to different deployment scenarios while maintaining robust operational standards.

Major Changes

1. Unified Database Architecture

   • Flexible PostgreSQL deployment supporting both integrated PGO operator and self-managed deployments
   • Enhanced PgSTAC bootstrap process using Helm hooks for reliable database initialization

2. Ingress System Improvements

   • New controller-agnostic ingress configuration that works seamlessly with both NGINX and Traefik
   • Streamlined path management and routing that reduces configuration complexity

3. Service Architecture Enhancements

   • Refactored service-specific templates for better modularity and maintenance
   • Improved service organization and dependency management

4. New Features

   • Integrated STAC Browser for intuitive data exploration and visualization
   • Azure Secret Vault integration enabling secure credential management
   • ArtifactHub.io integration for simplified package discovery and installation
   • Upgraded stac-fastapi-pgstac to v5.0.2 with latest STAC improvements

Breaking Changes Notice

Users upgrading from previous versions should note several breaking changes:

• PostgreSQL configuration has been refactored to support both PGO operator and self-managed deployments
• The ingress configuration system has been completely restructured
• Database setup procedures have been modernized with removal of deprecated configurations

Please refer to our migration guides in the documentation for detailed upgrade instructions. These changes, while requiring some migration effort, provide a more robust and maintainable foundation for your Earth Observation API deployments.

What's Changed

• Upgrade stac-fastapi-pgstac to v5.0.2 by @sunu in #204
• Refactor pgstacbootstrap job and ConfigMaps to use Helm hooks for execution order by @emmanuelmathot in #207
• Simplify PgSTAC Bootstrap Process by @emmanuelmathot in #208
• Add and reorganize changelog for EOAPI Kubernetes deployment by @emmanuelmathot in #214
• Fix: Add Artifacthub.io Integration (Issue #16) by @emmanuelmathot in #216
• Refactor PostgreSQL configuration and remove deprecated database setup by @emmanuelmathot in #215
• allow creation of pg-stac secrets from azure secret vault, refs #186 by @batpad in #187
• Unified Ingress Implementation - Fixes #205 by @emmanuelmathot in #219
• Refactor Helm Chart to Service-Specific Templates by @emmanuelmathot in #220
• Add stac-browser by @alekzvik in #168
• eoAPI Kubernetes v0.7.0 Release by @emmanuelmathot in #221

New Contributors

• @emmanuelmathot made their first contribution in #207
• @batpad made their first contribution in #187
• @alekzvik made their first contribution in #168

Full Changelog: v0.6.0...v0.7.0

v0.6.0

Breaking changes

• Database backups are now disabled by default. To enable them, set backupsEnabled: true in your values.yaml.

What's Changed

• Update GCP Setup instructions by @eschwartz in #188
• Remove GCP CI deployment tests. by @pantierra in #193
• Fix multidim entrypoint. by @pantierra in #192
• Fix unsupported regex in ingress-nginx config by @eschwartz in #189
• Add initContainers to wait for db and it's bootstrap. by @pantierra in #194
• Upgrade PGO to 5.7.0; Add option to disable backups by @sunu in #191
• Upgrade dependencies by @pantierra in #196
• Let all eoAPI services wait for db bootstrap. by @pantierra in #197
• Reduce errors about too many db connections. by @pantierra in #198
• Upgrade to latest stac-fastapi-pgstac by @pantierra in #195
• Upgrade tipg to 1.0.1 and titiler-pgstac to 1.7.1. by @pantierra in #199

New Contributors

• @eschwartz made their first contribution in #188

postgrescluster-5.7.4

A Helm chart for eoapi database dep for k8s