►
From YouTube: Kubernetes SIG Windows 20191105
Description
Kubernetes SIG Windows 20191105
A
All
right,
thank
you.
Everyone
for
for
joining.
This
is
November
the
fifth,
and
this
is
the
weekly
sig
windows
meeting.
So
please
be
sure
that
you
adhere
to
the
kubernetes
and
CN
CF
code
of
contact
and
conduct
and
which
basically
means
don't
be
a
jerk,
so
I
think
there's
a
number
of
people
out
this
week,
because
both
a
VM
world
and
the
Microsoft
ignite
event
are
going
on,
but
we
still
have
code
freeze
coming
up
on
next
Friday
prior
to
the
cube
Con
event.
A
A
B
C
B
Quick
update
from
on
the
container
decide
like
Justin
from
looking
at
that.
That
was
something
that
was
missing
initially
and
I.
Believe
Sean
already
put
in
the
changes
needed
on
the
CRI
API
site.
You
pass
the
red
speck
along
so
once
that
container
did
side
starts
like
as
part
of
one
thing:
Emily,
yes,
and
one
suggestion
is
ready.
With
the
container
decide
changes,
we
can
do
what
I
do.
Thank
you,
nerdy
as
well.
B
A
B
A
A
But
basically
there's
two
different
places
we
could
put
it.
It
just
comes
down
to
two
really
api
cleanliness.
It's
not
really
functionally
any
different.
We
just
need
someone
to
step
up
and
review
this
from
a
sig
note
standpoint,
so
we
can
get
this
merged
and
then
let
the
container
d
developers
go
ahead
and
vendor
that
in
and
start
implementing
it
over
on
the
windows
side.
A
A
The
test
pass
is
running
with
the
two
final
networking
modes
are
very
continuing
to
run
on
test
grid
and
so
we're
still
fixing
a
couple
of
the
bugs
there.
But
we're
about
to
move
this
over
to
the
okay.
So
those
test
passes
we're
running
on
on
a
fork
over
and
J
Terry
75
and
then
so
we'll
be
bringing
up
a
test
pass
on
the
main
branch
which
is
container
D,
I'm
/cr
I
this
week
and
then
we'll
be
checking
for
any
missin
fixes
that
haven't
made
it
over
to
the
master
branch.
Yet.
A
You
find
this
and
so
I've
got
the
list
of
open
bugs
and
everything
still
tracked
over
under
this
under
this
project.
That's
there,
but
we've
got
some
pr's
open
that
that
I'll
be
reviewing
this
week
and
then
we'll
you
know,
keep
pushing
on
it's
going
to
be
tight,
because
this
has
been
a
short
milestone.
But
but
overall
looks
like
things
are:
are
on
track
to
work.
A
A
A
B
C
A
Or
just
start
a
similar,
similar
project,
I
think
one
of
the
difficult
things
about
running
as
a
daemon
set.
Is
that
because
we
don't
support
privileged
containers,
it's
going
to
be
difficult
to
get
a
lot
of
the
data,
that's
needed
from
something
running
the
daemon
set,
and
so
it
would
need
to
be
installed
on
the
node.
Instead
in
order
to
get
things
like
crash
report
logs
from
the
node
and
look
at
you
know,
things
like
host
network
and
in
storage,
metrics.
A
A
A
So
maybe
we
could
start
discussing
that
next
week,
enlist
a
few.
Let's
see
if
we
start
getting
getting
feedback.
We've
also
got
a
chance
to
get
some
feedback
on
this
at
cube
con
as
well
and
within
the
sig
windows
talks,
and
so
I'll
start
a
notes
section
here
in
this
stock.
So
we
can
at
least
get
some
thoughts
in
one
place.
A
A
Okay,
well
I
guess:
if
anyone
has,
it
has
other
topics,
be
sure
to
bring
over
over
to
slack
as
usual
and
if
you've
got
PRS
needing
review.