►
From YouTube: Kubernetes SIG-Windows 20220726
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
A
Let's
get
started
first
announcement
is
code.
Freeze
for
125
is
one
week
away,
they've
actually
set
times
for
specific
time
zones
now
and
I
believe
it's
around
6
or
8
pm
pst
next
tuesday,
if
anybody's
interested
or
if
anybody
wants
specifics
on
that,
but
getting
pretty
close
so
and
planning
on
talking
about
a
lot
of
by
spending
a
lot
of
this
community
meeting
tracking,
all
the
enhancements
and
possibly
prs
that
we
want
to
get
in.
Does
anybody
have
else
have
anything
they
would
like
to
announce.
A
All
right
doesn't
sound
like
it.
Next
we'll
provide
some
space.
If
there's
any
new
contributors
who
want
to
introduce
themselves
so
feel
free
to
do
so
either.
You
could
just
write
your
name
in
the
agenda.
You
could
just
unmute
yourself,
say
hi
or
raise
your
hand.
A
Okay,
let's
go
on
to
the
agenda.
First
thing
I
wanted
to
do
was
go
over
some
of
the
enhancements
that
we're
tracking
for
125
and
get
some
status
on
that.
A
The
first
one
is
the
node
service
log
viewer.
I
did
hear
from
arvind
yesterday
on
slack
and
it
sounds
like
he's
on
pto
or
on
leave
and
he's
returning
on
august
2nd
and
doesn't
think
he
can
address
all
of
the
feedback
for
this
cap
by
then
so
right
now,
I'm
going
to
say
it's
at
risk,
but.
A
I
don't
think
that
this
is
probably
going
to
land,
hopefully
we'll
try
again
for
126
if
anybody
else
is
familiar
with
the
status
of
this,
maybe
from
red
hat
feel
free
to
chime
in,
if
not
we'll,
leave
it
like
that
and
I'll
update
the
agenda
more
with
details
after
this
okay
next
was
the
the
pod
os
field.
A
A
There
is
one
open
pr,
that's
updating,
some
of
the
rules
for
the
new
pod
security
standard
or
the
I
think
it's
excluding
certain
fields
from
being
in
from
having
their
the
the
security
standards
being
enforced.
If
the
pod
os
is
windows,
that's
still
open,
but
there's
some
pretty
active
reviews
from
the
security
folks
from
ligit
and
from
the
docs
team
about
that
too.
So
I
think
that
this
is
still
on
track.
I
will
link
those
prs
in
a
little
bit.
Actually
let
me.
A
A
So
then,
hopefully
that
will
merge
pretty
soon
and
then
that
feature
can
go
to
stable.
A
Next
was
operational
readiness.
Is
anybody
who's
working
on
that
here
I
mean,
I
know
that
we're
not
tracking
this,
like
with
the
release
milestones,
but
I
was
just
wondering
if
you
guys
wanted
to
give
a
quick
update
on
where
the
status
was.
I
know,
chinchi
did
a
demo
of
some
more
stuff.
Last
week.
C
Yeah
sure
so
we
are
keeping
the
project
outside
the
kubernetes,
I'm
sending
the
chat,
the
repository.
We
are
calling
this
project.
So
basically
we
finished
the
chichi
finished
the
gmsa
group
of
tests
and
I
think
she
finished
the
networking
part
as
well
and
if
I'm
not
mistaken,
she
was
starting
the
storage
part.
C
A
B
A
Yeah
yeah
what
we
should
be
able
to
to
do
that.
We
can
say
that
this
is
a
like
mark,
move
this
to
a
sub
project
and
then
work
on
getting
a
new
repo
set
up
for
that.
A
B
A
C
No,
that's
all
thanks.
Mark.
A
Okay,
great
and
next
was
I
wanted
to
go,
go
ahead.
D
Sorry
so
one
other
enhancement
that
I
think
we're
kind
of
involved
in
is
the
cry
stats
right
and
so
we're
just
trying
to
nail
down
exactly
how
or
and
what
the
structure
of
the
cry
call
is.
Gonna
look
like,
and
so
we
have
an
open.
D
I
have
an
open
pr
here
and
we're
kind
of
I
think
we're
getting
close,
but
hopefully
we
can
get
that
in
by
next
week
or
we
can
get
those
changes
merged
and
then
the
the
cry
changes
its
merch
as
well.
D
But
I
think
I
think
we're
getting
close
just
need
to
finalize
that.
A
Yeah
so
so
background
for
people
who
are
on
the
call
is
the
signode
is
working
towards
having
it
so
that
the
all
of
the
stats
that
the
kubota
report
are
just
returned
from
the
cry
api
and
there
was
an
alpha
implementation
that
was
done
and
it
populated
all
of
the
fields
in
the
cryo
pi
protobuf
definition
for
the
linux
side
of
things,
but
not
the
windows
side
of
things
so
and
then
I
think
james
opened
a
pull
request
to
the
enhancement
dock.
To.
A
A
A
A
Okay,
next,
I
wanted
to
just
discuss
some
like
open
pr's
that
aren't
necessarily
attached
to
any
enhancements
that
we
wanted
to
try
to
get
merged
for
for
125.
I
know
claudio
you.
You've
got
a
lot
of
different
pr's
open
that
fix
a
lot
of
different
issues.
Is
there
any
that
stand
out,
or
should
we
just
assume
most
of
those
who
want
to
try
and
get
at
125.
E
Yeah,
I
think
this
one
just
mentioned
during
the
peers
needing
reviews.
That's
interesting
issues
that
we
discovered,
while
trying
to
fix
some
windows
unit
tests
for
kubernetes,
in
which
basically,
the
cubelet
device
plug-in
watcher
was
not
working
as
intended.
E
Technically,
it
was
supposed
to
watch
some
folders
in
which
some
new
socket
files
would
pop
up
and
basically
register
those
as
new
devices
and
so
on,
but
the
way
that
it
was
checking
if
it
was
a
circuit
or
not
does
not
really
work
on
windows.
That's
not
really
how
you
check
it,
but
we
do
have
some
utils
functions.
That
checks
checks
that
bit
more
correctly
and
I
did
send
a
pull
request
which
fixes
that
issue.
It's
an
extremely
small
request.
E
E
In
addition
to
that,
I
do
also
have
another
pro
request,
which
has
another
interesting
thing,
which
was
it.
E
Nope
not
that
one,
oh
god,
I
thought
I
lost
the
link
one
second,
the
other
one
that
I
mentioned
is
kinda,
adding
or
to
say
so,
support
for
port
dns
policies
for
windows,
which
is
basically
here.
I
did
leave
a
more
in-depth
comment
about
what
this
is
going
to
mean.
E
So
if
you
have
time
give
it
a
read,
but
basically
I
don't
know
if
you
know,
but
basically
for
pods,
you
can
also
specify
dns
policy,
which
has
the
values
something
like
default,
cluster
first
and
then
cluster
first
with
a
host
network,
or
something
like
that.
I
think
there
are
three
values
but
for
windows.
In
all
cases,
that's
pretty
much
ignored
because
we
didn't
really
support
it
before,
because
we
didn't
have
the
code
necessary
for
that.
E
Now,
with
the
addition
of
this,
it
will
basically
mean
that
the
pods
that
you
spawn
on
windows
will
also
have
the
hosts
dns,
at
the
very
least,
the
dns
suffix
list,
which
you
have
set
and
in
the
default
case
it
will
also
have
the
dns
name
servers,
dns
name
server,
set
for
the
pod
with
the
default
dns
policy.
E
A
It
seems
like
this
should
be
like
if,
if
we
pursue
this,
maybe
we
shouldn't
just
say
this
fixes
unit
tests.
This
actually
updates
some
functionality
right.
A
E
E
A
B
A
E
Yeah
and
last
one
that
I
have
which
it's
a
bit
more
debatable,
is
regarding
the
windows
file.
Permissions
basically.
A
E
A
E
Know
I
do
have
another
pull
request,
which
also
imports
this
and
also
has
a
few
more
tests,
which
makes
some
additional
assertions
that,
yes,
indeed,
those
permissions
are
set,
as
we
actually
think
they
are
being
set.
D
I
think
my
my
biggest
concern
about
bringing
this
library
in
is
as
a
dependency
is
that
it
hasn't
been
updated
in
several
years
and
it
doesn't
look
like
any
of
the
pr's
or
issues
are
being
addressed.
And
so
I
I
lean
towards
like
bringing
in
the
functionality
that
we
need,
and
it
is
an
mit
license
and
calling
that
out
in
the
in
the
code,
so
that
we
can
make
modifications,
if
required,
versus
taking
the
dependency
on
a
library
that
hasn't
been
updated
in
several
years.
E
Mean
either
way
either
way
it's
fine.
We
pretty
much
use
most
of
the
functionality
from
the
library,
with
a
few
exceptions,
for
a
few
functions
that
we
do
not
use
and
the
prequels
that
you
have
mentioned,
I
think
only
two
of
them,
one
of
which
is
not
fully
functional
and
the
other
one.
It's
actually
a
good
to
have
requests
actually,
but.
D
E
Yeah
yeah,
all
right
most
of
my
other
stuff
is
test
related
or
bug
fix
rate
or
something
like
that.
A
B
A
B
B
B
B
I
can
demo
it
later
it's
I
mean
we're
gonna,
obviously
suck
it
into
our
product
as
well,
but
I
mean
I
can
show
a
demo
through
just
boot
and
cafe
and
doing
what
it
does
yeah.
I
would
love
to
do
a
demo
of
that.
A
D
Yes,
so
you
got
that
working
for
cluster
api
for
azure,
with
aks
as
well,
so.