<?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 Cisco ACI and Kubernetes Integration - encap_type VXLAN or VLAN in Containers</title>
    <link>https://community.cisco.com/t5/containers/cisco-aci-and-kubernetes-integration-encap-type-vxlan-or-vlan/m-p/3878196#M40</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;regard ACI and Kubernetes Integration, when we deploy the&amp;nbsp;&lt;SPAN&gt;Kubernetes VMM domain with &lt;STRONG&gt;acc-provision&lt;/STRONG&gt; we have option to choise to use &lt;STRONG&gt;VXLAN&lt;/STRONG&gt; or &lt;STRONG&gt;VLAN&lt;/STRONG&gt; as &lt;STRONG&gt;&lt;EM&gt;encap_type&lt;/EM&gt;&lt;/STRONG&gt;&amp;nbsp;used by &lt;STRONG&gt;OPFLEX&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Questions:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Which is the best practice or suggested option to use?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If we decide to use VLAN pool, I suppose them have to exists between leaf and&amp;nbsp;openvswitch container running on the host. In this case we will have one subinterface on linux host for each vlan? If yes, we need a new interface or it is possibile to use the same used for infra? And in case, will this subinterface be created during the addition of annotation?&lt;/P&gt;</description>
    <pubDate>Sun, 23 Jun 2019 22:36:33 GMT</pubDate>
    <dc:creator>Roberto Pancrazio Loiudice</dc:creator>
    <dc:date>2019-06-23T22:36:33Z</dc:date>
    <item>
      <title>Cisco ACI and Kubernetes Integration - encap_type VXLAN or VLAN</title>
      <link>https://community.cisco.com/t5/containers/cisco-aci-and-kubernetes-integration-encap-type-vxlan-or-vlan/m-p/3878196#M40</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;regard ACI and Kubernetes Integration, when we deploy the&amp;nbsp;&lt;SPAN&gt;Kubernetes VMM domain with &lt;STRONG&gt;acc-provision&lt;/STRONG&gt; we have option to choise to use &lt;STRONG&gt;VXLAN&lt;/STRONG&gt; or &lt;STRONG&gt;VLAN&lt;/STRONG&gt; as &lt;STRONG&gt;&lt;EM&gt;encap_type&lt;/EM&gt;&lt;/STRONG&gt;&amp;nbsp;used by &lt;STRONG&gt;OPFLEX&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Questions:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Which is the best practice or suggested option to use?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If we decide to use VLAN pool, I suppose them have to exists between leaf and&amp;nbsp;openvswitch container running on the host. In this case we will have one subinterface on linux host for each vlan? If yes, we need a new interface or it is possibile to use the same used for infra? And in case, will this subinterface be created during the addition of annotation?&lt;/P&gt;</description>
      <pubDate>Sun, 23 Jun 2019 22:36:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/containers/cisco-aci-and-kubernetes-integration-encap-type-vxlan-or-vlan/m-p/3878196#M40</guid>
      <dc:creator>Roberto Pancrazio Loiudice</dc:creator>
      <dc:date>2019-06-23T22:36:33Z</dc:date>
    </item>
  </channel>
</rss>

