►
From YouTube: Kubernetes SIG-Windows 20220802
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
Okay,
let's
get
started
announcements
only
announcement
I
have
is
that
code
freeze
is
today
or
tomorrow.
A
On
what
time
zone
you're
in,
I
think
it's
like
8,
00
p.m,
pst
so
yeah.
If
there's
anything
that
must
get
merged.
Please
let
me
know,
I
know
a
lot
of
the
node.
Reviewers
are
actually
out
all
week,
which
is
kind
of
unfortunate.
A
If
so,
if
there
is
anything
that
requires
an
odor
viewer
that
might
be
harder
to
get
in,
but
I've
seen
a
couple
of
things
merge
in
the
last
day
or
two,
but
if
there's
anything
else
yeah,
please
let
me
know
just
raise
it
on
slack
and
mention
me
and
I'll
try
and
get
that
in.
A
I
think
that
one
other
announcement
that
I
can
add
is
that
the
I
think
they're
finalizing
the
q
con
north
america
schedule.
The
schedule
should
be
up
sometime
tomorrow
or
possibly
the
next
day.
So,
if
anybody's
interested
to
see
what
kind
of
talks
are
got
accepted,
you
can
check
I'll
add
a
link
to
the
agenda
after
this
too.
A
Nope:
okay:
next,
we
can
give
a
little
bit
of
space
to
have
any
new
contributors
introduce
himself
if
they
want
totally
optional.
But
if
you
want
to
share
what
you're
working
on
or
what
you
hope
to
get
out
of
joining
the
community
meeting,
it's
always
appreciated.
A
All
right,
I
don't
see
anybody,
so
we
can
go
on
to
the
agenda.
First
agenda
item
that
I
had
was
actually
since
rfin
since
you're
here
and
sebastian.
Should
we
talk
for
a
minute
about
the
operational
or
not
the
operational
readiness,
the
node
service
log
viewer
enhancements?
Is
that?
Are
we
going
to
just
push
that
to
126.
C
Yeah
I
just
got
back
for
my
long
break
yesterday.
Over
the
weekend
I
started
to
work
on
it
again
and
I
addressed
some
of
jordans
and
tim's
comments,
but
yeah
we
would
have
to
push
it
out.
I
just
I
was
I
had
like
unrealistic
expectations
on
on
my
time
in
the
last
few
months.
C
Yeah
I
couldn't
get
much
done
on
it,
but
I
think
my
tack
is
going
to
be
to
just
get
it
finished
and
reviewed
and,
unlike
last
time,
when
I
kind
of
took
a
took
a
break
once
it
didn't
make
it
in
since
I
just
got
back,
I'm
not
going
to
take
a
break,
I'm
just
going
to
try
and
you
know
slam
it
through,
and
I
I
really
want
to
thank.
I
just
saw
a
pr
from
someone
fabian.
C
C
Once
I
make
once
I
update
the
api
to
use
the
new
query
field
instead
of
the
service
and
path
field,
basically
the
service
and
path
will
collapse
now
into
query
and
it'll
become.
Like
I
don't
know,
I
still
haven't
figured
that
out.
It's
supposed
to
be
some
kind
of
magic
that
tim
wanted,
that
you
kind
of
sense
whether
you're
asking
for
a
file
or
a
service,
and
then
you
you
either
use
the
file
server
to
present
it
or
use
the
http
server
with
the
journal
logs
to
present
it.
C
So
I'm
still
working
through
that.
So
I
think
we
would
then
need
to
modify
the
end-to-end
test
to
use
that
new
api,
but
that's
the
status
on
that.
D
A
Well,
yeah
anyways,
thanks
for
the
update
and
welcome
back.
Thank
you
folks.
Does
anybody
have
any
questions
or
anything
else
to
add
how
about
this.
A
Nope.
Okay.
Next
agenda
item
was
some
folks
from
the
release
team
posted
in
slack.
Today,
too,
they
were
asking
if
there
were
any
major
themes
that
sig
windows
would
like
to
include
in
the
release.
Notes
I'll
be
working
with
some
of
the
other
leads
on
putting
that
together.
A
But
if
anybody
has
any
things
that
they'd
like
to
have
called
out
in
the
125
release
feel
free
to
either
add
them
to
the
major
themes,
doc
that
was
linked
in
the
slack
channel
or
you
know
mention
it
inside
windows
and
we
can
make
sure
to
get
that
added.
A
I
think
we'll
call
out
the
pod
os
fields,
and
we
talk
a
little
bit
about
the
perfwork
that
got
added
and
other
things
like
that,
but
feel
free
to
reach
out.
If
done
anything,
possibly
the
operational
readiness
work
too.
I
think
that's
in
a
state.
That's
we've
seen
some
demos
of
that,
so
that'd
be
good
to
call
out
to
get
some
more
eyes
and
momentum
behind
that.
A
Mike
did
you,
I
think
you
said
in
slack
and
earn
a
dm
that
you
wanted
to
give
an
update
on
cni
container
d.
Do
you
want
to
do
that
now.
D
E
D
A
Okay,
so
I
I
think
that
I
I
misunderstood
that
I
think
he
was
just
saying
here
to
answer
any
questions
so
can
remove
that
yeah.
Does
anybody
have
anything
else
they
want
to
discuss?
I
see
blooper
mirrors
on
here
and
I
know
there's
been
some
conversations
in
slack
about
documentation
for
getting
windows
cni
set
up
for
as
part
of
joining
clusters
to
the
nodes.
I
don't
know
if
people
want
to
talk
about
that,
for
a
few
minutes
might
be.
D
F
A
Yeah,
so
I
think
we
talked
a
little
bit
at
slack
and
the
the
old
page
was
against
some
of
the
current
guidelines
for
the
websites,
but
we
can
try
rehosting
that
on
sig
windows
tools.
That's
something
that
if
nobody
has
any
objections
to,
we
can
try
and
put
together,
like
some
some
readmes.
F
Yeah,
a
plus
one
for
me.
Basically,
I
was
closing
issues
at
the
website
that
marking
there
was
a
duplicate
of
what
existed
issue
that
we
have,
and
basically
the
issue
covers
that
the
problem
that
users
don't
know
how
to
add
the
cli
part
yeah.
I
think
it
makes
sense
to
even
even
if
you
link
to
some
sort
of
placeholder
with
you
know
not
the
full
guide.
I
think
the
website
people
might
be
okay
with
that,
but
I'm
not
sure
because,
as
you
may
know,
they
are
kind
of
strict
what
we
link
externally.
A
Okay,
yeah
yeah.
That
makes
sense,
I
think
we
can.
We
can
try
and
see
what
the
folks
say
about
that
after
yeah
after
code
freeze,
I
think
there'll
be
more
bandwidth
from
people
to
to
do
that
and
we
can
just
I
I
think
one
of
the
suggestions
was
linked
to
an
issue
that
we
had.
A
I
think
it'd
probably
be
a
little
bit
better
to
at
least
start
a
markdown
doc
in
that
repository,
with
maybe
one
example
and
then
link
to
that,
and
then
we
can
just
iterate
on
that
markdown
document
rather
than
linking
to
an
issue,
because
the
issue
is
kind
of
both
an
outline
of
how
we
wanted
it
to
work
and
some
links
to
some
ad
hoc
docs,
but.
G
You
mean
hosting
the
markdown
into
the
see
windows
stores,
repository.
G
I
think
I
think
that
fabian
can
give
a
hand
on
that,
because
he's
been
trying
qubit
dm
as
well,
and
he
encounters
a
couple
of
issues
and
he
pretty
much
figure
out
how
to
deploy
all
the
necessary
bits
for
windows.
And
I
think
you
can
give
a
helping
hand
on
that
set
of
things.
A
Awesome
yeah.
That
would
be
that
would
be
helpful,
there's
a
discussion
and
slack
that
or
that
I'll
link
to
after
the
let
me
see
if
I
can
find
it,
and
we
can
continue
to
talk
in
there
to
drive
that.
Where
is
it.
F
Yeah,
I
think
it
might
have
been
a
good
idea
to
actually
keep
the
old
page
until
we
have
the
new
documentation,
even
if
it's
external,
but
I
to
by
the
city.
The
recommendation
was
from
the
sick
dogs
people
to
unify
the
pages
or
something
like
that,
which
I
don't
think
it
was
the
right
time
for
it.
But
maybe
I
don't
have
the
full
context.
A
Yeah,
we
were
doing
some
pretty
substantial
overhauls
to
a
lot
of
the
windows
documentation
and
as
part
of
that,
we
were
updating
the
the
docs
for,
like
the
cuba
dm
work
that
we
had
and
the
basically
the
docs
reviewers
said
all
of
the
content,
for
that
the
old
page
was
violating
their
like
clauses
or
like
that,
their
rules
for
documenting
how
to
configure
third-party
solutions,
and
so
they
had
asked
to
remove
all
of
that.
F
A
H
Yeah,
there's
there's
been
several
community
members
who
have
come
to
that
particular
issue
and
have
kind
of
put
their
walkthroughs
together
on
their
own
repositories,
and
so
maybe
we
can
reuse
one
of
those
or
have
them
contributed
in
some
way.
If
they're
interested.
A
A
And
and
container
d,
and
things
like
that
too,
I
know
that
yeah
calico
has
started
to
add
their
own
documentation.
I
think
I
think
the
the
the
reasoning
or
the
logic
behind
what
the
sig
docs
folks
were
saying
was
like
things
like
how
to
set
up.
A
Calico
should
be
documented
on
in
in
the
calico
docks,
and
so
that's
why
they're
against
hosting
kind
of
setup
steps
for
third-party
projects,
but
at
the
same
time
windows
is
kind
of
in
a
weird
state
where
a
lot
of
those
solutions
don't
have
the
windows
docks,
but
things
can
work
with
windows.
So
we'll
try
and
do
this.
F
Well,
there's
also
this
special
tag
on
the
website.
The
website
uses
hugo
a
hugo.
Has
this
like
attack
option
to
basically
inform
users
that
this
particular
section
of
the
docs
is
about
the
third
party
solution?
We
already
do
this
in
a
few
places,
so
yeah,
that's
that
was
potentially
one
option
to
consider.
A
Okay,
yeah:
I
think
we
can
work
on
this
a
little
bit
moving
forward
and
yeah
fabian
if
you
wanna,
to
help
out
here
feel
free
to
to
do
that.
That
would
be
appreciated.
E
I
kpng
update
is,
I
think
we
will
work,
merge
windows
this
week
and
once
we
finish
merging
windows,
I'm
going
to
work
with
dan
winship
from
sig
network
on
friday
to
finish
off
most
of
the
cap.
E
So
thanks
to
dimitri
for
finishing
and
polishing
it
off
and
testing
it
in
a
few
different
environments.
E
E
Some
help
help
you
all
with
some
of
the
other
stuff.
That's
going
on
or
they'll
accept
the
cap
and
I'll
continue
trying
to
harden
that
windows
proxy
and
the
other
things
in
there
that
we
need,
and
then
we
will
actually
have
a
an
idiomatic
windows
proxy,
but
I
really
hope
that
that
kept
does
get
accepted.
Of
course.
So
that's
the
update
on
the
windows
proxy
kpng
by
the
end
of
the
week
folks
should
be
able
to
merge
it
and
test
it
from
the
kpmg
repository.
We'll
see.
G
Hypothetical
hypothetical
question:
if
they
do
reject
kpng,
can
we
reject
the
rejection.
D
A
I
also
saw
that
vinicius
had
a
comment
in
the
chat
vinicius
asked
about
the
previous
topic
he
said,
or
they
asked
if
their.
A
If
the
problem
is
lack
of
intent,
documentation
on
how
to
play
windows
notes
into
a
kubernetes
cluster,
why
don't
we
use
the
windows
containers
docs
for
that,
and
I
think
the
one
of
the
issues
here
is
that
there's
many
different
cni
solutions
that
can
be
used
and
that
cni
solution
must
be
the
same
for
like
all
for
the
linux
and
the
windows
nodes
in
there
and
there's
a
lot
of
there's,
potentially
a
lot
of
configuration,
that's
required,
especially
depending
on
what
kind
of
environment
you're
deploying
into
so
I
don't
know.
A
I
don't
really
think
that
the
windows
containers
documentation
is
appropriate
for
all
all
of
that,
and,
as
mentioned
before,
like
the
best
solution
is
that
to
have
each
one
of
the
cni
maintainers
the
the
projects
document?
How
to
do
that?
We
can
provide
some
references
to,
but,
if
need
be,
we
can
figure
out
where
to
doc
like
where
to
document
it.
Until
that
happens,.
D
Mark
do
we
have
like
a
list
of
those
the
network
plugins
that
have
documentation
on
a
website
the
websites
or
do
not
have,
I
guess,
most
importantly,
do
not
have
instructions
to
support
windows.
D
E
D
H
What
I
thought
yeah
it
was
using
the
docker
and
wins
oh
good
times,
that's
that
was
yeah
which
which
had
challenges,
particularly
if
you
try
to
use
it
for
container
d,
yeah
yeah
and
that's
when
we
tried
to
update
that
to
use
calico.
That's
when
I
mean
it's
hard
to
use
container
d.
H
B
I
just
wanted
to
add
a
comment
regarding
the
documentation
and
I'm
not
expecting
a
solution.
Here
is
just
passing
on
comments
that
I
heard
from
other
people,
so
I
come
from
the
upside,
I'm
not
a
developer,
and
I
listen
to
a
lot
of
folks
that
are
getting
into
kubernetes
and
today,
if
you
look
for
either
microsoft,
documentation
or
kubernetes
documentation
like
someone
that
is
getting
into
kubernetes
and
trying
to
understand
how
it
works,
they
won't
be
successful
in
deploying
windows
that
period
right.
B
There's,
a
bunch
of
places
that
you
have
to
look
into
networking
is
all
over
the
place.
I
can't
I
can
get
a
windows
note
to
run
and
I
look
for
the
documentation,
multiple
places,
and
I
have
support
from
you
folks
in
trying
to
get
that
to
work.
So
I
get
my
feedback
for
this
group
is.
B
Maybe
we
should
look
into
a
way
to
get
folks
that
are
not
familiar,
not
so
familiar
with
kubernetes
as
you
folks
are
into
getting
started
and
then
pointing
them
into
more
advanced
documentation
that
is
available
on
whatever
cni
places
or
other
companies
places.
B
So
at
least
people
can
get
started,
understand
how
it
works
start
using
windows,
containers
on
kubernetes
and
then,
as
they
move
into
production
environments,
try
to
understand
more
complex
environments
and
scenarios.
They
can
look
for
more
advanced
documentation,
but
so
that's
my
feedback
based
on
customer
interactions
that
I
had
lately.
A
How
do
I
say
like
the
hurdle
yeah
like
so
I
or
or
what's
the
appetite
for
setting
up
trying
to
set
up
like
and
join
cluster
machines
to
a
cluster
kind
of
manually,
because
I
would
kind
of
expect
that
people's
first
introduction
to
kubernetes
and
windows
containers
is
to
either
use
a
managed
kubernetes
service.
That.
B
Yeah,
so
there
are
two
things
that
I've
heard
in
conversations
with
some
folks:
the
first
one
is
when
they
are
using
managed
kubernetes,
they
get
how
it
work
and
they
they
it's
so
much
simpler
right.
But
then,
when
it
comes
to
troubleshooting,
that's
where
they
get
into
the
weeds
of
okay.
But
then
what
are
the
things
that
the
managed
service
did
in
the
background?
So
they
try
to
understand
that
a
little
bit
better
and
then
they
want
to
deploy
a
windows
node
by
hand
on
a
not
not
managed
environment.
B
No,
that
that's
great,
I'm
not
a.
I
was
not
aware
of
that.
So
I'm
gonna
look
for
more
details
on
that.
So
thanks
yeah.
E
B
Yeah
that'd
be
great
perfect.
The
other
scenario
real
quick
is
people
start
with
the
managed
service,
but
then
they
want
to
go
into
a
certification
and
then
they
go
back
to
the
same
scenario
of
like
well,
I
want
to
see
what's
happening
in
the
background
and
under
the
hood.
I
I
made
the
pr
I
think,
mark
you
assigned
it,
I'm
not
sure
about
it,
and
that
was
the
main
issue
that
I
had
using
the
mark.
Adding
the
windows,
not
the
cluster,
because
I
used
deprecated
some
deprecated
flags
and
it
wasn't
actually
working
for
me.
H
The
so
to
speed
up
the
that
whole
process
of
booting
dev
tools.
We
build
a
container
or
we
build
a
vm
image
from
image
builder,
using
some
work
that
ameem
did
for
virtualbox
and
that
particular
script
got
fixed
in
image
builder,
but
it
didn't
get
fixed
because
we
were
using
an
older
version
of
the
that
the
image
built
from
image
builder.
So
that's
kind
of
where
that
came
from.
I
think
we
were
looking
into
that
with
auburn
as
well
about
a
month
ago,.
C
Yeah,
I
think
so
so
fabian
this
the
fix
that
you
have
done
right.
What
ends.
E
C
C
I
A
C
I
think
we're
talking
about
two
different
ones.
I
think
now
I
see
it.
It's
sig
windows
tools
that
fabian
has
added
that
vr
to
sorry.
So
I
think
that
the
idea.
A
So
we
should
make
sure
that
those
are
updated
too,
but
then
sig
windows,
dev
tools,
you
probably
used
the
same
scripts
and
they
may
have
gotten
updated
in
one
spot
or
not.
I
think
I
think
either
way.
I
think
it's
yeah
good
conversations.
I
think
we
do
need
to
work
on
the
documentation
for
joining
your
own
club
nodes
to
a
cluster,
so
we
can.