►
From YouTube: CNCF TOC Meeting 2020-12-01
Description
CNCF TOC Meeting 2020-12-01
A
A
A
B
A
A
C
Yeah
so
quick
update
from
rsi
first
on
project
flux,
also
potentially
now,
together
with
flagger,
requested
to
move
to
incubation
the
links
in
here.
That's
the
link,
that's
currently
with
the
toc
so
alexis
and
the
black
folks
pinged
us,
but
obviously
for
the
working
group
to
start
the
diligence.
We
need
the
official
goal
from
the
tlc
that
we
should
be
working
on
this
issue.
C
So
let
us
know
when
we
should
start
working
at
their
request
to
go
to
incubation
the
working
groups.
We
have
started
to
re-engage
now
around
the
operator
working
group.
So
if
you
remember
a
long
time
back,
we
started
with
this
definition
of
what
that
operator
is,
and
this
went
kind
of
in
circus
a
lot
of
discussions
in
there.
When
we
kicked
this
off
so
big
interest.
Now
we
started
to
rename
it
from
definition
to
white
paper
as
as
a
working
title
and
have
restructured
it.
C
C
The
current
chairs
want
to
pass
on
to
two
new
chairs
for
for
the
working
group,
basically
because
they
have
taken
over
most
of
the
work
and
they
think
it's
fair.
I
don't
know
whether
there's
an
official
process
for
working
group
chairs,
but
we
can
take
this
offline
and
another
request
that
came
in
is
to
have
a
small
server
and
operate
the
usage
with
frameworks
that
people
are
using
it
for
which
type
of
use
cases
and
so
forth.
To
also
have
some
market
insights
there.
C
Well,
the
next
one
you
most
likely
have
heard
of
already,
because
there
was
quite
some
mastermind
queues.
You
count
around
this,
so
the
consortium
around
github's
approached
us
to
have
a
githubs
working
group.
They
also
submitted
some
of
that
work
as
a
cncf
sandbox
proposal
as
well.
I
linked
in
their
proposal
doc
here
we'll
talk
to
them
tomorrow.
C
There's
other
sandbox
projects
for
the
tucs
to
have
a
look
at
so
the
goal
is
to
have
a
again
definition
of
or
capability
model
around
git
tops
and
avoiding
the
word
manifest
too,
because
some
people
were
not
really
happy
about
using
the
word
manifesto
in
here,
but
there's
those
ideas
about
like
having
trainings
and
other
materials
on
it
and
on
the
cncf
landscape
for
app
delivery.
That's
still
something
that
we
don't
have
an
update
on
that
honestly.
C
E
C
E
C
G
C
H
When
do
we
not
have
a
lot
in
there,
but
anyway,
hello,
everyone,
hello
friends,
I
hope
everyone
is
doing
well
doing
being
safe
josh
and
I
are
actually
going
to
do
the
update
today.
We
always
keep
the
discovery
survey
at
the
top
of
this
slide.
That's
just
an
ongoing
survey
for
us
to
collect
information
from
you
as
project
maintainers
and
contributors.
H
That
kind
of
helps
us
out
with
where
things
are
what's
going
on
with
70
now
70
plus
projects
in
the
foundation,
but
we
definitely
have
had
a
lot
of
stuff
go
on
in
our
sub
projects.
The
three
main
sub-projects
that
we
have
right
now:
maintainer
circle:
governance,
as
well
as
contributor
growth.
We
have
we're
moving
and
shaking
in
all
three
areas.
The
maintainer
circle
is
actually
going
to
be
kicking
off
on
december
17th.
H
Please
save
the
date.
This
is
at
10
30
a.m.
Pacific
time
on
thursdays,
yes,
we'll
also
include
a
survey
about
availability
to
see
if
there's
other
times,
that
would
be
better
for
people
who
would
really
want
to
attend
so
that
we
can
scale
from
there.
But
we
needed
to
just
get
the
first
one
off
the
ground
and
get
it
launched,
yay
open
source.
H
So
the
first
topic
is
actually
going
to
be
an
interactive
burnout,
slash
time
management
topic,
the
way
that
the
structure
of
the
events
are
going
to
go
at
least
for
the
first
couple.
Until
you
know
other
maintainers,
you
know
give
suggestions
as
to
other
structures
and
topics,
but
the
first
structure
is
going
to
be
announcements
and
then
lead
into
an
academic
talk,
so
a
professor,
a
researcher
etc.
On
the
topic,
that's
usually
tied
into
open
source.
H
H
You
know
what
what
had
happened
during
the
the
researcher
topic
and
then
also
just
really
that's
where
the
networking
and
the
camaraderie
and
the
sharing
of
experiences
will
happen
and
then,
after
that,
we'll
come
back
together
for
a
second
talk
and
that
second
talk
is
usually
going
to
be
a
maintainer
so
that
it's
relatable
and
then
we'll
go
into
the
last
breakout
session
and
we'll
end
the
end
of
the
event.
So
that's
what
the
maintainer
circle
structure
is
going
to
be.
The
future
topics
that
we
have.
H
We
already
have
a
couple
speakers
actually
for
these
and
we've
locked
them
down
for
january
and
february,
can't
believe
it's
already
january
and
february
that
we're
talking
about,
but
some
future
topics
that
we
have
speakers
for
is
creating
values
for
yourself
and
your
project,
inclusive
language,
accidental
evangelist,
because
as
many
maintainers
know,
they
are
now
an
evangelist
as
well.
They
didn't
really
know
that
ahead
of
time
and
then
also
dealing
with
conflict
grief
and
loss
as
a
project
leader.
E
Yeah
not
a
lot
because
we're
mainly
preparing
for
kubecon
related
activities,
but
we've
gone
ahead
and
merged
in
two
templates,
so
for
people
who
weren't
already
aware,
we
maintained
this
project
templates
repository
that
has
a
lot
of
mockups
and
markdown
for
projects
to
use,
as
their
initial
documentation
includes
things
like
a
contributing
md
file
and
several
other
things
and
we've
added
to
that.
Two
common
governance
models
example:
documents
for
that
one
is
a
simple
maintainer
circle,
governance
and
the
other
is
steering
committee
elections.
E
E
Do
you
want
to
take
the
contributor
growth
stuff,
paris,
or
should
I
yeah?
Okay?
The
other
thing
is
that
out
of
contributor
growth,
carolyn
has
started
work
on
the
disqus
contributor
maintainer
site,
with
information
for
maintainers
of
all
of
our
projects.
The
this
is
a
very
early
proof
of
concept,
very.
A
E
Yeah
per
discussion
it's
going
to
get
merged
with
the
existing
contribute.cncf.org
site.
You
know
with
a
you
know,
are
you
a
contributor,
your
maintainer
sort
of
switch
off
and-
and
they
also
began
a
draft
for
a
playbook
for
recruiting
contributors,
because
this
is
the
number
one
request
we
get
from
projects
for
help
which
is
recruiting
new
contributors
to
the
project,
something
that
everybody
struggles
with
the.
E
H
This
is
a
graduation
requirement
that
we
would
like
to
draft
up
for
projects
that
has
to
do
with
some
kind
of
document
that
would
indicate
what
their
community
management
strategy
and
or
contributor
strategy
is
going
to
be
aka
who's
going
to
take
care
of
your
people
and
your
ecosystem,
because
you
know
cncf
goes
so
far,
they're
not
going
to
send
every
tweet
for
you
kind
of
thing.
So
it's
important
that
scalable
graduated
projects
look
out
for
that,
especially
during
maintenance
phases.
H
That's
pretty
crucial
because
once
you
get
to
a
maintenance
phase,
people
are
like
oh
wow.
I
wish
I
had
a
community
manager,
so
that
is
a
to-do
item
for
us.
We
have
a
lot
of
words
on
paper
right
now,
but
nothing
to
show
for
it.
So
that's
soon,
and
then
we
did
put
all
of
our
other
work.
We've
got
20,
plus
issues
that
we're
working
on
and
would
love
to
have
other
project,
maintainers
contributors
or
academics.
Researchers
that
study
these
topics
to
come
on
and
help
us.
B
Hello,
so
sig
network
didn't
meet
the
week
of
kubecon,
but
the
service
mesh
working
group
did
twice
meet
since
last.
We've
given
an
update,
and
so
we'll
focus
a
little
bit
on
the
initiatives
that
the
service
mesh
working
group
is
pushing
forward.
Probably
the
one
that's
gotten
the
most
traction
is,
or
that
is
advanced.
The
most
is
the
suite
of
conformance
tests
for
service
meshes
that
are
adhering
to
smi.
B
So
let
me
present
a
question
to
you
and
you
can
provide
feedback
offline
or
here
if
you'd
like,
but
is
here's
here's
the
situation
service,
mesh
interface
as
a
set
of
four
apis
at
the
moment,
maybe
a
fifth
each
of
the
implementations.
So
this
is
really
like
it
should
to
make
this
question
generic.
This
could
be
for
really
any
any
api.
It
could
be
for
something
like
snmp.
B
B
B
So
all
of
you
are
no
doubt
familiar
with
envoy
has
has
a
project
there's
probably
more
there's
there's
at
least
one
sub
project
of
envoy.
It's
called
nighthawk,
it's
a
load
generator.
It
is
being
it's
gaining
in
popularity,
it's
being
enhanced
to
support
horizontal
scaling,
or
rather
support
being
cognizant
of
itself.
B
A
J
I
On
on
both
of
the
topics
you
you
covered
in
more
lane,
both
the
smi
conformance
stuff,
as
well
as
the
service
mesh
performance,
have
you
been
engaged
in
addition
to
you
know
envoy,
have
you
been
engaged
with
link
or
d,
and,
and
has
there
been
a
bi-directional
calms
between
the
projects?
You
know
we
run
it
in
production,
but
just
as
as
it's
also
broadly
used,
and
particularly
around
the
high
fidelity
metrics
down
to
route
level
with
their
prometheus
and
native
integration.
B
Rather,
the
efforts
here
are
bits
are
going
in
and
bits
are
coming
back
out
and
what's
the
latency
of
those?
What's
the
throughput
of
those?
Is
there
one
of
the
things
that's
interesting
in
nighthawk?
Is
that
it
there's?
It's
has
an
extensibility
model
for
an
adaptive
load
component,
so
the
ability
to
like
run
a
load
test
analyze,
it
maybe
run
based
on
the
results,
run
another
one
kind
of
analyze
that
sort
of
run
some
optimization
routines
if
you
will
and
that
those
aren't
specific
to
one
proxy
versus
the
next.
B
B
I
I
Forgot
of
the
order,
there's
a
bunch
here
I'll
try
to
be
somewhat
brief
and
we
might
have
a
couple
discussion
points
as
well.
So
at
a
high
level,
I
think
you
know
we're
a
new
sig
still
we
we
formed
it
in
what
the
q1
q2
time
frame,
early,
q2
and
so
the
last
six
months
I
think,
has
been
has
seen
a
lot
of
engagement
from
the
community.
I
will
say:
it's
tended
towards
folks
from
vendors.
I
There
are
sorry
for
efficient
background
noise,
but
the
specific
efforts
underway
are,
you
know,
we're
scheduling,
a
series
of
introductory
talks
with
other
other
projects,
so
examples
would
be
litmus
and
a
few
others
that
will
kept
in
or
d
etc
and
I'll
get
to
that
at
the
last
part.
There
are
some
these
efforts
by
the
way
are
being
driven
by
sig
members,
not
not
myself
or
or
or
or
richard,
but
there's
a
white
paper
that
folks
are
working
on.
I
That's
sort
of
a
you
know,
a
broad
view
of
various
topics
for
those
new
to
the
sig
or
new
to
the
space.
There's
an
index
page,
that's
being
in
draft
form
right
now
that
just
has
a
listing
of
all
of
the
other
projects
that
have
particularly
interesting
topics
around
observability,
and
we
have
a
couple
design
documents
that
have
been
proposed
for
various
tools
in
in
the
in
the
space.
One
of
them
is
a
migration
tool
coming
out
of
one
of
the
sig
members
daytime
job.
I
So
we
can
discuss,
but
you
know
relevant
things
to
consider.
Are
you
know
the
no
king
making
base
case
here?
And
you
know
you
know
if
indeed
there's
no
king
king
making
so
to
speak,
that
no
alignment
check
is
is
really
allowed
right.
We
don't
have
to
have
as
part
of
our
due
diligence
that
that
box
is
checked,
but
you
know
if
no,
then
it
becomes
a
almost
an
mp
complete
right.
We've
got
a
many-to-many
alignment,
so
so
that
gets
messy
if
we
say
that
there
must
be
alignment.
I
Ideally,
you
know,
should,
should
they
kind
of
take
the
same
approach
that
openmetrics
does
so
there's
a
couple
of
different
ways
to
think
about
that
we
we
did.
However,
you
know
have
agreement
that
we're
all
working
for
it
in
good
faith
and
since
the
sig
call
there's
been
some
subsequent
discussion
in
slack
around
you
know
the
way
forward
to
align.
I
You
know
various
aspects
of
open,
telemetry
and
open
metrics
in
a
go-forward
way,
but
that's
the
general
nugget
of
where
we
spend
most
of
our
time
is
really
in
this
space.
So
so
with
that,
if
there's
any
feedback
from
folks
here
or
opinions,
I
think
richard's
really
the
domain
expert
here.
So
I've
just
covered
the
framing
but
I'll
defer
to
him
for.
I
I
F
F
F
I
To
okay,
I
mean
in
this
case
we're
not
blocked.
You
know,
I'm
not
pulling
a
fire
alarm
here.
You
know
we've
got
open,
you
know
we're
all
on
the
same
team
when
it
comes
to
you
know,
particularly
standards,
and
and
as
I
mentioned
before,
open
telemetry
and
open
metrics
are
already
working
together
and
will
continue
to
do
so.
I
So
we'll
have
maybe
a
better
update
on
on
what
comes
out
of
the
next
set
rounds
of
discussion
stemming
from
the
the
due
diligence
for
openmetrics
upcoming
agenda
items
that
we've
got
for
for
our
next
set
of
calls.
Bartek
our
tech
lead
is
gonna,
be
doing
a
bit
of
a
talk
on
profiling
and
debugging
of
stream
latency
using
some
cool
stuff,
we've
got
more
open,
metrics,
obviously,
and
then
this
is.
There
is
a
bit
of
a
call
to
action.
I
You
know
now
that
we've
sort
of
come
through
the
first
couple
of
quarters
of
the
sig
and
we've
established
something
of
a
cadence
and
gotten
some
of
the
administrative
out
of
the
way
and
have
a
kind
of
a
core
core
set
of
folks
that
seem
to
come
back
every
week
for
more
or
every
two
weeks.
Rather
we're
going
to
start
scheduling
short,
you
know
10
to
12
minute,
if
you
will
maybe
even
15
but
time
boxed
introductions
from
other
projects
that
have
aspects
that
that
are
in
scope
for
the
sig.
I
So,
for
example,
there's
a
project
called
litmus.
It's
a
chaos,
mesh
testing
thing
and,
and
obviously
you
know
what
happens
during
something
like
a
chaos
experiment
which
is
sort
of
a
sadistic
way
to
to
slam
workloads
and
clusters.
You
know
how
you
communicate.
That
is
obviously
obviously
matters,
so
so
they've
done
some
integrations
with
prometheus.
But
but
how
do
you
visualize
something
like
a
chaos
test
ongoing
or
the
result
of
a
chaos
test?
I
Or
how
do
you
zoom
out
and
aggregate
kind
of
wrap
your
wrap,
your
head
around
a
whole
suite
of
tests
and
the
results,
perhaps
across
the
fleet,
so
so
they're
going
to
come?
Talk
about
aspects
of
observability,
same
thing
with
with
captain
linker
d
and
there's,
obviously
many
others.
So
you
know
we're
reaching
out
to
connections
that
we
have
and
or
in
in
some
cases
called
calling.
I
If
you
will
projects
that
are
an
obvious
good
fit
for
for
this,
just
to
build
this
community
and
start
having
the
sig
interface
with
more
projects,
some
of
whom
might
not
know
what
other
projects
within
the
umbrella
of
the
cncf
are
available
to
them
or
they
could
align
with
or
leverage
capabilities
from.
So
if
you
have
direct
connections
to
some
projects,
that
would
be
a
good
fit
for
sort
of
a
of
a
encapsulated
webinar
or
a
show
and
tell
to
kind
of
help
build.
You
know
these
cross-project
and
cr
relationships.
I
You
know
please
reach
out
either
in
slack
or
or
to
myself
or
richie
or
bartek
directly,
and
then.
Lastly,
I'm
going
to
be
formulating
this
a
little
more
formally,
but
we're
going
to
start
building
it's
in
our
and
it's
in
our
charter,
but
start
building
a
reference
architecture
catalog
particularly
of
end
user
generated
reference
architectures.
So
you
know
in
our
case
that
ever
quote
we're
running
various
observability
related
workloads
on
eks
right,
that's
just
what
we're
doing
and
we're
deploying
it
with
whatever
we're
using
in
our
case
mostly
tonka
and
helm.
I
But
you
know
there
are
other
other
projects
and
other
other
things
in
other
clouds.
So
we
you
know
we
want
to
launch
just
a
general
user
driven,
not
a
king
maker
style.
You
know,
thou
shalt
do
this,
but
just
here's
what
members
of
the
cncf
community
are
actually
doing
and-
and
this
could
be
either
useful
as
an
example
or
some
place
to
start
from
for
somebody
else.
That
wants
to
engage
with
these
same
projects
so
and
that's
really
all
we've
got
for
today.
That's
our
little.
I
A
K
So
a
very
interesting
project,
and
this
is
actually
being
led
by
the
folks
of
microsoft.
And
if
you
want
to
take
a
look
at
the
presentation,
I
I
put
up
the
link
there.
So
that
was
our
last
meeting
and
another
project
is
tryout.
I
mentioned
this
project
in
one
of
our
last
toc
meetings.
This
is
a
container
registry
written
in
rust,
so
they're
still
gathering
some
information.
So
hopefully
we'll
have
some
participation
from
them
or
a
presentation
or
a
discussion
session.
K
Then
we
have
a
sysbox
and
that's
a
project
that
allows
you
to
run
vm
vms
in
containers.
So
a
full-blown
vm
with
system
d
and
all
the
different
components.
With
this
you're
able
to
run
it
in
in
a
container,
so
I
think
a
lot
of
people
running
in
vms
they
want
to
move
still
want
to
move
to
containers.
So
this
is
a
useful
project
for
that.
K
K
K
This
is
another
project
in
the
operating
systems
for
containers
we
reached
out
to
them,
and
this
is
very
similar
to
some
of
the
some
of
the
other
projects
that
are
presented
before
in
the
sick,
like
flat,
car
and
talos,
so
exciting
new
projects
in
that
area
and
then
in
the
ai,
ops
and
iot
space
or
at
the
edge
cube
flow.
It's
gonna
present
at
our
next
meeting
on
thursday.
So
this
is
machine.
K
So
we're
looking
at
the
cfp
and
maybe
some
of
the
topics
to
present
there
to
get
more
engagement
in
our
workgroup,
the
container,
orchestrated
device
work
group.
It's
also
doing
the
same
so
planning,
maybe
a
panel
or
to
submit
something
for
kubecon
and
yeah,
and
that's
that's
pretty
much
it
that
we
have
for
a
sick,
run
time
so
glad
to
take
any
questions
or
if
you
want
to
talk
to
us
offline
glad
to
do
so
as
well.
D
Yes,
I
am
here
this
is
emily
fox,
hello,
everyone,
some
short
updates.
We
have
more
members
as
a
result
of
cloud
native
security
days,
smashing
success.
It
was
awesome.
We
had
excellent
feedback
from
it.
The
ctf
seemed
to
actually
be
the
most
widely
celebrated
part
of
the
day.
A
couple
of
quick
metrics.
We
had
327
misconfigured
clusters
over
the
course
of
seven
hours
of
the
event,
which
included
six
challenges,
each
of
them
getting
progressively
more
difficult
to
complete.
There
were
at
least
60
participants
that
participated
in
the
ctf.
D
We
believe
that
there
was
a
lot
more
that
tried,
maybe
one
or
two
challenges,
but
overall
at
least
60
participated
for
the
cloud
native
security
day
itself.
We
had
over
1200
individuals
registered
to
attend
the
event.
Just
looking
at
the
channel
information
we
had
about
310
folks,
just
in
the
cloud
native
security
day
channel,
I
think
we
had
about
180
or
so
in
the
ctf
channel.
Everybody
seems
to
love
the
event.
We
had
excellent
feedback.
D
We
also
worked
with
the
cncf
to
announce
the
cloud
native
security
white
paper.
It
was
formally
released
as
a
pdf
on
november
18
2020
we've
had
a
couple
of
prs
and
requests
for
changes
to
the
document,
already
small
tweaks,
a
couple
of
editorial
things
that
we
missed,
but
it's
already
been
translated
to
another
language
and
there's
an
open
pr
to
wrap
that
up.
So
that's
all
we
have.
J
The
longhorn
project-
that's
currently
in
sandbox
they
presented
to
the
sick,
I've
included
links
to
the
presentation
and
the
recording
with
the
stickers
reviewed.
The
project
has
tried
it
out
the
the
running
it
and
and
sort
of
gone
through
some
of
the
details
in
terms
of
end
users
and
maintainers,
and
things
like
that,
and
we
think
it's
ready
for
the
next
stage
of
of
due
diligence.
J
J
J
It's
you
know,
we.
We
we're
obviously
aware
of
the
of
the
ability
to
to
view
the
recordings
and
things
like
that,
but
I
I
was
wondering
you
know:
should
there
be
a
process
or
or
do
we
have
a
method
whereby
maybe
we
can
ask
some
clarifying
questions
either
on
behalf
of
the
project
or
the
project
directly
to
the
toc
to
to
to
get
some
feedback.
J
Okay,
that
that
that
sounds
good,
I
I
I
was
we-
we
had
one
of
the
sandbox
proposals
that
that
had
a
review
request
and
we
just
wanted
to
get
some
some
additional
feedback,
because
the
project
asked
for
some
information
from
the
second.
Obviously
you
know
we
didn't
necessarily
have
some
of
the
backgrounds
that
led
to
the
decision.
J
J
J
As
you
know,
additional
projects
go
through
the
pipeline
and,
as
the
the
sort
of
the
content
continues
to
grow
so
very
happy
to
to,
if
anybody
fancies
throwing
their
hats
into
the
into
the
into
the
process
or
into
the
ring,
so
to
speak,
let
me
know
or
or
any
of
the
other
sig
members
and
would
be
very
happy
to
have
a
discussion
and
and
maybe
explain
some
of
the
responsibilities
in
further
detail
or
answer
any
questions,
but
it
would
be.
It
would
be
great
to
to
to
help.
D
A
All
right
last
bit
in
here
is
a
note
about
the
new
diversity
training
that's
come
up.
This
is
the
pieces,
come
in
with
collaboration
with
the
national
center
for
women
in
information
technology
and
we're
pretty
excited
about
this
there's
a
issue,
that's
currently
open.
That
makes
this
a
required
training
for
toc
members,
sig
chairs.
I
think
anybody
in
a
leadership
position
so
wanted
to
be
able
to
highlight
this
for
folks
here,
and
that
is
our
last
agenda
item
today.
A
I
don't
know
if
there
is
one
right
now,
it's
just
kind
of
like
a
hey.
This
is
this
has
come
out.
We
put
the
side
around
kubecon.
We
wanted
to
be
able
to
make
sure
that
people
were
at
least
aware
of
it,
and
then
I
think
we'll
probably
have
more
of
a
like
a
deadline
around,
like
you
know,
being
able
to
do
this,
probably
like
in
the
new
year.
Does
that
help.