►
From YouTube: CNCF TOC Meeting 2022-03-15
Description
CNCF TOC Meeting 2022-03-15
A
A
All
right
with
cornelia
coming
in
that
gives
me
quorum
so
hooray,
oh
god,
and
kick
a
socks.
We've
got
a
lot
to
do
today.
Welcome
to
your
toc
meeting
for
march,
15th
2022,
a
normal
anti-trust
policy
applies
here.
You
have
made
it
to
the
meeting
well
done
or
you're
watching
another
recording
doc
member's
attractive,
toc
attendance
tracker
in
the
public
doc,
and
here
we
go.
We
have
our
annual
reviews.
A
This
is
the
first
time
we've
done
this
in
an
open
meeting,
so
bear
with
us.
There
might
be
some
questions
around
how
we
all
do
things.
There's
some
pieces
in
the
annual
review
process
about
how
three
particular
toc
members
need
to
be
able
to
vote
for
it.
I
think
we
deal
with
that
at
the
end.
Unless
dims,
I
see
you
nodding
and
being
able
to
have
like
other
other
opinions,
but.
A
That's
basically
like
that
there
are
some
procedural
things
that
I
know
that
we
need
to
work
out,
so
I
will
get
us
started
in
here.
What
we've
done
as
far
as
like
toc
kind
of
like
reviewing
all
of
these
annual
reviews
is
each
individual
project
that
came
in
for
this
morning,
because
we
were
doing
this
last
week
and
a
little
bit
yesterday
has
a
toc
kind
of
sponsor
attached
to
them
that
they've
gone
through
and
actually
reviewed.
So
as
we
move
towards
each
of
them,
I
will
pass
towards
that
particular
member.
C
Hello,
everyone,
so
thank
you
so
much
for
submitting
your
annual
review
we've
gone
through
and
taken
a
peek
at
it
and
also
checked
some
status.
Information
about
the
project
looks
like
you
all
have
been
making
some
excellent
work
on
getting
adopters
of
the
project
wanted
to
understand
a
little
bit
more
of
your
perspective
on
some
of
that
adoption.
Do
you
see
any
challenges
or
any
opportunities
over
the
next
year.
A
D
C
I
guess
we
can
ask
it
afterwards
so
looks
like
widespread
adoption.
They
had
some
key
call
outs
for
things
that
they
wanted
to
get
done
before
incubation.
So,
in
addition
to
those
based
off
of
a
review
of
the
repository,
there
looks
like
there
could
be
some
more
work
that
could
be
done
to
better
prepare
the
project
for
all
of
the
requirements
that
come
with
incubation
and
all
of
the
additional
exposure
and
opportunity
with
that.
C
So
I'd
be
happy
to
follow
up
with
kuma
offline
after
this
to
discuss
what
some
of
those
key
items
are.
That,
I
think,
would
be
beneficial
for
the
project
to
be
able
to
move
forward
and
it
looks
like
they
had
some
outstanding
requests
of
cncf
to
be
able
to
assist
the
project
and
their
readiness
for
incubation
is
there
anything
else
that
I
missed
amy
or
dimms.
B
A
There
is
so
we
do
have
the
ability
to
be
able
to
go
through
a
telemetry
policy
and
kind
of
walk
this
through
legal
and
all
of
that.
So
if
projects
want
that,
the
best
example
that
I
have
for
you
right
now
is,
I
think,
it's
spinnaker
project.
Don't
quote
me
on
that
directly
because
I
haven't
looked
at
this
in
a
bit,
but
we
do
have
a
policy
and
projects
can
go
through
this.
B
B
C
A
This
is
intended
to
be
a
lightweight
just
review,
intended
to
be
like
hey
project.
How
can
we
help
with
one
note
if
a
project
asked
for
marketing
help
directly?
I
didn't
put
it
in
the
slides
because
that's
not
something
we
can
offer
for
sandbox
projects.
I
fully
understand
where
the
request
is
coming
from
and
there's
it's
just
not
available.
So.
F
F
This
is
also
a
good
site,
and
when
we
look
at
the
implementations
of
details,
open
crews,
I
will
say
it
is
on
the
right
track
by
position
by
positioning
itself
as
a
tool
set
to
help
middle-size
or
large-sized
companies
to
deploy
cooper,
to
use
kubernetes
at
large
scale
by
providing
features
like
in-place
upgrades
and
to
manage
static
cars
at
massive
scale.
These
these
are
features
which
cannot
be
found
in
option
kubernetes,
but
still
needed
by
many
many
companies
in
their
own
user
scenarios.
F
That's
why
I
feel
it's
complementary
to
the
existing
community
instead
of
saying
a
fork,
or
I
know
people
are
asking:
why
don't
you
contribute
back
to
option
because
the
upstream
had
its
own
goal
had
its
own
feature
state
and
those
cases
which
have
been
handled
by
open
crews,
mainly
target
on
massive
scale,
enterprise
scale?
You
know
we
should
have
some
tools
that
would
help
that.
F
I
I
feel
that
open
code
is
also
on
that
track
on
the
right
track
in
the
in
terms
of
that
part,
and
the
last
is
the
the
open
course
containers
of
also
asking
for
a
move
to
next
move
into
next
stage,
which
I
personally
feel
they
they.
They
are
they're
almost
ready
for
that.
I
would
like
to
see
and
improve
the
contribute
contributor
diverse
and
to
the
further
stage
note
that
today
they
already
have
a
diverse
maintainership
in
a
project.
I
think
they
are
also
on
the
right
direction
in
this
part
yeah.
A
F
E
A
B
B
In
general.
They
have
been
trying
to
do
the
right
thing
across.
You
know
what
what
they
do.
I
did
have
a
few
questions
in
the
pr
itself
and
jim
from
the
project.
You
know
give
me
the
details
like
I
was
asking:
where
are
the
design
docs?
You
know
what
is
a
plan,
for
you
know
the
salsa
levels
that
they
were
talking
about
for
the
security
chain,
then
the
other
one
that
I
had
a
question
about
was.
B
B
B
For
example,
oppa
folks
right,
like
oppa,
is
already
established
and
it's
used
in
cks
and
things
like
that
they
were
trying
to
figure
out
like
how
do
we
go
to
the
point
where
we
are
listed,
alongside
of
oppa
in
the
various
things
that
cncf
does
or
the
documentation
or
that
we
have
in
different
repositories?
And
things
like
that.
B
I
think
that's
a
fair
question
and
you
know
I
was
going
to
probably
point
out
like
hey:
let's
get
you
through
inco
incubation
and
then
as
part
of
incubation,
we
will
work
on
these
things,
we'll
identify
a
set
of
things
to
do
and
go
around.
You
know
getting
help
from
other
people
to
go.
Do
that
so
I
do
not
have
any
concerns
at
this
moment
and
I'm
looking
forward
to
reviewing
the
you
know,
incubation,
dd
and
other
materials
for
kubernetes.
B
G
Yes,
it's
shooting
down
here,
I'm
from
kirono
community.
It's
actually
my
first
time
joining
this
meeting,
because
I
saw
the
message
that
you
said
it's
an
open
meeting
so
welcome
everybody
to
join.
So
that's
why
I'm
here-
and
I
believe
jim
already
like
answered
most
of
your
questions
in
that
any
review
and
we're
also
working
on
the
dd
doc
for
the
incubation
application
and
you
know
happy
to
discuss
any
other
like
food
questions
offline.
But
regarding
that
zoom
link,
we
had
like
problem
posting
it
or
I'll
like
live
stream
it
on
the
youtube.
A
A
H
H
I
would
also
highlight
there.
There
was
an
effort
from
the
project
to
move
away
from
the
jet
stack
organization,
github
and
similar
things.
There
was
one
item
left,
I
think,
which
is
a
reference
to
the
chess
stack
on
the
project
website.
Maybe
we
can
we
can
check
that
one
as
well
with
the
for
the
other
items
here
in
this
slide.
The
incubation
process
has
actually
already
started.
So
I
think
the
due
diligence
and
the
suggested
security
audit
will
help
the
project
a
lot.
H
H
I
I
H
B
Yeah,
I
guess
the
challenge
is
a
cert
manager
works.
You
know
very
well,
so
people
don't
need
to
feel
the
need
that
they
have
to
do
more.
I
guess,
but
they
don't
see
all
the
things
you
know
that
could
be
done.
I
guess
they'll
just
see
what
what
doesn't
work
for
them
and
have
like
a
small
patch
for
just
that
right.
I
H
A
No
that's
perfect.
This
is
exactly
what
we
would
want
to
see
for
projects
that
are
looking
to
be
able
to
move
to
incubation
like
please
do
your
annual
review.
It
shouldn't
be
that
hard,
and
it
should
actually
give
you
a
good
guideline
about
whether
or
not
you're
ready
to
be
able
to
go
for
incubation.
So
thank
you
project.
E
E
E
I
think
some
of
it
is
because
people
haven't
heard
of
the
project,
maybe,
but
it's
also,
I
think,
partly
because
people
probably
already
have
homegrown
solutions
for
this
problem
that
they
already
have.
Certainly,
I
was
asking
around
internally
at
docker,
and
that
was
the
case
with
us
and
like,
and
they
I've
kind
of
pointed
them
and
scheming
her
and
said,
like
here's,
a
tool
you
can
look
at
instead
of
something
homegrown,
but
I
think
that
that's
probably
what
the
the
competition
is
to
some
extent
there's
not
been.
E
You
know
spend
time
talking
to
users
and
work
out
work
out
if
you're
solving
the
right
problems,
why
people
aren't
adopting
and
work
on
a
plan,
a
plan
to
fix
that
yeah,
absolutely
cornelia.
I
I
totally
agree
that
that
the
clarity's
giving
regulation
is
a
fabulous
idea,
so
you
know
we
have
to
kind
of
see.
E
K
I
I
definitely
hear
what
you're
saying
and
completely
agree
with
both
points,
one
that
we
need
to
really
work
on
adoption.
We
have
a
few
folks
that
we're
trying
to
get
to
list
as
the
in
the
adopters
file
like
they're
early.
It's
still
not
a
massive
number,
but
that
is
our
our
primary
focus.
I
think
like
more
than
adding
new
functionality
in
like
that
is
has
to
be
our
focus
right
now
and
I
think
that's
yeah,
like
we
called
that
out.
K
K
Yeah,
I
mean,
I
think
you
hit
kind
of
the
challenge
that
we
have
right
now,
where
the
folks
who
do
see
it,
you
know,
have
started
to
adopt
it
and
and
they
like
it,
it's
slow
traction
for
us
right
now,
but
you
know
nobody's
heard
of
it.
Yet,
even
on
this
call,
you
know
we're
seeing
comments
that
people
are
sitting
at
for
the
for
the
first
time.
So
you
know
it's
that
that's
the
challenge,
and
I
understand
that
as
a
sandbox
project,
there's
very
limited.
K
L
E
K
There's
there's
like
tools
like
liquid
base
as
an
example:
they
have
a
commercial
and
an
open
source
offering
you
know,
and
we've
actually
spent
some
time
talking
to
the
the
team
at
liquid
base
on
how
we
can
collaborate
with
existing
tools
that
are
out
there
to
kind
of
bridge
that
gap
for
people
who
have
already
adopted
tools.
Yeah
fly
away.
K
If
I
can't
just
ask
a
question:
if
it's
complimentary
or
a
replacement
to
liquid
base,
you
know,
I
think
it's
definitely
complementary.
It
could
be
a
replacement
for
some
specific
use
cases,
but
liquid
base
does
more
than
schema
hero
does
today,
and
so
we
think
that
there's
like
a
potential,
you
know
solution
where
it's
complementary,
where
it
handles
the
schema
migrations
and
doesn't
handle
data
migrations
getting
really
into
the
weeds
on
the
project
actually
does.
K
B
B
K
So,
where
we've
seen
early,
adoption
is
like
when
folks
start
really
adopting
git
ops
as
a
deployment
model
where
their
ci
process
is
like
they're
using
flux
or
argo
or
some
other
get
ops
tool
to
do
it
and
they
don't
want
an
out-of-band
schema
migration.
They
want
to
like
like
tightly
couple
those
schema
migrations
in
with
the
application
deployment.
It
doesn't
have
to
be
late
in
the
adoption.
You
know
once
you
have
kubernetes,
though
it's
it's
viable.
B
K
A
K
K
Yeah,
I
think
you
know,
if
you
know,
one
of
our
intents
is
like
managing
database
migrations
using
control
in
kubernetes
native
tooling
is
that's
one
area
that
we
we
seem
to
hit
a
little
bit
of
challenges
with
some
folks
where
developers
were
managing
database
migrations
and
now,
if
you
have
an
sre
team
or
an
ops
team,
that's
actually
managing
it
because
they're
managing
the
cluster,
you,
you
shift.
The
task
of
that
and
the
ops
team
or
the
sre
team
needs
to
be
able
to
understand,
schema
migrations
a
little
bit
more.
A
Fair,
that's
why
I
was
like.
I
need
more
context.
I
think,
okay,
I
I
will
go
ask
like
the
team
that
does
all
of
that
like
what
their
cycle
for
being
able
to
update
things
looks
like
so.
Thank
you.
Thank
you
all
right.
I'm
actually
gonna
move
us
like
technically,
we
should
have
provega
coming
up
next,
but
I
don't
have
that
particular
toc
member
on
the
call
just
yet
so
I'm
going
to
move
us
on
to
network
service
mesh
and
we'll
come
back.
As
I
see,
aaron
join.
M
There
weren't
really
any
asks
from
cncf
for
the
toc.
The
team
said
that
they
were
pretty
happy
with
the
support
they're.
Getting
the
biggest
kind
of
concern
is
that
there
are
things
that
they
will
get
at
incubation
that
they
would
love
to
get
now,
but
I
think
that's
a
common
concern
of
almost
any
sandbox
project.
M
I
think
the
most
interesting
conversation
to
have
with
network
service
meshes
around
adoption
and
there
were
a
few
comments
on
adoption
in
the
dock
and
then
I
think,
frederick
is
here
and
I
think,
he's
probably
the
best
person
to
talk
about
adoption.
I
know
that
this
conflicts
with
their
weekly
project
meeting,
so
I
want
to
give
him
a
chance
to
to
speak
up
since
he
skipped
that
to
join
us.
M
Hello.
Thank
you
so
in
in
terms
of
adoption
to
understand
where
we
are
there's
there's
a
couple
things
that
have
to
happen.
So
it's
not
like
you
just
suddenly
say:
hey,
there's
an
endboot
user
who
wants
to
use
it,
they
go
and
install
it
and
then
they
move
forward.
So
the
adoption
requires
something
that
network
service
mesh
itself
controls.
M
So
in
other
words,
if
you,
if
you
want
to
have
a
data
plane
or
something
hook
up
to
it,
never
service
mesh,
would
it
would
interface
interact
with
that
thing
and
then
and
then
from
there.
The
the
end
user
could
then
use
that
to
coordinate
multiple,
disparate
systems,
as
as,
if
they
were
one
thing
across
vendors,
and
so
in
terms
of
adoption.
We've
we've
been
working
with
a
few
with
a
few
vendors.
M
We
have
comments
from
both
cisco,
I
think,
disclose
a
comment
on
there,
erickson
and
and
intel
within
the
within
their
within
the
the
review.
Unfortunately,
there's
not
much
more,
I
can
say
in
there,
but
what's
what's
in
there
is,
is
the
the
blessed
approved
versions,
but
I
can
say
that
there
is
there's
a
lot
of
active
work
going
on
in
order
to
provide
additional
that
additional
vendor
support
so
from
the
consumer
side,
and
I
come
from
a
consumer
company.
M
Yeah
at
least
to
me
that
makes
sense,
and
I
took
the
ed
for
a
while
yesterday,
because
we
had
the
the
toc
liaison
network
tag
meeting
yesterday
as
well.
So
I
think
all
of
my
questions
are
answered.
I
don't
know
if
anybody
else
either
from
the
toc
or
anyone
else
on
the
call
has
questions
or,
if
we're
good,
to
move
on.
B
N
Hello
and
your
mic
works
yay,
go
ahead
all
right,
so
provega
has
actually
had
a
really
healthy
adoption
and
contributions,
since
they
first
presented
to
the
tag
for
sandbox
a
while
ago
I
mean
they've
had
76
different
releases.
They
have
had
a
very
diverse
set
of
contributors
and
customers
adopting
the
technology.
So
what
is
provega,
I
would
say
you
know
at
a
high
level.
It
definitely
is
comparable
to
kafka
and
pulsar.
You
know
it's.
It's
a
distributed
messaging
service
that
works
on
streaming.
N
I
think
it's
pretty
unique
in
terms
of
the
different
storage
possibilities
within
the
cncf,
so
I
like
that
it
offers
a
little
bit
different
set
of
features
that
aren't
typically
available
in
our
standard
kind
of
storage
solutions,
and
so
they
have
a
diverse
set
of
use
cases
that
is
continuously
growing
on
the
cncf
website.
You
can
see
you
know
kind
of
a
comparison
of
the
different
features
available
between
kafka
and
pulsar
and
how
it
differentiates,
which
I
think
is
really
important
when
we
consider
taking
projects
from
sandbox
to
incubation.
N
That
is
one
of
the
standards
is.
How
is
this
different,
and
it's
clearly
articulated
through
that?
You
know,
unfortunately,
github
doesn't
give
you
like
a
a
year-long
view
of
how
many
contributions
commits
and
things
are
going.
So
I
think
you
know
just
triggering
off
the
releases.
I
think
we
can
conclude
in
the
number
of
people
who
are
contributing
to
it
from
a
year
ago
that
it
is
healthy.
It
there's
a
lot
of
interest
and
it's
unique,
and
so
are
there
any
questions.
I
know
I
went
through
that
rather
quickly.
N
The
only
the
only
thing
that
wasn't
updated
was
not
on
the
cncf
provega
site,
but
the
purvega
project
site.
The
road
map
seems
to
be
a
little
bit
lagging
behind.
So
that
would
be
one
thing
that
I'd
want
to
make
sure
is
updated
before
we
went
further
is
to
understand
all
the
different
things
that
they've
put
for
different
releases.
How
does
that
fit
into
the
roadmap
into
the
current
timeline?.
L
N
E
I
just
want
to
say
I
got
because
I
did
the
original
sandbox
review
for
professor
when
I'm
really
pleased
with
the
progress
it's
been
making
since
it's
joined
the
sandbox,
because
I
remember
you
know
having
those
discussions
with
you
and
it
was
a
very
early.
You
know
from
the
adoption
point
of
view,
it
was
very
early
stage
back
then,
and
I'm
really
pleased
to
see
how's
kevin
martin
in
the
sandbox.
L
Yeah,
I
think
our
challenge
is
having
qualified
end
users
as
adopters.
So
we
have.
You
know
several
vendors
that
have
adopted
or
a
lot
of
adoption
is
maybe
early
in
the
prototypal
stages,
or
you
know
we're
seeing
a
lot
of
adoption
in
the
flint
community,
especially
in
china,
but
we
need
to
see
people
get
to
production
and
then
be
willing
to
publicly
acknowledge
their
use
of
provega.
A
O
That
mute
button
come
on
in
myself,
hello,
so
athens
deals
with
well
authentication
authorization
stuff
and
they
aren't
going
for
incubation
anytime
soon,
so
the
project
is
mostly
developed
out
of
yahoo
and
yahoo,
japan,
which
are
two
distinct
legal
entities.
If
I
understand
it
right
and
it's
mostly
works
with
azure
and
aws,
all
their
contributions
come
from
these
organizations.
O
In
fact,
if
I
look
at
contributions
for
the
last
few
months,
there
hasn't
been
any
from
any
other
outside
organizations,
but
it
is
actively
developed
by
them
and
being
actively
worked
on
and
used
by
them.
It's
one
of
those
areas.
They
know
they
need
to
improve
on
and
they
just
started
collecting
those
who
are
actually
using
it.
So
they
just
started
trying
to
collect
that
and
get
that
information.
O
There
is
somebody
vespa
who's,
looking
at
adding
gcp
support
to
work
with
their
system,
and
so
there
might
be
some
expansion
there
coming,
but
there
is
active
ongoing
development
around
it,
they're
just
not
seeing
a
lot
of
community
growth
and
those
other
things
put
into
it
right
now.
In
fact,
if
you
go
to
the
website,
it
reads
a
lot
like
a
product
thing
without
a
whole
lot
that
says
here's
kind
of
how
you
get
involved
if
you're
going
to
go,
contribute
or
be
involved
in
that
community.
A
J
O
J
O
J
No,
I
think,
as
we
have
mentioned
in
the
pr,
we
are
gonna,
go
for
the
security
review
and
hoping
to
get
more
eyes
on
it
in
terms
of
what
project
is
and
where
we
can
improve.
And
yes
I
mean,
I
understand
it
being
a
sandbox
project
doesn't
have
direct
marketing
support,
but
we
are
gonna,
see
what
we
can
do
to
get
adoption
going.
O
B
Right,
so
we
could
do
it
in
a
couple
of
ways.
One
way
is
to
check
if
any
of
us
have
any
concerns
about
the
projects
that
we've
talked
about
right
now
or,
and
if
there
are
so
we
can,
we
can
do
like
wood
on
bulk,
saying.
Okay,
all
the
projects
that
were
reviewed
today
are
good
with
a
plus
one,
zero
minus
one
or
if
you
want
to
split
it
into
individual
ones.
We
can
do
that
too,
which
one
would
the
toc
members
prefer
any
any
suggestions
there.
E
A
F
Yeah,
so
all
the
needed
review
and
the
due
diligence
work
has
to
be
finished,
so
the
the
true
boyfs,
which
is
known
as
cube
fs
today,
so
this
project
is
generally
ready
to
move
to
incubation,
so
we
are
still
waiting
for
some
minor
feedbacks
from
toc
site,
but
everything
is
ready.
I
think
this
project
we
can
actually
ask
for
public
comment
for
their
due
diligence.
Talk
yeah.
H
H
A
P
M
We
have
made
almost
no
progress
here.
I
think
we
talked
a
little
bit
in
december
and
january
and
our
plan
was
to
have
some
conversations
with
end
users
and
adopters
of
artifact
hub
as
we're
still
kind
of
debating
the
like
how
well
it
fits
the
model
of
projects,
conversation
that
we
had
before,
and
I
think
that
conversation
was
happening
with
matt
before
matt
was
on
the
toc,
so
matt
and
I
just
need
to
get
together
and
figure
this
out
and
get
to
some
of
the
next
steps.
N
So
I'm
in
this
similar
situation
as
dave,
I
think
there
were
some
reservations
about
key
cloak
initially
in
terms
of
diversity
of
contributors
and
end
users,
and
so
I'll
need
to
go
through
the
same
due
diligence
to
make
sure
the
things
that
were
raised
before
on
the
toc
with
previous
sponsors
are
satisfied
since
I'm
taking
it
over
secondhand.
So
I
am
in
process
of
doing
that
and
we'll
provide
an
update
as
they
come
in.
A
H
A
E
A
A
Okay,
seeing
big
thumbs
up
all
around
one
request
that
I
had
in
the
middle
of
the
meeting
and
then
kind
of
switched
towards
was
like
talk
a
little
bit
about
what
the
project
actually
does,
because,
even
though
all
of
us
actually
know
what
it
is,
that
is
not
immediately
apparent
towards
the
community
overall.
So
I
think
in
the
future,
we
will
set
up
a
way
to
be
able
to
make
sure
that
the
project
knows
that
this
is
happening
more
than
just
like
a
week
in
advance
and
also
directly
inviting
them
again
as
well.