►
From YouTube: Kubernetes SIG-Windows 20221108
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
November
8th,
2022
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
cncf
code
of
conduct
all
right.
Let's
get
started
a
pretty
light
agenda
today,
but
we
were
just
discussing
I
think
we
can
add
a
few
more
there's.
A
few
things
to
discuss.
A
First
announcement
is
code.
Freeze
is
tonight's
I
think
it's
5
p.m,
PST!
So
there's
some
PRS
that
need
to
get
in.
Let's
try
and
get
those
merged.
A
I
think
everybody's,
probably
just
tracking
for
that
code-
freeze
all
right.
Next,
we
can
see
if
there's
any
new
contributors
here
or
anybody
wants
to
say,
hi
pause
for
a
minute.
If
there
is
either
you
know,
add
your
name
to
the
agenda,
feel
free
to
just
say:
hi,
say
something
in
the
chat.
A
Okay,
Jay
did
you
want
to
give
a
quick
update?
Well
and
then
we
can
look
at
the
node
service
log
viewer
stuff
that
Irvin's
adding
yeah
yeah.
B
I,
after
back
and
forth,
Signet
and
cigarch
for
the
kpng
stuff,
I'm
thinking
we're
going
to
propose
a
coup
proxy
Library
implementation
that
takes
maybe
60
or
well
not,
there's
no
percentage,
some
of
the
core
Library
like
functionality
in
kpng
for
the
for
the
proxy
and
make
that
a
separate
repo
and
then
different
folks,
Can
Vendor
it
how
they
want
to
to
make
custom
Coupe
proxies.
However,
they
want
right,
so
I
think
that
sort
of
kind
of
renews
the
conversation
of
what
we
want
to
do
for
Windows.
B
B
A
Would
I
know
like
some
of
the
other
cnis
are
either
doing
their
own
implementation
of
Q
proxy
in
their
like
in
their
own
Solutions
I'm,
not
I
haven't
looked
enough,
but
if
any
of
them
are
supporting
Windows,
would
they
use
the
same
library
or
would
it
really
just
be
a
Sig
Windows,
Q
proxy?
That
would
be
consuming
that.
B
It
would
be
the
there's
definitely
people
outside
of
this.
This
direction
is
actually
proposed
by
people
outside
of
the
windows
community
for
sure.
So
because
you
know,
I
was
kind
of
like
all
in
Yolo
like
let's
just
yeah
burn
everything
to
the
ground
and
I
I
just
wasn't
able
to
sell
that.
So
the
the
middle
of
the
road
Solution,
that's
being
proposed
by
some
folks
actually
over
at
Red
Hat.
Is
that
look?
B
B
Like
you
know,
I
mean
let's,
let's
make
it
so
that
eventually
the
the
Intrigue
could
proxy
can,
if,
if
we
want
at
some
point
possibly
start
to
adopt
some
of
that,
but
part
of
the
deal
that's
going
on
here
is
the
biggest
part
of
the
most
important
thing
in
the
entry.
Proxy
is
IP
tables,
which
is
now
deprecated
So
within
the
next
two
or
three
years.
The
most
important
parts
of
the
Intrigue
proxy
are
not
even
gonna,
be
supported
anymore.
You
know,
like
red
hat,
has
moved
off
of
I.
B
Think
I,
don't
even
know
if
Red
Hat,
even
ships,
support
for
IP
tables,
anymore
I
think
it's
all
I
mean
I,
think
they
use
iptables
nft,
but
I
don't
know
so
it's
kind
of
going
to
be
a
weird
slow,
death
type
thing,
I
think
maybe
I'm
not
sure,
but
yeah
all
the
cnis
are
doing
their
own
thing
as
well
and
I'm,
not
sure,
obviously
we're
kind
of
in
a
chicken
in
the
egg
situation
where
no
nobody's
going
to
adopt
it
until
somebody
adopts
it.
B
So
the
goal
here
is
to
get
Sig
Network
to
adopt
and
fully
endorse
something
and
the
easiest
way
to
get
Sig
Network
to
fully
endorse.
Something
is
to
make
that
thing
as
small
as
possible,
of
course
right
because
it
reduces
the
reduces
the
technical
commitments.
So
that's
that's.
That's
that's.
Why
we're
going
to
library
approach.
C
Could
open
the
you
can
open
the
pr
I
can
give
a
quick
overview
of
what
has
happened.
I
I
got
a
review
from
Tim
Hawkins
on
Friday,
and
you
know
there
are
a
bunch
of
changes
he's
requested.
Most
of
them
are
doable,
but
there
are
two
big
ones
that
are
basically
blocked
the
pr
one
is
again
the
question
of
whether
this
needs
to
be
a.
We
won
PR,
we
won
API
or
V1
Alpha
One
API.
C
C
The
first
time,
because,
apparently
it's
hard
to
change
the
API
once
it's
there,
even
if
like
so
for
example,
if
you
want
to
make
a
V2
API,
it's
very
hard
to
do
and
to
be
frank,
I,
don't
fully
understand
the
complexity
of
API
missionary
to
like
drop
this
like
at
the
level
Jordan
has,
but
during
this
go
around
Tim
Hawkins
is
asking
why
we
can't
make
this
a
video,
an
API,
V1,
Alpha
API,
so
like
going
back
to
where
we
were
before
so
I'm
kind
of
like
okay,
I,
don't
know
what
to
do
here.
C
This
is
not
my
area
of
expertise.
I
need
someone
from
the
API
reviewers
to
actually
you
know
help
out
here
and
we've
tagged
Jordan
a
couple
of
times,
but
I
haven't
heard
anything
from
him.
The
other
request
that
Tim
has
made
is
so
I've,
I
I,
hope
you
folks
remember.
The
demo
I
showed
you
where
there's
a
query
command.
C
There's
a
query
flag
that
we
add
to
cube
cuddle
for
node
logs,
and
then
you
say
you
know,
query
Fubar
and
if
it's
just
a
plain,
Foo
bar
I
assume
it's
a
it's
a
service
and
I
show
you
the
service
output.
If,
if
it
is
slash,
Fubar
I
assume
it's
a
file
and
I
show
you
the
file,
but
Tim
wants
the
heuristics
to
be
a
little
bit
more
involved.
He
wants
us
to
say:
query.
Full
bar
and
Fubar
could
be
a
file
and
I
should
go
and
show
the
file.
C
I,
don't
see
the
reason
for
doing
this,
it's
getting
to
a
stage
where
it's
like
you
know.
If
someone
wants
to
see
fubar.log,
it's
obvious
that
they
know
that
it's
a
it's
a
file
like
I,
don't
see
many
people
having
a
log
file
called
FUBAR,
but
so
this
is
the
other
thing
that
he
wants.
C
I
mean
given
these
two
things:
I,
don't
think
this
PR
will
make
it
in
this
time
around
the
other
changes
I
could
I
could
easily
make
they're,
not
that
difficult,
but
the
the
API
and
and
this
sort
of
makes
it
a
bit
difficult.
A
Get
that
fully
did
I
think
I
even
commented
and
I
saw
you
comment
asking
if
that
could
be
like
if
that
was
put
black
and
an
alpha
implementation
to
Timber
or
did
Tim
respond
to
that
no
I.
C
A
A
A
2020.
I'm
dropping
a
link
in
the
chat
thanks
and
then
where's.
The
discussion
around
the
V1
Alpha
One,
like
I
I,
want
to
see
what
so.
C
C
A
C
Yeah
he
was
saying
that
this
is
on
the
same.
It's
in
the
same
space
as
like
the
Pod
logs,
which
I
think
has
the
same
issue.
C
No
I
think
I.
Don't
think
he
really
cares
about
I
I,
don't
think
he
cares
about
what's
happening
in
Cube
CDL,
it's
mainly
in
the
API
side.
I've
said
this
is
a
rerun
API
yeah.
That
is
where
the
contention
is,
whether
that
should
be
V1
or
so
now
it's
under
I
think
I
added
it
to
core
B1
again,
it's
because
Tim
Tim
told
me
to
added
a
core
view.
There's
another
comment
where
I've
asked
him
like
I
need
direction
here,
should
I
add
it
to
node
or
should
I
add
it
to
core.
C
Added
a
Decor
view,
one
like
I
can
go
back
and
add
it
to
yeah
like
it's.
Not
it's
not
something.
I
can't
do
because
that's
how
I
started,
but
then
Jordan
mentioned
this,
but
now
we're
back
to
the
same
spot
again.
So
that's
where
you
know
it's
and
it's
already
what
it's
12
45
Eastern,
so
like
what
I
have
four
hours
and
and
the
pro
the
other
problem
here
folks
is.
C
A
A
Let's
maybe
take
a
step,
oh
I
think
my
browser
froze
because
the
spear
is
too
big.
A
Oh
I
will
wait
what
like
I
was
gonna
say.
Should
we
don't
have
to
do
it
at
this
meeting,
but
should
we
take
a
step
back
and
see
like
what
we
can
do
to
try
and
get
this
to
to
merge,
because
I
think
clearly,
with
the
approaches
that
we've
been
taking
is
not
getting
all
like
the
all
the
review
attention
that
we
need
here?
A
Is
it's
really
that
the
and
I'm
just
asking?
Maybe
the
case
like
these?
These
API
reviews
are
coming
in
too
late
to
react
with
things,
and
it
seems
like
that
is
the
case,
because
this
I
know
that
this
peer's
been
iterated
on
for
most
of
this
development
cycle
and
then
there's
these
big
questions
that
have
already
been
discussed
like
in
a
previous
release,
Happening
Here
or
is
it
that
there's
or
I
mean,
and
that
can
be
part
of
it?
Is
it
that
the
peers
are
too
big?
Is
there
a
way
to
split
it
up?
A
C
C
A
C
And
and
in
fact
so-
and
it's
very
hard
to
maintain
those
two
sets
of
PRS
like
I've-
done-
that
in
other
projects-
and
it's
super
like
you-
have
to
keep
pulling
from
another
place,
there's
lots
of
git
magic.
You
need
to
do,
but
it's
doable.
It's
not
like
it's
not
impossible.
It's
it's
doable,
but
you
know
it's
it's,
especially
in
this
review
cycle
right
like
so.
If
you
take
about
it,
this
has
been
going
on
for
a
while.
C
So
my
fear
is
right.
Like
every
time
we
go
switch
over
to
release
I
I
can
again
like
I'm,
not
sure
how
to
resolve
this,
but
do
we
get
them
on
a
call?
Do
we
have
a
meeting
with
them?
I.
A
Was
actually
gonna
say,
I
think
that
might
be
the
next
step
is
either
bring
this
to
the
API
Machinery
review
or
ask
for
like
a
half
an
hour
breakout
to
your
meeting
with
them
and
I.
Think
with
like
everybody
involved,
so
that
we
can
discuss
this
and
then
say
like
okay
are
enough
stakeholders
here
that
if
any
other
reviewers
come
and
suggest
a
change,
we
can
say
no.
This
has
already
been
reviewed
by
a
panel.
B
B
A
B
C
Maybe
that
was
pretty
coveted
I
don't
know,
no
no
Jordan
is
in
in
Raleigh
Tim
I,
don't
know
where
he
is
I
know.
Jordan
is
in
rally.
D
What
I'm
hearing
is
I
think
the
the
big
blocker
here
is
the
V1
Alpha
versus
the
V1
part
of
it.
The
other
part
is
a
little
bit
of
a
like.
You
know
it's
Alpha.
We
could
probably
fix
that
and
resolve
it
for
the
next
version,
but
we
need
to
get
Tim
and
Jordan
on
the
same
page
as
to
whether
or
not
this
goes
into
alpha
or
V1
and
having
either
a
slack
thread
with
the
two
of
minute
or
a
phone
calls,
probably
yeah,
that's
way
to
go
I.
D
A
I
think
that
if
we
can
get
something
scheduled
with
with
Tim
and
or
Jordan,
we
could
probably
do
that.
But
my
concern
with
that
is
even
if
we
get
an
exception,
we're
not
like
we're
not
going
to
get
that
API
review
in
time,
but
for
the.
A
C
A
A
C
B
And
for
the
heuristic
one
I
mean
I
I
I'm
reading
this
I
was
like.
Is
it
hard
Arvin
to
just
say
if
there's
a
slash,
it's
a
file,
otherwise
it's
service,
that's
what
you're
saying
right!
Yeah!
That's
what
I've
done!
I
think
that
that's
logical,
like
I've,
seen
plenty
of
programs
in
the
past.
That
say
you
know
you
have
an
absolute
path
or
not
I
think
it's.
B
Then
no
slash
no
file,
that's
what
you're
saying
you
want
to
do.
No
slash,
no
file.
That
makes
sense.
That
totally
makes
sense
like
like
I
mean
I
get.
You
could
do
better
things.
You
could
do
more
complicated
things,
but
I
think
it
makes
enough
sense,
yeah
to
at
least
be
able
I.
Think
Tim
should
be
okay.
If
we
just
let
him
know
that
we
think
it
makes
sense,
maybe
he's
just
calling
it
out
as
hey
double
check.
This
yeah.
C
Yeah
I
can
again
add
to
that
comment
and
just
say:
I
thought
about
this
more
this
a
little
bit
more.
Okay,
all
right.
A
I
don't
know
yeah
and
I.
Think
like
this
should
sound
like
the
perfect
candidate
of
you
know:
let's
get
the
implementation
out
there
and
then
wait
for
feedback
or,
like
I'd
say
we
can
address
that
for
feedback,
and
even
if
we
have
to
update
the
cap
to
say
we
will,
you
know,
commit
to
doing
that
either
before
beta
or
before
stable
yep
Clark
gonna
get
feedback.
If,
okay,
if
it's
not
out
there,
yeah
or
yeah
people
aren't
going
to
give
feedback,
I
should
say
yeah.
C
All
right
so
action
items
is
I'll.
I'll.
Add
another
comment
to
what
Tim
said
about
the
Slash
and
then
I'll
start
a
Threading
API
reviews
and
see
where
we
can
go
from
there.
Yeah.
A
And
just
I
don't
know
if
this
is
any
consolation,
but
there
are
like
this.
Pr
is
not
alone
in
this
class
of
issues.
There's
another
one.
That's
been
going
on
in
Sig
node
for
not
quite
as
long,
but
definitely
three
releases
for
in
place.
Pod
vertical
Auto
scaling
that
I
think
it's
kind
of
the
same
in
the
same
issue.
It's
I,
don't
think
it's
all
API
reviews
holding
it
up.
A
It's
something
node
reviewers
too,
but
they
seem
to
be
stuck
in
this
cycle
of
doing
a
bunch
of
work
and
then
reviews
not
coming
in
until
the
end
and
then
missing
a
release.
I
am
planning
on
bringing
this
up
at
one
of
the
chairs
and
TL's
meetings
to
see
if
there's
something
that
we
can
do
either
with
Sig
architecture
or
contributor,
it
contribex
to
figure
out
what
the
best
way
like
to
brainstorm,
how
to
get
these
big
PR's
actually
merged.
Instead
of
sitting
there
forever.
No.
B
Yeah
I
think
the
best
thing
to
do
is
what
we're
doing,
which
is
getting
getting
to
him
or
whoever
on
the
phone
and
just
because,
because
usually
it's
pretty
simple,
because
we
had
to
do
that
for
kpng
to
Arvin
like
it
was
back
and
forth,
and
it's
been
out
for
two
years.
And
finally,
we
just
got
to
him
on
the
phone
and
we
figured
that
actually
what
he
was
saying
wasn't
that
different
than
what
we
were
talking
about.
We
just
were
talking.
C
A
Yeah,
the
gatekeeper
for
the
peers
at
that
point,
which
is
not
healthy
for
Tim
or
the
project,
yeah
and
I,
do
remember
for
the
host
process.
Containers
I
think
I
tried,
like
I,
think
that
the
same
thing
happened,
but
it
only
slept
One
release
with
the
API
reviews
came
in
late
without
time
to
address
anything.
A
But
I
remember
running
into
that
issue
too.
Where
I
mean
it's
kind
of
like
hurry
up
and
wait
to
address
these
feedback
and
hope
that
they
get
a
chance
to
re-review
before
a
code
freeze
which
usually
doesn't
happen.
B
A
B
C
D
C
B
C
B
A
Got
some
problems:
Jay,
yep
yeah,
all
right,
I
saw
Jay
link
to
this
I
do
need
to
drop
for
signode
in
a
minute
or
two
to
also
go
and
Nag
on
some
other
PRS.
So
I'm
not
going
to
start
another
big
conversation
right
now,
but
you
guys
can
discuss
if
you
want
I'll
hop
on
for
two
minutes
or
stand
for
two
minutes.
Yeah.
C
A
B
A
B
B
I,
don't
have
much
here
and
I
actually
also
have
to
go
but
yeah.
If
folks,
I
I
think
it
would
be
real
a
lot
of
fun
and
we
could
move
faster
and
be
able
to
build
a
better
Coupe
proxy
Community
around
the
windows
stuff
if
we
moved
it
out
of
tree.
So
I've
put
this
thread
on
the
mailing
list:
I
just
if
anybody
has
strong
opinions,
one
way
or
other.
Please
leave
them.
Even
if
you
disagree
with
me
because.