text stringlengths 0 1.49k |
|---|
[1838.92 --> 1840.42] So it |
[1840.42 --> 1841.40] includes NSX-T, |
[1842.12 --> 1844.10] which is |
[1844.10 --> 1844.90] VMware's overlay |
[1844.90 --> 1845.36] network. |
[1845.52 --> 1846.20] It's the second |
[1846.20 --> 1847.22] generation of |
[1847.22 --> 1847.40] it. |
[1848.52 --> 1849.10] And what this |
[1849.10 --> 1849.98] does over |
[1849.98 --> 1851.52] any of the |
[1851.52 --> 1852.20] other solutions |
[1852.20 --> 1853.04] that are out |
[1853.04 --> 1853.36] there, because |
[1853.36 --> 1854.46] most people will |
[1854.46 --> 1855.60] typically go with |
[1855.60 --> 1856.42] Flannel originally |
[1856.42 --> 1857.18] and then maybe |
[1857.18 --> 1858.04] look at something |
[1858.04 --> 1858.92] like Calico for |
[1858.92 --> 1859.64] the policies. |
[1859.64 --> 1861.98] it actually |
[1861.98 --> 1863.90] gives every |
[1863.90 --> 1865.54] pod a |
[1865.54 --> 1865.88] container |
[1865.88 --> 1866.44] interface that |
[1866.44 --> 1866.72] can be |
[1866.72 --> 1868.02] managed outside |
[1868.02 --> 1870.00] of just the |
[1870.00 --> 1870.76] environment. |
[1870.92 --> 1871.30] So you can |
[1871.30 --> 1871.82] have a network |
[1871.82 --> 1872.66] administrator who |
[1872.66 --> 1873.12] sets up a |
[1873.12 --> 1874.26] bunch of global |
[1874.26 --> 1875.26] policies in some |
[1875.26 --> 1875.88] other system, |
[1876.18 --> 1876.96] the NSX |
[1876.96 --> 1877.82] management plane, |
[1878.32 --> 1878.96] and that will |
[1878.96 --> 1880.02] then translate |
[1880.02 --> 1880.84] into rules for |
[1880.84 --> 1881.54] Kubernetes, for |
[1881.54 --> 1881.90] example. |
[1883.56 --> 1884.48] There's more |
[1884.48 --> 1885.28] stuff to it, |
[1885.34 --> 1885.74] right, because |
[1885.74 --> 1886.72] NSX-T is quite |
[1886.72 --> 1887.48] an extensive |
[1887.48 --> 1888.82] piece of work. |
[1890.44 --> 1891.68] So it's pretty |
[1891.68 --> 1892.92] optimized in how |
[1892.92 --> 1893.44] it deals with |
[1893.44 --> 1894.14] sending traffic |
[1894.14 --> 1896.30] and doing the |
[1896.30 --> 1897.40] routing rules and |
[1897.40 --> 1897.98] so on, but those |
[1897.98 --> 1898.68] are implementation |
[1898.68 --> 1900.08] details of NSX-T |
[1900.08 --> 1900.50] itself. |
[1902.10 --> 1903.32] What is unique, |
[1903.40 --> 1904.40] I think, is that |
[1904.40 --> 1905.26] it has a |
[1905.26 --> 1905.56] centralized |
[1905.56 --> 1906.52] management plane |
[1906.52 --> 1907.38] for all types |
[1907.38 --> 1907.94] of container |
[1907.94 --> 1908.54] interfaces. |
[1909.96 --> 1910.76] And that is |
[1910.76 --> 1912.66] where Kubernetes |
[1912.66 --> 1913.50] also takes |
[1913.50 --> 1914.30] advantage of it. |
[1914.70 --> 1915.48] So NSX-T |
[1915.48 --> 1916.40] has, or the |
[1916.40 --> 1917.46] NSX team, |
[1917.48 --> 1919.30] has an |
[1919.30 --> 1920.08] integration for |
[1920.08 --> 1920.88] Kubernetes that |
[1920.88 --> 1921.50] it also works |
[1921.50 --> 1922.74] with some of |
[1922.74 --> 1922.98] the other |
[1922.98 --> 1923.40] Kubernetes |
[1923.40 --> 1924.78] distributions. |
[1925.90 --> 1926.48] And so, yes, |
[1926.50 --> 1926.92] it's a very |
[1926.92 --> 1927.58] important piece |
[1927.58 --> 1928.36] of it, the |
[1928.36 --> 1930.64] security aspects |
[1930.64 --> 1931.44] that NSX-T |
[1931.44 --> 1932.08] brings to bear. |
[1932.72 --> 1933.66] Now, if I |
[1933.66 --> 1934.26] remember right, |
[1934.32 --> 1935.08] there's a lot |
[1935.08 --> 1935.74] of components |
[1935.74 --> 1936.52] that have been |
[1936.52 --> 1937.86] built by either |
[1937.86 --> 1939.06] Pivotal or |
[1939.06 --> 1940.92] VMware that |
[1940.92 --> 1941.64] kind of contribute |
[1941.64 --> 1942.32] to this system. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.