►
From YouTube: CNCF TAG App Delivery 2021-11-03
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
A
A
B
All
right,
thank
you,
jennifer
for
giving
me
a
heads
up
on
today's
date.
B
Okay,
so
one
of
the
things
that
we
got
done
over
the
last
few
months
was
start
off
by
defining
a
set
of
terminologies.
Most
of
the
information
that's
available
here
was
living
in
different
google
docs.
We
sort
of
brought
that
into
a
git
repository
thanks
to
amy
for
giving
us
this
space
on
the
cncf
github.
B
We
have
a
glossary
which
we're
trying
to
keep
live
and
add
more
information
about
chaos.
Engineering
I've
tried
to
make
it
a
little
bit
different
from
the
usual
glossary,
in
the
sense
that
it
is
not
alphabetically
sorted
and
instead
it
is
in
some
kind
of
a
conceptual
sequence
and
the
terms
that
people
would
encounter
as
they
begin
chaos
engineering.
B
So
we've
had
some
couple
of
meaning
meaningful
contributions
from
members
that
have
taken
a
look
at
it
outside
of
the
core
working
group.
So
that's
a
positive,
so
we've
sort
of
started
with
that
and
we
also
started
with
user
interviews.
This
is
one
of
the
things
that
we
wanted
to
do
as
part
of
the
working
group.
B
The
idea
is
to
keep
it
is
it's
to
keep
it
mostly
platform,
neutral
or
tool
neutral,
but
focus
more
on
why
a
particular
practice
was
adopted.
How
organizations
are
doing,
cares,
engineering,
what
prompted
them
to
what
were
the
challenges
around
it,
and
if
somebody
created
a
tool,
what
was
the
area
that
they
were
basically
trying
to
target?
What
was
the
gap?
They
were
trying
to
fill
things
like
that.
B
B
B
Finally,
so
that's
what
we
have
going
on
in
the
working
group
and
the
idea
is
to
take
this
learnings
and
knowledge
back
into
the
white
paper,
which
is
under
construction,
and
we've
got
some
progress
on
adding
actual
content
to
the
whitepaper.
B
We
have
a
couple
of
folks
working
on
adding
illustrations
and
diagrams
aided
notes
on
introduction
to
chaos.
Engineering
sayam
is
one
of
those
that
is
helping
us
with
this
was
going
to
attend
this
meeting
today,
but
couldn't
get
into
a
conflict
later.
He
sends
regrets,
and
most
probably
by
november
12th,
which
is
the
next
working
group
meeting.
We
will
have
an
introduction
section
available
with
a
significant
amount
of
illustrations
and
aids,
and
we
also
intend
to
get
a
initial
working
draft
of
this
white
paper
by
the
kubecon
china.
B
So
I
think
we've
kept
kubecons
as
our
milestones.
We
we
couldn't
do
it
for
north
america
cubecon,
so
the
target
is
to
have
it.
The
first
draft
available
for
sort
of
advocacy
by.
B
And
thanks
also
to
jennifer
for
suggesting
we
had
a
cubicle
digest
around
chaos
engineering
information
presented
during
kubecons.
We
basically
went
back
and
added
some
talks.
Some
of
them
are
case
studies.
Some
of
them
are
updates.
Some
of
them
are
basically
integration
efforts
that
were
spoken
about
all
that
information
can
be
found
here,
we'll
hope
to
add
to
that
in
the
coming
coupons.
B
B
C
A
A
Thank
you.
Thank
you.
That's
very
nice.
I
just
don't
so
to
double
check
you
consider,
then.
The
charter
of
the
group
like
completed
now
is
that
the
case.
B
Yeah,
so
we
had
a
couple
of
tbd
items,
especially
in
in
terms
of
security
chaos
with
folks
from
security
security,
sorry,
tax
security
joining
in,
and
I
think
there
was
a
comment
that
we
had
on
the
dock,
which
was
about
rewording,
one
of
the
goals.
It's
the
workgroup
is
not
only
focused
on
building
security,
tooling
or
similar
search,
it's
more
about
defining
some
best
practices
and
trying
to
see
how
chaos
engineering
can
aid
in
security
validation.
B
There
are
a
category
of
experiments
or
security
chaos,
experiments
which
some
of
the
projects
are
trying
to
build
and
basically
the
it
was
about
rewarding
that
and
putting
it
resolving
it.
So
we've
committed
that
into
the
repository.
B
There
is
a
tpd
there
on
chairs
of
the
working
group.
We
sort
of
really
went
ahead
with
user
discussions
and
other
deliberations
without
really
having
a
formal
chair
on
this.
So
that's
probably
something
that
we
might
see
being
discussed
about
in
subsequent
discussions
as
we
reach
better
shape
so
yeah.
I
think
that
that's
one
of
the
things
we
still
need
to
fill
in,
but
otherwise
we
have
the
charter
and
the
goals
more
or
less
sorted
out.
A
Okay,
yeah,
because
I
believe
there
is
maybe
one
step
of
like
making
it
official
like
it's,
it's
it.
It's
doing.
It's
taking
its
course
like
it's
moving
on
at
least
like
nothing
is
blocking
it.
I
hope,
but
just
so
we
can
like.
I
think,
because
this
working
group
involves
different
tags.
It's
a
bit
bit
different
I'll
just
touch
base
with
some
of
the
with
the
tags
that
are
involved
involved
in
this
working
group
as
well,
just
in
case
for
them
to
just
encourage
them
to
take
a
look
at
the
chart
as
well.
A
In
case
they
have
some
some
comment
and
then
we
can
just
like
officialize
it
by
making
it
to
the
poc
etc.
Just
to
close
that
so
then
thank
you.
Okay,.
B
We
just
had
a
new
entrant
in
terms
of
the
projects
to
the
working
group
as
well.
Here's
blade
he's
also
a
cncf
sandbox
project
now
and
is
also
participating
in
the
the
work
group.
So
that's
a
positive.
We
have
for
perspective
and
jennifer.
We
did
sort
of
share
the
charter
around
a
little
bit.
I
think
alex
also
shared
it
in
the
observability
slack
channel
tags
lecture
sometime
back
but,
like
you
said,
it's
still,
probably
not
very
well
known
amongst
the
different
teams.
B
We
probably
should
go
ahead
and
get
people
to
take
a
look
at
it
little
bit
more.
So
we'll
focus
on
that,
and
we
will
see
if
there's
anything
else,
that
the
other
stakeholders
or
the
tags
want
to
add
into
these
goals
with
something
we
will
work
on.
Thank
you.
A
B
I
think
they
did
I'm
not
completely
sure,
but
I
think
it's
on
the
cncf
landscape
and
we
had
some
focus
folks
from
ps
blade
who
have
joined
us
in
the
work
room.
We
have
had
their
participation
in
the
calls
and
they
are
bringing
in
some
interesting
perspective
about
how
they
implemented
the
tool
and
what
was
the
need-
and
things
like
that,
so
it
is
always
great
to
have
more
ideas.
So
that's
that's
one
of
the
recent
developments
since
the
last
update
that
we
gave
here
about
working
group.
A
B
I
think
we
could
probably
schedule
that
one
I
I
will
check
with
the
the
the
maintainer
or
contributor
who's
joined
from.
He
has
blade
to
see
if
they
have
any
plans
of
doing
a
demonstration
presentation
in
the
working
group.
A
D
I
couldn't
take
a
shot
at
that
robert,
so
we've
had
two
meetings
so
far
and
we're
beginning
to
firm
up
where
we're
going
after
this
we'll
talk
about
the
chairs.
I
guess
next
steps
once
with
those
chairs
in
place
is
we're
gonna
be
well.
We
need
to
drum
up
a
bit
of
participation,
but
I
think
that's
also
part
of
defining
what
we're
doing
too.
So
that's
on
the
list.
We
really
want
to
learn
from
users
and
robert
was
probably
going
to
go.
D
I
don't
know
if
he's
done
it
yet,
but
put
together
a
survey,
so
we
can
and
talk
with
the
cncf
about
how
we
can
connect
with
end
users
and
get
some
info
from
surveys
and
see
if
they're
interested
in
doing
a
real
interview,
maybe
with
us
and
then
we'll
come
up
with
a
set
of
questions
to
find
out
what
their
problems
are
with
infra.
You
know,
so
we
can
make
sure
we're
aligned
with
what
our
users
need
next
thing
meeting
schedule.
D
I
think
it's,
the
second
and
fourth
wednesdays,
we'll
make
sure
it's
on
the
calendar.
If
it's
not
and
then
a
couple
a
couple
items
we're
kind
of
pursuing
and,
like
I
said,
we're
refining
exactly
where
we're
going,
but
one
of
them
is
deploying
infrastructure
services
straight
up
and
one
is
deploying
infrastructure
along
with
apps
from
a
code
perspective.
D
You
know
we're
focusing
on
that
as
our
kind
of
sandbox
and
also
recently
and
scott
actually
brought
up
another
area
which
we
might
consider,
which
is
standards
around
conventions
for
infrastructure
such
that
you
know
like
resource
models
and
things
like
that,
such
that
you
know.
If
things
follow
those
conventions,
then
they
would
they
would
just
work
or
if
we
drove
towards
conventions
and
standards
around
modeling.
B
D
B
B
Also
would
have
to
yell
if
I
had
but
I'll
say
something.
A
C
Yes,
I
think
george
already
announced
that
there
are
some
new
chairs
for
the
for
the
cooperative
delivery
working
group,
so
we
made
we
had
we
we
asked
for
nominations.
Last
two
weeks
some
people
were
nominated
and
in
the
last
two
days
we
saw
the
chairs
the
tail
leads
and
the
tech
leader
zones
voted
for
the
new
chairs.
We
elected
two
chairs,
and
these
are
and
I'm
glad
to
congratulate
josh
and
robert.
C
I'm
sure
you
make
a
good
work
and
strive
to
drive
the
progress
of
the
working
group
further.
So
thank
you.
Thank
you
for
stepping
up.
A
Yeah,
thank
you
both
thank
you.
Everyone
who
like
joined
the
working
group
and
actually
working,
thank
you
both
for
the
active
efforts
and
shaping
their
working
group
as
well.
It's
going
to
be
very,
very
cool
yeah.
With
regards
to
potato
head,
I
would
like
to
ask
for
update,
but
also
last
a
few
meetings
ago.
There
was
one
action
that
was
to
get
like
some
adaming
to
look
at
a
little
issue.
Josh,
I
believe
now
I
had
a
chat
with
the
like
folks
yesterday
and
I
think
we
can.
A
We
will
give
try
to
get
you
access
like
admin
access
and
then
I
think
that
will
be
solved
but
yeah
apart
from
that,
is
there
anymore
date
and
potato
head.
D
Not
much
we
could
use
you
know
if
anyone
has
some
time
to
we,
we
have
the
the
base
templates
move
to
the
multi-service,
you
know
customize
and
helm,
and-
and
things
like
that,
so
if
anyone
has
time
to
I'm.
D
A
So
next,
just
small
updates,
like
kubecon
china
and
thomas
and
hong
shower,
preparing
a
presentation,
only
tag
up
delivery,
one
finding
that
we
had
on
the
presentation
that
we
did
on
the
me
and
alois
on
the
na
was
north
america
was
that
very
few
people
knew
it
existed
the
tag,
so
we
were
being
discussing
that
like
it
would
be
nice
to
to
to
get
more
of
the
message
out
there
like
not
like,
because
lots
of
people
yeah
just
don't
know
those
tags
exist
and
encourage
you
to
share
whatever
your
social,
medias,
professional
et
cetera.
A
A
I
believe
that's
what
we
have
here
did
we
do
a
digest
ourselves
like
I
didn't
follow
up
on
on
getting,
but
the
k
of
the
limited
escape.
Sorry,
the
chaos
engineering
working
group
digest
really
nice.
I
really
like
that.
So
perhaps
we
can.
We
could
feel
the
idea
of
putting
it
somewhere
like
for
people
to
do
that.
I
think
so.
A
C
D
Yeah,
I
was
actually
thinking
as
karthik
was
presenting
like
an
awesome,
app
delivery,
markdown
file
with
a
list
of
talks,
and
you
know
maybe
eventually
a
list
of
projects
or
something
yeah.
That
sounds
that
makes
sense
I'll.
Think
about
that.
A
A
Another
20
minutes
back
of
your
day.
Thank
you
very
much
for
all
the
everything
that's
now
and
hope
to
see
you
folks
soon
have
a
nice
evening.
Everyone
thank
you,
everyone,
congrats
josh
and
robert
and
the
whole
cooperative
delivery
working
group.
That
seems
to
be
moving
quite
nicely
and
the
chaos
engineering
as
well.