Closed pooknull closed 3 months ago
Test name | Status |
---|---|
custom-extensions | passed |
demand-backup | passed |
init-deploy | passed |
monitoring | passed |
one-pod | passed |
operator-self-healing | passed |
pitr | passed |
scaling | passed |
scheduled-backup | passed |
self-healing | passed |
start-from-backup | passed |
tablespaces | passed |
telemetry-transfer | passed |
upgrade-consistency | passed |
upgrade-minor | passed |
users | passed |
We run 16 out of 16 |
commit: https://github.com/percona/percona-postgresql-operator/pull/787/commits/616dcd2e7995be078b904d42355a8546fc9629b8
image: perconalab/percona-postgresql-operator:PR-787-616dcd2e7
https://perconadev.atlassian.net/browse/K8SPG-519
DESCRIPTION
Problem: When installing custom extensions it is not possible to point to a custom s3 object storage endpoint.
Cause: The s3 SDK within the extension installer is only minimally configured, currently using default values.
Solution: Add an optional flag to the extension installer named
endpoint
and configure the s3 SDK appropriately.It's an improved version of the https://github.com/percona/percona-postgresql-operator/pull/672 PR. Since the branch https://github.com/timorusky/percona-postgresql-operator/tree/extensions-endpoint was archived, it was decided to continue development of the feature in a separate PR.
CHECKLIST
Jira
Needs Doc
) and QA (Needs QA
)?Tests
Config/Logging/Testability