►
From YouTube: CNCF TAG App Delivery 2021-07-07
Description
CNCF TAG App Delivery 2021-07-07
A
A
A
C
A
B
B
B
C
B
A
Yes,
I'm
very
proud
to
announce
that
we
finished
operate.
The
white
paper
on
I
think
monday,
so
we
we
merged
the
last
pull
request
and
currently
we
are
trying
we
are
about
to
get
this
to
get
this
published.
You
know
and
make
a
printed
document
out
of
this,
so
the
cncf
and
linux
foundation
are
working
on
the
on
the
document
now
and
we
will
get
this,
hopefully
a
finished
version
in
the
next
weeks,
and
I
also
contacted
amy
today
that
that
she
should
remove
the
operator
working
group
meeting
from
the
calendar.
A
B
Yeah,
maybe
some
words
for
people
who
really
joined
what
potato
head
is
potato
head
was
a
project
we
created
for
our
cube
con
session
last
year.
I
think
so
yeah
I
created
to
showcase
some
app
delivery
projects
and
it
was
just
supposed
to
be
a
repo
that
contains
just
some
examples
of
a
delivery
project,
but
then
more
people
started
to
contributing.
I
think
right
now,
there's
over
10
different
tools,
deploying
a
simple
application
that
was
single
tier
now.
B
This
got
extended
to
have
support
for
metrics
so
that
you
can
validate
your
deployments
already.
What's
also
coming
is
open,
telemetry
support
and
the
litmus
team
also
built
a
distributed
version
so
yeah.
The
idea
was
to
have
a
simple
application
like
compared
to
sockshop
and
some
others
where
the
applications
are
rather
heavy,
and
if
you
want
to
test
the
multi-stage
deployment
on
your
local
laptop,
it
gets
rather
hard
and
complicated
with
potato
head.
It's
simple
and
you
really
can
focus
on
the
tooling
stack
that
you
want
to
run
and
you
can
easily
compare
them
plus.
B
The
plan
going
forward
was
to
also
support
more
complex
scenarios
like
stateful,
workflows
or
workloads
that
require
authentication
and
and
so
forth,
and
as
we
have
that
the
project
has
always
been
the
cncf
repository
simply
because
we
created
it
there
as
a
working
group,
but
as
there
is
continued
interest
and
people
are
contributing
to
it,
wanted
to
put
it
into
a
more
standard,
cncf
context
as
a
more
or
less
learning
application.
So
obviously,
if
you're
willing
to
contribute,
if
you
have
interest,
feel
free
to
also
provide
feedback,
I
mean
it
already
exists.
D
D
D
B
I
think
we
have
to
look
at
the
charter
and
then
we
will
share
it
with
our
toc
liaison
and,
if
they're
good
with
it,
we
just
then
send
a
note
to
the
toc
and
usually
we
get
the
the
approval
from
from
from
the
toc,
but
that
would
be,
if
you're,
at
the
stage,
where
I
think
it's
good
to
share.
We
should
share
this
cornelia
and
and
harry
tell
them.
B
B
Also,
when
you
look
at
the
keytops
working
group,
usually
like
having
like
50
60
people
who
have
at
least
their
initial
interest,
is
a
good
sign
as
well
so
share
it
with
the
wider
community
if
they're
interested
to
come
contribute.
It's
also
like
super
helpful.
I
didn't
look
at
the
old
latest
version.
How
many
interested
parties
we
had,
but
I
think
it's
not
that
many
that
yet
were
interested
there.
So
a
bit
more
advocacy
to
other
interested
projects
and
other
interested
parties
might
make
sense
as
well.
C
B
I
can
start
there
because
it
was
initially
involved
in
the
hong
kong
feel
free
to
jump
in
here
we
started
to
look
into
the
review.
I
also
asked
the
team
to
present
to
tag
app
delivery
because
I
think
they
never
really
presented.
At
least
I
can't
remember
it
unless
nobody
else
can.
I
think
they
really.
This
really
kind
of
got
lost
yeah.
E
A
C
B
B
B
B
A
C
E
Go
ahead,
okay,
yeah!
I
also
like
reach
out
to
the
tails
mesh
of
team
like
they
are
really
interested
in
participating
in
the
upstream
and
and
especially
the
chaos
engineering
of
like
working
group,
but
they
asked
by
just
wondering
what
what's
the
status
of
the
working
group
now
and
like
how
could
they
participate
into
that
later,
because
I
think
there's
no
like
working
group
meeting
like
being
set
up
or
something
right.
B
The
case
one
is
an
interesting
one,
so
I
happened
to
join
the
observability
tag
meeting
yesterday
and
the
observability
team,
the
observability
texas.
They
also
see
them
being
responsible
for
chaos,
engineering
and,
I
think,
well,
chaos
engineering
spans
a
lot
of
tags
like
for
us.
Obviously
it's
still
it's
part
of
testing,
so
it's
part
of
delivery.
Observability
obviously
wants
to
look
into
how
things
are
working
or
not
working
then
network
chaos
mesh
obviously
gets
into
the
networking
space,
and
then
you
have
security
chaos
which
gets
into
the
security
space.
B
B
B
See
this
a
bit
more
freely,
but
I
think
we
should
have
this
discussion.
I
mean,
I
think
it
doesn't
really
affect
who
the
projects
collaborate
with,
but
maybe
having
like
the
working
group
and
bringing
all
the
interested
parties
together
is
really
something
we
should
push
forward
a
bit
faster.
I'm
still
also
reviewing
the
working
group
or
contributing
to
the
working
group
doc.
B
So
we
should
really
try
to
move
this
forward
to
have
the
chaos
working
group,
because
it's
really
bring
a
lot
of
people
together
and
we
should
have
some
way
of
collaborating
and
also
getting
it
on
the
on
the
calendar.
So
I
think
that's
that
definitely
makes
sense.
It
seems
like
everybody
now
starts
to
be
interested
in
this
skills
topic
here,
which
is
good,
which
is
good.
C
B
C
C
B
C
B
B
F
All
right
so
well,
it's
great
to
make
sure
first
time
that
I
joined
this
tags
call.
So
my
name
is
leonardo,
I'm
based
in
costa
rica
and
with
refworks,
and
I'm
one
of
the
three
coaches
of
the
working
group.
I
don't
know
when
was
last
time.
Petrol
received
an
update
from
us.
So
if,
if
I'm
redundant,
please
let
me
know
in
terms
of
ongoing
initiatives,
we
have
the
cube
the
get
upscon
happening
as
a
co-located
event
for
on
kubecon
na.
F
There
is
a
weekly
call,
which
is
actually
happening
today
from
the
events
committee,
so
we
have
a
community
that
is
working
towards
building,
what's
necessary
for
evaluating
cfps
and
organizing
everything
else.
That
needs
to
be
organized
for,
for
the
event,
any
questions
around
the
github
spawn
as
a
follow-up
event
with
kubecon
north
america.
B
F
F
As
far
as
other
progress,
the
so
as
as
I'm
pretty
sure
you
all
know,
the
get-offs
working
group
is
now
like
the
clock.
Maintaining
or
I'm
not
gonna
say
maintain.
It
is
the
organization
the
work
group
that
created
an
open,
github's
project,
there's
two
different
things:
the
working
group
on
the
open,
githubs
project,
the
open
githubs
project-
is
something
that
will
last
as
opposed
to
the
work
which
is
ephemeral
and
the
open
github
project
is
going
to
have
a
website.
F
F
We
created
a
principles
committee
and
just
to
give
you
all
kind
of
a
sense
of
this
history
of
how
we
got
there
in
the
world.
In
the
get
offs
working
group
repo,
we
had
an
open
pr
where
we
were
working
on
the
definition
of
the
getups
principles
collaboratively
with
the
community.
The
the
dialogue
became
overwhelming.
The
pr
became
gigantic,
so
we
decided
to
create
a
principles
committee
that
meets
weekly.
The
version
0.1
of
those
principles
has
been.
Thank
you.
A
lot
has
been
already
defined.
What
we're
working
towards
now
is.
F
There
was
a
lot
of
very
rich
discussion
that
happened
on
that
original
pr
on
the
get
us
working
group
repo
that
should
be
integrated
somehow
into
this
new
principles
document
in
the
documents
repo
of
the
open
githubs
project.
So
that's
the
focus
of
the
principles
committee
at
this
point
basically
scanning
all
the
previous
collaborations
in
the
previous
pr,
integrating
those
into
documents
of
the
open,
githubs
repository
with
a
focus
of
getting
to
version
1.0,
and
once
we
have
version
1.0,
the
objective
is
to
basically
socialize
into
the
broader
community
to
start
getting
corporate
buy-in.
F
F
E
F
So
look
I
I'm
going
to
answer
two
questions.
As
I
interpret
it.
One
is
the
first
get
up
scott
that
happened
during
qcon
eu
that
was
not
organized
or
the
cncf
was
not
involved
this
and
I'm
I'm
likely
using
the
wrong
terminology.
But
there
is
no
idea
of
kind
of
collocated
event
versus
zero
day
event
or
something
like
that.
There's
a
difference.
The
first
one
was
completely
community
organized
this
one.
Actually,
the
cncf
was
involved
and
this
one
we
have
sponsorship
packages
and
it's
actually
not
free.
F
F
Kind
of
executed
whether
there
is
going
to
be
a
get
up
spawn
with
every
kubecon.
I
really
wouldn't
be
able
to
answer
that
question.
What
I
can
tell
you
is,
there
is
kind
of
a
an
expressed
desire
across
the
more
active
members
of
the
githubscan
working
group
and
github's
community
to
kind
of
increase
the
dimension
of
github's
related
events
going
forward
right,
there's
a
lot
of
traction
and
there's
a
lot
of
interest.
E
E
I
can
share
the
data
to
the
to
the
form
but
like
basically
like
they
are
also
like
trying
to
do
more
participating
in
more
open
source
like
a
community
like
such
conferences,
but
like
they,
but
they
are
located
in
china
now
but
like
they
can't
travel
due
to
the
covet,
I'm
wondering
is
it
okay?
Is
it
like
virtual
or
or
is
it
have
to
be
physical?
E
F
I
think
for
for
coupon
as
well
as
speed
up
scrum,
the
whole
model
is
going
to
be
hybrid.
To
tell
you
the
exact
truth.
I
don't
know
what
that
means
right.
I
don't
know
if
every
talk
is
gonna
be
broadcast
live.
I
don't
know
if
there's
gonna
be,
I
don't
know
what
the
hybrid
really
will
look
like,
but
there
there
is
a
hybrid
or
kind
of
like
a
virtual
version
of
of
kyoko
and
github's
con,
but
I
don't
really
have
the
except.
He
tells
us
to
how
the
implementation
of
that
will
look
like.
G
G
G
But
I
think
all
of
the
talks
are
going
to
be.
Everything
is
going
to
be
you're,
going
to
have
a
basically
two
two
events
and
I
I'm
not
sure
what
they're
going
to
do
either.
If
we're
going
to
do
the
talks
in
person
and
they're
going
to
record
them
and
broadcast
them.
I
think
that's
probably
how
they're
going
to
do
it.
G
A
G
G
E
B
Yeah,
I
think
we
should
wait
also
closer
to
the
event
to
get
updates.
I
think
right
now
in
july
it
might
still
be
hard
to
know
what
october
is
going
to
look
like
I
mean
we
all
wish
the
best.
How
was
he
to
get
there?
So,
let's
see
what
the
next
months
are
going
to
bring?
Maybe
one
more
thing
about
kubecon,
usually
right
now,
then
after
kubecon,
what's
going
to
happen,
you
will
see
a
lot
of
proposals
in
different
areas
or
like
a
lot
of
proposals,
saying
that
their
proposals
were
not
accepted.
B
I
was
also
part
of
the
reviews
for
for
one
track
and
as
a
lot
of
people
who
wanted
to
introduce
a
smaller
open
source
projects
and
get
feedback
on
smaller,
open
source
projects.
I
think
that's
also
something
that
where
we
could
actively
invite
people
to
present
also
here
as
part
of
a
tech,
app
delivery
and
share
them,
because
there
are
some
interesting
projects
there.
B
I
mean
not
talking
about
the
details
which
we're
not
allowed
to
do
as
a
program
committee,
but
there's
like
this
really
interesting
open
source
project
that
try
something
really
interesting
and
new.
It's
just
done
by
one
or
two
people
as
part
of
the
company,
and
they
might
have
like
three
github
stars
and
maybe
not
even
ever
or
just
have
a
version:
zero,
zero
dot,
dot,
one.
B
So
nothing
you
would
necessarily
accept
for
kubecon,
but
if
the
project
is
interesting,
some
of
those
projects
that
I
would
actively
invite
here-
and
I
know
that
seek
runtime-
is
doing
this
a
lot
so
bringing
projects
to
present
new
ideas,
and
I
think
as
to
seek
I
sorry,
I'm
still
saying
sick.
When
I
should
be
saying
tag
as
tech
app
delivery.
I
think
we
can
also
use
them
and
and
share
them
with
the
wider
community
and
give
this
approach
to
those
an
audience
and
and
learn
more
about
them.
B
I
think
this
is
something
we
should
take
up
again,
and
so,
if
you
come
across
any
interesting
project
that
you
think
this
might
be
interesting,
we
might
get
or
might
deserve
to
deserve
some
more
attention
in
the
app
delivery
space
either.
Let
us,
as
the
chairs,
know
or
reach
out
to
them
and
that
have
to
present
we
have
done
some
of
them
in
the
past.
B
This
kind
of
stopped
a
bit,
but
I'd
also
encourage
you
to
if
you
know
about
any
projects
or
if
you
know
about
people
or
there's
a
project
that
you
are
using,
that
you
think
this
might
be
interesting.
It's
not
like
widely
adopted,
but
might
make
sense,
feel
free
to
do
so
as
well,
and
maybe
we
also
start
the
list
of
projects
that
we
are
interested
in
in
presenting
like.
B
I
have
a
list
now
of
six
projects
that
I'd
like
to
see
what
they're
doing
in
detail,
but
again
they're
like
very
early
stage
and
not
necessarily
what
you
would
have
for
coupon
immediately.
Think
of
it
like
as
the
app
the
tag
app
delivery
version
of
kubecon
rejects,
and
I
think
there
is
some
opportunity
there
for
presentations.
There's
also
now
a
lot
of
people.
B
This
is
our
tool
stack
that
we
were
using,
but
again
at
some
point,
there's
so
many
of
those
that
you
know
not
all
of
them
are
going
to
make
it,
but
these
are
still
interesting
stories
and
yeah.
This
is
just
my
proposal
to
then
reach
out
to
those
people
and
where
we
know
this
is
happening
to
also
socialize
this
by
social
media.
If
you
want
to
present
on
it
on
this
topic
and
it's
app,
delivery
related
also
feel
free
to
come
to
the
tag,
because
there
are
interesting
stories
there
as
well.
B
H
H
We
wanted
some
more
eyes
on
the
charter
to
formalize
the
goals
and
non-goals,
and
we
have
received
some
interest
on
the
slack
channel
and
the
next
step
would
be
to
go
ahead
and
meet
to
decide
on
the
cadence
and
the
other
modalities
of
how
we
will
operate
within
this
work
group.
So
that's
the
current
status
there.
H
We
made
some
more
progress
on
the
surveys
that
we
are
carrying
out
for
the
chaos
engineering
white
paper,
which
I
now
believe
will
be
an
artifact
or
an
end
product
of
the
work
group
itself.
So
yeah.
I
think
that
that's
where
we
are
at.
I
would
request
the
community
to
take
a
look
at
the
charter
and
probably
add
to
the
goals
and
the
challenges
that
we
have
stated
there,
and
we
can
chat
on
what's
a
good
time
to
have
the
first
meeting
so
that
we
can
decide
on
how
to
proceed.
B
Yeah,
I
think
you
before
you're
right.
We
talked
about
it
as
well.
Yesterday
in
the
observability
tag,
meeting
observability
ozone
wants
to
get
involved,
so
it
looks
like
you're
becoming
super
famous,
because
now
four
techs
are
interested
in
this
working
group.
So
I
think
it's
not
getting
everybody
involved
on
the
same
page
and
from
other
charters.
In
my
experience
it
might
make
sense
to
set
up
a
first
meeting,
maybe
as
soon
as
next
week.
If
you
think
that
the
charter
is
ready
for
for
an
initial
discussion
and.