zalando / zalando/postgres-operator
Operator warning - warnings.go:70] v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.22.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? K8s
- Are you running Postgres Operator in production? yes
- Type of issue? Question
Hi All,
We are noticing this warning in the operator logs after the K8s upgrade of 1.33 from 1.31. Is this take care in the new version? Is there any impact if we are using the same version as this is warning only. please suggest.
W0320 12:47:13.422376 1 warnings.go:70] v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
W0320 12:47:13.621974 1 warnings.go:70] v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at warnings.go:70 and trace which operator code requests the v1 Endpoints API after a Kubernetes 1.33 upgrade. Check whether the operator version in use has an EndpointSlice-based path and reproduce the warning on a supported Kubernetes version. Done means the compatibility impact and required upgrade or code change are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100