►
From YouTube: CNCF TOC Meeting 2021-06-22
Description
CNCF TOC Meeting 2021-06-22
A
I
think,
first
of
all
does
anyone
disagree
with
my
belief
that
yarp
is
library
code
rather
than
a
standalone
project?
Hey
justin
we've
got
justin
as
well.
Sorry,
I'm
late.
Sorry,
we
were
just
starting
to
talk
about
yarp
and
I
was
saying
that
I
believe
that
yarp
and
also
another
project
which
I
will
will
come
to
at
some
point.
But
another
project
on
this
list
is
library
code
rather
than
a
kind
of
standalone
thing
which
might
be
okay,
but
I'm
not.
I
couldn't
think
of
anything
that
is
library
code.
A
A
A
A
A
C
E
F
D
A
A
C
G
H
C
Because
it's
it's,
I
mean,
there's
the
comment
and
the
link
to
issues
which
is
just
kind
of
like
we
want
to
make
it
more.
We
want
to
bridge.net
and
cloud
native,
and
it's
like
that's
great,
but
it
still
feels
like
one
component
out
of
many
is
in
would
be
in
cncf,
and
the
everything
else
in
the
net
ecosystem
is
in
the
net
foundation,
and
it
just
feels
kind
of
weird.
F
E
Well,
the
other
way
to
think
about
is
like
how
many
who
will
be
using
this
and
how
many
of
them
will
be
using
it
or
like
how
is
it
going
to
spread
right
to
be
useful
in
the
cncf
ecosystem,
and
do
we
see
projects
depending
on
this?
E
That
will
essentially
go
into
any
of
our
usual
deployment
models,
and
things
like
that
right?
That
would
be
the
fit
that
we
look
for,
and
I
don't
see
it
yet.
A
So
perhaps,
as
chris
is
suggesting,
the
the
net
foundation
might
be
a
more
suitable.
A
Why
can't
I
see
see
the?
Why
can't
I
go
back,
it's
basically
how
it's
like
I'm
new
to
computers.
What.
A
Why
can't
I
see
the
maybe
that's
what
I
need.
That's
what
I
need,
except
there
we
go
and
yet
hold
another
tab
right.
B
J
J
A
J
Well-
and
it's
not
just
the
microsoft
comment
either,
I
think
it's
just
as
it's
not
a
good
fit
for
what
we
see
being
a
viable
project.
A
A
Is
that
enough?
Okay,
what
was
the
next
one
on
the
list
of
repeat
see
please
pixie.
A
So
pixie
have
definitely
when
pixie
came
up
last
time.
I
was
concerned
about
them
having
linking
their
github
to
their
self-hosted.
Sorry,
their
their
own
hosted
version
of
pixie
and
they've
sort
of
they've
made
some
improvements
there.
They
they've
it's
not
like
on
the
first
page
of
the
github,
but
there
is
still
and-
and
I
kind
of
understand
why
they
have
it
right.
A
A
Not
unsurprisingly,
it
is
still
linked
to
quite
heavily
from
the
kind
of
getting
started.
A
Documentation
do
we
have
any
other
examples
of
something
where
the
project
hosts
a
version
of
the
solution
like
this.
I
A
K
A
I
K
I
know
there's
an
aws
collaboration,
I'm
sure
new
relic
who
bought
pixie
is
doing
something
with
it.
I'm
trying
to
go.
K
Yeah,
probably
they
paid
for
it
yeah
and
I
think
aws
said
something
that
they
plan
on
at
least
contributing
to
the
project
yeah,
which.
A
K
A
D
K
Probably
what
I
would
do
and
I'm
guessing
new
relic
aws
others-
will
offer
probably
hosted
sas
based
offerings
for
for
this.
A
E
What
what
did
we
ask
them
last
time
and
they
came,
we
had
to
revisit.
C
F
F
A
L
A
I'll
I'll
show
you
the
thing
I
mean
you
know
it's
not.
I.
I
completely
understand
why
this
is
here,
but
you
know
you
go
through
quick
starts
and
you
know
it.
It
tells
you
you
can.
Oh,
I
can't
even
find
the
version.
Oh
here
we
go,
you
know,
there's
this
pixie
community
cloud
which
saves
you
from
deploying
it
and
which
is.
D
C
C
E
Yeah,
so
the
only
other
thing
I
can
think
of
is
a
rename
pixel
to
something
else,
and
we
we
get
to
host
only
the
sources,
we
don't
care
about
the
website
or
whatever
service
they
are
running.
K
The
the
trademark
they're
for
sure
going
to
transfer
over
that
I
have
clarity
yeah,
it's
the
question
of,
like
you
know
their
whether
this
demo
service
runs
on
the
cncf
cluster
or
new,
relic
or
aws
offer
their
own
like
hosted
things
which
is
fine
as
long
as
they
name
it.
You
know
appropriately
right.
B
B
C
K
Was
purchased
generally,
we
would
ask
for
that
domain
to
be
transferred
over
as
part
of
the
process,
but
if
they're
not
using
it
in
any
fashion,
then
we
don't
care
as
long
as
it's
not
confused
as
long
as
it's
not
confusing
to
end
the
end
users,
they
could
that
it
means
no
longer
being
used.
We
don't
care,
but
the
justin
points.
I
view
this
as
like
a
transition
thing
where
you
know
as
part
of
onboarding
we
kind
of
deal
with
this
whole
thing.
K
K
A
E
A
A
So
I
think
the
next
we
can
probably
talk
about
them
together,
there's
mescheri
and
smp,
which
was
service,
mesh
performance,
very
cool.
A
So
when
we
discussed
this
last
time
we
were
talking
about
how
you
know
we
have
the
service
mesh
interface
already
we
have
service
mesh
performance
and
then
meshery,
which
kind
of
implements
some
of
these
things,
and
we
went
to
sig
network
where
we
have
the
interesting
scenario
that
sig
network
is
essentially
being
run
by
lee
and
he's
also
involved
in
all
these
projects.
A
So
I
guess
the
good
thing
about
that
is,
he
knows
what's
going
on,
but
he
did
go
out
and
have
a
conversation
with
lots
of
maintainers
on
the
service,
mesh
interface
project
and
mesherie
and
smp.
I
think
there
are
a
couple
of
things
that
we've
learned
from
that
one
is
that
smi
is
potentially
an
at-risk
project.
I
would
say
it's
not
going
from
from
what
I
hear.
There
are
some
issues
there
in
terms
of
its
support
from
its
own
maintainers.
A
A
A
A
A
All
right
so
now
we
can
go
back
to
the
top
of
the
spreadsheet
and
the
new
applications,
so
porter
lb
and
noting
that
we
already
mentioned
metal
lb.
I
think
there's
there's
a
a
couple.
Maybe
three,
maybe
even
more
load
balancer
projects
all
throwing
their
hat
in
the
ring
at
the
moment.
A
A
A
J
L
Like
they
haven't,
submitted
the
difference
between
them
and
other
a
lot
of
bouncers
for
better
metal
like
metal.
A
Guess
I
guess
what
we're
saying
is
we
can't
you
know?
We
can't
really
consider
the
application
very
thoroughly
because
they
haven't
really
filled
in
the
form
and
it's
always
possible
that
there
will
be
more
competition
and
we
might
not
accept
them
in
the
future,
because
you
know
there's
no
there's
no
guarantee
and
there
might
be
too
many
load
balances.
L
So
we
have
this,
we
have
this
field
explanation
of
alignment
and
overlap
with
existing
cncf
projects
and
it's
optional.
Should
we
make
the
requirement,
I'm
not
sure
why
it's
optional
on
the
forum,
the
description
is
an
option.
Is
it
the
description
is
not,
but.
M
H
C
H
C
D
A
A
A
A
I've
I've,
I
have
let's
say,
come
across
not
used
myself,
but
I
have
been
sort
of
adjacent
to
some
usage
of
metal
lb,
which
I
think
has
some
some
good
points
and
some
I
have
heard
people
concerned
about
scale,
but
you
know
that
is
probably
indicative
of
the
fact
that
they've
been
using
it
at
some
scale.
So
it
is
real
yeah.
E
H
E
A
C
E
C
E
It's
a
consulting
company
justin,
who
is
cube
sphere.
C
Does
it
I
thought
I
thought
it
was,
I
think.
M
E
The
only
other
thing
that
I
can
add
is
I
I
haven't.
I
didn't
run
across
the
name
in
any
of
kubernetes
related
mailing
lists,
or
you
know,
repositories
or
anywhere
else.
So
it's
brand
new
to
me.
A
A
E
And
it's
I
I
think
I
saw
separate
installers
for
standard
openshift,
kubernetes
and
k3s,
and
things
like
that.
A
A
G
G
So,
given,
as
I
do
not
see
a
passing
vote
in
here,
suggest
they
change
the
name
and
reapply
okay,
okay,.
M
A
C
But
so
this
is
being
donated
independently
of
the
om's
bag.
Is
that
correct.
M
A
M
M
C
I
have
but
yeah
I
I
didn't
I
I
didn't
realize.
I
think
I
hadn't
come
really
come
across
cube
furler
as
part
of
it.
So
I
kind
of
the
other
way
around
for
me.
E
I
ended
up
running
into
this
when
I
was
looking
at
like
dagger.io
and
shipper.iu,
so
it's
in
the
same
category
right
hurry.
E
Votes,
how
do
you
be
like
the
people
on
this
team.
C
Mean
I'm
not
asking
it's
just.
It
seems
weird
to
accept
it
right
like
it's
it.
It
seems
to
if
we
accept
it
as
kybala,
it
seems
more
like
better
that
the
organs
give
valuation
we
accept
it.
As
am
then
it's
fine
to
be
called.
How
I
am
I
I
I
don't
have
any
preference,
but
it's
like
it
seems,
it
seems
just
seems
a
little
bit
inconsistent.
A
M
So
they
are
actually
coupled
right
now,
that's
why
they
are
coupled
together
installation,
basically
like
api
implementation.
So
there's
no
other
implementations.
I
don't
think
there's
motivation
to
promote
any
other
implementation
based
on
that
yeah.
So
the
the
original
the
current
plan
is
that
the
whole
relation
moved
to
since
actually
it's
including
every.
E
So
how
much
rework
do
you
have
to
do
to
I'm
sure
you
have
oem
dev
in
the
imports
or
something
right
so
that
that's
going
to
be
your
issue.
M
Yeah,
so
renaming
will
require
some
work.
That's
actually
the
reason
we
didn't
do
that
before,
because
it
will
break
some
dependencies,
but
if
we
feel
it's
necessary,
I'm
totally.
Okay.
From
my
perspective,
just
some
technical
issues
to
solve,
there's,
no
political
or
any
non-technical
blocker.
For
that.
A
M
Right
we
discussed
that
before
so
there
is
a
plan
to
name
that,
but
some
maintainers
raised
concerns
about
that,
because
we
have
production
environment
that
rely
on
that
path
which
will
make
it.
You
know
take
some
time,
but
I
think
we
can
raise
the
issue
formally
to
discuss
that.
I
mean
in
github
to
see
if
folks
are
okay
to
renaming
the
github
report.
E
M
Yeah
I
can
understand
the
organization
name
is
essentially,
for
example,
like
clone
native
application
system
or
thing
like
that,
which
will
make
sense
to
cover
what's
inside
currently
in
that
organization.
That
is
actually
ideal.
Also,
I
would
try
to
ask
the
team
to
raise
the
issue
discuss
what
should
be
the
right
name
for
the
organization
github
organization
during
the
sandbox
onboarding
process,.
A
A
A
H
Yeah,
I
didn't
have
a
full
look,
but
actually
we
we
are
looking
for
a
component
like
this,
but
that
does
both
the
backup
and
restore
it's
it's
it's
not
as
trivial
as
it
sounds
in
fact,.
F
Yeah
I'll
plus
one
to
that,
I
think
valero
is
another
solution
in
this
space
and
they
also
use
restic.
A
H
Yeah
and
in
both
cases,
we
have
issues
with
with
actual
implementation
of
the
persistent
volumes
and
how
much
support
they
have
for
restoring
from
snapshots
and
things
like
this.
H
So
a
general
solution
like
this,
it's
it's
not
too
bad,.
A
Valero
rings
a
bell
to
me:
dude
is
it
in
the
sandbox
already?
I
can't
remember.
J
J
A
There
is
a
chris's
comment
about
having
to
change
the
license.
They
do
actually
say
in
their
kind
of
column,
p.
We're
currently
using
the
bsd3
clause
license,
but
we're
open
to
changing
the
license
to
apache
too.
So
I
think
that
would
be
that
that
sounds.
A
E
A
H
Yeah,
I
I
talked
to
them
for
the
cross
plane
review
as
well,
and-
and
they
mentioned
they
are-
they
were
submitting
this
this
project
they
working
on
giving
more
information
as
needed
as
well.
A
C
E
H
C
C
E
Yeah
and
yeah
from
vmware,
you
know
he
was
working
with
he's
the
second
one,
so
he's
the
one
working
with
them
to
get
it
working
with
cappy.
L
C
A
Enthusiastic
all
right,
the
next
one
on
the
list
is
cube.
Dl,
which
looks
as
though
it's
a
kind
of
cube
flow
alternative,
which
is
kind
of
intriguing
another
alibaba
project,
very
prolific.
G
A
Anyone
I
mean
165
contributors
and
sorry
165
stars
and
seven
contributors
is
quite
feels
a
little
bit
early.
H
H
M
So
this
project
is
also
my
team
is
partially
for
facebook.
So
the
the
overlap
with
puberty
over
kubiflo
is
the
tensorflow
job
crd.
So
the
cool
video
had
its
own
crd
for
tensorflow.java,
which
is
a
similar
but
had
differences
with
kubiflow,
but
for
other
parts
they
do
not
have
overload.
That
means
the
kubiflow
components
can
be
used
with
qbdl,
for
example,
it's
workflow
and
meantime
kubidio
provided
several
other
features
which
do
not
exist
in
could
be
flow.
So
this
this
is
the
relationship
between
these
two
projects.
M
A
A
All
right,
we
are
almost
up
at
time.
Let's
see
whether
the
next
one
looks
like
a
really
not
oh,
the.
A
Is
crustlet.
E
Yeah,
so
the
thing
here
is:
go
one
go
to
the
ninth
one:
seven
and
nine
go
together,
less
oh
right,
chrysler
and
oh
yeah
and
crater
yeah
yeah.
So
the
question
that
we
need
to
ask
them
is:
can
they
work
as
a
single
project?
I
think,
and
not
as
two
separate
projects.
L
L
We
can
also
ask
a
question
what
what
other
projects
use
crater
besides
crosslit?
Is
there
an
adoption
right.
C
D
A
A
Yeah,
so
maybe
going
back
to
them
and
asking
why
why
creator
isn't
part
of
christmas
as
a
project?
Okay,
we're
still
at
seven
for
qdl.
So
if
anyone
else
wants
to
add
a
vote.
E
Me
they
did
answer
that
question
saying
that
in
the
kubernetes
ecosystem
there
isn't
a
good
library
for
talking
to
kubernetes
and
that's
where
this
project
crater
is
useful.
All
right.
K
I
A
All
right,
I
think
we
are
up
to
time.
I
think,
because
we
have
several
left.
It
means
that
next
time
we
do
a
private
meeting,
we
will
go
through
what's
left.