►
From YouTube: Kubernetes Community Meeting 20191031
Description
Welcome to the Kuboonetes Community Meeting on a spooky October 31st!
A
B
B
C
Good
morning,
everyone
afternoon
evening,
depending
upon
where
you
are,
my
name,
is
hammy
the
hamster
I'll
be
covering
for
marki.
Today,
Markey
does
work
for
cystic.
He
is
part
of
the
sig
contributors
experience,
as
well
as
the
117
release
shadow
on
the
bug
triage
team.
This
is
our
community
meeting
on
October
31st,
2019
I'm
glad
to
have
everybody
here
today.
I
want
to
thank
you
all
for
taking
the
time
to
spend
with
me
and
all
of
these
fine
people.
C
I
would
like
to
remind
everybody
that
we
do
have
a
community
code
of
conduct
and
really
it
just
simply
says,
be
hamster
to
one
another
which
is
simply
just
be
nice
to
one
another.
Can
I
get
a
note-taker,
it's
a
really
fun
thing
and
if
I
could
get
one
that
would
be
super
super
awesome
and
the
hamster
would
thank
you
very
very
much.
C
Anyone
because
I've
only
got
a
hamster
hand,
and
this
is
not
gonna
work
for
me.
I
got
you
fam,
Oh,
beautiful
detective.
Thank
you,
okay.
Well,
let's
go
ahead
and
get
started
again.
Thank
you.
Everybody
for
being
here
we're
gonna,
go
ahead
and
get
started
with
the
117
release.
Update
I
am
going
to
turn
it
over
to
the
awesome
release,
lead
Guinevere.
May
you
please
take
over.
D
Even
new
button
today,
hey
happy
Halloween
everyone
I
am
here
to
talk
about
the
process
of
the
release,
as
it
is
right
now
we
are
in
the
phase
of
everyone
hunkering
down
and
writing
as
many
features
as
fast
as
they
possibly
can.
Code
freeze
is
coming
two
weeks
from
now
November
14.
So
until
then,
all
features
have
to
be
have
to
be
merged
into
the
kubernetes
master
branch
which
won't
be
forward
at
night.
We
actually
I'll
say
that
next,
after
which,
after
code
freeze,
everyone
has
to
follow
the
cherry-pick
process.
D
D
We
also
cut
the
beta
the
first
beta
of
117
this
week,
hooray
yeah.
Thank
you
especial
thanks
to
Stephen,
who
believe
live
stream.
That
process
I
wasn't
there
to
witness
it.
We
also
created
the
117
release
branch
which,
until
code
freeze,
will
be
updated
daily
via
all
the
changes
that
are
coming
in
to
kubernetes
master
branch.
D
C
C
B
B
Yes,
now
maybe
say:
yes,
we
can
okay
awesome.
Here
we
go
alright,
so
we're
gonna
start
off
with
the
release.
Team
Gwen
gave
a
wonderful
update
since
well.
Let's
talk
a
little
bit
about
what
happened
in
116
as
well
as
some
of
117,
so
we
have
I
for
anyone.
Who's
been
on
these
calls
and
been
part
of
the
release.
Retrospectives
we've
put
an
action
item
about
firming
up
the
firming
up
the
feedback
loop
between
sig
release
and
sig
scalability.
B
There
are
often
lots
of
late-stage
things
have
come
up
that
are
hard
to
debug
or
take
a
while
to
debug,
because
their
scalability
jobs
and
some
of
those
jobs
will
run
will
run
for
multiple
hours
or
only
run
twice
a
day.
So
it's
very
important
that
we
we
act
as
good
citizens
by
working
together
and
over
the
last
few
cycles
we
have
met
a
lot
more
frequently
with
sig
scalability
from
not
at
all
to
at
least
once
a
cycle
to
we're
meeting
at
least
twice
a
cycle.
Now
so
that's
been
pretty
great.
B
We
have
closed
up.
We've
got
a
lot
more
information
around
their
process
and
there's
always
more
more
room
for
improvement,
but
that
has
been
going
well
for
the
last
few
cycles
for
the
so
we
have
a
roll
on
the
release.
Team
called
the
emeritus
advisor
and
the
emeritus
advisor
is
essentially
responsible
for
acting
as
a
continuity
point
across
release
cycles,
acting
as
someone
who
is
been
on
the
release
team
before
kind
of
knows,
the
ins
and
outs
of
of
that
of
that
team.
B
Josh
burkas
kicked
it
off
and
who
has
done
a
wonderful
job
in
terms
of
getting
people
up
to
speed.
One
of
the
things
that
the
emeritus
advisor
role
is
responsible
for
is
mentoring,
the
shadows
that
are
on
the
release
team,
in
addition
to
the
role
leads
right,
so
that
has
been
having
a
senior
member
of
the
release
team.
Someone
who's
been
on
the
releasing
multiple
times
was
super
useful
for
the
shadows.
We
do.
B
B
So
thank
you.
Josh
thank
myself.
Who's
worked
in
the
Feres
advisor
role
as
well
as
Clair,
who
is
our
current
emeritus
adviser
and
was
our
previous
release
team
lead.
One
of
the
things
I'd
like
to
highlight
is
that
the
increased
diversity
across
the
the
release
team
so
last
cycle
we
had,
we
had
a
veritable
rainbow
of
people
across
I.
B
Think
five
of
the
seven
continents
participating
in
the
release
team,
so
we
made
sure
to
we
made
sure
to
kind
of
look
out
for
making
sure
that
we
were
diverse
in
location
and
company
affiliation,
ethnicity,
gender,
identity
and
I.
Think
the
number
rough
calculation
was
about
46%,
non
white
male
for
the
release
team
last
cycle
and
and
this
cycle
we've
got
a
bunch
of
women
in
in
lead
positions,
so
Gwen
and
and
Maria
and
Claire
as
an
emeritus
adviser
and
Elena,
as
I
signal
lead.
So
I
think
that
overall
we're
doing
a
good
job.
B
B
B
You
know
people
don't
want
to
be
the
first
people
to
touch
to
touch
a
dot
zero,
so
so
hats
off
to
everyone
who
was
involved
in
making
sure
that
release
one
got
out
on
time
and
and
was
as
bug
free
as
possible.
So
just
a
few.
Obviously
the
people
on
the
release
team,
Jordan
Liggett
been
the
elder
Kristoff,
so
many
names
so
many
names
that
I
could
name
that
are
revolt
and
involved
in
getting
moving
forward
on
those
late
stage
bugs.
So.
Thank
you.
Thank
you.
B
Thank
you
all
overall
process
and
automation,
improvements
for
all
of
the
roles.
This
I
think
between
this
cycle
and
last
we've
seen
a
lot
of
deleting
roles
deleting
responsibilities,
deleting
jobs,
improving
things
that
can
be
improved,
wiring
automation
into
our
spreadsheets,
the
the
you
know,
the
advent
of
the
release
notes
website,
so
lots
of
interesting
things
have
been
happening
in
terms
of
process
and
automation,
improvement,
we're
you
know
constant
process
in
looking
for
shadows.
This
is
something
that
happens
every
cycle.
It's
something
that
people
get
pretty
excited
about.
B
We
always
have
I
think
the
last
few
cycles
we
had
about
80
people
who
are
interested
in
and
being
a
shadow
for
the
release
team.
So
it's
always
nice
to
see
that
that
level
of
interest
for
I,
I,
think
I
I.
Think
you
one
of
the
the
more
stressful
roles
within
the
community
I
also
saw
people
filing
exceptions
for
tests,
making
sure
that
they
were
increasing
the
test
coverage
of
their
their
enhancements
before
they
got
out
of
the
door.
B
So
thank
you
for
all
the
contributors
that
were
were
extremely
extremely
diligent
about
one
getting
their
enhancements
out
on
time
and
and
then
also
improving
the
test
coverage
around
the
overall
code
base.
We
shifted
all
the
release
manager
roles.
You
may
already
know
about
this,
so
the
branch
manager
patch
release
team
had
been
done
earlier,
but
all
those
roles
have
been
shifted
out
of
the
release
team
now,
so
that
so
that
the
release
team
can
focus
on
what's
happening.
B
This
cycle
and
the
release
managers
can
focus
on
how
to
build
process
around
the
overarching
release
process.
Right
and
again,
there
was
an
uptick
of
test
cleanup
and
deletion
so
kudos
to
kudos
to
everyone
on
the
on
the
CI
signal
team,
who
has
been
ruthless
about
cleaning
up
tests
for
the
last
few
cycles,
specific
shoutouts
to
to
George
and
Elena
Maria
who's
been
who's
been
around
the
process
for
a
few
cycles
as
well.
Ok
enough,
really
seeing
more
stuff.
B
So
the
release
managers
group,
if
you're
not
familiar
with
release
managers
group
already,
it's
basically
the
it's
a
group
that
lives
within
within
the
release:
engineering,
sub
project
of
cig
release
and
it's
composed
of
the
patch
release
team.
The
branch
managers
release
manager
associates,
release
manager
associates
are
kind
of
apprentices
to
the
branch
managers
and
patch
release
team.
What
we
expect
of
the
release
manager
associates
is
essentially
to
help
us
pay
down
some
of
the
technical
debt
that
we've
been
building
up
in
the
project
over
the
last
few
years.
B
The
the
build
admins
build
admins
or
Googlers,
who
are
capable
of
cutting
depth
and
rpms
for
the
project.
So
we
are
working
on
we're
working
on
improvements
to
that
process
so
that
it
can
be
done
by
not
just
Google
Earth,
but
also
community
people
that
has
been
going
well.
The
sig
chairs
are,
of
course,
involved
as
sink
chairs.
We
also
act
as
release
engineering,
the
release,
engineering
sub
project
owners,
which
means
we
also
have
the
keys.
We
are
either
part
of
these
teams
like
I,
am
a
branch
manager.
B
B
So
we
modeled
this
team
kind
of
around
what
some
of
some
of
the
processes
that
the
product
security
committee
has,
and
especially
because
we
we
are
also
responsible
for
being
part
of
the
the
feedback
loop
and
the
and
the
fix
team
for
when
TVs
are
announced
or
when
sea
views
are
quietly
announced
right.
So
it's
important
that
our
processes
fall
in
line
closely
with
what
the
product
security
committee
does
day
to
day
so
building
a
team
that
is
that
is
rooted
in
trust.
Again,
these
are
people
who
have
the
keys
to
cut
kubernetes.
B
So
we
need
to
make
sure
that
they
are
active
community
members.
They
are
interested
and
excited
about
that
opportunity
and
also
care
about
the
responsibility.
That's
involved
in
that,
and
you
know,
and
the
this
all
exists,
to
build
a
contribution
ladder
around
release
engineering
within
the
project.
B
Your
your
and
what
we're
also
seeing
a
similar
thing
happened
and
like
working
group
Kate's
in
front
right
now
right
and
that's
a
that's,
an
awesome
effort
if
you're
not
involved
or
interested,
and
you
have
sra
or
in
engineering
experience
DevOps
II
experience
hang
out
in
the
WG
Cates
infra
channel
as
well.
They
are
always
looking
for
help.
B
So
more
specifically,
on
the
release
engineering
side,
we've
been
working
on
onboarding
we've
been
working
on
onboarding
the
release
manager
associates.
That
has
been
an
interesting
process
for
me
because
it's
a
lot
of
it
is
figuring
out
what
I
can
show
someone
when
they
are.
What
I
can
allow
someone
to
do
when
they
don't
have
access
to
do
the
thing
right
again?
It's
a
role
where
we're
building
trust
and
it's
hard
to
gain
the
trust
without
being
able
to
do
the
thing,
but
you
can't
do
the
thing
without
the
trust.
B
It's
it's
an
it's
been
an
interesting
dynamic,
but
I
think
we're
moving
along.
Well.
There
we've
started
to
wire
up
the
release
engineering
jobs
in
CI.
So,
for
example,
the
way
we
do
Deb
in
rpm
builds
that
actually
runs
as
those
run
as
proud
jobs.
Now
at
least
testing
the
process
right
not
actually
executing
creating
artifacts
and
uploading
them
anywhere.
It
just
validates
that
the
scripts
that
we
have
in
place
work
cleaning
up
some
of
the
process
documentation
again.
These
are.
B
This
is
kubernetes
releases,
a
repo
that
has
existed
since
I
want
to
say
2016,
maybe
even
earlier
so
very
early
in
the
project.
A
lot
of
the
scripts
that
are
there
are
have
been
there
since
close
to
the
inception
of
the
project
so
kind
of
going
going
through
those
scripts
and
and
starting
to
massage
some
of
those
things
and
also
writing
about
how
they
actually
work
right,
creating
build
jobs.
This
happened
recently
so
as
we're
moving
from
Google
based
infrastructure
over
to
CN
CF
sponsored
infrastructure.
B
We
need
to
test
the
way
we
build.
Can
we
still
build
like?
Are
we
making
the
assumptions
that
we
make
about
the
build
process
and
specifically
I'm
talking
about
like
the
CI
kubernetes
build
right?
So
that's
what
pushes
the
artifacts
into
into
buckets
for
you
to
use
so
if
you've
ever
used
a
DL,
docket
style
Inc,
that
is
the
that
is
landing
in
our
in
our
GCS
bucket
right,
so
replicating
that
process
for
the
the
case.
Infra
infrastructure
right
instead,
so
I
have
recently
wired
up
build
jobs.
B
We
started
rewriting
the
the
k
release
tooling
and
go
we
actually
reviewed
and
merged
the
first
PR
today,
the
first
one,
all
it's
been
in
progress
for
a
while,
but
I
finally
cleaned
that
up
and
it's
been
merged.
So
the
first
tool-
that's
that's
gone
in-
is
branch
fast
forward,
so
funny
enough
we're
in
the
branch
fast
forward
period
right
now,
so
the
branch
fast
forward
tool
is
the
first
tool
in
that
and
that
toolbox
the
next
one
will
probably
be
push
build,
which
is
used
across
lots
of
different
jobs.
B
So
lots
of
progress
they're
very
excited
about
that
we're
refactoring
the
debin
RPM
packaging
tools
to
fall
more
in
line
with.
So
there
is
a
so.
The
RPMs
are
built
in
Bosch
and
the
Deb's
are
built
with
a
go
script.
We're
trying
to
unify
those
two
right
now
and
and
provide
a
means
of
doing
a
declarative,
packaged,
build
right
so
submitting
an
a
yeah
Mel
to
this
tool
and
allowing
it
to
having
it
define
the
dependencies
for
each
of
the
packages.
B
We
kick
out
so
cube
a
DM
cube,
CTL,
cubelet,
CRI
tools
and
kubernetes
CNI
right.
There
is
a
discussion
around
hypercube
out
of
tree
in
progress.
We're
actually
going
to
talk
about
that
in
the
code
organization
meeting,
which
is
right
after
this.
That's
we'll
see
how
that
goes.
I
don't
have
an
update
there,
but
interesting
things.
Could
happen
and
finally,
code
base
walkthroughs,
so
recently
I
recorded
a
few
videos.
One
is
around
the
image
builder.
B
So
go
check
those
out
when
you
get
a
chance,
if
you're
interested
in
that
kind
of
stuff,
so
things
we
need
from
you,
there
will
probably
be
a
lot
of
announcements.
Coming
soon
will
be
at
cube
con.
We
have
a
few
talks.
Tim
and
I
are
doing
a
talk
on
the
the
state
of
release
engineering
these
days,
and
there
will
also
be
a
release.
B
Engineering
talk
with
myself
and
Hannes
around
it'll,
be
a
code
walkthrough
of
the
it'll,
be
a
code
walkthrough
of
the
kubernetes
release
repo,
so,
as
always,
I
think
I
copied
and
pasted
this
slide
from
the
last
thing,
because
it
is
always
true,
please
pay
attention
to
see.
I
signal
were
condi
flaking
your
tests
work
on
making
sure
it
tests
for
your
cigs
are
owned
and
they
are,
and
owners
are
notified
of
the
failures
for
those
tests
make
sure
that
you're
actually
acting
on
those
on
those
failure.
B
Notifications,
especially
if
someone
from
the
release
team,
is
reaching
out
to
you
and
they're
landing
they
land
on
master,
informing
or
master
blocking
boards.
Please
please,
please
make
the
release
teams
job
as
easy
as
possible
and
in
in
the
same
vein,
please
pay
attention
to
the
the
release
117
scheduled
dates
when
I
told
you
about
those
a
little
earlier,
but
we
have
a
readme
that
gives
you
a
tldr
about
all
of
those
dates.
B
So
take
a
look
at
that
when
you
get
a
chance
all
right
so
where
to
find
us,
we
will
be
hanging
out
at
cube.
Con
I
do
not
know
if
caleb
is
going
to
be
there.
I
think
he
probably
will
be
Tim
and
I
will
definitely
be
there
because
we're
talking,
we
will
be
there.
We
are
friendly
people,
come
hang
out,
come,
say
hi.
Our
homepage
is
get
that
Cates,
that
io
/
community
/
sig
release
/
readme.
We
also
have
gets
get
Kate,
CIO,
/,
say
release.
B
We
have
an
entire
repo
dedicated
to
our
documentation.
We
have
multiple
slack
channels.
One
is
sync
release.
There's
also
release
management
release,
CI
signal
release,
comms
there,
probably
I'm
forgetting,
but
that's
a
that's
a
good
start,
and
finally,
there's
the
there's.
The
kubernetes
sing
release
mailing
list.
We
also
the
release.
Engineering
team
is
also
available
at
release
managers
at
kubernetes
I/o.
If
you
need
to
reach
reach
us
regarding
release
e
stuff
yeah,
that's
that's
all
I
got
any
questions.
C
C
Right
well,
we're
gonna
go
ahead
and
move
right
into
our
announcements.
One
of
the
things
I'd
like
to
say,
don't
forget
to
register
for
the
contributor
summit.
A
lot
of
people
are
working
super
super
hard
on
that
it's
gonna
be
a
lot
of
fun.
So
please
do
do
register.
We
would
love
to
see
you.
There
have
fun
laughs,
hammy.
The
hamster
will
not
be
there,
but
I've
heard.
Someone
else
is
gonna,
make
an
appearance
so
stay
tuned
for
that,
let's
go
right
into
shoutouts,
so
shoutouts.
C
For
the
last
week,
DIMMs
gave
a
shout
out
to
and
I'm
gonna
butcher
some
of
these
names.
So
please
do
not
take
your
personal
fart.
My
claw
farts,
my
claw
for
setting
up
and
running
the
on
boarding
call
for
70
plus
folks
for
the
work
group.
K8A
infra
super
super
awesome
there.
If
you
have
not
gotten
a
chance
to
see
that
I
believe
that
video
is
up
on
YouTube
Daniel
Lippo
vet
ski
I'm,
not
even
gonna,
try.
C
The
ad
name
gave
a
shout
out
saying
thank
you
to
Neil
it
one
two,
three
four,
always
taking
the
time
to
help
and
mentor.
You've
been
there
for
me
and
many
others
and
what
seems
like
everywhere,
from
kk2
cube
admin
to
Docs
and
everything
in
between
Marky
who's,
not
here
today,
I'm
filling
in
for
him
gave
a
shout
out
to
Glen
aveer,
Chris
and
rial
for
getting
together
to
make
the
new
contributor
workshop
awesome
and
for
being
such
fine
peoples
to
work
with.
C
That
was
not
a
misspelling
I
like
saying
people
he
likes
saying
people's.
Thank
you
very,
very
much
for
all
that
you
do.
That
is
it.
Does
anybody
have
any
questions
comments
concerns
anybody
want
to
talk
about
what
they're
doing,
by
the
way
for
everyone
that
has
a
costume
on
super
super
awesome
for
those
of
you?
Don't
don't
worry
about
it.
It's
okay,
Oh
418,
nice!