►
From YouTube: Windows SIG – Craig Peters & Pengfei Ni, Microsoft
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Windows SIG – Craig Peters & Pengfei Ni, Microsoft
SIG-Windows participants will provide an update on the efforts to bring Windows to Kubernetes. This will concentrate on presenting new features that are being delivered and the General Availability of Windows Containers on Kubernetes. We will also have a detailed discussion on our future roadmap, key functionality that we want to enable, and open the floor for Q&A with customers and members of the SIG-Windows community. This is both an introduction to Windows on Kubernetes and a deep dive into the efforts of the team. Some familiarity with Windows on Kubernetes is required for the deep dive part since we will have an in-depth discussion on key features that are in the pipeline for Windows, explain their implementation and have a discussion on tradeoffs with the community.
https://sched.co/O4G4
A
B
C
Hello,
everyone
I'm
from
face
company
from
Microsoft
and
from
Microsoft
as
engineering
team
I'm
any
work
for
improving
the
committee's
experience
on
area,
so
I
work,
some
internal
work
to
improve
the
air
container
service
and
also
making
some
contribution
to
the
committee's,
such
as
the
cloud
provider,
the
canoe
runtime,
the
windows
and
so
on.
Nathan.
A
Thank
you,
I'm
Craig,
Peters
p.m.
in
the
azure
team
and
the
observe
container
compute
and
I'm
responsible
for
container
infrastructure
upstream
contributions
that
we
we
provide
so
that
kubernetes
and
other
container
workloads
work
great
on
a
service,
and
so
what
we're
going
to
start
by
talking
about
is
sort
of
how
we
got
where
we
are
today.
So
hopefully
you
got
the
contact
information
so
feel
free
to
reach
out
to
us.
A
C
A
D
A
B
C
A
Make
it
possible
to
do
that
in
sort
of
an
alpha
release
towards
the
end
of
2016
in
kubernetes
1:15,
we
worked
to
solve
a
bunch
of
problems
that
existed
in
the
networking
in
particular
and
support
the
CNI,
so
I
guess
the
initial
release.
The
key.
The
key
thing
is
that
there
was
a
cubelet
and
queue
proxy
ran
on
Windows.
That's
the
that's.
A
The
anchor
thing
to
make
the
workers
in
your
kubernetes
cluster
be
kubernetes,
be
kubernetes
running
on
Windows,
where
the
master
components
are
still
running
on
Linux
notes
in
1.9
many
improvements
were
made
essentially
fundamentally
added
CNI
support
to
the
cubelet
and
cube
proc
tea,
and
so
now
you
can
use
pluggable
network
components
for
Windows.
The
initial
support
was
cute,
Annette
and,
and
then
people
started
using
it
more
and
more.
In
March
of
2019
we
have
were
able
to
reach
the
stable
label
in
kubernetes,
so
we
internally
think
of
this
as
basically
GA
right.
A
This
is
something
that
we
recommend
that
anybody
now
use
it's
supported
with
community
support
and
as
we'll
get
into
later,
many
cloud
providers
are
also
providing
commercial
support
for
Windows.
In
there
today's
offerings
114,
the
the
major
things
were
that
we
made
it
easy
to
use
Windows
Server
2000
19,
that's
the
the
server
host
that
is
now
supported
in
stable
kubernetes.
A
That
means
that
we're
going
to
support
going
forward,
2019,
Windows,
Server,
2000,
19
and
higher,
and
then
in
115.
We
made
a
lot
of
sort
of
quality
improvements
and
usability
improvements.
So
let's
dig
a
little
bit
more
into
what
we
actually
released
in
114.
So
if
you're
not
aware,
114
was
dubbed
quatre
Nettie's.
That
was
the
release.
A
E
A
For
114
Aaron
of
cig
beard,
if
you're
familiar
with
him,
dubbed
it
so
and
it's
very
appropriate
since
he
loves
cats
and
releasing
kubernetes
as
a
community
project
with
all
these
inputs
is
very
much
like
herding
cats.
One
of
the
biggest
cats
to
hurt
for
the
release
team
was
actually
the
support
for
Windows
containers
in
world
14.
C
A
Turned
a
huge
thank
you
to
members
of
the
community.
We
had
a
lot
of
participation
from
people
at
VMware
at
docker
at
Google,
some
participation
from
AWS
and
a
bunch
of
other
companies
all
contributed
to
making
this
a
very
stable
release.
The
key
pieces
of
that
were
that
we
really
improved
the
end-to-end
testing
scenarios
like
that
was
actually
the
number
one
thing
that
had
to
happen
in
order
to
call
it
stable.
A
So
we
have
very
robust
end-to-end
tests,
which
we'll
look
at
it
quickly
and
we
did
a
lot
of
end
user
documentation
so
that
it
wasn't
the
mystery
how
you
go
about
doing
this
upstream.
We
have
high
quality
documentation
that,
if
you
use
I,
hope
you'll
have
a
great
experience
with
and
we'd
love
to.
You
know
hear
about
your
experience
with
that
and
get
your
feedback
over
in
115.
A
We
have
done
some
bug
fixes
and
there
was
an
alpha
release
of
global
managed
service
accounts,
support
in
kubernetes
that
was
primarily
contributed
by
by
docker
and
is
supported
through
some
integrations
in
dr.xu
that
has
continued
to
evolve
and
gotten
more
mature.
It's
moving
towards
a
beta
release,
beta
label
in
incoming
releases,
so
this
allows
you
to
have
pods
of
authentication
to
an
active
directory
so
that
your
host
doesn't
have
to
be
de
me.
You
know
join
to
your
domain
in
order
to
have
authenticated
services
running
in
your.
E
E
C
For
Windows
servers,
it's
for
three
kinds
of
network
topologies
and
overlaid
underlay
under
the
transparent
network
plug-in
so
overlay
Network.
Basically,
it
is
based
on
and
breaks
line,
and
you
have
to
choice
to
choose
set
up
your
overlay
Network.
The
wine
is
a
wind
overlay
network.
Plugging
in
this
is
a
part
of
the
official
stamp
like
a.m.
so
you
could
find
the
source
code
there
and
as
a
relation.
E
E
C
E
E
C
E
C
It
was
the
hosted
gateway
more
supportive,
so
then,
the
same
with
overlay
set
up.
If
your
link
not
have
already
you
use
the
play,
no,
then
you
can
chose
your
plan.
Oh
ho,
ho
gateway
at
the
windows
cm
plug-in
and
the
last
one
is
the
transparent.
So
this
is
based
on
some
the
the
hyper-v
base,
which
extension
so
then
your
container
could
be
connected
at
your
critical
of
networker
and
located.
C
C
C
Policy
we
have
a
gated,
the
boss,
callicles
and
the
open
inches
for
the
next
policy,
so
for
calico
you
knows,
and
calico
actually
provides
to
two
kinds
of
features
why
the
the
CM
plugin
and
the
other
is
the
next
policy,
but
for
Windows
calico
only
could
be
wrong
as
policy
only
today,
so
you
can
use
calico
to
manatee
or
next
policy
and
you
used
as
a
net-net
plugin
to
configure
your
network
and
the
open
is
actually
a
turnkey
solution.
So
it's
all
post
the
same
plug-in
and
the
the
next
policy.
Okay
yeah.
C
E
C
Couple
times
before,
you
join
your
application,
so
the
first
thing
is
and
how
could
you
decide?
Your
container
would
be
wrong
if
they
to
running
on
Windows
notice
of
only
on
Linux
notice.
If
you
need
a
Windows
server
node,
then
you
should
probably
know
some
noticed
lecture.
You
know
I'm
parked
back,
but,
however
your
classroom
may
be.
They
are
already
some
deployment
and
Iranian
Linux
notice
and
those
notice,
maybe
those
application.
Maybe
your
dealings
status,
no
selector
there.
So
sometimes
maybe
your
Linux
father
would
be
deployed
into
your
Windows
node.
C
Then
those
container
on
feeds
on
there
right.
So
we
have
two
options
here.
You
can
make
this
work,
so
the
preferred
one
is
added.
The
time
to
your
windows
knows
so
for
your
Windows
application,
you're,
tolerant
this
kind
then-
and
also
you
may
add
the
note
selector
in
your
Windows
applications,
so
that
they
could
only
deployed
to
the
windows,
node
and
also
for
for
existing
Linux
application.
You
don't
make
any
changes
in
in
such
a
way
another
option.
Of
course
you
can
make
changes
your
existing
Linux
deployment.
C
E
C
Why
this
option
was
preferred?
The
next
one
consider
is
rental,
as
you
know,
than
Windows
container
are
running
actually
very
different
from
the
Linux
container,
because
each
Windows
container
would
require
some
pressure
in
the
surveys
to
Jean
layer.
So
they
would
require
some
results,
such
as
CPU
to
memory
and
also
the
the
disk
space.
So.
E
C
C
The
last
one
is
actually
the
most
important
one
when
they,
the
Cunha
and
the
user
version
compatibility
issues
for
Windows
container.
So
the
the
general
idea,
then
Windows
kernel
version
should
be
matched
with
your
Windows
containers.
Bushing,
then
hey.
If
your
application
building
on
Windows
Server
29,
then
your
application
could
only
be
wrong
in
Windows
79
but
whatever.
C
If
you
have
already
some
applications
and
built
from
window
26,
maybe
then,
if
you
can
also
enable
the
halfway
isolation
so
for
Windows
containers,
they're,
basically,
two
kinds
of
isolation,
the
process,
isolation
than
here
actually
same
with
the
Linux
namespaces
isolation.
So
another
one
is
the
hyper-v
I
solution.
If
you
enable
the
hyper-v
isolation,
then
you
could
run
the
older
applications
on
the
newer
windows
7
or
so
so
you
can
run
your
Windows
Server
26
application
on
your
windows.
The
work
contain
nine
nodes.
Okay,
it's.
E
C
E
E
C
Know
they'll
have
different
versions
in
the
future,
because
the
window
J
will
need
support
of
Windows
Server
29
right
in
the
future.
You
may
have
more
Windows
Server
version,
so
you
you
may
show
the
different
control
runtime
handle
for
different
nodes.
So
then
is
another
option
in
the
future.
You
can
yoder
to
select
the
note.
Okay.
A
Things
that
we've
spent
the
last
six
months
really
investing
in
order
to
build
sort
of
trust
around
Windows
containers,
long
term
investment
that
we
picking
in
windows,
containers
for
Nettie's
is
to
build
a
very
robust
of
tests.
So
there
are
many
many
hundreds
of
tests
that
are
run
on
a
daily
basis
and
all
tests
grade,
along
with
the
rest
of
the
testing
in
the
community.
A
We've
worked
very
closely
with
Google
and
VMware
to
have
this
testing
run
on
their
platforms
as
well,
we're
expecting
AWS
to
join
and
we
invite
any
other
cloud
providers
to
please
join
testing
effort
and
contribute
resources
and
run
their
tests
on
your
platforms
as
well.
One
of
the
challenges
that
we
face
is
that
in
the
kubernetes
community
as
a
whole,
naturally
this
the
system
grew
up
from
assuming
linux
as
the
underlying
host.
A
E
A
B
A
Way
in
which
we're
doing
it
for
Windows
is
to
exclude
a
set
of
tests
that,
together
with
cig
testing,
we
have
just
described
as
Linux
only
tests,
that's
really
a
stopgap,
that's
not
really
being
solution
that
we
need.
What
we
need
is
to
come
to
a
shared
understanding
of
what
conformance
means
across
different
platforms,
different
hosts,
as
kubernetes
runtime,
spread
across
data
center
to
edge.
There
are
gonna,
be
a
very
wide
variety
of
environments
over
time,
and
so
that's
that's
an
active
area
of
development.
A
So
the
next
kind
of
point
that
I
want
to
make
is
that
you
know
in
the
community
there's
been
kind
of
a
worried
like
if
windows,
containers
and
communities
of
toys-
it's
something
that's
just
a
mental
thing
and
it's
gonna
go
away.
I
want
to
emphasize
that
this
is
not
the
case.
There's
a
huge
demand
in
the
customer
ecosystem
for
running
Windows
workloads
in
by
being
orchestrated
by
kubernetes
and
a
testament
to
that
is.
D
A
Many
different
service
providers
are
already
providing
solutions
based
on
this
very
new,
stable
support
of
Windows
containers
in
kubernetes,
so
we
can
see
everybody
from
Amazon
docker,
google,
huawei,
Microsoft,
obviously
Rancher
Red,
Hat,
VMware
and
pivotal
and
I'm
sure
this
list
is
incomplete.
This
is
the
ones
that
I
know
about
from
my
interactions
in
the
community
and
we
collaborate
with
all
of
these
people
to
make
it
possible
when
the
I
upload
the
slides,
you'll,
be
able
to
have
the
links
to
all
of
these
things.
C
Windows
can
enter
the
area,
we
also
have
them
open
side
projects,
the
holidays
that
have
the
environmental
and
a
try
it
on
yeah.
Then.
Yes,
for
example,
you
can
use
a
gas
engine
to
providing
a
clatter
with
both
windows
and
Latinos,
and
you
can
read
through
the
documentation
and
try
how
it
is
working.
Absolutely
a
great.
E
E
A
A
E
A
Operator,
even
don't
care
about
the
runtime,
it
should
just
be
transparent
in
the
creative
community.
You
know
they
cry.
Oh
there's,
dr.
shim
and
dr.
run
the
huge
ecosystem
of
runtimes
and
we're
seeing
that
there's
a
lot
of
consolidation
around
fry
container
D
as
a
way
to
label
the
open
plumbing
of
underlying
operating
system
capabilities
into
the
runtime
for
kubernetes
and
we're
putting
our
weight
behind
behind
that
as
well
the
the
things
it
will
help
us
do.
A
A
The
way
the
Windows
operating
system
works
from
Linux
that
mean
that
your
experience
fundamentally
is
different.
Today
there
are
some
limitations
and
the
way
the
docker
runtime
works
that
we
can't
fix.
Fundamentally,
the
abstractions
aren't
quite
right.
It's
a
cry.
Container
d
allows
us
to
do
that.
What's
happening
is
that
the
dr.
shim
layer
will
be
deprecated,
and
that
is
coming.
So,
if
you're,
depending.
A
A
The
GMs
a
support,
so
we've
worked
very
closely
with
docker
to
understand
the
way
in
which
they're
implementing
GMs
a
and
customers
dependency
on
GMS
a
and
we're
working
to
make
sure
that
that
that
support
is
built
into
the
container
D
runtime
as
well,
so
that
there's
a
seamless
transition
for
those
capabilities
as
we
go
forward.
There
may
be
other
examples
that
I'm
not
aware
of
yet
and
I.
Ask
you
to
please
bring
those
forward.
A
Another
thing
that
this
will
do
is
it'll
reduce
the
footprint
right,
so
we're
gonna
get
one
of
the
things
weaknesses
frankly
of
Windows
containers
is
the
size
of
the
images
and
the
size
of
the
sheer
size
of
the
node
overhead
that
you
need
to
run
and
Craig
container
D
is
gonna.
Help
us
shrink
that
that's
just
another
step
for
optimizing
everything
a
little
way
it.
A
C
Current
attacker
is
vented.
If
you
hadn't,
invited
the
hyper-v
isolation,
then
your
father
can't
be
wrong
with
more
than
one
container
with
the
one
pod
by
the
way,
a
Kraken.
Indeed,
we
can
adilyn
order
because
the
Committee
is
actually
based
on
the
the
very
new
features
from
windows.
Server
win
container
this.
A
C
A
The
kind
of
plumbing
that
yeah
container
crack
container
D
opens
up
for
us,
so
we'll
have
much
better
Sabourin
support,
so
we're
cabling,
new
windows
features
to
be
exposed
through
container
D
with
the
hyper-v
isolation,
we're
enabling
new
abilities
in
Windows
to
control,
CPU
and
memory
that
are
not
possible
today
or
dr
runtime.
So
the
this
is
like
the
biggest
thing
that
we
are
working
on
right
now.
We,
you
know,
we
really
want
feedback.
There's,
there's
an
open
proposal,
I'm
happy
to
share
with
you.
Actually
the
Lincoln's
hear
about
the.
C
C
But
if
you
check
the
the
tattoo
results
we
published
in
the
Ted
curator
yummy
fondant,
then
some
some
test
cases
you're,
not
sleep
enough-
do
many
some
test
failures
from
time
to
time,
so
we
would
like
the
contribution
from
all
users.
So
from
from
community
side,
we
have
also
set
house
steps.
You
could
contribute.
For
example,
you
can
use
and
try
the
features
and
report.
C
Channel
on
the
coca
ropes,
you
can
also
draw
in
the
median
of
the
ticket
windows
and
you
can
swing
your
feedback
on
all
of
these
places
and
also,
if
you
are
a
developer
and
you
would
like
to
contribute
some
changes,
and
maybe
you
have
some
ideas
to
propose.
So
maybe
it's
also
benefits
all
of
us
in
the
fourth
kuma
disk.
So
in
such
case,
you
can
also
make
some
contributions.
For
example,
you
can
send
out
some
changes
to
our
documentation.
C
Some
add
some
meetings,
that's
the
union,
our
step-by-step
guides
and
also
you
may
take
some
packages,
so
we
would
like
all
kinds
of
this
contribution
and
the
the
last
one
if
you
have
contributed
a
lot
of
features
in
this
area,
and
you
would
like
to
have
more
cheap
catalyst
involved.
You
can
also
enjoy
as
such
as
the
windows
the
sigil
windows
check.
Later,
maybe
you
can
also
mentor
someone
else
you
can
have
to
reveal
and
also
approve
some
changes
from
others
so
also.
A
Wrong
time
for
participates
from
this
region,
and
so
one
of
the
things
that
I'm
working
with
the
cig
leadership
to
do
is
to
shift
the
meeting
times
in
a
way
where
alternate
sessions
will
happen
in
Europe,
friendly
timezone,
and
then
a
ship
is
friendly
time
zone
so
that
every
other
meeting
alternates,
which
will
make
it
appear
to
have
participation
around
the
globe.
The
challenge
is
that
currently,
the
two
co-chairs
whose
contact
information
they'll
see
in
a
minute
are
are
in
both
in
the
North
America.
E
A
E
A
Is
our
links
in
the
presentation
to
the
recorded
meeting
so,
if
you're
not
able
to
participate
live,
you
can
always
go
back
and
understand
the
way
the
conversations
are
evolving
in
the
community
meetings.
The
link
here
is
to
recordings
of
all
of
the
meetings.
We
also
very
actively
maintain
and
go
through
in
those
meetings,
github
project
board,
so
the.
B
A
A
prioritized
backlog
or
peach
of
the
releases
and
we
very
actively
maintained
whose
assign
labels
to
those
like
like
good,
first
issue,
documentation
and
examples.
Those
kinds
of
things
are
also
labeled
in
there.
So
it's
a
great
place
to
go
and
kind
of
understand
the
dynamics
of
what's
happening
and
start
grabbing
issues
and
contributing
to
them
commenting
and
doing
reviews
on
other
people's
stuff.
That's
a
great
way
to
participate,
and
really
this
isn't
asked
for
me
as
a
product
management
kind
of
guy
I
want
to
talk
to
you
and
understand
your
use
cases.
A
C
A
Is
actually
a
tech
lead
on
signature
in
cig
windows?
He's
a
significant
contributor
I,
have
no
official
capacity
in
cig
windows
except
the
I-clay
PM
and
run
around
and
try
to
help
them
close
gaps,
but
in
here
these
are
the
links
to
all
the
ways
in
which
you
can
reach
kind
of
the
leadership
and
the
community.
A
A
A
A
C
Actually,
one
month
into
mission
and
to
you
know
then
many
to
serve
a
mission.
That's
the
lotion,
I
pasted,
down--
sidecar
right
by
the
sidecar,
is
actually
sometimes
not
working
on
Windows,
so
women,
yeah,
yeah
I
need
some
time
for
Windows
container
to
evolve
and
install
a
new
feature
in
there.
Oh
actually.
C
A
Today,
not
so
in
the,
if
you
go
to
the
slack
channel,
there's
Patrick
is
Patrick
Lang,
who
is
one
of
the
co-chairs
has
posted
a
proposal
or
three
different
options
which
works
exploring
together
with
the
rest
of
the
community
for
how
to
support
privileged
containers.
This
is
a
significant
challenge.
A
B
A
A
A
Focus
on
treating
the
nodes,
not
as
things
that
you
maintain
for
a
long
period
of
time.
You
need
to
build
your
practices
so
that
the
nodes
can
go
away
and
that
allows
you
then
to
kill
nodes
and
instantiate
new
nodes
with
whatever
KB
and
version
of
the
operating
system.
You
want
I
know
that
doesn't
work
for
every
workload
and
we
understand
that
so
we're
working
on
mechanisms
for
doing
patching
in
place
after
that
I
know.