►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Kubernetes on Windows - A Journey - Jerry Lozano, RX-M LLC
Kubernetes is almost always used in a Linux environment. Tutorials and examples, regardless of hardware platform, always run some distribution of Linux. Yet since 1.14, Kubernetes worker nodes are actively supported on Windows. This session describes one developer’s journey of designing, developing, installing, and deploying Kubernetes on modern Windows Server. The need for microservice implementations on Windows is just as valid as it is on Linux. Windows Server is hosted on at least 3-times the number of servers in use in the world and market share is still increasing (Statista). Most of these servers run enterprise applications that must meet the requirements for scalability, availability, and maintainability that any modern application faces. This session describes the benefits of hosting Kubernetes nodes on Windows Server, similarities and differences from execution on Linux, and lessons learned when implementing a microservice application with the Windows infrastructure.
A
Welcome
to
the
session
kubernetes
on
windows
a
journey-
my
name
is
jerry
lozano.
I
am
a
software
developer
and
I
work
for
rxm.
We
are
an
enterprise
cloud
native
development
training
and
consulting
firm.
I
carry
the
title
of
senior
consultant,
but
I
am
a
software
developer
who
specializes
in
system
level
and
operating
system
development.
A
My
work
over
the
years
has
led
me
through
unix,
linux
and
windows.
I
developed
device
drivers
for
all
operating
systems
and
I
have
focused
on
application
framework
in
related
software
architecting
applications
that
are
microservice
oriented
cloud
hosted.
It
was
a
somewhat
natural
migration
from
my
interests
and
skill
set.
So
thank
you
for
attending
the
title
of
this
presentation
is
a
little
misleading,
but
we
seem
to
be
attracted
to
intriguing
titles.
So
here
we
are
kubernetes
on
windows.
A
A
A
Well,
the
control
plane
of
kubernetes
does
not,
and
it
may
never
run
outside
of
linux.
The
official
documents
of
kate's
state
that
there
are
no
plans
to
support
a
windows
only
cades
cluster,
but
for
some
time
now,
since
1.14
kate's
has
permitted
mixed
clusters
with
windows,
worker
nodes,
running
side
by
side
within
linux
worker
nodes.
A
A
A
Statista
shows
that
over
70
percent
of
the
global
server
market
is
windows-based,
but
look
we're
not
here
to
argue
about
statistics
or
the
different
ways
to
look
at
market
penetration.
The
point
here
is
clear:
there
is
a
ton
of
code
on
windows
that
faces
the
same
challenges
that
any
application
moving
forward
faces.
That
includes
scalability
availability.
A
A
A
A
So
here
we
are
like
most
things
in
our
industry.
Maybe
most
things
in
the
world
in
life.
The
actual
path
to
hosting
a
mixed
cluster
may
not
be
as
straightforward
as
we
might
hope
or
maybe
is
the
documentation
might
imply
at
some
high
level.
The
problems
we
face,
I
think,
will
fall
into
two
categories:
those
that
are
part
of
choosing
two
different
operating
systems
to
execute
in
the
same
environment.
A
I'm
thinking
about
the
use
of
aws
and
building
the
mixed
clusters.
There
aws
networking
options
present
problems
of
their
own
when
you
work
with
a
mixed
cluster
and
then
there
are
those
problems
where
just
putting
two
different
operating
systems
on
the
same
cluster,
the
same
network,
the
same
orchestration
scheme-
in
other
words
the
kate's
portion
of
the
problem,
are
going
to
come
to
bear.
A
A
A
A
A
Along
the
path
of
our
journey,
we
encountered
several
noteworthy
problems.
We
want
to
talk
about
each
one.
The
first
problem
is
setting
up
the
windows
server
depending
on
the
provider
or
the
environment.
You
are
using.
This
problem
will
vary
in
difficulty
and
cost,
but
here
is
what
you
must
know
right.
A
First
kate's
requires
that
kate's
worker
nodes
run
windows,
server
2019.
We
assume
that
this
is
one
of
those
or
later
requirements,
but
for
now
it
says
windows,
server,
2019-
and
there
are
several
things
to
to
note
here.
First
most
of
us
use
ssh
right
to
connect
a
new
node
for
first
time
setup
or
debugging
or
monitoring
or
whatever,
to
connect
to
our
linux
console.
A
But
windows
server
starts
with
a
graphical
environment,
so
using
aws
we
need
to
do
our
initial
connection
using
rdp
from
a
windows
box.
We
would
use
remote
desktop
to
easily
connect.
But
beware
here
other
concerns
right
in
setting
up
windows
server
concern
licensing.
We
don't
go
into
that
much
here
on
the
slide,
but
make
sure
your
licensing
is
valid
when
using
windows
server,
especially
in
production,
you
don't
need
a
trial
license
expiring
30
days
after
you
deploy.
That
would
be
disastrous.
A
A
A
Surprisingly
right,
many
of
the
steps
involved
here
felt
familiar.
They
were
the
same
or
or
similar
to
adding
any
worker
node
to
a
case
cluster,
and
so
you
will
see
that
we
use
the
identical
cube
atom
join
command
that
we
do
when
we
join
a
linux.
Node
to
the
cluster,
but
first
here
right,
there
are
currently
some
restrictions
on
how
the
cluster
network
has
to
be
configured
for
windows,
nodes
nodes
to
join.
For
example,
we
only
have
two
choices
for
the
network:
flannel
or
an
l2
bridge,
slash
host
gateway
mode.
A
A
The
l2
bridge
host
gateway
has
its
own
set
of
requirements,
but
remember
regardless.
These
are
current
restrictions
and
could
and
probably
will
change
over
time.
I
would
strongly
advise
reading
the
current
documentation
and
understanding
flannel
before
embarking
on
your
own
journey
to
set
up
a
mixed
cluster.
A
A
Powershell
is
windows
default
command
line
tool
by
the
way
scripts
for
powershell,
typically
end
with
the
dot
ps1
extension
and
look.
There
is
a
github
repo
for
the
latest
windows
tool
to
install
and
set
up
kates
on
windows.
It
comes
down
to
a
powershell
script,
prepare
node.ps1
once
it
gets
executed,
which
you
see
here.
A
Look
at
slash,
var,
slash
log,
okay,
it's
under
that
c
colon
drive
and
nobody
likes
the
backslashes.
They
should
be
forward
slashes
so
that
you
know
powershell
will
accept
either
backslashes
or
forward
slashes.
But
that's
another
story,
so
we
you
know,
we
don't
like
to
see
colon
part
there.
It's
still
pretty
close
to
a
familiar
path
and
then,
as
you
can
see,
on
the
right
side
here,
we
use
the
exact
cube
atom
join
command
with
the
token
that
was
generated
by
our
control
plane
to
get
our
windows
worker
node
to
join.
A
This
process
works
right,
and
how
do
we
know
that
it
worked
so
easy
enough
to
try
right
both
the
we'll
use,
cube,
cube,
cuddle,
get
nodes
and
we'll
see
that
in
this
case,
right
both
the
linux
there's
our
ubuntu
worker
node
and
the
windows
worker
node?
There's
our
windows,
server,
2019
data
center
edition
are
up
and
running
right
and
they
each
have
their
own
internal
ip
address.
I
mean
they're
ready
for
use.
Use
I
skipped
over
having
the
the
the
process
of
adding
the
linux
worker
node
to
the
cluster.
We
understand.
A
That's
the
familiar
part
of
this
journey.
I
didn't
go
into
it
right
right,
so
our
next
step
here
has
to
be
to
deploy
our
pod
and
that
means
running
the
credit
card
auth
service
on
the
windows
node,
and
that
means
building
a
containerized
microservice
for
windows.
We
have
to
build
a
windows
container
image
exactly.
How
are
we
going
to
install
that
service
inside
of
our
container?
A
And
so
at
this
point
we
can
consider
two
possibilities.
I
think
one
would
be
a
standard
windows,
installer
file,
it's
known
as
an
msi
file,
and
when
you
execute
an
msi
file,
it's
like
an
rpm
file
right.
It
installs
the
application
making
changes
to
the
system.
It
mutates
the
system
to
host
the
application,
so
windows
uses
an
msi
file
and
when
we
use
that
for
a
web
service
it
installs
a
virtual
directory
under
iis.
A
A
A
Either
of
these
techniques
would
work
when
we
build
our
container
image.
Okay,
all
right!
Now,
let's
take
a
look
at
our
windows.
Microservice
we've
talked
about
implementing
this
as
a
windows
service,
so
the
code,
the
implementation
that
we're
going
to
use
here
right,
is
just
an
example
of
the
real
windows
code
that
would
be
used
in
a
real
kate's
application.
A
A
Okay,
it
shows
a
simple
web,
get
we're
going
to
use
a
get,
not
a
post
to
invoke
the
authorize
method
and
the
authorized
method
will
receive
two
arguments:
a
pretty
long
credit
card
number,
64-bit,
unsigned
integer
and
an
amount
to
charge
right,
we'll
pass
it
in
as
a
net
decimal
data
type.
The
actual
data
types
don't
matter
too
much,
because
we
know
that
we
will
be
passing
data
as
strings
over
a
restful
interface.
A
A
A
But
now
we
have
to
containerize
the
service.
We
need
a
docker
image,
we're
going
to
use
a
docker
image,
build
command
on
windows
and
we're
going
to
feed
docker
image,
build
with
a
docker
file.
That
in
many
ways,
is
something
that
we
are
familiar
with.
We
start
with
a
base
image
right
that
image,
as
shown
on
the
slide,
is
from
microsoft,
slash
iis.
A
A
These
base
images
are
not
necessarily
configured
the
way
you
would
like,
for
example,
asp.net
framework
isn't
installed
on
microsoft,
slash
iis,
that
might
be
a
little
surprising
web
service
files
like
our
cc.
Auth
svc
file
won't
be
processed
not
by
default,
so
our
docker
file
image
has
to
enable
these
features,
and
we
have
to
install
any
missing
prerequisites
for
the
service.
A
We
can
see
how
we
chose
our
base
image
and
how
we
installed
the
missing
features
or
the
necessary
options.
In
this
example,
here
we
just
once
again
use
install
dash
windows
feature
to
install
asp.net
okay,
or
we
want
the
web
management
compatibility
feature
so
that
our
msi
file
could
install.
That
was
why
that
prerequisite
was
installed.
A
Okay,
then
all
we
have
to
do
right
would
be
to
install
the
application
itself.
Our
little
cc
auth
service.
That
can
be
done
with
an
msi
file.
As
I
discussed,
how
are
you
going
to
do
that
right?
I
built
my
msi
file
right
from
from
my
windows
machine,
but
now
I've
got
to
get
it
into
my
docker
image.
First
things:
first
right
copy
the
msi
file
to
an
accessible
path
within
our
build
environment
and
then
run
msi
exec.
A
A
That's
present
on
my
windows,
machine,
okay!
This
is
almost
too
easy
right
in
some
ways.
Of
course,
I
would
say:
what's
missing
from
this
slide
would
be
that
we
should
test
the
container.
We
should
do
a
docker
run
container
run
and
then
maybe
use
curl
or
something
like
that
to
ensure
that
our
restful
interface,
our
call
to
authorize,
actually
works
the
way
that
we
think
it
should
when
we're
within
the
container,
and
so
that
step
was
actually
done.
A
When
I
built
this
example
here,
but
that's
pretty
obvious
that
that's
what
you
would
do
right,
okay,
we're
almost
done,
but
we
need
to
make
sure
that
the
control
plane
launches
our
service
only
on
windows
worker
nodes.
Remember
even
in
our
simple
example.
Here
we
have
two
worker
nodes.
One
is
linux
which
has
no
chance
of
hosting
this
container,
and
the
other
is
the
windows
worker
node,
where
we
need
to
make
sure
that
this
happens
right.
A
A
A
A
This
should
be
a
very
familiar
pattern
at
this
point.
Okay,
so
good
for
us,
we
got
this
up
and
running
and
our
entire
application
can
work.
We
now
have
a
restful
interface,
where
the
implementation
is
running
on
of
the
microservice
is
running
on
a
windows
worker
node,
but
we
should
point
out
that
some
current
restrictions
exist
in
this
story.
A
You
know:
first,
okay,
host
networking
mode
is
not
available
for
windows
pods
and,
at
the
moment,
service
vips,
virtual
ip
addresses
assigned
to
a
service
service.
Not
the
implementation
of
that
service
cannot
be
used
by
windows
worker
nodes.
This
is
a
pretty
severe
restriction
when
dynamic
scaling
is
occurring
in
large
applications.
A
A
You
can't
currently
use
ipv6
right
within
the
cluster
of
that
includes
windows,
worker
nodes
and
secrets.
Right
aren't
yet
integrated
with
kate's
secrets
and
etsy,
and
there
are
more
limitations.
Actually
there
are
many
others,
I'm
going
to
give
you
a
link
here
to
the
current
state
of
affairs
right.
No
one's
saying
this
is
a
perfect.
You
know
implementation
in
a
completed
state
at
the
moment,
but-
and
I
think
this
is
important
right
working
with
the
mixed
cluster-
is
simply
not
that
different
when
what
with
what
we
are
familiar
with
right.
A
A
You
can't
dismiss
this
point
as
oh
just
port
it
all
forward
onto
linux.
You
know
those
windows
messages
could
all
be
linux
signals
right
again.
That
was
meant
to
be
funny,
but
it
brings
up
a
serious
point
right.
People
that
don't
have
to
do
the
job
always
seem
to
be
the
ones
claiming
that
quote.
All
you
have
to
do
is
whatever
right
again.
A
A
A
In
any
event,
I
hope
you
enjoyed
hearing
about
this
journey.
There
are
obviously
many
more
events
that
occurred
on
this
journey
and
will
occur
anytime.
You
build
a
mixed
cluster
solution,
but
hopefully
you
found
some
of
this
talk
useful,
I
hope
to
meet
others
here
who
have
experienced
a
similar
journey
like
to
hear
from
you,
but
again,
thank
you
for.