Skip to content
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

Feat: adding configurable parameter for custom role label in multiple resources #2802

Draft
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

idanovinda
Copy link
Member

@idanovinda idanovinda commented Nov 19, 2024

New Spilo with Patroni 4.x integration: zalando/spilo#1050

This PR enhances operator to support Patroni 4.x while retaining compatibility with existing clusters by making the new role label configurable. The role terminology has changed from "master" to "primary". By default, Spilo will use the same value as before. But to allow flexibility in label configurations, we need to ensure that the role label are configurable.

This is achieved by adding configurable parameters:

  • pod_leader_label_value: default is set to "master"

@idanovinda idanovinda added the major Major feature changes or updates, e.g. feature rollout to a new country, new API calls. label Nov 19, 2024
@zalando-robot
Copy link

  • Aborted by pbungina

pkg/cluster/connection_pooler_test.go Outdated Show resolved Hide resolved
pkg/cluster/sync.go Show resolved Hide resolved
@idanovinda idanovinda changed the title Integrate Spilo image with Patroni version 4 Feat: adding configurable parameter for custom role label in multiple resources Dec 6, 2024
@hughcapet
Copy link
Member

The PR is still WIP -- migration procedure needs to be implemented. See https://patroni.readthedocs.io/en/latest/kubernetes.html#customize-role-label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major Major feature changes or updates, e.g. feature rollout to a new country, new API calls.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants