►
From YouTube: CNCF TOC Meeting 2021-02-15
Description
CNCF TOC Meeting 2021-02-15
A
A
A
A
D
A
That's
fine.
I
mean
like
this
was
in
fact
like
a
couple
years
ago,
and
a
lot
has
happened
since
then.
So
I
understand
yeah,
okay,
andrew's
also
here
from
the
spiffy
spire
like
folks,
yeah
and
andres.
Let
me
know
that
he's
running
a
little
bit
late
this
morning
so,
but
that
that
is
actually
good
to
remember.
As
far
as
like
yeah
no
justin
justin
cormac,
we
might
actually
like
call
on
you
more
directly.
A
All
right,
I'm
gonna,
actually
move
us
over
towards
the
projects
that
are
currently
in,
like
you
know,
as
things
are
moving
around
but
welcome
you
have
made
it.
This
is
our
normal
anti-trust
policy
notice.
This
is
our
normal
meeting
logistics
pieces
because
you
are
here.
You
have
made
it
to
the
particular
meeting.
Well
done.
A
Our
toc
members
are
currently
tracked
up
here
and
in
fact
we
do
have
quorum
today.
If
we
wanted
to
be
able
to
do
something,
but
it's
so
much
better
to
do
it
by
email.
So
please
don't
this
is
our
agenda
and
I'm
going
to
move
us
towards
the
projects
applying
the
move
levels
first
in
here
for
general
updates
general
comments.
Anything
else
running
around
and
justin
cormack,
I
will
pass
to
you
and
toto,
is
currently
in
voting.
E
So
so
we
have
finished
the
did
you
delegate
dog
for
tribal
fs.
I
failed
over
all
that
project
already,
so
I
will
send
out
all
the
materials
I
have,
oh,
including
the
end
user
interview,
of
course,
so
I
will
send
all
the
material
in
the
stack
channel
to
let
all
everybody
to
take
a
look.
If
we
feel
it's
great
and
then
I
feel
it's
safe,
we
actually
to
put
turbo
face
for
public
common
period.
So
this
is
a
current
status.
We're
very
promising
here.
A
A
A
D
A
E
B
Nothing
more
than
that,
so
we
were
working
with
them
on
their
security
posture
trying
to
get
them
to
write
things
down.
You
know,
enhance
their
processes
a
little
bit
and
ensure,
like
whatever
they
are
doing,
is
like
visible,
documented
and
so
people
can
go.
Take
a
look
and
feel
better
that
you
know
things
are
going
on
fine
and
if
there
is
a
something
that's
getting
get
gets
reported,
then
it
gets
worked
on
and
things
like
that.
A
Nope
that
that
sounds
like
it
is
all
reasonable
things.
So
all
right,
I'm
gonna,
move
us
back
over
towards
our
graduation
proposal
for
spiffy's
fire,
because
I
think
we've
got
all
of
that
team
on
the
phone.
Unless
anybody
had
any
questions,
I
didn't
see
anything
in
chat.
I
saw
a
note
around
like
custodian
status,
like
things
are
moving
hooray.
G
G
G
G
The
end
user
community
has
also
well
quite
an
uptick
in
the
end.
Well,
everything
we
do
is
in
service
of
making
organizations
more
secure.
So
that's
been
really
rewarding
and
fascinating
to
see
since
incubating
we,
we
also
transitioned
what
was
originally
the
spiffy
days,
our
our
gathering
and
hangout
into
a
collocated
event
that
kubecon
that
has
been
successful
by
many
measures.
It's
been
very
well
attended.
G
There's
been
great
participation
again
from
end
users,
speaking
about
their
usage
and
scenarios
and
outcomes
that
spit
the
inspire,
have
enabled
for
them
so
yeah.
I
I
think,
judging
from
our
own
evaluation
of
of
the
rubric
for
graduation,
we
we're
there.
We
think
we
meet
or
exceed
all
all
the
categories
we
since,
since
incubation
justin
cormack,
thank
you
for
graciously
leading
the
duel.
Diligence
for
us.
We
went
and
conducted
a
third
party
audit.
G
We
acted
upon
the
findings
of
that
audit
and
we
made
the
project
even
more
watertight
than
it
was.
We
have
written
book
that
gathered
members
from
the
community
at
large.
Thank
you,
emily
fox.
Congratulations
on
on
setting
now
the
talk
you
participated
in
the
book.
You
were
tremendous
contributor
to
it.
It's
called
solving
the
bottom
turtle.
You'll
find
the
link
in
the
incubation
proposal.
Sorry
in
the
graduation
proposal.
G
So
yes,
it's
it's
just
been
like
proliferating
and
growing.
We
expect
to
continue
to
grow,
that's
well
an
importance
of
being
a
cncf
project,
and
with
that
I
well
we
have
the
rest
of
the
steering
committee
members
here.
I
don't
know
if
anyone
wants
to
add
on
anything
to
that,
but
pass
it
on
to
the
talk
thanks,
tim's
hearts
too,
and
thanks
justin
for
the
link
to
the
book.
A
E
C
Yeah,
I
I
remember
I
remember
going
to
I
think
one
of
the
first
public
spiffy
meeting
at
cubecon
and
I
don't
know
tech
austin,
maybe
in
a
in
a
bar
with
with
carrick
with
powerpoint
karaoke,
and
I
think
it's
it's.
It's
come
a
really
long
way
since
then
and
yeah.
I
think
it's
really
interesting
how
it's
built
a
community
through
very
different
governance
structures,
very
different
people.
C
D
C
Unclear
then,
but
I
think
that
really
the
the
project's
showing
that
they
can
work
across
the
you
know
across
security.
You
know,
with
security
people
across
all
sorts
of
different
things.
I
think
that
the
book
has
been
really
helpful
for
helping
people
understand
the
shape
of
the
problem
they're
trying
to
address,
and
what
the
and
these
kind
of
these
kind
of
bootstrapping
problems
and
identity
problems
are
really
hard
to
help.
People
understand,
and
I
think
those
kinds
of
that
kind
of
thing
has
been
incredibly
helpful
in
in
helping
people
discuss.
C
You
know,
discuss
these
kinds
of
security
problems
in
the
community,
and,
and
so
I
think
that
that
kind
of
educational
material
is
a
real
lesson
to
other
projects.
That
is
it's
fun
to
do,
and
I
was
amazed
by
the
way
they
did
that
book
in
was
it
two
weeks
as
an
immersive
sprint
based
process,
which
was
really
interesting,
and
it
worked
really
well.
So
I
think
that
yeah,
it's
been.
It's
been
kind
of
really
interesting
watching
this
watching
this
journey.
G
G
So
yeah,
I
think,
thinking
outside
the
box.
Well,
the
book
is
one
of
many
examples
of
well
bringing
plural
views
and
thinking
outside
of
the
box.
Let's
try
different
things.
Let's
pull
pull
folks
in
and
let's
cater
to
the
different
ways
that
people
consume
content,
pay
attention,
learn
about
things.
G
B
C
Just
dems
we
have
had
other
projects
do
that
we've
actually
asked
for
it
at
various
times,
because
sometimes
it's
been
unclear
to
people
particularly
around
graduation,
which
parts
of
the
project
they
should
consider
production
ready
when
there
are
some
projects
that
are
clearly
not
so
you
know
it's
all
very
experimental.
So
it's
not
unprecedented
yeah.
G
G
We
also
maintain
a
a
number
of
language
bindings.
We
have
go
spiffy
java,
spiffy.
There
are
a
few
others
since
incubation.
We
also
folks
have
an
interest
in
building
systems
on
top
of
spire,
have
a
spire
federation
controller
for
multiple
trust
domains.
Brandon
lum
and
marius
from
ibm
started
that
project,
and
it
was
all
at
a
time
that
we
were
dealing
with
growing
pains.
Our
the
bandwidth
of
attention
of
our
maintainers
was
pegging.
G
We
were,
we
were
treading
water
and
we
had
kind
of
had
this
official
projects
and
we
tried
to
take
care
with
people
building
things
around
us
best
effort,
but
we
were
doing
a
great
service,
so
rescinding
a
little
bit
control,
but
like
stipulating
a
framework
for
people
to
be
able
to
develop
these
things
on
their
own
as
long
as
there's
proper
representation
of
well,
is
this
fully
supported
by
the
project?
Officially
or
well?
It's
nascent
effort,
and
it's
somewhat
experimental,
so
that
is
part
of
the
motivation
there.
G
B
G
G
I
think
it's
very
important
as
a
core
infrastructure
project
that
people
are
considering
trustworthy,
that
no
one
running
spy
in
production
experiences
an
outage
because
of
spire,
so
reliability,
stability,
making
sure
that
the
project
is
watertight
is
going
to
continue
to
be
a
priority
for
the
project
and
number
two.
It's
growing
integrations
ensuring
that
the
top
50
or
top-n
open
source
projects,
support
native
spiffy
authentication
and
that
we
start
bridging
and
de-balconizing
pockets
of
infrastructure
that
are
fragmented.
H
Muted
again,
I
double
beautify
there.
Folks,
I'm
gonna,
look
at
this
camera
too.
That's
probably
better.
I
think
andrew's
gave
a
great
summary.
I
don't
have
a
ton
to
add
to
it.
You
know
the
project.
You
know
we've
tried
to
keep
the
the
the
core,
the
core
problem
that
we're
trying
to
solve.
You
know
well-bounded
and
well-scoped,
so
there
certainly
will
be.
You
know,
as
always,
ongoing
efforts
on
on
stability
and
maintainability
and
and
ease
of
integration
in
terms
of
growth
going
forward.
H
You
know,
as
andreas
mentioned,
we'd
love
to
see
more
richer
upstream
integrations
native
integrations
into
things
like
say,
secrets,
managers,
identity
management,
platforms
and
so
forth,
and
you
know
a
lot
of
that.
You
you
see
captured
in
the
you
know,
early
incubating
projects.
You
know
within
the
within
the
spiffy
ecosystem
itself,
and
then
you
know,
I
think
your
success
for
us.
You
know
in
the
next
say
five
years
would
be
to
see
more
of
the
industry
align
around
the
spiffy
apis
to
align
around.
H
You
know
particular
things
like
the
workload
federation
api
to
allow,
as
andres
mentioned,
you
know,
kind
of
debulkinization
of
workload,
identity
and
decide
to
have
greater
interoperability
between
your
different
platforms
and
solution
sets.
So
we
think
you
know
that
graduation
will
will
facilitate
the
momentum
that
we
already
have
there.
G
G
I
Is
it
has
a
lot
of
potential
different
use
cases.
So
I'm
really
proud
of
the
work
that
the
team
has
done
and
both
their
embodiment
of
security
from
that
perspective,
but
as
well
as
their
commitment
to
diversity
and
inclusion
within
the
community
and
the
thoughtfulness
and
the
language
selection
that
they've
been
using
throughout
their
progression
from
the
security
assessment.
When
I
first
engaged
all
the
way
to
today,.
J
I
I
will
pitch
really
really
quickly
in
a
couple
of
minutes
and
I
I
think
it's
an
awesome
project
and
I'm
only
jumping
in
because,
because
things
asked,
I
think
it's
a
really
good
project.
I
will
say
I
have
personally-
and
this
is
just
personal,
so
it's
anecdotal,
I
haven't
seen
it
being
used
a
huge
amount
amongst
the
end
users
that
I've
spoken
with.
That's
just
anecdote
and
I
haven't
gone
out
to
look
for
it.
So
that's
my
only
kind
of
anecdote
to
add,
but
I
do
think
it's
a
really
solid
project.
A
G
Just
the
last
mile
from
like,
where
we
reach
at
and
parsekis,
is
a
great
example
of
expanding
and
extending
like
well
a
wire
protocol
and
abstraction
to
hardware
devices,
and
it
was
a
sign
up
like
incorporating
spiffy
and
that's
been
really
really
encouraging.
Well,
knowing
that
we're
directionally
correct
and
that
we
paid
enough
attention
for
people
to
seamlessly
integrate
and
extend
this
this
interfaces
and
like
tackle
the
problem
at
like
different
problems,
specific
to
particular
industries.
This
would
be
edge
and
iot,
which
is
some
of
the
key
use
cases
of
parsic.
B
A
G
A
I
mean
yes,
I
would
be
highly
in
favor
of
that
in
large
part,
because
we've
got
kind
of
new
folks
on
like
toc
and
being
able
to
help
them
kind
of
walk
through
processing
here
separately.
That
also
means,
if
somebody
gets
overwhelmed
or
busy,
then
like
there's
somebody
else
be
able
to
plumb
across
the
line,
so
yeah
fun
being
able
to
have
like
pairs
on
this
one.
C
A
K
A
G
Yeah
on
on
process:
well,
we
we
have
collected
well,
we
have
collated
a
number
of
like
public
case
studies
and
public
adopters.
I
know
the
process
entails
conducting
private
interviews.
Do
you
need
us
to
wire
up
those
conversations
for
you
or
like?
Do
you
reach
out
directly
to
these
organizations
back
channel
and
do
the
interview?
How
does
this
work.
C
A
G
C
A
A
Okay,
when
I
see
that
particular
proposal
come
through,
I
will
put
it
on
the
schedules
like
we're
kind
of
backed
up
on
things
for
a
bit
like.
I
can't
see
that
actually
coming
up
before
like
this
time
next
month,
and
our
next
sandbox
review
is
also
an
annual
review
meeting
as
well.
So
we
should
probably
look
towards
like
how
we're
going
to
deal
with
all
of
that.
Just
procedural
notes
so,
and
also
like
upcoming
things,
hooray,
there's
going
to
be
a
sandbox
meeting
review
ray.
A
Happens
today
today,
at
noon,
pacific
time
that
closes
hold
on
I've
even
gotten
this
written
down
the
next
piece
around
that
one
is
going
to
be
closing
nominations
close
on
february
22nd,
that's
toc,
nomination,
you're
going
to
get
a
form
at
about
noon.
Today,
february
22nd,
through
march
8th
we've
got
that
two-week
qualification
period
where
both
the
toc
and
the
governing
board
vote
we'll
do
a
very
short
election
from
march.