►
From YouTube: Keynote: CNCF Project Update - Liz Rice, Colin Sullivan, Andrew Jessup, Sugu Sougoumarane
Description
Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18)
Keynote: CNCF Project Update - Liz Rice, Technology Evangelist, Aqua Security; Sugu Sougoumarane, CTO, PlanetScale Data; Colin Sullivan, Product Manager, Synadia Communications, Inc. & Andrew Jessup, Co-founder, Scytale Inc.
About Liz
Liz Rice is the Technology Evangelist with container security specialists Aqua Security, and also works on container-related open source projects including manifesto and kube-bench. She has a wealth of software development, team, and product management experience from working on network protocols and distributed systems, and in digital technology sectors such as VOD, music, and VoIP. When not writing code, or talking about it, Liz loves riding bikes in places with better weather than her native London.
About Sugu
Sugu is CTO at PlanetScale. He is also the lead developer and community leader of the Vitess open source project which he co-created at Youtube in 2010. Vitess has helped multiple companies scale MySQL massively. Prior to Vitess, he worked on various scaling and infrastructure projects at YouTube and at PayPal. Sugu is passionate about distributed systems and consensus algorithms. He publishes his ideas about these topics on his blog at http://ssougou.blogspot.com.
About Andrew
Andrew is the co-founder of Scytale, who are helping bring SPIFFE into the world. Find out more at https://github.com/spiffe/spiffe Andrew is an engineer, and entrepreneur with a passion for building tools that help bring simplicity to software development. Prior to co-founding Scytale, Andrew was a product manager on Google’s Cloud Platform, launching many of the automation primitives on Google Compute Engine (including Auto-scaling, Managed Instance Groups, and Deployment Manager), helping improve developer workflow with the Spinnaker and Container Builder projects, and helping improve accessibility to developers and operations teams. As an Australian in the San Francisco Bay Area, Andrew spends most of his spare time trying to sell his Midwestern wife on the virtues of Vegemite.
About Colin
Colin is the product manager of NATS (https://nats.io). He has extensive experience developing messaging products and designing distributed systems. Prior to Synadia, Colin worked at Apcera and TIBCO software.
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
B
B
B
So
writing
software
is
dangerous.
All
of
it
so
I
have
this
new
framework.
Some
of
this
may
be
new
to
some
of
you,
so
I'm
gonna
go
through
it
really
quickly.
There's
a
live
tutorial,
so
no
code.
It's
the
best
way
to
write,
secure
and
reliable
software
right,
nothing
deploy
nowhere,
okay,
but
how
you
know
you
should
if
you're
gonna
write
code
and
make
sure
you
write
documentation
even
when
I
don't
write
code,
I
write
documentation.
B
So,
let's
step
through
this
all
right.
So
this
how
you
can
get
started
first,
you
start
by
and
people
do
this
mess
it
up
all
the
time
you
don't
write
any
code.
You
see
that
so
that's
just
an
example
application,
but
you
can
imagine
it
doing
anything.
You
want.
Okay,
let's
say
you
need
to
add
a
new
feature.
B
B
B
B
All
right,
thank
you
for
letting
me
do
that.
So
now
you
have
a
solution
to
Dan's
problem
and
with
that
I
want
to
bring
up
my
co-chair,
a
new
co-chair
to
kubernetes
and
she
represents
the
people
who
are
focused
on
helping
us
secure
all
of
that
code
and
what
that
I
want
to
give
a
big
round
of
a
welcome
to
Liz
Rice.
C
Hello
and
welcome
to
keep
Kahn
and
cloud
native
Khan
here
in
Copenhagen.
It
is
amazing
to
be
here
so
over
the
next
half
hour.
We're
gonna
do
a
whirlwind,
tur
of
what's
new
and
what's
been
happening
in
the
CN
CF
projects.
Since
we
last
met
in
Austin
who
was
in
Austin
yep
a
few
hands
I'm
sure
there
are
more
of
you
come
on
and
it's
gonna
have
to
be
a
whirlwind
tur,
because
the
CN
CF
is
growing
so
fast.
C
C
The
projects
go
through
three
lifecycle
stages,
sandbox
incubation
and
graduated.
So
let's
take
a
look
at
the
projects
in
each
of
those
stages,
starting
with
sandbox.
If
sandbox
sounds
familiar
up,
sounds
new
to
you.
It's
because
this
used
to
be
called
inception
until
recently.
These
are
early
stage
projects
and
they've
been
brought
into
the
CNC
f
to
encourage
collaborative
development
and
experimentation,
and
we've
had
three
new
projects
join
since
Austin,
let's
start
with
rook.
C
The
next
project
that's
joined
at
sandbox
level
is
the
open
policy
agent,
and
this
is
a
general-purpose
engine
for
enforcing
different
kinds
of
policies
across
the
stack
in
any
system.
It's
integrated
with
kubernetes,
with
SEO,
with
docker
and
many
more
and
it's
already
in
use
by
over
20
companies
and
the
third
project
in
the
sandbox.
It's
actually
two
projects
spiffy
inspire
and
they
help
work
loads
in
a
distributed
system,
verify
their
identities
to
each
other
and
to
explain
more,
please
help
me
welcome.
Andrew
Jessup,
co-founder
of
site
help.
D
Okay,
thanks
Liz,
so
folks,
I
just
want
to
take
a
few
minutes
to
tell
you
a
little
bit
about
spiffy
and
spire,
and
to
do
that.
I
really
need
to
start
first
with
the
problem
that
spiffy
inspire
are
trying
to
solve,
which,
in
a
word,
you
could
describe
as
trust
or
in
a
sentence
you
could
describe
as
establishing
trust
between
workloads
in
a
distributed.
Software
system
and
establishing
trust
is
not
a
new
problem.
If
you've
used
passwords
or
shared
secrets
of
any
kind,
then
you've
been
you've
participated
in
establishing
trust.
D
But
what
is
a
new
problem
is
the
complexity
and
the
scale
of
the
kinds
of
workloads
that
we're
trying
to
establish
trust
between
and
that
complexity
might
be
at
the
infrastructure
level,
you're,
probably
using
a
cloud
provider
you
might
be
using
several.
You
might
be
running
on
Prem
at
the
middleware
layer.
You
might
be
using,
of
course
kubernetes,
but
then
you
might
also
be
using
a
pass
system
like
Cloud
Foundry.
D
You
might
be
running
something
like
JBoss
or
websphere
and
then,
of
course,
we're
starting
to
see
workloads
that
are
elastically
scaled
and
dynamically
scheduled
and
in
this
new
world
the
existing
manual
mechanism
of
generating
secrets
and
keys
and
rotating
them
and
distributing
them
starts
to
become,
if
not
difficult,
actually,
outright
dangerous,
and
so
recognizing
this
problem
rewinding
to
2016
a
gentleman
whose
name
may
be
familiar
to
many
of
you
called
Joe
bata
proposed
a
project.
He
called
spiffy.
D
The
secure
production
identity
framework
for
everyone
and
at
the
heart
of
spiffy
is
a
solution
to
establishing
trust
between
workloads
wherever
they
may
happen
to
be
running
crucially,
unlike
manual
key
generation
and
distribution.
Spiffy
is
entirely
api,
driven
entirely
policy
driven
and
can
be
entirely
automated.
In
other
words,
a
more
perhaps
cloud
native
solution
to
the
problem
of
trust
management
spiffy
by
the
way
is
not
a
new
idea.
In
many
ways
it
jumped
just
as
kubernetes
I
was
a
lot
of
its
inspiration
to
an
earlier
system
at
Google
called
Borg
so
to
the
spiffy.
D
D
So
what
exactly
is
the
spiffy
thing?
Well,
at
its
heart,
spiffy
is
an
API.
We
call
it
the
workload
API.
The
workload
api
is
made
available
to
our
workload,
wherever
it
may
happen
to
be
running,
whether
that's
in
a
kubernetes
cluster
running
in
Azure,
or
a
an
application
running
in
jboss
at
the
back
of
the
office
somewhere,
and
this
API
allows
a
workload
to
answer.
A
very
simple
question,
which
is
Who
am
I.
The
workload
calls
into
the
API,
the
API
and
the
infrastructure
behind
it
attests.
D
Now,
as
I
said,
spiffy
is
a
specification,
but
specifications
aren't
that
interesting.
What
we
really
care
about
is
software,
something
I
can
deploy
and
use
to
solve
a
problem,
and
so
for
that
we
built
spire
the
spiffy
runtime
environment.
Spire
is
a
set
of
software
components
that
can
integrate
deeply
into
cloud
providers
into
middleware
layers
into
truss
primitives
like
TPMS
and
HSMs.
In
order
to
be
able
to
provide
this
workload
api
to
your
workloads,
wherever
they
may
happen
to
be
running,
and
with
these
two
projects,
spiffy
and
spire.
D
We're
creating
two
very
important
or
we
think,
are
important
communities.
The
first
community
is
around
the
spiffy
workload
API
and
projects
that
are
starting
to
integrate
into
that
API
in
order
to
make
their
own
authentication
and
onboarding
experiences
easier
in
these
complex
systems
that
we're
building.
For
example,
hashey
Corp
recently
announced
support
in
vaults
for
spiffy
IDs.
That
allows
you
to
do
secure
introduction
to
vault.
C
Thank
you
so
much
Angie,
okay
right.
So
that's
the
sandbox
project.
Now,
let's
move
on
to
the
projects
in
incubation,
there
are
quite
a
few
criteria
for
getting
to
this
stage,
including
being
in
production
use
with
at
least
three
independent
end-users,
and
the
big
news
is
that
since
Austin
we've
had
two
projects
move
up
from
sandbox
to
incubation
level.
The
first
of
those
is
core
DNS.
This
provides
DNS
and
service
discovery
in
a
cloud
native
deployment.
C
Core
DNS
aims
to
be
the
default
for
service
discovery
in
kubernetes,
and
it's
in
use
today
by
many
companies.
You
know
including
SoundCloud,
sky,
betting
and
gaming,
and
at
MIT
now
one
of
the
benefits
of
being
an
incubation
project
with
the
CNC
F
is
that
you
entitled
to
a
security
assessment
and
core
DNS
was
generally
found
to
be
in
really
good
shape.
C
But
there
was
one
critical
issue
related
to
DNS
cache,
poisoning
and
that's
been
fixed,
there's
been
a
security
release
and,
as
somebody
who
works
in
security,
I'm
really
happy
to
see
the
CNCs
helping
its
projects.
In
this
way,
the
second
project
at
level
up
to
incubation
status
is
link
a
d-link
ADIZ.
Our
service,
mesh
and
service
meshes
they've
become
quite
a
big
deal
right.
So
much
so,
we've
got
a
whole
track
dedicated
to
them
at
this
conference.
C
C
Another
service
mesh
project
is
envoi,
which
provides
a
high
performance
service,
mesh
data
plane
and
acts
as
a
distributed
proxy.
The
latest
release
includes
more
options
for
core
functionality
like
load,
balancing
and
routing
we're
in
Europe,
I'm,
going
to
say,
routing,
I
hope,
that's,
okay,
better
TCP,
proxying
and
better
support
for
tracing
envoi
was
originally
developed
at
lyft,
but
now
it's
being
used
by
dozens
of
big-name
companies
like
IBM,
air,
B&B
and
stripe.
C
C
And
if
you
want
to
switch
tooling,
you
can
do
that.
Open
tracing
has
contributors
from
many
different
vendors
and
end-user
companies.
It
supports
libraries
in
nine
different
programming
languages
and
since
Austin
they've
released,
updates
for
pythons
c-sharp
C++
and
a
lot
of
examples
from
across
the
open
tracing
community
Jaeger
is
a
distributed
in
tracing
implementation
based
on
those
open
tracing
api's
and
they've
done
three
releases,
since
the
last
cue
come
with
highlights,
including
the
ability
to
archive
traces
for
longer
attention,
performance
improvements
in
elasticsearch
storage
and
a
new
c-sharp
client.
C
C
So,
presumably
every
time
you
play
a
game
that
gets
logged
somewhere
version
1.2
has
just
been
released
with
upgrades
to
the
flew
in
d.
Kubernetes
daemon
set
they've
also
been
releasing
since
austin
a
new
api
encounter
and
metrics
improved
buffer
management
and
there's
a
new
open
source
connector
for
Splunk
enterprise,
also
in
the
fluently
ecosystem
is
fluent
bit,
which
is
a
lightweight
and
efficient
log
collector.
It's
now
seeing
around
75,000
akka
pools
every
day
and
the
release
latest
release
has
several
improvements,
including
a
prometheus,
compatible
metrics
api.
C
C
If
the
name
that
sounds
familiar
to
you-
and
it
certainly
did
to
me
that
might
be
because
it's
actually
a
project-
that's
been
around
for
over
seven
years,
but
it's
recently
been
welcome
to
the
CNCs
community.
Coming
in
as
an
incubation
project,
please
help
me
welcome
Colin,
Sullivan
and
Wally
quevedo
from
cinavia
to
tell
you
more
about
that.
E
Thank
You
Liz.
Now,
let's
talk
a
bit
about
Nats,
so
Nats,
as
Liz
said,
is
a
seven
year
old
production
proven
cloud
native
messaging
system
when
I
say
messaging,
really
mean
message
oriented
middleware
that
boils
down
to
an
infrastructure
to
send
and
receive
messages
between
distributed
systems.
Ease
of
use
is
really
really
important
to
us.
So
to
that
end,
Nantz
is
made
for
developers
and
operators
who
just
want
to
do
their
job
just
want
to
spend
their
time
doing,
work
and
less
time
worrying
about
how
to
do
messaging
and
we're
new
to
CNC
F.
E
We
just
joined
in
late
March
on
behalf
of
the
Nats
team.
I
just
want
to
say
how
happy
we
are
to
be
here.
We're
really
looking
forward
to
the
future.
Nats
features
multiple
communication
patterns
so
publish/subscribe,
which
is
more
of
a
fan-out
request
reply,
which
is
one
to
one.
We
have
some
load
balancing
patterns
and
others
that's
as
highly
performant
to
the
tune
of
tens
of
millions
of
messages,
a
second
highly
available
with
clustering
and
Auto
healing
technology.
Behind
it
very
very
simple
and
cloud
friendly.
The
Nance
docker
image
is
about
seven
megabytes.
E
It
spins
up
very
quickly
no
external
dependencies,
and
we
have
got
a
very
easy
to
use
and
straightforward
API.
We
have
client
support
for
over
30
programming
languages.
Log
base
streaming
with
guaranteed
delivery
that
allows
you
to
replay
historical
data
or
just
make
sure
that
you
don't
miss
a
message
and
we
already
have
some
CN
CF
project
integrations.
E
We
have
a
Prometheus
next
exporter
to
export
metrics
from
Nats
into
Prometheus
and
a
kubernetes
operator,
a
great
contribution
store
from
pelo
Perez
net
sports
range
of
use
cases
general
messaging
in
the
cloud
microservices
transports,
control
planes
and
service
discovery.
We're
also
found
in
IOT,
mobile
and
big
data,
and
we
found
that
our
users
are
using
Nats
to
augment
their
existing
legacy
messaging
technologies
as
they
move
from
on-prem
to
the
cloud,
sometimes
even
replace
it.
E
We've
got
over
200
contributors,
30
public
repositories
about
25
million
NAT
server,
docker
hub
pools
and
7
million
NAT
streaming
server.
Dr.
Rob
pulls
a
healthy
slack
community
and
a
pretty
good
cadence
of
releases
with
about
5
NAT
server
releases
a
year.
We
have
many
users
and
adopters,
and,
and
what
we
found
is
a
common
thread
like
many
other
CN
CF
projects
is
that
Nats
is
core
to
their
business
or
their
project.
E
Even
if
you
can't
make
those
come
talk
to
us,
a
chat,
we'd
love
to
hear
from
you,
wally
ginger,
and
I
will
be
here
at
CN
CF
all
week
and
now
we'll
do
a
quick
demo
with
Nats
and
kubernetes
will
demonstrate
Nats
performance
and
availability
using
the
Nats
kubernetes
operator,
we're
gonna,
scrape
some
metrics
from
Prometheus
and
then
display
it
in
a
dashboard
in
Griffin,
ax
I'm
gonna
hand
it
over
to
Wally
who's
gonna
run
through
the
demo.
Thank
you
thanks.
F
Colin,
okay,
so
in
this
demo,
I
just
want
to
show
how
simple
it
is
to
run
Nats
and
kubernetes,
but
using
the
Nats
operator.
So
the
next
operator
makes
use
of
the
customer
source
definition
feature
from
kubernetes.
That
allows
you
to
expose
this
and
that's
cluster
types
that
allows
you
to
parameterize
the
size
of
the
cluster
which
version
of
the
server
you
want
to
use,
and
in
this
case
it
allows
you
to
use
the
sacred
the
secrets
feature
from
kubernetes
to
make
the
communication
within
the
cluster
and
secure
by
default.
F
F
It's
going
to
assemble
and
create
the
full
mesh
and
that's
closer
topology,
so
that
clients
that
connect
to
the
to
the
cluster
they
can
just
connect
to
any
node
part
of
the
cluster
and
be
able
to
communicate
with
other
clients
right.
So
now
the
three
nodes
are
created
and
we
also
have
integration
with
Prometheus
right.
So
here,
in
the
background,
we
have
the
graph
on
the
dashboard.
We
don't
have
any
traffic
at
all.
It
is
flat,
so
let's
create
a
couple
of
workloads.
G
F
So,
in
the
background
we
already
can
start
seeing
spike
from
the
publishing
for
the
client
from
the
server
we
have
reached
close
to
13
million
messages
per
second
very
small
messages,
but
and
can
be
even
idea
how
fast
the
server
is
at
processing
them,
and
while
this
is
happening
just
to
show
you
some
of
the
really
nice
features,
let's
show.
Let's
follow
some
of
the
logs
from.
F
One
of
the
one
of
the
workloads
and,
let's
start
killing
just
servers
right.
So
let's
kill
the
lead
pot,
that's
one
and
you
can
see
that
prompted
got
detected,
disconnection
and
reconnect
it
to
another
server
and
in
the
cluster
and
as
you
can
notice
by
the
TLS
scheme
here
I
mean
everything
is
happening,
secure
line
by
default
right.
C
Great
to
see
a
live
demos,
Thank
You,
Allie,
okay,
so
another
core
part
of
any
distributed
system
is
the
networking
that
connects
containerized
workloads
and
the
container
network
interface
defines
how
libraries
and
plugins
can
provide
networking
support,
since
Austin
Amazon
have
contributed.
Ecs
plugins
and
the
communities
working
towards
a
new
version
of
the
spec
I'm
told
that
actually,
at
this
conference
there
will
be
a
record
number
of
talks
about
CNI.
C
Grp
City
provides
a
modern
way
for
clients
and
servers
to
communicate
with
libraries
in
many
different
languages
and
platforms
and
support
in
proxies
like
envoi
and
nginx.
The
team
have
made
four
feature
releases
since
Austin
with
highlights,
including
web
supports,
so
browsers
can
now
talk
directly
to
G
RPC
services
and
there's
also
a
new
library
in
the
dart
programming
language.
A
core
underlying
component
of
a
containerized
system
is
the
container
runtime,
of
course,
and
container
D
joined
the
CNC
F
at
the
EU
conference
in
Berlin
a
year
ago.
C
It's
about
to
release
version
1.1,
with
support
for
the
kubernetes,
contain
a
runtime
interface
and
that's
going
to
work
with
kubernetes
one
during
10
going
forward.
Container
D
is
working
on
support
for
Windows
containers
and
quatre
containers
and
it's
an
active
community
with
over
120
contributors.
C
The
update
framework,
also
known
as
tough,
is
a
framework
to
help
validate
the
provenance
of
software
and
verify
that
it
is
the
latest
version.
It's
used
in
production
by
companies
like
docker
crown,
Flair
and
VMware
they've
had
over
a
hundred
commits
since
Austin,
and
the
latest
version
improves
the
ability
to
retrieve
target
software
from
across
multiple
repositories.
C
They've
been
awarded
a
CII
best
practices,
badge
and
they've
worked
on
improvements
to
Docs,
and
they
also
have
a
new
website
at
the
update
framework.
Come
notary
is
a
secure
software
distribution
implementation
based
on
that
tough
framework
and
they've
recently
released
improvements
for
key
rotation
root,
key
rotations
and
for
wildcard
certificate
IDs
and
then
rounding
off
the
incubation
projects.
Let's
welcome
another
new
CN
CF
project
that
has
joined
at
this
level.
C
G
So
one
is
that
transactional
data
is
exploding
and
there
is
not
many
solutions
out
there
to
solve
this
problem
and
the
second
one
is:
everybody
is
moving
to
the
cloud,
but
databases
are
kind
of
left
behind
and
this
is
a
problem
that
also
needs
solving
and
the
third
one
is
actually
a
cultural
change
where
the
DPAs
are
redefining
themselves
to
database
engineers,
which
is
more
of
an
SRE
role,
and
we
need
software
and
tools
to
be
compatible
with
that.
So
what
is
with
us,
and
what
does
it
do
so?
G
We
test
is
essentially
a
middleware
for
databases
currently
focused
on
my
sequel.
It
can
scale
indefinitely
through
sharding.
So
now
you
can
do
sharding
in
your
application,
but
it's
very
painful
and
what
we
test
does
for.
You
is
take
that
pain
away
by
just
taking
on
all
the
sharding
logic
and
more
or
less
leaving
the
application
unchanged
and
even
better
once
your
shards
reach
capacity
with
can
recharge
your
database,
underneath
with
no
change
to
the
application
and
zero
downtime
and
obviously
with
Tess's
cloud
ready
and
as
great
observability
features.
G
So
that
is
led
to
a
good
adoption
and
good
momentum.
These
are
some
of
the
users
that
are
using
with
us
in
production
and
in
fact,
actually
the
number
of
users
evaluating
with
us
is
a
lot
more
than
what
you
see
on
this
slide.
So
in
particular,
I
want
to
talk
about
JD,
comm,
up
spot
and
Stitch
labs.
They
have
been
running
with
us
on
kubernetes
for
actually
quite
a
while
now
and
they
run
at
massive
scale.
G
G
All
right
so
I'm
going
to
go
through
a
demo
in
the
interest
of
time.
I
actually
executed
the
demo
before,
because
it
takes
about
30
minutes
to
execute
I,
have
captured,
screen
shots.
So
in
this
demo,
I'm
going
to
bring
up
a
single
shot
with
test
kubernetes
cluster
generate
some
load
and
then
bring
up
sixteen
new
shards
and
we
shot
down
to
them
and
then
scale
the
load
up
by
16x.
So
you
are
starting
off
with
our
familiar
UI,
which
is
a
kubernetes
dashboard.
G
G
So
once
this
process
is
called
you
say:
ok
I'm
ready
to
cut
over,
which
is
migrated,
served
types
commands,
and
once
you
are
done,
you
can
see
that
the
chart
is
flipped.
Now
the
sixteen
shards
are
serving
and
charge,
zero
has
gone
non
serving
and
then
we
scale
our
load
using
the
cube,
cuddle
scale
command
and
voila
you've
now
scaled
from
200
QPS
to
over
3,000.
G
Now,
in
fact,
actually,
the
Vita's
demo
is
actually
less
impressive
than
what
happens
in
real
life
because
real
life
we
run
like
tens
of
thousands
of
nodes
and
millions
of
QPS.
This
is
just
to
show
how
easy
it
is
to
recharge
an
instance.
With
with
this
and
what's
new,
with
with
tests,
we
recently
added
Prometheus
integration,
those
graphs
that
you
saw
we're
built
using
Prometheus
and
graph
fauna.
We
have
brand
new
helmets
and
operators
that
you
can
play
with,
and
if
you
are
more
interested,
please
attend
my
session.
C
Great,
thank
you
CD
right,
so
we're
going
to
do
something
that
has
never
been
done
before.
This
is
the
first
time
at
a
keep
corn
and
cloud
native
con
that
we
can
talk
about
a
project
reaching
graduated
status
and,
of
course
it
is
kubernetes.
Can
we
give
kubernetes
a
big
round
of
applause
for
graduating.
C
I'm
sure
you
all
know:
Kiva
Nessie's
is
an
Orchestrator
and
it
takes
care
of
running
your
containerized
applications
across
a
cluster
of
machines
or
virtual
machines.
Version
1.10
was
released
at
the
end
of
March
and
it's
stabilizing
features
in
three
key
areas
of
storage,
security
and
networking
and
Aparna
singer
will
be
giving
us
a
full
update
on
all
of
that
right
here
on
the
keynote
stage.
Tomorrow
morning
there
are
going
to
be
dozens
of
sessions
about
using
contributing
to
extending
kubernetes
over
the
next
three
days
and
last
time,
I
looked.
C
C
You
can
go
online
and
look
up
the
the
graduation
criteria,
which
talk
about
things
like
the
scale
of
adoption
and
the
breadth
of
contributors
and
requirements
around
governance.
But
what
does
that
mean?
Really
it's
a
sign
that
the
project
has
reached
a
certain
level
of
maturity
and
I'm
gonna
use
a
cliched
to
talk
about
this.
C
It
is
a
cliche,
but
just
because
something's
a
cliche
doesn't
mean
it's
not
true
right,
so
you've
probably
come
across
the
book
crossing
the
chasm
and
this
talks
about
how
it's
relatively
easy
for
a
product
to
get
adopted
by
innovators
and
by
the
early
adopter.
But
it's
a
real
challenge
to
reach
the
mass
market.
If
you
can
cross
that
chasm
to
reach
the
early
majority.
C
We
have
barely
scratched
the
surface
of
what's
going
on
across
all
those
projects
in
the
CNCs,
but
being
here
in
person,
is
a
great
opportunity
to
get
to
know
them
much
better.
There
are
the
track
sessions
where
you'll
hear
presentations
about
everything
from
the
nuts
and
bolts
of
technical
implementation.
Through
to
the
experiences
of
end-users
in
production,
we
have
a
record
number
of
sessions
organized
by
the
projects
by
the
SIG's
and
by
working
groups.
C
This
is
where
you
can
go
and
meet
the
maintainer
and
contributors
and
get
involved
in
whatever
aspect
of
cloud
native
you're,
most
interested
they've
been
organized
into
introduction
sessions
and
deep
dives.
So
the
introduction
sessions
will
get
you
up
to
speed
about
what
the
project
is
really
doing,
and
the
deep
dives
will
get
into
the
nitty-gritty
implementation
details
and
don't
forget
the
hallway
track
being
here
in
person
means
you
can
meet
like-minded
people,
whether
you're
meeting
them
in
the
sessions
in
the
hallways
in
the
sponsor
showcase.
C
You
can
take
this
opportunity
to
discuss
your
problems
and
your
ideas
together,
because
you
are
the
community
Alexis
Richardson,
chair
of
the
technical
oversight
committee,
will
be
with
us
later
this
morning
to
talk
about
the
vision
that
the
CN
CF
has
for
the
future.
But
one
thing
is
for
sure:
it's
a
team
effort
and
it
depends
on
all
of
you.