►
Description
The CNCF End User Community are collaborating on a new initiative to help teams understand:
* what technologies are actively being used by end users
* whether they would recommend them
* how usage patterns are changing
Join this webinar to understand the CNCF Technology Radar, a new regular feature from the CNCF, and get a sneak peak of what the CNCF End User Community think about Continuous Delivery.
Presenter:
Cheryl Hung, Director of Ecosystem @CNCF
A
Alright,
let's
go
ahead
and
get
started.
I'd
like
to
thank
everyone
who
is
joining
us
today.
Welcome
to
today's
CMC
of
webinar.
What
end
users
really
recommend
for
continuous
delivery.
I'm
Kristy
tan
marketing
communications
manager
at
CNCs
I'll
be
moderating
today's
webinar.
We
would
like
to
welcome
our
presenter
today.
Cheryl
hung
director
of
ecosystem
at
CNCs.
Please
note
that
the
recording
and
slides
will
be
posted
later
today
to
the
CMC
F
webinars
page
at
CNCs
IO,
slash
webinars.
With
that
I'll
hand
it
to
Cheryl
to
kick
off
today's
presentation
taken
away,
Cheryl
cool.
B
B
So
it's
called
the
CNC
F
technology
radar,
so
a
little
bit
about
me
and
what
I
do
at
CN
CF.
So
my
goal
really
is
to
drive
the
adoption
of
cloud
native
technologies
like
kubernetes
prometheus
and
the
dozens
of
other
projects
hosted
by
the
CN
CF
and
as
part
of
that,
I
focus
primarily
on
end
users.
So
these
are
companies
and
people
and
teams
that
are
adopting
cloud
native
and
making
sure
that
they're
successful
and
they
understand
how
to
work
with
the
open
source
ecosystem.
B
B
So,
after
several
years
of
hearing
some
of
these
really
great
discussions,
I
wanted
to
find
a
way
to
take
these
discussions
and
share
them
more
publicly,
but
in
an
aggregated
or
anonymized
way,
and
that's
what
this
technology
radar
is.
It's
a
CNC
F
initiative,
that's
supported
from
the
end-user
community
with
the
goal
to
share
what
tools
are
actually
being
used
by
end
users,
whether
they
would
recommend
them
and
look
at
of
these
140
odd
companies.
B
So
to
begin,
what
is
a
technology
radar,
so
the
original
technology
radar
came
from
a
consultancy
called
thought.
Works
they've
been
building
this
and
using
this
format
for
over
a
decade
since
2010,
and
it's
been
adopted
by
a
lot
of
other
companies
as
well,
and
this
is
their
latest
one,
so
they
publish
one
per
year,
and
this
is
what
the
radar
looks
like.
B
So
the
metaphor
behind
a
radar
is
that
things
that
are
in
the
middle
are
the
most
interesting
or
worth
sort
of
looking
at
or
they're
coming
up
in
popularity
and
as
you
move
further
out
of
the
wings,
these
ones
are
perhaps
some
some
good
recommendations,
but
maybe
only
for
specific
use
cases
and
we
go
as
we
go
further
and
further
out.
These
are
the
technologies
that
are
fading
away
or
not
being
used
so
much
nowadays,
and
the
thought
works
model
is
that
this
encompasses
not
just
tools
but
lots
of
different
things.
B
So
some
of
these
might
be
techniques,
they
can
be
platforms,
they
can
be
tools
or
they
can
be
languages
and
frameworks,
and
so
this
is
divided
into
quadrants
and,
for
example,
you
can
looking
at
platforms
since
we're
in
cloud
native.
You
can
see
that
thought.
Works
has
suggested
that
net
core
and
sto
maturing
or
ready
to
adopt
and
these
projects
list
it
down
on
the
side
here
were
all
in
the
trial
phase.
B
This
set
of
projects
are
in
assess,
assess,
meaning
you
should
consider
it
if
you're
looking
for
a
new
solution
and
hold
meaning,
you
should
consider
doing
something
else.
So
in
this
case
they
have
node
overload
I'm,
not
quite
sure
what
node
overload
actually
means,
but
thought
Works
has
recommend
that
you
hold
on
it.
Okay
and.
B
B
Trial
says,
we've
used
it
and
we
found
it
successful
and
we
think
you
should
also
be
looking
at
this
assess
means.
We
tried
it
out
and
we
think
it's
promising,
maybe
for
certain
use
cases,
but
maybe
it's
lacking
certain
features
or
it's
not
yet
as
mature
as
those
that
are
going
to
be
in
trial
and
adopt,
and
then
the
last
category
is
called
hold
so
hold
means.
B
B
Here
are
the
changes,
so
the
most
important
one
is
that
this
is
a
community
driven
initiative,
so
thought
works
and
all
of
the
other
companies
that
are
using
technology
radars
are
using
them
to
say
this
is
what,
within
our
own
company,
we
think
is
important
and
not
important,
as
this
is
a
community
driven
one.
The
hundred
and
forty
odd
companies
and
end-user
community
are
the
ones
who
Tribute
the
data
and
curate
it.
So
the
goal
is
to
look
broadly
across
a
range
of
companies
rather
than
from
a
single
company.
B
So,
following
you
know,
continuous
delivery,
you
could
say
we're
going
to
go
small
and
often
so,
instead
of
doing
a
hundred
items
once
per
year,
we're
going
to
do
ten
to
twenty
items
once
per
quarter,
and
this
is
for
two
reasons.
One
is
that
cloud
native
moves
really
really
fast.
So
if
we
just
left
it
from
one
year
to
another,
everything
would
change.
It
would
just
not
be
fast
enough
to
keep
up.
The
second
reason
is
that
means
that
the
visual
graphic
itself
is
a
little
bit
simpler
and
easier
to
understand.
B
So
I'm
going
to
talk
through
the
methodology
and
how
we
actually
got
this
data
from
those
140
ish
companies
how
we
use
those
to
create
the
final
version
of
the
radar
and
then
show
you
the
actual
results.
Just
so
that
you
understand
the
methodology
and
the
reasoning
of
why
things
end
up
in
certain
in
certain
wings.
B
If
there
were
projects
that
they
use
that
were
not
listed
here,
they
can
also
add
them
down
on
the
left
hand
side.
So
as
this
is
a
Google
Spreadsheets
you'll
note
that
this
is
not
anonymized
within
the
group,
so
every
company
can
see
within
the
end-user
community
can
see
what
the
results
were
from
other
companies,
and
here
are
the
results
that
we
got
so
I've
blacked
out
all
of
the
names
of
the
companies.
B
You
see
this
actually
wraps
around
from
here
to
here,
because
33
companies
told
us
what
they're
doing
with
continuous
delivery
and
they're
color
coded.
So
you
can
see
green
is
adopt,
this
Louie
green
is
trial,
yellow
is
assess
and
red
is
hold.
So
once
we
collected
this
data,
you
can
look
at
this
by
row.
So
what
do
companies
across
the
end-user
community
think
about
specific
tools,
and
then
the
challenge
is
to
find
one
or
two
choose
one
final
level
for
each
tool
to
end
up
in
that
kind
of
fairly
summarizes
the
range
of
opinions
and.
B
After
sorting
them,
so
it's
a
bit
easier
to
see.
This
is
what
I
came
up
with,
so
the
solutions
that
had
the
broadest
positive
consensus
went
in
adopt.
So
in
this
case,
flux
and
helm
both
had
a
plenty
of
companies.
That
said,
they
would
and
a
couple
that
were
saying
hold,
but
on
the
whole
positive
consensus,
those
that
had
several
positive
recommendations,
but
maybe
there
were
a
few.
B
B
B
This
is
a
little
bit
where
the
editorial
judgment
comes
in,
because
you
could
certainly
argue
you
know.
Maybe
this
level
this
set
of
results
should
be
in
here.
Well,
maybe
they
should
move
between
the
areas,
but
this
is
roughly
what,
as
an
editor
I
think
his
opinion
is
fair
to
those
answers,
and
then
the
third
step
in
this
is
to
look
at
the
patterns
in
the
themes,
so
these
patterns
might
include
things
that
were
not
present,
and
maybe
you
expected
them
to
be
or
they're
just
somehow
otherwise,
interesting
or
surprising.
B
Remember
that
this
technology
radar
is
not
a,
it
could
never
be
completely
objective
right.
It's
not
the
CN
CF
saying
you
should
do
this
or
you
should
do
that.
If
projects
or
product
is
not
recommended
here,
it
doesn't
mean
that
there
was
no
value
to
it.
It
just
means
that
from
this
particular
cohorts
of
companies
from
the
hundred
and
seventy
seven
data
points
that
they
had
submitted.
These
were
the
results
that
that
data
reflects,
and
the
idea
about
doing
this
on
a
regular
cadence
is
that
these
things
will
change
over
time.
B
B
Okay,
so,
hopefully
now
you've
understood
how
the
actual
methodology
behind
the
radar
and
how
it
was
created.
So
what
does
the
final
way
to
look
like
alright?
So
this
is
it
this
is
it
so
you
can
see.
First
of
all,
this
is
actually
a
half
radar,
a
half
circle.
This
is
just
to
make
it
easier
to
read,
especially
on
a
small
screen,
and
you
can
read
this
as
flux
and
Hjelm
were
both
short
showed,
broad
consensus
and
the
widest
adoption
across
these
companies.
Positive
recommendations
to
adopt
circle,
CI,
customize
and
get
lab
fell
into
trial.
B
So
these
were
mostly
positive
recommendations,
maybe
a
few
against,
or
maybe
just
not
enough,
not
as
much
data
compared
to
the
ones
that
are
in
adopt,
and
then
you
can
finally
see
all
of
the
items
that
are
in
assess
and
these
can
be
in
assess
because
they're
too
new
and
there
just
isn't
enough
data
to
make
a
judgment
one
way
or
another,
or
it
could
be
that
the
there
is
a
very
large
range
of
disagreement,
a
large
range
of
opinions,
because
I
know
that
people
the
first
time
they
see.
This
will
go.
Why
Jenkins?
B
That
is
where
editorial
opinion
comes
in,
but
the
the
goal
of
this
is
not
to
say
because
everybody's
heard
of
this
project,
therefore
it
should
be
higher
or
because
I
don't
like
this
project,
it
should
be
lower.
Instead,
it's
a
reflection
of
the
actual
data.
That's
real-world
companies
and
people
are
using
okay.
B
B
So
the
first
one
was
that
companies
don't
just
pick
one
CD
solution
and
stick
to
it.
A
lot
of
the
answers.
A
lot
of
the
companies
had
tried
anywhere
up
to
ten
options
and
actually
adopted.
Maybe
between
two
to
four
and
in
particular
some
of
the
larger
enterprise
companies
built
their
own
in-house
tours,
and
then
they
open
sourced
some
of
the
components
so
lunar
way
is
open
source.
Something
called
release.
Manager
box
for
cubicle,
cube,
applier
and
stack
sets
controller
from
zalando.
B
So
the
other
thing
that
I
thought
was
interesting
in
that
none
of
the
public
cloud
managed,
but
options
were
suggested
and
listed
by
the
end
users.
This
could
be
because
there
is
an
actual
preference
for
running
your
CD
solutions
in-house
or
it
could
just
be
a
reflection
of
the
options
and
the
features
that
were
available
a
few
years
ago,
when
these
companies
were
choosing
what
solution
to
use.
B
So
if
you
are
somebody
who
is
looking
for
a
new
CD
solution,
you
should
consider
jenkins,
but
you
should,
at
the
same
time,
consider
other
tools
that
are
supporting
modern
concepts
like
'get
ops,
and
that
is
why
flux
has
ended
up
also
in
the
adopt
phase.
So
again,
remember
that
this
is
June
2020.
This
is
the
snapshot
in
time
as
it
is
today.
If
you
were
choosing
a
continuous
delivery
solution,
what
would
you
recommend
to
other
people
and
from
the
33
companies
that
responded?
This
is
what
they're
recommending.
B
Okay,
so
that
was
the
technology
radar,
so
if
you
want
to
learn
a
little
bit
more
about
it,
these
are
the
CNC
of
projects
that
I
mentioned,
helm,
Argo
and
flux
worth
taking
a
look,
and
we
also
have
case
studies
which
are
focused
on
continuous
delivery.
So
you
should
go
to
this
link
to
check
out
the
Babylon
health,
CD,
CI,
CD
case
study
and
similarly
for
into
it.
B
Okay,
so
what
is
next,
so,
first
of
all,
I
really
hope
that
you
found
it
interesting
and
it
sparked
some
discussions
and
sparks
your
own
opinions
and
thoughts.
What
did
you
find
surprising?
What
did
you
expect
and
what
are
things
that
you
expected
to
see,
but
they
weren't
there
and
I'd
love
to
hear
what
you
think
about
it,
and
if
you
have
feedback,
how
can
we
make
this
more
valuable
or
what
are
things
that
we
should
be
doing
or
shouldn't
be
doing
for
this,
then
please
email,
any
thoughts
to
info
at
CN,
CF,
dot,
IO.
B
B
So,
as
I
said,
we're
publishing
this
on
a
quarterly
cadence.
The
next
one
is
going
to
be
in
September
2020,
so
between
now
and
September
2020.
If
you
have
an
opinion
about
what
a
particular
use
case-
or
you
want
to
learn
about
some
see
what
end-users
recommend
for
scenario,
then
you
should
go
to
this
link
and
that
will
redirect
you
to
a
github
issue
where
you
can
add
your
own
suggestions,
vote
upvote
down,
so
examples
of
these
might
be
security.
What
are
end-users
thinking
about
or
using
for
security?
B
What
are
they
doing
for
storage
well,
1
times?
Are
they
using
or
one-time
tools
and
what
service
tools
they're
using
all
this
could
be
something
different.
For
example,
this
could
be
what
is
financial
services
using
the
cloud
native,
so
the
the
final
choice
will
be
made
by
the
editors
but
we'd
love
to
get
your
thoughts
and
your
votes.
B
And
lastly,
as
I
said
before,
this
data
is
shared
within
the
end-user
community.
So
if
you
are
a
end-user,
if
you're
adopting
cloud
native-
and
you
want
to
find
out
exactly
who
is
using
each
projects,
we
to
the
detail-
comments
that
they
left
alongside
them,
then
please
join
the
end-user
community.
You
can
go
to
this
link
to
find
out
how
and
then
for
future
tech
radars.
The
the
target
is
for
those
to
be
created,
curated
and
the
themes
to
come
from
representatives
of
the
end-user
community.
B
A
Very
much
great
thanks
so
much
cheryl
for
a
great,
informative
presentation
and
thanks
again
to
everyone
who
joined
us
today,
a
reminder
that
the
recording
in
the
slides
will
be
posted
later
today
to
the
CNCs
webinars
page.
We
everybody
has
a
great
day
and
we
look
forward
to
seeing
you
at
a
future
CN
CF
webinar
thanks
everyone,
bye-bye.