►
From YouTube: CNCF TOC Meeting 02-01-2022
Description
CNCF TOC Meeting 02-01-2022
A
B
A
A
B
A
B
A
E
One
of
the
things
we've
been
working
with
is
some
of
the
marketing
folks
to
actually
start
raising
awareness
within
the
cnc
projects,
about
the
resources
that
we
have
available,
that
we've
generated
from
contributor
strategy
also
for
tag
security
as
well,
since
they
have
a
lot
of
important
resources
for
projects.
I
don't
think
the
majority
of
our
project
maintainers
know
about
them.
E
The
contributor
growth
has
started
work
on
a
reviewing
guide
for
projects
to
generate
how
to
review
documents,
which
is
something
that's
recommended,
but
not
required
by
any
of
the
graduation
stages
and
we'll
have
a
maintainer
circle.
Sometime
soon
look
for
announcements
there,
the
I've
not
had
a
chance
yet
to
file
a
toc
proposal
on
this
point,
I'll
wait
for
the
new
tsa
to
be
seated
that
cncf
wide
mentorship
as
you
who
are
requested
be
officially
assigned
under
contributor
strategy.
So
I'll
do
that
after
the
new
toc
is
seated.
B
F
A
E
F
And
I
think
too,
I
mean
anything
with
people
right.
Different
people
are
going
to
respond
to
different
formats,
so
some
people
are
really
great
at
email.
Some
people
are
better
at
twitter,
some
people,
like
blog
posts,
so
we're
thinking.
If
we
can
hit
people
from
multiple
channels
we
can
better
get.
The
word
out
certainly
makes.
A
G
I
Yeah,
sorry,
sorry
for
being
late,
but
it
was
it's
one
of
those
days
where
I'm
back
to
back
and
time
zones
are
great,
but
time
is
still
linear,
which
is
sometimes
painful
yeah.
So
a
quick
update
on
the
app
delivery
side
on
project
reviews,
just
a
reminder
that
captain
and
backstage
are
still
in
the
review
by
the
toc.
I
You
also
asked
us
on
some
feedback
on
conveyor
and
by
the
way.
This
is
the
feedback
really
here
for
it.
You
see
that
you
asked
us,
for
we
are
also
on
a
separate
track,
we're
going
to
discuss
with
the
conveyor
team
and
how
we
really
want
to
progress
there.
So
we
just
don't
want
them
to
hand
like
back
okay.
This
is
what
we
think
about
your
project,
so
very
high
level
on
conveyor.
I
So
for
those
of
you
not
familiar
it's
more
or
less
a
set
of
tools
that
emerged
out
of
some
consultancy
on
the
on
the
ibm
and
and
red
hat
side
for
migrating
applications
over
from
traditional
environments
to
cloud
native
world,
and
we
we
had
a
really
hard
time
wrapping
our
head
around
this.
So
first
we
think
I
think
it's
good
that
there
is.
It
was
always
part
of
the
charters
of
app
delivery
to
help
people
migrate
applications
over.
But
when
we
look
at
the
project,
we
found
a
couple
of
things
that
were
not
that.
I
I
Others
are
docker
compose-based
deployments
that
are
kind
of
available,
so
it
feels
like
it's
a
set
of
smaller
tools
that
are
put
together.
Some
of
them
are
actually
even
grafana
dashboards.
I
think
there
needs
to
be
some
housekeeping
that
needs
to
be
done
on
the
project.
Some,
I
would
move
intelli
out
like
there's
some
openshift
suite
openshift
4
migration,
tooling
in
there,
which
I
don't
see,
is
going
to
live
very
long.
I
There's
an
interesting
project
of
migrating
virtual
machines
to
cube
word
there.
The
question
is
shouldn't
this
actually
be
part
of
q
word
per
se,
where
it
might
be
a
better
home
for
it
and
might
fit
in
there
so
yeah.
I
think
our
overall
feeling
is
a
set
of
tools
that
they
kind
of
have
built
out
and
like
one
of
their
core
tools,
is
more
or
less
an
assessment
tool
that
comes
kind
of
like
with
this
consulting
backgroundish.
I
And
that's,
I
think,
where
we
still
and
we
will
follow
up
with
them.
I
think
some
bits
and
pieces
is
still
something
we
need
to
wrap
our
wrapper
ahead
around
it,
but
I
think
that
this
way
it
is
right
now
I
wouldn't
see
really
how
it
fits
into
as
a
sandbox
project
and
again
it
also
has
this
thing:
it's
never
going
to
really
graduate
because
it's
a
set
of
conversion
goals,
so
somebody
yeah
yeah.
J
Hey
this
is
this:
is
james
libakia,
so
I'm
involved
in
the
conveyor
project.
So
thanks
for
the
update
I
was
going
to
ask,
is
there
a
way
we
can
get
this
feedback
faster
going
forward?
I
put
a
link.
I
posted
this
because
after
we
submitted
the
sandbox
application,
I
went
to
the
tag
app
delivery
meetings
starting
in
november,
and
I
asked
you
know
feedback.
I
got
a
couple
of
questions
in
there
and
so
I
tried
to
answer
them
in
this
mailing
list
thread.
J
J
He,
but
he
said
I
can't
remember
like
the
specifics,
because
I
I'm
like
yeah
it's
good
to
hear
like
okay.
If
licensing
is
a
problem
and
deployment
method,
if
we
would
have
known
two
months
ago,
we
probably
would
have
already.
We
probably
could
have
already
standardized
that
one
and
moved
it
forward.
If
those
are
the
things,
but
I
think
just
getting
that
feedback
faster
would
be
very
helpful.
I
Yeah
we
tried
to
do
our
best
with
the
constraints
which
we're
in,
and
we
also
reached
out
to
work
with
you
on
this.
So
feedback
is
taken,
but
yeah
there
was
always
a
holiday
break
in
between
on
other
topics.
Awareness
for
the
working
group
is
also
something
we're
working
on,
because
one
of
the
feedbacks
from
kubecon
was
hey.
I
Anybody
who
has
done
this
before
think
security
has
done
that
your
feedback
is
highly
appreciated
on
how
you
set
this
up
and
make
this
work,
because
I
think
most
of
the
pre-conference
events
are
more
or
less
focused
towards
companies
and
not
the
tags
are
setting
them
up
so
much.
But
we
plan
to
really
get
this
done
for
the
upcoming
kubecon
to
have
more
of
the
app
delivery
conversations
happening
there
as
well.
B
That's
amazing:
I'm
going
to
guess
that
there
is
not
a
lot
of
lead
time
for
getting
that
co-located
event
up
and
running.
So
probably
you
know
time
is
of
the
essence,
but
I
think
that's
a
really
good
thing
to
try
and
put
together
the
security
con
folks.
Tank
security
definitely
had
a
ton
of
experience
on
how
they
got
theirs
off
the
ground,
so
that
would
definitely
sync
with
them.
L
Once
since
last
we
gave
an
update
and
the
focus
of
the
discussions
had
been
within
the
working
group
and
progress
toward
one
of
the
long-term
goals
that
that
is
that
the
working
group
has
had
and
that's
like
to
going
through.
Just
a
large
set
of
tests.
Scenarios
for
evaluating
characterizing
performance
across
different
service
meshes
and
different
configurations,
but
so,
as
of
today,
a
couple
of
the
maintainers
have
access
to
the
cncf
cluster,
so
we
met
with
equinix
metal.
L
I
tried
to
familiarize
with
the
environment
a
bit
or
sort
of
described
the
beyond
the
nature
of
the
tests
and
then
sort
of
the
ongoing
goals,
and
so
so
progress
there.
There
is
an
open
call
in
the
working
group
for
participation
for
folks
that
are
well
I'm
going
to
abuse
the
terms,
since
everyone
else
does.
I
suppose,
and
that's
to
say
that
folks,
that
are
more
into
devops
or
more
into
in
tooling
than
they
are
necessarily
into
code,
so
come
and
participate.
That's
there's
help
needed
in
that
project.
L
L
That's
kind
of
that's
the
update
from
the
working
group.
There
is
the
last
project
that
was
proposed
for
sandbox
is
fab
edge.
There's
a
there's,
an
active
thread
in
the
tfc
mailing
list.
Sort
of
you
know
discussing
the
the
project
and
the
co-chair
ed,
who
was
kind
of
deep,
diving
toward
fab
edge.
He's
got
a
conflict
today,
so
ken
who's
also
a
co-chair,
is
on
the
call.
L
Can
I
I
don't
know
that
either
ken
or
myself,
I
don't
have
a
have
a
response
like
it's.
Just
it's
not
a
project
that
that
I've
spent
time
with
yet
they
didn't
present.
It's
a
a
couple
of
things
to
take
away.
I
suppose
it's
well,
it's
a
new
project,
pretty
pretty
young.
It's!
I
think
it's
grown
two-fold
since
they
presented
a
couple
of
months
ago,
which
is
maybe
less
about
project
growth
and
more
about
how
that
that
it's
early.
L
L
B
B
B
So
maybe
we
need
the
kind
of
cni
project
to
sort
of
weigh
in
on
how
they
want
to
describe
that
or
classify
classify
that
or
or
something
because
I
I
I
guess,
people
won't
go
very
far
down
the
road
of
saying
oh,
we'll
use
this
cni
and
then
discovering
that
actually
it's
an
edge-specific
cni,
but
that
that
was
one
of
the
things
that
we
were
a
bit
worried
about.
I
think
also
when
we
were
looking
at
that
sandbox
proposal.
B
B
L
L
M
Lee,
I
think
you
might
want
to
involve
some
of
the
folks
on
the
q
batch
project
and
I
think,
there's
a
two
other
projects
that
are
working
with
technologies
related
to
the
edge
super
edge
and
open
year.
So,
and
I
think
it's
the
idea
just
to
have
more
clarification
about
the
different
projects
of
you
know.
F
L
Yeah
anyways,
that's
good
feedback.
We
had
asked
someone
yeah
like
I
can't
it's
unclear
yeah,
some
of
the
I
don't.
Some
of
the
presentation
was
a
bit
unclear
to
me
when
it
was
originally
proposed.
We
did
give
feedback
and
some
of
those
were
the
the
same
questions
was
like
was
clarification
on
which,
which
was
which
and
what
the
purpose
was,
and
so
he,
the
maintainer
that
was
proposing,
did
come
back
with
some
of
those
some
clarification
yeah
anyway,
I'll
I'll
reinforce
that
messaging
and
maybe
actually
ricardo.
I
think
to
your
point.
L
M
N
L
Yeah,
but
the
the
vision
there
is
that
the
hope
is
like
every
day.
The
vision
is
that
the
the
tooling
is
of
it
tooling
is
available
to
each
of
the
service
mesh
projects.
To
do
it
themselves,
like
each
of
the
projects,
are
going
to
have
an
opinion
about
what
the
particular
test
scenarios
are,
and
they
may
want
to
like.
L
The
part
of
the
goal
of
the
project
is
to
focus
on
the
strengths
of
each
of
the
those
service
meshes
in
context
of
their
performance,
acknowledge
where
they're
weak
or
maybe
what
what
scenarios,
what
workloads
or
what
deployment
styles,
maybe
don't
work
very
well
for
them,
but,
but
so
is
to
anyway.
The
tooling
is
is
open.
N
O
O
We
took
some
advice
from
chris
last
year
and
we
kind
of
you
know
started
filling
out
a
project
plan
for
observicates
which
I'll
get
to
in
a
moment.
In
today's
meeting,
we
have
catherine
paganini
from
the
glossary
project.
The
business
value
sub
committee
there's
a
clear
opportunity
to
to
help
contribute
observability
terms
to
the
glossary
project.
In
addition,
bumblebee
joins
us
to
discuss
the
project
solo.io.
O
The
cncf
member
has
open
sourced
this
as
an
ebpf
toolkit,
so
they're
going
to
come,
give
a
brief
overview
of
what
the
project
is
and
say
hello
for
the
first
time
in
future
meetings,
we'd
really
like
to
invite
other
projects
in
the
observability
space
that
are
that
are
relevant.
For
example,
hubble
we
would
love
to
have
hubble
come
give
a
deep
dive
or
an
overview
for
for
the
observability
community
about
you
know
how
it's
using
ebpf
and
just
what
it
is
and
how
it
works.
O
We
have
an
open
agenda,
so
I
mentioned
it
before,
but
there's
a
project
called
observe
dash
k8s
that
we've
launched
well
we're
in
early
planning
for
q1
will
be
really
planning
and
nailing
down
the
project
plan
and
resourcing,
and
things
like
that.
We
expect
to
be
actively
working
on
this
in
q2
and
q3
expect
an
email
from
me
later
on
today,
formally
requesting
the
toc
to
kind
of
approve.
O
Have
all
contributed
to
a
working
document
that
is
sort
of
charter
mission
and
overall
concept
that
I've
linked
in
the
slides,
and
we
expect
to
close
down
on
that
as
well,
so
we'll
announce
a
public
nomination
period
for
working
group
chairs,
and
we
are
excited
to
launch
that.
We
have
also
secured
the
observations
and
things
like
that
and
plan
to
transfer
all
of
that
to
the
cncf
if,
if
approved,
and
if
it
makes
sense
to
do
so.
O
In
short,
what
it
is
is
it's
a
curated
community
driven,
you
know
a
set
of
cloneable
representative
apps
with
examples
of
how
to
instrument
them
and
or
grok.
You
know
what
it
is
that
they're
doing
with
useful
examples
of
cncf
projects
and
tooling
brought
to
bear.
This
is
not
the
tag
saying
this
is
the
right
way
to
do
it.
O
This
is
the
tag
saying
we're
launching
a
project
and
projects
in
the
space
which
we'll
be
reaching
out
to
are
welcome
to
contribute
to
it
and
we
encourage
it
and
we
hardly
welcome
it.
So
we're
excited
about
that
again.
It's
early
definition
at
the
moment,
but
we
we
hope
to
to
be
closing
down
on
that
in
the
coming
months
and
then.
Lastly,
we've
got
chair
and
tl
nominations
and
elections
coming
up.
O
M
This
is
a
take
on
confidential
computing
and
it's
mainly
from
the
folks
at
intel,
I'm
so
excited
to
see
that
that's
going
to
be
next
month
about
a
month.
From
now
and
on
the
workloads
space
we
had
cluster
net
present
on
or
we're
having
cluster
net
present
on
february
17th
two
weeks
from
now.
This
is
a
project
that
allows
you
to
manage
multiple
kubernetes
clusters
or
a
fleet
of
kubernetes
clusters.
I'm
excited
to
to
see
that
project.
M
So
this
this
project
has
been,
we
got
a
foundation
for
a
while.
So
we're
excited
to
see
this
join.
The
the
cncf
cubert
is
another
project
that
is
going
through
incubation
and
we
just
completed
the
due
diligence,
diligence
document
and
that
will
be
share
with
the
the
rest
of
the
community,
the
rest
of
the
dlc
and
public
comment
period.
I
think,
will
be
open
pretty
soon
then
open
cluster
management,
another
project
that
is
very
similar
to
cluster
net.
M
M
M
So
if
you're
interested,
you
can
take
a
look
at
the
project,
they
haven't
thought
about
applying
for
the
same
cncf,
but
something
to
you
know,
look
in
the
future.
Maybe
they
will
why
and
then
in
terms
of
activities.
In
the
tag
I'm
excited
to
have
alex
kanepski
join
the
attack
as
a
as
a
tech
lead.
So
he
brings
in
about
20
or
plus
years
of
experience.
He
works
at
intel,
working
in
open
source
in
working
in
containers
and
making
sure
that
you
know
you.
M
G
Hello:
everyone.
We
have
a
few
updates,
we're
doing
a
lot
of
reorganization
within
the
group
to
make
sure
that
we're
staying
on
task
and
actually
getting
a
lot
of
things
accomplished.
So
first
up
cloud
custodian
review
is
complete.
We
just
have
a
few
more
checks
to
go
through
before
we
can
merge
that
into
the
repo
we've
started,
ramping
up
for
an
argo
review.
This
is
a
very
large
project.
It's
actually
consistent
of
four
sub-projects
that
we
will
be
reviewing
sequentially
due
to
low
reviewer
count.
G
So
if
you
are
interested
in
participating
in
a
security
review,
you
don't
have
to
be
a
security
person.
We
are
more
than
happy
to
mentor
and
talk
through
that
we're
looking
for
more
security,
reviewers
we're
also
working
on
refocusing
a
road
map.
So
last
year
we
had
a
very
large
plan
and
a
very
big
goal
of
a
lot
of
things
that
we
wanted
to
accomplish.
Unfortunately,
we
did
not
get
them
all
done.
G
We
do
have
a
lot
of
projects
in
flight,
though
so
we're
looking
to
close
all
of
those
out
and
kind
of
re-scope,
so
that
we
have
a
more
manageable
target
of
about
two
to
three
projects
per
quarter.
And
lastly,
we
want
to
welcome
pushkar
to
our
security
tag
leadership
team.
He
has
been
an
active
contributor
within
the
security
tag
for
a
number
of
years,
we're
very
happy
to
bring
him
into
the
leadership
team.
That's
everything.
B
K
K
In
that
process.
Open
ebs,
we've
had
a
meeting
with
the
team.
The
team
still
wants
to
proceed
with
the
process.
We
have
some
questions
open
with
them
around
some
of
the
changes
that
have
happened
following
following
data
cores
acquisition
of
of
maya
data
and
some
of
the
team,
changing
roles
or
or
moving
to
different
firms.
K
And
it
was
it's,
it's
very
large.
It's
very
large
project,
with
lots
of
components
and
lots
of
functionality
under
very
active
development
with
with
a
number
of
large
production
systems,
and
we
we
actually
had
to
schedule
a
follow-up
call
to
kind
of
go
through
some
of
the
some
of
the
more
technical
parts
of
the
components
which,
which
was
which
was
extremely
interesting.
At
this
stage.
K
I
think
there
is
nothing
from
from
the
tag
point
of
view
to
to
stop
recommend
a
recommendation
to
move
this
into
into
sandbox.
It
is.
It
is
a
very
interesting
system,
with
with
both
sort
of
block
and
file
system,
capabilities,
with
good
integration,
with
sort
of
connective,
client-linked
components,
and
I
think
there's
a
lot
of
promise
here.
You
know
some
rough
edges
that
that
the
team
are
working
on,
but
I
think
it
definitely
meets
all
of
the
criteria
for
sandbox.
K
P
A
A
Q
F
B
Q
Q
R
B
Amelia,
I
believe,
was
not
with
us.
Go
ahead.
Liz
I
was
gonna,
say
we're
missing
backstage,
which
is
with
me
yeah
yeah,
and
I
have
done
three
user
interviews
we're
in
reasonably
good
shape.
I
am
shooting
for
us
to
have
that
due
diligence
document
done
by
the
end
of
the
week
when
I
stopped
being
on
the
toc
and
then
someone
else
will
have
to
take
it
over
through
the
public
comment.
But
hopefully
there
will
be
someone
on
the
new
reconstituted
toc
who's
prepared
to
do
that,
because
I
will
have
done
all
the
legwork.
A
A
That
just
came
in
my
thinking
around
that
one
is
that
that's
meaningful
to
be
able
to
look
probably
like
the
the
the
meeting
on
the
15th,
because
there's
plenty
of
things
that
people
want
to
be
able
to
review
and
again
our
new
reconstituted
toc.
We'll
have
more
to
say
about
that.
Unless
somebody
wants
to
be
able
to
like
actually
sponsor
here,
which
I
was
not
going
to
put
you
all
in
the
spot.
For.
A
A
B
A
That
is
going
to
be.
My
next
thing
is
being
able
to
make
sure
that
all
of
the
emeritus
have
like
access
into
emeritus
can
come
in
and
weigh
in
on
projects,
and
let
everybody
know
as
far
as
like
hey,
if
there's
something
that
we
should
be
thinking
about,
that
we're
not
we
want
to
hear
from
you
brilliant.
I
hope
we
get
special
t-shirts
for
that
role.