►
From YouTube: CNCF TOC Meeting 2022-09-06
Description
CNCF TOC Meeting 2022-09-06
A
C
C
There
have
been
some
really
good
updates
from
the
maintainers
and
they're
and
we're
we're
expecting
further
updates
in
a
couple
of
weeks.
So
I
think
I
think
we
should
be
able
to
make
a
more
detailed
since
early
october
the
curve
storage
system
have
had
presented.
We
recommend
sandbox
and
the
curve
team
we're
going
to
reapply
for
that,
and
we
also
had
a
presentation
from
the
carina
project,
which
is
which
is
a
csi
driver
with
with
the
ability
to
provision
local
disks
via
lvm,
which
is
which
is
kind
of
interesting.
C
C
We
have
some.
We
have
some
ongoing
ongoing
discussions
around
the
performance
and
benchmarking
white
paper
which
we're
hoping
to
tidy
up
before
the
kubecon
timeline,
and
I
did
have
maybe
an
open
question
around
the
cloud
native
disaster
recovery.
So
we
had
a.
We
had
a
few
discussions
around
this.
We,
the
paper
is
finalized
and
we've
published
it
and
we
released
it
at
the
previous
coupon,
etc.
C
But
we
were
wondering
if
we,
if
it
would
be
a
good
idea
to
go
through
some
sort
of
formalization
by
the
toc
and
and
have
it
published
as
a
as
a
as
a
as
a
more
formal
cncf
white
paper.
If,
if
that
is
appropriate-
and
I
was
kind
of
wondering
what's
the
what
the
process
would
be
for
that,
I
know
I
know
the.
C
A
B
C
Thank
you,
fantastic
all,
righty,
then,
and
then
finally,
we've
had
some
interesting
updates
from
a
number
of
the
different
projects,
including
vitesse
at
cd,
and
we
also
had
an
update
from
longhorn
the
week.
A
couple
of
weeks
back
and
coming
up.
We've
got
rook
at
our
next
tag
meeting
and
we're
also
trying
to
do
a
presentation
from
an
update
on
cloud
native
postgres
operator,
which
is
which
is
from
the
edb
team,
so
yeah,
those
those
are
the
things
we're
working
on
next.
B
C
I
think
it
was
definitely
very
useful.
We
we've
had
we've
had
discussions
with
the
project
team
and
we
also
had
a
session
with
tag
and
the
toc
sponsors,
but
having
the
the
toc
issue,
I
think
really
helped
galvanize
and
formalize
the
the
response
site.
So
I
think
that
that
is
actually
a
much
better
way
of
doing
it.
B
Thank
you
and
on
the
curve
and
karina,
I
think
the
thing
that
we
were
thinking
about
was
hey.
Is
it
just
a
csi
or
does
it
have
a
larger
set
of
tools
and
things
like
that
around
it
framework
and
and
things
around
it
or
is
it
just
a
csi
like?
I
think
that
was
one
of
the
questions
that
we
were
having
when
we
were
looking
at
both.
C
So
so
curve
is
curve
is
a
fully
fledged
storage
system.
There
are
a
lot
of.
There
are
a
number
of
sort
of
rough
edges
and
it's
coming
up
to
speeds,
but
that's
why
we
recommended
sandbox,
but
it's
it's
it's
not
just
the
csi
karina
is,
is
a
system
to
allow
the
configuration
of
look
disks
within
within
a
kubernetes
cluster,
so
it
is
a
useful
tool.
C
A
B
E
Hello-
I
am
indeed
hi
andy.
Please
take
it
righto,
so
we
have
two
new
incoming
efforts
in
security
tag.
One
is
a
lightweight
threat,
modeling
guidance.
The
aim
here
is
to
provide
a
loose
but
guard
guardrails
type
frame
framework
for
which
to
try
and
move
more
quickly
through
threat,
modelling
and
cncf
project
as
it
comes
into
the
tag
so
far.
This
has
just
been
appraising
and
looking
at
things
that
trail
of
bits
deliver
kubernetes
various
other
different
mechanisms.
E
Instead
of
working
on
the
sort
of
contention
of
a
hypothesis
of
what
people
need
and
the
cloud
native
security
controls
mapping
to
nist.
It
is
pretty
much
what
it
says
on
the
tin.
We
have
a
set
of
recommendations
that
we
generated
and
we're
looking
to
ensure
that
they
line
up
with
nist,
and
then
we
have
had
a
couple
of
presentations
come
through
recently.
E
B
E
D
B
D
It's
more
of
a
checklist.
I
believe
the
group
had
plans
at
a
much
later
date
to
try
to
automate
some
of
the
checks
and
validation
mechanisms
of
the
recommendations
from
the
paper.
But
providing
this
initial
mapping
to
nist
will
be
a
huge
benefit
for
a
lot
of
organizations
that
leverage
this
for
auditing
purposes.
B
E
B
E
No,
all
that
is,
although
that
is
a
matter
of
interest
for
us.
We
noted
that
the
openstaff
have
produced
recently
a
supply
chain
security
survey
of
their
own,
we're
not
quite
at
the
same
at
the
same
level,
because
we're
focused
more
deeply
on
the
cncf
pieces
there,
but
there
are
also
some
ongoing
discussions
as
to
how
we
can
collaborate
best
with
vfs,
sir.
E
F
F
F
So
it
manages
the
policies
just
like
docker
docker
does,
with
container
images
and
in
terms
of
activities
with
the
tag
we
have
the
batch
system
initiative,
working
group
creation
and
that's
in
the
public
comment
period
that
is
ending
this
week
and
if
everything
goes
as
planned,
we'll
have
a
vote
for
that.
So
hopefully
we
can
get
that
created
in
the
next
couple
of
weeks
and
we're
also
planning
a
kubecon
north
america.
It
says
eu
and
the
presentations
there's
a
typo,
so
we
are
planning
a
run
attack
runtime
session.
A
B
G
So
I
guess
I'll
start
with
the
the
most
impactful
one.
We
have
a
new
logo,
so
thank
you
to
the
a
very
long
delayed.
Thank
you
to
the
art
artists
at
the
cncf
that
came
up
with
a
bunch
of
animal
logos.
I
think
in
the
future
in
the
next
month,
or
so.
If
we
get
to
it,
we'll
have
a
blog
post
on.
Why
owls,
but
there's
a
lot
of
cool
things
about
owls
as
an
animal
that
overlap
with
observability.
It
sounds
contrived,
but
it's
not
I
promise.
G
Next,
there
was
a
toc
asked
to
help
assess
the
health
of
the
cortex
project.
I've
just
recently
updated
that
issue
with
some
of
the
things
that
alolita
and
I
kind
of
brainstormed
around
last
week.
I
won't
go
through
all
of
it
here,
but
in
short,
there's
a
number
of
adopters
listed
in
the
cortex
repo
I've
listed
them
there,
so
we're
suggesting
and
recommending
that
you
know
each
of
them
is
contacted
to
see
what
their
position
is
on
the
cortex
project.
Are
they
still
an
adopter?
G
Are
they
still
running
it
if
they're
not
and
they've
gone
to
a
mirror?
What
were
the
things
that
drove
that
consideration
and
or
you
know
what
what
would
they
need
to
continue
using
the
cortex
project?
You
know
this
is
stemming
out
of
overall
concerns
around
the
longevity
of
it.
The
abandonment
of
the
project
by
its
maintainers,
shortly
after
it
achieved
incubation
status
and
then
started
to
get
some
critical
mass
and
the
lack
of
ability
or
the
potential
lack
of
ability
for
customers
to
have
vendor-supported
cortex.
G
You
know
enterprise
grade
support,
we're
suggesting
that,
and
we
need
to
confirm
some
of
this
with
the
with
the
existing
project.
Maintainers,
that
you
know
there
could
be
some
logistical
assistance,
that's
needed
to
to
help
with
community
development
and
the
project
itself
and
some
other
potential
needs
that
are
there.
G
I
guess
what
we're
asking
from
the
tlc
here
is,
you
know,
should
we
ask
you
guys
or
we'd
like
to
ask
the
folks
on
the
tsu
that
have
connections
to
some
of
these
companies
professionally
or
otherwise,
if
there's
some
avenue
to
kind
of
have
the
the
toc
or
it's
or
us,
reach
out
to
these
people
the
right
way
without
it
being
ad
hoc?
So
so
that's
one
place
that
we
could
use
a
bit
of
guidance.
B
Let's
talk
about
this
a
little
bit,
so
what
I
would
suggest
is
we
can
you
know
we
with
alolita
and
you
kind
of
like
taking
a
lead
on
a
google
doc.
We
can
draft
an
email
out
to
possibly
the
gb
folks,
let's
target
it
at
the
gb
folks
and
let's
come
up
with
a
text,
and
you
know
three,
four
of
us:
if
we
can,
you
know,
write
draft
the
letter,
then
we
can
send
it
to
them
to
see
if
anybody
bites
right.
G
B
G
G
It
also
has
the
support
of
tc
members
for
most
hotels.
So
so
you
know
this
has
been
a
nuanced
effort.
That's
been,
I
would
say,
slow
moving,
but
moving
slowly
enough,
so
that
we
can
get
sufficient
critical
mass
from
from
folks
that
are
that
are
interested
that
can
help
private,
so
yeah.
It's
a
I'm
optimistic
about
its
future.
G
The
supply
chain
working
group
out
of
stag
is
undertaking
some
of
that
and
has
a
similar
graph
based
project
underway
that
we're
that
we're
chatting
about
so
so
there's
some
overlap
there
and
a
potential
collaboration
details
are
at
the
links
and
then
lastly,
we
had
an
lfx
internship
approved.
It's
a
joint
between
internship,
I'm
one
of
the
mentors,
as
is
lee
from
tag
network,
and
it's
really
look
it's
looking
at
incubating
and
developing
and
on
an
ontology
for
kubernetes
resources.
G
That
has
a
lot
of
a
lot
of
different
applications
for
observability
and
and
tools
that
can
help
us
kind
of
understand
what
we've
created
and
how
to
observe
them.
So
we're
pretty
excited
about
it.
It
just
launched
yesterday
and
we
have
an
intern.
That's
been
working
with
layer,
five
for
some
time
and
she's
awesome
and
gonna
start
soon
too,
has
to
do
with
shackle,
owl
and
some
of
the
other,
some
of
the
other
acronym
soup
that
I've
put
there.
B
G
B
H
Hey
everybody,
so
our
big,
our
big
announcement
for
this
month,
has
been
our
website
redesign.
So
this
has
been
a
lot
of
work
for
books
like
carolyn
vince,
like
along
with
some
people
at
the
the
cncf
to
bring
the
contributor
site
in
line
with
kind
of
the
broader
cncf
website
website
design.
So
if
you
haven't
looked
at
it
recently,
have
a
look,
it
looks.
It
looks
really
fabulous
another
another
bit
of
big
news,
so
we
have
proposed
an
additional
co-chair,
so
catherine
paganini.
H
So
if
you
have
not
already
voted
on
that,
please
do
catherine
has
been
an
active
participant
in
the
tag
for
a
year
and
a
half
or
so
she's
authored
some
resources
and
she's
been
doing
a
bunch
of
our
tag
outreach,
and
so
we
think
that
she's,
an
excellent
excellent
counterpoint
to
the
skills
that
that
josh
and
I
have
as
as
co-chairs,
and
so
we
think
that
she
brings
kind
of
a
nice
balance
to
the
tag.
So,
if
you
haven't
already
voted,
please
do
on
the
contributor
growth
side.
H
We
have
a
few
things
that
have
been
going
on
so
noah
abrams
from
the
kubernetes
project
has
been
working
on
a
non-code
contributor
guide,
with
the
idea
that
you
know
they're,
revamping
and
expanding
this
guide,
and
the
idea
is
to
take
it
beyond
just
kubernetes
and
make
it
applicable
to
lots
of
other
cncf
projects.
So
he's
been
working
on
this
both
within
the
kubernetes
project
and
then
he's
also
been
bringing
it
into
the
into
the
tag.
H
We
also
have
a
few
folks,
like
carolyn
vince,
like
and
hippie
hacker,
who
have
been
working
on
community
infrastructure,
with
the
idea
that
we
can
use
github
actions
for
some
lightweight
prowl-like
functionality.
So
you
can
slash,
approve
lgtm
without
installing
all
that
is
prowl,
which
is
a
bit
of
a
beast.
So
we
think
we
can
do
a
lot
of
this
with
github
actions.
H
So
we
have
a
little
team
spun
up
who
are
who
are
working
on
that
and
it's
looking
looking
really
promising
with
the
idea
that
then
we
can
help
other
projects
within
the
cncf
use
this
these
github
actions
as
some
proud
like
functionality,
we
are
also
working
with
cnc
apps.
So
this
is
something
that
catherine
has
been
driving.
Is
a
contributor
survey,
so
one
of
the
things
that
we
realized.
H
So
we're
hoping
that
this
will
give
us
some
ideas
for
for
other
challenges
and
other
things
that
we
can.
We
can
help
with
as
a
tag
the
mentoring
working
group
is
off
to
an
excellent
start.
They
were
recently
approved
and
they've
kicked
off
their
meetings.
We've.
You
know,
they've
started
running
running
some
programs
and
the
the
new
zealand
team.
This
has
been
led
a
lot
by
jay
talhema
and
he's
been
participating
in
canvas
expo
on
diversity
and
tech.
H
So
the
idea
is
to
get
more
women
working
in
working
in
technology
and
getting
them
contributing
to
open
source
projects
through
things
like
the
cncf
mentorship
program.
So
that's
that's
a
really
interesting
project.
That's
you
know
coming
out
of
new
zealand
with
the
idea
that
we
can
then
replicate
that
other
places
within
the
governance
working
group
we've
been
continuing
our
mission
to
help
cncf
projects
improve
their
governance.
So
recently
we
assisted
both
the
operator
framework
and
the
falco
project
and
updating
their
governance
models.
So
we
think
that's
been.
H
We
hope
that
that's
been
a
helpful
use
of
our
use
of
our
time
within
the
tag
and
then
just
our
regular
reminder
that
as
you're
talking
to
projects
as
you're
reviewing
proposals,
annual
reports
and
things
and
when
you
provide
feedback
to
projects
about
needing
to
improve
governance
or
grow,
the
contributor
base
reach
out
to
us
or
have
the
project
reach
out
to
us.
We're
we're
happy
to
help.
H
B
H
Yeah,
we
have
a
few
things
going
on
there,
so
our
our
update
in
the
maintainers
track
is
going
to
be
around
mentoring.
Since
that's
our
newest
working
group-
and
we
haven't
talked
about
that
recently
at
a
kubecon,
so
we'll
have
that
maintainer
track
session
on
mentoring.
We
also
have
a
project
kiosk,
so
we'll
be
staffing
it,
I
believe,
in
the
mornings
for
for
half
the
day.
So
that's
where
people
can
come
come
talk
to
us
tech,
contributor
strategy
and
we
can
answer
their
questions
and
and
help
them
out.
F
H
Yeah,
I
would
say,
if
you're
interested
in
making
it
happen,
reach
out
to
us
in
the
tag
contributor
strategy
slack
channel-
that's
probably
the
best
way
to
get
a
hold
of
us.
The
short
answer
to
that
is
that,
right
now
this
is
not
quite
ready
to
use.
I
think
we're
gonna
pilot
it
within
tag
contributor
strategy,
so
that
we
can
we
can
use
it
find
out
what
what's
working
well,
what's
not
before
we
roll
it
out
too
broadly,
but
they
are
definitely
looking
looking
for
help.
I
I
So
I
think
there's
a
voting
progress,
so
if
you
can
take
a
look,
would
be
great,
he's
been
doing
a
lot
of
work
and
other
content
like
blog
posts
and
engaging
really
well
the
like
comparative
working
group
and
our
multi-tenancy
chats
upcoming.
Now
it's
on
kubecon.
We
have
a
booth
and
also
a
project
presentation.
I
I
We
are
getting
the
agenda
ready
and
going
to
post
on
our
blog
by
next
week.
It's
going
to
include
our
like
an
overall
update,
some
end
user
use
cases
and
also
talk
about
the
operator
white
paper
version
two
and
multi-tenancy
too,
and
the
call
for
people
to
come
to
our
booth
for
projects
that
are
and
want
advice
on
sandbox
preparations
like
sorry
applications
and
also
get
presentations
from
sandbox
projects
for
people
to
be
able
to
come
and
and
have
like
a
like
an
overview
of.
I
What's
going
on
now
we
are.
We
are
arranging
that
so
by
the
next
meeting.
We
will
have
some
a
page
to
share
with
you
yeah,
and
we
will
be
on
the
on
the
booth
ready
to
help
people
giving
feedback
and
also
q
a
from
some
working
group
people
we
are
checking
who
is
going
to
be
attending,
but
cooperative
delivery
and
multi-tenancy.
E
B
D
So
because
kubecon
is
usually
an
event
where
a
lot
of
folks
are
talking
a
lot
of
the
same
leadership
folks
and
primary
contributors
to
projects.
We
wanted
to
ensure
that
everybody
had
enough
time
to
present
or
to
prepare
their
presentations
for
kubecon,
including
any
toc
members
that
are
involved
in
any
ongoing
reviews,
so
we're
trying,
for
the
first
time
a
freeze
on
graduations
for
six
weeks
prior
to
the
conference
ending
shortly
after
the
conference.
A
The
one
that's
in
flight
right
now
isn't
quite
ready,
yet
we're
holding
with
the
ones
in
voting
and
because
we're
all
here
on
a
recorded
call
that
one
has
passed
the
vote.
We
are
just
trying
to
be
able
to
get
all
of
the
pieces
together.
Spiffy
spire
has
passed
the
vote.
It
is
just
we're
waiting
to
announce
to
be
able
to
get
everything
together,
so
yeah.
D
So
we
want
to
ensure
that
everybody
is
having
time
to
perform
the
proper
level
of
due
diligence
on
these
projects
and
provide
the
appropriate
level
of
the
input
that
they
are
wanting
and
not
missing,
because
they
are
focused
on
their
presentations
for
kubecon
or
other
activities.
Dims
did
I
miss
anything
else.
B
You
know
please
surface
them
up.
Let's
try
to
work
on
it
together.
I
know
that
we
have
some
things
in
progress,
so
yeah
see
the
cncftoc
issues
and
you
will
see
some
of
those
some
of
the
older
issues
that
we
were
talking
about
like
hey.
How
do
we
do
better
when
sandbox
projects
ask
for
what
do
they
need
to
do
to?