►
Description
Red Hat OpenShift can run and manage both Linux and Windows containers from one platform, so you're able to move Windows containers to OpenShift without needing to completely re-architect or write new code. And this week, Christian Hernandez, Technical Marketing Manager for Red Hat Cloud Platforms Business Unit, joins the live stream to cover the ins and outs of bringing your own Windows nodes to OpenShift. We'll look at configuring a cluster with hybrid Open Virtual Networking (OVN) Kubernetes networking and using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. Curious about the advantages of running Windows containers in OpenShift? As a developer, this means that you have one platform for Linux and Windows-based application components, and as an administrator, the consolidation of infrastructure (hopefully!) makes life simpler. Bring your questions and join us to learn more about Windows Container Support for Red Hat OpenShift.
We’ll also be celebrating the one-year anniversary of Ask and OpenShift Admin, so join the live stream and celebrate with us!
Learn more:
https://docs.openshift.com/container-platform/4.7/windows_containers/windows-containers-release-notes-2-x.html
About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Chris Short sit down to answer your questions about Red Hat OpenShift.
Follow us:
Christian Hernandez https://twitter.com/christianh814
Andrew Sullivan https://twitter.com/practicalandrew
Chris Short https://twitter.com/chrisshort
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
Openshift.com https://red.ht/33Fh6uV
OpenShift on github https://github.com/openshift/
OpenShift on redhat.com https://red.ht/2o4ccDk
#RedHat #OpenShift #ContainerPlatform
A
A
A
B
C
A
B
So
yeah
it's,
I
was
actually
talking
with
my
wife
earlier
this
morning.
Talking
about
so
the
the
room
is
a
shade
of
green.
So
I
couldn't
do
like
a
green
screen
in
the
squirrel
picture,
but
I
could
do
blue
and
then
I
could
just
randomly
phase
it
out
for
other
things.
You
know
using
some
sort
of
software
yeah.
B
B
Yeah
very
much
so
I
I
took
the
opportunity
to
collect
some
metrics
around
what
we
have
done
in
that
past
year.
So
if
it's
not
obvious
right
from
the
title
of
this
stream,
this
is
episode
43.
so
effectively
in
42
shows.
We
have
been
averaging
right
around
a
thousand
views
per
video
wow,
which
is
pretty
good,
pretty
impressive
right,
I
mean
you
know.
This
is
a.
B
Yeah,
and
so
for
something
that
is
both
technical
as
well
as
a
live
stream,
which
you
know,
the
three
of
us
have
had
lengthy
conversations
around
things
like
content
discovery
right.
How
do
we
make
sure
that
people
can
find
this
information
afterwards?
You
know
how
do
we
make
sure
that
it
is
you
know
relevant
and
evergreen?
B
We've
been
on
gosh
countless
meetings
together
of
tell
me
if
I'm
wrong,
like
I,
I
love
it
when
you
all
call
me
out
and
like
that's
what
we're
here
for
so
yeah
it's
it's
been
a
lot
of
fun,
so
yeah
40,
it's
just
shy,
or
just
over
41
000
views
on
youtube
alone,
so
that
doesn't
include
twitch.
That
doesn't
include
back
when
we
started
when
we
were
doing
what
is
the
twitter
thing,
periscope
yeah
yeah?
B
B
B
But
christian
and
reese
hosted
the
first
hour
talking
about
the
assisted,
installer
and
then
no
no
surprise.
The
third
most
popular
episode
was
when
robbie
jerome
joined
us
to
talk
about
vmware
openshift
on
vmware,
which
we've
been
talking
about,
bringing
the
vmware
folks
back
on.
So
I
don't
know
if
robbie
will
join
us,
but
perhaps
one
of
the
folks
on
his
team
will
be
able
to
join
so
lots
of
stuff
happening
there.
B
So
you're
done,
okay,
I've
got
I've,
got
two
more
statistics
to
cover
so
that
the
top
couple
of
episodes
from
just
a
minutes
watched
so
in
the
last
90
days
again.
That
was
all
we
pulled
to
watch
this
statistics
for,
if
I
could
speak
this
morning,
so
the
the
most
watched
episode
has
been
the
high
availability
episode
yeah,
and
I
think
that
one
yeah
that
one
had
now,
I
don't
have
it
up
anymore,
but
that
one
was
the
highest
by
a
like
a
15
margin.
B
The
next
was
compliance
and
security,
and
then
last
but
not
least,
or
in
third
place,
I
should
say-
was
acm
advanced
cluster
manager,
so
kind
of
expected
topics
there
right.
It's.
I
like
looking
at
these
things,
because
it
gives
me
an
idea
of
what's
interesting
to
you
all
so
and
always
never,
please,
don't
ever
hesitate
to
send
me
suggestions
or
requests
for
topics
yeah.
I
I
love
those
I'm
going
through
doing
show
planning.
B
B
So
yeah,
don't
don't
please
don't
ever
hesitate.
You
can
reach
out
on
social
media,
practical,
andrew
on
twitter
or
andrew.sullivan
redhat.com
via
email.
Don't
ever
hesitate
to
reach
out
with
a
request
or
a
suggestion
for
a
topic,
and
then
the
last
one
that
I
have
is
a
kind
of
a
simple
one.
If,
if
you
don't
know
we
stream
simultaneously
to
three
different
places,
so
we
stream
to
twitch.
B
Of
course,
we
stream
to
the
openshift
youtube
channel
and
we
stream
to
the
red
hat
youtube
channel
so
long
term,
because
twitch
of
course
rolls
videos
off
openshift.
The
openshift
youtube
channel
accounts
for
about
64
of
our
traffic
of
of
our
watch
time.
So
it's
you
know,
openshift
folks,
love
to
talk
about
openshift
or
hear
me
talk
about.
B
A
A
B
B
So
all
of
the
like
that
fancy
intro
graphic
that
you
see
all
of
the
other
stuff
like
that's
all
them
and
they've
done
a
just
a
great
job
of
both
the
public-facing
stuff
as
well
as
helping
you
know
me
and
chris
with
the
organization
and
getting
better
at
the
the
promotional
side
of
things
and
all
of
that,
so
I
I
can't
thank
them
enough.
All
right,
I'm
done
rambling
and
talking
about
us
and
and
the
stream.
So
chris,
you
said
that
there
was
a
question.
There
is
a
question.
A
C
B
A
A
C
A
C
B
And
just
to
clarify
so
odf
is
openshift
data
foundation,
which
is
the
rebranded
name
for
openshift
container
storage,
because
it's
more
than
just
what
was
traditionally
ocs
right.
It
has
evolved
to
include
a
bunch
of
other
things,
not
the
least
of
which
is,
of
course
nubo
for
object.
Storage,
you'll
be
seeing
oadp
coming
out
before
the
end
of
this
year
is
what
their
kcs
says.
So.
A
And
that
team,
the
odf
team,
we
have
a
show
slot
for
them
where
it
changes
out
storage,
admins
and
data
scientists
every
other
week
kind
of
deal.
So
it's
it's
a
nice
rotation
every
thursday
morning
at
9am,
so
you
can
catch
storage
and
people,
then,
using
that
storage
to
data
science
with
it
so
yeah.
It's
pretty.
B
A
B
Yeah
unprotected:
well,
it's
it's
funny
because
you
know
one
of
my
responsibilities
is
to
work
with
partners
and
I
work
with
several
storage
partners,
and
they
ask
me
you
know.
Oh
you
know
what
what
is
this
oadp?
What
is
this
data
protection?
Is
that
something
that
is
only
red
hat
only
ocs,
or
is
that
something
anybody
can
use?
Of
course,
and
it's
it's
an
open
set
of
apis.
B
B
I
know
that
there's
been
some
complications
there
so
kind
of
quickly
in
the
interest
of
time,
I'm
going
to
go
through
our
top
top
of
mind
topics.
So
please
do
keep
in
mind.
This
is
one
of
our
office
hours
series
of
streams,
so
don't
hesitate
at
any
point
in
time
to
ask
questions
about
whatever
the
topic
happens
to
be
so
I
christian
is
on,
and
christian
is
usually
one
of
my
escalation
points.
B
So
all
of
the
hard
questions
we'll
get
him
to
we'll
get
him
to
answer,
but
yeah
don't
hesitate
regardless
of
what
we're
talking
about
on
the
stream.
Don't
hesitate
to
ask
ask
questions
and,
as
is
tradition,
I
like
to
have
a
little
segment.
If
you
will
up
front
that
talks
about
kind
of
top
of
mind,
timely,
relevant
things
that
I
think
are
important
for
for
you
all
for
our
audience.
So
I'm
going
to
share
my
screen
here
drag
your
little
window
of
of
heads
around.
B
A
B
B
So
if
we
come
to
the
console
here,
we
go
to
open
shift
and
we
go
to
releases
so
in
4.8
you
can
see
in
fast
we've
got
4.8.11
and
4.7.30,
so
these
two
versions
incorporate
a
number
of
fixes
for
kind
of
outstanding
bz's
outstanding
issues
that
have
been
blocking
upgrades.
So
I
want
to
highlight
the
three
of
those
that
have
been
the
most
significant
and
just
point
out
that
hey
these
are
fixed
if
you're
encountering
some
issues.
B
A
C
B
Means
I'm
either
under
or
over
caffeinated.
So
this
one
came
up,
you
can
see
it
was
opened.
The
end
of
october.
Excuse
me
the
end
of
august,
so
this
one
came
up,
they
went
they
fixed
it.
We
should
be
good
on
again.
I
think
it's
4.8.10
was
the
first
one
or
29
was
the
first
one
to
include
this,
but
they're
kind
of
lumping
all
of
these
into
the
11
and
30
releases.
B
So
if
you
encountered
any
issues
with
that
again,
please
be
sure
to
update
as
soon
as
possible
the
next
one,
and
this
one
was
definitely
much
more
broad
creo
having
a
leak
in
the
run
fs,
so
slash
run
fs.
So
this
one
was
first
found
in
in
4.9.
It
turned
out
to
also
be
an
issue
in
earlier
versions,
so
they
back
ported
that
so,
if
we
scroll
this,
one
has
a
long
common
chain,
but
if
we
end
up
all
the
way
down
here
at
the
bottom,
you
can
see.
B
4.10
4.11
is
when
it
is
fixed.
So
definitely
be
aware
of
cognizant
of
that
you
will
probably
have
to
if
you
have
long
running
nodes
that
meet
the
various
conditions.
Inside
of
here,
you
may
have
to
reboot
those
occasionally
in
order
to
reset
it,
but
if
you
update
to
4.10
or
later
4.8.10,
not
4.10
for
that
8.10
or
later
that
one
is
fixed
as
well
as
whatever
the
equivalent
version
in
4.7.
B
If
I
scroll
up
here
slightly,
it
looks
like
it
may
be:
27
4.7.27
or
later
and
last
but
not
least,
we
have
a
an
issue
that
is
near
and
dear
to
my
heart,
because
this
one
was
also
or
a
very
similar.
One
was
also
an
issue
with
the
4.6
to
4.7
upgrades
in
the
early
updates,
and
that
is
a
issue
with
vmxnet
vmxnet3
network
adapters.
B
So
if
you
have
a
default
ipi
install,
you
may
not
be
hitting
this
one
if
you're,
using
if
you've
modified
it
or
if
you've
done
upi,
then
you
are.
You
have
a
high
chance
of
hitting
this
particular
bug,
so
the
issue
is
effectively
you'll
see
some
packet
loss
happening
inside
of
the
cluster
as
before
the
resolution
is
to
turn
off
the
offload,
so
the
first
time
it
was,
it
was
the
it
was
the
vxlan
offload
this
time.
The
solution
is
this:
ip
generic
transaction
or
transmission
checksum
ip
generic.
B
B
B
A
C
A
C
B
B
C
A
B
So
the
first
thing
I
want
to
bring
up
here
or
or
ask
you
christian
is
windows,
nodes
aren't
new.
You
know,
we've
supported
windows,
nodes
for
since
at
least
four
seven
in
a
ga
status
yeah,
but
it
was
limited.
So
what
we're
talking
about
now
is
an
expansion
of
capabilities
right.
It's
it's
less
limited
than
it
was
before
so.
C
You
know
we
want
to
get
everything
completely
automated,
making
making
sure
that
it's
up
there
with
functionality
with
the
linux
nodes
in
terms
of
the
ipi
install,
and
then
there
is
also
the
later
on
in
4.7
we
we
did
the
vsphere
ipi,
so
so
it's
nothing
new
right.
We,
I
came
on
the
show
before
we
talked
about
windows
nodes,
and
you
know
how
that
works
out.
So
we're
getting
excited
for
this
next
release
of
the
wmco,
which
is
the
windows
machine,
config
operator,.
A
C
So
the
wimco,
the
next,
the
next
release,
which
is
due
at
the
end
of
the
month
or
beginning
october.
I
mean
we're
always
in
in
open
in
openshift
land
right
like
we're,
always
like
it's
probably
will
be
released
if
everything's
pretty
good,
which
is
kind
of
a
for
our
red
hat
customers.
That's
kind
of
like
a
weird
thing,
because
you
know
with
with
rel
it
was:
it's
always
been
like
the
the
same
cadence
and
when
we
say
it
will
be
released,
it's
released,
but
so
the
the
wimco
is.
C
The
next
release
will
be
at
the
end
of
this
month,
so
hopefully,
in
a
few
weeks,
we're
adding
what
we
call
bring
your
own
host
right
or
so
it's.
So
this
is
the
idea
for
the
upi
installations,
so
the
upi
specifically
for
the
bare
metal
installs,
so
we're
bringing
support
for
the
bare
metal
or
as
more
specific,
a
platform,
agnostic,
upi,
install
right,
more
specific
right
platform.
C
B
C
So
it
is
for
all
upi
right,
so
it's
for
all
all
upi
installs,
so
not
just
the
platform
agnostic,
non-integrated,
upi
install,
but
also
what
what
I'll
be
kind
of
just
going
over
and
demoing
is
the
the
vsphere
upi
so
which
is
kind
of
interesting.
So
I
think
this
version
breaks
the
mold
a
little
bit
of
of
what
we
can
say,
because
this
is
because
this
is
technically
a
vsphere
ipi
install,
but
I'm
adding
a
upi
windows
node
into
the
into
the
mix
which.
B
That
you
know,
we've
talked
about
it
a
couple
of
times
here
on
the
stream,
but
you
can
deploy
an
ipi
cluster
and
you
can
add,
nodes
outside
of
machine
sets
yeah
I've.
What
did
I
do
that?
For
I?
I
did
a
proof
of
concept
for
oh
moving,
the
or
moving
the
ipi
load
balancer
to
an
external
load
balancer.
So
I
I
tested
that
extensively
and
it
works
quite
well,
not
the
load.
Balancer
part,
the
machine
sets
the
load.
Balancer
part
does
work,
but
it's
not
supported.
C
So
yeah,
so
that's
so
that's
kind
of
like
the
the
gist
of
windows
containers
bring
your
own
host.
So
I
will
I
prepared
kind
of
like
a
demo
like
I
was.
I
was
telling
andrew.
You
know
we'll
walk
through
some
of
the
steps,
but
I
have
like
I
said
since
it's
a
cooking
show.
I
prepared
some
stuff
like
offhand
so
that
way
we're
not
just
watching
screens
go
by.
So
let
me
let
me
first
share
my
screen
and
I'll
go
I'll.
Do.
B
So
christian,
while
you're
bringing
that
up
is
there?
Are
there
any
other
changes
to
the
windows,
machine,
config
operator
or
the
capabilities
kind
of
requirements
of
those
windows
nodes
like
I
assume
we
still
need
open
ship
or
ovn
kubernetes
with
hybrid
overlay?
Are
we
able
to
domain
join
windows,
nodes.
C
C
We
can
oh,
let
me
make
that
bigger.
Thank
you,
so
yeah
so
kind
of
the
the
prerequisites
and
that
that
sort
of
thing
right,
so
the
prerequisites
are
the
same
right.
This
is
kind
of
like
an
incremental,
I
would
say,
update.
The
focus
was
really
on
bringing
windows
nodes
that
outside
of
the
control
of
of
machine
sets
right.
So
it's
basically.
C
C
C
C
Exactly
yeah,
you
got
to
get
that
yeah,
that's
pretty
good,
so
I
mean
currently
with
with
wimco
version
two.
You
know
we
support,
like
I
said
before:
aws
azure
vsphere,
with
3.0
version,
3.0
it'll
be
it'll,
be
the
upi
installs,
essentially
right
so
it'll
be
version
3.0
and
and
above
this
will
change
as
well,
and
so
this
is
actually
a
kubernetes
thing.
So,
let's
look
at
these
windows
servers.
B
B
C
Yeah,
so
it's
it's
yeah,
so
it's
a
little
confusing
right.
So
you
know
here
to
four:
we've
had
we
said
all
right:
your
windows,
server,
2019
version
2004
or
when
you
write
it
2004
they're
like
what
is
that
still
supported?
No,
we
mean
we
mean
2004
anyways,
but
now
with
with
you,
know,
kubernetes
as
they
release
here,
we're
talking
about
windows,
server
2004,
you
know
20
h2.
I
guess
so
it's
kind
of
yeah.
I
guess
they.
A
A
C
B
C
Yeah
and
yeah,
someone
pointed
out
in
chat
windows,
server,
20
2022
is
ga,
and
we
do
not
plan
to
support
that
in
later
releases
because
it
includes
patches
that
we
desperately
need
to
make
some
of
the
other
functionalities
that
we
that
we're
thinking
about
working
so
but
for
now
2019
version
12,
either
2004
or
20
h2.
I
guess
they
call
it.
I
put
this
in
the
chat.
This
is.
C
Let
me
go
back
to
the
dock
so
now
so
now,
some
of
the
networking
information
right
so
in
order
to
the
prerequisites
are
the
same
right.
In
order
to
run
windows
containers,
you
need
to
install
ovn,
kubernetes
and
and
configure
hybrid
networking,
so
in
the
docs,
if
you
go
to
enabling
container
workloads,
the
prerequisites
are
listed
here
and
one
of
them
has
a
link
to
how
to
configure
hybrid
networking.
There's
this
big
old
red
exclamation
point
here.
C
Please
read
this
because
if
you're,
if
you're
preparing
for
windows,
containers
and
windows
nodes,
you
have
to
prepare
at
install
time
like
there's
no
way
to
install
the
cluster
and
then
switch
it
like.
Oh
hey,
I
want
this
cluster
to
run.
Windows
nodes
then
you're
out
of
luck.
If
you
didn't
do
these
prerequisites,
you
have
to
it's
essentially
reinstalled
right.
So
so
currently
really
two
configurations
need
to
be
set
here
and
then
I'll
switch
over
to
so.
C
Yeah,
so
there's
no
harm
in
turning
it
on
because
hybrid
configuration
it'll,
be
it's
basically
it'll
sit
there,
but
it's
not
it.
You
know
it's
not
doing
anything
until
you
add
something
that
supports
hybrid
overlay.
Networking.
I
think
the
only
other
thing
is
that
that
uses
that
I
think
it's
the
f5
plugin,
I'm
not
I'm
not
100
sure.
Don't
don't
quote
me,
there's
something
else
that
that
that
uses
the
hybrid
configuration
but
it'll
basically
sit
there
dormant
and
if
you're
using
ovn
kubernetes,
that's
gonna
be
the
default
anyway.
C
So
I
guess
you'll
be
the
ahead
of
the
curve.
So
so
here
I
have
like
I
said
I
pre-installed
get
the
version
here.
8.2
right,
I
guess,
there's
an
update,
but
it
works
with
8.2.
If
you
get
nodes
the
kubernetes
folks
slash
os
equals
linux
right,
it'll
just
list
all
the
linux
nodes.
You
can.
Actually
you
see
here,
no
funny
business.
So
hopefully
I
don't
pull
a
sully
here.
I'm
going
to
look
at
my
install
config.
A
C
Don't
don't
pull
a
sully
right
so
here,
so
so
this
here,
I'm
going
through
like
kind
of
the
prerequisites
and
how
it's
installed.
If
I
look
at
the
install
config
as
you
can
see
it,
it
takes
that
away
from
me.
Your
whole
secret
here
under
networking
you'll
have
network
types
set
to
ovn
kubernetes,
so
that
needs
to
be
set
in
the
install
config
file
and
then
the
other
thing
is:
let
me
get
the
network.
I
always
have
to
copy
and
paste
this
command
here.
C
So
the
I
think
you
have
to
set
hybrid
overlay
networking
right,
which
is
oh,
that
looks
ugly.
Where
is
it
there?
It
goes
so
there
it
is
so
hybrid
overlay
networking
basically
says
that
hey.
You
know
when,
when
you're
here's
the
ip
address
range
for
that
hybrid
overlay,
networking
configuration
this
here
is
the
vx
lan
port
this,
if
you're
on
vsphere
it
has
to
be
changed
right.
C
So
you
you,
you
have
to
change
it
because
of
a
bug,
or
else
containers
won't
be
able
to
communicate
with
each
other,
which
is
probably
what
you
want.
So
this
needs
to
be
changed.
This
is
all
called
out
in
the
documentation
right.
It
goes
through
the
steps
here
like
this
here.
It
even
calls
out
this
vxlan
port
important
to
note
that
it
must
be
set
for
vsphere,
but
it
must
not
be
said
for
others
or
others
right,
so
it's
kind
of
like
if
you're
not
on
vsphere,
it's
not
harmless,
it's
harmful.
B
B
B
You
can
absolutely
mark
those
control
plane
nodes
as
schedulable
on
day
one
or
at
install
time,
and
you
can
do
that
kind
of
two
ways.
So
one
with
ipi,
if
you
mark
the
actually,
I
don't
know
if
it's
supported
to
do
it
that
way,
although
it
does
technically
work
and
that
would
be
to
declare
zero
control
plane
nodes.
B
Alternatively,
you
can
do
a
in
your
install
config.yml,
so
you
have
three
control,
plane,
nodes,
three
compute
nodes
and
then
you
do
an
open
shift,
install
generate
manifest
and
it
will
spit
out
a
bunch
of
in
two
folders.
It
will
spit
out
a
bunch
of
files
and
in
one
of
those,
is
a
file
where
you
can
mark
the
control
plane
as
schedulable
and
all
of
those
just
for
kind
of
side
information.
All
of
those
files
become
what
goes
into
the
bootstraps,
install
config
or
ignition
file.
B
Rather
so,
yes,
you
can
absolutely
use
schedulable
control,
plane
nodes
with
a
traditional
deployment.
You
can
deploy
standards.
You
know
six
node
ipi
deployment
go
in
day,
two
mark
the
control
plane,
node
or
the
control
plane
is
schedulable,
and
then
you
can
scale
worker
nodes
down
to
zero.
If
you
want
and
then
you
know
scale
up,
if
you
need
to
no
absolutely
nothing
wrong
with
that,
whether
or
not
it's
suggested
is
really
completely
up
to
you
and
and
your
environment,
your
workload.
B
So
what
I
mean
by
that
is,
if
you
have
say,
a
cluster,
that's
a
hundred
nodes
or
a
cluster.
That
has
you
know
thousands
of
pods
inside
of
it
where
ncd
is
going
to
be
busy.
The
api
services
are
going
to
be
busy.
You
may
want
to
make
sure
that
you
know
there's
not
just
random
workload
running
on
the
control
plane,
so
that
way
it
can
have
access.
B
But
if
you
have
light
workload,
if
you
want
to
have
kind
of
a
scale
to
zero
type
of
thing
and
scale
up
from
there,
you
know
for
burst
stability
or
whatever
it
happens.
To
be
absolutely
you
know,
use
use.
Schedulable
masters
is
ossm,
so
openshift
service
mesh
still
slightly
funky,
with
ovn
kubernetes.
B
A
C
B
C
B
And
then
so
so
heikel,
my
apologies
for
butchering
names,
I'm
terrible
with
them.
So
can
you
please
elaborate
on
hybrid
network
and
that
is
more
or
less
the
same
question
I
was
going
to
ask
you
christian,
which
is
what
does
the
hybrid
network
actually
do,
and
I
think
it's
important
like
just
looking
at
the
config,
it's
important
to
highlight
two
things
here.
So
one
ovn
kubernetes
uses
geneve
as
the
overlay
technology,
whereas
the
hybrid
appears
to
use
vxlan.
C
C
C
I
guess
route,
I
guess
would
be,
would
be
the
best
the
best
way
to
to
call
it
gateway,
whatever
I'm
probably
getting
the
terminology
all
wrong,
but
it
creates
basically
a
layer,
three
communication
tunnel
between
this
service
network
and
this
other
service
network.
So
that
way
you
can
deploy
windows,
workloads
that
can
communicate
with
the
linux
workloads
over.
You
know
the
the
native
kubernetes
methods
right
with
service
right.
So
then
you
can
refer
to
something
as
the
service
name.
C
You
know
the
local
resolver
will
resolve
it
right.
Core
dns
will
resolve
it.
Yeah
and
the
networking
just
automatically
works
right.
So,
just
from
a
high
level,
the
hybrid
cluster
is
exact.
It's
essentially
that
the
hybrid
right,
you
have
two
software-defined
networks
and
the
hybrid
basically
connects
them
together.
B
Yeah,
I'm
I'm
curious
and
I'll.
I'm
gonna
take
a
note
to
ask
the
folks
is:
are
we
putting
vxlan
on
top
of
geneve
or
are
they
running
in
parallel
to
each
other
and
just
windows,
nodes
talk
to
the
rest
on
you
know,
vxlan
and
linux,
nodes
talk
to
the
rest
on
geneve
or
what
does
that
actually
look
like.
C
C
A
C
So
once
the
the
cluster
is
installed,
as
you
see
here,
you
know
it'll
it's
a
normal
openshift,
openshift
v4
4.8
cluster.
So
once
you
once
you've
installed
that
you
have
to
install
the
the
wimco
operator,
so
that's
easy
enough
right.
If
you
go
to
operator
hub
again
your
cube
admin
and
just
type
in
windows
which
feels
really
weird
right.
This
whole
this
whole
on
a
on
a
red
hat
system,
type
windows.
How
far
we've
grown.
C
Yeah
yeah
exactly
so
here
I
have
the
community
operator
so
for
those
of
you
who
are
using
juan
4.8
today
and
who
are
using
okd.
The
community
operator
supports
this
right,
so
I
have
that
installed
it.
It's
that
version
here
so
and
then,
but
when
this
gas
obviously
use
the
the
ga
release,
but
I'm
using
the
community
operator
that's
installed
and
then
one
last
prerequisite
right.
So
once
you
install
the
cluster
with
the
networking
freeware,
because
it's
once
you
install
the
wmco,
the
wimco
you
need
to.
C
Let
me
go
back
prerequisites
b
rooks
here
we
go
so
the
last
thing
is,
you
have
to
add:
you
have
to
provide
a
an
ssh
key
right,
so
you
get
to
create
an
ssh
key
pair
right,
private
public
key
here,
I'll
I'll,
actually
anchor
link
that
here
in
the
chat.
So
a
couple
of
things
to
note
right.
This
is
just
a
just
a
standard,
ssh
key.
C
You
have
to
upload
the
private
key
to
to
open
shift,
and
you
need
to
use
this
key.
You
need
to
use
the
public
key.
You
need
to
load
that
in
your
windows,
node,
which
I'll
show
in
a
second
how
you'll
load
that
into
the
windows.
Node
last
thing
I
want
to
call
call
out
is
that
you
need
it's
it's
one
key
per
cluster,
so
there's
there's
no
way
to
say:
hey
this
windows.
Node.
Has
this
key,
this
windows
node.
Has
this
other
key?
You
know
you
can't
have
multiple
keys.
C
So
currently
it's
one
key
per
cluster.
I
have
asked
about
this
because
my
first
question
when
I
was
testing
this
is
like
okay.
Well,
can
we
have
multiple
keys
right,
because
a
lot
of
the
times
I
would
imagine
administrators
would
want
to
have
separate
keys,
wanted
to
be
able
to
rotate
keys
so
that
that's
all
in
you
know,
backlog
that'll
be
addressed
right
because
I've
created
a
couple
rfes
around
that
so
so
yeah.
C
C
I
won't
expose
that
because
that's
an
actual
private
key
that
I
actually
use
in
my
actual
day-to-day,
but
trust
that
it's
there
so
so
once
you
have
those
installed
really,
the
prerequisites
for
the
open
shift
is
is
the
easy
part.
I
guess
for
me,
maybe
because
I'm
a
linux
guy,
kubernetes
guy
this,
this
all
was
easy
to
follow.
The
hard
part
was
actually
make
this
a
little
bigger,
actually
preparing
the
windows
notes.
C
C
C
C
C
C
C
B
C
C
Fine,
so
this
is
something
that
solely
showed
me
right,
while,
while
testing
this
out,
if
you
enable
what
is
a
p
s
r
remoting,
this
allows
you
to
use
powershell
remotely.
So
that
way
you
don't
have
to
connect
to
even
this
yeah
live
in
this
little
console
world
right.
So
here
what
I
like
doing
is
I
like
doing
pod
man
run
power,
shell.
Where
is
it
to
my
history
right?
So
you
can
actually
run
powershell
in
a
container.
C
C
C
Yeah
yeah,
okay,
so
you
install
docker,
docker
ssh
right
because
the
wimco
operator
uses
ssh.
You
have
to
open
a
few
firewall
port
rules
and
you
have
to
add
the
ssh
key
right,
so
the
ssh
key.
You
have
to
make
sure
that
ssa,
when
you
install
ssh,
you
gotta
miss,
make
sure
the
ssh
key
that
you
gave
the
operator
is
on
the
host
here.
This
is
something
weird
for
windows:
admins
right
for
us,
linux
guys
is
like
whatever,
but
you
could
only
have
lowercase
host
names.
C
So
what
does
that
mean?
That
means
that
the
let
me
go
back
to
so.
If
I
keep
this
as
this
uppercase,
the
it'll
just
barf
right,
so
you
have
to
change
the
hostname
for
this
for
this
host
to
lower
a
case
right,
it's
whatever
you
want
as
long
as
it's
lowercase.
So
as
sully
said
in
the
interest
of
time,
I
have
prepared
a
node
ahead
of
time
with
all
the
prerequisites
already
already
loaded
up
right
and
so
in
order
to
let
me
exit
out
of
this
here.
C
So
in
order
to
add
a
windows
node,
you
have
to
create
a
a
bring
your
own
host.
Node,
you
have
to
create
a
config
map
called
windows,
instances
right
so
here
you
name
yeah.
It
has
to
be
named
windows
instances
and
it
has
to
be
in
the
same
name
space
as
the
operator
and
essentially
you
just
give
it
ip
address
and
the
username
right.
C
B
B
C
C
C
C
Yeah,
it's
probably
because
a
machine
operator
unable
to
get
okay
yeah,
that
was
an
old
config
there.
It
was
barfing
at
an
old
config.
So
so
then
I
usually
just
tail
these
logs
and
these
logs
will
will
tell
you
that
it's
installing
here
so
this
will
take.
I
don't
know
like
two
minutes
or
so
you've
got
to
set
up
the
operator.
So
watch
that
so
this
is
so
yeah.
So
here
I'm
pausing
see
if
there's
any
any
any
questions.
So.
C
If
I
do
docker
images,
I
pre-pulled
the
the
image
specific
to
this
version
of
windows
so
for
windows.
It
matters
right
so
like
in
we've
been
kind
of
spoiled
in
the
linux
world,
where
hey
I'm,
just
gonna,
pull
an
ubuntu
image
and
run
it
on
openshift
and
it
runs
fine.
The
same
is
not
true
for
windows.
If
you,
if
you
try
to
run
a,
I
don't
know
server
2016
image
on
you
know
on
on
this
windows:
windows
2019,
it's
not
just
not
flat
out,
doesn't
work
and.
B
C
And
it
just
in
most
environments
that
just
takes
a
while
to
pull
the
default.
Timeout
is
two
minutes
right,
so
anything
that
takes
longer
than
two
minutes
to
pull
the
scheduler
will
say
error
and
then
it'll
try
to
pull
again
and
error.
It'll
try
to
pull
again
it'll
it'll,
basically
just
loop
forever,
because
the
image
will
never
get
pulled
because
of
the
timeout.
B
C
B
C
It's
on
the
roadmap
right
so
right
now
because
of
the
the
prerequisites
for
networking,
rosa
still
uses
openshift
sdn.
So
I
know
it's
on
the
roadmap.
I
know
they're,
you
know
all
the
hosted
right.
The
openshift
hosted
solutions
are
are
planning
on
eventually
supporting
this
right
is
because
it's
a
thing
of
like
preparing
right.
We
need
to
have
sres
right.
We
have.
B
C
B
Over
which
means
that
we
need
to
drop
for
the
next
next
stream
yeah.
We
will
have
some
more
windows,
node
goodness
happening
in
an
hour,
so
version
two
or
or
the
next
iteration.
If
you
will,
that
being
said,
thank
you
so
much
for
joining
us
today.
Thank
you.
So
much
for
a
great
first
year
of
the
ask,
an
open
shift.
Admin
office
hour
really
appreciate
everybody.