AWS eks documentation change
Summary
Removed section about PodSecurityPolicy configuration issues and related recommendations
Security assessment
Removal of PSP-related content follows Kubernetes' PSP deprecation but doesn't directly address a specific security vulnerability. This is documentation alignment with feature lifecycle changes.
Diff
diff --git a/eks/latest/userguide/eks-outposts-troubleshooting.md b/eks/latest/userguide/eks-outposts-troubleshooting.md index c801912ce..b0f1654f9 100644 --- a//eks/latest/userguide/eks-outposts-troubleshooting.md +++ b//eks/latest/userguide/eks-outposts-troubleshooting.md @@ -140,8 +139,0 @@ The most common issues are the following: - * Misconfigured Pod security policy: - - * The CoreDNS and Amazon VPC CNI plugin for Kubernetes Daemonsets must run on nodes for nodes to join and communicate with the cluster. - - * The Amazon VPC CNI plugin for Kubernetes requires some privileged networking features to work properly. You can view the privileged networking features with the following command: `kubectl describe psp eks.privileged`. - -We don’t recommend modifying the default pod security policy. For more information, see [Understand Amazon EKS created Pod security policies (PSP)](./pod-security-policy.html). -