microsoft/retina

Pod level metrics for drop may miss localCtx labels

Open

#80 opened on Mar 20, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (293 forks)auto 404
area/metricsarea/pluginscontrol-plane/standardgood first issuehelp wantedlang/gopriority/2scope/Stype/bug

Repository metrics

Stars
 (3,161 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug Consider the following scenario:

Server is running in a pod on node-1 We annotate the server to observe dropped packets Apply a network policy for ingress When a pod on other nodes try to connect to server, the IPTABLE rule on that node will drop the packet. However, for local context, our filter_map won't have the IP of the server, hence we will not generate any event. Thus, we will see drop_count increase at the node level, but no pod level labels for the drops True for external connections as well This is due to how Azure NPM works today. May need to add disclaimer to account for this behavior.

cc @anubhabMajumdar

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.