►
From YouTube: Kubernetes SIG Windows 20220322
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
All
right,
hello,
everybody
and
welcome
to
the
march
22nd
2022
iteration
of
the
kubernetes
seguenos
community
meeting.
As
always,
these
meetings
are
recorded
and
uploaded
to
youtube
so
be
sure
to
adhere
to
the
cncf
code
of
conduct.
Let's
get
started
with
some
announcements.
First
announcement
is
code.
Freeze
is
next
week,
that's
next
tuesday,
pst
or
I
think,
early
morning,
wednesday
gmt.
A
So
let's
work
to
try
and
get
everything
merged
that
we
want
we'll
talk
about
some
of
the
other
open
issues
later
on
in
the
agenda.
Next
announcement,
gmsa
keyboard
cctv,
plugin,
open
sourced
james-
did
you
want
to?
I
think
you
edited
this.
Did
you
want
to
comment
on
this?
If
not,
I
can.
B
Yeah
so
anybody's
been
following,
along
with
the
gmsa
side
of
things,
there's
a
new
api
in
windows
that
allows
you
to
authenticate
with
a
domain,
a
active
directory
domain
without
having
to
join
the
host
to
the
to
the
domain,
and
this
is
a
it's
a
plug-in
model,
and
so
this
is
an
example
of
how
to
do
that.
This
is
being
used
in
aks
today,
it's
if
you've
gone
through
like
aks's
key
vault
and
gmsa
steps
you'll
end
up
using
this
and
yeah,
so
the
team
has
open
sourced
it.
B
I
think
it
has
a
lot
of
valuable
ways
of
how
to
install
it,
how
to
interact
with
the
api,
how
to
store
things
in
external
resources
and
then
authenticate
against
those
things
and
so
yeah.
That's
there's
been
a
lot
of
questions
over
the
last
six
months
or
so
about
how
to
do
this,
so
you
can
go
check
this
out
and
give
us
feedback
as
well
as
see
how
to
how
to
make
this
work.
For
yourself,
I
do
have
a
pr
into
image
builder.
B
That
is
installing
this
into
the
windows
nodes.
I
just
posted
it
into
the
teams
into
the
chat
there,
and
then
I
also
have
a
pr
that
I
should
be
opening
up
in
the
next
day
or
two
that
implements
this
in
cluster
api
for
azure,
so
that
we
can
run
the
end-to-end
tests
using
it.
And
that's
actually
one
of
my
next
topics
to
talk
about
so.
A
Yeah
folks
in
the
past
might
have
heard
reference
to
a
gmsa
v2.
I
think
that
that's
what
this
was.
It's
that
credential
guard
or
container
credential
guard
plug-in
previously.
There
was
updates
to
the
like
microsoft
docs,
on
how
to
specify
it
in
your
the
gmsa
credential
spec,
but
there
was
no
reference
about
how
to
actually
configure
and
install
or
like
how
to
write
and
configure
the
plugins.
A
So
we
was
kind
of
quite
a
journey,
but
we've
got
some
of
that.
Opens.
We've
got
that
information
open
source
for
for
people
too.
So
take
a
look
if
you're.
B
Interested
and
we
also
updated
the
web
hook
to
be
able
to
support
those
extra
fields
as
well.
A
few
months
ago
mark
did
that
work.
A
Yeah,
so
that
works
in,
I
think
the
gmsa
admission
went
version
2.3.0
and
later
should
have
that.
That's
awesome,
good
check,
yeah,
yeah,
so
yeah
feel
free
to
reach
out
on
to
windows.
If
anybody
has
questions
or
ping
folks
here
does
anybody
else
have
any
announcements
before
we
move
on
to
the
agenda.
A
Okay,
next
is
we'll
leave
a
little
bit
of
space
for
each
meeting.
If
there's
any
new
contributors
that
would
like
to
introduce
themselves
or
ask
questions
or
say
what
they're
working
on
or
are
looking
for
things
to
work
on
so
I'll
open
the
floor
for
for
that
right
now,
if
there's
anybody
new
wants
to
say
anything
just
raise
your
hand
or
just
jump
on
in.
A
Okay,
I
don't
see
anybody
or
I
see
a
couple
new
people
here
today.
I
don't
see
anybody
wants
to
introduce
themselves.
Yet
that's
all
right.
We
can
go
on
to
the
agenda
next
agenda
item
james
cappy
and
gmsa
tests,
yeah.
B
Yeah,
so
I'm
working
on
automating
this
so
that
we
can
run
it
as
part
of
our
an
end
suite
that
shows
up
on
the
test
grid
signal
and
I've
got
it
all
working
end
to
end.
Except
for
this
part
here
where
our
end-to-end
test
calls
out
to
bash
and
cluster
we're
using
cluster
api's
framework
for
running
the
conformance
test,
and
it
calls
to
bash
or
sorry.
It
uses
the
performance
image
and
the
conformance
image
is
built
on
slim
or
actually
a
distro-less
image,
and
so
it
doesn't
have
bash.
B
It
doesn't
have
a
bunch
of
different
utilities
in
it,
and
so
I
think
I
don't
think
we
should
be
calling
out
to
bash.
I
haven't
found
any
other
instances
in
tests
that
do
this
type
of
thing,
and
so
I've
kind
of
evaluated
a
few
different
ways
of
going
about
solving
this
problem.
B
My
current
one
is
using
agn
host
and
installing
a
couple
extra
tools
that
we
do
need
and
then
calling
that
script
from
there.
I
do
have
a.
I
did
a
prototype
this
morning
on
making
that
work,
but
if
anybody
has
any
ideas
or
thoughts
or
I'm
totally
open
to
discussing
them,.
B
B
Right
that
that
test
and
and
the
job
itself
is
the
serial
slow
that
we
have
for
capsi
for
the
gupsy
okay.
B
And-
and
that's
because
I
put
a
link
in
there
if
you
look
at
like
cluster
api,
it's
that
top
link
the
way
they're
doing.
This
is
they're
using
the
conformance
image
to
to
run
the
ede
binary
and
that
conformance
image
doesn't
have
it's
it's
just
jewelry,
so
it
doesn't
have
anything
in
it,
except
for
cube
test,
cube,
ctl
and
a
binary
to
run
the
conformance
test.
A
B
Yeah
we
run
ede
test
binary
directly
on
jeepkins,
and
so
qkins
has
all
those
tools
installed,
and
so
it's
not
an
issue.
D
E
E
E
You
know:
writing
entire
scripts
into
into
bash,
especially
since
newer
versions
of
bash
have
more
specific
syntax,
which
is
not
supported
in
busy
box.
So
that's
going
to
be
problematic,
and
I
have
seen
issues
like
that
in
the
past
and
of
course
there
are
all
sorts
of
differences
between
windows
and
linux,
including
different
resources,
for
example.
E
How
you
know
depicting
linux,
you
have
stretchy
tc,
slash,
resolve.conf,
that's
different
on
windows
that,
besides
in
a
totally
different
place,
I
think
you
can
get
that
information
from
registries
between
those
and
all
those
type
of
differences
are
being
solved
by
the
agnost
binary
in
diagnosed
image,
for
example,
since
that
is
the
main
purpose
of
that
image
is
to
produce
the
differences
between
those
two
operating
systems.
B
Right
yeah,
what
I'll
do
is
I'll
open
up
the
pr
with
the
prototype
I
did
this
morning
and
then
I
think
that
will
make
it
a
little
bit
more
concrete
for
people
to
get
feedback
on.
B
Exactly
yeah
and
I
was
able
to
get
it
to
deploy
using
the
agm
host
image
and
I'm
using
the
linux
one
like
deploying
a
pod
onto
the
linux
machine
running
that
script,
and
so
there's
no
like
there's
no
obvious
up
issues
that
would
come
up
because
I'm
trying
to
run
it
on
windows
bash
or
something
like
that.
E
D
A
Okay
next
item-
I
added
this,
but
this
is
kind
of
on
behalf
of
robbie's
pr
to
promote
the
pandora's
field
to
beta.
A
I
think
everybody
on
all
of
the
participating
sigs
have
said
that
this
looks
good
pending,
seeing
it
run
as
an
e
test
of
I
took
a
quick
look
this
morning,
nice
james,
to
help
look
to
didn't,
have
enough
time
to
actually
look
at
it,
but
the
test
case
that
robbie's
adding
is
not
showing
up
even
in
the
skipped
list
for
any
of
the
pr
jobs.
So
I
think
we'll
need
to
keep
looking
at
that.
A
I
think
we
can
take
this
offline,
probably
yeah,
just
tested
for
related
too.
So
I
hope
that
we
can
get
that
sorted
out
later
like
earlier
today
to
get
this
merch
early
if
you're
gonna
be
around
james,
maybe
claudia
you
can
help.
Look
at
this
too.
E
Yeah,
can
you
drop
a
link
somewhere?
It's
in
the
meeting
notes.
Do
you
want
me
to
okay?
No,
I
can
find
them.
A
Okay
yeah,
I
I
before
this
meeting,
I
checked
out
the
pr
branch
and
then
I
the
meeting
started,
so
I
can
get
to
that.
Next
one
is
the
logs
node
service
log
viewer.
Pr
is
arvind
back.
I
think
he
was
on
pta.
No
I'm
back.
Okay,
yeah!
I
so
I
reviewed
this.
I
gave
an
lg
tm
for
like
the
window
specific
stuff
and
I
reviewed
the
cable.
It
changes
and
they
looked
okay
to
me.
I
think
ryan
also
looked
at
them.
A
It
seems
like
the
some
cli,
the
cli
reviewers
had
some
specific
feedback.
D
That's
correct,
so
I
think
we
have
addressed
ryan's
feedback.
Mache
gave
us
a
review,
I
think
last
thursday.
So
that's
what
chris
and
I
are
are
working
on.
I
still
think
we
should.
We
should
be
able
to
get
this
in
the
the
change
request,
at
least
from
looking
at
them.
Don't
seems
too
hard,
so
I'm
still
going
to
push
for
getting
this
in
the
the
last
remaining
thing
is
the
api
review.
I
did
ask
for
it,
but
other
than
that,
I'm
hoping
we
can
push
this
through.
A
If
usually
folks
will
go-
and
I
don't
when
was
it
added,
usually
the
api
reviewers
have
their
own
board,
where
they'll
put
things
into
like
reviewing
or
needs
reviewer
needs
review
assigned.
A
If
you
don't
see
that,
then
I
would
ping
in
the
api
review
slack
channel,
if
you
just
edit
it
okay,
yeah
I'd,
maybe
after
this
meeting
ping
folks,
just
to
make
sure
it's
where
that
okay,
I
can
do
that
I'll,
also
check
to
see
if
it's,
if
any,
if
it's
open
that
anybody
can
add
it
to
at
least
the
needs
review
for
124
column.
A
Probably
after
this
meeting,
okay
yeah
I'd
say
like
once:
it's
on
the
project
board
I've
I've
usually
seen
people
take
a
look
at
it,
but
if
it's
not
on
their
project
board,
then
I'd
ping
them.
A
Put
it
on
the
on
the
on
the
project
board,
I'll,
try
and
put
on
the
project
board
after
this
meeting,
and
if
I
can't
I'll
like
I'll
message
you
in
slack
okay,
so
did,
did
you
have
to
do
any
like?
Were
there
any
substantial
deviations
from
what
was
defined
in
the
the
cap
for
the
api
changes?
D
Think
so
I
think
they
were
it's
pretty
much.
You
know
what
we
set
out
to
do.
The
only
thing
is
clayton
wanted
something
that
we're
adding
here
to
be
extended
to
pod
logs,
but
this
pr
is
already
so
big
that
I
don't
see
a
way
to
add
that
so
I'm
going
to
do
that
as
a
follow-up
pr,
okay,
I'm
basically
focusing
on
the
node
log
viewer
bit
here.
A
A
For
for
all
of
that,
let
me
know
if
there's
anything
else,
I
can
do
to
help
next
set
of
agenda
items.
I
was
looking
at
the
prs
that
we
had
open
and
wanted
to
merge
for
124.
I
think
that
claudia
some
of
these
were
yours.
There
was
some
work
to
add
more
conformance
tests
for
windows.
E
Yeah
pretty
much
reviews
so
for
the
most
part
they
are
not.
They
do
not
they're
not
complicated
for
those
who
do
not
know
the
basically
their
conformance
tests,
which
pretty
much
everyone
has
to
run,
but
some
of
them
have
been
tagged
with
linux
only
because
they
could
not
run
in
the
past
for
windows.
E
Those
have
been
reduced
over
time
due
to
you
know,
sig
windows,
efforts
to
you
know,
add
new
features
and
make
it
more
bring
up
the
parity
to
make
to
make
the
parity
better
between
those
two
oss.
E
But
there
are
still
a
couple
of
of
this,
which
were
still
tagged
linux
only
and
they
became
the
issue
why
they
didn't
become
runnable
on
windows
was
because
we
had
to
support
docker
as
well,
which
was
removed
in
the
latest
release
of
kubernetes.
E
So
we
don't
have
to
worry
about
that
anymore,
since
we
are
now
pretty
much
supporting
container
d
and
those
features
work
on
container
d,
especially
since
we
continued,
we
have
introduced
a
few
other
features
as
well
like
host
processes,
because,
for
example,
there
are
some
tests
which
require
host
network
to
be
enabled
and
before
you
could
not
enable
host
network
at
all.
But
if
you're
using
host
processes
you
can
have
host
network
enabled
so
that
basically
enabled
a
whole
bunch
of
new
tests
to
be
enabled
it's
pretty
much
split
into
two
requests.
A
Okay,
hello,
I'll,
you
should
do
better!
You
can
close
that
later.
E
Yeah,
okay,.
A
E
There
shouldn't
be
too
many
conformance
tests
which
are
still
tied
with
you,
know,
sony,
but
the
ones
that
remain
are
pretty
much
strictly
related
to
something
like
cc,
ctl
or
stuff
like
that,
which
really
are
linux,
specific
yeah,
including
running
as
group,
ids
and
so
on,
and
so
on,
which
we
do
not
really
support.
C
A
E
A
Great,
I
checked
there's
a
couple
of
small
like
cubelet-related
prs
that
had
been
opened
for
124.
a
couple
of
them
merged
this
morning
after
and
all
approved
them.
So
I
continue
to
watch
the
board
of
her
new
prs
that
are
targeting
124
for
the
next
week
and
well
past
the
next
week,
but
I'll
pay
more
attention
the
next
week
and
see
if
anybody
has
any
any
feedback.
A
I
will
give
an
update
to
now
on
if
a
quick
update
on
the
status
of
the
docs
updates
that
we
wanted
to
do
so.
I
had
went
to
the
sig
docs
community
meeting
and
met
with
all
the
folks,
and
they
were
happy
to
have
somebody
show
up
for
those
the
plan
right
now
is
originally.
I
had
wanted
to
target
getting
all
these
merged
into
the
dev
124
branch,
so
that
when
that
did
just
get
merged
into
the
website's
main
branch,
those
changes
would
be
live.
The
docs
team
is
there.
A
A
Just
because
so
much
of
the
the
code
like
the
documentation
was
written
when
docker
was
the
doctor.
Shim
was
kind
of
the
only
thing
so,
but
they
did
agree
that
all
of
the
changes
should
go
in
all
at
once.
So
what
we've
worked
out
is
we'll
keep
the
prs
open
at
targeting
the
dev
124
branch,
and
that's
because
some
of
the
individuals
from
that
sig
are,
I
think,
on
a
weekly
cadence
now
but
moving.
A
But
as
we
get
closer
to
the
release,
more
frequently
are
emerging
maine
into
dev
124
to
pick
up
any
new
changes
there.
A
So
the
plan
that
we've
worked
out
with
is
that
after
the
dev
124
branch
merges
and
goes
live,
they
are
going
to
keep
the
dev
124
branch
open
for
all
of
the
windows,
docs
related
changes,
and
then
we
can
merge
those
into
the
dev124
branch
use
the
dev124
branch
for
a
short
period
to
stabilize
the
windows,
change
the
all
the
windows,
documentation,
changes
that
we
have
and
then
we'll
do
a
one
big
merge
from
the
dev
124
branch
into
the
master
branch.
Again.
A
A
The
alternative
would
be
for
us
me
to
maintain
another
branch
and
to
like
ingest
all
the
changes
in
or
a
child
branch
of
dead
124,
and
that
seems
like
a
lot
of
work
for
a
couple
of
days.
Delay
too
so
yeah,
that's
that's
the
update.
I
have.
I
think
that
we'll
still
most
of
those
prs
that
we
had
open,
especially
the
ones
that
were
updated
or
splitting
up,
that
big
windows
page,
are
up
for
review.
I've
seen
people
review
them,
it's
looking
pretty
good.
A
I
think
we
still
have
time
to
do
all
of
that
work,
though
too.
So
if
anybody
has
any
questions
with
that,
I
would
like
to
contribute.
Let
me
know
otherwise.
The
plan
is
to
get
some
to
sell,
merge
all
of
those
changes
into
dev
124
and
then
remove
those
all
and
it'll
just
be
a
little
bit
after
the
initial
dev124
payload
goes
into
the
master
range
remain
branch.
A
So
does
anybody
else
have
any
questions
agenda
items
anything
I
want
to
discuss.
A
Jay,
did
you
ever
settle
on
a
time
for
the
kpmg.
F
So
if
anybody
here
really
wants
to
help
drive
it
with
me,
speak
up
now
or
just
yell
at
me,
and
slack,
because
I've
got
a
lot
of
passive
agreement,
which
is
great,
which
is,
I
think,
is
enough
for
us
to
do
something.
But
I,
before
I
really
start
you
know
before
we
really
pull
the
trigger.
I
just
want
to
see
who's
planning
on
really
coming
every
week
and
what
time
zone
they
really
prefer.
So
I'm
looking
for
some
strong
opinions.
A
You
could
flip-flop
too
I've
seen
some
like
the
sig
ducks
they
actually
they
have
every
other
week,
it's
pacific
time
and
then
the
off
weeks
they
rotate
between
like
beijing
or
idc
time.
Okay,.
F
F
Yeah
yeah,
definitely
I
mean
I
I'm
up
for
anything.
So
again,
it
just
really
depends
on
what
folks
want
to
do
and
whether
folks,
you
know,
want
to
help
but
yeah.
It's
if
you
have
friends
that
want
to
get
involved
in
in
kubernetes
and
help
start
a
sub
project
or
anything
like
that.
Let
them
know
this
is
a
good
place
and
you
know
we'll
teach
them
what
they
need
to
learn.
So
folks
feel
free
to
reach
out
to
me
on
slack.