►
From YouTube: CNCF TOC Meeting 2020-04-07
Description
CNCF TOC Meeting 2020--04-07
A
B
C
G
H
A
A
J
K
D
Artifact
happens
how
you
want
to
work
with
it.
The
hard
work
ready
wasted,
one
this
is
just
ongoing.
It
has
been
most
of
the
hard
work
has
been
done.
We
have
answered
most
of
the
questions.
Is
it
just
with
us
right
now
to
just
provide
a
final
we
of
this,
but
we're
not
expecting
any
bigger
v2
from
from
the
activity
site
on
our
pool
here
on
the
aircraft
working
group
so
frozen
I?
D
Don't
know
what
we
have
in
doing
so
we
have
split
up
the
work
indie
into
individual
working
groups
that
came
out
of
this
enough
people
driving
it.
The
first
one
was
the
aircraft
working
group.
So
this
is
everything
we
need
this
obviously
running
in
restricted
environments.
Here
there
is
the
first
work
really
impressed
practices
for
installations
on
aircraft
in
the
world.
What
is
already
available
and
developing
best
practices
on
top
of
it
right
now
again,
focus
is
kubernetes
per
se.
D
D
D
Work
that's
going
on
there.
The
second
one
is
the
operator
working
group
that
focuses
an
operator
related
topics.
The
first
one
will
finish
will
be
finishing
the
definition
of
operators.
So
right
now
we
do
have
a
definition,
but
the
definition
is
very
high-level.
Like
it's
a
CD
and
the
controller
we
want
to
get
more
specific
there.
We
also
want
to
take
best
practices
that
are
available
around
operators
from
from
their
resources,
and
people
have
written
about
these
best
practices
and
start
working
on
this.
D
Interestingly,
about
this
working
group,
if
you
look
at
the
Charter
document
on
the
number
of
interested
parties,
that's
really
interesting
to
look
at
that's
the
first
working
group.
It
has
more
than
one
page
of
interested
parties
in
this
working
group
across
organizations
are
just
more
like.
The
first
page
is
just
people
who.
D
D
L
A
G
G
However,
since
we
started
this
with
a
couple
of
projects
in
mind,
we're
going
to
be
launching
a
couple
of
those
this
week,
Paris
is
going
to
be
starting
we're
conforming
the
maintainer
circle,
which
is
the
idea
of
a
a
peer
help
organization
for
the
maintainer
z'
across
the
n
CF
projects
and
I'm
going
to
be
launching
the
governance
working
group,
because
that's
how
I
got
involved
in
this
in
the
first
place
in
terms
of
providing
guidance
on
on
governance,
if
any
of
those
things
interest.
People
on
this
call.
G
M
G
M
G
M
N
So
AMA
we're
gonna
do
this.
We
since
we'd
be
bi-weekly
one
meeting
every
months
it's
going
to
be
dedicated
to
contributor
maintainer
AMA,
meaning
any
maintainer
can
come
and
ask
us
any
contributor
strategy
kind
of
question.
Think
not
like
low-level
contributor
office
hours,
the
high-level
contributor
office
hours
like
hey
I,
have
this
meet.
You
know
this
major
issue
or
hey.
You
know
how
do
I
get
10,000
10,000
were
reviewers,
hey
I
want
to
know
too,
but
anyway,
that
kind
of
stuff,
so
we're
gonna
do
a
send.
The
word
spre
spread.
N
The
word
send
out
here
to
the
TOC
list
and
also
do
some
kind
of
meta
introductions
about
ourselves
so
that
we
can
get
more
people
interested
and
I.
Think
the
best
thing
for
everybody
to
help
us
with
homophone
is
just
to
spread
the
word.
Once
we
get
some
of
this
introductory
information
out
there
about
us
like
a
meta,
blog
post
and
more
information
to
mailing
lists,
including
other
maintainer
mailing
lists.
N
That's
I
think
the
best
thing
is
just
information
discovery
bility
about
us
and
spreading
that
around
and
letting
people
know
that
we're
almost
open
for
business
we've
got
a
lot
of
love.
Well,
a
lot
of
the
other
issues
that
are
set
right
now,
our
issues
about
us
and
how
we
set
up.
So
you
know
once
those
floodgates
open.
We
want
to
make
sure
that
everything
looks
good
and
you
know
people
have
like
the
right
communication
inputs
and
outputs
and
things
like
that.
So
that's
what
the
that's
AMA.
M
N
N
J
B
Short
update
today,
two
topics:
both
projects
proposed
for
adoption.
One
is
chaos
mesh
proposed
for
sandbox,
the
majority
of
the
project,
contributors
and
maintainer
czar
physically
based
in
China,
and
so
while
we
typically
hold
the
Signet
work,
we
typically
hold
a
sig
net
work
meeting
at
an
hour
that
is
I,
wouldn't
wish
upon
anyone
in
their
time
selling.
So
we're
looking
at
moving
that
to
an
either
an
earlier
meeting,
I'm
at
8
a.m.
Pacific
or
potentially
a
later
one
I
think
the
later
one
would
actually
work
better
for
most
time
zones.
B
The
problem
is
that
they,
some
of
us,
have
conflicts
on
that
that
day.
So
so
what
we'll
probably
send
out
a
quick
survey
on
the
mailing
list
to
confirm
that
next
meeting
time,
but
want
to
make
sure
that
we're
accommodating
to
the
chaos
mesh
project
team
they've
been
in
queue
for
a
little
while
to
present
their
project.
A
second
project
that
has
been
proposed
for
adoption
at
an
incubation
level
is
contour.
B
Contour
is
under
active
diligence
at
the
moment.
Ken
Owens
and
Matt
Klein
are
both
are
both
going
through
that
diligence
right
now
and
confirming
positively
confirming
adopters
of
the
project.
So
just
just
got
message
from
both
I'm
Ken
and
Matt:
we're
that
they're
all
positive
traction,
thus
far
diligence
and
so
so
yeah.
So
good
good
report
progress
there
I
think
that
that's
it
for
the
racing
booty.
E
So
we
have
some
project
updates
virtual
cubelet,
presented
to
the
cig
about
four
weeks
ago,
they're
looking
at
going
for
incubation,
so
they
wanted
to
know
what
it
would
take
to
get
there.
So
they're
presented
in
the
SiC
runtime
team
provided
feedback
and
and
basically
they
they're
gonna,
add
more
documentation
as
far
as
the
you
know,
what
works
and
what
doesn't
work
in
terms
of
the
API.
E
So
harbor
is
applied
for
graduate
graduation
and
we're
still
waiting
on
some
of
the
SEC's
to
do
their
review.
So
sick
storage
already
completed
our
review,
but
we're
waiting
for
so
yeah
app
delivery
to
review
their
the
help,
charts
and
we're
also
waiting
for
security
to
complete
their
security
assessment
and
then
we'll
consolidate
those
reviews
and
send
out.
We
have
a
public
document
we'll
provide
to
the
TOC
it's
for
recommendation,
whether
to
graduate
or
not
then
there's
a
couple
of
projects
in
the
pipeline.
E
Kwe
supply
for
incubation
is
a
very
similar
project
to
harbor
it's
a
container
repository,
so
I
expect
their
team
to
present
in
Sec
runtime
in
the
next
couple
of
meetings
or
in
the
next
meeting,
and
then
another
one
is
metal,
cube,
they're
applying
for
sandbox.
That's
bare
metal,
provisioning
of
note,
so
kubernetes
notes
or
bare
metal
machines,
so
I
expect
them
to
present
I
think
in
the
next
meeting.
So
the
other
item
is
Quentin
and
I
met
to
talk
about
the
roadmap
for
the
stick
and
we're
looking
at
several
things.
So
those
include
health
check.
E
So
the
projects
you
know
container
de
built
bags
I
think
kubernetes
is
pretty
good
right
now,
but
there's
some
other
projects
that
you
know
they
might
want
to
check
on
their
health.
So
we
also
want
to
identify
some
existing
gaps
on
on
this
project,
so
some
technologies
that
are
not
currently
in
the
ecosystem.
Maybe
you
want
to
talk
to
some
projects
that
may
want
to
join
the
CCF
want
to
continue
educating
users
in
community
about
these
existing
projects.
E
We
want
to
define
some
interactions
with
some
of
the
other
cf6
and
other
community
groups.
What
would
it
take?
What
would
those
interactions?
Look
like
there's
some
roles
that
we
still
need
to
identify
so
starts
tech
lead,
so
we
run
more
participation
and
also
we're
looking
for
scribes
for
for
our
meetings.
So
this
roadmap
is
open
for
comment,
so
anyone
will
be
able
to
make
an
come
on.
So
the
idea
is
to
leave
it
open
for
about
two
weeks
and
from
there
we'll
decide.
E
You
know
what
what
will
be
the
priority
of
some
of
these
items.
What
will
will
take
on
so
the
other
items
is
that
related
to
the
roadmap
is
that
we
reached
out
to
several
communities
to
participate.
So
some
of
those
are
the
communities
sick
note.
We
have
Kara
containers
device
for
the
webassembly
community
and
the
firecracker
communities
so
while
to
get
some
participation
from
them
together,
you
know
people
are
interested
in
their
industry,
we're
looking
for
another
toc
liaison.
E
The
other
one
can
fulfill
that
duty,
so
there
are
some
people
interested
in
the
TOC,
but
that
hasn't
been
finalized
and
we
expect
that
to
happen
pretty
soon.
Then,
at
our
last
meeting
we
had
our
presentation
from
Kara
containers.
So
was
a
very
informative
presentation
and
you
know
this
is
some
of
the
things
that
we
want.
We'd
like
to
do
going
forward
to
have
some
of
these
communities
come
in
and
present
about
their
technologies
and
yeah,
and
that's
it
for
the
updates
for
cig
runtime.
E
J
J
P
J
Q
Q
Q
Main
iris
focus
and
sort
of
the
stability
in,
and
that
is
the
harbor
graduation.
Due
diligence
anchoring
the
work
around
what
security
is
providing
diligence
in
our
security
except
to
the
process,
its
armature
and
process,
and
link
here
to
the
overall
assessment
we
form
the
team.
Vega
is
going
to
be
taking
point
in
security
review
and
we
have
an
illustrious
team
of
reviewers
and
the
observer.
Who
is
participating
and
will
be.
Q
R
S
Q
T
Yet
tik
be
I
think
primarily
falls
under
storage
and
so
will
be
certainly
okay
in
the
next
few
days.
But
but
there
are
aspects
that
are
you
know,
security
related,
as
with
almost
all
project,
I.
Think
I
think
this
is
a
probably
a
syndrome.
We're
gonna
come
across
where
every
project
needs
security
review
pretty
much
so
I
guess
we
should
figure
out
how
how
six
security
is
gonna
kind
of
deal
with
that
very.
Q
Well,
we're
ramping
up,
you
know
each
each
process
we
go
through.
We
expand
the
team
and
use
we've
seen
increased
commitment
to
our
reviewers,
so
we're
building
momentum
to
be
able
to
sustain
that
really
happy
with
the
maturity
and
I
sort
of
you
know
going
back
to
the
security
assessment
as
that
being
core
wheelhouses
is
sort
of
emphasizing
that
that
muscle.
U
All
right,
six
storage,
then
alright,
so
last
week's
meeting
was
cancelled.
We
didn't
have.
We
had
wanted
true
Vega
to
present,
but
they
moved
it
out
a
couple
weeks.
So
it's
queued
up
for
tomorrow.
So
if
anyone's
interested
in
hearing
about
that
project,
please
join
us
and
our
backlog
is
all
cut
up.
I
did
have
a
last-minute
addition
to
this
slide
that
didn't
get
put
in
for
graduation.
The
project
has
updated
to
the
current
template
is
requested
by
the
TOC
that
was
just
posted
about.
U
U
J
J
G
W
But
you
can
teach
any
reset:
ok,
Wow,
yeah,
so
hi
everybody.
If
I
guess
I
will
just
talk
to
what
the
other
slide
says.
And
so
we
passed
the
toc
vote.
The
state
exists,
we
have
any
other
heads
on
Brendan
burns
and
you
have
two
chairs
to
start
off
with
and
we're
working
on
finalizing.
The
third
we've
got
a
proposal
for
our
first
tech
lead
and
we've
merged
the
Charter
and
let
me
hand
it
off
to
Ritchie
to
talk
through
the
rest.
Yes,
so.
I
The
next
steps,
as
you
know,
you
can't
see
him
anymore
so
anyway,
I've
just
stopped
free.
The
next
step,
Thank
You
Liz,
the
next
steps
we
will
expend
the
content
which
we
currently
have
content
or
comments
are
appreciated.
We
work
through
all
our
issues
and
such
we
need
to
select
and
vote
the
technique.
There
is
one
open
question
on
there
that
actually
happens.
Is
it
the
top
list
or
is
it
the?
Is
the
secret
the
sick
list?
We
just
don't
know
we
just
want
to.
We
need
to
know
so
we
can
start
that
process.
I
We
are
yet
to
set
up
recurring
meeting
times
but
know
that
we
actually
have
the
sick.
That's
one
of
the
next
things
we
are
going
to
do
and
as
a
general
FYI
cortex
was
the
only
thing
within
CN
CF
space
which
did
submit
the
URI
update.
So
it
makes
sense
that
that
would
be
the
first
thing
we
would
be
looking
at
as
a
group
and
we'd
that's
more
illicit.
So
again
we
have
there's
one
open
question
and
if
anyone
else
have
any
questions,
now's
the
time.
I
J
G
I
X
I
Are
following
the
process,
the
only
question
which
is
not
coming
or
not
answered
in
the
docs
and
in
the
process
there
does
the
actual
vote
happen.
Should
it
happen
on
the
TOC
mailing
list,
or
should
it
happen
on
the
sick
working
on
the
sick
mailing
list?
That's
the
only
thing
which
which
is
open.
Everything
else
is
answered
and
documented.
J
I
W
T
F
So
hey
it's,
this
Doug
and
Mark
is
on
as
well
to
cover
for
me
where
I
get
it
wrong,
so
those
of
you
may
have
been
following
the
six
serverless
discussions.
We've
been
kind
of
dragging
our
feet
a
little
mainly
because
we
weren't
quite
sure
whether
there
was
worthy
of
a
separate
sig
or
we're
gonna
try
to
merge
it
into
sig,
runtime
or
ABI
livery
or
one
of
the
other
ones,
and
also
we
didn't
like
the
name
server
list
we
couldn't
use
me.
F
Okay,
well
just
bite
the
bullet
and
do
it,
and
so
this
you
can
see
the
link
to
the
PR
in
there
and
we
we've
put
together
PR
with
the
draft
charter
in
there
and
what
we
decided
to
do
was
to
have
the
service
sig
focus
more
on
technologies
that
more
that
are
more
focused
on
delivering
a
simplified
user
experience.
So
the
way
to
look
at
this
is
you
may
have
a
platform
like
say
K
native
as
an
example,
you
know
it's
not
in
CNC
F.
F
So
then,
like
ki
native,
that's
just
trying
to
take
an
underlying
technology
like
kubernetes
and
simplify
it
for
the
end-user,
so
that
they're
trying
to
hide
the
technology
that's
used
under
the
covers,
so
six
service
won't
get
into
kubernetes,
but
it'll
get
into
the
technology.
That
makes
life
easier
for
the
developer
and
that's
probably
the
easiest
way
to
think
of
it
and
that
that
easier
user
experience
or
developer
experience
isn't
just
for
how
you
deploy
your
application.
F
Maybe
it's
how
you
manage
your
application
in
terms
of
like
workflow
how
events
maybe
flow
from
from
your
your
various
functions
right
or
maybe
about
how
you
connect
up
those
applications
to
back-end
services
right.
So
it's
not
how
that
linking
gets
done
through
config
maps
and
secrets,
but
rather
how
that
gets
exposed
the
end
user.
That's
where
we
think
our
sweet
spot
is
more
on
sort
of
the
developer,
experience
side
of
things.
F
That's
I
kind
of
alluded
to.
We
were
struggling
with
where
we
fit
well
to
the
other
SIG's
and,
as
I
said.
Probably
the
best
way
to
think
of
it
is
by
example
right
runtime
will
own
kubernetes.
The
server
list
will
talk
about
the
workflow
that
leverages
kubernetes
under
the
covers,
where
they'll,
hopefully,
the
workflow
is
presenting
it
in
a
simplified
user
experience
or
developer
experience
way
right.
F
So
we're
not
looking
at
really
a
whole
bunch
of
new
and
different
activity
at
this
point
in
time,
just
sort
of
continue.
What
we're
doing
honestly,
though,
I
do
kind
of
expect
that
the
current
working
group
might
have
to
actually
split
its
work
into
more
of
a
project
type
of
meeting
versus
an
administrative
type
of
meeting,
and
that
probably
would
happen
once
we
get
more
projects
brought
under
the
umbrella
of
sig
serverless,
because
we
can't
do
everything
in
one
hour
meeting
every
week.
F
So
we
may
have
to
do
a
split
at
some
point,
but
as
of
right
now
we
do
all
right.
We
are
able
to
manage
all
four
projects
under
one
weekly
meeting
and
I
think
that's
about
it.
Obviously,
we
are
looking
for
a
sick
days
on
if
someone
wants
to
volunteer
to
take
on
that
role,
but
otherwise
at
the
very
high
level.
This
is
more
of
a
morphing
of
the
current
working
group
into
a
sig
more
than
else,
and
let
me
sort
of
pause
there
and
see
if
mark
did
I
miss
anything
I.
F
S
F
Honestly,
I
suspect
we're
probably
gonna
get
this
question
a
lot
and
the
best
answer
I
could
give
is.
When
you
look
at
a
technology
like
helm,
it's
still
pretty
much
sense
focused
on
a
user
who
understands
kubernetes
right,
at
least
from
my
perspective,
and
so
I
would
not
actually
expect
helm
to
be
a
service
project,
because,
to
be
honest,
it's
a
little
too
technical
and
geeky.
It
doesn't
hide
enough
of
the
underlying
technology.
F
D
I
can
see
here
and
I
think
it
might
work
hard,
because
a
deeper
discussion
that
the
broader
group
maybe
should
have
like
the
sip
server,
less
people
service
people
to
cameras
yet
to
the
great
people
I
like
the
direction
that
you're
going
I
can
see
a
little
responsible
at
least
there
as
much
as
I
can
see.
There's
an
overlap
and
sweet
look
into
the
delivery
part
of
it,
but
not
necessarily
how
you
define
all
we
do
together,
an
application
which
is
not
in
our
focus
much
right.
D
Now,
we're
also
seeing
overlap
and
there
is
work
and
work.
It
has
not
been
started
but
should
have
been
started.
Maybe
it
is
a
random
old
application
definition
work
that
we
wanted
to
dive
deeper
into,
which
is
projects
like
om
and
and
and
others
where
we
still
don't
have
the
good
Marcus,
how
we
actually
define
an
application.
Maybe
this
is
something
but
also
fall
into
this
working
group
I.
D
What
I
can
offer
is
that
we
get
there
to
working
the
the
serve
others
working
group
and
a
delivery
gets
together
and
we
figure
out
the
way
or
we
figure
out
how
closely
related.
We
are,
and
whatever
clothes
have
eliminated
enough
to
kind
of
merge
things
or
where
we
keep
on
keeping
separate
or
if
there
is
a
splitting
point.
D
F
Yeah
I'll
reach
out
to
you
offline,
we'll
see
if
we
can
set
up
a
time
to
talk,
yeah
I,
said
I
think
this
is
gonna,
be
a
continuing
discussion,
whether
we
have
to
stick
or
not.
To
be
honest,
there
was
part
of
the
time
we
were
trying
to
figure
out
a
good
word
to
say
you
know
other
stuff
sake,
other
stuff
kind
of
thing
because
look
at
something
like
cloud
events
it.
There
is
no
good
home
for
right
now,
right
in
the
current
SIG's,
and
so
that's.
That
was
why
we
kind
of
dragged
our
feet.
F
D
Yeah,
maybe
to
this
point
yeah,
we
don't
want
to
become
everything
so
I
think
the
way
we
did
it
also
for
observability
and
other
things
is
a
few
more
is
the
umbrella
one
and
we
dumped
the
path.
We
went
a
bit
wider,
but
not
really
deep
and
worried
some
of
those
deep
topics-
and
this
might
be
the
same
case
here
like
there
like
one
or
two
bits
and
pieces
that
we
might
want
to
address
while
the
rest
is
over.
O
You
Tony
say
sake:
circle
s
is
going
to
focus
on
the
developer,
experience
and
obstructing
abstracting
away
this,
these
underlying
components-
and
that
is
essentially
it
paths,
and
you
know,
we've
we've
had
long
discussions
around
whether
we
want
to
host
pass
type
projects
in
the
in
the
scene
Thea.
So
if
that's
the
direction,
then
we
need
to
kind
of
come
around
and
have
another
discussion
about
it.
Michelle.
T
O
A
Scot,
this
scope
is
quite
large,
it's
not
its
own
vertical
necessarily
I
mean
you
can
make
it
wine
if
you
really
scope
it
in
a
particularly
worded
way,
but
it's
going
to
use
components
from
other
SIG's
like
storage
and
observability,
and
so
it's
not
its
own
independent
vertical.
Necessarily,
it
becomes
this
horizontal
layer
that
sits
on
top
of
all
of
the
states,
and
we
thought
initially
when
we
were
talking
about,
say,
cap
delivery.
O
There
was
just
so
many
other
things
that
we
wanted
to
to
get
two
foundational
components
and
building
blocks,
that
we
wanted
to
figure
out
the
terminology
for
and-
and
you
know,
discuss
and
debate
and
figure
out
the
landscape.
For
that
I
mean
that
on
its
own
is
a
is
a
large
scope,
so
I
think
we
decided,
though,
has
kind
of
fits
in
under
up
delivery.
O
O
Think
that
we've
had
a
past
project
come
in
so
I,
don't
think
we've,
given
our
recommendation
just
yet
so
I'd
have
to
discuss
I
think
the
T
is.
You
would
have
to
have
a
discussion
around
this.
Many
of
the
TOC
current
TOC
aren't
the
same
as
the
ones
previously.
So
there's
no
recommendation
right
now:
okay,.
T
O
T
O
F
F
There
are
things
that
just
don't
seem
to
fit
in
the
existing
things
and
that's
why
we
were
struggling
with
the
word
service
because
we
were
thinking
if
it's
not
quite
accurate,
because
it's
almost
like
okay,
this
project
doesn't
go
anyplace
like
cloud
events,
doesn't
fit
in
any
existing
sake,
but
needs
to
go
someplace
so
miscellaneous
right,
I,
don't
know
what
to
call
this
thing.
Yeah.
I
O
So,
let's,
let's
go
back
and
you
know
kind
of
go
through
what
we've
proposed
here.
I
think
server
list
is
a
really
important
topic,
but
I
understand,
like
the
wording,
is
a
little
complicated
and
we
need
to
like
think
more
about
that
and
what
the
implications
are
and
what
are
our
vision
is
here
and
just
kind
of
be
on
the
same
page
on
on
where
the
boundaries
are
so
I
think
yeah.
Let's
take
that
as
an
action
item.
Okay,
yeah.
F
O
J
J
J
A
A
K
L
J
L
B
B
Unless
there's
a
dissenting
opinion,
the
the
couple
of
the
Matt's
contributors
and
maintain
errs
that
might
even
be
on
this
call,
but
they've
certainly
been
attending
to
Syd
Network
meetings.
Since
its
inception
and
I
think
it
was
generally
understood
that
sort
of
sick
network
was
home
base
sort
of
speak
for
traffic
traffic
things
network
things
which
was
inclined.
H
J
We
probably
actually
to
be
fastened,
as
we
should
look
at
the
maintainer
situation
that
yeah.
If
that
is
going
to
be
a
blocker,
there
is
no
point
the
cig
looking
at
it
and
there's
no
point
see
spending
the
time
on
it
all
and
that's
getting
you
know,
led
down
a
particular
Road.
So,
let's
see
I
see
folks,
let's
all
take
a
look
at
the
maintainer
situation
there
and
see
whether
we
think
it's
improved.