Releases: achetronic/pg-selector
Release list
v1.1.0
Breaking changes:
-
Replace Zap logger with Golang's logger: Previously an external log library was used, now the native golang library configured to have json format is used. disable-trace flag is no longer supported.
-
Replace flag
disable-services-creationbyservices-creationwith default value oftrue
Features:
-
Manage a Kubernetes Service for standby nodes: Previously, only the service that pointed to the primary node was created, now a service that points to the standby nodes is also created.
-
Implement a wrapper manager for the
runcommand: The code structure of the run command has been changed to a more friendly approach, now the command creates a watcher and runs it checking for system signals (SIGTERM and SIGINT). -
Rearrange code logic for the shake of maintenance
Fixes:
-
Ignore duplicated primary nodes: Previously, if more than one primary was found, pg-selector would update the labels equally. Now it logs an error and does not update the labels.
Context: this is necessary because if more than one primary is found, it means that the replication manager has not been able to properly promote the other pod to primary, and therefore a manual action is required so that there is only one primary again. While this manual action is being executed, the service of the created primary is required to only point to one primary node, so that there are no inconsistencies in the data when writing to two primary nodes.
-
Avoid crashing on well-known situations: Previously the main loop would crash when some errors occurred, now it just logs the error and continues to the next sync time wait. The application crash should only happen in unexpected cases or due to configuration failure.
Contributors:
@sebastocorp
pg-selector-helm-chart-1.1.0
A Helm chart for PG Selector, a little companion for your Postgres HA deployment on Kubernetes that labels its pods with the current replication role (realtime)
v1.0.0 👨🏭🔧
Attention:
No changes, just regenerating resources (binary assets and Helm charts) as this is the final location for the project.
Please, use these instead of the previous ones.
pg-selector-helm-chart-1.0.0 👨🏭🔧
A Helm chart for PG Selector, a little companion for your Postgres HA deployment on Kubernetes that labels its pods with the current replication role (realtime)
No changes, just regenerating resources (binary assets and Helm charts) as this is the final location for the project.
Please, use these instead of the previous ones.
v0.3.0
Changes:
- Add ability to expand environment variable
PG_CONNECTION_STRINGjust in case you need it 😜
Contributors:
@achetronic @sebastocorp
v0.2.0
Changes:
- Add ability to create a Service that points only to primary nodes
- Add a flag
--disable-service-creationto avoid previous feature
Fixes:
- Now the EndpointSlice selection filter is more precise to avoid selecting several of them
Contributors:
@achetronic @sebastocorp
pg-selector-helm-chart-0.3.6
A Helm chart for PG Selector, a little companion for your Postgres HA deployment on Kubernetes that labels its pods with the current replication role(realtime)
pg-selector-helm-chart-0.3.5
A Helm chart for PG Selector, a little companion for your Postgres HA deployment on Kubernetes that labels its pods with the current replication role(realtime)
pg-selector-helm-chart-0.3.4
A Helm chart for PG Selector, a little companion for your Postgres HA deployment on Kubernetes that labels its pods with the current replication role(realtime)
pg-selector-helm-chart-0.3.3
A Helm chart for PG Selector, a little companion for your Postgres HA deployment on Kubernetes that labels its pods with the current replication role(realtime)