►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projectsKeynote: Kubernetes Project Update - Janet Kuo, Software Engineer, Google
To learn more: https://sched.co/GsxP
A
A
Thank
you
all
so
today,
I'm
not
going
into
details
of
every
new
features
covered
in
this
release.
Instead,
I
would
like
to
start
by
a
first
taking
a
look
at
how
popular
kubernetes
is
today,
so
this
graph
visualizes
how
many
searches
have
been
done
globally
for
a
kubernetes
since
its
beginning
in
2014,
as
you
can
see,
kubernetes
is
clearly
trending
and
has
grown
exponentially.
A
So
I
started
contributing
to
kubernetes
in
mid
2015
and
I
still
remember.
My
first
commit
to
kubernetes
github
repository
so
because
I
joined
the
project
during
code.
Freeze
and
Co
freeze
is
the
time
that
you
cannot
check
in
any
color
unless
it's
critical
bug
fix
that
will
unblock
the
release.
So
my
first
commit
is
to
fix
the
documentation
and
I
still
remember.
During
that
time.
A
Then
we
starting
focusing
more
on
scalability
so
that
it
came
Romberg
workloads
on
kubernetes
and
we
start
simplifying
kubernetes
user
experience.
So
it
becomes
very
simple
to
create
a
crew,
binaries
cluster
and
then
we'll
start
getting
early
adopters
and
more
Enterprise
users
are
running
kubernetes.
In
production
and
we
keep
hearing
more
success
stories
from
end-users
and
how
they
use
kubernetes
to
reduce
their
operating
cost
and
be
able
to
deploy
and
run
their
applications
more
efficiently
and
because
of
kubernetes
significant
impact
on
so
how
software
is
being
written
and
how
applications
are
built.
This
happened.
A
Tella
this
year,
kubernetes
warned
the
open
source
most
impact.
A
word
and
I
feel
so
proud
to
be
a
part
of
it.
When
I
saw
the
news,
and
did
you
know
that,
according
to
a
recent
CN
CF
survey,
the
majority
of
the
respondents
are
already
running
kubernetes
in
production
and
40%
of
them
are
from
enterprise
companies.
A
So
it
is
very
clear
that
kubernetes
has
transitioned
from
early
market
of
early
adopters
to
mainstream
market
of
early
majority
users.
These
early
majority
users
have
very
different
expectations
from
early
adopters.
They,
the
early
majority
users.
They
don't
want
to
learn
all
the
ins
and
outs
of
kubernetes
of
those
details.
A
They
want
kubernetes
to
just
works
so
that
they
can
focus
on
what
they
actually
care
about,
which
is
reactive,
market
conditions
faster
and
deliver
their
business
values,
and
the
good
news
is
that
true
Benares
is
now
getting
so
solid,
so
mature
and
so
great
that
it
is
now
very,
very
boring
and
don't
get
me
wrong.
Boring
is
good.
It
means
that
lots
of
companies
are
already
using
it
and
it
just
works.
A
A
Let's
first
take
a
look
at
open
standards.
Standard
allows
developers
to
have
expectations
around
the
behavior
of
a
system
and
how
their
applications
were
wrong.
Kubernetes
provides
a
set
of
building
API
standard
building
api's
so
that
those
api's
provides
a
convenient
layer
over
infrastructure
so
that
you
can
run
kubernetes
in
all
sorts
of
different
environments.
You
can
run
it
in
hybrid,
a
multi
cloud
or
even
at
the
edge.
For
example,
I
recently
read
a
blog
post
from
chick-fil-a.
A
If
you
don't
know
what
chick-fil-a
is
it's
a
an
American
fast
food
restaurant
chain
and
in
this
article
they
described
how
they
run
kubernetes
at
the
edge
in
every
of
their
2000
restaurants,
and
that's
amazing
and
I
recommend
you
to
go
ahead
and
read
that
blog
post-
and
this
is
just
one
example-
and
in
this
conference
you
can
also
hear
how
people
run
their
crew
binaries
in
every
different
environments,
and
the
next
standard
is
conformance.
So
you
want
your
workloads
to
run
anywhere.
A
How
can
you
be
sure
that
you
and
be
deployed
correctly
and
a
given
kubernetes
implementation?
So,
with
conformance
you
don't
need
to
test
your
applications
against
every
kubernetes
environment.
When
you
see
this
certified
kubernetes
logo,
you
can
be
confident
that
you
will
get
the
required
building.
Api's
and
you'll
get
consistent
behavior.
A
A
So
infrastructure
extensibility
enables
you
to
customize
kubernetes
how
kubernetes
consumes
the
underlying
infrastructure.
For
example,
you
can
configure
your
kubernetes
to
leverage
different
cloud
providers.
You
can
also
use
different
plugins,
for
example,
different
network
plugins,
different
container
on
terms
or
different
storage.
A
Plugins
and
those
plugins
are
standardized
by
the
plugin
api's
and,
for
example,
the
plus
the
container
storage
interface,
the
CSI,
the
container
runtime
interface,
CRI
and
container
network
interface
CNI,
and
those
standardized
api's
makes
eliminates
the
barriers
to
entry
for
new
service
providers
and
that
helped
build
a
healthier
ecosystem
and
another
extensibility
is
API
extensibility.
So
we
just
have
talked
about
kubernetes
building
API
and
it
is
very
generic
and
it
covers
about
80%
of
use
cases.
But
what
about
the
rest?
20%?
What?
If
you
need
to
customize
so
with
kubernetes
api
extensibility?
A
A
What's
more,
you
can
add
your
own
API
policy
so
that
you
can
make
changes
to
your
API
resources
and
then
you
can
do
some
validations
on
them.
One
example
use
of
that
is
steel.
You
can
deploy
a
steel
on
kerbin
Aires
and
it
still
uses
the
API
extensibility
to
create
a
steel,
specific
API
resource,
for
example,
there's
an
API
resource
called
virtual
service.
A
Today
there
are
already
more
than
a
thousand
github
projects
that
are
using
API
accessibility,
including,
and
we
start
seeing
more
interesting
uses
of
API
extensibility.
For
example,
you
can
see
those
uses
for
running
machine
learning,
workloads
for
monitoring
and
for
managing
databases
or
even
for
running
for
managing
resources
outside
of
kubernetes
clusters.
A
A
So,
to
recap:
kubernetes,
open
standards
and
accessibility
makes
it
a
ubiquitous
platform
for
building
your
platform.
You
can
have
a
set
of
standard
standardized
abstractions
that
makes
your
applications
portable
across
different
environments,
and
you
will
get
consistent
behavior
because
of
conformance
kubernetes
extensibility
allows
you
to
customize
kubernetes,
however,
you
want
and
kubernetes
is
open
and
compatible,
so
you
are
free
to
choose
whatever
solutions
that
best
suits
your
needs.
You
can
use
kubernetes
api
to
manage
everything
and
everything
in
built
can
be
built
in
kubernetes
way
and
you
can
even
manage
things
outside
of
kubernetes
clusters.