AWS eks documentation change
Summary
Removed manual BPF filesystem mounting requirements and renumbered subsequent steps
Security assessment
Procedural simplification for newer AMIs. While BPF relates to network security, the change documents platform improvements rather than addressing vulnerabilities.
Diff
diff --git a/eks/latest/userguide/cni-network-policy-configure.md b/eks/latest/userguide/cni-network-policy-configure.md index 652bbe262..04989bc22 100644 --- a//eks/latest/userguide/cni-network-policy-configure.md +++ b//eks/latest/userguide/cni-network-policy-configure.md @@ -5 +5 @@ -PrerequisitesStep 1: Set up policy enforcement at Pod startupStep 2: Enable the network policy parameter for the add-onStep 3: Mount the Berkeley Packet Filter (BPF) file system on your nodesStep 4: Configure your cluster to use Kubernetes network policiesStep 5. Next steps +PrerequisitesStep 1: Set up policy enforcement at Pod startupStep 2: Enable the network policy parameter for the add-onStep 3: Configure your cluster to use Kubernetes network policiesStep 4. Next steps @@ -135,20 +135 @@ If you have installed the Amazon VPC CNI plugin for Kubernetes through `helm`, y -## Step 3: Mount the Berkeley Packet Filter (BPF) file system on your nodes - -You must mount the Berkeley Packet Filter (BPF) file system on each of your nodes. - -###### Note - -If your cluster is version `1.27` or later, you can skip this step as all Amazon EKS optimized Amazon Linux and Bottlerocket AMIs for `1.27` or later have this feature already. - -For all other cluster versions, if you upgrade the Amazon EKS optimized Amazon Linux to version `v20230703` or later or you upgrade the Bottlerocket AMI to version `v1.0.2` or later, you can skip this step. - - 1. Mount the Berkeley Packet Filter (BPF) file system on each of your nodes. - - sudo mount -t bpf bpffs /sys/fs/bpf - - 2. Then, add the same command to your user data in your launch template for your Amazon EC2 Auto Scaling Groups. - - - - -## Step 4: Configure your cluster to use Kubernetes network policies +## Step 3: Configure your cluster to use Kubernetes network policies @@ -231 +212 @@ Once you’ve added the line, your `ConfigMap` should look like the following ex -## Step 5. Next steps +## Step 4. Next steps