►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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.
介绍和深入了解 TAG 应用程序交付 | Introduction and Deep - Dive into TAG App Delivery - Hongchao Deng, Alibaba & Thomas Schuetz, Dynatrace
TAG 应用程序交付专注于简化 Kubernetes 上的应用程序交付，以及改善开发者的体验。此次讨论将展示围绕运营商、混沌工程、应用交付方法和演示应用的最新发展情况。无论您是刚开始了解云原生应用交付，还是想要了解最新进展，此次讨论将基于应用交付领域的 CNCF 项目反馈，为您提供正在进行的活动信息、最新发展情况和所选定的发展趋势信息。
TAG App Delivery focuses on simplifying application delivery on Kubernetes as well as improving developer experience. This session will showcase recent development around operators, chaos engineering, application delivery methods and demo applications. Whether you are just getting started with cloud-native application delivery or getting up to speed on the latest, this session will provide you with ongoing activities, recent developments and selected trends based on feedback from CNCF projects in the app delivery space.
A
Welcome
everyone
in
this
talk,
we
will
give
an
introduction
and
deep
dive
into
the
app
delivery
tag,
we'll
talk
about
who
we
are,
what
we
do
and
what
progress
have
we
made
this
year
before
we
start
talking
about
anything,
I
would
like
to
introduce
the
speakers
a
little
bit,
I'm
hong
chao
from
alibaba
and
serve
as
the
co-chair
of
app
delivery
tech.
My
co-speaker
thomas
from
diner
chase
served
as
the
ted
lee
of
app
delivery
tech.
We
also
have
leaders
from
working
groups
of
cooperative
delivery,
chaos,
engineering
and
githubs.
A
So
what
does
our
tech
do?
We
basically
held
the
cncf
tlc
managers
projects
under
the
domain
of
app
delivery,
decides
what
projects
go
into
incubation
and
graduation
and
analyze
their
maturity
level.
We
also
write
down
materials
about
best
practice
and
publish
white
papers
about
app
delivery
domain,
so,
what's
included
in
app
delivery
domain.
A
The
first
thing
is
application
definition.
We
need
to
define
what
an
application
means
for
cloud
native
platforms,
how
we
can
make
obstructions
on
top
of
infrastructure
and
expose
application
centric
apis
like
how
to
make
sure
that
the
api
matches
the
majority
of
our
user
needs
and,
more
importantly,
how
to
extend
it
with
more
apis.
A
A
App
delivery
also
covers
how
to
design
and
develop
applications.
We
provide
best
practice
guides
on
how
an
application
architecture
should
do
and
will
fit
the
cloud
native
patterns.
Modern
applications
designed
with
such
patterns
would
benefit
from
the
community
and
the
cloud
better.
For
example,
dapper
has
empowered
modern
applications
talk
to
back-end
services
easily.
That
includes
open
source
components
like
mysql
kafka,
redis
and
many
other
cloud
services.
A
App
delivery
also
covers
application
bundling
and
package
management.
Today
we
already
have
two
top-level
cncf
projects,
ham
and
buildpack-
to
provide
solutions
to
application
packaging,
but
they
have
their
own
pitfalls
and
scenarios
they
don't
fit,
for
example,
in
ham.
It
couldn't
provide
me
the
needs
to
divide
delivery
workflow,
as
new
technologies
keep
coming
up.
We
believe
there
will
be
new
solutions
that
can
address
previous
problems
and
being
compatible
with
existing
software
packages.
Formats.
A
A
A
A
A
We
have
open
crews
to
provide
fine-grained
deployment,
upgrade
policies,
and
on
top
of
that,
we
start
to
have
some
user-facing
interface,
this
interface,
let's
user,
define
how
to
roll
out
new
application
releases,
how
to
do
a
canary
roll
out
how
much
traffic
to
be
diverted
to
the
new
releases
so
and
finally,
it
is
the
head
of
the
whole
architecture,
the
application
per
se.
Here
it
defines
the
application
abstraction
it
exposes
only
the
apis
that
application
developers
care
about.
This
is
what
projects
like
cookwell
and
argo
cd
provides
solutions.
A
B
B
B
We
are
always
talking
about
incubation
projects,
but
what
does
this
mean?
So
many
cncf
projects
start
the
sandbox
projects
and
get
more
and
more
mature
at
some
point
in
time,
while
the
entry
barrier
to
sandbox
projects
is
fairly
low.
The
next
stage
incubation
follows
a
bit
of
a
harder
process
to
get
to
incubation
a
full.
Due
diligence
has
to
be
performed
during
that
it
gets
evaluated
if
a
project
is
successfully
used
in
production
by
at
least
three
independent
end
users,
but
also
if
it
has
a
healthy
number
of
committers
and
enough
documentation.
B
B
Additionally,
the
tag
delivered
its
first
white
paper
about
operators
this
year.
This
should
give
end
users
an
overview
about
deming
queue
anita's,
but
also
deals
with
operators
beyond
cuban
eaters,
as
we
also
wanted
to
tackle
security
related
issues
in
the
context
of
operators.
We
asked
our
friend
from
tech
security
for
help
and
it
was
pretty
cool
to
work
with
them.
This
white
paper
provides
an
overview
for
people
starting
dealing
with
operators,
but
might
also
be
a
valid
source
for
those
who
get
want
to
get
deeper
into
this
topic.
B
B
The
operator
white
paper
has
been
achieved
by
a
working
group
and
the
main
purpose
of
this
group
was
to
define
what
an
operator
is.
Currently
three
working
groups
with
all
bringing
light
on
special
topics
exist
in
the
tech
app
delivery.
Additionally,
there
is
one
project,
the
potato
head,
which
is
maintained
by
members
of
the
tag,
so
that
said,
we
will
dive
a
bit
deeper
into
the
working
groups
so
I'll
hand
over
to
george
and
robert,
who
will
tell
you
a
bit
more
about
the
cooperative
delivery
working
group.
C
Thank
you,
thomas
and
hong,
as
we
just
saw
much
of
the
work
of
the
app
delivery
tag,
focuses
on
packaging,
up
business
logic
and
deploying
it
on
infrastructure,
but
the
revolution
that
we've
had
with
cloud
infrastructure
means
that
now
infrastructure
services
themselves
they're
not
servers
and
hardware
anymore.
They
are
defined
and
delivered
dynamically
as
software
like
the
software,
that
is
your
business
app
too.
D
Now
that
the
infrastructure
is
being
delivered,
that's
software
as
well
app
developers
have
to
also
coordinate
the
delivery
of
their
business
apps
with
delivery
of
software
infrastructure,
so
that
the
right
infrastructure
is
there
at
the
right
time
and
the
the
app
developers,
jobs
are
already
you
know
complex,
so
to
help
them
succeed.
We
believe
we
should
at
least
try
to
make
this
cooperative
delivery
as
simple
and
consistent
as
possible.
C
So
what
we're
doing
in
the
cooperative
delivery
working
group
is
developing
patterns
and
practices
that
will
encourage
cooperation
between
your
cloud
native
app
developers
and
wherever
they're
getting
their
cloud
infrastructure
from
so
like
as
an
example
you're
building
a
micro
service,
you
need
a
data
store
or
an
event
bus.
You
need
the
credentials
so
that
you
can
connect
to
that
and
the
address.
So
you
can
connect
to
that.
We
want
to
make
sure
that
that
gets
provisioned
and
published
before
your
act.
Microservice
starts
running
and
looks
for
it.
C
D
You
know,
but
some
of
the
first
initiatives
that
we
are
doing
right
now
is
that
we're
trying
to
gather
user
feedback
see
how
people
are.
Are
you
know
trying
to
solve
these
types
of
issues
out
there
now
and
see
how
we
can
help
with
that
and
also
gather
patterns
and
ids
in
both
code
and
on
discussion
on
github.
C
We'd
love
you
to
join
us
come
join
our
channel
in
the
cncf
slack.
It's
a
great
way
to
reach
out
asynchronously,
open
github
issues
with
your
ideas,
with
your
code
with
your
feedback,
and
if
you
want
join
our
video
meetings,
we
hold
them
the
second
and
fourth
wednesday
of
every
month.
The
exact
time
is
in
our
is
in
the
repo
thanks
so
much.
Thank
you.
Robert
thank.
B
E
E
E
The
open
get
ops
project
is
a
cncf
sandbox
project
which
holds
it
holds
all
the
lasting
programs
documents
and
code
related
to
get
ups.
That
is
the
goal.
It
seems
to
be
working
pretty
well
so
far,
some
announcements,
just
four
announcements.
The
first
is
well.
I
mentioned
that
the
open
gaps
project
is
is
now
in
sandbox,
it's
guided
by
the
working
group
and
it's
very
active
second.
D
E
E
One
important
note
here
is
that
this,
oh,
this
principle-led,
meaning
of
getups,
now
establishes
a
foundation
for
interoperability
between
tools,
conformance
and
certification
and
other
things
just
for
all
things:
getups,
okay,
so,
finally
just
a
little
bit
of
housekeeping
announcement.
This
is
mainly
so
you
know
where
to
get
info.
E
E
There
was
also
this
followed
on
the
heels
of
initial.
Very
successful
remote
only
get
opticon,
and
that
was
also
part
of
kubkani,
but
you
earlier
in
the
year.
The
next
is
that
we
we
had
a
git
ops.
One
stop
shop
that
have
major
vendors
speak
about
their
get
ops
offerings
which
all
use
flux.
In
the
case
of
this
one
event:
amazon,
web
services,
d2iq,
microsoft,
vmware,
weaveworks
and
red
hat,
so
plus
amazing
keynotes.
I
just
want
a
note,
including
brendan
burns,
one
of
the
original
kubernetes
authors.
E
E
B
F
F
At
the
outset,
I
would
like
to
thank
the
app
delivery
chairs
for
helping
curate
this
working
group
and
giving
us
this
opportunity
to
speak
about
it
now.
For
some
background
chaos,
engineering.
The
discipline
has
been
around
for
nearly
a
decade,
as
you
all
know,
put
simply.
It
is
about
injecting
random
and
unpredictable
faults
to
simulate
real
world
events
and
verify
system
behavior.
F
It
is
typically
practiced
by
sres
and
ops
folks
as
part
of
game
days
on
production
or
production.
Like
environments.
That
said,
the
cloud
native
paradigm
has
changed
the
way
the
apps
are
built,
tested,
shipped
deployed
and
maintained.
There
are
a
lot
of
changes
in
the
way
infrastructure
is
viewed
and
managed
too.
F
F
F
This
working
group
aims
to
establish
chaos,
engineering
as
an
important
practice
and
a
go-to
mechanism
to
enforce
resiliency
in
the
application
delivery
world
by
identifying
trends.
Developing
patterns
documenting
best
practices,
highlighting
user
stories
from
the
real
world.
All
this,
while
being
tool
and
vendor
neutral,
it
is
comprised
of
a
diverse
cross-functional
group
with
members
from
chaos.
Projects
like
chaos,
mesh
litmus
chaos,
chaos,
blade
and
others.
F
This
working
group
is
today
the
early
stages.
It
has
a
dedicated
git
repository
that
houses
important
artifacts,
such
as
a
conceptual
or
a
semantic
glossary
that
can
be
leveraged
by
users
that
are
beginning
their
journey
into
chaos.
Engineering,
a
white
paper
draft
which
captures
the
state
and
practices
of
chaos,
engineering
in
the
cloud
native
world
uses
stories
gathered
by
speaking
to
end
users
across
different
domains
and
organizations,
etc.
F
If
you
are
interested,
please
join
us
and
do
contribute
to
this
effort.
You
can
help
with
enriching
the
glossary
you
can
help
with
improving
the
white
paper.
You
can
participate
in
the
user
interviews
if
you're
already
doing
some
kind
of
chaos
testing
or
you
have
a
resilience.
Engineering
team,
you
could
also
take
the
survey.
It
has
a
set
of
simple
questions
designed
to
capture
chaos,
friends
or
you
could
just
hop
on
to
the
chaos,
engineering,
workgroup
meetings
and
just
join
in
discussions.
F
The
working
group
meets
every
alternate
thursday
at
8,
00
pm,
pacific
time.
The
event
is
listed
on
the
cncf
calendar,
so
you
can
just
join
and
participate
in
the
discussions
and
get
involved.
Add
yourself
in
the
interested
parties.
I
hope
this
was
helpful
and
a
quick
insight
into
this
working
group.
Once
again,
thank
you.
B
Thank
you
kartik.
It
looks
like
we
get
some
really
interesting
material
about
chaos,
engineering
in
the
future,
another
side,
project
of
the
tech
gap,
delivery
is
a
demo
application
called
the
potato
head
which
has
been
introduced
to
demonstrate
cloud
native
application
delivery
at
the
kubecon
northern
america
2020
in
the
meanwhile,
a
single
service
and
the
multi-service
application
exists
which
is
being
used
for
showcasing
application,
delivery
tools
and
packaging
microservices,
but
also
as
a
lightweight
application
for
educational
purposes
to
demonstrate
microservice
architectures.
B
Currently
many
demos
have
been
provided
by
maintainers
of
projects
like
helm,
catch,
argo,
celeb
and
gimlet
flux
and
captain.
We
are
always
looking
for
new
use
cases
like
service
meshes
and
stateful
services.
So
if
you
would
like
to
contribute
some
demo
use
case
or
have
any
idea
how
to
extend
the
potato
head
feel
free
to
reach
out,
we
want
to
get
more
insights
about
the
things
going
on
in
the
wild
and
work
close
with
the
community
and
end
users
to
help
all
of
them
establishing
appropriate,
deliberate
solutions
by
creating
content
and
discussing
them.
B
B
B
B
Last
but
not
least,
we
are
happy
about
all
of
your
ideas
and
your
feedback
just
reach
out
to
us
in
the
tech,
app
delivery
channel
of
the
cncf
slack.
You
can
also
find
all
of
the
information
about
the
tag
and
its
working
groups
on
github.
Last
but
not
least,
one
of
our
main
communication
channels
is
our
mailing
list.