►
From YouTube: Kubernetes SIG Release 20180925
A
A
To
that,
but
essentially
the
notes
will
take
will
be
they're
available
for
your
viewing
later
so
without
further
ado,
I
believe.
The
first
item
on
the
agenda
belongs
to
Dems.
If
Tim
was
around
which
I'm
looking
in
the
attendee
list
and
not
saying
well
pinging
dims
offline
and
see
if
he
wants
to
join
here
in
a
bit.
B
So
1.12
is
almost
wrapping
up.
I'll
wait
for
Tim
to
give
an
update
later
if
he
wants
to
so,
as
of
today,
113
is
set
to
start
next
Monday
October
1st.
We
have
a
full
release
team
thanks
to
Stephens
efforts
and
all
first-time
volunteers
and
people
continuing
on.
We
have
like
a
full
release,
team
or
fully
staffed.
So
that's
exciting,
so
I
have
posted
a
link
to
that
timeline.
B
This
is
a
very
crunched
release,
to
say
the
least,
between
the
two
cube
cons
and
Thanksgiving
holidays
in
the
last
weeks
of
December.
We
only
have
about
ten
weeks
of
each
time,
so
the
PR
there
goes
through
the
schedule.
We
have
some
LG
teams
and
consensus
there.
So
I'm
going
to
hold
till
end
of
day
tomorrow,
waiting
for
some
final
feedback
before
I
get.
B
The
first
draft
are
scheduled
in
and
we'll
have
to
after
that
play
by
the
year,
depending
on
how
the
lease
cows,
if
we
need
to
extend
the
gates
opportunities
ahead,
so
I
yeah.
Your
feedback
is
more
than
welcome
there.
The
last
piece
of
information
now
yeah
licking
it.
If
you
look
at
the
timeline,
you'll
see
that
the
most
critical
at
least
the
top
most
critical
thing
that's
going
to
determine
the
health
of
the
reefs
is
the
enhancement,
the
feature
boat
coming
in
so
Ken
Drake.
Who
is
the
feature
lead
and
I?
B
We
plan
to
sync
up
with
the
six
next
week's
specifically
to
get
an
assessment
of
what
they're
planning
for
113
and
how
much
of
the
follow
fallouts
from
112
are
still
on
track,
113,
so
that
we
can
kindly
hint
to
them
they're
not
to
be
too
aspirational
in
terms
of
features
for
the
release,
given
the
timeline
itself.
So
we
hope
to
have
like
like
a
good
list
by
the
end
of
first
two
weeks
at
ease,
and
then
we
plan
to
follow
pretty
closely
so
that
the
release
doesn't
deal
way
too
much.
B
And
the
final
piece
is
if
anybody
from
the
113
team,
if
you
are
under
call
I,
had
sent
out
a
set
of
housekeeping
notes
that
will
help
us
get
started
on
the
release,
including
the
calendar,
invites
of
what
Google
Groups
to
join
and
instructions
on
getting
membership.
So
if
you
didn't
receive
the
email
and
or
or
need
help
for
sponsorship,
anything
easting
me
on
slack.
As
of
now
the
burndown
is
set
to
start
next
Monday
October
1st
at
11:00
a.m.
PST
great.
A
A
A
And
what
I'd
say
is
you
know
we're
all
community
around
these
roles?
So
if
you
need
help,
definitely
don't
be
afraid
at
any
point
in
the
release
cycle
to
ask
in
this
meeting,
generally
speaking
is
a
great
place
to
do
that.
If
you're
curious
about
anything
this
bug
triage
or
whatever
you're
doing
in
this
release-
and
you
just
don't-
you
know,
feel
like
you're
you're
doing
the
right
things
or
you
don't
know
what
you're
doing
or
any
of
that
stuff.
D
That
point
a
little
note:
a
I
want
to
encourage
everyone
to
like
really
challenge
the
documentation
challenge
like
everything
that
exists,
because
I
think
some
of
the
the
best
lens
to
view
the
release
team
in
is
someone
who
hasn't
done
it
before.
So
you
know
over
the
last
two
release
cycles,
we've
had
a
lot
of
good
documentation,
come
in
cystic
release
as
Revo,
but
we
can
always
do
better.
A
For
real
yeah-
and
it's
interesting
too,
because
every
release
the
the
process
evolves
in
some
way
so
because
we
do
retrospectives
and
hopefully
learn
and
grow.
So
it's
it's
always
a
changing
thing.
So
there's
no
way
unless
we're
doing
completely
wrong
with
the
rule
that
any
of
the
documentation
is
correct.
After
a
release,
they
should
all
get
refreshed
with
what
we
learned.
So
thank
you,
Stephen.
That's
a
super
super
salient
point.
B
A
C
I
put
it
in
okay:
it's
cool
I
wanted
actually
coordinated.
Cuz
I
know
that
we
have
a
few
of
the
scheduled
now
that
we've
gotten
the
information
back
from
the
conference
organizers,
the
deep
dive
that
Chuck
and
proposed
for
Seattle
got
accepted,
and
so
that
will
be
sort
of
deep
dive
on
build
tools
for
for
Seattle
I.
Believe
there
was
an
intro
session
for
Shanghai
I
didn't
propose
it.
I
proposed.
E
I'm,
just
looking
at
what
what
the
text
of
the
proposal
is,
the
intro
is
really
just
a
high-level
intro,
but
we
could
for
it
as
proposed
for
Seattle,
but
I
would
like
to
do
a
panel
honestly
to
get
a
little
more
discussion
so
and
really
I
submitted
the
the
ones
for
Shanghai
sort
of
speculatively
open-ended.
So
at
this
point,
if
anybody
is
gonna
be
there
and
wants
to
do
a
panel,
let's
coordinate
it.
B
A
E
I'm
thinking
there
won't
be
much
crossover,
so
that's
kind
of
why
I
was
thinking
for
Shanghai
back
when
I'd
propose
things
intro
just
high-level
overview
and
then
for
the
deep
dive
to
really
try
to
make
some
connections
in
the
ecosystem
there.
If
folks
show
up
to
see
how
we're
doing
by
their
needs
and
maybe
drive
some
connections
there,
yeah.
A
A
A
A
F
A
Partly
because
there
is
a
pretty
good
chance
that
I'm
going
to
step
down
as
lead,
and
you
give
an
opportunity
for
someone
else
to
step
into
the
role
in
and
have
all
the
fun
of
running
these
meetings
and
all
that
good
stuff.
So
I
just
like
to
put
it
out
there
that
if
anybody
has
a
deep
interest
in
being
a
chair,
probably
when
we
redo
the
charter
of
make
a
good
time
to
to
make
that
transition.
A
D
E
I'm,
probably
interested
in
helping
out
too,
if
necessary
or
desired
I
own
obviously
focus
up
until
this
week
on
the
release,
but
getting
into
the
the
nitty-gritty
of
the
release
process
by
being
lead
on
the
112
cycle.
I
definitely
see
a
lot
of
things
that
I'd
like
to
continue
on
driving
improvements,
mm-hmm.
A
Well,
there's
no
limit
on
the
number
of
chairs
and
frankly,
as
I've,
seen
running
various
things
over
the
last
few
years,
I
having
more
people
to
makes
it
better
because
it's
you
know
some
of
these
in
the
conference
or
you
know
it
just
makes
it
way
easier
and
because
the
chair
is
not
a
roll
with
power,
it's
really
about
organizing
and
making
sure
that
people
are
rallied
around
the
right
problems.
The
more
lenses
we
have
on
that
the
better
I
mean
I,
think
everybody
Stephen
will
make
a
great
chair,
I.
A
Think
Tim
you
make
great
chair.
I
should
make
a
great
chair,
there's
the
we're
just
flush
with
people
who
are
just
eminently
qualified
to
do
it.
So
what
I
just
say
is
you
know
I'm
if
we
can
define
the
role,
however,
we
want,
we
could
have
seven
chairs
for
all
I
care
and
we
split
it
up,
but
I
just
want
to
make
sure
it
represents
a
good
cross-section
of
the
community
and
grass
of
what
we're
trying
to
accomplish
and
ideas
and
all
that
stuff
and
in
good
company
diversity,
and
all
that
so
Steven.
A
D
A
A
We
probably
are
going
to
have
a
sub
project
around
artifacts,
because
I
think
we
we're
probably
on
deck,
to
figure
out
what
we
actually
consider
official
release
artifacts
and
what
those
are
used
for
right,
they're
sort
of
the
debate
over
is
it
is
it
a
reference,
is
a
reference
artifact
or
is
it
something
that
we
support
and
recommend
people
install
on
their
production
clusters
or
all
that
good
stuff?
Then
there's
provenance
associated
with
those
so
that
we
can
do
some
sort
of
signing?
Or
you
know
something?
A
A
A
B
A
B
A
Yeah
and
that's
why
I
like
having
the
idea
of
a
lot
of
leads
I
would
look.
You
know
this
thing.
Sig
release
has
traditionally
been
one
of
the
most
cutting-edge
SIG's
in
terms
of
defining
roles
and
our
processes
being
really
well
defined
and
accountabilities.
A
lot
of
stuff
I
would
love
for
us
to
be
the
model
of
what
a
good
Charter
system
looks
like,
and
good
leadership
and
sir
projects,
because
I
feel
like
right.
A
A
And
also
to
just
a
in
case,
I
mean
probably
nobody's
worried
about
this,
but
I'm
not
going
to
disappear
from
the
project
or
anything.
It's
just
a
I
just
want
to
make
sure
that
we're
making
room
for
the
next
generation
of
leaders,
which
is
not
me,
I've,
been
on
this
thing
for
three
years,
pretty
much
every
day
of
my
life
for
the
last
three
years,
so.
A
B
Today,
are
you
talking
about
the
dogs
role
in
general
today
or
or
revamping
the
dogs
for
bug
triage
by
the
way
we
could?
If
you
are
part
of
bug,
triage
yeah,
you
could
definitely
take
a
look
at
the
dogs
and
see
what's
missing
or
what
you
want
to
make
better,
that
we
could
definitely
do
in
1:13
and
also
there's
the
whole
dogs
team
that
does
the
whole
dogs
portion
of
it
yeah
we
can,
we
can
definitely
chat
offline.
We
can
use
your
help.
Yeah.
E
For
the
sort
of
parallel
question
about
how
does
the
release
process
work?
This
isn't
super
well
documented,
so
especially
for
folks
on
the
release
team.
If
you
start
with
the
role
handbooks,
you
have
and
read
what
we
have
documented
so
far
and
then
are
paying
attention
during
the
cycle
and
sort
of
questioning
actively
like
hey
well,
this
doesn't
quite
match
with
what
was
in
the
document
or
or
even
even
better,
maybe
like.
Why
are
we
doing
it
this
way?
He
sure
it's
what's
documented,
but
could
we
do
better
and
here's?
A
E
I've
got
a
question
kind
of
in
that
similar
vein.
As
we
were
discussing
some
of
the
release
artifacts
and
build
process
stuff
last
week,
Caleb
suggested
that
maybe
it's
time
to
start
formulating
a
kept
around
that
what
we
think
the
release
engine
engineering
process
should
be
and
get
more
folks
talking
about
it
and
follow
the
kept
process
for
it.
I'm
curious
what
folks
think
so.
D
There
was
I
forgot
exactly
where
it
was,
but
someone
said
there
someone
said
someone
was
working
on
a
kept
for
something
relief,
engineering
related
I,
don't
know
where
it
lives,
it's
probably
hidden
in
the
sick,
reliefs
chat
somewhere
I
can
try
to
take
it
up.
But
yes,
we
should
absolutely
for
milk
fertilize
one
in
in,
in
name
on
the
Charter
and
and
two
kept.
A
Yeah
I
think
just
even
to
have
a
cohesive
place
where
we
document
the
evolution
of
it.
It
would
be
good
I
do
want
to
think
really
harder,
though,
about
what
a
campus
is
designed
to
document
and
how
the
release
process
deviates
from
that
and
how
we
can
inform
the
kept
process
itself
with
what
we,
what
we
decide
and
learn,
because
the
camp
process
is
really
not
geared
toward
process
as
much
as
this
implementation
of
stuff
code
and
a
lot
of
the
release
process
is
not
necessarily
code.
It's
toxin,
I,
wonder.
A
D
A
A
E
A
A
A
Hundred
percent
yeah
no
I
yeah-
let's,
let's
just
do
that
at
asynchronously,
then
in
the
the
sig
release
channel-
and
we
can
figure
it
out
there-
maybe
organize
at
work.
I
would
love
to
see
this
work,
get
spread
out
a
little
bit
and
also
not
have
to
have
the
people
who
are
tasked
with
the
release
process
having
to
do
all
this
stuff.
On
the
same
time,
because
that's
a
lot
so
ya
feel.
E
Like
when
you're
staffed
from
my
perspective,
I
feel
like
I,
guess
kind
of,
like
echoing
what
I
said
earlier
being
the
release
lead
for
this
last
cycle.
I
feel
like
it
unformed
me
quite
a
bit
and
I
I'm
excited
to
not
have
to
deal
with
the
release
now
and
be
able
to
get
down
to
some
of
that
that
work
so
yeah
there's
at
least
my
pair
of
hands
coming
available.
Okay,.