►
From YouTube: Kubernetes SIG Node 20181002
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).
B
B
The
main
reason
I
wanted
to
meet
with
various
sakes
was
to
bring
point
your
attention
that
the
whole
release
cyclists
super
shot
this
time,
considering
it's
the
last
release
of
the
year
and
we
have
to
keep
cons
and
the
holidays
and
everything
rolling
in.
So
we
just
have
about
10
weeks
to
wrap
the
entire
cycle
and
we
are
targeting
a
release
date
of
December
3rd.
B
That
said,
I
just
something
that
they
are
not
formally
doing,
but
we
are
trying
to
talk
to
the
different
sects
and
have
kind
of
rally
around
is
to
make
this
release
morpha
stability
release,
rather
than
taking
in
large
chunks
of
new
features
going
into
alpha
for
the
first
time.
This
is
mainly
to
de-risk
as
much
as
possible
and
to
keep
the
release
on
track.
B
So
while
we
why
we
are
not
making
it
very
formal,
my
asked
to
this
sig
leads
and
to
the
feature
owners
is
to
try
and
try
and
focus
more
on
stability
fixes
for
this
release,
which
could
be
around
landing
things
that
were
differed
previously.
All
focusing
on
bug
fixes
locks,
long-standing
bugs
that
you've
always
wanted
to
get
fixed
or
increasing
the
test
coverage
for
your
existing
features.
B
So
again
we
will
start
the
formal
feature,
collection
process,
next
Monday,
so
Kendra
Casa
features
lead
he'll,
be
thinking
with
you
guys
more
closely,
but
I
just
wanted
to
meet
beforehand
and
yeah,
ensure
that
I
drive
home
this
point
that
the
release
is
super
shot
and
I
just
wanted
your
help
in
future
planning.
Accordingly.
So
any
questions
around
this.
C
I'll
just
add
one
more
thing
on
here,
so
just
looking
at
the
the
features
repo,
there
are
31
open
features
right
now,
some
of
them
are
tagged
112
still,
some
of
them
are
tags
from
milestone
113.
If
you
are
an
owner-
and
you
know
that
you
have
high
confidence,
go
ahead
and
tag
it
for
this
release.
If
not,
let
me
know
I
can
tag
it
for
you.
If
not,
then
I'll
be
bugging
the
hell
out,
everybody
starting
next
Monday.
A
A
F
A
The
most
is
first,
this
thing
is
too
efficient,
another
hard,
eight
and
implement
that
one.
So
we
have
the
design
and
for
training.
Mascota
tophane
is
believe
so
and
the
most
token
like
that
then
expiry.
So
we
can
finish
at
work
and
this
court
I
work
with
Ramona
to
the
p0,
and
then
we
are
going
to
finish
this
one
to
achieve
our
skin
vehicle.
So
another
one
is
the
reflection
of
the
know
that
obstacle
comes
on
them
and
all
the
dependency.
A
H
Yeah
sure
so
we're
continuing
the
stability,
push
and
I'm
working
on
getting
the
test.
Prs
they're
needed
merged,
so
one
of
the
first
ones
was
actually
emerged
and
that's
that
was
needed.
So
we
could
point
to
the
appropriate
windows,
container
images
and
then
the
next
one
that
we're
using
for
actually
scheduling
the
periodic
jobs
on
the
juror
is
in
review
right
now
and
then
once
that's
merged
and
we
just
need
the
ones
on
the
updates
in
prowl
and
test
grid
subway.
H
A
H
H
A
Okay,
so
team
and
I
have
the
of
nine
discussing,
and
so
we
go
over.
All
those
random
casts
the
pending
items
and
there's
the
huge
amount
of
those
things
and
amount
all
those
kind
of
things
we
identify.
We
want
to
give
you
the
cue
for
it's
a
short
holiday
and
also
there's
the
to
cubicle
coming,
and
so
we
identify
one
what
it
is
p1
it
is
the
design
and
implement
Rankine,
awhile
steadily
incremented
for
sure,
but
I
catch
them
so
so
in
and
also
we
identified
one
more
item
in
ears.
A
We
hope
someone
from
the
community
can
want
to
hear
to
take
over
its
dynamic
Amira
gesture
of
operation
addition
of
that
time,
for
example,
for
Windows
and
the
rent
time,
and
also
for
the
for
the
crowd.
So
you
want
so
so
so
all
those
kind
of
if
you
want
to
have
the
special
ocular
features-
and
you
want
probably
different
runtime,
and
so
so,
even
without
those
kind
of
things
miss
you
could
cast,
the
enemy
could
be
manually
set
up
those
kind
of
things.
A
So
we
make
this
a
substitute,
but
oh
there's
many
people
asked
about
how
we
make
this
is
dynamic
register,
and
so
that's,
why
I
promote
this
to
the
here
and
ask
a
Mac
as
the
happily
there
then,
the
next
one
and
I
never
they
use
the
namespace
to
support
that.
Do
you
want
to
talk
about
this?
One
yeah.
G
I
mean
so
this
is
a
this
is
a
indicated
on
just
getting
final
API
review
agreement
we'd
like
to
keep
trying
to
push
this
as
much
as
we
can
remain
in
the
air,
because,
obviously
a
lot
of
the
the
original
engineering
investment
have
been
made
so
I'm
hoping
we
can
line
up
with
the
API
review,
updates
and
closed
on
them.
This
release,
and
so
yeah
we'll
keep
pushing
ahead
on
that.
One.
G
A
So
so
next
one
it
is
the
resource
management
well
show
this.
In
this
quota
we
only
promote
the
one
to
the
PQ,
which
is
the
designed
for
impacts,
update
how
the
all
containers
requester.
So
this
is
in,
like
the
noun,
the
time
request
the
front
of
the
scanning
team
and
they
want,
for
the
vertical
part,
the
auto
scaling,
so
we
sang
out
to
have
them,
keep
dying.
It's
actually
an
adult,
because
because
this
will
affect,
after
the
are
whole,
the
entire
of
the
work
node
of
the
sickle
tree.
G
On
this
section,
thought
I
know:
you're
19,
you
a
chance
to
sync
up
too
much
before
today's
meeting,
but
I
anticipate
that
Red
Hat
will
want
to
continue
to
iterate
on
the
ability
use
XFS
quota
to
do
little.
This
tracking
and
so
I'll
supplement
that
here
and
then
also
I'd
like
to
give
folks
from
Intel
a
chance
to
potentially
look
to.
You
know
see
what
appetite
they
have
in
this
release
to
then
support
evolving.
The
demonstration
they
previously
I
don't
know
Connor
if
you
guys
have
capacity
this
way
cycle.
Yes,.
E
Yeah
I
think
we'd
really
like
to
push
that
forward.
It's
I
think
it's
an
enhancement
that
benefits
few
existing
features.
You
know,
CPU,
pinning
and
device
plugins
and
I.
Think
we've
got
a
lot
of
support,
so
I
guess.
The
question
is
how
that
fits
into
the
stability
release
story.
That's
maybe
a
question
for
you
and
Don.
E
A
So
yeah,
that's
the
leader
behaviors,
yes,
that's
it
actually
I
do
think
about
the
both
asleep
and
in
the
Auslan.
Also
the
work
you
get
down,
but
you
might
be
like
hair,
stuff
and
I
think
we
can
post
make
progress
in
q4
and
the
only
thing
it
is
we
need
talk
about
in
in
detail.
It
is
how
we
include
those
kind
of
things
like
the
same
thing,
for
the
increase,
update,
pod
and
cousin
requests
that
always
sign
around
here.
It
is
just
around
we
really
try
to
do.
G
I
think
we
can
shake
out
the
details
on
that
dawn.
Like
an
in
fairness,
we
could
also
make
the
same
commitment
that
we'd
close
on
design
for
the
work
that
Intel
has
been
pushing
as
well
and
q4,
and
then
see
how
far
we
get
with
a
alpha
style
implementation.
But
I
do
think
that
we
should
figure
out
a
way
that
we
can
appropriately
allow
progress
while
not
introducing
too
much
risk
yeah.
A
A
F
G
F
G
A
The
people
may
notice
that
these
partners
Nezumi
connect
with
the
company
runtime
or
application
management
and
because
the
giving
is
so
we
learn
to
be
the
stable
new
society.
Any
things
change
in
that
area.
But,
of
course,
there's
the
back
and
there's
the
issue.
We
are
going
to
continue
support
and
also
help
to
qualify
and,
for
example,
and
we
are
going
to
use
your
help
to
qualify
the
continuity
one
that
to
you
and
also
I,
believe
the
cry
also
have
the
newly
needs
and
communicate
we
are.
G
Yeah
nothing
from
my
and
other
than
the
two
items
we
just
discussed,
which
I'm
sure
we
can
come
to
some
consensus
on,
but
I
think,
given
the
timelines
and
understanding
that
how
short
q4
is
and
holidays
and
conferences
and
a
person
I'd
like
to
avoid
having
to
review
too
much
on
like
a
Thanksgiving
holiday
like
last
year.
So
what
people
can
appreciate
the
the
desire
to
keep
things
tight
and
so
yeah
that
this
is
seems
completely
appropriate
to
me.
A
G
G
G
In
some
ways,
those
times
are
arbitrary,
so
like
in
some
cases
like
we
had
a
pod
start
timeout.
That
was
one
minute
in
our
CI
infrastructure.
It
was
taking
a
minute
fifteen
and
either
we
were
running
different
instance
types
or
network
was
loaded
or
we
were
hitting
a
cloud
quota
problem
mm-hmm
that
I
didn't
know
like.
G
If,
if,
as
a
group,
we
could
talk
through
a
future
way
that
we
can
make
more
of
these
times
tuneable
without
changing
the
code,
because
I
think
it'd
be
useful
for
folks
who
run
conformance
tests
and
stuff
like
that
in
a
variety
of
deployment.
Architectures
that
sometimes
anytime
assumptions
we
make
are
not
always
the
best
but
I
think.
A
That
would
be
useful,
especially
for
I,
believe
metric
Patrick,
a
definite
interesting
because
the
some
of
archives
of
the
techniques,
time
to
let
other
windows.
But
there
are
some
fast
camera
on
the
windows,
but
it
may
have
to
do
you
have
to
send
a
different
parameter.
So
if
you
make
that
are
cast
yeah,
so
we
we
could
go
through
all
those
kind
of
things.
A
Maybe
we
could
I,
don't
know
how
to
run
those
kind
of
things
we
could
there
hire,
or
maybe
we
can
aggregate
all
the
information
and
do
some
shared
document
or
what
spreadsheet
or
whatever
so
I.
What
have
ties
that
we
can
improve
we've
one
night.
This
cannot
idea
a
while
back
two
years
ago
in
the
chiquinho
team
internally
and
I'm
not
sure
how
how
a
physical
can
run
among
the
community.
A
A
Today
you
make
the
random
icon,
they
just
choose,
and
then
we
just
finish
those
for
the
two
days
and
then
then
then
compact
off
the
metrics,
and
if
you
find
what's
the
success,
metrics
how
to
measure
and
then
so,
then
we
run
those
kind
of
things
I'd
together
and
then
look
at
so
I'm.
Not
ruthless
I
just
threw
this
idea
because
we
used
to
run
this
in
turn
on
FX
much
easy,
because
everybody
stick
on
the
table,
then
we
come
to
each
other.
A
G
Well,
either
way,
then
just
for
heads
up
in
the
I
think
I
don't
know
if
Renault's
on
the
phone,
but
we've
kept
getting
hit
by
the
same
seven
flakes
and
I
think
we've
exhausted
the
setup
ER
as
we
were
looking
to
get
a
open
up
stream,
so
I,
don't
think
that
any
more
will
be
there.
But
just
so
I
know
you
do
had
a
question
like
this.
This
was
the
context
from
which
we
were
coming
from,
which
was
sure
our
timeouts
are
not
very
flexible
for
different
deployment.
Architectures
mm.
F
G
If
the
image
pool
time
varies
slightly
at
all,
then
we
sometimes
we
would
hit
our
threshold
right
like
between
a
one-minute
thing
versus
a
1
minute
and
5
second
thing
and
I
think
we
try
and
creep
all
images
but
yeah.
G
After
all,
the
containers
in
that
pod
had
ran
to
completion,
but
that
was
the
only
area
where
I
saw
like
a
logic
problem
that
we
had
on
the
code
that
did
merchants
get
fixed
so
anyway,
we're
just
trying
hard
to
get
our
CI
in
in
better
shape,
and
so,
if
folks
see
a
few
others
that's
kind
of
like
so
anyway.
That's
all
I
have
for
today,
but
thank
you.