►
From YouTube: Kubernetes SIG-Windows 20211005
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
have
a
pretty
short
agenda
today,
so
if
anybody
has
anything
that
they'd
like
to
discuss,
feel
free
to
put
it
in
the
chat
or
raise
your
hands
or
end
it
to
the
agenda
afterwards.
I
mostly
just
wanted
to
give
a
couple
of
announcements
regarding
kubecon
next
week,
we'll
cancel
the
sig
windows
community
meeting,
so
people
can
attend
more
of
the
activities
for
kubecon
north
america,
but
if
anybody
has
anything,
they
want
to
discuss
just
bring
it
up
in
slack,
and
we
can
work
around
that.
A
Then
I
did
highlight
the
two
sig
windows
talks
in
case
anybody's
interested
in
those
the
first
one
is
the
sig
windows
maintainer
series
talk,
and
for
that
we'll
be
focusing
on
showing
demos
of
the
host
process
containers
and
that
is
setting
up
a
cluster
with
cluster
api
using
bringing
in
cube
proxy
and
the
cni
via
host
process
containers,
and
then
there's
a
demo
and
a
lot
more
details
about
the
dev
environments
that
a
lot
of
folks
have
been
working
on
that
is
on
wednesday
october
13th
at
11
a.m.
A
A
So
if
anybody
is
interested
in
either
of
those
topics
be
sure
to
check
out
the
talks
either
virtually
or
in
person,
if
you're
attending-
that's
really
all
I
had
today,
I
don't
know:
does
anybody
have
anything
they
want
to
discuss
or
should
we
give
everybody
a
bunch
of
time
back
or
move
into
the
the
pairing
session
early.
B
All
right,
can
you
hear
me
now?
Yes,
yeah,
for
some
reason,
zoom
always
resets,
my
my
microphone,
irrespective
of
what
I
do,
I
I
just
want
to
call
out
that
I
did
write
up
a
little
doc
about
the
projector
volume
issue,
so
I've
added
it
to
the
chat
here
suggests.
I
I
I
just
got
an
lgtm
from
david
eads,
so
he
seems
to
be
happy
with
what
I've
written
up
there.
I
would
like.
B
I
would
like
someone
with
you
know,
either
mark
or
james
or
someone
with
more
windows
background
than
both
me
and
david,
to
also
take
a
look
and
make
sure
what
we're
saying
there
is
accurate,
and
if
not,
you
know
we
can
make
changes.
I
I
think
this
goes
back
to
our
plan
of
documenting
this
somewhere
and
saying
what
the
expected
behavior
is,
and
you
know
so
that
it's
that
in
the
dark,
so
that
people
don't
use
projected
volumes
and
assume
that
things
are
are
working
as
expected
in
the
in
the
linux
land.
C
C
A
B
No,
I
think
I
just
added
it
to
our
repo
as
a
starting
point.
I
think,
okay,
once
we
finalize
this
right,
I'm
planning
on
getting
it
into
the
openshift
docs,
but
we
should
get
it
into
the
kubernetes
docs
and
I
think,
was
it
mars
or
was
it
brandon
who
was
talking
about
whether
they
should
also
put
it
in
the
microsoft
dock
somewhere.
B
Yeah,
I
I
don't
know
whether
we
can
take
this
and
just
move
it
to
the
kubernetes
dots,
but
I
think
parts
of
this
can
be
extracted
and
moved
into
the
kubernetes
results,
because
I've
also
called
out
some
openshift
specific
stuff
that
we
did
to
sort
of
work
around
this
issue.
Okay
and
the
other
call
we
might
need
to
make
is
if
a
user
has
a
pod
with
runner's
username
set
and
run
as
user
set.
B
B
The
only
place
I
think
where
users
might
be
affected
is
if
they
are
running
on
a
cluster
that
has
some
admission
controller,
that's
just
applying
run
as
user
without
carrying
whether
it's
a
windows
or
the
next
part,
though
those
users
would
be
affected.
So
that's
something
we
need
to
think
about.
So.
A
I
think
that
this
is
actually
going
to
get
blocked
by
ravi's
changes
to
add
the
os
field.
I
do
remember
seeing
some
validation
that
if
the
os
field
was
set
to
windows
and
and
a
number
of
fields,
including
the
run
as
user
field
were
set,
the
pod
will
get
rejected
at
admission
time.
Oh
that's
great!
Then
then
we
we
don't
have
to
worry
so
much
about
that
scenario.
That.
B
C
B
I
mean
we
still
have
the
problem
of
the
permissions
not
being
said
correctly,
but
that's
sort
of
you
know
a
separate
thing
with
with
the
windows
set
right,
all
right,
I'll
I'll
post
this
on
on
slack
also
so
that
moz-
and
you
can
forward
this
to
your
folks
in
microsoft-
awesome
yeah.
I
think
this.
A
Thank
you
for
sharing.
Does
anybody
else
have
anything
to
discuss.
A
A
I
probably
can't
leave
the
pairing
session
because
I
was
going
to
join
sig
node.
Does
anybody
want
to
stick
around
and
do
the
pairing
session?
Should
we
cancel
for
this
week?
A
Hey
ross,
have
you
been
able
to
like
see
if
there's
any
like
find
any
time
to
start?
Looking
at
the
cluster
testing
of
those
tools,
I
have
not
had
the
time
yet
it's
on
my
list.
It's
just
I'm.