►
From YouTube: Public Technical Oversight Committee (TOC) Meeting –
Description
Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io. The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Public Technical Oversight Committee (TOC) Meeting – Liz Rice, Aqua Security; Katie Gamanji, American Express; Saad Ali, Google; Justin Cormack, Docker; Michelle Noorali, Microsoft; Sheng Liang, Rancher; Matt Klein, Lyft
The Technical Oversight Committee (TOC) provides technical leadership to the cloud-native community. The CNCF will host a public TOC meeting, inviting the community to discuss various agenda items along with holding an open Q&A for the community with TOC members.
https://sched.co/aqUY
A
A
You
know,
project
aspects
of
the
organization
work
behind
the
scenes,
so
to
kind
of
kick
things
off.
My
name
is
chris
santazig.
I
have
the
fun
job
currently
serving
as
cto
and
ceo
of
the
organization,
but
I
played
many
roles
from
executive
director,
janitor
sales
and
salon
for
the
organization,
so
it's
been
fun
to
see
it
grow
over
time.
A
We
have
a
subset
of
the
11
tfc
members
today
for
the
panel.
I
will
go,
introduce
them
and
give
them
an
opportunity
to.
You
know,
discuss
a
little
bit
about
their
background
and
so
on
in
the
cloud
native
world,
then
we'll
go
in
and
discuss
a
little
bit
about
how
cncf
is
kind
of
structured
and
works
and
then
we'll
kind
of
open
it
up
to
questions
that
will
come
from
me
and
hopefully
from
the
audience.
So
to
kick
things
off.
B
Hello,
my
name
is
elena
prohercic.
I
work
for
apple
as
a
part
of
the
field,
engineering
team
and
I
help
various
apple
team
with
a
cloud
of
adoption
and
making
their
first
upstream
contributions
prior
to
that,
I've
been
a
part
of
ranger
labs
and
I've
been
involved
with
open
source
community
for
more
than
10
years.
Happy
to
be
here.
C
D
Hello,
everyone,
my
name
is,
and
I'm
one
of
the
compact
engineers
for
american
express,
I
joined
american
express
quite
recently,
actually
just
half
a
year.
However,
the
purpose
of
my
team
is
to
be
disruptive
and
to
introduce
some
of
the
new
practices,
some
of
the
best
practices
actually
within
the
cloud
native
space.
D
Historically
or
previously,
I've
had
quite
a
solid
experience
with
the
indies
companies
and
actually
being
part
of
that
spectrum
so
and
I've
actually
been
elected
as
an
individual
as
well.
So
I'm
here
to
kind
of
bring
that
point
of
view
and
make
sure
that
we
have
the
end
users
in
mind
when
we
crafting
the
cncf
landscape.
E
Hi,
yes,
so
I'm
liz
rice,
I
look
after
open
source
engineering
at
aqua
security,
so
like
justin,
I'm
very
interested
in
the
kind
of
security
side
of
cloud
native
and
a
lot
of
the
projects
and
interesting
developments
that
are
happening
on
the
security
side
and
yeah
I,
prior
to
being
on
the
toc.
I
had
the
privilege
of
being
the
cubecon
cloud,
nativecon
co-chair
back
in
2018,
which
feels
like
a
really
long
time
ago,
but
I
think
this
has
been
a
really
you
know
in
the
circumstances.
F
F
Okay,
hey
everyone.
My
name
is
matt
klein,
I'm
a
software
engineer
at
lyft,
where
I've
worked
for
the
last
five
and
a
half
years
there.
I
provide
technical
leadership
for
our
production
infrastructure
team,
where
I
spend
about
50
of
my
time
and
then
the
other
50
of
my
time.
I'm
the
de
facto
project
lead
of
envoy,
where
I
obviously
spend
a
lot
of
time
with
folks
here
around
the
cncfm
within
the
industry.
G
Hey
I'm
michelle,
I'm
a
software
engineer
at
microsoft.
I've
been
here
for
a
few
years
now
before
this
I
was
at
engine
yard
and
deus
where
I
worked
on
platforms
as
a
service
and
around
kubernetes
application
package
management,
so
I've
historically
been
a
core
maintainer
on
several
projects
that
help
with
packaging
cloud
native
applications,
helm
draft
cnab
and
now
I
work
in
the
service
mesh
space
on
service
mesh
interface
and
on
an
open
service
on
open
service
mesh,
which
is
a
new
service
mesh
implementation.
G
G
H
H
I
am
one
of
the
co-authors
of
the
container
storage
interface
and
have
been
involved
with
the
kubernetes
storage
community.
I
think
almost
from
the
beginning,
my
interest
in
the
toc
and
the
in
the
cncf
has
kind
of
been
born
out
of
my
participation
in
these
communities
and
learning
what
healthy
communities
look
like,
and
you
know
wanting
to
champion
those
ideals
and
help
grow.
The
cloud
native
ecosystem.
I
Hi
hi,
I'm
shen,
I'm
one
of
the
co-founders
and
ceo
of
rancho
labs,
so
at
rancher
labs
we
basically
built
a
business
around.
You
know:
commercializing
cncf
technologies
like
kubernetes
and
helm
and
prometheus
fluently
a
lot
of
a
lot
of
them.
We
also
try
to
contribute
to
some
new
projects
into
cncf,
like
longhorn
and
more
recently
k3s,
which
became
sandbox
projects.
A
Awesome,
thank
you.
Shang,
it's
great
to
kind
of
have
a
mix.
You
know,
as
you
could
see,
there's
folks
that
come
from
end
user
companies
from
vendors,
you
know
and
startups,
so
we
have
kind
of
a
healthy
mix
on
the
toc.
I'm
now
gonna
go
through.
You
know
a
few
minutes
to
kind
of
explain
just
in
general
how
the
cncf
is
structured.
A
You
know,
just
you
know,
try
to
you
know,
reiterate
some
of
the
principles
we
have
in
our
organization
and
then
I'm
gonna
go
ask
some
questions
to
the
toc
and
then
we'll
go
open
it
up.
Hopefully,
to
you
know
the
audience
so
I'm
gonna
go
quickly,
share
my
screen
and
see
if
this
actually
actually
works.
A
So
hopefully
everyone
sees
this
content,
but
you
know
we
started
with
a
nice
kind
of
brief
introduction.
You
know
with
our
toc
members.
You
know
if
you're
not
really
intimately
familiar
with
how
cncf
works
in
terms
of
how
it's
structured
you
know
behind
the
scenes,
is
you
know
it
is
a
linux
foundation,
sub
foundation
and
with
every
linux
foundation
so
foundation.
We
generally
always
separate
our.
You
know:
funding
governance
and
technical
governance.
So
in
cncf
we
have
a
governing
board.
A
These
are
essentially
members
who
pay
in
the
organization
it's
a
mix
of
vendors
and
users.
They
mostly
fund
the
organization,
so
we
could
put
on
events
such
as
kubecon,
and
you
know,
do
things
like
security
audits
and
so
on.
So
these
are
folks
that
essentially
have
you
know,
you
know,
get
a
chance
potentially
to
have
a
seat
on
the
governing
board,
and
you
know
focus
on
marketing
related
initiatives
like
webinars
and
so
on.
A
By
being
on
the
governing
board,
they
have
a
chance
to
have
a
voice
or
vote
into
how
the
budget
is
spent
in
the
organization,
but
they
don't
have
a
voice
in
technical
matters
per
se,
the
toc
that
is
on
you
know
this.
This.
This
presentation
you
know
today,
is
what
we
call
the
technical
oversight
committee.
There
are
essentially
11,
you
know
technical
experts
in
the
cloud
native
field,
they
control
the
admittance
and
archiving
of
projects
in
the
community.
A
We
have
over
50
projects
now
in
cncf,
which
is
a
little
bit
wild
and
they're
there,
basically
to
act
as
a
resource
to
guide
projects
and
kind
of
oversee
the
overall
technical
strategy
for
the
organization.
It
is
important
to
note
that
the
toc
essentially
represents
the
different
constituents
in
our
community.
We
have
11
folks,
and
there
are
seats
that
are
reserved
for
the
maintainer
community.
A
That
was
both
blessed
by
the
governing
board
and
toc
there's.
You
know
two
handfuls
of
principles
that
go
over.
You
know,
you
know
if
you
kind
of
go
through
them,
it
just
kind
of
gives
the
overall
philosophy
of
how
we
how
we
run
the
organization
from
a
toc
perspective.
You
know
I'm
not
gonna
go
through
all
them,
but
essentially
you
know
from
a
quick
glance.
You
know
the
organization
at
tc
want,
you
know,
is
focused
on
projects.
A
You
know
we're
focused
on
ensuring
that
projects
are
self-governing,
the
toc
doesn't
step
into
and
interfere
with
project
related.
You
know
duties,
we
have
a
rule
around.
No
king
makers
and
no
kind
of
one
size
fits
all.
If
you
know
of
the
50
plus
cncf
projects,
some
are
very
small,
some
are
maybe
specifications
and
some
are
large
as
kubernetes
and
prometheus.
We
are
also
not
a
traditional
standards
body,
which
means
you
know.
A
We
focus
on
code
first
and
real
world
uses,
and
you
know
really
above
all
the
organization
there
is
to
kind
of
help,
projects
and
kind
of
get
out
of
the
way.
We
recently
also
formed
special
interest
groups,
which
kind
of
helped
scale
the
toc
over
time.
Initially,
when
we
started
the
toc
was
only
nine,
it
was
kind
of
small.
A
We
were
much
simpler
organization,
I
think
back
then,
but
as
we
grew,
you
know,
we
started
to
basically
form
special
interest
groups
and
kind
of
focus,
specific
work
and
coordination
in
this
group
to
help
scale.
The
toc,
the
kubernetes
community,
went
through
a
similar
exercise
and
were
very
kind
of
inspired
by
the
work
there.
A
You
know
in
terms
of
proposing
projects.
This
is
a
question
that
we
get
asked
all
the
time
we've
been
doing,
work
to
simplify
this
process
a
lot.
A
lot
of
it
is
now
documented
in
one
place
on
github,
we
have
different
project
levels
which
I'll
I'll
talk
to
the
toc
about
in
a
second.
But
if
you
kind
of
want
to
you
know,
look
at
proposing
a
project
in
cncf,
I
recommend
you
checking
out
that
document.
A
A
Now
I
kind
of
want
to
take
an
opportunity
to
ask
some
questions
to
the
toc
and
you
know
more
importantly,
kind
of
get
their
feedback
on
where
they
see
the
organization
going
in
the
future
and
honestly
what
projects
you
know
they're
looking
to
potentially
bring
in
and
which
areas
they
want
to
focus
on
in
the
future.
So
I
will
stop
sharing
my
screen
and
start.
You
know
asking
some
folks
questions
there.
A
A
You
know
someone
from
the
tfc
to
kind
of
take
on
you
know.
Why
is
this?
You
know?
Why
do
we
allow
this?
Why
is
this
a
good
thing?
You
know
for
our
community
to
do
this,
because
you
know
some
people
say
it
could
be
confusing
you're,
giving
me
options,
so
anyone
want
to
kind
of
step
in
and
discuss.
You
know
why
we
allow
this.
This.
C
I
mean
we
joke
about.
You
know
five
versus
emacs
and
whatever,
but,
like
these
choices
are
part
of
our,
you
know,
part
of
the
well,
some
people,
just
peop
people
like
working
one
way
or
working
another
way.
There
are
people
want
to
try
new
ideas,
and
I
think
you
know,
I
think
it's
really
good-
that
with
the
sandbox
we've
been
very
explicit
about
things
can
fail.
C
Things
can,
you
know
happen
at
the
same
time
or
you
know
different
ways
and
that
different
things
can
happen
and
projects
we've
had
projects
merge
in
the
cncf,
which
is
great,
so
the
open
tracing
and
so
on.
I
think
so
so
I
think
there's
a
lot
of
different
journeys.
Projects
can
take
and
I
think
there's
a
lot
of
learning,
and
this
is
a
really
new
space
and
there's
loads
of
stuff.
That
can
happen,
and
I
think
that
trying
to
decide
up
front
that
something's
going
to
win
is
just
a
mistake.
G
I'll
just
jump
in
here
yeah.
I
agree
with
that.
I
think
it's
helping
to
have
different
perspectives
and
different
solutions
in
this
space
and,
like
justin
mentioned,
like
you
know,
there's
a
collaboration
and
mergers
and
consolidation
that
may
happen
later,
but
people
have
different
organizational
structures
and
different
development
environments
and
different
deployment,
environments
and
production
environments,
and
it's
just
there's
no
one-size-fits-all,
like,
like
you
mentioned
so
it's
nice
to
have
these
competing
solutions
and
if
there's
a
way
to
consolidate
in
the
future
great.
G
If
there's
not
that's,
okay,
too,
as
long
as
things
are,
I
think
I
hear
the
term
and
and
unlike
the
term
now
interoperability
a
lot,
so
you
know
your
solution
should
have
a
way
to
fit
in
and
and
work
with
other
solutions
and
as
long
as
there's
kind
of
a
story
there.
I
think
it's
nice
to
to
have
different
solutions
from
the
space.
E
Of
the
set
of
projects
that
are
currently
cloud
native
in
two
three
four
five
years
time,
I
don't
think
any
of
us
know
which
of
these
projects
are
still
going
to
be.
You
know
the
star
solution
for
each
particular
problem
and
new,
better,
more
efficient
in
in
whatever
way,
improved
versions
or
solutions
for
different
parts
of
the
problem
might
come
along,
and
that
would
be
a
really
good
and
healthy
thing
that
innovation
might
come
from
within
a
given
project,
or
maybe
it
comes
from
a
a
separate
project
and
and
that's
all
good
and
healthy.
I
Yeah,
in
fact,
one
of
the
principles-
sorry
liz,
you
know,
in
fact
one
of
the
principles
of
chris
you
said
earlier-
was
no
queue
makers
and
one
size
does
not
fit
all.
So
I
think
the
fact
that
cncf
takes
on
one
project
doesn't
mean
that
you
know
all
the
innovation
in
that
particular
space
has
already
happened.
B
A
A
Cool,
so
you
know,
that's
that
that's
great
to
kind
of
hear
people's
view
viewpoint
on
that.
It's
definitely
kind
of
something
that
people
ask
frequently
and
confusing
where
people
just
assume
that
we
will,
you
know,
bless
one
particular
you
know
solution
where
we
don't
we're
more
similar
to
an
organization.
You
know
like
the
apache
foundation,
which
has
a
ton
like
five
different
key
value
stores
or
something
at
least
so
you
know
another.
You
know
kind
of
question
that
comes
up.
A
You
know
quite
frequently
is
around
you
know
what
is
the
toc
gonna
focus
on
you
know
in
the
future,
what's
essentially
missing
in
our
landscape
of
of
projects,
you
know
you
know:
where
does
the
toc
kind
of
want
to
invest
its
time
in
there?
So
you
know:
does
anyone
kind
of
want
to
discuss
what
their
viewpoint
is
in
terms
of
what
cncf
is
potentially
missing
in
its
you
know,
suite
of
50
plus
projects
that
we
have
so
far.
E
Thank
you,
nobody
else,
volunteers.
I
will
jump
and
say
I
think
one
of
the
really
great
things
we
have
right
now
is
you
know
the
end
user
technology
radar,
the
input
from
end
users
that
we
get
you
know
from
people
like
elena
and
katie
on
the
toc
and
then
that's
where
we're
gonna
find
out
where
the
real
gaps
are
that
need
to
be
solved,
and
also
some
of
the
project,
submissions
that
we're
starting
to
see
from
end
user
companies.
G
G
You
know
how
we
can
integrate
our
other
projects,
those
those
components
and
the
solution
we
talked
about
like
there's,
five
different
solutions
for
a
problem,
so
you
should,
you
know,
pick
one
but
then
have
like
a
unified
interface
to
really
interact
with
all
your
infrastructure
related
tooling
and
operational
tooling.
So
I
I'm
excited
about
the
dashboard
space.
I
think
historically,
we've
shied
away
from
it
because
a
lot
of
us
aren't
you
know,
front
end
developers.
G
G
So
that's
one
area
and
then
just
I
think,
we've
been
talking
about
software
supply
chain
security
for
a
really
long
time,
but
I
think
now
we're
finally
getting
to
a
point
where
there
are
like
some
tools
that
are
maturing
in
this
space,
and
this
is
kind
of
becoming
more
top
of
mind
for
people
and
I'm
seeing
you
know
more
and
more
best
practices
and
patterns
put
in
place,
but
that's
an
area.
I
think
that's
right
for
innovation
and
hardening
and
mature
maturity
and
maturing
whatever
the
right
word
is
but
yeah.
D
Sorry,
I
think
that
is
the
delay
on
my
side
yeah.
I
just
wanted
to
agree
with
michelle
quite
happy
here
because
from
an
end
user
perspective,
we
I
think
it's
going
to
be
extremely
valuable
to
abstract
as
much
as
we
can
and
as
much
as
it
actually
makes
sense
from
deploying
to
capabilities,
and
I
think
it
comes
to
actually
have
this
transparency,
where
your
application
is
from
a
developer's
standpoint.
You
don't
really
need
to
understand
kubernetes,
but
you
need
to
know
how
to
operate
with
it
and
well
talking.
D
Infrastructure
operators
talking
about
actual
developers
and
actually
closing
that
gap.
I
think
there
is
a
lot
of
movements
in
that
area
to
actually
make
sure
that
there
is
a
smooth
experience
of
onboarding
as
well.
What
I've
actually
would
like
to
see
more
is
the
enterprises
adopting
cloud
native
applications.
There
is
still
quite
a
resistance.
There
is
still
this
thinking
of.
D
You
need
to
pay
your
support
or
have
a
support
team
available,
24
7.,
so
you
always
have
that
backup
plan,
but
I
think
this
is
where
the
community
comes
in
quite
nicely
together
to
actually
produce
these
best
practices
because
and
fail
over
mechanisms
and
actually
sharing
some
of
the
failure
stories.
All
of
these
feedback
loops
are
quite
important
for
the
end
users
in
the
community
to
understand
better
how
to
operate
the
tool
and
to
actually
raise
this
maturity
level.
A
Awesome,
thank
you.
Thank
you,
katie
and
one
more
kind
of
question
before
we
kind
of
look.
If
there's
any
questions
from
the
audience,
sod
storage
kind
of
comes
up
a
lot.
In
terms
of
you
know,
questions
asked
to
to
see
in
staff
association
staff.
Unfortunately,
and
you
know,
storage,
some
people
consider
it
boring,
and
then
I
think
things
have
gone
and
improved
direct.
You
know
tons
in
the
kubernetes
community,
but
I
hear
a
lot
about
devices
and
other
kind
of
you
know
outside
of
the
typical
block
and
blob
storage.
H
Yeah,
I
think
you
hit
the
nail
on
the
head
block
and
file.
Storage
has
had
a
ton
of
innovation,
especially
around
kubernetes
in
the
last
few
years
with
csi.
You
know
you
can
integrate
any
existing
blocker
file
storage
system
that
you
have.
We
have
a
ton
of
software
defined
storage
system
solutions
within
the
cncf
portfolio
with
the
rook
you
can
integrate
ceph
and
other
sdss.
We
have
platforms
and
sandbox
like
open
ebs
that
are
trying
to
innovate
in
that
area.
H
A
A
E
G
When
I
was
co-leading
kubernetes
sig
apps
was
a
while
back.
We
had
some
biotech
folks
come
in
saying
they
wanted
to
use
kubernetes
to
make
research
easier
for
people
and
that
just
really
lit
up
my
eyes
and
I
was
like
wow,
that's
so
cool
I'm
so
excited
to
be
working
on
this
in
a
space
that
enables
that
kind
of
technology,
and
so
I
think,
just
to
add
and
echo
what
liz
is
saying.
G
G
H
Yeah
and
if
I
can
add
to
that,
I
think
the
toc
here,
it's
impossible
for
us
to
be
able
to
represent
every
single
viewpoint
and
and
understand
all
the
requirements
that
everyone
has,
and
so
one
way
that
we're
scaling
is
through
these
cncf
storage.
Special
interest
groups
and
the
special
interest
groups
are
effectively
small
communities
where
everyone's
welcome
to
join
and
provide
their
input
and
that
gets
funneled
into
the
toc
and
and
plays
heavily
into
how
we
operate.
C
B
A
A
There
called
super
compute,
which
was
actually
happening
at
the
same
time
as
kubecon
last
year,
and
it's
like
another
10
000
person
event
with
like
all
hpc
people,
so
it
would
be
cool
if
we
found
a
way
to
kind
of
bridge
those
communities,
because
you
know
they
are
solving
interesting
problems,
maybe
we'll
fund
some
type
of
toc
that
super
compute
thing.
You
know
one
time
I
don't
know
we'll
we'll
figure
it
out.
A
One
final
question:
before
we
kind
of
wrap
things
up-
and
you
know
we're
always
available
on
the
toc
channel
and
the
tsc
meetings
are
open
question
from
alexis
here.
How
do
you
feel
about
some
cncf
and
apache
projects?
Kind
of
trying
to
solve
the
same
problems
regarding
standards,
thinking
about
cloud
events
and
open
messaging,
so,
basically
having
cncf
and
apache
having
similar
competing
overlapping
projects
insert
xkcd
comic
about
standards?
Anyone
want
to
take
this
question.
H
H
It's
you
know
it's
difficult
to
say
that
one
project
for
sure
is
going
to
have
the
right
answers
for
everything,
and
so
until
there
is
that
clarity,
it's
worthwhile
to
explore
and
innovate
and
allow
the
innovation
to
happen.
If
a
de
facto
you
know
project
emerges
in
a
space,
maybe
you
know
it's
time
to
deprecate
or
archive
a
project,
we're
totally
open
to
that
as
well.
C
But
there
are
you
know
there
there's
cooperation
across
those
groups
of
people
too,
and
I
think
there
should
be
more
and
it's
particularly
you
know,
it's
kind
of
these
aren't
supposed
to
be
silos
or,
and
they
and
things
are
not
supposed
to
be
grouped
by
accidental
things,
but
it
I
mean
it
definitely
makes
there's
definitely
a
community
around
kubernetes
things
in
cncf,
but
that's
it's
not
exclusively
that
by
any
means
and
projects
that
are.
You
know.
C
D
A
Awesome
you
know,
given
that
we've
got
30
seconds,
left,
we'll
kind
of
wrap
things
up.
Regarding
that
we've
done
a
lot
of
work
where
you
know
we
have
the
kubernetes
community
meet
with
openstack
and
other
kind
of
organizations
and
projects.
So
I
think
projects
are
always
open
and
if
you
know,
if
you
see
areas
where
we're
not
being
collaborative
or
we
should
be
covering,
please
reach
out
to
the
toc
and
the
cncf
staff,
where
we're
happy
to
kind
of
accommodate.
A
So
with
that
said,
you
know
we're
about
over
time,
and
you
know
please
take
an
opportunity
to
join
tsc
meetings.
You
know,
hopefully,
people
see
that
we're.
You
know
everyone's
a
friendly
bunch
here
and
you
know,
looks
forward
to
kind
of
helping
our
you
know
wider
claw
native
community.
So
thank
you,
everyone
on
panelists
for
your
time,
and
hopefully
you
enjoyed
our
virtual
kubecon,
which
has
been
a
bit
of
adventure
for
all
of
us.
So
thank
you
again
all
and
see
you
next
time
thanks.
Everyone
bye.