►
From YouTube: CNCF TAG App Delivery 2021-09-01
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
B
C
A
All
right
guys,
I
think
jennifer-
is
feeling
unwell
today,
so
I
will
be
hosting
the
meeting
for
this
for
today.
Like
welcome
to
join
this
meeting
like
I
think,
let
me
see
it's
always
here
today.
No,
but
we
are,
but
I
think
we
can
get
started
on
the
meeting
right
now.
A
Okay,
so
please
let
me
post
the
meeting
schedule
we
can
talk
because,
oh
I
see
it
it's
already
here
anyway,
so
yeah
so
first
of
all
feel
free
to
add
your
name
to
the
attendees.
A
So
so
the
first
meeting
item
is:
we
will
have
james
to
give
an
update
on
the
conveyor
and
sandbox
application
submission
james.
Like
would
you
take
a
look.
B
Yeah,
thank
you.
Let
me
share
my
screen.
Actually,
let's
see
if
I
can
do
that,
I
guess
I'll
have
to
share
my
whole
desktop,
which
is
fine.
So
let
me
do
that.
Hopefully,
you
can
see
my
screen
share.
If
you
can't
please
let
me
know.
B
Thanks
ramon
yeah,
so
thanks
for
the
time
everybody
so
the
conveyor
community,
you
could
find
us
at
conveyor.io
we're
looking
to
submit
actually
for
sandbox
status
from
the
cncf
so
prior
to
doing
that,
I
wanted
to
get
feedback
from
this
group
and
see
if
there
were
anything
we
should
consider
before
we
actually
make
the
submission
in
the
google
form.
B
So
we
have
kind
of
a
series
of
projects
inside
of
conveyor
around
those
different
areas:
re-hosting
re-platforming
and
refactoring-
there's
kind
of
five
main
projects
inside
there
that
we're
working
together
with
you
know.
I
just
wanted
to
share
this
document.
I
could
probably
I
don't
know
if
this
is
this
is
probably
I
should
have
done
it
under
the
conveyor
community.
B
Sorry,
I
think
I
did
it
in
my
own
gmail
account,
so
I
could
share
this
as
a
follow-up
with
all
of
you,
if
you're
interested
in
looking
at
our
answers
and
commenting
on
them.
B
But
the
reason
we
want
to
put
this
into
the
cncf
community
because
we
believe
that
they're
in
why
we
want
to
donate
this
to
the
foundation
and
work
more
closely
is
because
we
believe
that
there
are
many
other
customers
and
partners
and
even
vendors
that
would
like
to
participate
and
by
putting
in
the
foundation,
we
think
we'd
encourage
more
participation,
we've
already
put
in
place
a
contributor
ladder,
a
governance
model,
a
code
of
conduct
and
all
those
things
and
everything
is
licensed.
B
Apache
too,
I
believe
all
the
projects
are
apache2
licensed
inside
of
the
community,
and
so
we
we
have.
You
know
we'd
like
to
kind
of
go
ahead
and
move
forward
with
placing
this
in
there.
B
We
don't
believe
that
there's
anything
inside
the
cncf
today
that
addresses
the
onboarding
of
applications
of
like
application
modernization.
A
lot
of
it
is
focused
on
new
technologies,
but
not
necessarily
moving
people's
applications
into
there.
So
we
think
it
could
also
be
valuable
to
the
community.
From
that
perspective,
there
are
some
projects
outside,
so
so
we'll
help
move
people
to
kubernetes,
but
also
cube
rook
cni
csi,
so
we
actually
integrate
with
some
of
those
existing
projects
already
and
the
outside
of
the
cncf.
B
There
are
some
similar
projects
that
you
see
listed
here,
such
as
open
rewrite
and
others.
Some
of
these
that
we're
actually
actively
contributing
to
already
valero
is
one
that
we
have
developers
on
the
conveyor
community
that
are
also
contributing
to
valero,
and
one
of
the
projects
is
looking
at
integration
with
open
rewrite.
So
there
is
opportunity
to
bring
more
projects
in
and
integrate
with
the
conveyor
project,
and
so
I
just
wanted
to
kind
of
share
this
and
there's
an
existing
overview
of
the
presentation
but
prior
to
submitting
for
sandbox.
B
We
wanted
to
discuss
this.
I
also
invited
suresh
veda,
I
don't
know
if
he
was
able
to
join.
I
know
he
he
is
actually
at
wells
fargo
and
they
are
using
one
of
the
projects
today
actively
to
help
analyze
their
existing
java
applications
to
modernize
them
and
migrate
them
over
to
kubernetes,
and
so
you
know
he
he
also
saw-
and
it
thinks
it's
a
good
idea
for
us
to
commit
this-
to
the
foundation
to
have
external
contributors
such
as
wells
fargo,
but
even
others
in
the
future.
B
So
let
me,
I
guess,
pause
there.
I
could
stop
sharing
this
specific
document,
but
I
can.
I
can
share
a
link
to
it
in
a
in
a
fashion
that
you
can
all
comment.
I
don't.
E
C
And,
as
you
highlighted,
I
think
one
of
the
most
important
components
of
the
sandbox
submission
is
to
identify
overlap
with
other
cncf
projects
and
the
alignment,
and
we
can
take
a
look
at
that.
I'm
sure
we'll
have
some
feedback
subsequently.
B
Yeah,
I
put
a
link-
I
I
will
add
it
so
that
it's.
B
And
then
yeah-
and
I
probably
should
have
started
so
by
way
of
introduction.
I
I
work
at
red
hat
and
then
todd
who's
on.
The
call
is
one
of
the
engineering
managers
at
red
hat.
That
is
a
lot
of
his
team.
Are
developing
these
projects
upstream
jonathan's
been
doing
a
lot
of
the
community
community
advocacy
and
kind
of
growing
out
the
community,
and
then
ramon
is
one
of
the
product
managers
for
a
downstream
offering
based
on
this
upstream
community
so
and
josh.
E
Yeah
and
I'm
also
on
cncf's
tag
contributor
strategy,
so
I've
been
working
on
conveyor
both
from
the
perspective
of
red
hat
osbo,
trying
to
get
it
contributed
and
also
tag
contributor
strategy,
making
sure
that
incoming
projects
actually
have
all
of
their
paperwork.
F
Just
to
get
it
started,
so
we
talk
a
lot
in
this
group
about
delivery
pipelines
and
things
like
that
does
conveyor
fit
in
before
the
delivery
pipeline.
Like
I
convert
and
then
I'll
use,
say
flux
or
something
to
deploy,
or
does
it
actually
extend
all
the
way
to
the
full
delivery
too.
B
Yeah
yeah,
that's
a
good
question.
I
I
could
maybe
try
and
take
it
a
little
bit
and
then
I'll.
Let
ramon
and
todd
kind
of
maybe
speak
to
specific
use
cases.
So
there's
five
projects
inside
of
conveyor
right
now:
forklift
crane
tackle
polaris
and
move
to
cube,
and
so
they
each
have
a
specific.
B
You
know
area
that
they're
focused
on
forklift
as
an
example
will
take
virtual
machines
and
re-host
them
into
cube
vert.
So
it's
just
a
re-hosting
tool.
Crane
is
essentially
what
it's
doing
is
it's
helping
you
migrate
applications
between
kubernetes
clusters,
but
in
that
process
of
migrating
between
kubernetes
clusters,
what
we're
find
what
we've
found
is
that
it's
not
just
about
moving
the
persistent
data,
but
it's
about
automating.
B
The
application
deployments
is
the
bigger
challenge
that
most
people
face
because
they've
manually
deployed,
and
so
crane
is
actually
looking
at
solving
that
problem
by
helping
them
automate
their
application
delivery
as
part
of
migration,
and
then
the
tackle
project
basically
does
assessment
and
analysis
of
your
applications
for
refactoring.
B
So
it
has
both
a
human
element
of
asking
you
questions
and
then
determining
like
the
risks
for
containerization.
Like
do
you
have
access
to
the
source
code?
You
know
those
those
sorts
of
questions
and
then
the
analysis
piece
does
static,
both
static
code
analysis
and
then
it
can
do
decompilation
of
java
applications
specifically
and
then
look
for
there's
a
series
of
rules
that
will
look
for
things
that
violate,
say.
You
know
12
factor
app
rules
like
local
file
systems
or
hard-coded
ip
addresses
and
start
to
flag
those.
B
F
B
Yeah
yeah
right
right
now
they
yeah
right
now,
they're
distinct,
so
yeah.
I
think
over
time
it
would
be
great
to
bring
them
together
and
because,
like
we're,
the
tackle
project,
for
example,
has
an
application
inventory.
So
it
would
be
great
to
have
like
you
know
some
of
these
integratable,
but
at
the
same
time
we
we
don't
want
to
build
like
something
that's
bloated.
I
guess
you
know
over
time.
D
Yeah,
but
that
that
kind
of
use
case
is
something
that,
for
example,
he
moved
to
cuba
is,
is
willing
to
address
in
the
future.
The
idea
of
being
able
to
create
suitable
deployment
manifests
for
for
an
application
that
comes
from
a
more
traditional
platform
out
of
the
source
code
by
analyzing,
the
the
type
of
application
that
it
is
and
creating
these
deployment
manifests.
D
B
A
So
james,
I
have
one
question
about
like
I,
I
saw
that
that
conveyor
is
trying
to
like
modernize
my
legacy
like
java
applications
into
like
kubernetes
applications
like
not
like.
If
I
have
a
job
application,
I
do.
I
still
have
to
build
an
image
right.
This
is:
is
it
this
process,
something
that,
like
conveyor
like
automatically
generate
an
image
for
the
java
application?
D
Yeah
yeah,
that's
that's
something
that
we
would
like
to
do
in
the
future.
That's
something
that
it's
not
happening
right
now.
It's
a
news
case
that
we
are
analyzing
right
now.
What
we
have,
for
example,
in
the
tackle
project,
which
is
more
focused
on
bringing
traditional
workloads
towards
kubernetes,
is
more
about
analyzing,
the
application
source
code
to
try
to
find
anti
patterns
that
would
prevent
the
the
application
from
running
on
on
containers.
D
So
it's
it's
more
focused
on
the
actual
application
architecture
and
the
source
code
and
finding
anti-patterns,
rather
than
automatically
generating
some
artifacts
to
have
it
deployed.
So
one
of
the
things
we
were
talking
about
was
the
deployment
manifest
in
in
in
kubernetes.
That's
something
we're
looking
into
with
move
to
cube
both
move
to
cuban
tackle
about
the
images
it's
something
that
we
we're
studying
as
well.
That
is
something
that
we're
not
quite
there
just
yet,
but
it's
something
that
will
happen
eventually.
B
Maybe
I
suresh
joined,
I
know
I
thought
I
don't
think
he
was
having
trouble
catching
a
link.
So
suresh,
I
don't
know
if
you
want
to
introduce
yourself
and
kind
of
explain.
You
know
your
your
interest
in
the
project
and
that
sort
of
thing
but
feel
free,
sure.
G
Yeah
yeah
myself,
I'm
the
enterprise
architecture
in
wells
fargo,
and
we
started
looking
at
two
of
the
tools
under
the
conveyor
chain.
One
of
them
is
the
mta
toolkit
and
then
the
move
to
cube
as
well
the
main
intent
that
we
were
looking
at
these
two
offerings,
where
primarily
for
taking
applications,
java
applications
running
on
legacy
platforms,
and
then
you
know
be
able
to
migrate
them
to
target
platforms
of
our
choice.
G
The
specific
use
case
that
we
were
looking
for
is
moving
from
workloads
from
weblogic
to
tomcat,
which
is
the
initial
journey
right,
and
once
we
last
moved
from
weblogic
to
tomcat,
then
the
next
step
is
obviously
to
see
what
we
can
do
to
containerize,
that
application
make
sure
that
it
is
cloud
ready.
Bending
the
cloud
compliancy
related
reports
as
well,
and
once
it
is
all
cloud
compliant
then
container,
is
it
and
move
it
into
our
internal
kubernetes
environment
and
eventually
to
the
cloud
as
well
right.
G
So
that
is
the
journey
that
we
wanted
to
take
it
to
words
and
we've
had
we've
done
some
pocs
to
that
hand,
and
it
has
given
us
good
research
right.
So
the
migration
toolkit
for
applications
is
the
one
that
I'm
specifically
talking
about.
It
externalizes
the
rules
in
a
in
an
xml
file
and
you
can
like
go
in
there
and
that
is
like
already
out
of
the
boss.
There
is
like
a
bunch
of
roots
that
we
get
to
use
there.
G
Those
are
specifically
meant
for
moving
to
the
jboss
application
server,
but
most
of
those
rules
are
pretty
much
the
same.
If
you
are
targeting
something
like
a
contact,
so
you
can
take
those
rules
and
customize
them
a
little
bit
and
you'll
be
able
to
apply
and
generate
a
report
that
allows
you
to
take
these
java
applications
from
something
like
web
logic,
and
then
you
know,
apply
those
recommendations
and
generate
a
new
version
of
the
application
that
is
compliant
for
running
on
tomcat.
G
That
is
where
the
cloud
readiness
report
comes
in
handy,
and
that
is
another
offering
from
the
mta
toolkit
as
well,
so
you'd
be
able
to
generate
a
cloud
readiness
report
there
and-
and
you
might
notice,
when
you
look
at
those
rules,
that
a
lot
of
those
rules
are
in
line
with
the
12-factor
12
compliance
methodology,
development
methodology
so
you'd
be
able
to
take
those
12-factor
related
correlations
and
you'll
be
able
to
address
all
of
them
by
generating
those
reports.
G
G
It
will
generate
your
deployment
yamas
the
docker
files,
as
well
as
the
actual
container
images
also,
and
it
be
able
to
actually
push
it
to
the
container
repository
of
your
choice.
You'll
be
able
to
use
the
scripts
that
are
generated
for
pulling
down
those
container
images
and
then
deploy
them
to
the
kubernetes
environment.
You
are
not
limited
to
your
own
internal
environment.
G
If
you
are
deploying
it
to
aks,
gke
or
aws,
the
options
are
available
also
as
part
of
the
tool,
and
a
lot
of
the
configuration
can
be
managed
in
such
a
way
that
you
know
that.
But
by
default
this
youtube
cube.
It
will
last
a
number
of
questions,
but
there
is
configurations
available
in
there
where
you
can
like
put
in
a
bunch
of
defaults,
and
that
will
like
make
this
whole
experience
a
lot
more
smoother.
G
So
that
is
something
that
we
are
looking
closely
at
and
we
are
working
on
a
process
of
taking
my
modern,
modernizing
our
internal
application
portfolio
and
these
tools
are.
We
are
looking
at
these
tools
very
closely
to
see
how
they
are
going
to
help
assist
in
moving
those
workloads
to
the
new
future
platforms
that
we
are
targeting.
D
Yeah,
just
just
to
to
clarify
some
things:
mta,
it
has
been
a
product
of
wrecked
at
red
hat.
For
some
years
already,
there
was
an
open
source
project
behind
it,
windup,
which
was
the
upstream.
We
are
contributing
this
this
project
to
the
whole
conveyor
in
each
initiative
under
the
tackle
project,
which
is
focused
on
this
refactoring
of
of
applications.
D
So
we
have
the
tackle
end,
which
basically
provides
insight
for
the
architects
to
to
make
some
informed
decisions
on
which
is
the
path
they
want
to
follow
when
modernizing
and
bringing
their
applications
on
board
on
kubernetes,
and
also,
we
have
moved
to
cube,
which
goes
through
a
more
maybe
opinionated,
but
automated
path
to
bring
these
applications
into
into
kubernetes.
So
there's
there's
enough
freedom
for
for
the
decision
maker
to
decide
which
is
the
path
they
want
to
follow
when
adopting
kubernetes
and
moving
their
workloads
towards
kubernetes.
B
Yeah
also
just
to
note
so
suresh
and
wells
fargo
they're,
not
using
red
hat's,
kubernetes
distribution.
So
just
there's
a
point
of
showing
that
we're
actually
trying
to
build
tooling
that
helps
people
move
to
kubernetes
and
cloud
native.
That's
not
really
tied
to
anything
specific
inside
of
our
distribution,
and
we
are,
I
think
we.
We
really
firmly
believe
that
this
is
a
gap
and
that
if
every
system,
integrator
and
every
cloud
provider
and
red
hat
included
builds
their
own
tooling.
B
G
In
fact
to
to
stress
further
on
the
point
right,
originally,
our
intent
was
looking
at
only
java
applications,
but
if
you
look
closely
at
the
rules
for
the
mta
toolkit,
it
is
actually
doing
pattern
matching
and
then
based
on
that
it
is
generating
all
these
reports
and
that
kind
of
pattern
matching
is
not
language
specific
right,
so
it
can
like
do
direct
source
code
scans,
so
it
you
don't
have
to
necessarily
limit
yourself
to
java
based
projects.
G
If
you
are
having
other
languages
that
pattern
matching
capability
can
be
extended
as
well
to
these
other
spheres,
and-
and
we
have
like
looked
at
some
of
the
competitor
tools
out
there-
some
of
them
commercial
in
nature
as
well.
The
quality
of
reports
that
are
getting
generated
is
a
lot
more
developer
friendly
when
it
comes
to
the
mta
tooth.
You
certainly
have
noted
that
and
our
development
teams,
when
we
showed
these
reports
to
them,
we
really
loved
what
what
was
what
they
were
getting
out
of
this.
C
Just
one
final
question:
from
from
my
side,
do
you
see
yourself
expanding
your
usage
of
the
tooling
available.
C
G
Yeah
so
so
see
at
this
point
of
time,
we
are
in
the
process
of
evaluating
and
recommending
it
right
from
architecture
perspective.
That
is
my
job
right
to
be
able
to
analyze
these
tools
and
put
in
the
recommendation
and
then
the
various
business
line
of
businesses.
It
would
be
them
that
would
be
ultimately
deciding
and
that
is
not
desired.
At
this
point
of
time,
I
have
like
multiple
meetings
where
I
am
presenting
to
the
various
cios
within
the
organization
to
see
whether
they
are
interested
in
moving
forward
with
this.
G
They
are
very
close
to
making
that
decision,
but
it
is
not
desired.
At
this
point,
I
probably
know
in
like
another
couple
of
weeks
time
whether
we
are
going
to
be
investing
in
this
and
moving
forward
or
not.
C
F
One
other
question:
so
it's
fresh
you
brought
this
so
is
that
does
tackle
only
address
java
apps
right
now
and
if
so,
is
it
extensible
easily?
I
mean
to
what
suresh
said:
do
you
all
see
us
adding
other
things.
D
Yeah
for
the
moment,
tackle
only
works
with
java
application
applications
on
the
analysis.
Bit
of
it
I
mean
tackle,
is
aimed
at
becoming
a
toolkit,
so
the
analysis
bit
of
it
is
just
a
part
of
the
whole
thing,
so
we
have
different
components.
We
already
mentioned
the
application
inventory.
We
have
also
pathfinder,
which
is
for
a
high
level
assessment
of
your
application
portfolio.
Let's
say
that's
that's
the
questionnaire-based
tool
that
james
was
referring
before
so
in
terms
of
analysis,
the
attack,
the
tackle
analysis
bit
is
focused
on
on
java.
D
Only
but
for
the
moment
we're
aiming
at
expanding
this
thing
because,
as
suresh
said,
we're
doing
pattern
matching
the
the
analysis.
Engine
that
we're
using
should
be
should
not
should
not
be
tied
up
to
any
language,
but
since
we
had
the
actual
knowledge
about
java
migration
based
on
our
own
expertise
on
consulting
doing
these
things,
that's
the
knowledge
that
we
we
shared
but
yeah.
I
I
see
the
the
possibility
of
getting
into
other
languages
as
well
with
the
future.
B
So
so
we
would
definitely
be
open
to
contribution.
We've
had
requests
around
that,
but,
as
you
could
imagine,
red
hat
doesn't
have
a
lot
of
like.net
experience
and
things.
So
so,
but
you
know
we'd
be
happy
to
have
the
the
help
from
anybody.
That's
interested.
G
D
I
don't
think
so:
no,
it's
it's
just
a
static
analysis
of
of
source
code
and
pattern
matching,
and
and
that's
it
at
least
for
the
moment.
So
we
don't
that's,
that's
why
it's
flexible
enough
to
work
with
other
languages
as
well,
so
we're
not
getting
into
the
actual
jbm
and
running
anything
just
to
do
reflection,
as
you
were
saying,
there's
there's
not
that
much
gobbling.
If
you
want
to
see
it
that
way
with
the
java
language.
B
Cool
great
well,
if
there
aren't
any
other
questions,
I
know
I've
shared
the
document
and
with
several
of
you
already
sorry
for
having
you
you
needing
to
request
access,
we'll,
try
and
move
it
over
to
the
conveyor
account
that
we
have
that's
open,
wide
open
and
then,
if
you
have
any
comments
or
questions,
feel
free
to
reach
out.
C
Last
question
was:
when
are
you
aiming
to
submit
you're
looking
to
do
it
this
week
like?
When,
do
you
need
your
feedback
bye.
B
C
Yeah,
I
think
it'd
be
good
to
get
alois
who's.
Not
here
co-chair
to
have
a
look
at
it
as
well
and
thomas
who's.
The
co-tech
lead
I'll
I'll
mention
to
them
and
we'll
make
sure
that
we
have
a
look
at
it
prior.
B
B
C
Okay,
I
think
we
can
do
it
asynchronously,
but
yeah
we'll
aim
for
this
week.
Thank
you.
A
And
and
gems,
I
think
the
link
that
you
post
in
the
meeting
doc
is
is
not
publicly
like
viewable.
If
you
can
upload
the
link
to
something
that
other
people
can
comment
on.
Yeah.
B
Yeah
I'll
switch
over
to
the
conveyor
account
now
and
and
and
and
create
a
new
dock,
put
it
all
in
there
and
then
share
it
in
the
chat.
A
So
we
can
go
to
the
next
topic.
It's
about
the
potato
head
reviews
like
I
think
josh.
I
can
hand
it
to
you,
but
you
can
take
over.
F
Sure
so
I
just
I
wanted
to
discuss
this
a
bit
since
a
few
weeks
ago,
when
we
merged
in
the
the
first
multi-service
support,
I've
been
working
on
the
repo
trying
to
gradually
update
the
other
scenarios
and
examples
there's
other
things
we
want
to
do
in
the
future.
But
this
is
like
that
we
have
to
get
these
moved
to
the
new
wealthy
service,
so
I
just
wanted
to
present
them.
F
I
haven't
gotten
they've
been
up
there
for
like
a
little
over
a
week
and
if
I
just
I'm,
not
sure
even
who's
supposed
to
review
them,
but
one
of
them
updates
the
the
github
action
so
that
people
can
build
and
test
in
their
own
forks,
and
I
use
that
pattern
now
in
the
in
the
ones
that
I've
addressed
so
far,
which
are
cube,
cuddle,
helm,
customize
and
catch
there's
a
test
in
each
one,
and
now
the
github
action
with
the
updated
github
action.
You
can.
It
runs
that
test.
F
F
You
know
it's
it's
a
tricky
thing
now
that
we
have
like
five
or
six
services
there,
so
I've
described
them
each
in
their
own
yaml
file,
and
you
know
and
may
not
customize
through
them
just
need
a
review
on
that
and
then
catch
which
was
pretty
tricky
actually
so
that
one,
I
also
got
updated
a
pretty
big
update
from
0.2
or
whatever
we
were
at
the
point
for
so.
F
C
Thanks
josh,
I
can
take
this:
do
you
if
you
want
to
assign
them?
I
can
make
myself
the
default
reviewer,
because
I
think
I'm
more
active
than
thomas
and
I've
just
approved
your
github
actions,
pr.
They
take
me
quite
a
while
to
read
because
they're
quite
large
pr's,
but
it's
the
first
time
I've
seen
them
so
just
poke
me
if
they,
if
pr's
in
this
repo,
don't
get
moved.
I'm
gonna
move
myself
to
the
default
reviewer
right
now,
but
these
are
great.
C
So
thank
you
so
much
for
contributing,
because
it
looks
like
a
really
good
foundation
for
making
this
the
canonical
resource
that
we're
going
to
use
going
forward
so
I'll
make
sure
that
all
of
these
are
reviewed
by
this
week,
the
github
pr
for
actions
I'm
going
to
merge
in
right
now,
okay,.
C
And
again,
just
maybe
for
folks
who
aren't
particularly
familiar
with
this
repository
potato
head
is
becoming
the
cornerstone
of
the
new
working
group
that
we're
establishing
for
cooperative
delivery,
where
we
can
illustrate
some
examples
of
patterns
of
application
and
infrastructure
delivery.
So
whatever
your
technology
or
platform
you
might
be
using,
there
might
be
a
use
case
where
you
could
use
potato
head
and
you
could
use
it
at
kubecon
in
your
in
your
talks,
as
well
as
a
as
a
kind
of
a
touchstone
reference.
C
It's
a
pretty
simple
service,
but
josh
and
and
others
have
been
doing
a
lot
of
great
work
in
making
it
useful
right
and
representative
of
something
that
might
be
used
in
production
with
various
micro
services.
So
please
check
it
out
and
if
you're
interested
do
collaborate
and
contribute.
Thank
you.
A
Cool
yeah
alex:
do
you
have
permission
on
the
repo?
You
can
merge
the
pr.
C
Yeah,
I've
got
I've
got.
I've
got
all
permissions
other
than
changing
defaults.
Actually,
so
I
can
add
myself
to
reviews,
but
I
cannot
change
the
default
reviewers,
but
I
can
I've
merged
that
initial
pl.
A
Yeah,
so
I
think
that's
all
we
have
for
today's
meeting
thanks
for
the
converse
team,
also
josh
for
the
updates-
and
I
think
that's
all
for
today's
meeting
anything
anything
some
any
any
questions
in
the
last
minute.
If
you
know
probably,
we
can
end
this
meeting
for
today.
C
I
just
had
one
final
update
hong
chow,
which
is
the
cooperative
delivery
group,
has
almost
finished
toc
coc
vote.
So
it
looks
like
we're
going
to
try
and
get
that
rolling
in
the
next
week
or
two
so
just
stay
tuned
for
that.