Get a free AWS Well-Architected Assessment ->

Cross peering connectivity is allowed by Pod

Security & Compliance

When using Kubernetes or other container orchestration tools, it's important to ensure that cross peering connectivity is not allowed by pods. This means that pods should not be able to communicate with resources in other VPCs or accounts without explicit permission. By default, pods in a Kubernetes cluster are able to communicate with resources in the same VPC, but they may also be able to communicate with resources in other VPCs or accounts if the appropriate permissions are not set. Allowing cross peering connectivity can pose a security risk by allowing unauthorized access to sensitive resources, so it's important to ensure that it is only allowed when necessary and with the appropriate safeguards in place.


To remediate the issue of cross peering connectivity being allowed by Pod, you can take the following steps:

  1. Update the network policies: Create network policies for the Kubernetes cluster that explicitly allow traffic only to the required peers. Network policies define the rules that allow or deny traffic to Kubernetes pods. Update the network policies to block any traffic to unwanted peers.
  2. Use Kubernetes security contexts: Use Kubernetes security contexts to limit the capabilities of pods. Security contexts specify the security settings for a pod, such as the user ID, group ID, file permissions, and SELinux context. You can use security contexts to ensure that the pod does not have excessive privileges and that it cannot access other pods in the cluster.
  3. Disable the kube-proxy: kube-proxy is a network proxy that runs on each node in a Kubernetes cluster. kube-proxy enables network communication between different pods in the cluster. If the pod does not require network communication with other pods, you can disable kube-proxy to prevent any cross peering connectivity.
  4. Use network isolation: Use network isolation to separate the different pods and services in the Kubernetes cluster. This can be achieved by creating separate virtual networks for different pods or services. Network isolation can prevent unauthorized access to pods and services that are not required.
  5. Use Kubernetes Network Policies: Kubernetes Network Policies are an additional layer of security that can be used to control traffic within a Kubernetes cluster. Network Policies are similar to traditional firewall rules and allow you to define ingress and egress rules for pods. Network Policies can be used to block traffic to unwanted peers and ensure that pods are only communicating with the required peers.

By implementing these remediation steps, you can prevent cross peering connectivity from being allowed by pods in a Kubernetes cluster.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.
Deploy cloud infrastructure changes with confidence. Troubleshoot faster with the complete context of your cloud environment.