kubernetes/kubernetes

Tracking Issue - Conformance Coverage for Networking

Open

#73,425 opened on Jan 28, 2019

View on GitHub
 (27 comments) (0 reactions) (1 assignee)Go (43,066 forks)batch import
area/conformancehelp wantedkind/featurelifecycle/rottensig/networksig/testing

Repository metrics

Stars
 (122,268 stars)
PR merge metrics
 (Avg merge 28d 17h) (343 merged PRs in 30d)

Description

What would you like to be added: This is a place holder to track Conformance Coverage on the Topic. This issue should remain open until all related work is accomplished in the k/k repo This issue will contain analysis of the coverage. Existing tests and additional tests requested with links to those issues/PR's

Why is this needed: Specifically address CNI networking, identify tests that tests pod-pod communication

/area conformance

Contributor guide

Research direction
Analyze existing conformance tests for pod pod communication, identify gaps, and propose new tests. Review CNI plugin behavior.
Tech stack
go
Domain
backendinfrastructure
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesNetworkingCNI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50