►
From YouTube: CNCF Reference Architecture Meeting - 2018-07-11
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
A
This
is
hippy
hacker,
yippee,
hey,
Chris
and
then
I
think
we
also
have
lucena
connecting
from
the
bulk
thing.
That's
just
confusing.
A
I
think
the
documents
were
great
I
think
the
landscapes
working
great
I,
don't
by
any
means
mean
to
claim.
Oh,
this
is
like
obviously
the
correct
reference
architecture
and
should
never
be
changed.
But
it's
just
not
clear
to
me
that
some
meaningful
amount
of
work
is
gonna,
move
things
around
and
then
suddenly
are
we
just
gonna
say:
oh
now,
it's
clear
right.
B
A
B
A
B
A
B
A
B
B
A
Let
me
go
ahead
and
just
again
sort
of
put
my
cards
on
the
table
and
I'm
specifically
focused
around.
What
are
the
biggest
categories
is
something
like
I.
Don't
know.
Container
registries
has
a
bunch
of
stuff
in
it,
but
they're
all
container
registries.
It
doesn't
seem
to
me
like
it
needs
attention.
C
A
But
so
like
a
few
ones
like
database
and
data
warehouse
is
really
big,
but
there's
not
an
obvious
break
up
to
me.
There's
not
it's
not
like
clear
that
you
can
just
say:
oh
well,
let's
do
sequel
versus
no
sequel
where
let's
do
clustered
versus
non
clustered,
but
there's
so
many
sort
of
Gray's
in
there.
That
I
think
that
category
probably
needs
to
stay
relatively
close
to
where
it
is
the
one
that
Kris
is
eager
to
add
is
he
has
a
new
category.
A
If
we
get
the
that
needs
to
get
scheduled
for
T
or
C
boat
and
I'm
argued
to
him
that
that
would
be
a
natural
thing
to
put
under
the
observability
and
analysis,
because
the
Hesse
engineering
tends
to
go
across
all
the
other
categories,
so
that
would
be
one
new
one
and
then,
as
I
think
in
my
email,
my
sort
of
biggest
complaint
or
unhappiness
right
now
is
with
service
man
yep
with
the
title,
secure
images,
because
I
don't
think
that's
quite
describes
what
it
is
and.
C
B
A
Okay,
I
guess
maybe
we
could
start
on
the
service
management,
so
we
had
that
email
exchange
and
I
suggested
breaking
out
RPC
as
being
a
separate
category.
A
D
B
B
A
A
A
Hi
guys
I'm
sorry
about
that.
So
let's
see
I
was
looking
for
CN
CF
reference
architecture,
mailing
list
and
how
to
reorganize.
A
A
Just
pasted
it
into
the
chat
window,
so
the
RPC
seems
separate
enough
and
I
guess.
I
would
kind
of
make
the
argument
for
the
API
gateways
that
those
for
the
open
service
broker
API
doesn't
really
belong
there
as
chip
pointed
out,
but
that
those
four
are
all
API
gateways,
which
is
like
a
real
category.
A
A
D
A
The
argument
of
combining
them
is
that
people
are
probably
only
going
to
choose
one
from
that
whole
group
you're
not
going
to
do
both
envoy
and
a
load
balancer,
and
then
we
still
have
these
last
there's
there's
now
going
to
be
four
and
other,
which
is
open
policy
agent,
reactive
interaction,
gateway,
stolen
and
the
open
service
broker.
Api.
A
B
B
A
I'm
totally
happy
with
it
being
my
rule,
is
sort
of
been
I.
Think
the
smallest
category
we
have
right
now
is
four,
which
is
source
code
management,
so
I've
sort
of
been
hesitant
to
create
a
category
with
just
one
thing
in
it,
but
changing
subject
a
little.
If
you
go
down
to
key
management
and
to
secure
images,
those
aren't.
A
B
A
A
So
my
my
takeaway
here
can
is
that
is
that
any
thing
that
we
change
will
generate
criticism
from
someone
and
I
hope.
Not
changing
anything
will
generate
criticism
from
someone
I,
but
my
suggestion
is
that
we
go
ahead
and
go
forward
with
these
changes
and
then,
when
people
complain,
we
ask
them
to
come
back
to
the
mailing
list
exact
and
proposed
an
alternative
and
I
mean
we're
just
we're
literally
trying
to
publish
a
new
version
of
this
every
month.
A
B
A
A
A
Where
rook
is
yeah
because
and
then
the
last
one
yeah
was
the
reactive
interaction
gateway.
A
And
I
think
that
can
just
go
in
the
service
mesh
one
yeah.
It
means
essentially
an
API
for
service
much
okay,
so
that
actually
solves
it.
I
mean
I'm
gonna,
do
an
email
and
announce
that
change
sorry
and
then
the
last
one
that's
tricky
is
the
open
service
broker
API.
A
No
I
ships
not
very
helpful
here.
He
says
open
serviceworker
api
isn't
an
api
gateway.
I
was
going
to
suggest
service
discovery,
but
it
doesn't
do
runtime
service
discovery
or
even
touch
data
path.
Looking
at
the
other
categories,
it
feels,
like
other
may,
be
the
best
option
that
or
service
catalog
becomes
a
category
c.
Everybody
always
wants
their
own
category
because
everyone
just
know
every
project
is
a
snowflake.
No.
B
C
B
A
Ahead
and
yeah
announce
this
to
the
list
and
see
how
much
pushback
we
get
and
then
try
and
have
it
in
the
neck
and
then
look
at
pushing
down
the
next
versions.
While
I
have
you
for
a
few
more
minutes,
though,
and
also
for
the
for
the
bulk
and
other
folks
on
the
call
I'd
love
for
you
to
look
down
at
the
host
management,
tooling,
infrastructure,
automation
and
private
cloud.
A
A
B
B
B
A
B
Okay,
so
I
like
that,
that
makes
a
lot
cleaner.
A
A
E
C
C
A
And
I
mean
we're
just
somewhat
arbitrarily
splitting
out
key
management
from
security
on
the
theory
that
there's
enough
key
management
projects
to
deserve
its
own
category
and
I'm
kind
of
fine,
with
the
idea
that
we
can
keep
splitting
out
new
things
out
of
out
of
security
over
time,
but
I'm.
Sorry
and
then
we're
moving
open
policy
agent
down
into
security,
but
is
are
there
other
changes
you'd
like
to
see.
A
A
A
E
A
Great
okay,
well
I'm,
going
to
write
up
this
right
now
before
I.
Forget
it
all
and
send
it
to
the
list
and
give
it
a
week
or
more
to
percolate,
but
this
is
actually
everything.
I
was
hoping
to
accomplish
with
this
working
group,
and
so
I
really
just
saw
you
in
a
working
group.
This
mailing
list,
so
I'd
really
like
to
just
keep
it
open
and
allow
people
to
come
back
and
complain
and
say
how
we're
doing
it
all
wrong.
A
A
B
Some
categories,
if
we
want
to
try
to
break
them
down,
do
you
know
to
your
point?
Some
of
the
categories
I
have
a
lot
in
them.
There's
any
way
we
can
segment
them
into.
You
know
not
one
or
two,
but
you
know
if
we
have
a
grouping
of
like
four
or
five,
we
can
poop
into
a
sand
subcategory
which
we
can
take.
D
D
D
D
C
D
D
A
Okay,
I
think
I'm
going
to
need
to
go.
Do
some
research
to
to
follow
up
on
that
one.
But
it's
a
fair
question
and.
D
And
then,
potentially
the
service
management
there
may
be
some
stuff
to
break
out.
Watson
noted
some
of
them
are
communication
protocols
like
the
wrist
and
the
gr
PC,
so
it
could
potentially
have
something.
That's
if
someone's
just
looking
at
protocols
for
integrating
between
oh
yeah,
we're
going
to
create
a
new
category
called.
D
D
C
C
Service
mesh
minor
would
be
an
ingress,
would
be
two
separate
subcategories,
something
like
that
or
so
service
mesh
and
what
it
the
subcategory
under
service
mesh
could
be,
how
the
community
ingress
being
one
so
we'll
balance,
handling
their
state
and
then
it's
kind
of
like
separating
by
the
problem.
It
solves
no
words
right.
The
challenges
that
envoy
tends
to
solve
all
everything
right
and
they're,
just
service
mesh,
so.