►
From YouTube: Keynote: Stitching Things Together – Dan Kohn, Executive Director, Cloud Native Computing Foundation
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 projects
Keynote: Stitching Things Together – Dan Kohn, Executive Director, Cloud Native Computing Foundation
https://sched.co/NcT2
A
Cn
CF
is
the
organization
that
hosts
those
open
source
projects
and
runs
this
event
and
here's
a
picture
of
our
event.
Two
years
ago,
in
Berlin,
let's
zoom
in
on
the
graffiti
orchestration
containerization
microservices
our
shorthand
for
explaining
cloud
native
last
year,
our
technical
oversight
committee
came
up
with
a
much
more
expansive
characterization
the
CMC
F
cloud
native
definition
version
1.0.
It
includes
ideas
like
declarative,
api's,
resiliency
observability,
an
ecosystem
of
open-source
vendor-neutral
projects.
One
word:
that's
not
included
in
the
definition
is
kubernetes.
A
A
So
why
were
these
two
incredibly
similar
sites,
both
developed
at
essentially
the
same
time
I
found
my
answer
playing
a
game?
How
many
of
you
have
ever
played
Sid,
Meier's,
Civilization,
yeah
me
too,
and
SIF
six
is
my
12-year
olds
favorite
game,
one
of
sid
meier's
greatest
innovations
was
to
explicitly
map
out
a
technology
tree.
If
you
want
to
add
Knights
as
a
warrior
for
your
civilization,
you
need
to
have
first
developed
the
stirrup
to
domesticate
horses
and
metal
working
to
create
armor.
A
The
development
of
new
technologies
depends
on
the
availability
and
sometimes
the
ubiquity
of
other
technologies.
Both
campus
network
and
the
Facebook
depended
on
personal
computers
in
the
internet
being
in
dorm
rooms,
as
well
as
a
whole
set
of
other
technologies
such
as
algorithms
for
efficient
graph
traversal
in
this
process
of
simultaneous
invention
is
something
that
we
see
throughout
history.
Let's
go
back
further
in
time
to
1858.
A
This
is
a
picture
of
the
British
naturalist
who
collected
beetles
and
spent
his
formative
years.
As
a
scientist
documenting
the
natural
history
of
whales,
he
went
on
a
multi-year
expedition
in
the
mid
1800s
to
collect
specimens
after
reading
a
book
on
population
growth
by
Thomas
Malthus.
He
formulated
a
theory
of
evolution
I'm,
not
speaking
of
Charles
Darwin.
Another
British
naturalist,
who
collected
beetles,
studied
Welsh
natural
history,
went
on
a
multi-year
expedition
and
11
years
earlier
after
reading
the
same
book
by
Malthus,
discovered
evolution.
No
the
man
on
the
left
is
is
Alfred.
A
Russel
Wallace
in
history
knows
him
as
the
other
person
who
discovered
evolution,
quote
the
centrifugal
governor
of
the
steam
engine
checks
and
corrects
any
irregularities
almost
before
they
become
evident
in
like
mad
manner.
No
defects
deficiency
in
the
animal
kingdom
can
ever
reach
any
magnitude.
That's
Wallace
could
describing
control
theory,
which
is
central
to
how
both
evolution
and
kubernetes
work.
A
We
can
go
back
further
to
18th
to
1687
and
see
Gottfried
Leibniz
and
Isaac
Newton
independently
discovering
the
calculus.
And
finally,
we
have
John
Tyndall,
he's,
often
credited
with
first
establishing
in
1859
that
carbon
dioxide
is
a
greenhouse
gas
that
leads
to
climate
change
standing
in
for
Eunice
Newton's
foot.
We
have
the
cover
of
her
scientific
paper.
A
A
So
now,
let's
return
to
this
decade
and
the
cloud
native
definition,
a
number
of
companies
have
faced
the
challenge
of
building
and
running
applications
at
scale
and
with
the
prerequisite
technologies
having
become
available,
including
the
internet
and
Linux.
A
Cambrian
explosion
of
container
orchestrators
was
created.
A
These
systems,
each
of
which
follow
the
cloud
native
definition
enabled
these
companies
to
reach
web
scale,
with
fewer
servers
and
fewer
staff
than
would
have
been
possible
before
they
include
Alibaba,
Sigma,
Amazon,
Apollo,
Apache,
mezzos,
Baidu,
matrix
cloud,
foundry
garden,
Diego,
core
OS
fleet,
docker,
swarm,
Facebook,
Tupperware
and
finally,
Google
Borg
and
Omega.
No
just
kidding
we're
only
halfway
through
there's,
also
hashey
corp,
nomad
IBM
IBM.
A
Platform
symphony
join
Triton,
lyft,
v3,
infra,
Microsoft
service
fabric,
Netflix
Titus,
Ranger
cattle,
Red,
Hat,
open
shift,
v2
broker,
Spotify
Helios,
Tencent,
Gaia,
Twitter,
Aurora
and
uber
peloton.
So
how
are
all
of
these
organizations
able
to
develop
similar
approaches
to
their
similar
to
their
scaling
challenges?
A
You
could
say
that
the
prerequisite
technologies
were
in
the
air
and
as
Isaac
Newton
wrote,
we
stand
on
the
shoulders
of
giants,
which
is
what
Newton
was
doing
when
he
adapted
that
saying
from
Bernard
de
chartres,
which
is
what
I
am
doing
in
that
I
reused.
Those
two
quotes
from
the
fantastic
video
essay.
Everything
is
a
remix,
but
now,
let's
return
firmly
to
the
present,
we're
all
here
at
Q
con
cloud
native
con
Barcelona
many
other
technologies
had
to
be
developed
before
cloud
native
could
emerge.
A
But
why
aren't
we
at
helios
con
or
matrix
con
or
on
these
are
the
results
of
web
searches
on
some
of
the
open
source
cloud
native
offerings
over
the
last
three
years?
What
is
responsible
for
kubernetes
extraordinary
growth?
Let's
finally
try
to
answer
the
earlier
question.
Why
kubernetes?
In
my
view,
there
are
three
main
reasons:
number
one:
it
works
really
well.
A
Kubernetes
was
not
just
built
on
a
decade
of
learning
within
Google
from
Borg
and
Omega,
but
has
now
also
incorporated
key
architectural
ideas
from
Red
Hat
Huawei
and
dozens
of
other
companies
number
two
vendor
neutral,
open
source
enterprises
that
are
going
to
build
on
top
of
a
platform
want
to
see
multiple
companies
backing
a
technology,
so
they're
not
locked
into
a
single
vendor.
No
one
wants
to
have
to
pay
a
platform
tax
for
the
lifetime
of
their
application
from
the
beginning,
Google
explicitly
encouraged
developers
from
other
companies
to
take
leadership
roles.
A
A
The
project
has
been
developed
by
an
extraordinary
group
of
has
done
an
impressive
job,
onboarding
new
users.
What
has
been
called
the
time
to
first
serotonin
and
has
explicitly
worked
to
narrow
the
distance
between
the
steps
of
the
contribution
ladder
from
user
to
contributor
to
reviewer
to
leader,
we'll
be
hearing
from
too
early
in
their
career
leaders
on
this
stage
in
the
next
hour?
A
So
these
are
my
ideas
on
the
three
reasons
for
success,
but
I'd
love
to
hear
yours
either
in
person
here
at
the
conference
or
on
Twitter,
and
the
thought
I
want
to
leave
you
with
is
how
deliberate
all
three
elements
of
kubernetes
success
have
been.
To
quote
the
climate
writer
David
Roberts,
stitching
things
together.
Building
up
institutions
that
work
figuring
out
how
to
keep
diverse
interests
on
the
same
page
is
difficult
emotionally
and
intellectually.
A
The
magic
of
the
technology
tree
is
that
we
can
only
be
here
because
our
predecessors
have
developed
extraordinary
innovations
like
Linux
and
tcp/ip
and
in
a
bigger
sense,
evolution,
the
calculus
and
the
cause
of
climate
change
in
the
work
that
we're
doing
here
together
this
week.
Building
on
top
of
the
shoulders
of
giants,
maybe
neither
Swift
nor
easy,
but
is
also
laying
the
foundations
of
the
next
generation
of
innovations
which
are
even
now
being
built
on
top
of
kubernetes.