►
From YouTube: Simplifying Windows Runtime and Deployment in Kubernetes - Michael Michael, Mark Rossetti
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. 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.
Simplifying Windows Runtime and Deployment in Kubernetes - MICHAEL MICHAEL, VMware, Mark Rossetti & Muzz Imam, Microsoft, & Deep Debroy, Docker
The leaders of SIG-Windows will provide an update on the efforts to bring Windows to Kubernetes. This session will concentrate on presenting new features and capabilities as well as focus on advanced capabilities like ContainerD integration, CSI, Networking, and Cluster API/kubeadm for Windows. Some familiarity with Windows on Kubernetes is required for the in-depth discussion on advanced features that are in the pipeline for Windows. At the end, we will open the floor for Q&A with users and members of the SIG-Windows community, discussing implementation and trade-offs.
https://sched.co/ekFu
A
C
E
A
Thank
you
all
so
today,
we're
going
to
talk
about
all
the
investments
that
seek
windows
and
cloud
native
windows
community
have
been
doing
in
the
last
few
months.
We're
going
to
basically
talk
to
you
about
our
future
roadmap
and
what
that
looks
like
and
talk
about
some
of
the
key
areas
that
you
might
be
interested
in.
A
A
B
Michael,
so
in
windows
operating
system
update,
so
we
have
a
lot
of
exciting
stuff,
starting
with
nano
server.
1809
support
has
been
extended
officially
to
2024
same
as
the
windows
2019
ltsc
support
cycle.
This
was
based
on
the
request
we
got
from
kubernetes
community.
The
other
one
important
that
mark
is
going
to
talk
about
in
container
d
as
well
is
the
single
file.
Mapping
is
now
fully
supported
the
from
an
operating
system
perspective.
B
B
As
far
as
the
plans
for
v120
goes,
we
have
a
couple
of
critical
bugs
that
were
filed
by
the
kubernetes
community
that
are
being
resolved,
for
example,
virtualized
time
zone
for
containers
and
in
future,
based
on
this
relationship
between
the
kubernetes
and
the
windows,
os
team,
we're
looking
at
the
changes
for
service
mesh.
That
michael
is
going
to
talk
about
session
affinity
for
q,
proxy
and
especially
msmq
msdtc
supported
scenarios
in
future.
With
that,
I
will
hand
it
to
mark
who
will
talk
about
container
d.
D
Hi
yep,
so
anybody
who's
been
following
sig
windows
has
noticed
that
in
the
compute
space
recently
we're
really
just
focusing
on
our
efforts
on
container
d
container
d,
as
the
container
runtime
provides
a
lot
of
benefits
over
docker,
at
least
with
the
current
windows
implementation
today,
so
I'll
go
over
a
couple
of
those
real
quickly.
The
first
one
is
is
that
it
utilizes
the
host
compute
service,
v2
schema
for
those
unfamiliar
with
windows.
D
The
host
compute
service
is
a
management
service
that
just
helps
start
and
stop
and
run
containers.
The
host
compute
service
v1
introduced
with
windows,
server
2016
and
it
was
revamped.
It's
windows,
server,
2019..
Some
key
benefits
that
that
brings
to
the
kubernetes
community
is.
It
allows
us
to
address
some
kind
of
parity
issues
with
features
in
terms
of
with
respect
to
linux
containers.
Some
of
those
are
highlighted
here
and
that's
with
this
new
schema.
D
We
can
support
properly
support
single
file
mappings,
so
you
can
get
an
updated
cd
host
files
into
your
container
and
also
containers
can
just
write
to
dev
slash
termination
log
to
get
their
error
messages.
In
addition
to
the
windows.
Specific
functionality,
container
d
is
based
fully
on
the
cry
of
the
container
runtime
interface.
D
D
D
Another
kind
of
important
one
is
we're
working
to
enable
gpu
support
through
device
assignments
and
some
future
things
we're
investing
in,
but
not
necessarily
in
120.
In
this
space
are
we
hope
to
enable
privileged
container
support
for
windows
in
the
near
future
and
are
also
working
on
enabling
hyper-v,
isolated
containers.
C
Thanks
mark,
so
we
have
been
mainly
concentrating
on
the
csi
proxy
in
order
to
enable
csi
support
for
node
plugins
in
windows.
We
have
introduced
the
new
system,
api
group
in
csi
proxy.
This
involves
adding
support
for
a
bunch
of
things
around
querying
the
status
of
the
service.
That's
running
within
windows,
as
well
as
enabling
support
for
iscsi.
C
C
We
are
starting
to
support
csi
proxy
as
a
native
windows
service,
so
that
you
can
just
configure
it
as
a
service
when
you
set
up
the
windows
host
and
finally,
on
the
cicd
side
of
things,
we
have
enabled
github
action
based
unit
and
integration
tests
that
are
fairly
stable.
At
this
point,
plans
for
upcoming
plans
for
120
is
to
continue
to
add
apis
to
csi
proxy,
so
that
we
can
support
the
vsphere
plugin
as
well
as
as
well
as
the
generic
iscsi
plugin
on
windows.
C
We
want
to
improve
on
those
latencies
and
figure
out,
what's
causing
them,
we
want
to
introduce
automated
automated
api
documentation
and
generate
them
directly
from
the
api
protofiles,
so
that
we
can
continue
to
publish
documentation,
that's
fairly
up-to-date
on
the
csi
dev
documentation
sites.
And
finally,
we
want
to
investigate
a
smooth
and
seamless
migration
path
from
the
current
csi
proxy
to
the
future,
which
is
privileged
container
support
in
windows,
so
beyond
120
the
future
would
be
to
take
in
the
future.
C
We
want
to
take
csi
proxy
to
a
stable
state,
add
more
storage
plugins
that
can
be
supported
through
csi
proxy,
for
example
the
aws
eps
plugin
and
finally,
look
to
was
deprecating
the
entries
entry
storage
plugins
that
target
windows
today
in
the
next
slide.
We
have
architecture
diagram
of
how
csi
proxy
enables
a
csi
note,
plugin
in
windows
to
communicate
with
the
various
components
such
as
cubelet
and
the
csi
note
driver
register,
as
well
as
to
the
host
operating
system,
to
drive
privileged
operations.
A
Thanks,
thank
you.
Thank
you
deep.
So,
let's
talk
a
little
bit
about
networking.
You
know:
we've
been
seeing
a
lot
of
advancements
in
storage
as
well
as
compute,
and
we're
actually
putting
a
tremendous
amount
of
effort
around
networking
as
well
in
the
latest
release
we've
enabled
dsr
mode
for
low
balancing,
as
well
as
endpoint
slices.
Both
of
these
features
make
it
easier
for
you
to
run
more
applications
on
the
same
node
in
kubernetes
and
we
make
it
more
efficient
for
you
to
run
have
more
endpoints
on
your
kubernetes
containers.
A
In
addition
to
that,
there's
two
major
changes
that
are
happening
on
the
cni
world.
The
container
networking
plugins
for
kubernetes
calico
has
open
source
their
network
plug-in
for
kubernetes
for
windows,
which
is
a
major
major
thing.
Now
you
get
the
great
advantages
of
caligo
and
you
can
try
it
out
without
requiring
a
subscription,
in
addition
to
that,
the
andrea
cni
now
supports
windows,
including
support
for
network
policies.
A
So
now,
if
you're
looking
to
get
started
with
windows,
containers
on
kubernetes
and
you're,
looking
at
you
know
your
network
plugins
and
what
can
support
your
needs
as
an
infrastructure
operator,
you
have
two
great
cni's
that
are
made
available
for
you
in
addition
to
that,
the
envoy
proxy,
which
is
kind
of
the
base
for
a
lot
of
other
features
in
the
cloud
native
ecosystem,
for
example,
istio
and
contour,
and
other
ingress
controllers,
had
their
alpha
release
of
supporting
windows.
This
is
huge.
A
Now
we
make
it
possible
for
you
to
start
trying
out
what
it
will
mean
to
run
the
envoy
proxy
in
some
of
these
capabilities
like
ingress
and
and
other
tools
on
top
of
windows
for
1.20.
Our
plan
is
to
promote
envoy
proxy
to
beta
so
you're,
going
to
see
an
advancement
of
the
capabilities
there,
making
it
making
more
more
solid
as
a
as
a
supported
offering
we're
going
to
have
ipv4
and
ipv6
dual
star
networking.
A
E
So
in
a
couple
releases
ago
we
added
cube
adm
support
and
we
are
now
in
beta
with
that
and
as
we
look
forward
we're
going
to
be
adding
support
to
cluster
api
cluster
api
is
going
to
be
using
the
cube
adm
support
that
we
did,
that
we
added
it'll
also
be
using
some
tooling
that's
out
in
the
ecosystem,
around
cloud
base
that
enables
cube
adm
to
boot
these
nodes
very
quickly.
This
will
be
support
for
workload
clusters.
A
Thank
you
james,
and
we
look
forward
to
that
demo
maz.
You
know,
we've
talked
about
all
of
these
features:
compute
network
storage,
making
it
easy
for
people
to
run
and
our
users
to
run
windows,
containers
and
kubernetes
and
production.
But
the
big
issue
is:
what
do
you
do
with
all
these
legacy?
Apps
that
are
running
windows
out
there
in
the
wild.
B
Yeah
thanks
mike
and
that's
that's
the
one
of
the
feedbacks
and
questions
we
got
from
the
last
coupon
as
well,
so
the
so.
I
think
that
the
first
thing
to
start
with
the
with
the
modernizing
legacy
application
is,
of
course,
to
lift
and
shift
your
application
from
mono
from
monoliths
to
to
micro
services,
and
the
first
step
is
is
pretty
simple
one.
B
All
you
need
to
do
is
basically
try
to
containerize
the
application
locally
on
your
own
computer,
using
docker
containers
and
see
if
it
works
and
and
the
general
rule
of
thumb
here
is
the
web-based
applications,
the
simple.net
application
that
been
running
the
legacy
application
which
work
great
in
your
organization.
You
want
to
keep
it
and
modernize
the
infrastructure
start
with
those.
B
You
know
the
low
hanging
fruit
and,
generally
we've
seen
a
majority
of
the
application
lie
into
that
the
complex
application
leave
them
for
later
now,
in
terms
of
containerization
of
applications
locally.
There
are
many
tools
out
there
as
well
to
help
you
write
the
docker
file,
getting
the
first
step
going
and
testing
it
on
your
local
machine.
One
of
those
is
the
windows
admin
center,
which
a
lot
of
windows
administrators
use.
We
have
a
new
extension
called
container
extension
and
the
link
is
right.
There.
A
Absolutely
thank
you.
Thank
you
mars
and
you
know,
like
must
mentioned
it's.
The
best
thing
to
do.
Is
you
start
slow?
You
start
with
some
applications
that
you
lift
and
shift
and,
as
you
get
more
knowledge
about
how
to
modernize
some
of
those
applications,
as
you
understand
some
of
the
gotchas,
then
you
can
slowly
apply
the
same
blueprint
to
more
and
more
applications,
because
there's
a
lot
of
classes
of
applications
out
there
at
organizations
that
look
very
similar.
A
So
what
the
knowledge
that
you're
going
to
get
from
modernizing
some
of
them
is
going
to
apply
very
equally
to
other
ones,
but
as
you
go
through
that
process,
you're
going
to
identify
some
things
that
don't
really
work
as
well
and
some
things
that
you
have
to
know
note
into
your
as
you're
going
through
that
process.
So
the
first
one
is
image:
selection,
use,
derived
images
to
share
application,
building
blocks
and
dependencies.
A
Why
is
that
important?
You
don't
need
to
figure
out
how
to
put
iis
into
a
base
windows,
server
image
start
with
the
iis
derived
image
same
thing
for
python
and
other
programming
languages
like
leverage
the
power
of
microsoft
that
produces
these
base
images
for
you
with
all
these
applications
in
it.
So
you
don't
have
to
do
that.
Work,
they're,
going
to
make
sure
they're
patched
they're
going
to
release
them
frequently,
and
then
you
can
just
build
on
top
of
it
in
some
ways:
you're
becoming
operating
system
independent.
A
By
doing
this
be
careful
windows,
registry
storage,
a
lot
of
legacy,
applications
use
windows
registry.
As
a
storage,
you
have
to
figure
out
a
way
to
redirect
that
output
into
persistent
volumes
or
other
kubernetes
friendly
storage
providers,
so
that
you
can
maintain
that
storage
and
that
ability
to
access
that
data
as
your
application
could
be
shut
down
or
move
from
node
to
node
in
kubernetes.
A
Same
requirement
applies
to
local
storage,
so
not
just
registry,
but
local
storage
as
well
or
usage
of
local
databases,
kernel
drivers
or
application
drivers
may
not
exist
in
windows
containers.
So
if
your
application
is
making
use
of
those,
you
have
to
identify
them
figure
out
if
they
are
necessary
and
either
split
the
application
into
different
components
where
some
components
could
still
run
in
virtual
machines
or
completely
re-architect
those
components.
A
Active
directory
support
at
the
os
level
does
not
exist
in
windows
containers.
You
have
to
think
about
that
and
use
gmsa.
That
mark
mentioned
earlier,
as
the
ability
to
reach
out
from
the
container
into
active
directory
assets.
Be
careful,
be
careful
of
dotnet
version
compatibility.
You
know.
Wcf,
for
example,
may
not
exist
in
net
core
database
requirements.
Certificate
management,
other
application
dependencies
like,
for
example,
windows,
api
dependencies
like
msmq
and
ms
dtc.
You
know
if
you
have
old
style,
applications
using
com
and
they
require
the
distributed
transaction
coordinator.
That's
something
to
think
about.
A
A
E
James
excellent,
okay,
so
I've
got
a
video
here
of
using
a
cluster
api
and
image
builder
to
start
building
images.
So
one
of
the
challenges
is
just
building
that
base
image
with
all
the
best
practices
baked
in
and
so
there's
a
repository
out.
There
called
image
builder
and
you
can
run
a
simple
command
and
it
will
kick
off
building
an
azure
vm
in
as
well
as
several
other
types
of
vms
and
then
we'll
begin
to
install
all
the
components
that
are
required
for
cluster
api.
E
E
E
So
at
the
at
the
end,
here
you
get
a
disk
url
that
you
can
then
reuse
and
then
what
I'm
doing
here
is
transitioning
over
to
the
cluster
api.
So
cluster
api
has
a
concept
of
a
management
cluster,
and
so
what
I'm
showing
you
here
is
the
management
cluster
and
then,
once
we
have
the
management
cluster
run,
we
then
deploy
the
workload
cluster.
So
I
can
there's
many
different
templates
out
there
that
have
different
types
of
crds,
we're
going
to
deploy
those
out
and
the
it's
going
to
begin
to
create
the
workload
cluster.
E
Here
is
the
management
cluster
logs.
These
logs
are
just
showing
you
that
the
the
workload
cluster
is
actually
being
reconciled
as
it
gets
deployed
and
in
a
moment
here
we're
going
to
see
that
the
first
control
plane
node
came
up
now.
This
is
a
linux
control,
plane,
node
and,
on
the
right
hand,
side.
Now
that
that
control
plane
node
has
been
deployed.
I
can
connect
to
it
and,
on
the
left
hand,
side
I'm
going
to
query
the
crds
for
the
management,
cluster
and
watch
these
components
come
online
as
cluster
api
begins
to
provision.
E
On
the
right
hand,
side
here,
I'm
now
talking
to
my
cluster,
the
workload
cluster
that's
been
deployed.
You
can
see
that
the
nodes
are
have
come
online,
so
we've
got
the
windows
nodes
deployed
and
we've
got
a
fully
functioning
cluster
here.
So
we've
got
all
of
the
management
cluster
components
that
deployed,
and
now
we
can
deploy
our
our
extra
components
on
there.
So
we'll
deploy
out
the
let's
see
here
so
we're
going
to
deploy
out
our
flannel,
we'll
deploy
it
to
the
linux
once
those
are
all
up
and
ready
and
and
running.
E
E
E
That's
going
to
be
our
helper
test
component,
so
we
can
see
that
they've
come
up
online
here
and
and
we've
got
ip
addresses,
and
here
we
have
the
is
service,
we're
going
to
go
out
and
actually
make
sure
that
that
got
provisioned
correctly
here
so
copy
that
ip
address
and
open
up
a
browser.
And
here
we've
got
iis
running
on
that
workload,
cluster
and
then
the
last
step
of
this
is
executing
into
that
test
component.
E
We're
going
to
query
the
iis
cluster
and
we'll
also
query
out
make
sure
that
we
have
internet
connection
out
to
an
external
site,
and
finally,
here
we'll
see
that
we've
got
all
of
the
pods
and
at
the
bottom
here,
you'll
see
that
we
have
windows,
server,
2019
with
docker
ee
running
on
it,
and
we
were
able
to
do
query
and
deploy
all
those
those
pods
to
it.
And
so
this
is
an
example
of
using
cluster
api
azure
to
deploy
windows,
notes
I'll
hand
it
back
to
you.
A
What
a
dynamite
demo
thank
you
james
and
the
entire
team,
both
from
sig
windows,
as
well
as
from
the
c-cluster
life
cycle.
That's
been
working
on
this.
You
know
it
is
super
super
exciting.
For
me,
it's
gonna
make
it
easier
for
it
admins
and
operators
to
deploy
windows
clusters
by
basically
defining
just
a
yaml
for
their
clusters,
giving
us
a
specification,
and
then
we
do
all
the
work
and
all
the
plumbing
together
cluster
up
and
running,
based
on
the
definition
and
the
desired
config.
A
A
So
as
you've
seen,
you
know,
we
have
a
tremendous
amount
of
innovation
happening
in
sick
windows
and
one
of
the
things
that
mark-
and
I
have
talked
about
in
community
in
the
past
and
one
of
the
blogs
we've
created,
come
and
join
sick
windows.
It's
one
of
the
few
unique
opportunities
you
have
in
kubernetes
to
work
across
the
board
of
the
entire
kubernetes
subsystem.
You
can
work
in
storage,
compute,
networking,
api
cluster
api
who
have
everything.
So
if
you
want
to
really
touch
everything
in
kubernetes
windows
is
one
of
those
areas.
A
We
have
weekly
meetings,
they're
all
recorded,
so
you
can
go
and
record
and
view
all
the
recordings
from
past
meetings.
If
you
want
to
come
in
and
help
us
write,
documentation
and
user
stories
or
fix
some
bugs,
starting
with
the
good
first
issue
or
even
review
our
open
prs,
we're
a
welcoming
community,
we
want
to
need
to
come
in
and
contribute
we'll
mentor
you
or
help
you
get
started.