mittwald / mittwald/kube-httpcache

Kubernetes v.1.33+ deprecates endpoints:

Open
#301 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
313
Forks
82
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
kubernetes v.1.33+ deprecates endpoints:

I0611 01:07:53.372731 1 warnings.go:110] "Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice"

To Reproduce
Steps to reproduce the behavior:
- args:
- '-admin-addr=0.0.0.0'
- '-admin-port=6083'
- '-signaller-enable'
- '-signaller-port=8090'
- '-frontend-watch'
- '-frontend-namespace=$(NAMESPACE)'
- '-frontend-service=varnish-headless'
- '-frontend-portname=http-varnish'
- '-frontend-port=6081'
- '-backend-watch'
- '-backend-namespace=$(NAMESPACE)'
- '-backend-service=my-app-service-no-cache'
- '-varnish-secret-file=/etc/varnish/k8s-secret/secret'
- '-varnish-vcl-template=/etc/varnish/tmpl/default.vcl.tmpl'
- '-varnish-storage=malloc,100M'

Expected behavior

No warning appears around kubernetes api

Environment:

  • Kubernetes version: [e.g. 1.18]
  • kube-httpcache version: [e.g. v0.2.2]

Configuration
If applicable, add your VCL configuration file and other relevant configuration settings

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the warning on Kubernetes 1.33+ using the provided frontend-watch and backend-watch arguments, then locate the Kubernetes service-watching entry points. Trace where the deprecated v1 Endpoints API is used and update the watch path to the discovery.k8s.io/v1 EndpointSlice API. Done means both watches work without the deprecation warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.