►
Description
Keynote: Kubernetes Secret Superpower - Chen Goldberg & Anthony Yeh, Google
About Chen Goldberg
Chen Goldberg is a technology leader with +18 years of experience leading engineering teams. In her current role as Engineering Director, she leads Google Container Engine (GKE) and the OSS Kubernetes project engineering team in Google Cloud. Her team is the largest team working on Kubernetes today and is committed to Kubernetes success and enabling open cloud.
About Anthony Yeh
Anthony is an engineer on the Kubernetes Engine team at Google, focused on developing tools and best practices for making complex workloads self-managing. Before Kubernetes, Anthony worked on Vitess, the cloud-native MySQL clustering system at the heart of YouTube's main database.
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
A
A
A
Think
of
a
platform
that
will
allow
you
to
quickly
build
cloud
native
applications.
It
will
have
all
the
primitives
and
the
patterns
you
need,
like
declarative
style,
API
built
in
automation,
a
policy
enforcement
mechanism,
and
not
only
that
you
can
take
all
of
that
and
reuse
it
and
generalize
it
and
make
it
specialized
for
your
own
needs
and
don't
worry.
It
won't
create
any
friction
for
the
developer,
the
user
or
the
operator.
They
wouldn't
need
to
learn
anything
new
and
on
top
of
it,
it
runs
everywhere.
A
I've
been
focusing
my
entire
career
in
building
tools
to
increase
productivity
for
engineers
when
I
started
my
career
some
years
ago,
I
led
the
team
with
a
similar
chart.
Our
goal
was
to
build
a
new
platform
to
increase
engineers
velocity.
Yes,
it
was
a
different
technology
stack,
but
we
did
build
that
and
we
did
everything
for
those
developers
formalin
during
the
UI
2
database,
optimization
monitoring,
logging,
everything
and
we
were
successful.
It
was
super
easy
to
new
applications.
Customers
were
very
happy.
We
even
enabled
mobility
between
teams
of
developers
in
retrospective
when
I.
A
Look
in
on
that
platform
that
we've
built
I
think
we
had
two
main
flaws
in
it,
the
first
one
it
wasn't
extensible.
This
means
that
every
time
there
was
a
new
UI
attack,
for
example,
or
any
kind
of
technology,
a
new
use
case,
it
was
sometimes
impossible
or
just
very,
very
hard
to
integrate
it
into
the
platform.
And
the
other
point
was
that
we
deliver
that
to
our
engineers
as
a
black
box,
and
now
they
didn't
kill
how
the
platform
works
until
it
breaks
and
as
much
as
we
think
of
ourselves
as
great
engineers.
A
A
A
Yes,
this
is
be
honest.
That's
important!
None
of
it
is
new.
Ok,
we
are
still
solving
very
similar
problems
for
a
very
long
time.
I
think
kubernetes
and
its
ecosystem
can
be
that
platform.
I
started
with
kubernetes
already
have
many
of
the
plain
primitives
and
support
for
cloud
native
applications
like
scale.
It
can
run
all
type
of
workloads,
but
kubernetes
is
also
open.
We
designed
it
with
flexibility
and
accessibility
in
mind
to
allow
new
functionality
to
be
built
in
in
a
seamless
way.
That's
why
there
is
such
a
large
ecosystem
around
the
kubernetes
project.
A
Many
times
when
you
add
new
functionality,
you
have
to
compromise
the
usability
of
that
feature
or
just
introduces
a
different
view
experience.
But
when
extending
the
system
in
a
native
way,
you
actually
get
to
use
the
same.
Api
machinery
cube
cuddle
the
UI,
the
API,
and
when
you
look
into
the
system,
you
feel
like
you're
in
a
familiar
territory
and
of
course
it
runs
everywhere,
making
it
an
open,
hybrid
platform.
A
Now,
let's
take
a
deeper
look
into
kubernetes
Brian
grant
created
this
diagram
to
capture
the
compass
cope
of
this
project
and
also
help
lead
the
discussion
of
what
kubernetes
is
and
what
should
be
its
roadmap.
He's
gonna
talk
in
his
keynote
tomorrow,
exactly
about
it,
so
make
sure
you
don't
miss
it.
As
you
can
see,
it
is
much
broader
than
container
orchestration.
You
know.
I
just
saw
the
the
website
that
healthy
showed
of
what
kubernetes
is.
We
have
to
update
that
website.
A
It
started
with
the
goal
to
increase
our
own
stability
sustainability,
but
as
we
advanced
and
the
project's
mature
I
think
the
project
is
now
ready
for
all
of
you
to
use
those
extensions
and
build
on
top
of
it.
I
wish
I
could
have
covered
everything
here
in
this
talk,
but
it
will
take
us
days.
There
will
be
many
many
great
talks
in
the
next
couple
of
days
discussing
different
aspects
of
the
extensible
today.
I
want
to
talk
about
automation,.
A
A
The
downside
of
this
approach
that
you
actually
need
to
be
familiar
with
all
the
events
and
also
you
need
to
be
prepared
to
handle
the
scale
and
the
amount
of
events,
because
all
their
matters,
the
kubernetes
approach,
is
talking
about
this
reconciliation
control
loop.
This
is
when
we
look
at
the
current
state
understand
what
is
the
difference
between
the
current
state
and
the
desired
state
and
continuously
helping
and
working
towards
their
desired
state.
That's
what
makes
it
a
self-healing
system
and
it's
very
powerful
I,
like
the
edge
trigger
automation.
It
is
built
for
chaos.
A
A
We
have
different
ways
to
extend
the
kubernetes
api.
The
first
way
is
the
cube
aggregator
that
allows
you
to
build
your
own
api
server
using
the
kubernetes
api
machinery.
You
can
build
package
and
install
it
separately
from
kubernetes,
but
from
you
when
you
from
the
user
perspective,
it
feels
like
it's
extension
of
the
kubernetes
api
and
it's
serving
in
the
same
manner.
This
is
the
most
flexible
way
and
the
most
powerful
way
to
extend
kubernetes
people
before
me
talks
about
how
we
want
to
lower
the
barrier
for
entry
to
kubernetes.
A
The
team
has
been
building
a
PI
server
builder,
for
example,
which
is
a
set
of
libraries
and
tools
that
guide
you
through
the
process
of
building
new
API
servers,
because
it
can
be
non-trivial
coding
to
do
that,
but
you
wanna
make
it
really
really
easy
with
no
coding.
This
is
what
we
introduced
the
custom
resource
definition,
which
is
make
it
really
easy
to
extend
and
create
new
types
within
kubernetes,
and
it
does
help
accelerate
innovation.
It
makes
things
simpler
for
you,
because
you
don't
need
to
build
on
your
own
all
of
those
building
blocks.
A
This
is
just
a
few
I.
Don't
have
enough
space
on
this
slide
to
have
more,
but
I
did
want
to
show
here
a
variety
of
things
that
are
built
on
top
of
kubernetes,
starting
with
the
open
service
broker,
which
makes
it
easy
to
consume
services
in
any
cloud
native
platform
it
is
build.
On
top
of
the
cube
are
Kikaider
implementing
their
own
API
server.
A
We
have
Prometheus
rook
cublas,
which
is
a
service
framework,
Etsy
D
from
operator.
All
of
them
are
using
CL
DS.
All
of
them
have
been
extending
kubernetes
in
what
we
say,
kubernetes
native
way
and
from
the
user
experience
it
looks
the
same.
You
can
set
use
the
same
UI
you
can
zoom.
You
can,
of
course,
use
cube
color
and
at
the
same
API,
so
it
makes
it
simple,
and
when
you
look
into
the
system
you
recognize
everything,
but
we
didn't
stop
there.
We
talked
about
the
controller.
Before.
A
A
B
All
right,
thank
you
again.
My
name
is
Anthony.
Ten
explained
how
kubernetes
is
powered
by
these
reconciliation
loops
that
we
call
controllers
my
goal
here
is
to
make
writing
a
controller
so
simple
that
you
can
just
go
to
a
web
page
copy
a
sample,
make
some
changes
and
then
run
it
immediately.
Custom
resource
definition
achieved
this
level
of
simplicity
for
the
storage
step
of
adding
an
API.
It's
where
you
put
the
object
but
defining
the
behavior
of
those
objects.
B
That's
kind
of
the
most
important
part
and
we
met
a
controller,
is
now
the
missing
piece
that
kind
of
makes
that
step
also
as
simple
as
you
want
it
to
be,
if
you're,
starting
with
a
simple
use
case,
so
you
can
go
to
this
github
repo.
If
you
want
to
see
the
full
details,
I
only
have
time
to
go
through
a
quick
example.
B
So
let's
say
that
I
want
to
add
a
feature
to
a
stable
set,
for
those
who
aren't
familiar
steeple
said
is
an
API
that
is
useful
for
running
apps
that
need
these
kind
of
properties
with
like
unique
identity,
persistent
storage
order,
deployment
and
scaling,
and
so
on.
The
first
thing
I'm
going
to
do
is
just
install
meta
controller
itself.
B
So
a
metal
controller
itself
is
just
a
CRD
and
a
custom
controller.
So
it's
really
an
extension
mechanism
built
on
other
extension
mechanisms,
and
that
means
that
it
lives
totally
outside
of
kubernetes.
It's
not
part
of
the
release
process,
which
is
1/9
recently
done
very
thankful
for,
and
so
you
can
install
it
on
any
cluster.
B
So,
let's
take
a
quick
look
at
what's
in
this
controller
code,
as
I
said,
it's
JavaScript,
but
I
only
use
JavaScript
to
drive
home
the
point
that
this
could
be
any
language
you
can
use
Python
Ruby,
whatever
you
want
and
I
want
to
point
out
that
this
there's
no
imports
here,
there's
no
dependencies
all
right.
So
this
is
how
you
can
make
it
truly
any
language.
B
We
don't
have
to
write
anything
to
allow
you
to
use
your
language
and
nevertheless,
it's
still
only
about
100
lines.
It
was
101
lines
without
the
copyright
hitter
and
unfortunately
we
had
to
add
that
so
contrast
this
with
the
original
PR
that
added
stateful
said
he
was
called
Petzi
at
the
time.
This
was
24
files,
almost
3000
lines.
The
author
come
in
and
this
took
longer
than
I
expected
and,
of
course
this
only
builds
if
you
have
the
rest
of
all
of
kubernetes
code
as
your
dependency.
B
So
let's
just
go
and
see
that
this
is
behaving
like
stateful
set
all
right.
So
we
have
these
nginx
background
back-end
and
we
have
these
stable
identity,
pod,
0,
1
2
each
one
also
has
its
own
volume.
So
we
have
the
zero
one,
two
volumes
for
that
staple
set,
but
if
we
look
at
the
service,
we've
only
created
one
service
for
this
whole
thing
that
selects
all
three
pods.
So
the
feature
I
want
to
add
is
let's
say:
I
want
to
have,
in
addition
to
a
volume
for
every
pot.
B
I
want
to
have
a
service
for
every
pot,
and
you
might
want
to
do
this,
for
example,
if
you
want
to
make
sure
that
as
the
pod
moves
from
note
to
note,
it
keeps
it
consistent
cluster
IP
or
you
might
want
to
do
this.
If
you
want
to
give
a
public
IP
and
put
a
load
balancer
in
front
of
each
individual
pot
in
your
stateful
set,
let's
see
what
those
changes
look
like.
B
B
Then
we
have
a
little
helper
function
in
the
controller
itself
that
just
fills
in
the
fields
of
the
surface
template
and
finally,
of
course,
we
just
have
a
for
loop
that
creates
these
services,
so
this
is
all
stuff
that
you
could
probably
put
together
by
making
a
copy
and
add
this
in
and
then
to
deploy
this
change.
All
we
really
do
is
go
back
through
the
same
process
that
we
use
to
deploy
it
in
the
first
place,
except
this
time,
I'm
going
to
put
it
in
rename
the
config
map.
B
B
B
So
that's
all
we
have
time
to
go
over,
but
I
want
to
show
you
no
cat
set
is
just
one
example
that
I
made
in
an
afternoon.
This
is
a
list
of
some
other
examples
that
are
in
the
repo.
But
the
point
is
that
you
can
have
any
automation
that
you
want
and
most
importantly,
this
proves
that
you
no
longer
have
to
go
through
the
kubernetes
core
go
into
a
release
in
order
to
get
this
kind
of
automation.
B
The
next
stateful
set
type
of
feature
is
not
going
to
come
from
the
kubernetes
maintainer
x',
it's
going
to
come
from
some
user
who
just
says:
I
need
this.
They
go
and
do
it
and
then
they
share
it
and
I
think
this
pattern
is
gonna,
be
very
powerful.
So
I
look
forward
to
seeing
what
all
of
you
come
up
with.
Thank
you.
A
The
first
time
I
saw
this
demo.
I
thought
it
was
mind-blowing.
The
idea
that
you
can
do
something
like
stateful
set
and
instead
of
investing
so
many
quarters
and
engineering
effort
into
it
and
just
building
in
one
hungry
line
of
code,
it
can
be
a
game-changer.
It
can
be
a
game-changer
for
everybody
of
how
quickly
we
can
innovate.
A
But
what
the
question
is:
can
you
really
rely
on
that
I
started
about
talking
about
the
maturity
of
this
project?
A
cat
I
said
it's
boring,
I.
Think
one
of
the
strongest
single
signal
of
maturity
of
this
community
project
is
this
justification
program.
We
just
announced
it
last
month
and
there
are
already
over
30
logos
on
this
slide,
showing
that
the
community
is
committed
and
the
vendors
are
committed
to
make
sure
that
those
api's
are
available
everywhere
and
we're
committed
to
support
them.
A
Accessibility
is
about
empowering
anyone
can
write
an
app
a
feature
that
will
change
the
world.
What
is
missing
in
the
cloud
native
space
in
the
next
couple
of
days,
my
colleagues
will
demonstrate
some
of
the
things
that
we've
been
working
on.
All
of
them
are
leveraging
these
extensions
and
the
power
of
kubernetes
Google,
together
with
IBM,
for
example,
is
building
East
EO
an
open
platform
to
connect
managers
to
Q
micro
services.
It
is
using
CR
DS,
it
is
using
web
hooks.
Actually,
it
was
one
of
them.
A
Incentives
to
bring
web
hooks
to
beta
in
149
David
are
on
check
and
Vishnu
will
be
presenting
today
as
to
how
they
bring
machine
learning
to
kubernetes,
and
tomorrow
there
is
a
great
demo
by
Alec
Brewer
and
Aparna
Sinha
showing
how
they
are
using
open
service
broker
and
consumption
of
services
in
a
hybrid
setting.
All
of
them
are
using
those
extensions.
A
We
will
continue
to
apply
everything
we
have
learned
from
our
Google
experience
of
managing
micro
services
and
services
in
Google
scale
to
kubernetes.
We
are
working
towards
that
future
platform.
We
will
continue
investing
in
accessibility
in
application
definition,
format
and,
of
course,
extending
the
conformance
test,
but
not
only
building
the
platform
in
the
core
of
kubernetes,
but
our
plan
is
to
continue
and
make
the
kubernetes
ecosystem
richer
and
make
things
more
pieces
that
are
available
from
the
developers
experience
within
google
available
to
everybody
as
open
source
in
the
kubernetes
ecosystem.