►
From YouTube: CNCF TAG App Delivery 2021-11-17
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).
A
A
B
I'm
sorry
out
a
new
smart
speaker
phone
thing
and
yes.
A
Yeah,
so
I
am
embracing
from
the
developer
advocate
perspective
getups.
So
that
is
why
I'm
here
today.
E
E
Nice
and
twitter
randy
person
and
right
now,
just
love
sharing
the
potato
head
commit
messages.
I
think
they're,
the
most
hilarious
thing
that
comes
out
there
fixing
the
right
arm
because
it
was
broken.
I
mean
this
is
one
of
the
best
commit
messages
ever.
A
F
E
Yeah,
we
didn't
do
a
good
job
on
the
on
the
agenda.
This
time.
I
think
it's
overall
updates
from
the
individual
working
groups
and
I
think
we
should
announce
especially
the
cooperative
delivery
working
group.
A
F
D
A
C
E
Yeah
on
the
agenda,
it's
really
working
group
updates.
I
think
one
other
topic
is
we
have
people
here
from
get
ups.
We
we
and
by
we
I
actually
mean
the
great
alex
jones-
has
hopefully
fixed
your
github
right,
so
that
you
should
be
able
to
commit
now
to
the
repo
as
well,
because
I
think,
basically,
mostly
requests
from
josh,
but
it
should
be
working
for
you
right
now.
Okay
and
what
we
did,
you
should
be
able
to
submit
prs.
E
It's
just
way
to
add
non-code
shares
as
being
giving
them
right
access
to
repos.
I
mean
they
should
still
be
able
to
submit
prs.
It's
just
a
bit
harder
to
keep
it
in
in
in
line
there,
so
it
shouldn't
be
too
much
of
a
burden
for
you
to
manage
this,
but
but
the
way
we
set
it
up
right
now,
I'm
your
sub
director.
You
should
be
able
to
submit
now
cool.
E
Us,
but
that
should
I
think
I
fixed
this
yesterday
and
yeah.
I
think
we're
moving
the
content
over
and
we
have
it
all
in
one
place.
Nice.
C
On
that
topic,
I
just
wanted
to
mention
you
guys
did
give
me
commit
rights
in
the
potato
head
repo
and
I've
been
working
with
the
prs
there
that
it
it's
I'm
one
of
the
more
active
folks.
I
guess
so.
If
other
people
want
to
participate
more,
just
you
know
reach
out
to
me
and
say,
like
don't,
merge
or
whatever
make
sure
we
get
two
lgtms
or
something,
but
so
far
to
be
going
smoothly.
I
just
wanted
to.
E
Yeah
thanks
for
the
work
on
potato,
I
think
we
should
have
here
a
bit
of
the
update
presentation
not
today,
so
I
don't
want
to
put
you
on
the
spot
today,
but
yeah.
I
really
appreciate
the
commitment.
I
mean
the
whole
way
how
this
project
came
along
is
so
funny
and
the
velocity
it's
kind
of
getting
by
more
and
more
people
contributing
it's
kind
of
interesting.
C
Yeah
somebody
contributed
that
said,
they
had
used
it
to
give
a
workshop
and
they
came
back
in
and
realized
they
need
to
get
updated
for
the
multi-service.
That
was
a
good
sign.
I
love
that.
E
E
Yeah
I
I
also
talked
to
bridget
from
the
from
the
helm
team
and
they
might
also
be
able
to
support
on
the
helm.
So
I
think
we
should
do
a
better
job
telling
people
what
we
want
them.
Bridgette.
Yes,.
C
We
need
to
update
I've
been
working
with
thomas,
like
the
core
code
needs
a
needs
a
bit
of
a
refactor.
I
think
my
go
background.
E
A
E
Yeah
so
yeah,
but
if
I
think
for
the
next
meeting,
if
you
could
also
ask
people
where
we
need
contributions
and
maybe
have
a
list
of
things
where
they
can
contribute
would
be
helpful.
E
F
E
E
C
And
yeah
I
actually
have
tests.
I
I
couldn't
get
it
to
work
perfectly
in
the
main
repo,
but
in
the
forks
it
runs
and
it
actually
there's
a
script
that
I've
been
adding
to
each
one
that,
within
a
k
and
the
clustering
cluster,
sets
up
flux
and
deploys
and
checks
that
the
api
is
available.
C
F
Just
a
small
update
on
the
chaos
engineering
charter,
I
I
reached
out
to
tag
security,
observability
network
tag.
Security
has
like
come
with
some
feedback
and
focus
on
the
working
group
are
looking
at
and
like
tag
network
like
are
happy
with
that,
and
then
observability
is
going
to
follow
up
soon.
So
it
should
be
soon.
We
should
have
some
I'll
get
in
contact
with
toc
for
just
an
approval.
F
E
E
Obviously,
as
the
project
was
part
of
app
delivery,
we
talked
about
app
delivery,
but
then
they
talked
about
network
care.
So
that's
how
we
got
signet
attack
network
involved.
Then
they
talked
about
security
chaos,
that's
how
we
got
tech
security
involved
and
obviously
it
doesn't
make
a
lot
of
sense
to
rank
heroes.
E
Experiments
if
you
don't
know
where
they're
running
well
and
that's
how
tag
observability
also
get
involved,
and
it's
now
a
working
group
that
is
run
across
four
tags
and
that's
why
I
think
it's
a
bit
challenging
to
get
this
really
off
the
ground,
because
we
need
to
get
a
lot
of
people
on
the
same
page
here.
But
I
think
overall,
it's
a
great
sign
that
we
start
these
activities
where
we
have
this
collaboration
across
multiple
texts
within
the
cncf.
F
E
D
Time
zones
are
weird,
unfortunately,
but
yeah,
but
that
makes
sense
because
it
touches
so
many
of
the
different
tags.
So
I
think
everyone
should
be.
You
know
represented
in
that.
In
that
context,.
E
E
B
E
B
E
Support
the
overall
team
that
kicked
it
off.
So
that
was
our
discussion
as
well
as
attack
chairs
because
they
wanted
just
to
start
the
white
paper
and
then
the
thing
kept
growing,
bigger
and
bigger
and
bigger
from
an
organization
point
which
again
per
se
is
good,
because
it
shows
that
there
is
interest
and
there
is
required
collaboration
across
a
lot
of
people.
D
E,
well,
yes,
so
we're
we.
We
are
not
great
at
communicating
when
stuff
happens
so
so
we
we.
We
agreed
to
a
bi-weekly,
cadence
and
and
and
then
we
don't
save
the
people
when
we
have
meetings.
So
I
I
happen
to
just
drag
scott
into
scott
rigby
into
the
meeting
because
he's
interested
in
that
and
he
helped
with
a
lot
of
things,
and
you
know
all
the
pr's
or
issues
and
stuff
like
that
that
he
created
is,
you
know,
came
from
that
meeting.
D
So
we
we
all
kind
of
agree
that
we
need
to
drive
a
little
bit.
You
know
have
some
call
to
action
and
yell
at
people
that
were
in
the
interested
parties
list.
We
haven't
done
that,
obviously,
so
before
the
next
meeting,
which
is
next
week,
I
plan
on
trying
to
you
know
spam,
the
slack
with
with
the
information
about
the
fact
that
the
meeting
is
gonna
happen
and
stuff
like
that,
just
to
make
sure
that
people
are
are
actually
aware
and
stuff.
A
E
D
Yeah
yeah,
I
haven't
sent
anything
into
the
mailing
list,
so
probably
should.
D
A
E
D
That
yeah,
this
makes
sense,
and
I
think
the
ghettos
working
group
did
that
as
well.
Is
that
why.
A
D
D
D
Why
last
week's
incorporated
delivery
meeting
you
know
it
wasn't
on
there,
but
the
next
one
is
yeah,
so
we
just
need
to
clean
up
a
lot
of
those
kind
of
things,
and
I
think
also
that's
why
scott
created
a
list,
a
issue
about
being
able
to
use
the
cncf
community
thing.
E
My
problem
is
right
now
and
I'm
talking
to
in
the
js
working
group
how
to
fix
this,
how
to
actually
update
this
like
how
to
really
actually.
Where
do
I
need
to
write
an
update
to
update
that
page
when
I'm
working
on
figuring
out-
and
my
second
issue
is
that
I'm
kind
of
existing
twice
like
not
existentially
existing
twice,
but
I
have
two
users
and
two
users
with
different
rights,
and
once
this
gets
fixed
and
within
the
cncf,
then
I
should
have
proper
access.
E
So
this
is
currently
in
motion
and
I
have
designed
my
to-do
list
to
keep
to
get
them
things
updated
and
also
share
it.
What
we
can
do
pretty
much
immediately
if
we
have
meeting
times
that
we
want
to
share
at
least
update
it
on
the
github
readme
page,
where
we
have
just
this
meeting
right
now
and
clean
out
the
other
ones.
D
F
D
We
we
have,
we
have
an
action
about
creating
a
survey
for
for
for
getting
that
kind
of
information.
So
currently,
on
that
point,
I'm
I'm
just
gathering
questions
which
is
really
hard
when
we're
only
like
two
people.
So
as
I
I
got
a
couple
of
questions,
I'm
going
to
run
that
by
the
next
meeting-
and
hopefully
there
will
be
more
people
to
you-
know-
come
with
some
inputs
because
apparently
they're
working
24
hours
a
day
doesn't
make
my
brain
work
any
better.
Apparently
so,.
E
A
F
D
Yeah
this
is
this,
and
that's
also
like.
I
think
we
need
to
be
better
at.
This-
has
solely
been
done,
yeah
in
the
notes
for
the
working
group
in
the
and
as
well
as
yeah
in
the
meeting
themselves,
basically
so,
and
since
no
one's
there,
you
know
that
doesn't
work.
So
I
we
need
to
be
better
at
just
getting
all
this
information
out
there
and
be
better
to
update
people.
E
D
E
E
I
think
the
key
for
the
corporative
delivery
working
group
and
everybody
knows
that
I'm
not
the
biggest
fan
of
the
name,
but
I
also
couldn't
come
up
with
a
better
one.
That's
why
I
was
sticking
with
it,
and
this
is
something
we
were
discussing,
maybe
having
a
blog
post
or
anything.
What
it's
actually
doing
and
also
define
like
a
tangible
result
for
people
to
to
work
on.
E
Is
that
that's
what
I
saw
was
a
lot
of
white
white
papers,
and
I
mean
we
yeah
the
great
team
we
had
on
the
white
paper
for
the
operator
that
kind
of
worked
out
eventually,
but
it's
I
feel,
like
people,
sometimes
have
a
hard
time
motivating
themselves
for
white
papers
more
than
hey.
This
is
a
problem
I'm
actually
interested
in
and
be
interested
in
how
people
are
actually
solving
it
and
investing
my
time
there.
E
D
And
that's
been
that's
been
a
thing
because
when
we're
talking
about
white
papers,
I
I've
heard
horror
stories
about
how
long
some
white
papers
can
take
and
yeah
everyone
involved.
There
is
doing
it,
you
know
besides
work,
so
that
all
of
a
sudden
takes
a
lot
of
time.
So
I
I
totally
agree.
We
need
something
very
something
relatively
easily
easy
to
get
to
fast.
Just
to
get
you
know
everything,
rolling
and-
and
that's
have
kind
of
been
the
topic
of
every
working
group
meeting.
D
So
far,
but
again
it's
been,
it's
been
back
and
forth
and
who's
in
there.
So
we
kind
of
just
repeat
ourselves
every
time
more
or
less
so,
hopefully,
if
more
people
come
and-
and-
and
you
know
every
time
this
week
will
be
easier
to
discuss-
and
we
talked
about
everything
from
just
having
updating
potato
it
with
a
different
kind
of
you
know:
delivery
method.
D
That
also
includes
infrastructure-
and
you
know
doing
smaller
and
you
know
not
white
papers,
but
some
you
know
document
patterns
somehow
and
doing
stuff
like
that,
that's
more
there's
more
minor!
That's
not
an
entire
white
paper.
Obviously
I
haven't
landed
on
something
very
specific.
The
only
thing,
that's
specific
that
we
have
is
to
get
out
a
survey,
so
we
can
kind
of
start
gauging
where
people
are
at
when
it
comes
to.
You
know
both
delivering
up
and
infrastructure
in
the
same
type
of
pipeline
and
how
they
coexist.
E
Yeah,
I
like
the
idea
actually
having
a
patterns
or
like
cookbook
style
type
of
approach,
because
it
also
encourages
people
who
have
solved
certain
problems,
and
I
remember
when
we
presented
it
also
at
kubecon
we
had
people
think
from
splunk
and
apple
coming
over
and
say
yeah.
We
exactly
have
that
problem
yeah,
and
we
have
built
some
of
these
things
in
the
past
and
we
want
to
share
with
other
things,
because
that's
how
we're
doing
it-
and
it
might
be
just
the
one
page.
E
I
think
people
usually
have
time
to
have
a
one-pager,
then
present
and
have
a
discussion
with
others.
That
might
be
a
quick
way
to
get
certain
things
done
and
like
also
alex
who
was
initially
driving
it
and
thomas.
I
think
they
have
ideas
on
some
things
that
they
have
built
and
starting
out
with,
like
very
simple
examples,
might
be
super
helpful.
It's
also
shareable,
so
we
can
share
it
over
our
social
channels,
get
people
interested
that
they
bring
in
new
topics,
but
everything
that
sounds
like
a
lot
of
work.
E
Like
a
white
paper,
yeah
they're
unconscious
that
we
are
living
two
years
through
a
pandemic
and
it's
also
the
end
of
the
a
very
stressful
year
for
a
lot
of
people.
They
rather
hesitate
to
do
that,
but
if
it
attacked
the
problem
that
they
have
to
do
in
their
day,
jobs
most
likely
as
well,
they
are
way
more
inclined
to
to
contribute
and
participate.
E
So
maybe
if,
if
looking
at
two
or
three
of
them
might
actually
be,
might
actually
be
helpful-
I
mean
it's
still
your
working
group,
you,
you
have
to
do
whatever
what
what
you
want,
but
I
think
there
are
already
some
and
asking
people
like
full
small
patterns.
When
you
make
a
small
idea
on
what
that
pattern
looks
like
could
be
super
helpful
and
easily
for
us
to
share
getting
people
involved.
They
can
file
and
we
can
even
just
put
it
on
github.
E
I
mean
it
doesn't
need
to
be
like
demolished,
and
then
it
actually
publish
it
as
a.
D
Just
having
some
sort
of
like
channel
where
people
can
go
and
see
a
a
summary
and
click,
and
then
you
know
if,
if
they
land
in
the
markdown
documents,
you
know
that
get
up,
they're
gonna
represent
an
official
okay
way,
then
that
should
be
fine,
and
I
I
like
the
I
like
the
like
the.
I
guess
that
I
get
called
the
small
scope.
You
know
and
cookbook
style
of
doing
study
all
right.
You
wanna
you
wanna,
do
this
with
with
this
sort
of
infrastructure
in
this
sort
of
application.
D
On
this
here's
a
way,
one
of
the
ways
that
that
can
happen.
I
just
need
I
just
which
I
think
we
just
need
to
find
a
a
a
way
of
doing
that,
that
that
makes
sense
and
and
and
then
people
would
use.
I
guess.
E
That
I
would
try
this
with
the
first
one
and
I
think
alex
has-
and
you
also
have
put
some
examples
in
the
charter
and
just
hit
one
of
those
examples.
That's
in
there
like.
How
can
we
ensure
that,
when
we
ship
an
application
config
that
the
underlying
infrastructure
matches
and
not
that
we
then
figure
out
that
we
have
the
wrong
storage
classes
available
and
the
whole
app
doesn't
deploy?
E
One
of
the
examples
that's
in
there
or
how
do
you
manage
like
update
cycles
like
picking
one
or
two
and
then
providing
like
one
cookbook
type
solutions?
I
think
that's
other
than
easier
for
people
to
comment
on
usually
like
starting
from
nothing.
It's
like
what
should
I
do
and
if
it's
like
to
call
it
like
not
the
best
phrase,
maybe
but
create
some
type
of
attack
surface
where
people
can
work
against
okay,
this
is
how
we
do
it
and
then
other
people
can
iterate
over
it,
and
maybe
alex
has
some
ideas
as
well.
D
E
A
E
I
was
just
looking
at
the
agenda
and
I
was,
I
think,
james.
You
were
here
from
the
conveyor
team.
I
assume.
B
Yeah
yeah,
I
just
I
was
talking
to
josh
burke
as
a
redhead
yesterday,
he
mentioned
that
the
group
got
together
to
kind
of
review
the
cncf
sandbox
applications,
and
I
think
there
was
some
questions
about
conveyor,
so
I
just
want
to
make
sure
like.
If
there's
anything,
I
could
any
information.
I
could
give
you
all.
I
pasted
a
demo
in
there
to
kind
of
show
you
the
functionality
of.
E
A
E
B
Yeah
exactly
so,
basically,
yes,
it's
not
like
we're
documenting
everything
for
that
yet,
but
we're
on
we're
in
process
like
you
could
actually
here
I'll
put
this
link
in
there
in
the
zoom
chat,
but
I
mean
basically,
this
is
crane's
documentation,
that's
being
built
out
and
you'll
notice.
You
know
you
can
run
this,
it's
not
specific
to
openshift
so
yeah.
The
goal
is
to
make
this
work
for
kubernetes
and
to
get
all
the
docs
there
as
well.
So.
E
Yeah,
I
think
then
we
simply
at
some
point
should
look
at
it
from
a
or
try
some
of
these.
If
you
have
any
examples
or
anything
which
we
can
try
and
other
clusters,
I
think
that's
what
the
uc
wants
us
to
look
at
just
experimenting
on
some
other
type
of
clusters
and.
E
E
The
only
thing
that
I
was
wondering
about
conveyor
I
mean,
I
think
it's
it's
great.
What
you
build.
You
did
a
presentation
a
while
back,
and
this
is
a
problem
that
some
other
projects
that
are
submitted
right
now
have
as
well.
E
E
B
I
think
there's
a
couple
of
thoughts
around
that
one
is
that
the
modernization
of
workflows
is
never
really
ever
done
so,
as
new
features
are
are
deployed
on
kubernetes
you're,
gonna,
you're,
gonna,
analyze
those
again
and
then
so.
A
good
good
good
example
would
be
serverless
right.
So
maybe
you
move
over
you're,
not
leveraging
serverless.
Then
you
do
an
analysis
with
tackle
and
you
and
we
do
some
code
analysis
and
we
realize
you
can
actually
take
advantage
of
serverless.
So
we
then
make
your
app
serverless
right.
So
I
think
it's
like
I
mean
app.
E
B
B
That's
one
thing:
I
guess
the
other
one
would
be
even
if
it
doesn't
graduate
being
in
the
sandbox
would
be
helpful
because
it
puts
people
potential
contributors
at
ease
at
contributing
to
it,
because
it's
not
something.
That's.
Even
though
we
have
a
contributor,
a
contribution
guide,
a
governance
model
and
all
that,
knowing
that
it's
not
owned
by
red
hat
or
run
by
red
hat,
but
it's
part
of
the
foundation
would
be
helpful.
E
It's
just
just
to
get
me
where
I'm
not
I'm
not
really
against
this.
This
project,
at
all,
just
came
up
with
other
projects
as
well,
like
potato
head
being
also
one
of
them
where
which
is
really
about
learning
after
delivery,
which
I
think
is
valuable,
which
shouldn't
be
handled
by
one
organization,
because
right
now
I
think
it's
15
different
projects
and
even
more
organizations
contributing
to
it.
But
back
then,
the
feedback
from
that
that
you
see
was.
E
Of
how
you
can
fulfill
those
requirements
for
graduation,
I
think
it's
still
valuable
and
eventually
that
that
is
an
ongoing
discussion
with
the
toc.
How
to
handle
projects
like
this
at
add
value,
and
this
requirement,
just
in
some
cases
that
doesn't
really
make
sense
or
we
need
to
have
some
some
freedom
of
definition
here
might
might
make
sense
there
as
well
so
definitely
watch
the
video.
E
Thank
you
for
sharing
this,
but
just
to
also
keep
this
in
mind,
because
I
don't
want
to
like
to
run
into
endless
situations
as
you're
doing
this
cool
thanks
for
the
feedback
and
yeah,
and
maybe
also
statement,
might
make
sense.
To
your
point
I
mean
if
we
want
to
have
others
contribute
and
currently
it's
hosted
by
by
redhead.
It's
not
where
you'd
like
to
say.
I
wanted
to
be,
and.
B
Is
there
do
you
want?
Do
you
think
it
would
make
sense
for
me
to
write
that
up
and
then
just
share
it
with
the
group
like
in
writing,
like
what
you
know,
some
of
those
some
of
those
areas.
E
Yeah,
I
would
at
least
think
the
requirement
through.
I
don't
think
you
have
to
write
a
full
incubation
due
diligence,
but
at
least
I
mean
the
requirements
are
publicly
on
on
on
the
website
and
or,
if
not
just
reach
out
to
us,
to
see,
okay,
how
it
fits
in
there
yeah
I'm
just
preparing
you,
because
this
might
come
up
again.
We
had
these
conversations
in
the
past
to
be
fair.
E
There
are
other
projects
in
the
cncf
already
that
cannot
graduate
like,
as
we
have
the
githubs
the
open
kit
that
project
they
also
can't
like
really
graduate.
So
we
start
to
have
those
projects
which
are
focused
more
on
education
and
collecting
resources
on
a
lot
of
topics
so-
and
I
think
that's
at
some
point
in
a
conversation
for
the
toc
to
have,
but
I
mean
like
versus,
isn't
it
production
usage?
If
there's
like
15
companies
out
there
that
are
using
it.
B
Yeah
yeah,
so
so
I
mean
we
have,
like
you
know
of
the
I
think,
eight
or
900
people
that
are
subscribed
to
the
mailing
list.
Over
half
of
them
are
outside
of
our
organization
right.
So
it's
like
almost
50
on
there.
We
do
see
usage
and
things
getting
picked
up
by
external
parties,
but
it's
also
tough
to
tell
because
it's
all
upstream
and
there's
no
tethering
back
to
us
on
usage,
but
but
yeah.
E
Yeah,
but
also
next
week,
we
have
the
tuesday,
I
think
it's
next
week
we
have
the
toc
meeting
yes
or
in
two
weeks
the
tc
meeting
again
there.
We
will
also
bring
it
up.
How
do
we
handle
like
these
more
educational
type
of
projects,
to
bring
it
back
on
the
tc
agenda
as
well,
because.
E
B
Yeah
yeah
exactly
yeah,
so
all
the
documentation
that's
being
written
now
is
going
upstream
first
and
it's
all
running
on
kubernetes
and
the
demo
is
all
there.
I
think
there's
there's
some
bits
and
pieces
that
have
some
rough
edges
like,
for
example,
like
sso,
and
things
like
that.
Where
we're
like.
Okay,
we
need
to
make
a
choice
right
on
sso,
even
if
you're
using
vanilla,
kubernetes
and
some
other
things
so
so
those
things
I
think
I
agree,
those
will
work
out.
B
If
there
is
a
separate
designation,
we
should
pursue
that
exists,
I'm
happy
to
do
it.
Otherwise
you
know.
I
think
the
goal
is
to
make
this
like
a
day,
two
part
of
the
platform
where
it's
not
just
point
in
time,
but
it's
then
how
do
you
continue
to
you
know,
evolve
your
application
and
refactor
it,
but
yeah
it's
good
feedback.
I
will
yeah.
E
For
things
for
you
actually
what's
also
helpful
like
in
this
whole
process,
to
point
to,
if
you
have
certain
items
that
you're
actually
working
on
right
now-
and
you
might
have
this
already-
everything
you
which
you
have
is
github
issues
or
maybe
a
dedicated
project
is
also
super
helpful
to
point
people.
To
I
mean
it
feels
that
we
haven't
done
anything
yet
we
are
sandbox
like
the
early
stage,
but
it
is
on
our
roadmap.
It
is
something
we
are
actively
working
on
in
a
well
documented
way
is
always
helpful.
B
E
Discussion
we
can
have
this
as
a
discussion
in
the
in
the
slack
channel
or
we
can
have
a
smaller
group
with
the
chairs.
Whatever
you
prefer,
I
mean
if
you
think
that
there's
something
that
you
want
to
have
in
a
smaller
group.
That's
fine,
too!
If
you
think
you
can
have
the
profession
fully
openly,
then
we
can
just
use
this
live
channel.
A
B
E
I
think
it's
important-
I
just
saw
it
yesterday
and
I
wasn't
wondering
who
was
wondering
as
well,
but
are
you
going
to
show
up
here
and
this
time
or
whether
we
should
invite
you
for
the
next
meeting?
So
I'm
glad
you
could
make
it
today.
E
D
Working
on
qcon
things,
I
guess
that's
the
only
that's
that
that
will
just
be
a
thing,
though.
Just
continue
to
yeah
some
new
planning
getups
come
europe
2022.
D
I
think
things
are
yeah.
I
haven't
been
in
those
meetings
because
you
know
time,
but
as
far
as
I
can
see
that
christian
hernandez
has
started
like
the
process
and
he's
kind
of
like
taking
taking
the
lead
this
time,
as
has
discussed,
you
know
someone
to
actually
need
the
the
effort
so
he's
doing
that
now
and
he's
contacted
everyone
to
start
that
process
and
updates
everyone
and
stuff.
So
so
things
are
happening
there
and
besides
that,
I'm
not
really
sure
to
be
honest.
A
I
mean
I've
got
some
stuff
in
flight,
but
it's
mainly
just
administrative
like
getting
videos
out
there
on
the
web.
A
That
kind
of
thing
but
yeah
like
I
just
got
the
email
yesterday,
setting
up
the
program
committee
for
get
up,
calm
2022.
Here
we
go
again.
F
E
We're
also
looking
into
having
an
app
delivery
related
pre,
coupon
day,
like
on
the
wider
app
every
related
topics
we
didn't
hear
yet
back
from
the
from
the
cncf,
but
the
plan
was
to
also
like
make
it
a
bit
wider
as
well.
I
cover
like
the
chaos
topics
and
like
lots
of
the
works
that
other
projects
are
doing.
D
I
really
really
really
really
want
to
try
to
get
to
valencia,
so
if
things
are
happening
yeah
you
know
with
those
kind
of
events
I
can.
I
can
help
with
stuff-
hopefully
maybe
so
I'm
trying
to
get
there
physically
we'll
see.
A
E
Idea
is
to
have
a
wider,
app
delivery
scope
conference,
also
with
best
practices.
A
couple
of
other
talks,
like
other
tags,
are
doing
it
as
well.
We
have
now,
obviously
lots
lots
more
content
that
we
can
use
also
with
the
ongoing
work
on
chaos.
Cooperative
delivery,
related
topics
that
we're
working
on,
obviously
we'll
also
factor
in
githubs,
but
as
you
must
like
will
have
your
own
github
stay
on
top.
I
think
it
makes
sense
to
have
some
of
at
least.
B
D
Yeah
and
and
and
again,
if
I'm
there,
I
could
do
that
as
well,
depending
on
what
what
type
of
content
on
github.
So,
if
you
just
update,
what's
going
on
in
the
github's
working
group,
I
can,
I
can
work
with
everyone
involved
and
get
something
done
and
present
it,
because
if
I'm
there,
that
should
work
again.
A
D
Is
this
is
in
may
so
may.
D
E
C
I
am
hearing
hey
there,
you
hear
me
it's
something
with
this
there's
a
new
bluetooth
headset,
so
something
has
been
going
back.
It's
it's
nothing!
Major!
I
just
was
what
I
was
saying
before
about
potato
head,
that
I
hope
we
can
use
that
for
the
infrastructure,
stuff
and
and
yeah
so
side,
side
chat
of
the
major.
E
I
think
we
should
and
also
for
the
issues
I
think
we
can
reach
out
to
us
using
it
as
a
demo
by
the
way
the
thing,
but
it
was
initially
the
plan
for
the
potato
head
demo
application
as
well
that
we
currently
did
not
put
in
there
yet
is
also
complex
scenarios
that
are
usually
not
handled
by
demo
apps,
because
they're
mostly
focused
on.
E
C
Maybe
open,
maybe
it
would
be
worth
opening
and
we
should
have
like
a
scenario
kind
of
issue.
Like
here's.
The
scenario
I
propose
can
somebody
you
know
put
this
together:
stateful
app
or
migrating
from
a
monolith
or
something
like
that.
E
D
Yeah,
I
think
I
think
those
kind
of
things
also
is
something
that
might
come
out
of
like
the
survey.
I
try
to
have
questions
that
also
ask
like
what
is
you
know?
What
is
the
problem?
Do
you
have
a
problem?
You
know
not
that
question
in
particular,
but
it
doesn't
lead
anywhere,
but
something
intervals
to
that.
So
we
can
get
to
see
what
like
kind
of
pain
point
people
have
when
it
comes
to
these
things.
Hopefully
that
might
help
also,
you
know,
set
the
direction
a
little
bit.
E
E
C
E
D
Well,
maybe
not
survey
results.
It
depends
on
how
quick
we
can
get
that
out
and
and
who
is
so.
I
have
no
clue
how
that's
going
to
work
yeah,
but
at
least
done
like
the
questions
and
everything
like
that
should
be
done.
But
then
I
guess
something
really
bad
happens.
C
D
E
Keep
in
mind
a
lot
of
tags
and
projects
want
to
engage
with
the
end
user
community
and
they
might
be
deliberately
throttling
a
bit
so
that
people
don't
get
10
services
a
week.
Yes,
so
that
might
then
also
take
a
bit
so
one
I
think
as
soon
as
we
have
something
like
also
sharing
it
in
our
own
social
channels
and
starting
at
this
concussion
around.
What
we
find
might
be
the
quicker
way
to
actually
do
this.
A
D
Even
quicker,
so
if
we
got
like
the
survey
out
and
got
it
kind
of
like
unofficially
spammed
out
across
channels
and
then
maybe
later,
cncf
would
boost
that
at
the
end
to
just
get
like
the
you
know.
So
they
can,
you
know,
pace
things
out
as
they
wish,
but
still
we
kind
of
get
some
results
in
and
see
that.
E
D
E
We
don't
make
it,
we
don't
need
to
make
it
scientifically
complete.
This
is
just
really
getting
piles
of
the
community
out
there
what
they're
working
on
and
what
might
be
helpful
for
them,
and
I
think
we
can
do
that.
Can
you
maybe
share
it
also
on
the
slack
channel
with
people.
The
survey
questions
you
just
just
just
can
get
some
feedback
on
it.
D
Yes,
I
will
I
have
that
on
my
to-do
list,
so
that
would
happen
hopefully
before
the
weekend,
because
how
things
are
these
days
I'll
get
that.
A
E
As
we
go
and
then
more
people
can
contribute,
you
can
see
this
now,
something
as
we
say.
Well,
you
have
to
submit
to
the
server
in
the
next
one
to
two
weeks,
but
as
we
have
like
the
first
results
coming
in
people
may
be
contributing
as
we
go
yeah.
I
just
found
surveys.
They
sound
so
easy
to
do
but
turn
out
to
be
so
hard
because
everybody
wants
to
do
surveys
and
people
just
nah,
not
yet
another
survey
that
that
that
I
wanted
to
do.
D
Yeah,
that's
yeah
yeah,
that's
unfortunately,
but
but
I
I
will
I'll
try
to
get
something
specifically
done
and
see
get
some
feedback
on
the
questions,
at
least
before
something
gets,
I
guess,
put
into
a
form
of
any
sort.
So
we
so
we
all
agree
that
these
are
questions
that
we
want
answered
or
not.
F
Yeah
to
me,
it's
like,
I
understand
that
the
survey
itself,
like
sometimes
doesn't
get
much
engagement
but
like
just
knowing
like
agreed
like
what
are
we
wanting
to
know
helps
like
with
like
proactively,
you
know
getting
like
trying
to
get
the
information
getting
help
like
I
can
speak
to
you
know
we
can
get
the
information,
so
it
would
be
easier
for
me
to
just
to
understand
how
like
what
everyone
is
agreeing
on.
B
Yeah,
I
think
we
surveyed,
like
several.
We
have
a
firm
going
out
research,
firm,
external
research,
firm.
I
think
it's
400
500,
it's
all
speaking
because
of
budget
reasons,
but
it
was
like
us,
uki,
australia,
new
zealand,
singapore,
a
couple
other
countries
with
a
sample
size
of
like
400
500
enterprises,
and
it
was
kind
of
asking
like
rehost
three
platform,
refactor
kind
of
questions
like
what.
What
are
you
thinking
about
doing
in
these
areas?
B
What
percentage
of
your
workloads
do
you
think
fall
in
this
is,
like
you
know,
frameworks
and
languages
you're
using
on
top
of
kubernetes
those
sorts
of
things,
so
I'd
be
happy
to
share
it
and
that's
actually
we're
planning
on
having
it
done
in
january
and
then
just
branding
it
with
conveyor.
And
then,
if
we
have
like
the
cncf
thing,
put
that
in
there
too,
to
kind
of
promote,
I
think,
the
the
dual
brands.
So
I'm
happy
to
collaborate
beyond
that
if
it
helps.
E
Okay,
like
that,
we
have
some
action
items
here
and
james.
We
just
take
that
further
feedback
from
the
toc
and
follow
up
on
it
again.
My
point
doesn't
just
help
closing
in
because
I
don't
want
you
to
go
in
circles
like
the
next
time.
The
next
question
comes
up
that
it's,
I
think
well
prepared
yeah.
I
appreciate
it
and
yeah.
I
think.
A
E
A
E
E
A
E
D
E
D
E
Yeah
we're
not
really
violating
any
trademarks,
but
it's
always
great
to
see
it
on
twitter
as
well,
by
the
way
for
those
who
haven't
seen
it.
Yet.
E
E
Like
all
the
arms
and
the
feet
are
obviously
micro
services,
so
I
think
it's,
the
potato
head
is
like
more
or
less
the
the
children's
version
of
how
to
explain
microservices
to
them
like
each
of
them
has
a
specific
responsibility,
but
they
all
work
together
and
you
can
exchange
them.
You
can
even
show
blue
green
deployments,
as
you
can
see
here,
with
the
legs
which
are
actually
blue
deployed
in
this
case.
E
E
Nobody,
it's
a
helpful
and
fun
way
to
to
use
it,
and
I
mean
one
of
the.
The
design
goals
was
as
well
to
make
this
small
enough
that
people
can
run
it
on
a
small
kind
cluster
on
their
laptops,
because
that's
especially
feedback
we
got
from
people
who
want
to
learn
something
they
say
well,
I
know
I
can
have
like
some
free
cluster
credits,
but
then
I
need
to
do
it
and
I'm
a
student.
E
E
C
It
doesn't
use
any
dependent
infrastructure,
I
mean
other
than
kubernetes
itself.
It's
just
that.
But
it's
interesting
that
you
just
brought
that
up,
because
if
I
start
trying
to
add
in
databases
and
cues
and
other
things,
I'm
going
to
make
sure
that
it
doesn't
get
in
the
way
of
that
at
least
it's
just
optional
or
something.
E
Okay,
then
I'm
giving
you
six.
I
ended
up
meeting
six
minutes
early,
which
houses
free
gives
you
time
to
grab
a
coffee
or
do
whatever
you
want
to
do
with
six
minutes.
We
all
spend
too
much
time
in
meetings.
Anyways,
I'm
glad
seeing
all
of
you
all.
There
are
new
people
showing
up
here
and
hopefully
talk
to
you
soon
in
two
weeks.
From
now.