►
From YouTube: CNCF App Delivery 2020-05-06
Description
CNCF App Delivery 2020-05-06
A
A
A
C
We
have
a
charter
finalized
and
yeah,
and
we
are
working
on
our
user
stories
for
how
companies
and
teams
are
deploying
kubernetes
and
other
things.
You
have
projects
in
the
NAG
apps
environment
and
all
that
is
linked
in
our
our
landing
page
in
the
app
delivery
github.
So
you
can
take
a
look
there.
Yeah.
A
A
A
A
We
don't
have
a
lot
more
topic
on
the
agenda
for
today
on
project
reviews.
I
think
we
are
progressing
nicely
there
so
to
go
and
answer
this
working
group
Sara,
let's
workflows,
is
still
ongoing
on
our
site.
Same
obviously
for
artifact
of
the
others
so
far
are
with
the
TOC
right
now
is
50%
box
project.
If
he
hasn't
follows
the
TOC
call
this
week,
there's
quite
a
discussion
on
how
sandbox
projects
are
handled
now
going
forward
due
to
some
changes,
I
can
put
in
the
link
to
the
updated
document.
A
A
D
B
A
I
think
I
main
work
group
items
there's
one
thing
he
hasn't
really
been
investing
a
lot
of
time
into,
which
was
the
landscape
that
we
initially
wanted
to
work
down.
It's
like
having
a
landscape
on
earth
delivery.
This
was
always
like
going
back
and
forth,
but
nobody
really
took
the
leader
of
the
effort
to
really
move
this
forward.
A
Maybe
I
see
also
never
really
took
the
time
to
really
discuss
what
the
landscape
is
going
to
look
like
it's
not
a
lot
of
landscapes
around,
but
the
idea
was
to
reuse
the
model
that
Harry
initially
worked
on,
like
this
Abdo
liberal
and
the
layers,
and
try
to
assign
the
current
CN
CF
project
into
those
layers.
So
this
is
definitely
and
so
a
very
good
point.
This
is
something
that
we
should
be
investing
some
more
time
into
lining
currency,
as
you
have
projects
into
like
a
kind
of
landscape
following
that
model.
So.
E
Let
me
ask
a
question:
if,
if
we're
gonna,
do
we
have
a
picture
of
those
layers,
because
one
of
the
really
powerful
things
about
the
landscape
is
that
somebody
can
show
up
as
an
end-user
who's,
just
a
consumer,
because,
like
99%
of
people
who
are
involved
in
CN
CF
projects,
don't
contribute
a
look
and
nothing
they
just.
They
consume
it
and
happy
consumers
and
they
they're
trying
to
find
the
stuff,
and
so
the
experience
of
discovering
things
should
be.
What
does
somebody
who
has
to
deal
with
app
delivery
building
and
operating
applications?
E
What
are
they
going
to
be
searching
and
using
for
and
that
talk
sauna
me
and
so
I'm
curious?
What
we've
got
and
how
it
maps
to
the
kinds
of
things
that
they
do
and
they
need,
especially
since
so
many
of
us
here
are
builders
of
things
and
not
necessarily
in
that
same
mindset
of
just
a
consumer.
I
know
I'm
totally,
not
in
that
just
a
consumer
space
and
so
I'm
curious
how
that
mapping
works.
A
A
A
A
That
we've
done
it
was
also
the
one
that
was
presented
at
cube
con,
where
we
basically
put
in
like
initially
called
them
layers
and
then
refrain
from
calling
them
layers,
because
people
wanted
it
was
the
terms,
but
what
we
broke
it
down
is
more
less
implications.
As
a
mission
to
how
do
you
define
your
replication?
That
was
one
of
the
key
areas:
how
in
communities
to
actually
find
what
my
application
is
and
like?
A
What's
the
descriptor,
what
kind
of
use
then
I
would
see
the
packaging,
which,
especially
was
the
air
gap,
becomes
even
more
interesting
like
how
can
I
put
like
this
whole
thing
together
and
install
it
somewhere,
so
then
probably
lose
about
installing
entire
applications
and
those
are
something
I
think
people
are
honoring.
So
how
can
I
ship
it
and
I
have
got
my
application
like
how
can
I
ship
the
whole
thing
and
discussion
about
the
whole
thing
was
I?
A
Was
he
not
just
my
my
yellow
files
or
my
charts,
but
also
the
containers,
all
the
security
bits
and
pieces
that
I
need
and
everything
that
I
wanted
to
get
here,
and
then
it
moves
into
more
operation
lab
like
how
do
we
really
support
application
that
deployment
and
roll
out
like
lifecycle
management?
This
is
where
operators
will
fall
in
as
an
example,
but.
E
E
Okay,
so
if
I'm
a
consumer
coming
in
what
am
I
going
to
be
looking
for
when
I
want
to
discover
something
like
what
kind
of
categories
were
to
consumer
come
at
this
stuff,
first
and
say:
I
need
to
consume
stuff.
How
am
I
gonna
discover
it
like
what
are
the
different
things
they'll
want
to
to
select
in
their
landscape.
That
says
hey.
This
is
how
I'm
filtering
on.
E
B
Man,
I
was
under
the
end
this
understanding
that
the
consumers
here
for
the
output
from
from
say
gap
delivery
would
potentially
be
people
who
may
be
developers,
but
maybe
somebody's
you
know,
produced
a
package
or
maybe
a
product
owner
product
manager
says
hey
I,
want
my
package
to
I
want
to
deploy
my
package
to
my
customers
on
kubernetes.
What
am
I
going
to
what
am
I
going
to
need
for
that
I
kind
of
viewed
that
that
might
be
a
consumer
of
the
output
from
from
this
group.
Well,.
E
E
If
we're
doing
a
landscape
for
this,
that's
meant
for
people
to
just
roll
up.
I
would
expect
people
far
outside
of
say,
gap
delivery
to
do
it
because
it's
people
or
kin
saying
hey,
they're
doing
this.
So
if
we
have
to
do
it,
then
we
really
probably
need
to
note
on
there
that
the
scope
is
that
this
is
people
who
are
producing
things
for
other
people
to
consume,
because
right
now
tons
of
people
come
to
this
landscape.
B
Some
of
these
categories,
like
you
know
you
got
a
procedure
called
category
and
and
API
gateway
and
and
the
container
runtime
I
mean
these
a
general
person
that
I
would
construe
these
consumer.
You
know
isn't
going
to
be
looking
for
a
good
RPC,
you
know
solution
or
what
API
gateway
they
want
to
use
right,
they're.
Just
looking
for
the
keeping
the
apps
give
me
the
end-user
apps
right,
but
the
landscape
contains
a
lot
more
than
just
the
end.
You
our
apps.
B
It
contains
the
apps
that
that
people
will
be
using
to
to
deliver
the
apps
right,
so
there's
kind
of
layers
of
consumers.
There's
the
middle,
we're
producers,
there's
a
you,
know
the
infrastructure
producers.
It
goes.
You
know
up
and
down
the
stack,
and
you
know
my
view
and
it
might
be
the
wrong
view.
But
my
view
is
application.
Delivery
group
would
would
help
people
who
want
to
put
their
apps
up.
You
know
in
a
cloud
cloud
native
and
kubernetes
environment
right
so
would
be
more
leaning
towards
the
developer.
B
F
You
know
I'm
relatively
new
to
this
group,
so
I
wasn't
around
the
last
time
we
talked
about
having
a
landscape
for
app
delivery.
I
love
the
cloud
native
landscape
from
the
CN
CF,
but
it's
pretty
broad
in
scope,
and
so
what
I
think
you're
talking
about
here
is
saying:
let's
create
a
landscape
that
helps
people
unpack.
First
of
all,
the
categories
that
you
were
showing
just
a
moment
ago,
the
different
layers
or
we're
not
calling
in
layers
the
different
categories.
F
Those
are
prospective
categories
for
them,
bucketing
things
into
those
categories,
various
components
that
components
or
standards
or
best
practices
that
and
dress
that
category.
So
address
the
category
of
bundling
address
the
category
of
packaging
address
the
category
of
deployment
address
the
category
of
observability,
maybe
I
don't
know,
and
so
that
was
my
understanding
here,
so
I'm
not
sure
I'm,
not
getting
this
wrapped
around
the
axle.
As
you
are
Matt
on
whether
it's
consumer
producer
I.
E
B
E
F
A
Maybe
to
share
some,
but
we
have
this
initial
discussion
like
a
very
long
time
back
to
get
one
of
the
main
drivers
for
this.
Was
you
come
to
the
Callanetics
community?
Obviously
you
have
your
committee
discussed
and
running
and
then
you're
starting
to
build
Enterprise
great
applications,
and
you
start
to
have
like
all
this
enterprise,
great
effort,
delivery
problems
where
some
of
them
who
started
to
address
like
because
it
kept
on
what
are
you
specific,
but
just
a
very
simple
question?
A
A
Where
do
I
put
this
or
have
to
have
an
order
of
upgrading
or
they'll
say:
okay,
it's
great
that
a
happy
thing,
but
should
there
even
be
how
did
that
package
this
up,
that
vidcon's
gets
to
air-gap,
but
other?
What
I
see
at
least
a
lot
with
the
people
who
I
will
go
is
to
say
well
according
to
an
image
and
dr.
Mapp
is
is
not
how
you
ship
applications.
So
nobody
is
downloading
an
image
from
from
dr.
happen
in
enterprise
setting
without
properly
scanning
and
taking
those
images.
A
They
might
do
it
for
like
a
proof
of
concept,
but
I
very
rarely
see
people
just
taking
images
that
are
on
the
public,
Internet
and
installing
them
into
production
clusters.
But
then
you
realize
okay,
this
kind
of
gets
now
complicated.
So
first
I
want
to
like
be
final
with
these
premises,
and
it's
not
just
our
ticket
services
and
security
credentials
and
how
do
they
properly
get
attached
to
my
application
at
the
certain
stage
and
I
want
to
move
those
other
things
done
down
there,
and
the
question
was
Natsume.
A
B
That's
that's
a
direct
consumer
use
case.
I
believe
could
say
you
know
when
we
work
with
customers
and
they
they
start
relying
on
more
than
one
application,
which
is
really
quick
right
now,
they're
juggling
a
number
of
different
applications,
they're
downloading
from
a
number
of
different
sources
and
they're
saying
well
what
what
are
my
options
here
to
manage
this
process
right
and
this?
This
could
be
a
tool
to
show
them
hey.
These
are
the
options
that
that,
or
these
are
options
it
that
you
have
to
deliver,
deployed
a
package
to
manage
some
of
these.
B
These
items,
of
course,
I
guess
from
since
since
I'm
working
with
a
lot
of
software
vendors.
My
point
of
view
is
is
a
little
different,
but
you
know
we're
trying
to
help
them,
use
best
pack
practices
and
find
best
practices
for
for
packaging
and
managing
their
applications,
so
that
when
our
solutions
team
wants
to
integrate
their
software
with
with
one
of
our
solutions,
we
can
do
that
in
a
already
known,
reliable
way
and
and
giving
them
a
place
to
start
like
it
really
answers
the
the.
B
What
I'd
like
to
see
is
is
our
ability
to
quickly
answer
a
question
like
what
options
are
out
there
and
how
and
where
do
I?
Where
can
I
get
started
like
and
and
those
to
the
questions
that
I
hear
the
most
from
granted
from
from
developers
and
and
people
representing
software
products,
but
also
in
the
use
case
that
you
put
out
there.
B
E
I
I
kind
of
noticed
two
things
in
here,
though
one
is
the
kind
of
thing
that
you're
going
to
get
in
a
landscape
which
is
basically
just
a
dashboard
of
different
projects.
You
can
filter
by
category
and
that's
actually
not
going
to
tell
you
here-
are
good
practices
and
they're
going
to
be
people
who
disagree
on
what
the
good
practices
are,
and
why
and
how
you
you
touch
things.
You
know,
tie
things
together
and
then
they're
actually
gonna
be
what
our
practices
and
how
do
you
take
holistic
things
into
account?
E
B
B
A
A
B
E
Ooh
I
have
an
idea
on
this
because
I've
been
around
since
since
the
beginning,
when
app
delivery
was
just
an
idea
because
they
said
hey,
sig
apps.
We
need
to
talk
about
apps,
oh
there's,
kubernetes,
cig
apps,
and
we
don't
want
the
name
to
be
confusing,
even
though
they
have
very
similar
scopes
and
ideas.
So
we
need
a
different
name,
so
we're
gonna
call
it
kubernetes,
sig,
app
delivery,
and
in
talking
to
some
of
the
TOC
members,
they
have
talked
about
everything
fitting
in
here
from
like
tools
that
plug
into
visual
studio
code
and
help.
E
A
I
think
where
we
had
a
lot
of
discussions,
do
we
want
to
put
it
like?
How
do
we
structure
an
application
from
what
it
is
right
now
to
tell
me?
Well
it's
a
nice
idea,
but
it's
also
a
bit
vague
and
very
white
and
pretty
much
everything
that
I
needed
from
ok.
I
have
now
this
artifact,
which
in
most
cases
is
a
container
to
the
point
where
I
push
it
zoom
up
or
deployed
I,
run
it
and
manage
it,
and
I
eventually
get
rid
of
it
and
replace
it
by
a
new
version.
A
That
would
be
as
a
my
definition
of
from
what
we
did
back
then.
Is
we
talk
about
delivery?
I
think
my
definition
doesn't
get
wider
to
the
retirement
piece,
because
a
lot
of
people
think
ok.
Now
we
have
shipped
it
yeah,
but
you
have
to
update
it.
You
have
to
retire.
It
eventually
get
it
out
of
practice,
also
partic
updating
an
application.
It's
also
done.
Otherwise,
we
have
to
accept,
like
that
fox
world,
where
we
have
it.
Okay,
we
have
shipped
it
it's
great,
but
now
it
should
be
already
running.
So
what?
A
If
all
like,
the
observability
artifacts
there
as
well,
that
I
need
from
like
monitoring,
configuration
and
and
so
far
but
I
think
we
move
this
forward,
a
liquor
is
still
a
number
of
questions
that
we
can
agree
on
and
we're
I
guess
you
mentioned
that
working
with
customers
questions
that
they
have.
We
chose
initially
started
this
conversation.
We
can
start
by
answering
those
questions
and
a
landscape
might
fall
out.
A
white
paper
might
fall
I.
Think.
Is
there
important
course
like?
How
do
I
package
my
application.
A
Does
it
make
sense
for
our
people?
Okay,
like
the
key
questions
that
people
have
think
this
is?
These
are
all
the
things
you
have
to
think
of
when
you
put
your
first
application
into
production
like
delivering
to
all
of
those
stages,
and
also
to
your
point.
Yet
this
is
what
people
usually
ask
me
like.
B
B
A
A
I
will
just
throw
in
some
example
questions
so
that
people
just
get
started
and
for
the
next
meeting
we
can
then
go
through
those
and
then
decide
on
next
steps
and
which
one
we
want
to
tackle
and
if
just
for
the
time
being
throw
all
of
them
in
there
I
just
won't
eat
it,
try
to
structure
them
and
what
I
think
is
so
we
can
have
as
much
a
discussion.
Obviously,
if
you
disagree
under
structure
in
just,
let
me
know,
and
we
can
we
can
discuss
so
I'll-
create
it,
let's
throw
things
in
there.
A
B
A
Actually
take
care
of
this
today,
so
I'll
just
create
the
doc
and
put
it
in
here,
questions
and
share.
Why
I
think
mailing
lists
right
out
this
fear
for
everyone
to
get
this
as
a
start
just
like
to
have
them
all
in
a
box
rather
than
tearing
it
on
the
mailing
list
they
did
in
the
past,
and
usually
these
mailing
list
discussions
tend
to
get
rather
complex
and
make
the
first
form
of
collaboration
is
usually
a
Google.
Doc
is
usually
good,
because
people
can
comment
on
what
others
mean
by
this
and
yeah.
B
A
D
A
A
F
D
A
F
D
A
A
A
A
D
F
A
A
F
A
A
Okay,
good
so
then
for
the
next
meeting,
I
put
overly
the
link
to
this
question
in
the
dark
of
this
right
after
this
one,
let's
collect
the
questions
that
the
next
time
we
really
have
something
to
discuss,
and
just
maybe
one
more
thing.
If
you
have
a
question
and
you
using
a
certain
tool,
we
might
also
have
it
just
listed
in
there,
so
that
might
make
sense.
It'll
make
like
a
template
of
what
a
question
could
look
like
and
I
quote.
Your
answer
looks
like
average.
Are
you
using
which
sort
of
you
think
of
it?
A
Fulfills
the
CDF
for
footsies
requirements?
I
wasn't
there's
not
a
minute.
You
see
MDF
projects.
What
I
find
quite
fun
prison
were
interesting
yesterday
in
the
TAC
meeting
it
was
seeker
on
Tambor
was
also
reaching
out
to
other
projects
that
are
doing
interesting
things
in
their
space.
So
maybe
also
was
this
exercise.