►
From YouTube: CNCF TOC Meeting 2021-01-05
Description
CNCF TOC Meeting 2021-01-05
A
B
A
A
A
A
E
A
All
right,
I
don't
see
the
participant
number
creeping
up
at
the
moment.
How
are
we
doing
for
quorum.
C
A
A
You
all
made
it
into
the
meeting
and
I'm
sure
amy
will
update
with
the
people
who
are
present,
and
I
think
today
is
all
about
updates
from
the
sigs
and
hopefully
kicking
off
another
amazing
and
productive
year
for
the
cncf.
C
You
know
suddenly,
I'm
gonna
do
a
quick
look
through
the
the
chat
as
well.
I
didn't
see
anyone
updating
from
app
delivery.
I
think
they're
still
on
vacation,
but
if
you're
here
and
you
wanted
to
be
able
to
do
an
update-
that's
perfectly
fine
too.
A
F
Hello
good
morning,
I
think
so
as
good
as
it's
going
to
get
wow.
My
goodness.
Let
me
collect
my
thoughts.
It's
a
new
year.
You
think
I'd
be
refreshed.
There
are
I'm
heavier,
that's
for
sure.
So,
just
just
so
everyone
knows
that
watch
out
for
the
christmas
cookies
they'll
get
you
two
two
items
three
items.
One
is
that
we
are
in
need
of.
F
F
There's
networking
is
a
big
old,
fast
space,
one
of
the
working
or
the
only
sort
of
sub-working
group
that
we
have
at
the
moment
is
the
service
mesh
working
group,
an
update
from
so
there's
a
few
threads
of
efforts
that
are
going
on
inside
that
working
group
and
those
are
the
bullet
points
on
the
left
hand,
side
of
the
slide.
F
The,
since
last
we
spoke,
the
hyperlink
for
a
project
called
get
nighthawk.
Wasn't
there
before
it's.
That
project
is
trying
to
help
bring
some
additional
support
to
envoy's
load
generator.
It's
nighthawk
is
a
sub-project
of
envoy.
It's
a
load
generator
written
in
c
plus
plus
helps
characterize
the
performance
of
data
service
meshes
of
data
planes
that
run
on
envoy,
and
so,
but
it
doesn't
have.
F
It
has
a
single
distribution
in
one
docker
container
and
so
the
because
of
the
the
interrelated
work
streams
that
happen
inside
of
the
service
mesh
working
group,
hopefully
bringing
some
additional
distribution
to
nighthawk,
helping
uplift
that
subproject
and
making
it
more
accessible
will
enable
a
few
of
the
service
meshes
that
are
looking
at
it
today.
F
Historically,
istio
has
used
a
load,
generator
called
fortio
and
still
does,
but
has
been
looking
more
toward
nighthawk
and
its
use,
so
has
the
app
mesh
team
and
so
have
maybe
some
others
that
are
using
envoy
in
their
data
plane.
So
anyway,
that's
what
that
project
in
bold
is
about,
and
specifically
some
some
of
the
individuals
that
red
hat
and
at
google
who
work
on
nighthawk
are
aren't
in
the
time
zone.
F
That
works
well
for
the
1pm
central
meeting
that
we
have
so
the
second
update
or
the
third
update
so
to
speak,
is
on
ambassador
and
it
being
it's
been
under
review
for
some
time.
It's
gotten
thumbs
up
from
matt
klein
from
sid
network
for
opening
to
so
it's
due
diligence
is
sort
of
closed
due
diligence
is
completed
and
has
passing
colors.
A
Awesome
is
that
ambassador
due
diligence
document
has
that
been
circulated
around
the
tfc.
It
might
have
been,
and
I
have
just
not
noticed
it.
F
G
F
I'm
is
mr
klein.
A
On
matt,
are
you
there.
A
Okay,
I
guess,
if
he's
not,
we
can
call
on
him
to.
Let
us
know
if
ambassador
is
ready
for
public
dissemination.
H
A
A
J
Ready,
I
was
like
I
wasn't
really
ready,
but
anyway,
so
we
actually
have
a
lot.
We
we
came
into
this
update
going.
Oh
it'll
just
be
a
quick
one,
and
then
we
actually
started
updating
and
we
were
like
oh
different
story.
So
just
in
some
meta
news
for
us,
we
are
gonna.
Have
some
incoming
charter
updates.
J
The
one
charter
update
is
gonna,
be
sort
of
a
proposal
of
our
graduation
process
for
our
docs
and
guidance.
Now
that
we
have
this
beautiful
thing
set
up,
it's
cncf
slash
project
template
repo.
J
J
We
already
have
some
docs
for
review
to
go
through
that
kind
of
a
process
and
we'll
have
a
email
list
or
excuse
me,
mailing
list
we'll
have
a
mailing
list
item
out
by
the
end
of
today
with
some
of
those
docs,
for
example,
the
contributor
ladder
guidance
is
included
in
that
I
know
lee
and
a
couple
other
folks
have
been
eagerly
anticipating
that.
So
that's
one
of
the
one
of
the
many
in
there
and
then
other
charter
changes
that
we
have
coming
down.
J
The
road
are
really
just
based
off
of
the
road
map
that
we
had
initially
set
forward,
and
I
think
we
have
hit
and
achieved
all
of
those
things
that
we
said
we
would
so
now
we're
going
to
include
2021
and
beyond.
J
So
as
far
as
sub-project
activity.
This
is
where
the
two
slides
was
necessary
because
we
were
like
wow.
We
really
did
do
a
lot
for
maintainer
circle.
Guess
what
we
had
our
first
one.
That's
awesome.
It
took
like
nine
months
to
get
that
off
the
ground
and
it
really
ends
up
just
being
one
meeting,
but
it
was
awesome.
Nonetheless,
we
had
41
maintainers
come
from
seven
different,
unique
projects.
J
J
She
came
and
did
a
little
bit
of
a
review
of
the
research
and
the
people
that
she
talks
to
about
her
research
and
her
burnout
interviews
and
things
like
that.
And
then
we
had
aaron
krikenberger
maintainer
on
kubernetes,
come
and
give
a
very
personal
story
of
his
about
his
burnout
and
some
of
the
challenges
that
he
had
as
well
as
some
of
the
things
that
he's
done
to
help
himself.
J
So
we
also
had
break
rooms
after
each
one.
So
there
was
a
lot
of
introductions,
a
lot
of
camaraderie,
a
ton
of
personal
stories.
So
that's
why
it
was
not
recorded
and
they
will
most
likely
not
be
reported
in
the
future,
because
there
was
a
ton
of
personals
shared,
which
is
amazing.
Everybody
felt
very
comfortable
sharing,
sharing
some
of
that
information
and
was
very
lovely,
so
future
sessions
expect
us.
We
will
be
talking
to
you
all
on
the
maintainer
cncf
list,
as
well
as
a
maintainer
circle.
J
On
slack,
this
will
be
at
least
once
a
month.
Other
future
sessions
coming
to
you
are
going
to
think
are
going
to
be
things
like
inclusive
language,
value
and
principle
building
for
yourself,
as
well
as
your
project,
maintaining
conflict,
managing
during
grief
and
loss
and
other
really
awesome
things
like
that.
D
J
Yeah,
I'm
happy
to
happy
to
link
up
with
whoever
I
have
a
to-do
item
to
get
a
kind
of
like
what
we
learned
out
of
the
session
to
the
maintainers
list.
So
I
can
happily
take
that
info
to
them
or
or
whatever
dorothy
included
some
of
her
research
and
things
like
that.
So
I
can
forward
that
to
you
or
whoever
thanks
yeah,
so
governance
and
contributor
growth
are
two
other
sub-projects.
J
We
started
to
discuss
the
idea
of
taxonomies
and
then
also
building
out
all
of
the
project,
templates
and
guidance
like
I
said
that
that
we've
been
building
for
governance
taxonomies.
I
don't
want
to
hit
on
this
too
much,
but
I
definitely
think
that
toc
and
folks
will
take
interest
in
this.
If
anybody's
read
the
nadio
working
in
public
book.
This
is
what
a
part
of
the
book
just
one
part
that
you
know,
attempts
to
do,
which
is
open
source
is
so
big
now
and
there's
more
ways
to
eat
a
recent
pcs.
J
So
therefore,
we
should
probably
lump
this
into
things
like
contributor
communities
and
not
contributor
communities,
and
and
what
have
you,
because
not
everybody
needs
to
have
a
contributor
community
to
to
open
source.
So
this
is
a
discussion
that
we've
been
having
and
it's
gonna
hopefully
turn
into
something.
J
If,
if
you'd
like
to
join
us
for
this
discussion
and
hopefully
turn
it
into
something
potentially
badging
and
other
really
cool
things,
let
us
know
and
then
contributor
growth
we've
got
a
maintainer
site.
That's
about
to
pop
up
would
definitely
appreciate
any
and
all
contributors
there
to
help
us
with
that.
J
This
will
be
all
information
that
is
very
relevant
to
not
only
new
contributors
and
surfacing
the
github
repository
that
eor
and
so
many
others
have
been
steadfast
and
amazingly
working
on
so
give
some
discoverability
to
that,
but
also
bubble
up
maintainer
information
that
isn't
necessarily
accessible
at
all.
So
that's
the
idea
behind
the
site.
We've
also
got
a
draft
state
of
the
recruiting
playbook,
which
will
go
into
our
larger,
larger
contributor
growth
framework.
J
But
if
you'd
like
to
take
a
take
a
peek
at
where
we
are
with,
you
know
how
to
recruit
contributors
feel
free
to
weigh
in
there
and
then
we
still
have
the
thing
on
deck,
where
we
were
going
to
talk
about
community
management
and
a
contributor
strategy,
graduation
requirement,
but
that's
just
again
that's
more
of
a
discussion
right
now
still
and
on
deck,
but
that's
pretty
much
it
sorry.
I
ate
up
all
your
time.
We
had
a
lot
so
hope
everybody
has
a
good.
A
Year,
wonderful,
I'm
just
having
a
quick
scan
of
the
proof
of
concept
of
the
contributor
maintainer
site.
There's
clearly
lots
of
good
work
going
on
in
this
sig.
It's
amazing,
pretty
cool.
K
Yes,
I
might
cut
out
again
because
my
home
line
is
having
major
issues
the
last
few
weeks.
Also,
I'm
not
quite
certain
if
we
covered
parts
of
this
already.
Of
course,
I
kind
of
brain
flushed
over
the
new
year.
K
So
stop
me
if
you,
if
you
heard
the
part
of
this
before
first,
is
just
a
a
look
back
of
the
past
six
months
of
who
attended
and
we
have
a
centric
of
maybe
12
people,
I'm
not
going
to
read
out
the
list
of
of
companies,
but
those
are
the
companies
who
attended
over
this
half
year
of
of
stick
observability
existing
our
current
incr.
Our
current
in
progress
efforts
can
be
obviously
seen
in
in
our
github.
K
We
are
working
on
on
that
white
paper,
which
we
want
to
get
out
and
still
would
like
some
some
feedback
on
our
current
design
docs.
We
did
finish
the
due
diligence
document
for
open
metrics
incubation,
which
is
linked
here
last
year.
We
had
a
call
with
alina
and
dave
who
are
both
interested
in
sponsoring
josh
and
paris.
Had
some
concerns.
That's
sorry,
governance
wg,
not
sick
governance,
but
same
difference.
K
K
We
have
scheduled
a
few
midi
project
things
where
basically,
projects
can
come
and
self-introduce
themselves
to
to
seek
observability
and
also
we
want
to
create
a
architecture
catalog
which
basically
tells
potential
users.
How
actual
end
users
are
using
observability
tools
in
their.
A
I'm
curious
about
the
last
item
on
that
page
about
scheduling
an
explainer.
A
E
Hey
happy
new
year,
everyone
yeah,
so
runtime
we
didn't
have
a
lot
of
activity
in
december.
I
think
some
of
the
folks
were
actually
out
but
yeah
we're
continuing
with
the
projects
and
reaching
out
to
some
of
them,
and
we
did
actually
have
one
meeting
another
one
of
our
meetings
got
postponed
so
on
the
different
spaces.
So
we
have
containers
and
runtimes.
E
We
have
this
project
called
sysbox,
and
this
is
like
a
project
that
allows
you
to
run
containers,
but
in
a
vm
like
setting
like
you
can
run
them
with
systemd
and-
and
it
looks
like
a
vm,
so
they're
gonna
be
presenting
on
february
4th
so
next
month.
Trial
is
another
project
that
we've
been
talking
to
for
a
couple
of
months
already
and
they're
still
gathering
some
information
and
they
will
be
presenting
sometime
in
the
future.
This
is
a
container
image
registry
is
written
in
rust,
so
that's
trout.
E
Then
we
have
a
few
web
assembly
projects
that
we
we
reached
out
to
so
webassembly
is
a
very
new
area
and
I
guess
exciting.
So
a
lot
of
people
are
interested,
so
we
want
to
get
more
engagement
there.
So
swam
is
webassembly,
runtime
written
scala,
so
hopefully
we'll
get
them
to
present.
E
So
on
the
ai
ops
in
iot
space,
in
our
only
meeting
that
we
had
in
december
open
yurt
presented-
and
this
is
a
project
that
allows
you
to
extend
kubernetes
to
the
edge
and
it's
a
very
similar
project
to
cube
edge
so
they're,
actually
a
cncf
sandbox
project
now
so
they're
happy
to
be
in
the
cncf,
and
they
mentioned
that
they've
gotten
a
lot
of
traction
from
being
in
the
cncf,
so
they're,
pretty
excited
and,
and
hopefully
they're.
Looking
at.
E
E
Postponing
and
they're
actually
presenting
on
the
17th
on
this
month
and
k3s
is
another
project
at
the
edge
or
targeting
kubernetes
at
the
edge,
and
we
have
been
talking
to
them
and
they'll
be
presenting
soon
they're
already
a
cncf
sandbox
project,
so
exciting
projects
and
in
the
other
area
we
have
the
operating
systems
for
containers
or
operating
systems
in
general.
E
So
this
is
a
lightweight
operating
system
that
allows
you
to
run
containers
it's
similar
to
some
of
the
projects
that
presented
in
the
past,
like
talos
and
flat
car,
and
then
we
have
rest
ctl
project
from
the
folks
at
facebook,
and
this
allows
you
to
control
resources
in
an
operating
system
using
metrics
like
latency
and
errors,
and
you
know
sre
type
of
metrics,
so
they'll
be
presenting
soon
so
yeah
and
that's
the
activity
that
we
have
for
the
projects
and
as
far
as
the
sick,
we
we're
planning
to
meet
all
the
chairs
and
maybe
set
up
a
plan
for
next
year
and
to
see
where
we
can
get
more
engagement.
E
I
mean
we've
been
getting
a
lot
of
these
projects
coming
to
present,
but
maybe
we
can
think
about
some
of
the
things
that
make
this.
This
can
actually
increase
the
engagement
yeah
and
then
we're
looking
for
some
guidance
from
the
toc
too.
As
far
as
you
know,
where
to
go
this
next
year
is
there's
some
new
things
that
you
know
their
toc
is
thinking
about
and
then,
where
the
six
actually
can
help
out
yeah
and
that
that's
it
for
the
updates.
A
J
K
I
can
try,
but
not
promise
it's
it's
been
horrible,
the
last
two
weeks
or
so,
which
is
great
with
the
lockdown
not
having
internet
anyway.
I've
been
informed
that
the
last
thing
which
which
was
open,
was
poc,
requests
basically
liz.
K
You
wanted
to
have
a
bit
of
an
explainer
about
open,
metrics,
open,
telemetry,
open
tracing,
open
census.
All
the
other
opens-
and
I
just
wanted
to
to
ask
the
group
when,
when
you
would
like
to
have
that
schedule,
basically.
A
C
A
Okay,
let's
move
on
to
whoever
is
after
security,
okay,.
L
Hello,
everyone
quick
update
from
us.
We
have
73
members
now
from
60
different
affiliations
and
we
wrapped
up
our
nomination
process
to
determine
who
we
would
like
to
nominate
as
additional
technical
leads
to
the
two
that
we
currently
have.
So
on
the
slide.
We've
got
ash
and
aradna
and
andres
with
the
breakdown
just
like.
We
did
last
time
about
why
we
feel
like
they
would
be
excellent.
Technical
leads
for
sig
security.
A
A
A
I
I
I
It
looks
very
strong,
so
it
should
be
fairly
straightforward,
open
ebs,
we're
still
in
some
ongoing
discussions
with
the
project
team
on
on
some
changes.
If
our
needs
is
in
terms
of
some
new
topics,
one
one
of
our
one
of
our
members
proposed
a
disaster
recovery
as
a
discussion
and
we've
started
ordering
a
document
which
we're
going
to
share
with
the
group
at
the
next
call,
which
is
going
to
cover
a
bunch
of
topics,
some
of
them
theoretical,
some
of
them
sort
of
pragmatic.
I
How
to's
in
terms
of
implementing
disaster
recovery
in
in
cloud
native
ways
between
between
clusters,
you
know
and
talking
about
different
replication
mechanisms
and
failover
mechanisms
that
are
available,
which
is
which
is
proven
to
be
a
really
interesting
topic
for
everyone.
I
We
also
had,
in
our
last
call
a
discussion
to
set
up
a
a
set
of,
I
guess
community
presentations
to
build
out
some
community
content,
so
so
this
will
probably
take
the
form
of
some
presentations
and
recorded
sessions
which
we
will
be
sharing
as
part
of
a
way
of
disseminating
information,
but
also
getting
getting
a
bigger,
creating
a
bigger
community
in
in
six
storage,
we're
still
working
on
the
performance
and
benchmarking.
I
My
paper,
although
that
kind
of
stalled
a
little
bit
over
the
holidays
and
we've
we've
been
looking
to
recruit.
Some
additional
tech
leads
with
the
sig
and
we
have
two
or
three
candidates
now
who
are
very
interested
and
we're
and
we're
talking
them
through
the
process.
I
So
we'll
probably
be
looking
to
nominate
those
leads
in
the
next
in
the
next
call.
A
A
I
I
Mean
that's.
That's,
that's
a
fair
comment.
I
think
there
are
some
similarities.
It's
right
right
now.
Longhorn
seems
to
be
sort
of
on
a
trajectory
of
kind
of
sailing.
I
Process
as
far
as
we
can
tell
open,
ebs
has
has
some
additional
challenges
which
which
we're
working
through,
which
is
which
is
probably
going
to
slow
things
down.
So
we'll
I'm
quite
happy
to
have
that
discussion
if
we
think
that
that's
important,
obviously,
there
are
other
cncf
projects
where,
where
there's
some
overlaps-
and
I
think
we're
going
to
see
similar
sort
of
things
in
storage
too,
but
I
think
the
you
know,
architecturally,
the
the
projects
do
have
some
interesting
differences.
A
Okay,
any
other
questions
and
thoughts
for
six
storage.
A
A
Great
we
flew
through
that
anyone
got
any
other
questions
or
points
they
would
like
to
bring
up
today,
I'm
shocked
by
alex's
300
days.
It's
really
sad.
C
One
last
note
chris,
has
put
some
notes
into
chat
about
the
upcoming
toc
elections
feel
free
to
reach
out
if
you
got
questions,
but
these
come
from
both
the
gb
and
the
end
users.
This
time
around.