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

Bandwidth plugin with NP is currently unsupported #2572

Merged
merged 3 commits into from
Sep 18, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,6 +572,8 @@ Default: `false`

Setting `ENABLE_BANDWIDTH_PLUGIN` to `true` will update `10-aws.conflist` to include upstream [bandwidth plugin](https://www.cni.dev/plugins/current/meta/bandwidth/) as a chained plugin.

NOTE: Network Policy is supported from CNI version v1.14.0 onwards. We use TC(traffic classifier) system to enforce network policy for the pods ingress and egress traffic. If the bandwidth plugin and network policy is enabled and the network policy enforced pods have "ingress-bandwidth" and "egress-bandwidth" configured then network policy enforcement will fail since bandwidth plugin uses TC which will collide with aws-eks-nodeagent TC configuration. We will provide updates [here](https://github.com/aws/aws-network-policy-agent/issues/68)
jayanthvn marked this conversation as resolved.
Show resolved Hide resolved

#### `ANNOTATE_POD_IP` (v1.9.3+)

Type: Boolean as a String
Expand Down