►
From YouTube: CNCF TOC Meeting - 06-07-2022
Description
CNCF TOC Meeting - 06-07-2022
A
A
A
All
right,
let's
go
ahead
and
kick
us
off
welcome
to
our
normal
anti-trust
policy
notice,
normal
meeting
logistics.
You
are
here,
you
have
made
it
coc
members
present
today.
This
gets
updated
over
in
the
toc
tracker
over
on
the
public
thing,
so
here's
our
agenda
day
I'll
be
chatting
about
the
special
election
and
then
I'll
hand
it
off
to
dims,
and
everyone
else
should
be
able
to
run
through
tag
updates.
Note
that
new
order
that
I
talked
about
at
the
top
of
the
call,
so
we
have
basically
flip
things,
run
them
backwards.
A
So
with
that
come
on,
oh
goodness,
it
is
hanging
here
there
we
go.
That's
what
I
was
going
for
all
right.
As
you
all
know,
we
have
had
a
toc
member
stepped
down
and
we
have
a
special
election
open
and
these
are
open
from
your
friendly
neighborhood
governing
board.
So
if
you
have
someone
that
wants
to
be
nominated
here,
governing
board
can
do
it.
This
closes
at
noon
pacific
today,
with
the
hope
of
being
able
to
have
this
person
seated
by
july,
1st.
D
Hello,
it's
been.
It's
been
a
quiet
couple
of
weeks,
of
course,
because
of
kubecon,
but
a
couple
of
updates
in
terms
of
the
projects,
so
cubafs
is
in
the
process
of
being
voted
for.
If
you
haven't
voted
already,
just
a
quick
reminder
that
it's
waiting
feel
free
to
ask
any
questions.
If
there
are
any
open
ebs,
we
had
some
discussions
around
the
next
steps.
I
I
believe
we're
still
waiting
for
a
toc
sponsor
on
this.
D
So
I
think
we're
we're
pausing
until
until
somebody
from
the
toc
is,
is
able
to
put
their
hand
up
on
this
one
and
the
curve
storage
system
we
recommended
for
sandbox.
I
believe
it's
in
the
list
at
the
moment
in
terms
of
tag
meetings,
we
are
going
to
be
following
on
with
some
of
the
work
with
the
cartographers
project,
we're
putting
together
some
of
the
technical
maturity
model,
steps
for
the
storage
side
of
the
world,
and
tomorrow
we
have
a
presentation
from
the
cd
project,
which
should
be
quite
interesting.
D
D
In
in
my
case-
and
I'm
sure
this
applies
to
some
of
the
other
chairs
as
well-
we've
probably
exceeded
our
term
by
quite
a
bit,
and
I
guess,
and
partly
that's
because
of
you
know
nobody
else
coming
forward
and
probably
also
a
little
bit
of
us,
not
necessarily
you
know
going
out
and
actively
looking
for
other
chairs
as
well,
but
I
guess
the
the
question
is:
how
do
we
want
to
resolve
that
going
forward?
Do
we
want
to
do
we
want
to?
D
E
D
Term
lines
so
so
having
had
the
pleasure
of
writing
the
operating
model
for
the
tags
with
clinton,
what
we
had
put
into
the
overall
operating
model,
which
applies
to
all
the
tanks,
is
that
there
are
three
co-chairs
there.
They
need
to
be
approved
by
the
by
the
trc
and
that
each
coacher
has
a
two-year
term
and
that
there
is
a
level
of
rotation
so
that
you
never
take
out
all
of
the
chairs.
At
the
same
time,
that
was
the
original
intention.
D
A
There's
there's
some
comments
in
chat,
which
I
think
are
relevant
and
worth
being
able
to
bring
up,
because
the
ideal
is
in
fact
to
be
able
to
mentor
a
new
chair
and
to
be
able
to
help
like
pull
these
things
along.
I
I
also
recognize
that,
frankly,
due
to
lack
of
time
and
all
of
that,
that
probably
hasn't
been
as
available
so
I'd
kind
of
like
to
be
able
to
do
something
somewhat
in
between
as
far
as
like.
Yes,
we
can.
We
can
definitely
go
towards
like
being
able
to
say
all
right.
A
F
F
With
entire
security
we
have
set
it
up
such
that
you
do
not
have
to
be
a
technical
lead
to
become
a
co-chair
part
of
the
deliberation
in
the
security
tags.
Co-Chair
selection
process
was
largely
around
the
value
that
each
co-chair
brought
to
the
tag
itself,
so
we
always
had
somebody
that
was
very
community
growth
and
development
focused.
F
Now,
that's
not
going
to
work
for
everybody.
We
do
have
a
lot
of
active
participants,
but
we
also
have
a
lot
of
ongoing
projects
and
a
somewhat
documented
mechanism
to
elevate
individuals
that
lead
projects
into
a
technical
leadership
position
and
then
nominating
them.
We
recently
ran
through
a
study
of
the
level
of
effort
involved
in
organizing
and
executing
our
tag
and
versus
how
many
folks
in
leadership
positions
are
taking
on
that
work
and
we
had
to
increase
the
amount
of
technical
leads
for
that
group.
Because
of
that,
a
lot
of
this
is
mentoring.
G
F
D
No,
I
I
I
I
think.
That's
that's
really
great,
what's
happening
in
the
security
tag
and
I
think
they,
you
probably
have
a
little
bit
more,
perhaps
a
community
interaction
than
some
of
the
other
tags.
I
think
tanks
sort
of
differ
differ
in
size.
We've
been
quite
successful
in
terms
of
adding
tech,
leads
to
to
the
storage
tag,
for
example,
and
and
we
promoted,
one
of
the
tech
leads
to
a
co-chair
as
well
as
part
of
this
process
but
yeah.
Nevertheless,
for
example,
my
personal
position
is
yeah,
I'm
over
my
two-year
term.
F
So
I
would
strongly
recommend
that,
when
your
term
is
coming
up
to
an
end
identifying
someone
in
the
community
as
a
technical
lead
or
with
an
industry
that
has
an
interest
and
mentoring
them
from
a
continuity
perspective
to
showcase
to
them.
This
is
the
level
of
effort.
This
is
the
work
that's
involved.
Are
you
interested
I'd
like
to
get
you
to
a
position
to
be
able
to
do
this?
That
means
showing
up
more
to
these
meetings,
participating
and
provide
that
clear
path.
C
H
You
know
the
latter
kind
of
relies
on
our
personal
connections
or
professional
connections
that
already
exist,
and
perhaps
some
communication
at
a
slightly
higher
altitude.
You
know
kind
of
saying:
hey
opportunities
abound.
You
know
that
that
might
help
cross-pollinate
and
spread
word
more
broadly
as
a
proposal.
F
I
would
also
add
that,
while
communications
to
a
larger
audience
are
excellent,
nothing
beats
reaching
out
to
somebody
in
your
slack
channel
and
one-on-one
following
up
with
them
and
checking
in
with
them.
That
is
where
we
have
had
the
most
success
in
security
tag.
Is
that
one-on-one
engagement?
Hey,
I
see
you
joined
our
channel
here
are
some
easy
issues.
I
Yeah,
I
think,
in
terms
of
tag
runtime
I
mean
we
don't
have
a
lot
of
participation
in
in
our
meetings.
So
typically
we
have
four
and
five
and
typically
they're
different
people.
You
know
they
show
up
every
time
and
yeah
I've
been
trying
to
reach
out
some
people,
but
you
know
it's
not
that
easy
to
get
interest
on
on
that
specific
tag,
I
think
it's
just
not
the
the
more
popular
area
of
cloud
native.
I
So
that's
why
I
think
it's
also
been
kind
of
challenging.
So
besides
maybe
having
some
sort
of
ambassador
in
the
tag,
it
might
be
helpful
if
some
other
folks
within
the
toc
umbrella
or
tag
umbrella,
can
help
out.
Maybe
tag
contributor
strategy,
help
out
with
some
outreach
and
maybe
have
something
that
says
you
know.
Look
we
have
these
tags.
You
know
provide
this
participation
or
you
know,
have
some
twitter
type
of
announcement.
Like
you
know,
we
need
some
tag.
Please
participate.
J
J
The
the
other
thing,
at
least
on
the
coms
or
I'm
starting
on
on
the
comms,
like
I
I'd
say
like
six
months
to
your
term,
is
up
is
kind
of
like
the
final
point
would
be
like
okay,
I
want
to
potentially
stick
with
this
for
like
another
term
or
I
need
to
start
really
thinking
about.
You
know,
mentoring,
someone
into
to
to
take
my
spot.
J
It's
also
like
I
will
say
from
personal
experience.
It's
not
always
easy.
I
have
like
personally
mentored
a
few
people
to
trying
to
take,
like
my
spot
in
as
a
contributex
lead,
and
they
have
all
had
to
back
out
out
of
time
commitments
but
more
firmly,
defining
the
role
their
responsibilities
in
creating
additional
roles
to
sort
of
distribute
the
load
makes
it
a
lot
easier
for
people
to
potentially
you
know,
take
on
those
positions
or
give
them
stepping
stones
to
be
able
to.
You
know
eventually
go
up
to
those
positions.
G
Okay,
so
yeah,
I
do
have
one
thought
real,
quick
tim.
You
know
in
in
all
of
this
stuff
right,
it's
it's
a
little
bit
of
mentorship
as
culture
as
we
go
right.
It's
a
culture
thing
to
identify
when
somebody
shows
up
and
encourage
them
to
come
back
or
encourage
them
in
what
they're
doing.
If
somebody
volunteers
saying
you
know,
I
might
want
to
do
this,
I
haven't
done
it
before
write
down
their
name
and
figure
out.
How
do
you
help
them?
Take
a
next
step.
G
I
think
it's
it's
a
culture
thing
that
that
we
can
all
probably
learn
to
do
and
the
more
people
that
we
encourage
that
way.
They
have
a
good
environment
around
the
more
people.
They'll
tell
about
it.
The
more
people
who
can
show
up
so
that's
on
top
of
already
being
useful
but
being
an
environment
where
they
can
grow
in
learn,
skills,
engage
in
it's
about
creating
that
tone.
I
think-
and
that
doesn't
come
naturally
to
me,
and
so
I'm
sure
it
doesn't
to
others.
C
Thanks
matt,
so
I
had.
I
have
two
thoughts.
I
generally
agree
with
all
the
forward-looking
positive
set
of
things
that
we
need
to
do.
You
know,
over
a
period
of
time
to
cultivate
new
folks
for
the
short
term.
I
would
say
you
know
two
things
one
is:
there
is
a
list
of
toc
contributors
that
I'm
trying
to
redirect
to
tags.
So
let
me
think
about
it.
A
little
bit
more.
C
C
So
that
is
one
the
other
one
is
for
those
folks
whose
terms
are
almost
ending
or
already
ended.
I
think
we
should
just
renew
what
we
need
to
do.
So,
let's
follow
the
process
that
we
have
already
in
terms
of
like
notifying
the
toc
and
getting
you
know,
plus
funds
from
the
doc
members
and
such
to
at
least
get
everything
back
on
paper.
C
You
know
restart
the
terms
essentially
and
not
let
it
you
know
just
go
as
it
is
happening
right
now,
plus
one
to
a
calendar
for
sure
for
ever
yeah,
so
whether
we
want
to
maintain
it
at
the
tag
level
or
whether
we
want
to
do
it
at
the
toc
level.
I'm
open
to
suggestions
there
and
amy
can
probably
help
with
that
too.
A
G
F
F
F
F
F
F
F
F
F
I
think
overall,
the
tag
is
doing
well.
I
think
they
have
reached
a
point
where
they've
generated
a
lot
of
their
research
in
the
paper
oriented
needs
that
from
the
community,
it's
a
matter
of
updating
them
at
this
point
and
sustaining
them
with
the
exception
of
the
auditability
portion
of
the
charter.
That's
where
the
controls
group
comes
in
the
next
steps.
I
believe
that
their
group
can
be
more
largely
successful
in
is
a
lot
more
of
that
technical
implementation.
F
So
the
reference
to
architecture
partnering
with
the
foundation
to
ensure
all
cncf
projects
have
the
associated
supply
chain
mechanisms
that
they
need
to
provide
a
greater
level
of
assurance
that
our
cncf
projects
were
built
in
a
secure
fashion
and
then
being
able
to
attest
that.
So
that
is
probably
the
largest
next
leap
in
those
two
areas:
auditability
and
actual
application
of
the
recommendations
from
our
papers.
I
I
I
I
Well,
sorry,
last
week
and
finally,
ray
and
cube
ray
two
projects
that
go
together,
gray
is
a
distributed,
computing
framework
and
cube
ray
is
its
kubernetes
operator
and
they
will
have
a
presentation
on
july,
7th
and
in
terms
of
activities.
In
the
tag
our
batch
system
initiative
working
group
continues
to
meet
twice
a
month
and
they're
continuing
they're
continuing
to
iron
out
the
details
for
their
charter
and
in
terms
of
kubecon
eu.
We
had
the
attack
runtime
session.
I
I
A
H
H
H
Most
of
the
time
I
understand
was
spent
on
the
observed
k-8s
project,
which
has
been
moving
along
in
the
recent
months
and
now
has
a
fully
working
observates
demo.
That's
that
michael
hasenblast
and
henrik
rex
and
some
others
have
contributed
to
and
there's
a
link
there
for
for
details.
Obviously
our
17th
may
was
canceled
and
our
meeting
today,
which
immediately
follows
this
meeting.
H
A
E
E
E
One
of
the
participants
from
from
cisco
was
well
asking
an
old
question
about
details
of
deployment
models
and
things
around
best
practices
and
those
questions
really
fell
into,
or
they
were
in
context
of
the
service
mesh
performance.
Dashboard,
that's
coming
out
of
the
service
mesh
performance
project
and
what
tests
should
the
questions
are
like
what
tests
should
be
run?
What
scenarios
are
typical?
What's
what
are
good,
representative
workloads
and
those
types
of
questions?
E
But
but
that
was
an
update
from
from
that
project.
Since
last
we
spoke
so
just
a
a
new
index,
new
way
of
measuring
and
characterizing
the
value
of
your
cloud-native
infrastructure.
So
that's
about
it
lfx
and
gsoc.
I
think
they
they've
kicked
off.
So
there's
a
number
of
the
projects
within
within
the
tag
that
are
participating.
C
M
E
That's
a
great
question,
so
there's
being
familiar
with
a
few
of
these,
the
one
of
the
gsoc
interns
is
working
directly
on
that
service,
mesh
performance
dashboard
and
they
just
presented
this
last
thursday
their
their
update.
So
if
you
go
to
the
dashboard,
you
can
tell
it's
a
work
in
progress,
because
that's
a
good
example
in
the
past
another
had
worked
on
like
the
smi
con
smi,
conformance,
dashboard
and
kind
of
the
tooling
around
performing
that
performance.
E
E
B
B
B
Of
course,
a
big
part
of
the
goals
awareness
campaign
was
to
make
the
projects
aware
that
there
are
resources
and
help
available,
and
we've
heard
from
some
projects
since
then,
the
for
recent
activity
around
kubecon,
we're
redoing
how
we
document
the
templates
and
the
first
one
of
those
is
the
contributing
template
to
make
the
documentation
clearer
and
all
of
the
templates
are
going
to
be
redocumented.
This
way,
I
sent
an
email
to
the
toc
mailing
list
today
requesting
comment
on
a
mentoring
working
group.
B
So
please
comment
on
that
and
then
we'll
take
a
vote.
After
we're
done
commenting,
as
always,
please
encourage
projects
to
reach
out
to
our
tag
when
you
provide
feedback
and
due
diligence.
A
ts
member
recently
did
that
for
the
flux
project
and
they
came
to
us
asking
for
advice
on
writing
new
governance,
which
I
think
worked
out
for
everybody.
B
C
B
B
Yeah
that
said,
tag
contributor
strategy,
of
course,
is
looking
for
more
people
to
be
involved.
Part
of
the
idea
of
adding
new
working
groups
is
to
expand
the
number
of
activities
that
people
might
be
interested
in
participating
in
and
among
other
things,
I
have
overstayed
my
two
years
as
chair,
so
I
am
looking
for
a
replacement
chair.
N
N
Sorry,
like
like
two
weeks
before,
but
like
I
wanna,
give
an
update
on
the
just
like
what's
happening
in
last
month
that
the
projects
we
reviewed
and
the
work
we
have
done
like
first
of
all,
for
the
projects
like
there
are
a
couple
of
projects
that
presented
in
our
tech
and
also
we
sponsor
one
of
them
into
to
to
help
them
move
into
incubation,
which
is
captain
it's
in
public
voting
period.
So
please
vote
your
opinions
and
other
than
that
we
also
have
open
future
and
open
crews.
N
Trying
to
get
into
cncf
open
cruise
is
trying
to
move
to
incubation
and
open
future
is
also
being
donated
to
as
a
sandbox
project,
and
we
also
have
missed
io
just
getting
presented
as
well.
They
want
it.
So
let
me
give
a
brief
introduction.
What
each
project
does
like
captain
is
a
like:
ci,
cd,
tooling,
focus
on
security
and
and
like
yeah.
N
Workloads
like
like
just
like
deployment
but
more
advanced
and
mr
io
is-
is
very
much
like
cross
plane,
but
with
its
own
api.
So
if
you
are
interested,
you
can
join
our
tech
meeting
and
also
like
discuss
them
with
us
as
well
and
other
than
that,
like
on
the
working
group
side,
we
have
three
updates.
So,
first
of
all,
we
we
have.
The
cooperative
delivery.
Working
group
have
finished.
The
edward
had
finished
the
evergreen
charter
in
this
in
the
slice
dock.
N
Actually
you
you
need
to
get
in,
get
the
slides
and
and
put
get
the
and
click
the
link,
but
actually
those
things
are
available
in
our
our
meeting
meeting,
like
notes
as
well.
So
so
you
can
definitely
find
them
in
there
as
well
so
and
other
than
that,
like
we
also
have
are
planning
a
operator
white
paper
version.
N
Two
previously
we
have
published
version,
one
operator
white
paper,
but
like
so
much
things
have
been,
have
been
changing
since
then,
like,
for
example,
there
are
nutrients
like
multi-cluster
and
solubility
and
git
obstacles,
kind
of
thing
be
in
added
to
operators.
So
we
are
trying
to
add
those
things
and
and
just
refresh
what
operator
does
and
that's
what
we
have
stopped
drafting
a
new
doc
for
that
and
we
are
also
and-
and
we
also
like
planning
a
multi-tenancy
white
paper.
N
Currently,
we
are
gathering
people
to
discuss
what
what
does
multi-tenancy
means
and
what
what
problems
it
solves,
because
it's
so
important
like
there
are
so
many
people
just
providing
a
kubernetes
cluster
on
top
of
one
apparent
kubernetes
cluster.
But
this
is
a
very
common
pattern
we
want
to
collect.
We
want
to
build
collective
intelligence
and
and
just
share
our
knowledge
on
that
and
build
best
practices
and
for
the
upcoming
meetings
we
also
have.
We
have
some
projects
going
to
present
as
well.
One
is
one
of
them
is
rupex.
N
L
A
Thank
you
f,
delivery,
all
right,
we're
coming
in
fine
on
time.
Assuming
this
moves
come
on
no
too
fast.
We
have
our
projects
to
be
able
to
review
and
not
sure
why
it's
holding
on
us,
but
I
kind
of
want
to
be
able
to
do
a
rundown
here
of
things
that
are
currently
in
voting
which
we
can
see,
but
I
know
that
we
have
a
lot
of
projects
currently
sitting
out
there,
so
I'm
going
to
pass
towards
we'll
start
at
the
top
cloud
custodian.
L
A
L
A
A
F
A
C
C
C
C
You
know
the
steps
are
detailed
in
the
email,
but
I'm
just
voicing
here
that
there
is
a
effort
in
progress
and
we
had
a
couple
of
discussions
during
kubecon
as
well,
and
if
anybody
is
interested,
we
can
update
you
on
what
has
happened
so
far
and
where
we
are
headed
and
things
like
that
too,
on
a
separate
call
or
you
know
we
can
do
it
one-on-one
or
in
a
group
setting
as
well.
So
if
you're
interested
in
this
topic,
please
step
up-
and
you
know,
help
any
questions
here,.
C
Okay,
I
think
once
going
twice
that
was
easy,
so
essentially,
this
is
a
collaboration
between
cnc
of
gb
and
the
cncftoc,
because
both
of
us
have
to
sign
off
on
how
this
is
going
to
work,
and
this
is
the
first
time
we
are
trying
to
do
this
in
public.
Usually
it
doesn't
happen,
so
that
is
a
very
good
sign
of
you
know
how
we
are
trying
to
do
this.
That's
all
I
had
thank
you.
A
I
C
It
hasn't
been
finalized,
yet
the
first
step
is
to
identify
the
people
who
will
be
working
on
this,
and
then
you
know,
hopefully
we'll
follow
a
community
process
similar
to
what
we
do
elsewhere.
Where
people
will,
you
know
swarm
on
a
doodle
or
something
like
that
to
figure
out
what
times
will
work
and
what
cadence
will
work?
You
know
they
can
decide
on
the
in
their
first
meeting.
C
O
O
C
The
sustainability
right,
yep,
okay,
so
the
the
typical
question
I
ask
here
is
like
not
being
a
tag.
Is
it
affecting
their
day-to-day
work
right
now?
If
not,
you
know,
I
would
say
you
know,
get
some
some
initial
wins
under
your
belt
and
then
come
up
with
things
that
you
can't
do
right
now,
because
you're,
a
working
group
versus
a
tag
and
being
revisited
and.
O
O
So
I
agree
and
it's
kind
of
one
of
those
things
like
security.
I
think
you
can
agree
where
it's
in
every
little
part
emily
it's
not
able
to
operate
in
a
silo,
and
I
think
that's
why
they
were
looking
the
formalization.
But
I
think
it's
completely
fair
to
say
you
know,
as
many
of
these
started
from
a
white
paper
framing.
What
does
that
mean
the
size
and
the
scope
and
moving
it
more
into?
You
know
a
formal
tag
of
executing
and
interacting
with
these
different
ones.
So
I'm
I'm
fine.