- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi!
To start with, check out this article for a great solution to address your challenge with a little extension. Very simply, the EKS cluster is deployed with worker nodes (EC2) and these have one or more ENIs attached to accommodate the pods deployed with the VPC CNI.
You will always need to map the IP with the pod name in the VPC which you can see using this command:
kubectl get pods --all-namespaces -o wide
The main issue is that these can change if the pod migrates, gets restarted etc. You could use the solution above and extend it further with Athena to merge the flowlogs data with a "pod name to IP mapping" document to create the picture you are looking for. See the INSERT INTO function for some ideas.
AWS Detective allows you to examine VPC flow log information for your EKS workloads, display visual summaries about these network flows, and aggregate information by EKS pods.
This still does not capture flows between pods within the same node. @Mstein-AWS and @AWS-User-7455027
Contenus pertinents
- demandé il y a 9 mois
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 mois
- Comment choisir des sous-réseaux IP spécifiques à utiliser pour les pods de mon cluster Amazon EKS ?AWS OFFICIELA mis à jour il y a un an
Hi @Mstein, Thanks for the reply. But this link, I am not able to open this article in "check out this article for a great solution". While I can open the INSERT INTO link.