►
From YouTube: Kubernetes SIG-Windows 20230103
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
We're
just
coming
off
of
some
U.S
holidays
here,
so
kind
of
might
be
a
little
bit
slow
today,
but
let's
get
started
first
set
of
announcements
that
I
added
are
the
release.
Schedule
for
127
is
mostly
finalized.
I've
added
some
of
that
here.
A
A
There's
been
a
couple
emails
that
went
up
to
kubernetes
Dev
with
more
information.
If
anybody
is
looking
for
that
one
other
announcement
is,
there
is
a
release.
Team
Shadow
application
that
closes
today.
If
anybody's
interested
in
shadowing
any
one
of
the
release
roles,
it's
a
good
way
to
get
involved
with
the
release
process
and
get
to
know
more
people,
there's
a
link
to
an
email
with
more
details.
If
anybody's
interested
just
make
sure
to
do
that
today.
Before
it
closes,
does
anybody
have
anything
else
they'd
like
to
announce.
A
Not
we
can
give
some
space
if
there's
any
new
contributors,
I
want
to
say
hi.
Looking
at
the
attendee
or
participants
list,
though
I
think
everybody's
already,
everybody
knows
everybody
is,
but
if
anybody
wants
to
just
feel
free
to
say
hi
now
we
can
go
into
some
agenda
items.
A
All
right
first
agenda
item
James
is
a
pull
request.
A
B
B
It
was
using
wins
in
kind
of
a
couple.
Different
hacks
enabled
usage
for
that,
and
so
since
that
we
don't
really
support
Dr
Shim
anymore,
and
we
have
now
a
working
host
process.
Container
guide
I
was
hoping
to
get
rid
of
this,
so
I
just
wanted
to
open
it
up
and
let
folks
know
this
is
kind
of
been
broken
for
a
while,
because
people
are
trying
to
use
it
with
containerdy.
It
didn't
work
and
a
bunch
of
stuff
like
that.
B
So
I
think
it'll
just
simplify
a
lot
of
this
to
not
have
it
in
there
and
avoid
confusion.
A
A
A
B
Yeah
thanks
I
just
want
to
say
thanks
to
Fabian
for
pushing
through
and
working
on
those
the
those
guys,
but
we
got
there
and
somebody
over
the
weekend
said
that
they
got
it
working.
So
thank
you.
A
A
Are
you
guys,
using
the
final
images
produced
out
of
segment
of
tools
for
the
non-host
process?
Containers
scenario
is
this:
PR
is.
C
No,
we
should
move
Calico
is,
is
unnecessarily
using
PS1
Scripts
still,
so
we
should
move
that
to
host
process.
Andrea
doesn't
yet
support
host
process
flannel.
We
never
had
to
begin
with,
but
I
think
I
filed
an
issue
to
move
Calico
over
to
host
process
containers,
if
not
I'll
file
it
now.
Okay,.
D
A
D
Yeah
go
ahead,
yeah,
sorry,
I
think
with
Calico
there's
some
Calico
like
as
Jay,
was
saying:
there's
a
Calico
Powershell
scripts
that
we
run.
That's
where
all
that
setup
was
happening
and
I
think
I.
Think
Jay's
suggestion
has
moved
that
to
post
process
containers.
C
Yeah
issue
217,
so
if
anybody
wants
to
pair
on
it
or
anything,
let
me
know
I'm
happy
to
help
with
it,
if
not,
eventually,
we'll
get
around
to
it.
B
Yeah
and
I
guess
this
is
my
part
of
my
master
grand
plan.
Zoo
get
rid
out
of
the
business
of
building
cnis,
so
the
next
step
would
be
to
get
some
of
the
work
that
we
have
here
really
is
like
stable
in
in
Calico,
as
well
as
maybe
flannel,
and
have
them
building
and
Publishing
images.
B
A
A
Good
I
was
gonna,
say
we
just.
We
opened
up
a
request
to
get
a
repository
for
that
work
in
mid-December,
but
I
think
folks
were
probably
out
of
office.
A
So
I
was
gonna,
try
and
follow
up,
but
sounds
like
Jay
did
so
I
think
that's
the
two
kind
of
different
work
streams
for
moving
a
lot
of
the
the
image
building
stuff
out
of
the
sequence
of
tools.
Is
that
dedicated
Windows
service,
proxy
repository
and
then
the
different
cnis,
which
would
be
great
if
weren't,
all
maintained
by
Sync
Windows
into
this
repository?
So
should
we
drop
a
comment
on
that
here
too
Jay
that
we
would
want
to
probably
Target
the
new
out
of
tree
Windows
service
proxy.
C
Yeah
yeah
definitely
yeah
that
yeah
go
for
it
and
then
so
I
yeah.
Actually,
while
we're
on
that
subject
really
quickly,
I've
made
a
couple
PR's
into
kpng
to
make
it
extremely
readable
for
new
people
specifically
because
I
know
we're
going
to
try
to
adopt
it
and
so
that
one
of
them
merged
another
one
should
be
merging
soon.
C
It
should
be
self-documenting
and
then
I
just
need
to
find
Doug
and
then
we're
going
to
take
over
Doug's
PR
to
get
all
the
code
for
the
initial
drop
of
a
standalone
version
of
of
Windows
proxy
for
kpng
and
I
and
I.
Think
we
should
be
able
to
have
that
by
the
end
of
the
week
and
then
we
can
start
migrating
the
code
over.
A
Sounds
good,
yeah
and
I
think
we
also
should
ask
or
ask
like
David,
and
some
of
the
other
people
have
been
working
on
it,
to
make
sure
that
all
of
the
fixes
that
have
been
going
into
Cube
proxy
for
Windows
have
made
it
to
kpng
code
base
2.
just
so
we
don't
have
some
drift
there.
A
I
mean
I,
see
in
the
chat.
Fabian
also
said
we
should
probably
work
on
this,
so
I'll
bring
this
up
to
on
the
same
side.
We
should
check
this
in
too.
E
E
This
updates
the
scripts
for
the
build
of
Cub
proxy
for
host
process.
I
mean
the
scripts
only
build
like
six
I,
believe
six
images
and
updated
build
like
all
images
from
wanton
to
three
123
to
the
present
in
case.
Somebody
wants
to
use
a
specific
version
since
on
the
the
image,
since
the
images
are
not
built.
A
Yeah,
okay,
I'll
take
a
look
at
this
too,
and
we
should
I
believe
that
I
added
a
GitHub
action
to
that
repository
to
make
sure
that
we
have.
B
A
Okay
yeah,
so
this
GitHub
action
should
check
to
see
if
we
have
all
of
the
images
for
each
release
so
which
one
is
missing.
A
Oh
and
then
I
see
yeah
Claudio
just
commented
said
we
should
at
the
very
least
we
should
update
the
official
Docs,
and
that
was
the
next
agenda
item
that
I
had
on.
Here
was
what
do
we
want
to
do
with
the
docs,
because
I
think
initially,
the
kubernetes
dot
IO
website
had
a
pretty
big
guide
on
how
to
add,
join
Windows
nodes
to
it
and
then
that
got
removed
and
moved
into
the
Sig
Windows.
The
Sig
Windows
tools,
repository
and
I
think
we
should
go
and
Link
that
back.
A
D
Yeah
sure
so
I
basically
have
rewired
everything
through
the
API
server
now
and
seems
to
be
working.
I
have
not
been
able
to
test
this
on
Windows,
because
I
still
haven't
figured
out
how
to
update
the
API
server
on
Sig
windows
devtools,
because
so
far
everything
was
just
cubelet
and
Cube
cuddle,
and
so
it
was
easy,
but
now
I'm,
updating,
API
server,
also
and
I'm
I'm,
not
sure
so.
D
I
still
need
to
figure
out
how
to
update
the
API
server
on
Sig
Windows
devtools,
because
I
think
the
the
human
image
that's
already
pre-built
and
they
just
that's
what's
getting
used
there.
So
we
would
need
to
like
update
Sig
Windows
Dev
tools
to
also
build
the
API
server,
in
addition
to
like
cubeadm,
Cube
cuddle
and
all
those
other
things
and
use
it.
I
I
looked
at
it.
I
couldn't
figure
out
an
easy
way
to
do
it.
So
I
used
local
up
cluster
to
test.
D
All
of
this,
so
I
know
it
works
on
you
know
on
on
the
Linux
side,
but
the
windows
side
we
still
I
still
need
to
figure
out
how
to
how
to
test
it.
C
D
On
the
current
Sig,
Windows
devtools
environment
I
have
just
update
the
image.
Is
that
what
you're
saying
like
build
the
image?
Push
it
to
some
repo
of
mine
and
then
point
to
that
image?
Is
that
what
you're
saying
I
guess.
C
C
D
Yeah,
it
does
cubelet
cubeadm
q
proxy,
but
it
doesn't
do
control
plane
or
whatever.
The
API
is
over.
Oh.
D
C
Cool
I
mean
if
anything,
file
an
issue
and
I'll
take
a
look
at
it.
If,
if
there's
an
issue
there.
D
Okay,
all
right
yeah,
so
I've
done
it.
If
you
folks
have
some
time
just
take
a
look
about
there's
a
cubelet
thing
which
I
think
might
might
be
a
hack
but
I'm
not
fully
sure.
A
Oh
was
that
was
that
one
of
the
options
I
thought
it
was,
or
maybe
that
was
a
proposed
option
with
I.
Don't
know
how
to
do
that,
but
I'll
have
to
pick
up
that
email
that
he
sent
to
kadev
should.
D
D
Okay
did
I,
follow
all
his
instructions
correctly
or
did
I
mess
something
else
up,
and
so
that's
the
that's
the
main
PR,
but
on
an
aside
I
think
I
got
pinged
by
Machi
about
the
126
code
based
having
the
tested
Fabian
added,
oh
without
the
feature
actually
being
there
and
mate
was
like
you
need
to
take
this
out.
So
I
think
Fabian
had
to
go
ahead
and
revert
the
pr
and.
D
Yeah
so
I
I
think
Fabian
on
on
the
latest
stuff
to
see
I
think
what
we
can
try
and
do
is
you
know:
Fabian,
can
open
a
PR
and
make
it
Market
clearly
as
work
in
progress
or
as
a
draft
PR,
and
then
I
can
keep
pulling
in
the
test
from
that
PR
oud.
Okay,
that's.
What
I
think
is
the
best
way
forward
and
try
to
get
it
all
merged
in
one
shot.
D
Yes,
so
Fabian,
whenever
you
have
a
chance,
let
me
know
I
can
we
could
work
together
on
that
or
something
and
pull
that
in,
but
I
think
the
first
step
is
to
get
you
know,
Jarred
into
sort
of,
say:
okay,
you're.
A
On
the
right
track
for
the
new
for
the
API
server
or
the
API
updates.
D
D
C
D
B
E
A
So
I
I
I
think
that
just
add,
like
a
little
page,
that
links
to
the
Sig
Windows
Dev
tools
or
say
windows
tools,
Repository
we
could.
We
could
try
that
I
think
that
so
I
know
that
they
didn't
want
any
like
cni,
specific
details
in
the
kubernetes.io
page,
but
a
general
page
that
links
to
other
documentation
probably
be
accepted.
B
A
But
but
I
think
we
did
say
in
an
issue
that
we
do
plan
on
like
curating,
some
better
documentation
or
more
documentation
in
the
kubernetes
repository
which
we've
done
and
the
link
to
that.
A
So
yeah
I
think
it's
really
just
finding
the
best
spots
and
Signal
or
Sig.
Docs
is
probably
going
to
have
opinions
on
that.
So
maybe
just
try
opening
up
a
PR
to
add
this
back
right
here,
but
just
with
the
content
saying
go,
look
at
the
docs
and
say
when
the
tools
might
be
the
easiest
way
to
get
the
conversation
started.