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

follow-up todos for maglev #13138

Open
15 of 25 tasks
borkmann opened this issue Sep 10, 2020 · 4 comments
Open
15 of 25 tasks

follow-up todos for maglev #13138

borkmann opened this issue Sep 10, 2020 · 4 comments
Assignees
Labels
area/loadbalancing Impacts load-balancing and Kubernetes service implementations kind/meta Meta-task for co-ordination. sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages.

Comments

@borkmann
Copy link
Member

borkmann commented Sep 10, 2020

RELEASE BLOCKERS

@brb

@borkmann

1.10 or 1.9 best-effort

@brb:

  • OpenOrCreateUnpinned -> CreateUnpinned (Add Maglev consistent hashing to kube-proxy replacement #13131 (comment)).
  • Add struct for args of pkg/maps/lbmap.go:UpsertService().
  • Potentially missing bits from V1.8.1 maglev #13189
  • Extend test_maglev(): 1) remove a non-selected pod and check that the same backend is selected (EDIT: 1) is flaky due the possible 1% changes in the backends configuration) 2) remove the selected backend and check that different backend is selected.

@borkmann:

  • Kernel: implement flexible max_elems for arraymap so htab can have flexible sized inner map (this can then be realised via Cilium-specific service annotations)
  • Maglev nodeport test also for XDP layer (test: extend XDP coverage for Maglev #13847)

@brb / @borkmann:

@borkmann borkmann added priority/release-blocker kind/feature This introduces new functionality. labels Sep 10, 2020
@borkmann borkmann moved this from WIP (Martynas + Daniel) to WIP (Daniel) in 1.9 kube-proxy removal & general dp optimization Sep 14, 2020
@brb brb moved this from WIP (Daniel) to WIP (Martynas + Daniel) in 1.9 kube-proxy removal & general dp optimization Sep 30, 2020
@borkmann borkmann removed the kind/feature This introduces new functionality. label Oct 5, 2020
@joestringer
Copy link
Member

@brb to follow up to determine which of these items should block the v1.9 release vs. which ones should not.

@borkmann
Copy link
Member Author

Unmarked from release-blocker given #13821 is out and the rest in here are best-effort and can land in later 1.9 or 1.10.

@christarazi christarazi added kind/meta Meta-task for co-ordination. sig/loadbalancing labels Feb 10, 2021
@aanm aanm added the sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. label Jan 6, 2022
@gaffneyd4
Copy link
Contributor

Can the task Strategy for draining old backends be marked as complete by this PR?

If so to clarify, does this mean that for those using bpf-lb-algorithm: maglev, these issues (10217), (14844) are solved as of v1.11?

@brb
Copy link
Member

brb commented Aug 2, 2022

Can the task Strategy for draining old backends be marked as complete by #17716?

cc @aditighag

@brb brb removed their assignment Mar 10, 2023
@brb brb removed this from WIP (Martynas + Daniel) in 1.9 kube-proxy removal & general dp optimization Mar 10, 2023
@julianwiedmann julianwiedmann added the area/loadbalancing Impacts load-balancing and Kubernetes service implementations label Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/loadbalancing Impacts load-balancing and Kubernetes service implementations kind/meta Meta-task for co-ordination. sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
Projects
None yet
Development

No branches or pull requests

7 participants