<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: In the environment of kubernetes(AWS EKS), the traffic information of the container cannot be obtained in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/In-the-environment-of-kubernetes-AWS-EKS-the-traffic-information/m-p/111154#M452</link>
    <description>&lt;P&gt;Traffic information in containers is a very complexed topic, since there are too many CNI specific implementations. The plan for now is to provide topology visibility of containerized environments, and then look for a generic solution to monitor the traffic. There's no ETA specified at the moment.&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jun 2020 08:49:55 GMT</pubDate>
    <dc:creator>dglugla</dc:creator>
    <dc:date>2020-06-02T08:49:55Z</dc:date>
    <item>
      <title>In the environment of kubernetes(AWS EKS), the traffic information of the container cannot be obtained</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/In-the-environment-of-kubernetes-AWS-EKS-the-traffic-information/m-p/111153#M451</link>
      <description>&lt;P&gt;In the environment of kubernetes(AWS EKS), the traffic information of the container cannot be obtained.&lt;/P&gt;&lt;P&gt;kubernetes(AWS EKS) uses cni by default for network communication&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/aws/amazon-vpc-cni-k8s"&gt;https://github.com/aws/amazon-vpc-cni-k8s&lt;/A&gt;&lt;/P&gt;&lt;P&gt;/usr/bin/kubelet --cloud-provider aws --config /etc/kubernetes/kubelet/kubelet-config.json --kubeconfig /var/lib/kubelet/kubeconfig --container-runtime docker&lt;STRONG&gt; --network-plugin cni&lt;/STRONG&gt; --node-ip=x.x.x.x --pod-infra-container-image=602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/pause-amd64:3.1 --node-labels=role=generic-worker,eks.amazonaws.com/nodegroup=generic-worker&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/24561-1586400689118.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/24552-1586401068516.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/24571-1586400697146.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Does it not support docker network monitoring under Kubernetes?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Apr 2020 02:56:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/In-the-environment-of-kubernetes-AWS-EKS-the-traffic-information/m-p/111153#M451</guid>
      <dc:creator>olin_li</dc:creator>
      <dc:date>2020-04-09T02:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: In the environment of kubernetes(AWS EKS), the traffic information of the container cannot be obtained</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/In-the-environment-of-kubernetes-AWS-EKS-the-traffic-information/m-p/111154#M452</link>
      <description>&lt;P&gt;Traffic information in containers is a very complexed topic, since there are too many CNI specific implementations. The plan for now is to provide topology visibility of containerized environments, and then look for a generic solution to monitor the traffic. There's no ETA specified at the moment.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2020 08:49:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/In-the-environment-of-kubernetes-AWS-EKS-the-traffic-information/m-p/111154#M452</guid>
      <dc:creator>dglugla</dc:creator>
      <dc:date>2020-06-02T08:49:55Z</dc:date>
    </item>
  </channel>
</rss>

