►
Description
Keynote: Introducing CD Foundation - Dan Lorenc, Tracy Miranda
Join us for KubeCon + CloudNativeCon in 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
Yeah,
so
thank
you
all
so
much
for
being
here,
especially
our
first
one
hands
up
if
you
walked
the
long
way
around
the
building
this
morning
great,
but
thank
you
for
your
effort
and
I'm
sure
there's
a
few
more
still
doing
that,
but
we'll
join
them
in
as
they
come
okay.
So
this
morning
we
are
your
hosts
with
just
some
introductions:
I
am
Tracy
Miranda
and
I'm
on
the
governing
board
of
the
CDF
I'm.
A
So
dan
and
I
have
been
working
really
hard
behind
the
scenes
to
get
CD
off
the
ground
and
planned
the
summit
yeah.
So
we're
really
excited
to
be
here
and
so
glad
that
you
could
all
join
us
today.
So
we
learned
that
this
has
actually
been
one
of
the
fastest
growing
co-located
events.
Do
you
know
how
many
people
signed
up
I.
B
So
I'll
do
a
quick
run
through
the
plan
for
today
and
then
some
housekeeping
items
before
we
get
started.
So
this
is
the
morning
schedule
here.
We're
gonna
be
starting
off
with
a
couple
project,
kickoffs
from
four
different
projects
that
are
hosted
in
the
CDF
today,
we'll
have
a
little
bit
of
a
morning
break
in
between
and
then
as
a
pretty
exciting
announcement
of.
The
original
plan
was
for
everyone
to
have
lunch
on
their
own,
but
thanks
to
our
awesome,
sponsor
Jay
Frog
we're
going
to
be
having
lunch
right
here
in
this
room
around
12:30.
B
B
And
so
there's
two
tracks
going
on
this
afternoon.
One
of
them
is
a
set
of
Bo,
FS
or
birds
of
a
feather
with
a
couple
different
topics
which
you
can
see
here
and
then
the
other
one
is
a
few
more
talks
and
panels
we'll
be
starting
off
with
an
end
user
talk
by
Salesforce
and
then
a
panel
on
the
future
of
CI
CD
with
kubernetes
and
then
finishing
up
with
a
series
of
lightning
talks.
B
B
The
BOF
is
going
on
this
afternoon
are
meant
to
be
sort
of
unconference
e
and
led
by
the
community
here.
So
if
you're
interested
in
helping
moderate
or
run
one
of
them
either
send
an
email
here
to
me
or
find
us
somewhere
in
person
during
lunch,
and
we
can
help
get
that
planned
out
and
then
finally,
the
like
the
lightning
talks,
the
the
idea
there
is
a
series
of
ten
minute
talk,
so
you
don't
need
slides.
You
don't
really
need
anything
prepared.
B
We
have
a
few
sign
ups
already,
but
if
you'd
like
to
sign
up
for
that,
I
find
one
of
us
during
lunch
and
we'll
get
you
added
to
the
agenda
as
well
and
then
one
more
very
important
rule.
I
know
a
lot
of
us
might
have
missed
a
television
show
yesterday,
I'm
flying
here,
so
no
spoilers,
at
least
until
tomorrow
did.
B
B
This
is
the
continuous
delivery
summit,
so
I
think
most
people
here
have
some
idea
of
what
continuous
delivery
means,
but
it's
basically
a
software
engineering
approach
and
which
teams
produce
software
reliably
continuously
and
quickly,
with
the
goal
being
that
your
software
can
be
released
to
production
at
any
given
time.
The
rise
of
micro
services
and
cloud
native
architectures
has
led
to
a
proliferation
in
the
number
of
teams
before
working
on
a
model
with
a
code
base
and
deploying
a
monolithic
application
only
had
one
or
a
small
number
of
environments
they
had
to
worry
about.
B
A
Yes,
so
we
see
continuous
delivery
as
something
that
should
be
really
natural
to
what
you
do
almost
like
using
gates.
Everybody
should
be
doing
it
and
we've
got
a
lot
of
research.
So
who
has
read
the
accelerate
book
by
Nicole
I?
Think
you're
gonna
hear
a
lot
more
about
it
at
this
conference,
I'd
bet
but
yeah,
but
Nicole
Fusco
and
Jess
humble
Jean
Kim.
They
wrote
the
book
on.
You
know
software
delivery
and
what
the
research
said
was.
There
is
no
trade-off
in
terms
of
going
fast
versus
breaking
things.
A
You
can
go
fast
and
not
break
things
and
I
love.
That
quote
from
Nicole,
which
says
you
know.
Software
delivery
is
an
exercise
in
continuous
improvement
and
year
upon
year,
the
best
keep
getting
better.
So
you
know
we've
had
continuous
delivery
for
a
long
time.
The
book
on
it
was
written
about
ten
years
ago.
So
the
real
question
is
you
know
why?
What
do
we
need
a
foundation
around
it?
Why
do
we
only
to
be
gathered
in
this
room?
Really?
A
So,
on
the
one
hand,
you've
just
got
like
so
many
tools.
If
you
look
at
the
the
landscape
of
what
CI
CD
tools
out
there,
there
are
so
many
different
variants,
and
it
isn't
that
we
want.
You
know
one
size
fits
all
a
one
tool
that
could
magically
do
everything,
but
it
is
challenging
for
users
to
figure
out.
You
know,
which
is
the
tool
that
works
for
my
use
case
and
if
I
use
that
tool
for
that
bit
and
this
other
tool
for
that
bit.
A
Will
they
work
together
automatically,
or
is
it
like
an
exercise
to
the
user
to
go
figure
out
how
to
make
things
work
together?
So
that's
one
of
the
big
challenges,
just
the
sheer
number
of
tools
and
trying
to
understand
how
they
work
together.
Even
the
concepts
might
be
quite
similar,
but
not
actually
be
the
same
thing.
A
The
second
challenge
we
see
is
well
simply
that
the
tech
landscape
is
changing
very,
very
dramatically
as
I'm
sure
you're.
All
here
for
cube
con,
so
you're
all
familiar
with
the
term
or
maybe
not
but
cloud
native-
is
something
that's
come
up
in
the
last
few
years
and
it
just
compromises
something
completely
different.
We
see
a
lot
of
teams
are
focused
now
on
getting
their
code
into
micro
services
and
running
them
on
cloud
native
architectures,
and
this
could
mean
things
like
you
know:
automatically
scaling
up
or
scaling
down
scaling
left
scaling
right.
A
How
do
you
do
continuous
delivery
in
that
environment?
You
know
what
changes,
if
you
can
have
all
the
resources
you
want,
you
know,
would
you
build
every
single
pull
request?
You
know,
how
does
it
change
and
how
do
you
go
about
implementing
those
changes
in
your
teams
and
then
we've
barely,
you
know,
got
to
grips
with
cloud
native
and
then
along
comes
another
paradigm,
so
we've
got
you
know
serverless
emerging,
you
know
how
does
this
continuous
delivery
change
when
it
comes
to
the
service
landscape?
A
A
A
How
do
we
make
this,
something
that
can
keep
growing
and
evolving
in
the
changing
landscape
and
then
working
with
dan
dan
was
coming
in
from
the
Tecton
side,
and
there
they
had
this
idea.
You
know
they
bought
into
the
whole
like?
Can
we
standardize
things?
Can
we
make
them
work
together?
So
it
was
really
good
to
kind
of
meet
people
with
shared
mindset
and
start
on
this
idea
of
well.
Actually,
if
we
got
a
lot
of
people
together
to
solve
continuous
delivery,
would
that
work?
Would
we
be
able
to
do
something
much
bigger
than
any?
A
One
of
us
could
do
it
ourselves,
so
there
we
started
talking
to
people
and
spoke
to
a
lot
of
people
and
over
many
many
months
and
finally
got
to
the
point
where
we
could
say
actually
there's
lots
of
people
who
buy
into
this
idea
that
we
should
have
something
dedicated
to
continuous
delivery,
and
we
should
have
a
neutral
home
where
we
can
all
come
together
and
solve
the
problems
in
this
space.
So
we
launched
back
in
was
it
work.
A
A
The
new
stack,
like
you
know:
can
this
foundation
fix
open
source
pipelines
when
I
say
yes,
we
can
but
I'm
gonna
need
all
your
help
to
do
it
and
then
even
you
know,
Forbes
we're
talking
about
it.
So
you
know
something
we
need
to
focus
on
for
continuous
delivery.
Now
and
then
my
personal
favorite
was
the
register
for
this
headline
head
of
ups
fans.
We've
got
another
TLA
for
you
to
write
down
typical
register
style.
A
A
And
if
you
look
at
our
Charter,
we've
got
our
mission
captured
there
I'm
not
going
to
read
this,
but
I've
just
highlighted
a
few
things
and
for
me
the
key
is
going
to
be
just
a
collaboration
and
integration
that
we
can
focus
on
and
that
we
we
want
to
do
that
with
you
know
all
sorts
of
practitioners,
so
you
know
developers,
testers
architects,
just
anybody,
you
can
come
in
documentation.
We
need
all
sorts
of
people
working
on
this
together.
So.
A
A
B
The
very
first
thing
that
we
decided
CDF
is
that
we
want
a
prioritized
code
over
everything
else.
Many
of
us
here
in
this
room
at
this
conference
and
in
the
CDF
themselves
are
engineers,
and
we
know
that
when
you
get
a
whole
bunch
of
different
people
in
a
room,
it's
very
hard
to
make
progress
and
we
know
that
code
is
what
people
use
to
solve
real
problems
for
real
users.
So
we
believe
that
code
comes
first
year
and
that's
where
we
got
started
with
for
initial
projects
in
the
CDF
we
have
Jenkins
here.
B
A
B
X
there's
a
new
CI
CD
platform
focused
on
delivering
cloud
native
applications
to
kubernetes.
We
also
have
spinnaker
from
Netflix
it's
an
open
source,
multi
cloud
delivery
tool
focused
on
delivering
software
with
high
velocity
velocity
and
reliability
and
then
finally
Tecton,
which
is
the
project
I
work
on.
It's
an
effort
to
define
and
standardize
kubernetes
native
building
blocks
for
CI
CD
to
help
push
in
your
ciliary
forward
and
reduce
fragmentation.
Tecton
pipelines
were
run
on
kubernetes,
but
are
designed
to
be
able
to
deliver
software
anywhere.
B
So
foundations
like
the
cdf
exists
as
a
place
where
competitors,
partners,
vendors
and
then
users
can
all
come
together
to
collaborate
in
the
open.
The
primary
goal
of
the
cdf
in
this
regard
is
to
reduce
fragmentation.
I
tracy
said
across
the
super
crowded
ecosystem.
We
have
before
it's
a
pretty
exciting
time
in
software
and
in
the
delivery
space
with
the
rise
of
containers.
B
We
finally
almost
have
a
universal
artifact
that
people
can
use
to
define
and
build
and
ship
any
type
of
software
to
any
environment,
so
we
can
finally
start
to
build
and
standardize
higher-level
pieces
for
delivery.
On
top
of
that,
there
are
dozens
of
systems
and
tools
and
vendors
focused
on
solving
similar
problems
for
users.
One
of
the
biggest
challenges
is
that
everyone
seems
to
use
a
slightly
different
set
of
terms,
but
it
can
like,
in
some
cases
and
kind
of
overloaded
everywhere.
B
Different
vendors
refer
to
things
like
workflows
and
tasks
and
pipelines
and
the
same
set
of
four
or
five
different
terms
to
represent
a
whole
array
of
different
actual
principles
underneath
so
one
of
our
first
goals
is
to
help
reduce
this
and
come
up
with
a
set
of
standard
building
blocks.
Everyone
can
use
so
I
hope
that
we
can
work
together
in
this
foundation
and
the
community
help
reduce
this
confusion
by
building
up
a
set
of
standard,
ap
eyes
and
frameworks
and
building
blocks.
A
Yes,
so
code
first,
but
culture
matters
a
lot,
so
you
can't
solve
everything
with
tools
and
then
then
you
need
to
get
to
a
point
where
you
can
change
culture,
which
is
the
real
challenge.
So
when
it
comes
to
culture,
I
think
there's
no
easy
answers.
We
go
back
to
the
idea
of
you
know,
just
collaborating
and
working
with
lots
of
different
practitioners.
A
We
have
a
few
ideas
about
how
this
will
work,
but
ultimately
I
think
it's
going
to
be
a
collective
effort
and
not
just
CDF
so
we're
here.
For
you
know,
this
is
a
co-located
event
with
cube
con,
which
is
part
of
the
cloud
native
computer
foundation,
and
we
do
often
get
asked
you
know
as
a
CDF
palliative,
CN,
CF
or
what's
the
relationship
there.
A
So
CDF
is
a
separate
foundation,
but
we
do
want
to
work
very
closely
with
the
CN
CF
and
a
lot
of
the
folks,
for
example,
on
our
board
are
also
on
the
CN
CF
board.
So
we
expect
to
be
collaborating
not
just
as
a
community
ourselves
but
with
all
the
other
communities
out
there
and
you
know,
borrowing
ideas
of
what
has
worked
well.
So
CN,
CF
and
kubernetes
has
been
the
model,
for
you
know
large-scale
collaboration
and
there's
a
lot
of
good
stuff.
We
want
to
learn
from
there,
and
particularly
things
like
special
interest
groups.
A
I
think
would
map
really
well
to
CDF,
so
we're
thinking
a
lot
about.
How
would
we
have,
let's
say,
industry,
vertical
groups?
You
know
CD,
for
let's
say
the
financial
sector
or
any
specific
sector
where
the
problems
are
unique
in
that
space
and
people
want
to
come
together
to
not
only
discuss
those
problems
but
just
share
stories
of
how
they've
gone
about
making
those
changes
inside
their
companies
and
the
little
things
have
done
to
nudge
people
into
changing
behaviors
and
creating
habits.