All right, so for our game plan for the network,
let me go ahead and just chat about a few critical components.
One is DNS.
We need to make sure that we have our internal DNS
and that everything is resolvable.
We also want to make sure that we have internet access
and that would include features like a default gateway
for clients to use on a given subnet
and also some flavor of NAT or PAT
to make sure that we are translating from our private address
bases would go out to the public internet.
And one other element I'd also coach you strongly about
is for the actual infrastructure that we're going to be using WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is for the actual infrastructure that we're going to be using
for the Kubernetes and then eventually the NSX application
platform, I'm going to recommend no SDN, no software
find networking.
Now I know it is really, really cool and easy to spin up
and create T0 gateways and tier one gateways
and all the segments, whether they're VLAN based or overlay
based and that those can be used to connect to external networks
and so forth.
However, what I want to put out here from experience WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
However, what I want to put out here from experience
over the last week and a half of doing this more than a dozen
times is that if we're going to implement our Kubernetes
on top of a software defined network,
we are asking for a world of hurt.
So although there is the possibility of successfully
implementing the NSX application platform on top of a SDN
network, it would be better as part of our infrastructure
to go ahead and just use traditional VLANs
and traditional routers for supporting the infrastructure
including the Kubernetes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
including the Kubernetes.
So although we don't have to avoid SDN and software
to find networking for the actual Kubernetes
and the NSX application platform itself,
I would strongly recommend doing it without it.
And that way you have that as part of your infrastructure
to support the other routing and switching
or implementing with software via NSX.
Another key element I would point out
is let's avoid using 192, 168, anything.
Because there is some IP addressing using that space
as part of the NSX application platform WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as part of the NSX application platform
and the underlying Kubernetes.
So if you're trying to use that as well
for network reachability,
that can also go ahead and cause grief.
So I'm going to go ahead and stay positive here
and I'm going to remove these nodes
and just focus on the key elements that we want to implement.
So for our game plan, for our infrastructure,
I'm going to be using a top of rack switch right here.
I'll label that T-O-R for top of rack.
And it's going to be the core device.
It's just so happens that I have this in my network already.
I'm going to be using it for the network
to support the NSX application platform. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to support the NSX application platform.
So again, the part about it being Cisco isn't too critical.
I just want to let you know what it is.
So for our game plan, let's go ahead and use this network
right here and let's use in my network, let's use VLAN 10.
And that's using the IP address space of 10.10.0 with a/24.
And then over here, the top of rack switch,
this multi-layer switch, it has the IP address of .1
on that 10.10.10 network.
So I just want to reinforce that I'm using a physical gateway
here connected to this VLAN.
And I'm not using a tier 0 or a T1 gateway WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I'm not using a tier 0 or a T1 gateway
as part of the infrastructure that we're setting up here
for the NSX application platform.
So another network I'd like to go ahead and use
as part of the infrastructure here is going to be VLAN 11.
So for VLAN 11, the addressing space we're going to use here
is 10.11.11.0 with a 24-bit mask.
So anytime we see VLAN 11, we'll know
as the network, the IP address space of 10.11.
And over here, the top of rack switch
has the default gateway address of .1.
Then next, let's go ahead and use another VLAN.
Let's use VLAN 12. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's use VLAN 12.
And for the IP address space for VLAN 12,
we use 10.12.12.0 with a/24 bit mask.
And the default gateway here will be .1.
And let's use one more network here as well.
And that will be VLAN 13.
So that's the layer two broadcast domain, VLAN 13.
And for the IP address space for devices in that VLAN,
let's use 10.13.13.
With a 24-bit mask.
In fact, to make this easier to read,
we're going to assume that we're using a /24
for all the networks as part of this topology. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for all the networks as part of this topology.
And the top of rack switch is going
to be the default gateway of .1 for that 10.13.13 address
space.
So for DNS services, I'd like to place my little Windows
server here on the 10.10.10 network at .100.
So as part of our infrastructure and testing,
we want to verify this little Windows servers here
at 10.10.10.100.
And we're going to be using that server for DNS for name
resolution, as well as network time protocol.
So before we're completely done,
we'll want to verify that all that is working.
And then here on VLAN 11 on the 10.11.11 address space, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then here on VLAN 11 on the 10.11.11 address space,
this can be my management network,
not just for the management of my ESXi host and for vCenter,
which is also true for that.
But it's also going to be the management network
for the Kubernetes cluster.
And then as part of Kubernetes, it's
also going to ask us for a front-end network.
So we're going to use VLAN 12 for that.
And it's also going to want a workload network.
So we'll need to make sure that we have these VLANs in place,
that my switching environment supports it.
And also that vSphere knows about it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And also that vSphere knows about it.
For example, having port groups for the management network
and port group for the front-end network
and a port group for the workload network
from a distributed switch.
We also want to make sure we're providing internet access.
So in my lab environment here, I've
got this top-of-rack switch, which I mentioned
is a Cisco multilayer switch.
And then I have another router right here,
which happens to be a 40-gate router.
And that is then connected to the internet.
So as far as the vendors are concerned,
it really doesn't matter.
You can use whichever vendor you want,
as long as you have the functionality.
So they've got a little common network segment here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So they've got a little common network segment here.
So the top-of-rack switch has a default route going this way.
And then at this router, I'm implementing NAT,
or more specifically, PAT, port address translation.
So if device is here, trying to reach a remote network,
they'll use their default gateway.
The top-of-rack switch, that routing environment,
will forward that traffic based on its routing tables
to my external router here, who will then
provide the network address translation services
before saying that traffic out to the internet.
So we want to verify that DNS is working.
We want to verify that internet access is working, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We want to verify that internet access is working,
including the use of a default gateway here
at my top-of-rack switch.
And if we do access the internet,
we'll also be able at that point
to verify that NAT/ PAT is working as well.
Now as we continue in the subsequent sets of videos
and subsequent skills, we'll be using this topology
that we've now implemented and verified
as the place where we can then deploy
the Kubernetes cluster.
And then after that, the NSX application platform
that's using the Kubernetes cluster.
So I can't stress how important it is
to have this infrastructure in place and tested, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to have this infrastructure in place and tested,
because just one tiny little element
out of the many prerequisites that have to be in place
if just one of them isn't correct,
it's gonna cause us a failure as we get to the point
of deploying the NSX application platform.
Now, one question might be, well, if we implement this,
for example, we have all these VLANs created,
we have our top-of-rack switch setup,
we have all the routing and that setup as well,
how do we test it prior to implementing
and deploying the NSX application platform?
The answer is we should probably place VMs, little VMs, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The answer is we should probably place VMs, little VMs,
tiny ones that are very quick to deploy
on each of these segments, just to verify
that they can use this DNS server,
just to verify that NTP is working,
and also verify that they can get access out to the internet,
because it's a lot better to identify a problem
with our topology here, rather than waiting
for the deployment of the NSX application platform,
and then having some weird or abstract error come up
that we're not sure what it is,
when it was all based on our infrastructure
not working correctly.
So as part of getting this all up and working WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So as part of getting this all up and working
and functioning, we have a couple of tasks.
Number one is we need to make sure
that the physical environment has these VLANs
and that they exist, and also from a vSphere environment,
we also wanna make sure we have poor groups
that reflect this as well.
So here's what I propose we do.
Let's head over to vSphere first,
and just take a look at the hosts that we plan on using,
also give some tips on starting points
to help avoid problems later,
and we'll make sure that we have connectivity
to these VLANs via port groups.
So I'll see you in the next video WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'll see you in the next video
as we take a look at this topology
from the perspective of vSphere.
So I'll see you there in just a moment.