►
From YouTube: Kubernetes SIG Windows 20230502
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
B
A
Right
all
right
welcome
to
the
May,
2nd
2023,
sick,
Windows
community
meeting.
This
meeting
is
recorded
and
uploaded
to
YouTube.
So
please
add
here
to
the
CNC
at
Port
of
conduct.
If
anybody
is
wondering
what
the
code
of
conduct
is,
it
is
basically
be
nice
to
everyone
all
right.
So
let's
get
the
meeting
off
any
announcements.
I
don't
have
any
Mark.
Do
you
have
any
announcements.
B
A
Okay,
I
was
going
to
update
the
no
log
viewer
enhancement
just
to
reflect
whatever
happened
at
the
end
of
127.,
but
I
don't
plan
on
moving
it
to
Beta
in
128.
I.
Think
we'll
give
it
one
release
to
sort
of
you
know
what
we're
doing
in
the
openshift
side
is
we're.
Actually,
we've
take
we're
downstreaming
that
to
work
with
our
OC
ADM
node
log
command.
A
Also
so
we're
going
to
get
some
feedback
from
the
openshift
site,
so
I'm
not
planning
on
moving
into
beta,
yet
I'll
leave
it
for
an
alpha
for
One
More
release
and
then
in
129.
We'll
shift
it
to
Beta
is
my
is
my
plan.
B
A
Yeah
we
can
do
that
The
Next
Step
would
be
is
any
new
contributors
that
would
like
to
say
hello,
of
course,
no
pressure,
but
this
is
a
time
we
would
like
to
give
for
new
contributors
to
introduce
themselves.
A
All
right
don't
see
anyone
speaking
up,
so
we
can
move
on
to
the
agenda.
I
did
see
a
item
in
listed
under
the
future
list
about
whether
Cube
CTL
is
being
tested
for
Windows
using
end-to-end
framework,
so
I'm
not
sure
if
the
person
who
added
this
to
the
agenda
is
in
the
meeting,
if
not,
we
can
move
this
to
the
next
session.
We.
C
There
was
somebody
posted,
it
might
be.
The
same
person
in
Secret,
Windows
and
I
I
responded
and
showed
where
we
run
our
tests.
I
think
there's
a
few
Cube
CTL
ede
tests
that
we
we
run
but
I,
don't
know
any
of
the
specifics.
I
also
I
think
I
mentioned
to
reach
out
to
the
cube
CTL
maintainers,
because
they
would
probably
know
more
specifics
on
on
what
should
be
run
or
is
run.
C
A
B
B
Now
that
we
have
the
framework
for
running
the
unit
test,
this
could
be
a
good
place
for
like
to
a
good
help
on
an
issue
is
to
get
just
get
to
some
of
those
tests
running.
A
A
Don't
start
that
all
right,
we'll
move
on
to
announcements,
then
yeah
all
right,
128
announcements,
there's
the
no
log
wearing
announcement.
I
gave
a
brief
about
that
already.
The
plan
is
to
move
that
to
beta
in
129,
keep
it
in
Alpha
for
128.
B
Is
there
anything
to
do
around
getting
the
extra
like
I
thought
part
of
that
now
is
we
need
the
the
plugin
the
qctl
plugin?
Do
we
need
to
should
we
work
on
getting
that.
A
That's
a
good
point.
That's
a
good
point.
Mark
I.
Think
I
should
put
that
on
my
plate
to
do
I
I'm,
not
trying
to
take
the
work.
If
somebody
else
wants
to
jump
in
and
out
and
happy
to
take
contributions
there,
but
you're
right,
I
think
I
will
work
on
adding
a
Cube,
City
or
cucumber
plugin
for
that.
So.
A
Yeah
and
also
I
think
Fabian
was
working
on
some
end-to-end
tests.
We
should
try
and
get
that
merged
in
128.
A
Right
we
can
move
on
I
think
this
is
yours
right
Mark
about
the
root
FS
files
file,
size,
yeah,.
B
We
can
go
to
Alpha
so
for
people
who
are
new
here,
there's
a
little
bit
of
context,
and
the
context
is
that
when
you
start
Windows
containers,
it
creates
a
volume
like
the
scratch
volume
or
the
rudifest
volume
is
kept
at
20
Gigabytes
of
sized
and
that's
sometimes
not
enough
for
some
workloads
and
usually
what
we've
done
is
just
suggested
that
they
use
like
an
empty
their
volume
and
put
whatever
data
they
need
in
that
empty
their
volume,
because
they
can
specify
the
size
of
that.
B
We
just
need
to
figure
out
how
to
wire
that
up
in
in
kubernetes,
so
before
I
had
tried
to
talk
with
sigmode
about
using
the
container
resources
limits
and
ephemeral
storage,
and
there
were
some
reasons
which
I
highlighted
in
this
document
that
or
that
didn't
work
so
now
I'm
proposing
that
we
do
use
the
resources
that
limits.
That
storage,
which
is
used
in
a
number
of
other
kubernetes
API
objects,
but
not
on
for
container
resources,
because
I
think
that
that
makes
sense.
A
B
A
B
That's
a
good
point
yeah
and
that
once
we
figure
out
what
the
API,
what
like,
where
we
put
this
in
the
API,
the
actual
code
changes
to
publisher,
are
easy.
They're
already
done
and
I
think
I
linked
to
code
review
already
or
up
here
that
I
had
open
to
so
hopefully
we'll
just
work
with,
say,
storage
and
the
API
team.
To
get
this,
to
figure
out
where
to
put
this
yeah.
A
A
B
He
said
he
well,
he
didn't
commit
to
anything,
but
he
did
here's
what
he
suggested
use
of
ephemeral
storage
before
and
what
would
happen.
I
think
there's
reasons
why
we
don't
want
that.
So.
A
A
All
right
does
anybody
else
have
any
questions
for
Mark
on
this
announcement.
You're,
of
course,
welcome
to
review
it
and
leave
comments
on
the
pr
itself.
B
B
B
Two
big
or
like
the
two
enhancements
that
were
tracking
for
this
release:
I,
don't
know
if
there's
any
other
ones
we'll
have
to
ask
Jane
I
mean
if,
if
they've
had
time
to
work
on
the
operational
Readiness
work,
but
that's
also
out
of
trees,
and
that
is
important
for
the
enhancement
freeze
deadline.
A
A
Is
that
an
enhancement,
Mark
James
or
is.
C
It
yeah
it's
an
enhancement,
sick
notice,
driving
we're
just
making
sure
Windows
supports
it
when
they
turn
it
on.
B
Already
Alpha
and
then
they
slipped
beta
in
127
and
I,
don't
think
it
was
just
because
there
was
not
Windows
support.
I
think
that
they
had
some
other
issues.
A
Right,
so
that's
the
other.
Do
you
have
a
link
handy
for
that,
or
is
that
the
yeah?
That's
it
right
there,
okay.
E
Yeah
I
was
going
to
bring
that
up.
I'm
looking
for
reviews
from
Claudio
again
as
I
addressed
his
comments
on
the
pr
so
Claudio.
Please
take
a
look
when
you
get
a
chance.
No.
E
A
All
right,
that's
awesome,
yeah,
and
this
is
referencing
the
pr
that
it's
working
against.
A
All
right
so
I
guess
we
have
three
main
well,
the
no
log
viewer
there's
not
much
I
think
just
we
don't
even
need
external
reviews
for
that.
We
just
need
reviews
from
you
know,
mainly
you
Mark
I,
think
and
you
know
Fabian
or
someone
can
also
look
at
it.
Yeah
I
think
it's
a
root
file
size
that
is
going
to
be
big
for
us
and
we're
gonna
have
to
get
API
reviews
for
that
yeah,
that's
going
to
be
a
biggie.
B
The
actual
work
is
very
small,
so
but
I
think
just
figuring
out,
I
guess,
depending
on
where
it
goes
in
the
the
API.
It
could
be
some
work
in
the
API
too,
but
and
hope
that
that
one
is
yeah.
A
A
E
A
Did
but
yeah
all
right,
so
we
are
through
our
the.
A
We
have
one
more
item
which
is
commit
memory,
yeah.
C
I
just
added
this
one,
so
this
one
is
a
proposal
to
expose
commit
memory
right
now
we
expose
working
set
memory
and
on
Windows
the
limits
set
for
set
on
the
job.
Object
are
based
on
Commit.
So
if
you
make
a
request
for
memory
that
will
at
that
time,
when
you're
asking
for
that
commit,
it
will
throw
up.
C
If
you
don't
have
enough
memory,
and
so
this
can
cause
some
scaling
issues
on
the
edge
of
of
the
HPA,
because
it's
looking
at
working
set
versus
commit
and
so
we're
trying
to
get
this
exposed
and
moved
up
through
I,
just
throw
it
out
here.
Anybody
wants
to
take
a
quick
look
and
review
it.
We're
going
to
bring
it
to
sick
node
next
week
and
get
some
feedback
as
well.
C
So
this
is
just
the
cry
changes
that
the
information
is
actually
already
in
containerdy,
and
so
we
just
need
to
plumb
it
back
up,
and
this
would
eventually
require
some
changes
to
HPA
and
the
metric
server
and
other
components
there.
C
What
I'm
hoping
we'll
learn
a
sick
note
this
week,
yeah
I
I,
don't
know
if
we
do
or
or
not.
B
A
And
James
this
is
on
the
May
10th
call
right,
not
the
call
right
or
the
main
ninth
call,
not
the
call
right
after
this
meeting
no.
C
Yeah,
it
looks
like
they're
doing
a
retro
of
127
today,
so
I
thought
we'd
just
bring
it
next
week.
Okay,
all
right.
B
D
D
About
something
else,
yeah,
that's
the
one
Fabian
is
working
on
I,
don't
have
the
link
at
hand,
I.
B
D
It's
a
pretty
straightforward
implementation.
I
think
there
are
a
couple
of
comments
on
the
pull
request,
but
pretty
much
should
be
easy
to
merge
a
lot
easier.
It's
a
lot
of
things
are
on
par
with
how
things
work
on
Linux,
so
should
be
any
contestations
conversations.
D
The
future
actually
merged
last
cycle
and.
A
B
A
B
B
Or
yeah
something
so.
A
Right
so
I
don't
see
any
more
agenda
topics.
If
there's
nothing
else
to
discuss
I
can
we
can
give
everybody
back
five
minutes.