Skip to content

allow creation of pg-stac secrets from azure secret vault, refs #186 #187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 58 commits into
base: main
Choose a base branch
from

Conversation

batpad
Copy link
Member

@batpad batpad commented Mar 12, 2025

Refs #186

Creates the pgstac-secret- object reading from an Azure Secrets Vault.

We may or may not want to include this in a main eoapi-k8s release, but it would definitely be helpful to have a helm chart with this to test our deploy.

cc @geohacker @emmanuelmathot

[EDIT] Emmanuel 08/04/2025

  • Refactored specific azure service account to generic service account management
  • Added extra placeholders in values.yaml to mount extra volumes and extra secret managed by azure in a generic way
  • Deactivate existing postgres secret when postgrescluster.enabled is false
  • Added Azure specific documentation for using Azure managed postgres and keyvault
  • Added pod debug logs when startup fails in CI/CD
  • updated PGO to 5.7.0

batpad and others added 28 commits March 12, 2025 18:14
…figmap.yaml for PGADMIN_URI initialization and PostgreSQL environment variables
…o ensure PGADMIN_URI is initialized correctly
…figmap.yaml for PGADMIN_URI initialization and PostgreSQL environment variables
@emmanuelmathot emmanuelmathot marked this pull request as ready for review April 8, 2025 10:30
@emmanuelmathot emmanuelmathot requested a review from pantierra April 8, 2025 18:42
@emmanuelmathot emmanuelmathot requested a review from sunu April 8, 2025 18:43
@@ -9,7 +9,7 @@ on:

env:
HELM_VERSION: v3.15.2
PGO_VERSION: 5.5.2
PGO_VERSION: 5.7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest to align with 5.7.4 which we are using currently. This will also make it easier not to miss when we upgrade again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants