►
From YouTube: Kubernetes SIG Windows 20211214
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everybody
and
welcome
to
the
december
14th
2021
iteration
of
the
kubernetes
sig
windows
community
meeting.
As
always,
these
meetings
are
recorded
and
uploaded
to
youtube
so
be
sure
to
adhere
to
the
cnc
code
of
conduct.
A
Let's,
okay,
let's
get
started,
there's
a
couple
of
announcements.
One
is
that
the
kubernetes
dev
mailing
list
is
being
migrated
in
early
january.
I
believe
that
the
contributor
experience
team
is
planning
on
doing
that
on
january,
2nd,
so
what's
happening.
Is
there
a
lot
of
the
current?
The
kubernetes
like
mailing
lists
are
google
groups
and
which
are
the
I
guess,
the
free
offering
for
the
google
suite
groups
and
they're
running
into
a
lot
of
limitations.
A
So
they
are
migrating
those
to
g
suite
groups,
so
they
have
a
lot
more
control
and
everything
this
should
be
kind
of
transparent
for
most
users.
I
think
that
they're
still,
finally
or
finalizing
some
communications
mails,
but
basically
in
early
january
they're,
going
to
stop
updates
to
the
existing
kubernetes
that
mailing
list
they're
going
to
keep
it
around
and
they're
going
to
migrate
all
of
the
users
to
the
new
mailing
list,
which
I
believe
is
just
going
to
be
kubernetes
dev
at
kubernetes.io.
A
So
just
be
aware
of
that.
If
you
have
any
filters
that
are
filtering
like
male
filters
for
that,
you
may
see
emails
coming
from
a
different
address
and
the
other
thing
is,
we
will
be
working
on
re-sharing
all
of
the
doc
or,
like
all
docs,
like
the
meeting
notes
that
we're
looking
at
here
with
the
new
alias.
If
anybody
sees
any
issues
with
this
pass
like
in
in
january,
just
reach
out
and
slack
to
take
windows
or
any
of
the
other
channels,
there'll
be
more
messaging.
A
Coming
through
the
next
announcement
was
docker
shim
was
removed.
The
pr
to
remove
docker
shim
from
the
kubernetes
code
base
went
in
last
week,
which
prompted
us
to
you
know,
fix
up
a
lot
or
disable
a
lot
of
docker
shim,
test
jobs
and
everything,
but
other
than
that.
There's
not
haven't
been
too
much
impact.
Yet
this
also
means
that
cubenet
is
removed
if
people
were
kind
of
relying
on
cubenet.
That
was
one
that
kind
of
less
advertised
than
change
here.
A
So
if
there's
any
questions
or
if
you
were
lying
on
cubenet,
that's
I
guess
like
that
was
removed.
So
just
be
aware,
if
we
want,
we
could
talk
about
this
more
as
part
of
the
community
meeting.
If
anybody
has
any
concerns
about
the
doctorship
removal
or
anything
like
that,
one
last
announcement
is
in
the
u.s
there's
a
lot
of
like
holidays
coming
up,
and
I
was
wondering
if
people
were
okay
with
canceling
the
next
two
community
meetings,
especially
the
one
on
the
28th.
A
I
think
there's
not
going
to
be
a
lot
of
the
folks
here.
If
anybody
has
any
concerns,
let
me
know
if
not
I'll,
probably
cancel
those
and
give
let
folks
kind
of
just
relax
and
have
some
time
to
focus
on
whatever
they're
working
on.
A
Okay,
if
not,
we
could
start
with
some
of
the
topics.
Jing,
I
see
that
you
commented
on
this.
Are
you?
Yes,
I
see
you're
in
the
meeting.
Oh,
it's
like.
B
Yes,
I
was
reading
this
documentation
about
windows,
support
and
I
feel
some
part,
I'm
not
very
sure,
and
it
might
need
to
be
updated.
B
I
list
a
few
of
those,
for
example,
here
the
first
one
module
months
cannot
project
file
so
directory
back
to
the
host
file
system.
I'm
not
sure
the
meaning
of
this,
and
it's
still
true
or.
A
I
have
not
looked
at
this
recently.
I
know
I've
made
some
other
updates
to
like
what
was
supported,
because
I
did
see
a
lot
of
things
like
the
I'll
find
them
later.
A
lot
of
yeah.
A
lot
of
this
document
was
outdated.
B
A
A
I
don't
have
a
lot
of
the
history
about
why
we
say
some
things
like
body:
mods
cannot
project
files
or
directories
back
to
the
host
file
system.
Does
anybody
else
on
the
call
have
some
of
that
context?
If
not,
I
think
we
could
probably
just
reword
it
so
that
they
make
like
do
some
validation
and
then
update
the
wording
or
just
remove
some
of
these.
A
D
Yeah
I
had
a
couple
of
things
as
well,
I
think
so
mark.
Should
we
just
like
redo
the
thing
in
a
big
effort.
Should
we
just
do
small,
pr's
and
like,
but
I
think
at
some
point
we
discussed
in
this
community
meeting
about
like
kind
of
restructuring
it
like
this
page
has
grown
to
be
too
too
huge
and,
like
there's
a
lot
of
information
there,
but
I
don't
know
if
it's
the
right
time
should
we
just
keep
doing
the
prs
for
now.
A
Yeah,
so
tim
bannister
did
do
a
pretty
big
restructuring,
but
I
think
that
there's
still
room
for
improvement
here.
If
for
for
things
like
like
this,
where
it's
just
little
like
comments
that
are
either
not
true
anymore
or
confusing,
we
should
probably
just
update
those
quickly
with
a
small
targeted
pr
for
just
to
fix
the
accuracy.
A
D
Okay
sounds
good
yeah.
There
are
a
couple
of
more
inaccurate
things
there
that
were
called
out
by
some
of
the
customers
who
come
to
this
page
very,
very
frequently,
apparently
so
anyway,
I'll
make
the
brs
too.
E
I'll
also
make
my
sales
pitch
for
dev
tools
here,
because
that
was
one
of
the
reasons
we
originally
built.
It
was
that
it
doesn't
it's
the
there's,
an
abstraction
in
the
way
we
document
windows
stuff-
that
is
not
clear,
was
not
clear
at
least
to
me
once
I
started
working
on
it
and
it's
like
our
options
are
aks
gke,
which
are
paid
kind,
is
not
an
option.
Kind
is
like
the
reference
for
everyone
else
right
in
linux,
and
you
know
another
free.
E
We
don't
have
to
go
with
devtools,
because
there's
also
cluster
api,
which
is
a
great
abstraction
to
go
with
it's
a
different
one,
but
it's
a
immutable
image
based-
and
it's
like,
I
think,
picking
one
of
those
as
like
the
framework
for
how
we
talk
about
this
might
be
might
for
me
would
be
more
useful
because
it's
like
it's
like
have
it's
like
starting
with
something
concrete
is,
is
easier.
I
think.
A
Yeah,
I
think
it's
I
think
this
page
is
trying
to
serve
too
many
purposes,
because
I
can
see
some
users
coming
from.
You
know
like
a
cloud
offering
or
something
just
saying:
hey.
Does
this
work
as
I'm
expecting
it
to
work
and
and
those
for
that,
for
some
of
that
for
some
of
those
scenarios
it
is
handy
to
be
able
to
see
like
things
like.
Oh
you
know,
volume
ups
like
certain
types
of
resize
operations
may
not
work
as
or
or
things
like
that
and
they're.
E
D
E
If
you
want
to
get
a
cluster
working
and
then
you
can
go
to
any
of
those
projects,
whichever
one
you're
interested
in
and
read
the
internals
of
how
they
set
up
windows
and
sick
windows.
Well,
we
create
this
one
that
you
can
just
get
one
working
locally
on
your
machine,
so
you
don't
need
a
cloud
for
that
and
it's
like
that
would
be
the
best
introduction.
I
think,
for
a
person
to
then
dive
into
those
other
things.
A
Yeah-
and
I
think
that
also
kind
of
so
I
think
we
ran
into
some
of
these
conversations
a
little
bit
when
our
event
was
updating.
The
the
volume
out
like
properties
in
the
documentation
is
like,
I
think,
originally
all
of
the
documentation
on
this
website
was
for
linux,
except
for
this
one
windows
page,
but
over
time.
A
More
and
more
of
the
individual
features
that
are
coming
online
or
like
the
the
concepts
pages,
are
saying
like
here's,
how
things
work,
here's
the
differences
between
windows
and
linux,
and
I
think
that's
actually
where
a
lot
of
this
should
be
because,
if
somebody's
looking
for
you
know
how
does
this
one
feature
work,
they
may
not.
They
probably
won't
come
back
to
the
windows
page
to
see.
Oh
here's,
the
difference,
so
one
thing
that,
like
might
make
sense,
is
to
actually
remove
a
lot
of
content
from
this
page
and
put
it
into
the
other.
E
What
what
if
we,
what
if
we
just
set
up
a
time
where
we
literally
restructured
it
with
tim,
and
we
made
like
five
pr's
together
right
and
we
just
said
like,
let's
just
make
all
like,
we
could
do
it
in
the
after
hours
right.
We
could
just
ask
him
to
come
and
we
could
just
do
it
right,
like
kind
of
online
like
pair
on
it,
and
then
we
wouldn't
have
a
big
back
and
forth.
You
know
yeah.
E
Let
me
I'm
happy
to
go
to
a
separate
meeting,
but
I'm
just
thinking
that
might
be
more
efficient,
because
every
time
I
do
a
docs
pr,
I
go
back
and
forth
so
much
on
it
that
it
takes
months
to
merge
it.
It's
like
you
know
it's
like
if
we
all
just
looked
at
it
together.
It
might
save
us
all
a
lot
of
time
and
we
just
break
the
pages
out
right
then,
and
there.
A
Okay,
yeah
I'll
take
that
as
an
action
item
I'll
set
something
up.
Let
me
reach
out
to
tim
to
see
what
time
zone.
E
E
A
Yep
yeah,
I
think
that's
that
would
be
good,
but
yes,
so
for
the
until
then,
if
if
there
is
any
accuracy
issues,
let's
open
up
small
prs,
I
can
I
can
help
open
up
the
pr,
but
if
people
want
to
do
that
too
feel
free
to
do
that
cool
thanks
for
bringing
this
up
thing.
B
Sure
one
also
a
quick
question
about
mount
propagation
with
I'm
not
sure,
as
someone
posted
in
the
chat
that
there
was
issue
and
once
there's
pr
to
disable
mount
propagation
with
host
process
feature,
I
don't
know
month,
propagation
might
work
with
source
process
or
I
haven't
really
looked
into
the
details.
C
No,
I
have
not
seen
anything
about
anyone
trying
to
do
that.
B
Yeah,
so
I
think
at
that
time
people
like
test
is
not
working
in
windows,
so
there
is
a
pr
that
I
just
posted
in
chat
to
disable
my
propagation
for
windows
container
so
looks
like
the
code
check.
If
it's
runtime
is
windows,
it
return
use
private
for
it.
B
Just
want
to
confirm,
there
is
also
mentioned
in
windows.
Node
is
expanding,
mounted
volume
not
supported,
but
I
don't
know
overall,
like
we
have
this
feature
called
volume
expansion
it
it
work
for
some
of
the
already
for,
let's
say
csr
drivers.
So
I
don't
know
what
that
claim
means.
A
A
F
A
E
Of
agenda
items,
I
can
I
just
from
thinking
about
this.
I
just
sort
of
was
pasting
together,
a
blog
post
for
our
internal
here,
but
it's
none
of
the
stuff
is
proprietary,
so
I
figured
I'd
just
share
it,
but
I
guess
if
you
give
me
screen
or
if
you
go
to
that
link,
that
might
be
a
good
solution
to
the
thing
we
were
just
talking
about.
I
mean
not
this
post,
but
maybe
we
could
just
like
borrow
the
diagram
from
it.
E
I
don't
know
if
you're
thinking,
oh
yeah,
but
my
my
only
ask
would
be
please
nobody
here
like
go
like
tweet
this
or
anything,
because
it's
supposed
to
be
a
tons
of
blog
post,
so
so,
but
like
just
for
us,
we
can
look
at
it
like
this
was
kind
of
I
had
to
solve
this
problem
of
like
how
do
you
introduce
people
to
this
different
concept
of
installing
kubernetes,
so
that's
kind
of
the
way
I've.
E
This
is
the
way
I've
kind
of
described
it
to
simplify
it
and
then,
if
you
scroll
down,
it
shows
like
what
we
do
for
image
builder,
like
zooming.
In
on
that
first
thing,
where
we
use
the
burrito
and
then
we
use
the
burrito
to
pull
stuff
into
image
builder,
and
then
we
set
those
parameters,
and
then
that
makes
the
ova
and
then,
if
you
scroll
down
again,
you'll
see
another
one
and
that's
sort
of
telling
us
how
we
in
in
teen
tons.
E
We
use
cluster
api,
but
we
generate
a
bunch
of
ytt
and
stuff
and
so
that
sort
of
describes
how
you
make
a
linux
control
plane.
And
then
you
have
windows,
worker
cluster
and
that
all
really
applies
to
cluster
api
as
well.
E
I
assume
james,
you
all
do
the
same
thing
in
some
manner,
for
whatever
that
version
of
azure
is
that
uses
capzi,
but
that
I
guess
those
are
kind
of
the
three
things
that
I
kind
of
think
of
like
there's
the
part
of
creating
an
image
and
then
there's
the
part
of
like
joining
that
image
into
some
linux
control
plane.
It's
like
those
are
kind
of
like
the
three
steps
and
mate,
and
then
everything
else
is
kind
of
just
fluff.
It's
like
you
know
it's
like
the
conformance
and
all
that
stuff.
E
So
we
don't
really
have
to
look
at
the
other
stuff,
but
I
just
wanted
to
share
that
because
it
might
be
a
thing
we
can
steal
like.
We
could
totally
possibly
steal
that
if
we
wanted
to
go
down
making
docks
for
cluster
api
on
windows.
But
I
don't.
E
Better
docs
for
cluster
api
on
windows
that
I
should
be
referencing
here,
so
yeah
kind
of
a
open-ended
question.
F
Do
have
a
windows
introduction
dock
for
capsi.
I
can
link
it
here,
but
I
don't
think
it's
it's
not
necessarily
beginner
cluster
api
kind
of
stuff.
E
And
then
I
don't
have
so
the
only
other
thing
was
I
figured.
I
would
just
mention
that
we
have
that
the
operational
readiness
stuff
I
figured.
Maybe
we
could,
if
we
had
a
prototype
up,
it
might
help
move
the
move
things
forward
on
our
on
our
cap.
E
So
I
I
I
sort
of
hacked
one
together
on
sunday
and
it's
pretty
stupid,
but
it
does
sort
of
does
the
thing
that
we're
supposed
to
do
in
the
cap
in
a
really
really
primitive
sort
of
way,
and
so
I
don't
know
I
might
hack
on
it
some
with
muzz
or
something.
E
But
the
idea
is
that
it
will
implement
that
spec.
So
you
would
write
your
json
out
and
then
it'll
figure
out
whatever
ginkgo
tags
and
whatever
and
it'll
just
output.
Here's
what
your
windows
cluster
can
do
and
here's
what
it
can't
do
and
I'm
hoping
to
be
able
to
give
that
to
customers
from
a
sono
buoy
perspective
pretty
soon
so
I'll
probably
work
some
on
it,
maybe
with
muzz
or
we'll
see
if,
if
other
folks
want
to
hack
on
it,
but
I
don't
think
there's
enough
work
for
like
10
people
so
but
yeah.
D
Hey
dude,
whenever
you're,
quoting
just
just
being
honest
like
I'll,
be
ready.
I'm
I'm
free
this
week.
E
F
Yeah
jay,
I
I
took
a
look
at
this
and
also,
I
think,
thanks
for
all
those
updates
to
the
the
cap,
that
was
the
implementation
or
the
idea
for
this,
and
so
I
think
most
of
my
ans.
My
questions
are
all
answered,
so
I
don't
know
if
anybody
else
wants
to
take
a
look,
but
I
think
we're
moving
in
the
right
direction.
Excited.
G
A
That
cap,
I
was
following
the
updates.
I
think
we
still
need
the
pr
review
in
order
for
that
to
be
merged,
we'll
see
if
robbie
do
you
know
if
david
deeds
is
around
and
for
this
week.
H
Have
you
been
reviewing
it
or
if
you
are
looking
someone
from
the
broad
readiness
team,
yeah.
A
I
would
say
the
right
level
of
context
to
do
some
of
the
pride
readiness
things,
but
we
can
find
a
different.
A
As
well
needed,
okay,
because
I
think
it's,
I
think
from
the
pride
readiness
perspective
like
I
do
think
that
there
is
some
value
of
having
somebody
who's.
Not
you
know
super
familiar
with
windows.
Reviewing
it
to
you
know,
just
help
like
make
sure
things
are
clear
for
like
would
be
clear
for
users
or
people
coming
in
from
a
primary
linux
background
too,
but
he
does
have
he.
A
A
H
A
E
Yeah,
I
mean
there's
no
need,
but
I
think
unless
there's
strong
opinions
against
it
for
us
on
our
end
once
it's
in,
we
can
really
sort
of
dig
into
it
and
get
it
working,
invest
into
it.
And
it's
going
to
be
hard
for
us
to
do
that
if
it
doesn't
merge.
So
if,
if
we
want
this
tool,
then
I
think
we
would
want
to
then
it's
in
our
best
interests
to
sort
of
bug
people
to
merge
it.
E
You
know
so
it's
not
it's
not
like
it's
something,
that's
going
to
block
a
release,
though,
so
I
don't
want
to
be
like
at
the
same
time
that
I'm
like,
let's
merge
it.
I
also
don't
want
to
be
like
you
know,
like
have
people
not
do
other
things,
you
know
so,
hopefully
it's
not
a
complicated
process
to
you
know
it
feels
to
me,
like
it's
just
a
matter
of
getting
a
stamp
on
something
I
I
you
know.
A
H
I
Can
I
ask
a
quest
question
quickly?
Yeah.
This
is
gene
from
microsoft.
So
actually,
yes,
I
I
start
a
thread
with
mark
and
james
asked
about
server
2022
support
from
upstream.
So,
as
everybody
know,
we
have
already
published
the
test
results
in
test
grid.
So
is
it
anything
else
we
need
to
take
care
to
announce
like
server?
2022
is
officially
supported
like
the
kubernetes
documentation
or
any
other
actual
item.
We
should
start
looking
into
just
want
to
get
some
opinion
from
you
guys.
A
I
Yeah,
like
the
kubernetes
public
documentation,
is
the
mentioned
like
server.
2019
is
supported
as
a
windows
note.
Should
we
update
like
server
2022
is
also
supported,
or
somebody
is
who
is
the
owner
for
this
documentation.
A
We
we
are,
I
think
we
can,
let's
double
check
the
test
results.
If
the
test
results
look
good
for
123
on
windows,
server
2022,
then
we
can
update
it
to
say
that
that's
supported,
because
we
do
have
all
the
test
images
we
do
meet.
All
the
we
would
be
meeting
all
the
criteria
for
that.
We
had
said
before,
with
the
sac
releases.
A
G
Just
a
small
note:
when
support
for
windows
server
2022
was
added
to
the
pause
image
that
should
have
also
been
included
in
the
release.
Notes
for
123
kubernetes,
just
fyi.