Skip to content

Conversation

@gkech
Copy link
Contributor

@gkech gkech commented Oct 2, 2025

K8SPG-866 Powered by Pull Request Badge

DESCRIPTION

Problem:
v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice

Solution:
Before this PR, the operator created only the -primary Endpoints resource. All other Endpoints resources are created by patroni. Patroni currently does not support creating EndpointSlices in place of the deprecated Endpoints.

This PR replaces the -primary Endpoints resource with an EndpointSlice once version 2.9.0 is reached. As part of the migration, the deprecated Endpoints resource and the mirrored EndpointSlice created by endpointslicemirroring-controller.k8s.io from the deprecated Endpoints resource are deleted.

This PR also addresses the fact that EndpointSlices are not supported on GKE out of the box. The default DNS provider on GKE is kube-dns, which does not support EndpointSlices. To use EndpointSlices, users must manually deploy CoreDNS or use Cloud DNS. To fix tests, every test deploys CoreDNS in the kube-system namespace if it is not already present.

Please note that Endpoints resources are mirrored to EndpointSlices by endpointslicemirroring-controller.k8s.io, which is why the upgrade-consistency test includes assertions for EndpointSlices.

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Are all needed new/changed options added to the Helm Chart?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported PG version?
  • Does the change support oldest and newest supported Kubernetes version?

@JNKPercona
Copy link
Collaborator

Test Name Result Time
backup-enable-disable passed 00:07:08
custom-envs passed 00:19:05
custom-extensions passed 00:13:31
custom-tls passed 00:05:24
database-init-sql passed 00:03:04
demand-backup passed 00:23:54
finalizers passed 00:03:48
init-deploy passed 00:02:43
monitoring passed 00:07:44
monitoring-pmm3 passed 00:09:51
one-pod passed 00:05:53
operator-self-healing passed 00:08:19
pgvector-extension passed 00:02:54
pitr passed 00:12:26
scaling passed 00:05:12
scheduled-backup passed 00:28:12
self-healing passed 00:09:17
sidecars passed 00:02:41
start-from-backup passed 00:12:04
tablespaces passed 00:06:54
telemetry-transfer passed 00:03:23
upgrade-consistency passed 00:06:56
upgrade-minor passed 00:05:29
users passed 00:04:21
Summary Value
Tests Run 24/24
Job Duration 01:24:27
Total Test Time 03:30:24

commit: 967ede9
image: perconalab/percona-postgresql-operator:PR-1307-967ede907

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.

4 participants