►
From YouTube: CNCF Cooperative Delivery WG 2022-05-11
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
A
Yeah
thanks
for
posting
about
it
in
a
couple
places,
it's
been
chicken
and
egg
like
we
want
to
build
momentum,
but
at
the
same
time
you
can't
build
momentum
without
having
momentum.
So.
A
A
Nobody
likes
middleware
and
integration,
but
I
feel
like
infrastructure
is
the
the
new
middleware
in
some
ways.
A
You
just
think.
Oh,
it's
an
integration
problem.
I
gotta
work
with
my
ci
cd
team.
What
we're
trying
to
do
is
kind
of
level
that
up
is
say:
hey.
We
got
20
different
companies
each
with
their
own
bespoke
ci
cd
pipelines
to
coordinate
all
this
stuff.
Let's
learn
from
each
other
and
develop
some
patterns,
and
you
know
and
like
it
could
be
in
like
a
year,
we'll
come
up
with
the
it
will.
A
A
Yeah,
so
we
could
talk
thomas,
but
I
don't
know
if
I
don't
know
if
we're
gonna
get
more
folks
here
I
was
hoping
the
one,
the
the
on
the
multi-tenancy
stuff,
something
I've
been
going
through.
A
lot
is
the
tenant
orient.
Sorry,
the
cluster
oriented
multi-tenant,
stuff,
kcp,
v-cluster
and
red
hat
has
something
called
hypershift,
which
is
a
way
to
host
one
cluster
in
another
cluster
and
serve.
A
Using
cluster
as
the
unit
of
multi-tenancy,
that
was
one
of
the
things
that
I
kind
of
thought
we
might
talk
about,
is
name
space
versus
cluster
as
unit
of
tenancy
and
and
also
multi-tenancy
for
other
infrastructure.
Besides
clusters
that.
A
A
C
I
think
for
them
for
one
of
the
next
meeting,
so
so
what
our
next
steps
should
be
for.
We
should
try
to
write
a
very
short
blog
post
about
the
things
you
mentioned
now,
so
about
the
about
the
ideas
about
tenancy
and
we
don't
have
we
don't
have
to.
We
don't
need
to
have
a
solution
for
that
in
a
blog
post,
but
at
least
we
could
state
that
there
is
something
like
this
and
just
release
a
blog
post
and
just
to
just
to
get
people
on
board.
Hello,
alex.
C
A
I
yeah
hey
alex
thanks
for
joining.
I
have
a
couple
guys,
yeah,
that's
actually
a
great
idea:
I've
been
thinking
of
putting
together
a
blog
post
on
my
own
about
the
different
virtual
clustering
options
so
yeah.
If
we
want
to
publish
it
under
tag,
app
delivery
and
use
that
use
that
yeah
I
can.
I
can
do
that.
I
can
share
that
so
I'll
write
up.
It
should
hopefully
the
next
few
days
I'll
write
something
up
and
then,
but
I
have
to
figure
out
how
to
publish
it.
I
guess
work
with
who.
C
A
C
D
Yeah
yeah,
that's
why
why
I
joined
I
it's
been.
It's
been
a
while
since,
since
the
last
time
I
joined,
I
wanted
to
check
what's
happening
with
that
and
if
you
need
any
help
somewhere.
A
Yeah,
I
think
we
we
definitely
need
to
help
on
this
paper.
We
could
lead.
You
know
we
could
use
someone
to
lead
the
effort.
I
think
right
now
we
might
discuss
what
it
would
contain.
Some
of
the
things
thomas
and
I
were
just
discussing-
were
I
was
talking
about
cluster
level
tenancy,
but
another
thing
is
tendency
for
other
aspects
of
infrastructure,
so
yeah
I
just
wanted
to
open
the
conversation
about.
You
know
what
we
think
is
going
to
be
in
here
and
yeah.
Can
somebody
kind
of
take
the
next
steps?
E
A
Kubernetes
has
a
sig
multi-tenancy
and
they
actually
drop.
I
dropped
into
the
dock
here
into
our
notes,
dock,
which
I
can
show
the
nuts
link
to
their
dock,
which
they're
about
to
publish.
A
A
A
A
B
E
B
E
A
E
A
Yeah,
I
don't
know
so
yeah.
Are
we
saying
that
this
is
enough?
The
kubernetes
multi-tenancy,
the
only
thing
that
I
could
think
of
in
addition?
Well,
two
things:
one
we
could
emphasize
projects
in
cncf
if
we
wanted
like
v
cluster
and
stuff
like
that,
and
I
think
that's
sciencia
and
the
other
is
other
infrastructure
besides
kubernetes.
So
that's
what
I
was
talking
about
before
you
came
in
like
let's
say
I
need
a
space
in,
I
don't
know
jenkins
or
a
database
or
an
identity
provider.
How
do
I
make?
A
How
do
I
get
that?
Is
that
a
problem
that
people
are
having?
Maybe
it's
you
know,
I
don't
know
you,
you
declare
a
resource
type
and
it
provisions
it
grant.
How
is
that
working
in
the
is
that
all
I
mean
it's
using
the
multi-tenant
stuff
from
the
clouds
that
it's
provisioning
from,
or
I
don't
know
I.
A
E
Of
that's
an
interesting
story,
the
idea
of
multi-tenancy
in
the
sense
of
secret
management
and
ci
cd,
because
they
often
track
to
the
organizational
active
directory
structure
right
and
there's
a
strong
difference
between
that
and
the
way
that
kubernetes
thinks
about
multi-tenancy.
You
know
v-cluster
whatever
you're
using
everything
seems
to
be
namespace
constrained,
but
that's
not
backed
by
any
kind
of
regular.
You
know
there's
nothing
that
really
checks
that
it's
all
kind
of
an
automation
process
to
create
a
namespace.
It's
not
actively,
then
mapped
and
deleted.
E
So
an
example
would
be
that
if
you
delete
a
cluster,
sorry
delete
a
group
in
active
directory.
I
don't
think
anybody
is
really
using
that
to
map
to
cake.
So
I
think
we're
still
at
quite
an
interesting
point
in
the
in
the
history
of
how
this
stuff
all
pulls
together,
so
that
I
I
feel
like
it
might
be
worth
almost
adding
a
stanza
or
a
paragraph
on
the
white
paper
for
the
sig
to
contribute
some
thoughts
around
that
potentially.
C
So
what
I
found
out
is
that
the
thing
the
thing
which
is
which
we
have
in
front
of
us
is
not
a
white
paper
per
se.
This
is
only
for
the
giving
this
documentation.
C
As
far
as
I've
seen
so
the
in
the
top,
they
wrote
that
this
is
a
working
document
to
define
an
outline
for
a
multi-tenancy
focused
section
in
the
cubone
in
this
document.
So
this
is
not
a
white
paper.
In
my
opinion,.
A
C
That
it's
something
you
can
publish
in
one
in
one
in
one
thing-
and
this
is
part
of
a
larger
thing-.
C
A
I
guess
that's
fair,
but
but
thomas
if
that
means
that
this
white
paper
contains
all
the
content
we
need.
It's
just
not
in
the
right
format.
Is
that
yeah.
D
I
think
this
is
the
issue
from
github
that
you
that
you
mentioned
just.
I
think
this
is
the
one,
so
I,
from
from
what
I
understand,
they're
trying
to
with
this
document,
they're
trying
to
close
this
issue.
D
So
yes,
it's
it's
not
like
a
white
paper.
It's
it
seems
to
be
like
an
addition
to
the
kubernetes
dogs
which,
like
I
I
don't
know
exactly.
What's
the
difference
between
the
white
paper
and
the
dogs,
but
but
yes,
it's,
it
seems
to
be
more
relevant
to
the
dog,
I'm
going
through
it
as
we
speak.
I
haven't
seen
that
before
so.
C
I
also
think
this
is
something
we
could
do
as
asynchronously
to
find
out
what
what
their
goal
was
and
what
our
goal
is,
since
a
cncf
tag
or
work
group
should
be
because
they
are.
They
are
mainly
focusing
on
cuban
this
as
far
as
I've
seen,
but
they
are
not
as
much
focusing
on
the
landscape
and
so
on.
E
I
think
I
think
you're
right
like
reading
through
that.
One
of
the
things
that's
slightly
surprising
to
me
is
there's
less
than
a
paragraph
about
data
plane,
isolation,
which
is
one
of
the
most
important
concepts
in
multi-tenant
environments.
So
it
could
be
that
they
they
need
more
end
users
to
feedback.
It
could
be
the
case
that
they
just
don't
want
to
have
a
strong
stance
in
it.
E
It
could
be
that
it's
a
work
in
progress
or
it
could
be
the
fact
that
that
network
isolation
subheader
is
part
of
that,
but
the
sentiment
I'm
getting
from
this
is
that
you're
right,
it's
more
of
a
documentation
piece
around
kate's,
whereas
I
always
feel
like
a
white
paper
is
quite
opinionated.
So
I
think
about
the
operator
white
paper
you
go
in.
You
talk
about
what
are
the
keys
concepts
you
look
at
what's
going
on
in
the
industry,
and
you
put
together
some
some
some
narrative
around.
These
are
the
kind
of
things
that
we're
seeing.
E
Right
like
actually
interviewing
folks
who
are
working
at
companies
that
are
so,
for
example,
jenkins.
A
common
solution
is
to
use
jock
and
then
to
have
federated
jenkins
instances,
but
then
that
doesn't
scale
you
know
if
you've
got
a
thousand
teams.
You
know
a
thousand
jenkins
there's
a
whole
bunch
of
interesting
complexity.
Issues
around
multi-tenants.
A
Yeah
yeah,
even
what
you
were
saying
like
the
name
yeah,
we
kind
of
rely
on
a
namespace
to
do
tenancy
and
kubernetes,
but
then,
when
you
provision
the
resource,
is
there
any
like
tag
that
you
can't
like?
If
I'm
in
an
aws
database,
does
it
have
awareness
that
it
came
from
my
tenants
in
kubernetes
like
that,
might
be
relevant
for
sharing?
So
you
know
breaking
down
a
barrier
like.
I
need
this
resource
to
be
usable
by
another
team,
also
like
s3
bucket
or
something
yeah.
E
And
I
mean
this
also
lends
itself
to
how
cloud
providers
do
multi-tenancy
right
because
they
have
to
deal
with
these
problems
from
a
from
a
regulatory
perspective,
as
you
know,
as
in
the
natural
discs
that
they
lie
on
need
to
have
that
that
isolation
between
between
the
data.
So
I
think
it's
a
really
interesting,
quite
deep
subject
from
what
I
see
there
there's
a
good
effort
from
those
folks,
but
we
could
definitely
add
some
some
interesting
narrative
and
opinions.
I
think.
A
Yeah
I'd
like
that,
you
brought
up
cloud
providers
like
let's
say
rds
or
something
like
how
does
amazon
well
that's
easy
because
they're
in
machines,
but
let's
say
the
serverless
one,
how
do
they
handle
in
like
lambda
multi-tenancy
and
then
actually
that
will
tie
back
to
our
enterprises
like
like?
If
you
run
your
own
database
operator,
that's
where
it's
gonna
come
up.
If
you
run
an
operator
in
the
class
in
the
not
the
open,
okay,
you
guys
know
what
operators
are
like.
How
does
that
achieve
multi?
E
E
E
So
I
think
we've
got
options.
I
think
I
think
that
should
happen
regardless.
I
think
there's
another
group
or
there's
some
work
being
done
on
the
operator
white
paper
we're
going
to
revisit.
I
think
that
should
be
part
of
it
independently,
but
there's
definitely
a
follow-up
around
the
other
part
of
the
wider
context
among
tenancy.
C
E
You
think
for
for
which
bit
for
writing
a
v2
of
the
operator
white
paper,
no.
E
I
do
I
do
think
that
saying
you're
writing.
A
white
paper
tends
to
attract
quite
a
lot
of
interest.
It's
coming
from
cncf
because
everyone
wants
to
be
involved
and
to
have
their
voice
listened
to.
I
think
before
we
get
to
that
point,
we
need
to
clarify
exactly
what
we
want
to
talk
about,
so
that
it's
very
much
a
clear
process,
and
we
don't
have
any
of
this
hesitation
of
oh
what
the
kubernetes
are
already
doing.
C
A
I
have
a
hypothesis
that
a
lot
of
these
white
papers
get
written
mostly
by
one
person
and
then
a
lot
of
people
edit
them.
I
don't
know
if
you
agree
with
that.
I'm
not
sure
100
I've
seen
that
in
some.
So
do
we
need
to
find
somebody
to
write
that
initial
draft.
I
guess
in
this
case
the
blog
post
and
then
and
then
you
could
be
a
pr.
We
don't
have
to
publish
it
straight
from
that,
but
something
to
get
us
started.
E
I
think
that
if
you
break
the
the
surface
area
down,
it
becomes
a
little
bit
less
overwhelming.
So
you
could.
We
can
give
some
section
headings.
We
use
a
group,
could
define
loosely
some
high
level
section
headings.
Maybe
then
go
one
level
deep
and
then
invite
people
to
start
thinking
about
contributing,
and
that,
I
think,
is
a
good
strategy.
Of
course
you
need
to
be
using,
like
you
know
what
sort
of
voice
you're
at
you're
using
and
the
writing
style
needs
to
be
fairly
consistent,
but
overall,
I
think
just
getting
something
down
on.
C
Was
a
thing
which
worked
pretty
well
on
the
operator
white
paper
after
some
time
after
we
had
some
kind
of
structure
and
we
had
work
packages
which
we
could
assign
someone,
then
it
worked.
Let's
say,
let's
say
battle.
E
E
E
A
Yeah,
I
agree
with
that.
I'm
a
little
hesitant
I
mean
to
assign
it
to
any
of
us
to
be
honest
because
we're
already
doing
most
of
the
work
anyway.
That's
why
I
don't
want
to
just
be
you
know,
josh
and
thomas
and
alex
putting
four
white
papers
together.
I
mean
that's
good,
but
maybe
I
mean
I
would
love
chris.
D
Well,
this
is
this
is
very
interesting
to
me
as
well,
but
I
I
I
cannot
guarantee
like.
What's
my
availability
in
the
coming
a
couple
of
weeks,
that's
why
I'm
a
little
bit
hesitant!
I
wanted
to
understand
a
little
bit
more
about
what
what's
the
work
involved
before
I
I
commit
to
anything
because
yeah
I
wouldn't
like
to
let
everybody
down,
so
I
will
think
I
will
think
about
it.
D
I
will
go
over
the
documents
and
the
notes
that
you've
kept
josh
and
and
yeah
I'll
I'll
get
back
to
you
at
least
before
before
the
next
before
the
next
meeting
right.
A
Yeah,
that's
fair.
What
I
can
do
in
the
meantime
is
try
to
put
some
of
the
stuff
in
the
issue,
the
stuff
that
is
in
our
notes
here
and
let
everyone
know
what
we're
thinking
about
and
maybe
other
people
will
step
up
there
too.
E
Okay,
so
the
plan
is
that
in
the
next
couple
weeks,
we
will
reconvene
to
have
more
of
a
session
around
the
specific
paper
like
actually
hash
it
out
and
try
and
think
about
what
is
the
story
we're
trying
to
tell
here?
What
is
it
that
we're
trying
to
achieve
and
then
from
that
hopefully
we'll
be
able
to
identify
some
topic
areas
in
the
paper?
We
might
move
them
around
later
on,
once
we've
done
that
it
makes
it
easier
for
people
to
start
thinking
about
contributing.
Does
that
make
sense.
A
C
Be
cool,
so
we
do
the
same
thing
as
for
the
operator,
we
do
white
paper
source
dedicated
dedicated
session
for
that,
or
should
we
do
this
in
the
next
cooperative
library
working
group
meeting.
A
I
guess
it
could
be
in
the
cooperative
meeting.
I
don't
want
us
to
only
be
about
multi-tenancy,
but
but
yeah
we
don't
have
much
else
so.
C
Well,
should
we
do
the
should
we
say
the
next
meeting
is
about
this,
and
because
there
are
not
much
topics
on
the
table
to
be
honest
and
get
and
drive
and
drive
these
efforts
forward
in
the
first
step.
E
Yeah,
I
think
it
makes
sense
because
you,
you
know
you
can
help
to
co-chair
the
group.
Can
you
know
as
you've
been
doing
and
we
can
make
sure
there's
a
regular
cadence
on
it
and
effectively.
The
cooperative
group,
in
the
short
term
at
least
has
something
to
to
sink
its
teeth
into
that's
meaningful
work.
You
know
the
way
these
projects
always
work
is
there
are
people
who
just
jump
on
the
bandwagon
right?
It's
99
done
and
that's
what
will
be
the
case
here
as
well.
I'm
sure.
C
C
C
A
I
mean
the
other
main
topic
that
we're
thinking,
at
least
in
my
opinion,
is
the
coordination
so
that
when
I
deliver
an
app,
I
am
getting
all
of
the
infrastructure
I
need.
So
I
want
to
make
like
service
planning,
operator
and
crossplay,
and
things
like
that.
I
don't
want
to
lose
sight
of
those
things,
but
yeah
we,
those
are
more.
We
need
we're
looking
for
input
on
that,
I
guess
from
from
users,
and
we
don't
really
have
it.
So
I
think.
C
From
from
a
working
group
perspective,
it
would
be
cool
for
the
for
the
for
the
working
group
meetings,
where
we
don't
work
on
on
such
white
papers
or
whatever,
and
that
we
get
some
projects
who
want
to
present
just
like
cross
plane
just
so.
How
do
you
do
they
deal
with
cooperative
delivery?
C
A
Yes,
so
that
actually
I'm
glad
you
brought
that
that's
actually,
this
I've
been
working
on,
you
know
what
our
strategy
is
for
the
working
group
and
that's
exactly
what
I'm
proposing
is.
I
want
to
bring
in
some
thought,
leaders
in
the
area
and
drum
up
conversation
and
us
I
want
us
to
like
that's
why
I
put
down
on
my
thing:
hey.
I
can
present
to
you
all.
You
know
v,
cluster
and
kcp
today
and
and
kind
of
make
this
a
meeting
or
a
group.
That's
at
the
bleeding
edge.
I
guess
of
this
stuff.
E
Josh
are
you
at
cubecon
next
week,
unfortunately,
no
okay,
we,
I
think
you
just
made
me
think
of
a
subject
that
we
need
to
really
explore
and
I
think
the
machinery
in
place
to
make
tags
successful,
isn't
quite
there
like.
We
don't
have
a
way
to
ingress
ideas
right
into
our
own
roadmap
that
aren't
very
kind
of
infrequent
and
sometimes
just
by
chance
like
the
multi-tenancy
stuff,
and
it
would
be
really
good
to
give
you
the
machinery
to
say.
E
I
know
what
this
this
working
group
is
is
going
to
be
doing
for
the
next
six
months
right.
I
know
what
things
are
going
in
and
out
what
projects
are
going
to
be
spinning
up
and
down.
So
I
think
from
a
wider
tag
perspective
some
of
the
coaches
and
ourselves
could
could
definitely
try
and
think
about
reinvigorating
that
I'm
just
looking
at
our
boards,
our
roadmap,
that
should
be
full
of
things
that
people
want
from
a
community
perspective
from
us
to
cover.
You
know
as
a
tag
and
as
a
subsequent
working
group.
E
A
Actually,
what
he
said
was
one
of
the
things
that
I've
noticed
like
chris,
when
you
gave
the
presentation
to
tag
app
delivery
on
miss
naio.
The
incoming
projects
are
inspirations
honestly,
like
I
mean
crossplay,
those
those
we
don't
necess
like
I
don't
know,
I
think
that's
our.
It
fits
with
the
role
at
cncf
every
project
that
comes
in.
I
take
a
look
at
and
and
there's
new
ideas
that
come
out
of
each
one.
A
It's
not
the
only
source,
but
that
I
know
we've
been
having
a
thread
in
cncf
about
how
to
bring
in
sandbox
projects
and
just
so
yeah.
That's
just
that's.
Just
one
strategy
we
could
take
is
hey
every
project
that
comes
in
that
can
influence,
and
you
know
lead
thought
in
the
app
delivery
space.
Let's
make
sure
that
we
talk
about
it
in
tag,
app
delivery
or
cooperative
delivery
and.
C
So
that
that's
the
thing
we
should
drive
a
bit
forward
in
the
future,
so
I
think
every
project
tester
has
the
has
the
posit
the
same
as
mister
has
the
possibility
to
present
themselves
in
the
gap
delivery
for
the
cooperative
delivery
working
group.
This
would
be
with
a
specific
use
case
so
with
the
tradition.
C
So
what
we
thought
about
when
we
wrote
the
charter
for
for
the
cooperative
delivery
worker
group
was
that
we
we
find
a
lot
of
solutions
for
for
exactly
the
problem.
We
stated
there
and.
D
Just
from
the
perspective
of
a
person
who
did
it
recently,
it's
also
like
a
discoverability
issue
like
I
I
I
didn't
know
what
to
do
and
who
should
I,
who
should
I
reach
and
how
I
should
communicate.
What
I'm
trying
to
do,
and
you
know
what
are
the
options
or
if
it's
an
option
or
not,
so
I
I'm
a
little
bit
more
persistent
than
the
average
type.
D
So
I
found
my
way
through,
but
I'm
guessing
that
somebody
who's
like
a
little
bit
more
sigh
or
you
know
it
would
be,
it
would
be
harder
for
them
to
figure
it
out
and
get
in
front
of
you.
So
I
I
don't
know
if
this
is
like
a
documentation
issue
or
not,
but
like
I
had
to
do
three
four
hops
from
person
to
person.
D
Until
I
find
something
and
then
you
know
which
person
stops
responding
at
some
point,
so
you
need
to
get
back
to
them
and
then
again
and
again
until
you
find
your
way.
So
it's
it's
a
little
chaotic
and
can
discourage
people,
but
I
I
can
at
least
for
new
ones
right,
okay,
because
the
existing
sincere
projects,
it's
much
easier.
You
just
reach
out
to
the
people
and
that's
it
like
you:
they
they
either
get
in
or
not
so
it's
it's
much
easier
there,
but
for
new
projects.
D
A
Well,
so
what
I'm
hearing
from
you
chris
is
not
so
much
about
you
know
just
general
contribution
attack.
It's
your
project
missed
io,
as
the
you
know
would
have
been
nice
if
they
had
said
you
know,
when
you
first
asked
the
samex
hey,
why
don't
you
go
to
tag
app
delivery?
Ask
them
for
help
present
in
that,
and
then
me
or
thomas
might
have
said.
Okay,
chris
how's
it
going
like
yeah.
D
Exactly
exactly
like
some
sort
of
not
very,
very
well-defined,
but
at
least
a
high
level
of
a
high
level
description
of
a
process.
Let's
say:
like
hey,
you
know
we
are
interested
in
abcd.
If
your
project
is
is
doing
something
interesting
there,
then
you
know
reach
out
to
josh
thomas
whoever
or
find
us
on
slack
and
book
a
slot,
so
you
can
present
what
you're
doing
on
our
next
meeting
or
something
you
know
something
like
a
simple.
I
didn't
find
anything
like
if
there
might
be
something
like
that.
D
I
don't
know,
but
I
didn't
find
anything
that
was
myself.
I
had
to
go
through
people
and
pinging
them
on
slack,
sending
them
emails
and
until
I
figured
it
out
so
yeah,
maybe
something
like
this,
which
will
serve
as
a.
D
The
top
of
the
funnel
for
new
for
new
things-
maybe
this
should
be
described
at
least
on
on
on
the
tags
page.
A
D
C
We
we
are
trying
to
to
make
some
noise
in
the
last
in
the
last
time.
So
I
hope
you
saw
this
on
twitter.
D
Yeah
yeah,
I
saw
it
like
thanks.
D
D
That
that
you
shared
and
yeah
I'll
I'll
reach
out
again
is
slack
the
the
best
way
to
do
this.
D
A
D
Think
about
it
in
any
case,
I
want
to
go
over
it
just
to
have
a
better
understanding,
because
you
know,
especially
if
you
kind
of
open
it
up
to
more
than
one
platforms.
I
mean
not
just
kubernetes
but
other
clouds
as
well,
then
it
can
get
really
really
big,
but
they're
really
interesting.
In
the
same.
At
the
same
time,.
A
D
Yeah
you
can,
you
can
do
any,
that's
the
that's
the
idea
yeah.
So
what
its
underlying
platform
does
is
really
really
important.
We
have
experience
pretty
much
with
everything,
so
I
think
there
we
could
contribute
a
lot
of
our
experience,
cool
all
right.
A
A
Yeah,
I
have
a
couple
other
items
on
here,
but
we
don't
necessarily
have
to
do
them.
In
fact,
let's
not
do
them,
because
I
we
said
that
this
clusters,
the
unit
dependency
I'll,
write
a
block,
but
if
you're,
still,
okay,
with
that
thomas
I'll
write,
a
blog
post
on
that
mainly
to
you
know,
build
credibility
for
us.
Yes,.
C
A
A
Yeah
exactly
it
will
be
a
cool
paper.
I'm
excited
about
this.
The
other
thing
I
was
going
to
mention
is
potato
head.
I've
got
a
pending
pr
there
that
adds
open
id
connect.
A
I've
only
tested
it
with
google's
sign
in
so
far,
but
people
can
test
that
it
only
uses
that
if
you
want
like
by
default,
if
nothing
is
said,
it
will
keep
working
the
old
way.
I
also
added
in
sessions
as
part
of
that
well
kind
of
part
of
that,
but
it
was
relevant
and
but
it's
only
cookie
based
the
reason
why
I'm
doing
all
this
is
my
next
step
is
to
actually
use
an
external
database,
so
I
figured
an
easy
one:
is
the
session
store
so
I'll
use?
A
I
don't
know
redis
or
sql
or
my
sql,
or
something
as
the
session
store,
and
that
will
finally
give
me
a
piece
of
infrastructure
to
coordinate
with
my
app
that's
the
goal
there
very
cool
yeah,
oh,
and
I
also
the
argo
cd
walkthrough.
I
finished,
but
I
haven't
pr
it
yet,
but
it's
not
that
hard.
Actually,
it's
really
much
easier
than
flux.
Interestingly,.
C
It
might
be
that
I
create
the
pull
request
for
the
argo
ct
stuff
in
the
next
few
weeks.
I
have.
C
Yes,
but
I
I
would
like
to
to
contribute
the
code
for
that.
A
A
Yeah,
so
I
think
that's
we
have
any
other
stuff
here.
We
talked
about
building
nothing
more.
C
From
my
side,
so
I
took
it
as
an
item
that
I
will
create
the
multi-tenancy
white
paper.
The
organization
in
the
community
portal.
C
525
because,
because
initially
when
I
created
the
when
I
created
the
the
series,
I
only
created
the
series
for
half
a
year,
and
this
is
over
now.
So
what
I
would
do
now
is
that
I
would
create
a
dedicated
market
and
the
white
paper
organization
for
the
next.
In
two
weeks,.
B
C
And
I
would
also
create
the
I
would
I
would
create
the
vedic,
the
real
cooperative
delivery
working
group
meeting
only
once
a
month,
so
every
four
weeks,
so
that
we
can
always
decide
what
we
want
to
do
in
every
in
in
every
second
meeting.
C
C
C
B
A
A
B
No,
I
I
arrived
late,
sorry
and
then
there's
people
like
shouting
at
me
in
slack
and
then
I'm
like
half
here
up
there.
So
sorry
about
that,
so
you
are
like
going
to
write
a
blog
post.
See
about
like
in
is
that
I'm
inviting
people
to
to
join
to
to
join
the
white
paper
like
crafting
and
then
and
but
as
we
will
first,
are
we
first
going
to
decide
what
we
aim
for
as
as
the
structure
and
then
invite
people
to
like
contribute?
Once
we
have
some
opinion
on
a
structure.
B
C
Step
should
be
that
that
george
writes
down
his
ideas
and
so
on,
and
we
can
publish
a
white.
We
can
easily
publish
a
blog
post
regarding
this.
D
C
Step
we
could.
We
agreed
on
like
having
a
working
station
regarding
the
white
paper
finding
out
the
structure
of
the
white
paper.
A
Yeah,
the
first
one,
what
I
write
is
going
to
be
just
like
a
technical
thought,
leadership
that
says
and
we're
thinking
about
this
so
come
help
us
and
then
the
next
one
after
we
have
the
meeting
and
have
you
know
a
rough
outline
will
be
all
right.
Now
we
have
a
rough
outline.
Come
join
us
something
like
that
sounds
good.
B
Yeah
yeah,
I
think
yeah,
like
I
think
I
heard
alex
saying
about
the
the
amount
of
people
is
good
and
I
I
heard
you're
saying
that
it's
like
it's
a
lot
of
work
as
well.
You've
been
doing
a
lot
but
yeah
like
I
guess.
If
we
just
have
this
when
thomas
and
I
were
in
the
operator
v1,
it
was
a
bit
of
like
lots
of
people
joined
and
then
they
were
like.
I
can
help
or
something.
But
then
may
it's
easier
when
we
like.
This
is
what
you
can
do
concretely.
B
You
can
fill
up
this
section.
You
can
add
these
things
and
then
it's
like
a
little
easier
for
people
just
to
feel
in
their
mind
some
actionable
item
rather
than
oh.
If
you
have
an
idea
like
no
one
kind
of
maybe
commits
something,
so
maybe
it's
better
to
be
a
bit
more.
Unless
people
have
a
strong
opinion,
then
fine
challenge
us
but
maybe
come
come
with
the
suggestion.
First
is
easier:
yeah.
B
A
No,
no,
the
blog
post
I
write
is
just
going
to
be
about
cluster
clusters
as
a
unit
of
tenancy
and
several
projects
that
are
pursuing
that
and
then,
as
like
about
you
know,
we'll
say
at
the
bottom
or
the
top,
or
something
like
we're.
Just
we're
pursuing
these
topics
and
tag
up
delivery
come
join
them.
This
meeting,
thank
god.
B
A
Because
that
it's
just
gonna
be
my
you
know,
but
you
guys
will
vet
it,
but
just
be
you
know
an
opinion
piece
really.
A
Yeah,
it's
not
the
operator,
so
yeah,
okay,
so
I
think
we
can
call
it
or
are
we
good
here
anything
else
we
want
to
discuss.
Give
you
all
some
time
back.
A
Okay,
thank
you,
thomas
for
for
helping
out
with
getting
some
folks
here
and
for
the
good
the
good
plan
here
on
the
multi-tenant
stuff.
It's
really
helpful.