►
From YouTube: Kubernetes SIG Node 20201201
Description
Meeting Agenda:
https://docs.google.com/document/d/1j3vrG6BgE0hUDs2e-1ZUegKN4W4Adb1B6oJ6j-4kyPU
A
So
today
is
the
december
1st
and
it
is
the
first
signal
after
our
coupon
count.
I
believe
many
people
attended
cubica.
I
couldn't
this
year,
so
we
have
only
one
topic
proposed
for
today
and
let's
start
kick
out
today's
meeting
start
as
yoyo
sergey.
Do
you
want
to
update
our
peer,
the
the
poor
and
and
also
issue
status
here.
B
Yeah
so
as
expected,
it
was
a
short
week
in
u.s,
so
less
reviews
than
usual
and
it's
a
release
time.
So
only
most
of
them
are
just
except
one,
I
think
is
cherry
peaks
and
some
like,
like
c
advisor,
rendering,
for
instance,
some
something
that
needed
for
release.
B
Anyway,
we
a
little
bit
like
growing
on
number
of
prs,
but
hopefully,
after
a
release,
look
down
will
be
lifted.
We
can
see
more
prs,
be.
C
C
D
D
A
Okay,
so
so
we
are
going
to
so,
I
will
talk
to
fox
at
google
and
we're
going
to
nominate
someone
and
and
participate
and
also
provide
the
review
okay
for
another
anchor
yeah,
so
that
would
be
helpful
because
yeah.
This
is
why
I
signaled
we
tried
to
balance
right
so
now,
yeah,
okay,.
A
B
Tests
so
one
test
area
that
currently
is
failing
because
of
recent
pr,
I
believe
from
some
from
somewhere
from
continuity.
It's
a
container
d
tab
on
that
screen.
So
if
anybody
want
to
participate
and
fix
it,
we've
been
discussing
it
yesterday
on
sick
ci
group
as
well.
So
if,
if
you
want
to
participate
and
fix
it,
please
welcome
yeah.
Otherwise,
just
keep
keep
we'll
keep
posting
everybody.
Another
topic
is
we're
working
on
sick
on
a
sidecar
proposal,
team
wrote
a
small
document
outlining
the
idea.
B
Ultimately,
we
want
to
understand
what
the
fine
balance
be
for
side
cars
for
the
fine
balance
between
scenarios
that
we
want
to
support
and
flexibility
like
ultimate
flexibility
of
ordering
of
container
start.
So
if
somebody,
if
you
haven't
seen
this
document,
you
can
reach
out
to
me,
for
instance-
and
I
can
I
can
point
to
the
document.
D
Okay,
so
next
time,
oh
yeah,
if
you
have
time,
I
I
I
just
had
one
thing
in
mind:
I
was
gonna
propose
so
like
basically
have
sec
comp
enabled
by
default
in
to
make
the
clusters
more
secure
out
of
the
box
and
for
that
adding
a
featured
flag.
So
just
want
to
throw
this
idea
out
and
see
what
people
think
so
have
a
default
set
combinable
and
then
decide
on
what
the
profile
is
like
defined
at
the
kubernetes
or
we
go
to
a
runtime
default
and
slowly.
A
Yeah-
I
I
don't
know
we
talked
about
this
before
so
I
I'm
not
sure
other
people
last
time
have
constant
was
today
here.
I
personally
like
this
one,
but
there's
the
depend
on
then.
A
Let's
end
the
app
to
like
the
what
it
is
the
default
profile
right,
so
docker
have
some
default
profile,
and
but
a
lot
of
people
don't
agree,
that's
the
default
one,
and
even
that
one
don't
cause
some,
I
believe,
won't
cause
some
production,
existing
production
issue
regression,
but
some
people
have
concern
because
so
so
so
make
that
a
d
for
the
enable-
and
I
think
that
if
we
want
to
do
this,
I
personally
approach
this
one.
A
And
if
we
want
to
do
this
one,
we
may
have
to
call
out
of
some
announcement
earlier
so
and
but
but
I
think
they
introduce
a
flag
and
they
give
the
flexibility
to
disable
it.
Based
on
each
production,
that's
okay,
and
then
we
also
need
to
call
out
at
the
release,
notes,
make
sure
people
qualify.
It's
not
out
of
box
and
not
the
out-of-box
and
simply
upgrade
may
hurt.
Some
may
cause
some
regression
product
equation
for
some
people
for
some
vendor,
so
we
could
start
a
push
forward
on
that
direction.
D
I
can
yeah
I
can.
I
can
track
down
the
people
and
work
on
an
enhancement
for
that,
and
I
think
one
one
open
question
is,
as
you
pointed
out
right,
if
we
as
sig
node,
want
to
try
to
come
up
with
a
profile
that
we
call
as
a
default
that
everyone
can
use
or
if
they
want,
they
can
use
the
runtime
default
or
their
own
and
they
can
control
what
they
want
to
do
in
the
cluster.
But
if
we
have
like
kubernetes
default,
which
is
guaranteed
to
kind
of
work
with
cuban
discussions.
A
Yeah,
the
the
problem
is
because
docker
already
being
pre
exists
right
the
default
order,
so
for
us
actually
most
people
based
on
last
time.
That's
a
couple
years
ago
to
using
docker
default
actually
is
it
is,
is
not
much
risk
to
cause
the
product
in
the
question
to
us,
but
many
people
don't
like
that
one,
because
it's
don't
think
about
that.
Really
it's
misleading
and
to
some
degree.
So
because
it's
not
a
cover
many
thing,
so
they
want
to
define
some
kubernetes
default.
So
we
even
partner
with
the
container.
A
I
think
the
docker
and
continuity
community
try
to
come
up
some
like
the
holder
container
technology,
some
some
of
the
another
time
of
the
default,
but
that
project
didn't
move
forward.
So
I
just
share
with
you
here
and
I'm
okay
start
to
find
like
the
darker.
D
Default,
yeah
yeah
exactly
we
start
from
there
and
then
we
keep
on
making
it
adjusted
tune
it
and
make
it
better
over
time.
Right.
A
Yeah
I
yeah,
but
you
can
start
to
look
into
this
one
and
then
we
can
propose.
And
but
I
just
gave
you
a
pre-warning
because
we've
been
there.
D
In
the
past
yeah,
because
I
I
just
feel
bad-
that
there
are
cvs
that
come
out
and
the
only
I
mean
if
we
just
had
second
enabled
by
default,
then
some
of
those
wouldn't
be
an
issue.
A
Totally
totally
that's
exactly
yeah
that's
this
is
this
is
why
every
recently,
all
the
container
runtime
related
cve
come
out
guys
are
not
being
harmed,
it's
just
because
they
do
an
above
circle
by
default,
so
they
also,
they
also
have
come
up
their
own
default
profile
already.
So
this
is
why,
in
most
cases,
this
is
not
a
hard
gvisor
environment
yeah.
So
this
is
go
ahead.
D
Also,
we
added
like
a
flag
where
we
say
use
default
if
empty,
but
I
I
would
rather
that
we
do
it
in
signal
than
for
for
everyone.
We
defaulted.
A
D
A
A
A
A
So
looks
like
that's
all
for
today,
unless
anyone
have
some
new
time
yeah.
So
so
thanks
everyone,
and
so
everyone
got
45
minutes
back
and
have
a
great
week
week.