Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Cilium image BPF patches have no runtime test

Aperta
  • Qualcosa non va?
#4,784 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go
Ambito
testing

Direzione di ricerca

Start from the BPF patches in packages/system/cilium/images/cilium/patches and existing E2E tests for kubeovn-cilium variants. Add a test case verifying that a pod with an HTTP readiness probe under a CiliumNetworkPolicy allowing only fromEntities: [cluster] becomes Ready. Add a second case ensuring fromEntities: [world] ingress deny does not block host-network clients calling same-node pods. Run the E2E suite to confirm the tests catch the v1.20 regression.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

triage/needs-triage

Nothing in CI checks that the BPF patches we carry on the Cilium image actually do their job on a running cluster. The image build only checks that each patch applies with --fuzz=0 and leaves the expected number of markers in the source. If a patch applies cleanly but stops doing what it should, the build stays green.

This bit us with the v1.20 bump. On the kube-ovn chained variants, host traffic to a pod on the same node started arriving as world (#4781), so kubelet probes failed under default-deny ingress policies and the API server timed out calling webhooks on its own node. The only signal was admission timeouts in E2E reports, and finding the cause took a live cluster and pwru. #3343 now carries a patch for it under packages/system/cilium/images/cilium/patches, next to the IPv6 passthrough patch, and neither has a test that would catch it breaking.

A small E2E case on a kubeovn-cilium variant would cover the current regression: a pod with an HTTP readiness probe under a CiliumNetworkPolicy that allows only fromEntities: [cluster], which has to become Ready. A second step could check that a fromEntities: [world] ingress deny does not block a host-network client calling a pod on the same node. The IPv6 passthrough patch would need its own case on an IPv6 fabric, which may not be practical in CI.

Lingua principale
Go
Stelle
2.2k
Fork
209
Merge medio
3g 18h
PR unite (30g)
241

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cozystack/cozystack

Tutte le issue di cozystack/cozystack

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.