►
From YouTube: Kubernetes SIG Windows 20210518
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
B
Welcome
everyone:
this
is
sig
windows.
C
Regular
meeting
it's
may
18th
2021,
and
this
is
a
cncf
meeting,
we'll
be
following
the
cncf
guidelines
and
code
of
conduct.
If
you
have
any
questions
or
concerns,
you
can
reach
out
to
myself
or
anyone
else
from
the
community.
C
So
we're
going
to
kick
off
the
meeting
today
and
we
typically
try
to
start
with
some
intros.
If
there's
anybody
new,
I
do
see
one
or
two
names
that
I
haven't
seen
before.
I
want
to
introduce
themselves.
Let
them
let
us
know
why
you're
interested
in
seek
windows
and
what
you're
trying
to
get
out
of.
C
C
Okay,
so
then
we'll
go
ahead
and
get
to
get
on
to
announcements
and
feel
free
anybody
to
add
any
items
to
the
agenda.
If
you
have
anything
that
you
want
to
talk
about
so
for
announcements,
we
have
the
csc
csi
proxy
is
going
stable
in
122.,
the
kep
and
updates
for
that
merged
last
week.
So
congratulations
to
everybody!
That's
been
working
on
that!
That's
that's
a
huge
milestone!
C
So
congratulations,
everybody
working
on
that!
I
just
also
we've
been
doing
the
sigma
news
after
hours.
We've
mentioned
it
a
few
times
on
the
thing
I
just
wanted
to
call
it
out
explicitly
jay's
been
helping
lead
that
and
we've
had
quite
a
few
folks
and
some
new
new
members
of
sig
windows
joining
and
it's
just
a
time
for
us
to
get
together
and
work
on
projects
prs
little
do
some
code
reviews.
Those
types
of
things
ask
lots
of
questions.
C
It's
an
informal
time
for
everybody
to
get
together
just
wanted
to
call
it
out.
We
do
it
right
after
our
normally
scheduled
meeting
here
for
so
10
pm
eastern,
and
we
do
that
for
30
to
40
minutes
depending
on
what
we're
working
on
and
how
how
interesting
it
is.
D
All
right,
I
think,
one
more
james,
just
I
think
the
the
date
was
extended
for
submitting
anything
for
coupon.
I
know
most
of
the
folks
have
already
submitted,
but
there
is
still
time
I
think
it's
may
31st.
D
C
C
So
it
looks
like
you
have
till
the
end
of
the
weekend,
so
for
anybody,
that's
interested
in
doing
that.
C
If
you're
looking
for
feedback
or
anything
like
that
and
drop
it
into
seek
windows
and
I'm
sure
people
would
review
the
talk
too
cool,
so
the
other
so
we'll
go
on
to
the
agenda.
The
first
item
is
from
me:
there's
a
kep
for
c
advisor
list
and
cry
full-time
container
and
podstats.
C
So
moving
away
from
the
advisor
implementation
and
getting
all
of
the
stats
into
the
cry
api
they
merged
that
pr
and
are
going
to
be
doing
their
alpha
implementation
in
122
and
they
pinged
us
on
the
on
the
issue
to
let
us
know
that,
there's
a
couple
open
issues
for
windows
and
they
wanted
to
have
somebody
take
a
look.
C
So
I
post
it
in
the
slack
channel,
but
I
also
wanted
to
call
it
out
here
we're
looking
for
some
some
folks
who
are
interested
in
this
particular
component
to
just
kind
of
go
read
through
the
cap
and
give
some
feedback
and,
if
interested,
be
able
to
help
identify
any
gaps
or
challenges
that
we
might
have
with
the
windows
thing.
A
I
did
start
going
through
it,
but
I
haven't
completely
got
there.
One
of
the
things
I
did
do
is
grab
an
excerpt
of
the
stats
summary
page
and
then
put
it
in
because
I
think
they
were
looking
for
it
because
I
don't
think
they
had
a
full
list
of
everything
that
we
were
grabbing
on
that
page,
so
just
drop
that
in.
C
Yeah,
so
again,
if
anybody
else
wants
to
take
a
look
go
ahead
and
it's
be
very
helpful
to
to
get
some
more
eyes
on
that
cool
muzz.
You
have
the
next
agenda.
D
Yes,
so
I
know
I
mean
this
could
be
another
reminder
and
also
like
I'm
trying
to
get
some
feedback.
So
probably
you
guys,
you
folks
know
that
docker
shim
is
being
deprecated
shouldn't,
be
a
news
for
anyone,
the
the
date
that
is
written
on
the
faq
and
the
com.
You
know
the
confirm
date.
What
I've
gotten
there
has
been
confusion.
D
Some
people
are
saying
it's,
you
know
it
will
be
taken
out
or
removed
completely
in
122,
but
the
written
date
is
123.,
so
in
kubernetes
123
when
they
release
it,
which
is
expected
to
be
around
september.
D
The
docker
shim
won't
be
part
of
the
cubelet,
which
means
that
anybody
using
the
docker
runtime
if
they
moved
to
123
their
clusters
would
stop
working.
So
I
mean
that
that's
the
reminder,
but
now
the
from
a
feedback
perspective
I've
heard
there
are
so
there
are
two
kind
of
people
who
run
kubernetes
with
windows
or
linux
I
mean
there's
one
which
are
the
the
distributors
or
the
distro's.
D
Like
you
know
the
google
amazons
and
the
microsoft,
it
seems
like
they're
pretty
much
on
track
in
moving
to
container
d
they're
all
making
a
good
progress,
but
then
I
mean
we've
been
in
touch
with
google
as
well
on
that,
and
you
know
I
I
there
were
some
issues
I
think
have
been
important
in
the
continuity
upstream,
but
doesn't
seem
like
a
blocking
issue
so
far,
but
then
there's
also
do-it-yourself
customers
who
are
running
their
own
kubernetes
and
they
may
be
running
into
issues
as
well.
D
So
the
feedback
I
was
trying
to
see
is
we
could
go
especially
because
windows,
container
d
is
newer
than
linux
and
we
had
less
of
the
time
to
move.
We
could
go
to
the
community
and
like
dims
and
signal
and
say
you
know,
just
like
give
us
one
more
release
that
would
take
that
may
take
the
pressure
off
and
it
may
be
good
for
some
of
the
customers
who
are
struggling.
But
I
wanted
to
just
you
know,
get
feedback.
D
Okay,
so
it
seems
like
there
is
no
feedback.
It's
okay,
I
mean
you
can
even
reach
out
to
me
on
slack
I'll,
be
monitoring,
slack
and
I'll
post
the
question
there
as
well.
I
wanted
to
see
like
you
know,
if
there
are
like
more
requests,
it's
not
that
hard
clay.
James
and
craig
peters
told
me.
You
know
the
the
way
we
we
will
create
an
issue
we'll
go
to
the
extension
and
we
could
try.
D
But
you
know
if
if
there
is
no
demand
or
like
you
know,
nobody
needs
it,
then
then
we
could
leave
it
for
kubernetes
123.
A
I
guess
the
only
the
only
thing
is
just
checking
that
we
got
parity
with
at
least
some
cni's
and
make
sure
that
that
works.
I
mean
we've.
This
container
d
storage
issue
is
gone
for
gsma
that
that's
kind
of
resolved,
but
I
don't
know
of
any
other
things
that
aren't
a
parity
between
continuity
and
docker.
Apart
from
cni
right,
yeah,.
D
And
that's
the
thing
right:
barry
I
mean
we
don't
know
like
we
have
tested
it.
It
doesn't
seem
like
there
are
issues,
but
there
could
always
be
issues
when
you
start
running
it
at
a
scale
right
like
once,
you
have
moved
and
the
customers
start
using
it
and
that's
why,
having
a
little
bit
buffer,
it
could
be
good.
C
D
D
C
B
C
And
then
so
I
just
added
this.
This
is
just
kind
of
a
quick
call
for
help
so
gmsa
the
gmsa
component
that
we
use
for
wiring
everything
up
it.
You
was
using
v1
beta,
1
apis,
and
so
someone
had
opened
up
a
pr
and
I
added
support
to
for
a
couple
extra
apis
that
were
also
being
blocked.
C
This
is
causing
failing
tests
in
122.,
there's
a
new
functionality
that
depreciated
all
the
old
apis,
and
so
I
was
attempting
to
upgrade
that
and
looks
like
there's
a
cert
request
in
getting
the
correct,
cert
request
formed
I'm
having
a
little
bit
of
trouble
with
that.
So
I
just
I
posted
in
stack
yesterday,
but
if
anybody
has
any
experience,
upgrading
from
v1
beta
1
to
the
v1
version
of
the
cert
request,
please
let
me
know-
and
maybe
we
can
work
on
that
together.
C
B
C
Is
there
any
other?
You
know
ad
hoc
questions
or
comments
or
things
that
this
folks
want
to
discuss
with?
Let's
discuss
on.
C
Great
then,
I
guess
we
can
end
the
meeting
a
few
minutes
early
here
and
I
don't
see
jay
on
yet.
A
C
Yeah,
that's
okay.
We
can
get
started
for
the
seed
windows
after
or
it's
a
little
bit
early,
so
I'm
going
to
go
ahead
and
stop
the
recording
for
the
regularly
scheduled
programming
and
anybody
that
doesn't
want
to
stick
around
for
some
coding
and
looking
at
seek
windows
issues
and
work
like
that
can
drop
off
otherwise
stick
around
and
I
think
I
saw
perry
was
gonna
lead
us
in
some
container
d
work
potentially.
A
C
Okay,
tweeted
something
about
that.
So
all
right,
I'm
gonna,
stop
the
recording
and
we'll
switch
over
thanks.