►
Description
Keynote: Backstage with Kubernetes - Chen Goldberg, Director of Engineering, Container Engine & Kubernetes, Google
The kubernetes community has earned the love of developers worldwide in a way few other open source projects have before. Users trust this community to continue to innovate, stabilize and deliver at a rapid clip. What makes this possible and how will we maintain this as we grow? In this talk we will go behind the scenes to look at what keeps the community humming, growing, contributing, productive and happy.
About Chen Goldberg
Chen Goldberg leads Container Engine and OSS Kubernetes project engineering team in Google. Chen has a customer-centered development philosophy and believes open source is the best way to innovate and develop incredible technologies that are accessible and beneficial to everyone.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
Hi
good
morning,
everybody
I'm
very
happy
to
be
here.
I've
joined
Google
about
eight
months
ago
and
I
was
really
excited
to
join
this
team
I
a
few
years
back
as
an
engineering
manager,
I
I
thought
that
the
best
thing
you
know
whatever
time
we
needed
to
choose
a
technology,
we
prefer
to
use
open
source
and
the
reason
is
that
we
didn't
want
to
be
locked
in
to
anything.
A
We
didn't
want
to
discover
two
years
into
our
journey,
that
we
are
missing
a
feature
and
also
it
increases
the
credibility
of
the
technology
at
an
engineering
manager,
I
I
like
being
close
to
the
user.
This
means
that
we
can
get
feedback
from
users
and
we
know
what's
going
on
and
how
they
are
using.
It
definitely
working
on
open
source
technology
is
the
best
way
to
get
it,
and
luckily
I
got
the
opportunity
to
join
this
community.
A
So,
let's
talk
about
kubernetes.
Yes,
it's
a
very,
very
successful
project.
How
do
we
know
that?
First
of
all,
it's
one
of
the
top
projects
on
github.
We
know
it
based
on
amount
of
stars.
For
example,
there
are
over
33,000
project
external
project
dependent
on
kubernetes
right.
We
kept
hearing
about
extendibility
in
the
community.
We
care
about
it
a
lot
and
we
invest
a
lot
in
that
to
name
a
few,
our
OpenShift
paths
and
aprender,
and
we
have
projects
like
helm
and
compose
specifically
helping
kubernetes
community
to
make
things
easier.
A
We
have
170
meetup
groups
around
the
world.
That's
a
lot.
It
means
that
if
you
are
on
vacation,
for
example,
you
can
definitely
crash
on
a
local
meetup
and
learn
something
new,
but
it
is
not
just
that
right.
It
means
that
it's
easy
to
hire
people
which
are
experts
in
kubernetes
and
they
know
the
technology
and
do
something
important.
When
you're
making
a
choice
of
what
platform
to
use.
A
We
had
5000
commits
added
into
1.4
it's
a
three
month
release
and
this
adds
up
to
35,000
commits
when
the
project
started.
That's
a
lot,
that's
big
right!
Hey!
When
we
had
the
birthday
of
kubernetes
someone
did
the
math
and
figure
this
about
230
engineers
years
just
in
kubernetes,
okay.
So
the
technology
is
great
right
in
the
next
couple
of
days.
You're
going
to
talk
about
and
hear
about
new
features
and
how
you
people
are
using
kubernetes
and
how
it
makes
everything
better
in
this
world.
A
A
This
is
an
interesting
slide,
just
in
the
last
couple
of
weeks
when
I
was
preparing
this
bag,
I
had
to
change
the
numbers
and
bring
them
up
right
now
we
have
950
contributors
on
github.
This
is
we
had
350
new
contributors.
Just
in
this
year
we
have
people
working
in
15
time
zones
around
the
world
and
kubernetes.
Even
if
you
eliminate
daylight
saving
it's
a
lot.
We
have
people
in
the
u.s.
in
China
in
India,
in
Germany,
in
UK,
from
forgetting
some
some
other
countries.
A
When
building
such
a
product
or
solution
like
kubernetes,
you
need
more
than
just
engineers
right,
so
our
community
has
tech
riders
right.
We
heard
them
saying
about
the
documentation,
so
we
have
several
dedicated
technical
writers.
We
have
product
marketing
for
that
management
program
managers.
We
have
managers
in
our
community
and
different
kind
of
roles
that
helps
us
make
it
successful
and
also
the
community
is
really
engaged.
So
there
was
an
analysis
with
bigquery
based
on
github
issues,
and
we
saw
that
the
kubernetes
community
is
the
most
engaged
one
and
all
the
people
right.
A
So
we
keep
talking
who
are
those
nine
hundred
and
fifty
people.
This
is
how
it
looked
back
in
2000
2014.
When
we
started
the
project,
you
can
see
the
majority
or
Googlers
right
people
experience
with
writing
this
systems
and
the
mature
and
the
rest
was
divided
between
independent
contributors
and
redheads.
A
So
Google
today
is
only
46
percent
of
the
commits.
The
next
majority
are
independent
contributors
to
name
one.
So
here
in
the
audience,
for
example,
we
have
the
young,
the
youngest
COO
Meg
maintainer
in
the
kubernetes
community
and
Lukas
is
a
high
school
student
from
Finland,
and
he
started
working
on
kubernetes
by
playing
on
a
raspberry,
PI's
and
kubernetes.
That's
how
he
started
and
we're
really
happy
to
have
him
here
now.
A
A
When
I
presented
that
slide
to
someone
from
the
community,
he
told
me
make
sure
they
understand.
This
is
not
companies
working
on
kubernetes.
This
is
people
working
on
kubernetes.
This
is
not
just
our
day
job.
This
is
what
we
do
it
for
fun.
This
is
what
we
enjoy
doing,
and
this
is
what's
special
about
this
community.
A
So
how
do
we
make
it
work?
How
do
we
make
sure?
The
community
really
works
together
as
one
being
open
for
new
ideas.
We
think
there
are
three
things
that
are
special
about
the
community.
The
first
thing
is
the
special
interest
groups.
The
second
is
the
value
of
transparency.
We
keep
hearing
it
from
previous
sessions
right.
That
is
something
that
we
are
demonstrating
in
our
community,
and
the
last
thing
is
how
we
as
a
community,
learn
together.
A
So
what
are
seeds?
Everything
in
kubernetes
community
is
operating
around
six.
Six
are
a
group
of
people
working
on
a
specific
area.
Together
they
decide
what
features
they
want
to
work
on.
They
discuss
roadmap
strategy,
they
triage
issues
total
release.
They
make
decisions.
That's
the
most
important
thing:
when
a
community
is
so
big,
we
have
to
grow
leadership
and
distribute
it
I've.
Just
to
six
to
introduce
to
you
what's
special
about
them.
They
they
care
about
you,
the
users,
the
first
one
is,
the
cluster
lifecycle,
see
it's
led
by
Luke.
A
They
meet
every
Tuesday
at
9:00
a.m.
and
their
Charter
was
to
make
it
easy
to
spin
off
a
new
cluster
right,
but
not
just
for
newcomers
to
kubernetes,
but
also
for
experts,
and
they
want
to
make
sure
that
whatever
they
do,
it
is
portable.
So
you
can
use
it
on
every
platform
right,
one
of
the
advantages
of
kubernetes.
They
came
up
with
cube
ADM
in
1.4
and
what's
cool
about
their
work.
If
you
go
and
look
on,
the
notes
from
their
meetings
is
that
they
just
don't
just
care
about
the
cube
ADM
their
new
solution.
A
They
are
also
investing
of
how
to
converge
all
the
different
solution
that
out
out
there
right
now
in
the
community.
They
want
to
make
sure
that
we
provide
a
choice,
but
also
we
don't
confuse
you
right
of
what
the
right
tool
for
you
to
choose.
The
second
sig
is
the
UIC,
it's
led
by
Dan
and
pewter,
and
they
meet
every
Wednesday
at
4:00
p.m.
central
Eastern
time
right.
So,
if
you
are
from
Europe,
it's
probably
a
better
stick
to
join
and
they
wanted
to
make
sure
that
users
can
do
their
job
right.
A
So
what
our
user
doing
last
year
in
cube
con
there
was
a
user
survey
that
they
did
and
based
on
the
result,
they
found
out
what
you
care
about
that
you
want
to
know
how
to
do
troubleshooting,
for
example,
and
when
they
build
the
new
features
of
the
dashboard.
They
thought
about
that
they
thought
about
the
users
and
they
were
working
with
usability
experts,
for
example,
and
graphic
designers
to
make
sure
the
solution
is
the
best
out
there
and
it's
a
great
thing
to
say
great
job.
A
UI
I
think
this
is
what
you.
A
It
was
really
amazing,
and
there
is
a
great
session
about
it
and
in
the
next
couple
of
days,
keeping
two
things
aligned
is
easy
right.
We
just
need
to
make
sure
that
loop
talk
to
Dan
and
Parata
and
we're
good,
but
we
have
twenty
two
six
and
we
have
more
six.
Coming
up,
it's
important
to
mention
that
six
in
the
kubernetes
community
don't
map
to
a
different
repo.
It
means
that
everything
needs
to
work
together
as
one
project.
It
means
that
everybody
needs
to
play
nicely
with
others
right
and
they
have
to
talk
together.
A
A
It
also
gives
you
the
tools
to
be
to
act
on
that
right
to
act
on
the
information
and
also
it
helps
to
unbowed
new
members.
So
we
saw
before
that
the
community
is
really
at
the
top,
with
a
check
having
making
comments
on
issues
right,
and
why
is
that
everything
we
discuss
is
documented
on
the
github
issues,
every
functional
decision,
everything
you
considered
every
alternative
we
considered.
So
if
you
are
newcomers
to
the
community-
and
you
want
to
ask
like
why
didn't
you
choose
that?
A
A
So
all
everything
will
create
items
in
that
repository
and
we'll
make
sure
that
they're
transparent
about
the
work
and
the
pros
progress,
and
we
have
a
special
working
group
rpm
working
group.
They
are
responsible
to
review
all
the
features
there
and
make
sure
that
everything
makes
sense
and
it
provides
a
comprehensive
platform
for
you
to
use
and
that
you
don't
have
overlapping
or
think
that
confuse
you
later
on.
The
future
repository
is
also
for
you.
If
you
want
to
know
what's
coming
up
in
1.5,
and
you
can't
wait.
A
I
can
understand
that
just
go
to
github
looking
at
future
repository
everything.
Is
there
the
functionality
where
the
documentation
is
ready
or
not?
Maybe
it's
an
opportunity
to
help
us
with
that,
and
this
is
a
really
important
tool.
But
this
is
not
enough
right.
How
can
someone
actually
walk
with
all
this
information?
It
can
be
overwhelming.
This
is
why
we
have
the
community
meetups.
Every
Thursday
10:00
a.m.
A
we
meet
together
over
a
video
conference
call
and
we
see
Sarah
Sarah
is
our
community
manager,
I'm,
pretty
sure
she's
here
somewhere
NextEra
and
it's
always
a
nice
thing
to
see
right,
because
she
will
greet
us-
and
she
will
say
good
morning
and
good
afternoon
and
good
evening
and
we'll
celebrate
everything
that's
happening
in
the
community.
We
will
start
with
a
demo,
usually
from
someone
from
the
community
showing
a
new
product
or
a
new
integration,
and
then
we
will
have
one
of
the
six,
for
example,
demonstrating
a
new
feature
and
then
we'll
talk.
A
A
We
take
it
really
seriously
the
responsibility
for
your
productions,
so
it
means
that
when
we
release
something,
we
want
to
make
sure
that
we
put
a
quality
bar
really
high.
So
we
make
a
community
decision
when
we
are
ready
to
release
something
we
will
try
out
issues
together
when
there
is
something
that
is
not
working,
we'll
make
sure
that
people
are
checking
it
on
bare
metal,
probably
from
Red
Hat
and
then
we'll
have
maybe
adjusting
working
on
AWS
and
people
from
a
our
team
or
just
testing
it
on
GCP
we
more
won.
Actually
it
works.
A
But
we
don't
know
everything
and
I
would
lie
if
I
would
say
it's
easy
to
manage
such
a
big
community
and
we
make
mistakes.
So
the
important
thing
is
the
community
we're
engaged
to
learn
together
and
to
improve,
and
we
are
really
engaged
in
investing
a
lot
of
time.
So
this
is
a
short
gift
from
our
latest
retrospective.
A
You
might
say
retrospective.
What's
new
about
that,
we
do
retrospectives
all
the
time.
When
was
the
last
time
you
did
retrospective
with
strangers
with
people,
you
don't
actually
only
know
their
github
handler
right
and
now
you
need
to
come
up
and
say
this
is
what
went
well,
but
this
is
where
we
made
mistakes.
I
love
our
community
retrospectives,
the
first
one
we
scheduled
for
one
hour.
We
had
many
things
to
discuss.
A
A
So
if
there
is
one
thing,
I
want
you
to
remember,
and
probably
from
this
whole
conference
you
hear
about
it,
you
will
hear
about
it
a
lot.
Is
it
kubernetes?
It's
not
just
an
open
source
technology.
It's
an
open
community
kubernetes
make
it.
It
makes
it
easier
to
run
software.
We
as
the
community
make
it
easier
to
run
software
on
top
of
kubernetes
when
I
came
up
and
made
this
slide.
Originally
I
had
two
parts
of
it
right,
so
the
top
one
was
companies
contributing
to
kubernetes
and
the
lower
part
was
about
users
using
kubernetes.
A
But
this
is
not
the
case
with
our
community
right.
We
just
heard
Sam
from
box
and
they've
been
sharing
they've
been
converting
code
to
the
project
when
we
started
everybody
are
doing
both
right
and
that's
something
that
is
very
important
for
us.
So
if
you
as
users,
want
to
contribute
back
to
the
community,
it
can
be
with
code,
it
can
be
by
arranging
meetups.
It
can
be
by
sharing
your
experience
and
sharing
some
best
practices
within
the
community.
So
now
probably
everybody
are
thinking.
A
How
can
I
join
this
fun
place
to
work
it
and
it
is
fun,
I
love
our
community.
So
definitely
we
would
like
you
to
join
us.
We
want
to
hear
more
from
you.
We
want
to
get
feedback,
we
want
to
learn
from
your
experience
and
even
with
that,
we
want
to
get
better.
So
we
will
be
introducing
a
new
onboarding
program
and
this
will
be
with
the
help
of
Intel
what
we
call
class
zero.