►
From YouTube: Kubernetes SIG Windows 20220104
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
All
right,
hello,
everybody
and
welcome
to
the
january
4th
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.
Let's
start
off
with
some
announcements.
First
of
all,
well
happy
new
year's
everybody
hope
everybody
was
able
to
that
wanted.
A
A
I
think
just
this
week
they
archived
that
so
you
can
no
longer
send
messages
to
that
and
the
new
alias
is
dev
at
kubernetes
dot
io.
This
is
another
google
groups,
but
it's
managed
by
g
suite,
so
they
have
a
lot
more
control
over
things
and
there's
a
link
to
manage
like
the.
If
you
choose
to
not
get
emails
but
like
to
look
or
search
through
the
history,
there's
a
link
to
the
google
groups
to
manage
that
right.
A
Now
they
are
asking
people
to
not
join
the
new
group,
they're
auto
migrating
everybody
and
want
to
wait
for
that
to
be
completed
before
they
join
the
new
group.
But
if
you
have
any,
you
know
docs
or
mail
filters
docs
that
you're
sharing
with
add
the
new,
alias
mail
filters.
Add
that
new,
the
new
alias
to
that
to
get
that
all
set
up.
The
other
groups,
including
like
the
sig
specific
mailing
lists,
will
be
getting
migrated
in
a
couple
of
weeks.
A
I
think
they
want
to
see
how
how
this
works
and
how
all
their
migration
tools
and
everything
work
before
they
go
ahead
and
migrate.
Some
of
the
some
more
groups,
so
that
will
be
happening
in
the
next
couple
of
weeks.
But
for
now
it's
just
that
the
the
dev
alias,
if
you
have
any
questions,
there's
an
email
that
either
went
out
or
will
be
going
out
soon
with
how
to
contact
people
if
there's
any
questions,
but
it's
most
of
the
same
channels.
A
Just
slack
and
controvex
is
are
probably
the
best
points
of
contact
for,
if
you
have
issues
like
not
able
to
join
or
not
getting
messages
next
set
is
there's
a
tentative
proposal
for
the
124
release.
I
scanned
it
yesterday.
I
forgot
most
of
the
details,
but
the
important
thing
is
that,
right
now
the
proposed
enhancement
freeze
is
january
27th,
that
is
a
thursday
and
it's
in
a
couple
of
weeks.
A
So
that
is
probably
the
most
important
deadline
for
124
right
now,
since
we
are
tracking
the
number
of
enhancements
that
we'd
like
to
progress
in
124.
A
The
next
announcement
is
the
mirantis
container
runtime
20
version
2010
9
has
been
released.
This
has
a
couple
of
fixes
for
containers
not
started
or
not.
Cleaning
up
after
they're
stopped,
and
I
think
it
has
fixes
for
the
cdes
that
we've
discussed
here
before
for
people
new
here
mc.
The
marriage's
container
on
time
is
the
rebranding
of
docker
ee.
So
if
you're
still
using
docker
ee
on
some
older
well
120
percent
release,
if
you're.
A
Docker
e,
you
be
sure,
to
update
to
docker
or
the
mirantis
container,
runtime
2010
nine
at
your
earliest
convenience.
Yes,
it
looks
like
it
fixes
one,
the
two
cves
that
we
had
mentioned
here.
A
That
is
all
that
I
had
to
remember
to
add
for
the
announcements.
If
anybody
has
any
announcements
feel
free
to
raise
your
hand
or
just
talk
here,
if
not
we'll
continue
the
meeting.
A
Okay,
let's
get
let's
go
on
since
we
are
kind
of
entering
the
enhancements
portion
of
the
the
milestone.
I
wanted
to
spend
a
little
bit
of
time
in
here
to
discuss
what
enhancements
sigma
news
is
planning
on
working
on
in
124.
A
These
are
the
enhancements
that
we're
currently
tracking,
if
there's
any
other
enhancements
that
people
would
like
to
propose
and
work
on.
Please
let
me
know,
and
since
enhancements
are
now
opt
in
by
each
sig,
so
the
states
need
to
mention
to
the
enhancements
team
which
enhancements
that
they're
planning
on
tracking.
A
So
we
can
go
over
quick
status
and
I
just
want
to
make
sure
that
we
have.
We
know
what
we're
planning
on
working
on.
So
the
os
pod,
spec
fields,
yeah
ravi's
on
the
call
ravi.
Are
we
planning
on
taking
this
to
beta
in
124?
I
think
we'll
leave
so.
C
Yeah
so
in
124
we're
planning
to
make
it
better.
I
have
already
I
mean.
Yesterday
I
opened
a
work
in
progress,
enhancement.
Sorry
cap.
I
will
also
continue
making
some
changes
on
the
code
side,
but
I'll,
let
you
know
let
you
guys
know
once
it
is
ready
for
review,
but
it's
on
track.
C
None
technically
it's
just
updating
the
the
feature
gate
to
make
it
better.
At
this
point
of
time,
in
125,
we
are
going
to
make
some
changes
to
the
cubelet.
This
is
for
the
n
minus
2
support
that
that
we
have
been
talking
about
earlier.
A
Okay,
next
is
the
the
note
service
log
viewer,
arvind
and
session
comments.
I
believe.
B
E
Can
you
folks
hear
me
you're
very
quiet.
E
How
about
now
much
better
okay,
so
yeah?
I
spent
part
of
the
break
kind
of
looking
at
it.
Of
course,
I
got
distracted
a
lot
by
sigmund
node's
devtools,
because
I
was
using
that
environment
to
sort
of
test
this
feature
I
have
parts
of
it
working
now
I
have
you
can
go
to
a
particular
node
and
you
can
start
looking
at
the
log
files.
E
What
I'm
now
working
on
is
to
get
the
services
viewing
of
services
working
for
both
linux
and
and
windows.
I
also
am
having
trouble
getting
the
selector
type
options
to
to
work.
The
main
issue
here
is
is
oc
is
very
different.
The
oc
the
openshift
command
line
tool
is
very
different
from
cubelet
and
how
how
that
works
so
trying
to
get
the
code.
That's
there
and
oc
into
cubelet
is
the
struggle
that
I
think
christian
and
I
are
facing,
but
again,
like
I've
mentioned
this
before.
A
I'm
just
I'm
adding
a
note
so
especially
around
you
said
that
the
cube
ctl
changes.
A
Okay,
oh
yeah,
we
can
see
how
that
is.
Is
this?
This
might
be
a
good
thing
to
demo
in
one
of
the
next
coming
community
meetings
as
well.
E
A
Okay,
yep
sounds
good,
so
I'll
leave
it
as
we're
on
track
for
alpha
for
124
for
now
and
just
proceed
as
with
that.
As
the
plan.
A
Next
is
the
operational
readiness
spec.
I
think
I
mean.
B
Yeah,
so
the
operational
operational
readiness
is
reviewed.
We
got
this
in
the
end
of
the
year
and
I
think
we
are
waiting
for
the
pr
are
that
s2k
to
give
the
final
approval.
A
Yeah-
and
I
believe
that
I
think
we
reached
out
to
david
eads
to
do
the
pr
review,
but
I
will
try
and
reach
out
to
him
again
it's
better
to
get
there
like,
especially
the
pr
reprovers
who
look
at
many
different
caps
for
many
different
areas
of
the
project.
It's
best
to
get
their
approval
or
like
get
them
to
review
early
as
as
possible.
A
I
think
david
is
probably
the
most
familiar
with
sig
windows.
He's
been
the
pr
viewer
for
like
the
most
processed
containers,
the
node
service,
log,
viewer
and
other
caps,
but
we
can
ask
too,
it
doesn't
hurt
to,
I
think,
there's
a
slack
channel.
We
could
post
on
that
later
today
too,
and
to
see
if
anybody
wants
to
pick
it
up.
I
I
don't
I'm
not
a
huge
fan
of
how
they
ask
you
to
select
a
reviewer
and
put
it
in
the
ammo.
A
Yeah,
so
we
can,
we
can
play
around
with
that,
and
you
know
try
and
get
the
attention
and
just
change
it.
If
somebody
has
been
with
her
reviewers
interested.
A
A
A
There
are
a
couple
of
issues
are
like
not
issues
but
usability
things
that
we're
hoping
to
improve
and
have
it
have
the
changes
be
available
in
another
beta
release
brendan?
I
don't
do
you
want
to
comment
on
anything
on
this.
D
C
A
That's
all
that
I'm
tracking
does
anybody.
Is
anybody
proposing
any
new
enhancements
or
have
any
ideas
for
any
new
enhancements?
Not
we
can
continue.
A
Okay,
I
don't
have
anything
else
on
the
agenda
for
today.
Does
anybody
want
to
propose
any
agenda
items,
or
should
we
give
everybody
a
little
bit
of
time
back
or
go
into
the
pairing
session?
I'm
open
for
any
of
these
options.
A
Okay,
then,
I
think
we'll
stop
this
meeting,
I'm
going
to
stop
the
recording,
and
then
we
can
sort
out
the
pairing
session
that
folks
want
to
stay
on.
For
that,
thank
you,
everybody
for
attending,
and
I
hope
everybody
has
a
great
year
and
we'll
oh
yep,
just
kind
of.
Hopefully,
people
are
getting
back
into
this
thing
of
things.
Thanks.
A
Thanks,
I
am
going
to
leave
for
signode
at
10
they're
talking
about
the
signo
signate
enhancements,
and
I
want
to
say
for
that
all
right
like
I
want
to
be
there,
for
that.
Does
anybody?
Do
we
want
to
stop
the
recording?
Oh
yeah?
I
stopped
the
sharing
oops.