►
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Public Technical Oversight Committee (TOC) Meeting - Moderated by Chris Aniszczyk, CTO, The Linux Foundation
A
Welcome
welcome
everyone.
This
is
kind
of
our
you
know.
Kubecon
open
kind
of
you
know
session
with
the
toc
they'll
do
introductions
of
who
they
are
and
then
we'll
kind
of
go
through
the
kind
of
the
basics
of
how
the
organization
works
from
a
toc
perspective
and
then
we'll
kind
of
just
open
up
to
the
audience
for
questions.
People
always
have
questions
regarding
how
do
things
work?
How
do
you,
how
do
I
submit
a
project
and
and
so
on?
A
B
F
G
A
One
more
we
will
get
to
that
eventually.
So,
quick
little,
you
know
intro.
For
you
know,
a
lot
of
folks
cncf
mission
is
all
about
making
cloud-native
computing
ubiquitous
and
the
toc
is
essentially
our
technical
board
that
helps
set
the
overall
kind
of
vision
and
helps
ensure
that
projects
are
cared
for
advised
for
and
and
so
on.
The
way
the
cncf
is
structured.
If
you're
not
familiar
with,
you
know,
open
source
foundations,
there's
generally
a
board
of
directors.
Sometimes
there's
you
know,
technical
project
leads
and
so
on.
A
The
way
it's
done
in
cncf
at
least
is
there's
three
main
pillars.
There
is
the
governing
board,
which
is
kind
of
your
boring
business.
You
know
budget
kind
of
decision
makers.
These
are
generally
the
companies
that
will
pay
to
sustain
the
organization
so,
like
your
ibm's
googles,
oracle's
apples
of
the
world
and
they
get
basically
a
vote
on
how
kind
of
budget
is
kind
of
spent
across
the
organization
you
have
the
toc,
which
is
you
know
here,
represented
here
today.
They
focus
on
accepting
projects
advising
projects
potentially
dealing
with.
A
You
know
issues
when
it
comes
to
conflicting
projects
and
and
so
on.
They
are
basically
the
technical
leadership
advisors
of
the
organization,
and
then
you
have
the
end
user
community,
which
is
a
group
of
end
user
companies,
not
vendors,
that
kind
of
share
practices
and
work
together,
and
they
also
get
to
nominate
people
to
sit
on
the
technical
board,
and
these
things
are
overlapping
but
distinctly
fired
while
firewalled
offering
each
other.
So
just
because
you
have
a
board
seat
on
the
governing
board,
because
you
pay
maybe
for
a
seat.
A
You
necessarily
don't
have
the
ability
to
influence
technical
decisions
and
that's
kind
of
our
best
practice
of
you
know
separating
the
business
side
of
the
house
from
the
technical
side
of
the
house,
and
we
have
11
members
that
exist
in
in
this
doc.
So
other
things
you
know
for
folks
that
are
new
the
organization.
The
toc
a
while
ago
came
up
with
set
of
principles
that
kind
of
guide
how
they
work
as
an
organization.
A
You
know
highly
recommend
folks
to
kind
of
go
over
this
if
they've
never
seen
this
before,
but
the
simple
idea
is
being
project
centrics,
you
know,
projects
are
essentially
self-governing.
The
toc
doesn't
necessarily
meddle
in
the
matters
of
projects
they
they
work
out
on
their
own,
we're,
not
a
standards
body.
You
know,
there's
no
kind
of
slow,
traditional
standard
body
processes
within
cncf.
A
There
is
not
a
one
size
fits
all.
There's
we
they
aren't.
We
aren't
king
makers
also
and
what
what
that
essentially
means
is
we
allow
for
competing
and
overlapping
projects?
If
you
kind
of
see
in
the
120
plus
projects
we
have
now,
there
are
projects
that
you
know
overlap
a
little
bit
in
the
service
mesh
space,
there's
probably
at
least
five
six.
Maybe
seven,
I
don't
know,
there's
a
lot
of
surface
measures.
We
have
these
days,
there's
a
lot
of
security
related
projects.
That
kind
of
overlapping
could
be
a
little
bit.
A
That
dynamic
is
meant
to
happen.
It's
healthy
competition
breeds
innovation
and
better.
You
know
solutions
potentially
for
and
and
end
users.
A
lot
of
people
always
ask
like.
Why?
Don't
you
just
have
one
project
of
anything?
That's
not
how
we
work
or
how
we
were
structured
to
go
about.
We
want
to
allow
that
competition
to
flourish
and
overall,
the
toc
is
really
there
to
kind
of
truly
help
help
projects
and
not
interfere
with
with
their
day
to
day.
A
Moving
on
the
way
kind
of
things
are
structured.
You
have
the
11
person
body
up
here
and
the
way
the
kind
of
toc
divvies
out
work
to
the
community
is
structured,
usually
through
these
things
called
technical
advisory
groups
or
they
used
to
be
known
as
sigs
previously
when
we
had
to
rename
them
due
to
the
confusion
caused
between
the
kubernetes,
sigs
and
and
our
tags
here
and
they're
generally
broken
up
by
specific
categories.
So,
whether
it's
you
know,
security
storage,
you
know
observability
and
so
on.
A
At
the
end
of
the
day.
How
do
projects
work
in
csf
there's
three
levels?
I'm
sure
people
have
seen
the
crazy
landscape
and
so
on,
but
generally
the
way
projects
are
broken
up
in
cncf
is
by
what
we
call
maturity
levels
you
have
sandbox,
which
is
meant
to
be
very
early
stage,
generally
a
very
low
barrier
to
entry
to
get
as
a
sandbox
project.
You
have
to
meet
minimum
bars
around.
You
know
ip
due
diligence
and,
like
you
know,
code
of
conduct
roadmap
and
all
this
kind
of
basic
things
incubation.
A
It's
kind
of
the
next
level,
where
you're
a
little
bit
more
mature.
You
may
have
a
little
bit
more
diversity
in
terms
of
companies
and
organizations
contributing
to
the
project
and
then
graduation,
which
is
kind
of
the
stamp
of
approval
from
the
toc
that
this
is
something
that's
going
to
be
around
for
a
while.
It's
not
necessarily
going
to
go
away.
A
The
pathways
are.
We
mostly
recommend
people
to
start
a
sandbox.
That's
generally
meant
for
the
kind
of
early
stage
and
first
kind
of
stage
projects.
It's
a
very
simple
google
form
that
you
fill
out
with
basic
details
and
then
the
toc
reviews
them
I'll
say
like
once
once
or
twice
yeah,
oh
yeah,
one
every
two
months.
Basically
it's
kind
of
the
rough
cadence.
You
could
also
apply
through
incubation
pathways.
You
know:
we've
had
projects
like
k,
native
and
istio.
A
Go
that,
but
that's
a
little
bit
longer
pathway
to
get
to,
but
those
are
more
mature
projects
at
the
end
of
the
day.
So
we'll
go
through
a
little
bit
more
and
then
I'm
gonna,
you
know
open
up
and
ask
some
questions
for
the
toc
and
then
we'll
just
kind
of
open
it
up
to
everyone
to
have
an
opportunity
to
ask.
You
know
why
they're
whatever
questions,
why
their
project
wasn't
accepted
and
so
on
so
yeah.
Thank
you.
Why
was
my
sandbox
project
not
accepted?
She
didn't
like
it.
A
So
you
know
so
these
are
some
just
kind
of
you
know
ideas,
but
you
know
the
the
question
I'll
kind
of
start
off
with
before
you
know
allowing
the
audience
to
kind
of
open
up.
Is
you
know
we
we
have
128
or
seven
whatever
you
know,
projects
in
in
the
cnc.
It
covers
all
sorts
of
of
aspects
of
cloud
native
computing
and
we've
kind
of
expanded
that
over
the
years.
A
What
is
missing,
what
what's
next,
essentially
what
what
what
needs
to
be
fill
filled
in
potentially
that
currently
is
not
there
or
what
potentially
needs
to
be
consolidated.
So
basically,
my
question
to
you:
is
you
know
what
do
you
think
kind
of
the
future
missing
gaps
that
still
need
to
be
filled
in
the
organization
over
the
next?
You
know
six
to
12
months.
D
Get
started,
personal
answer
would
be
more
integration,
also
more
open
standards,
because
we
have
this
huge
breadth
of
projects
and
one
of
the
things
which
I
hear
again
and
again
and
again-
and
I
think
most
of
you
will-
is
that
people
are
confused
about
how
to
do
things
and
where
to
get
started
and
where
to
go
to
the
next
step.
And
we
have
all
those
really
really
great
tools.
D
H
I
B
I
think
interoperability
has
been
a
very
important
factor
for
cloud
native.
It
has
been
happening
from
the
beginning.
If
you
look
at
kubernetes,
there
are
a
lot
of
interfaces
that
allowed
us
to
integrate
different
networking
and
runtime
components,
so
that
was
always
a
factor
and,
I
think
continue
kind
of
building.
On
top
of
that
is
going
to
be
quite
important
for
our
community
in
terms
of
the
missing
technologies.
I
I
think
this
is
like
a
long-term
strategy
for
well.
B
Emily
can
maybe
talk
more
about
this
one,
but
security
is
a
very
important
factor.
We're
not
talking
about
adoption
at
the
bleeding
edge
anymore,
we're
talking
about
enterprises
looking
into
adopting
cloud
native
and
they
need
to
be
secure.
They
need
to
be
insured
over
and
over
again.
This
is
safe
to
run
in
production,
and
you
can
actually
bet
your
business
on
top
of
it
and
I
think
that's
definitely
something
which
gained
a
lot
of
momentum,
and
another
thing
that
I
can
kind
of
would
like
to
emphasize
is
we
have
a
lot
of
tools?
B
We
have
a
lot
of
tools
to
do
our
like
basic
infrastructure.
We
have
observability,
we
have
continuous
deployment.
However,
we
still
need
to
improve
how
we
optimize
these
tools.
It's
not
just
about
integrating
something.
It's
about.
How
can
we
optimize
this
on
top,
so
I
think
interoperability
is
still
going
to
be
a
very
important
factor
with
that.
B
But
if
you
look
at,
for
example,
the
cncf
landscape,
if
you
look
at
the
observability
side,
you
will
see
that
there
is
like
a
new
range
of
companies
focusing
on
continuous
optimization,
and
this
is
something
that
has
like
billions
of
dollars
in
investment
at
the
moment.
So
this
is
quite
new,
but
definitely
something
to
keep
an
eye
on.
So
that's
my
take.
F
I
can
take
next,
but
I'll
actually
quote
dave,
because
since
I
joined
the
tlc
there's
something
that
sometimes
keeps
coming
back,
which
is
from
an
end
user
perspective,
how
do
you
build
your
stack?
How
do
you
make
choices
and
there's
there's
a
topic
that
came
back
a
couple
of
times
and
we
never
really
got
to
like
a
good
answer,
yet
I
think
it's
something
to
come,
which
is
this
idea
of
like
having
something
like
reference
stacks
and
how?
Where
do
people
choose?
Why?
F
C
So
then
you
figure
out
which
one
of
the
the
categories
you
want
to
use
the
second
best
one
in
because
they
do
work
well
together.
So
this
kind
of
combination
of
knowing
what
stacks
work,
having
open
standards,
interoperability
and
having
some
understanding
of
which
projects
kind
of
do
what
and
which
ones
I
like
work
well
together,
really
goes
a
very
long
way
for
end
users
and
the
the
next
thing
I
was
going
to
say,
of
course
was
security.
E
E
So
this
is,
this
is
one
of
those
large
spaces
and
then
taking
a
further
step
back
it's
what
are
the
secure
development
pipelines
of
all
of
our
cncf
and
open
source
projects?
How
should
they
be
looking?
There's
a
lot
of
different
requirements
and
salsa
has
been
kind
of
leading
the
way
in
what
secure
software
development
looks
like,
but
we
need
to
get
that
across
the
ecosystem
and
get
a
lot
of
our
projects
on
board.
G
G
Storage
becomes
a
challenge
just
pulling
the
image
just
becomes
a
challenge,
so
I
would
like
to
look
at
those
areas
to
see
what
is
the
new
innovation
and
try
to
figure
out
if
we
can
do
some
of
those
here.
That
is
what
I
would
like
to
look
at.
Also
there's
always
cutting-edge
stuff
that
we've
been
wanting
to
do
like
you
know.
We
at
one
point
we
said:
okay,
serverless
is
the
cutting
edge.
G
So,
let's
do
several
s
right
so
and
then
k
native
is
coming
to
came
into
us,
and
so
there
are
other
things
like
wasm.
Related
stuff
is
happening.
The
rust
related
stuff
is
happening
in
the
community
like
how
do
we
welcome
them
into
the
cloud
native
world
and
how
will
they
fit
into
the
things
that
we
are
doing
right
and
it
can't
be
just
the
kubernetes
is
the
only
solution
here.
G
So
we
need
to
go
figure
out
like
what
is
there
anything
else
that
we
can
do
based
on
the
knowledge,
information
and
things
that
we
have.
You
know
got
from
how
we
are
building
kubernetes
running
kubernetes
and
to
see
what
are
the
other
projects
that
we
could
be
doing,
and
especially,
what
are
the
other
things
that
we
could
be
doing
that
will
explode
with
ecosystem
building
projects
similar
to
the
success
we've
had
with
kubernetes
as
well.
So
those
are
some
of
the
things
that
I
would
like
to
think
about.
A
Awesome
I'll
kick
it
back
to
me
so
one
more
question
before
opening
it
up
to
folks
in
the
audience,
so
developer
experience
huge
kind
of
problem
depending
which
projects
you
know
use.
You
know,
I'm
a
pretty
terrible.
You
know
engineer,
but
things
like
prometheus
actually
very
easy,
for
you
know
even
me
to
kind
of
get
started.
You
know
and
work
with
kubernetes
a
little
bit
more
difficult,
depending
which
you
know
which
way
you
go.
You
know
k3s
or
everything.
A
What
are
your
thoughts
of
like
what
we
could
do
as
a
community
from
a
to
specific
to
ensure
that
projects
have
like
a
baseline,
improved
developer
experience
for
especially
new
folks
in
the
community
get
started,
because,
even
though,
like
kubernetes
has
made
so
much
strides
to
make
things
significant
easier
to
get
started,
it's
still
difficult
for
a
lot
of
a
lot
of
folks,
and
then
we
have
other
projects
that
you
know
something
like
falco.
It's
like
good
that
it's
hard
good
luck,
yeah
like
so
so
it's
like.
A
G
G
So
but
there
are
de
facto
standards
that
end
up,
that
we
end
up
building
or
we
collaborate
with
multiple
communities
and
get
them
to
go
together,
lock
steps.
So
it
becomes
easier
for
the
end
user
to
adopt
like
open
telemetry
that
we
were
talking
about.
So
I
like
to
give
this
to
richie,
so
he
can
complete
the
thought
on
observability,
since
he
asked
about
prometheus.
D
I
don't
think
this
is
mainly
about
prometheus,
maybe
the
one
thing
about
prometheus
and
kubernetes.
For
those
who
don't
know
those
were
like
the
first
two
projects
and
it's
kind
of
a
little
bit
cheating,
because
borg
and
borgmon
share
history.
For
me,
this
is
incredibly
share
history,
but
they
are
super
well
integrated
with
each
other,
so
they
uplift
each
other,
and
that's
one
of
those
things
where
you
can
see
that
early
integration
keeps
paying
forward
forever.
D
As
to
the
actual
question
hire
10
tech
writers
hire
two
people
who
just
do
the
icd
and
stuff
for
the
project,
because
speaking
as
the
second
largest
project,
like
the
second
project
within
cncf
and
pretty
much,
everything
is
second
after
kubernetes,
kubernetes
has
its
own
resources.
That
is
not
the
case
within
cncf
across
the
projects.
So
the
thing
which
I
see
again
and
again
and
again
and
for
those
who
don't
know,
I'm
the
developer
seat
on
the
governing
board.
That's
part
of
my
platform.
D
What
I
want
to
actually
try
and
do
get
all
the
toil
and
all
the
genitalia
work
out
of
the
project's
way.
So
they
can
actually
focus
on
the
code
because
they
are
the
subject:
experts
at
code,
they're,
not
the
subject,
matters
but
writing
good
documentation
or
having
good
grammar
or
finding
out
that
there's
this
one
gap
they
can
work
with
those
people
or
if
we
move
to
a
new
thing,
where
cncf
gets
cheaper
cloud
credits
like
it's
on
the
projects
to
migrate.
E
E
A
J
F
J
So
much
of
what
the
toc
does
really
hinges
on
that
sort
of.
I
know
it
when
I
see
it
with
respect
to
cloud
native
so,
like
I
guess
you
know,
have
there
been,
you
know,
do
you
each
you
know?
Do
you
have
your
own
sort
of
spin
in
terms
of
what
you
think
of
when
you
say
when
you
see
cloud
native,
what
does
it
mean
for
you
and
how
does
that
influence
the
the
the
decisions
that
you
make
on
the
toc.
G
Joe
thanks
for
the
question,
so
we
struggle
this
every
time
we
try
to
vote
in
a
new
sandbox
project
literally
right,
like
you
know,
sometimes
for
example,
we
were
looking
at
projects
that
is
plugins
for
vs
code
or
intellij
and
like
what
is
the
cloud
native
stuff
out
there
right
and
do
we
need
to
get
them
in?
Is
it
going
to
be
beneficial
to
the
community
and
is
it
going
to
improve
the
developer
experience?
So
those
are
some
of
the
kinds
that
we
think
about.
G
There's
a
debugging
tool
in
the
community
is
it
cloud
native?
Does
it
help
debug
cloud
native
applications?
Then
you
know
how
much
relevant
is
of.
Is
it
a
side
business
of
the
project
to
debug
cloud
applications,
or
is
it
the
whole
business
right?
So
we
start
looking
at
those
kinds
of
things.
So,
yes,
the
google
form
is
simple,
but
we
do
have
to
spend.
Each
of
us
have
to
spend
time
on
looking
through
all
the
things
that
are
that
the
project
brings
into
the
our
ecosystem.
G
A
Do
you
think
you'll
ever
update
the
definition
again,
because
I
remember
you
know
blessed
brian
brian
grant's
heart?
I
think
he
spent
a
a
long
time
trying
to
push
that
through
and
it
took
probably
six
plus
months
of
of
I
don't
say
bike
shedding,
but
like
collaboration
to
get
something
written
down,
I
I.
G
Honestly
think
we
should
at
some
point-
and
it's
not
here
yet,
and
we
are
still
trying
to
make
sense
of
where
we
are
and
trying
to
build
a
complete
picture
for
for
the
people
who
are
using.
So
the
other
thing
about
the
mission
statement
also
is
the
main
thing
that
we
have
in
mind.
To
get
things
across
is
a
cncf
end
user.
Can
they
rely
on
the
set
of
projects
that
we
have
and
rely
on
the
health
of
the
projects
that
we
have
to
build
and
sustain
their
own
businesses
right?
K
E
So
I'll
start
so
I
obviously
am
on
the
talk
former
security
tag
co-chair,
but
I
am
also
becoming
more
and
more
active
within
the
open
source
security
foundation.
A
lot
of
the
initiatives
there,
because
I've
recognized
we
have
a
lot
of
overlap
and
activities
and
in
some
cases,
some
of
the
work
that
our
foundation
has
done,
has
really
kind
of
set
the
stage
for
how
we
can
continue
to
move
forward
in
that
space.
So
having
individuals
that
are
really
passionate
about
these
specific
domain
areas
take
on
leadership
positions
in
both
foundations.
F
G
So
the
other
thing
is
in
the
end,
it's
the
people
right
like
who
show
up
in
multiple
spaces.
Like
you
ask
any
any
one
of
us,
everybody
is
wearing
multiple
hats
means
they're
doing
different
things
in
different
spaces
at
different
levels.
So,
in
the
end,
it's
the
people
that
bring
the
rest
of
the
people
together.
Right
like
we
can
do
something
a
on
us
a
we
need
a
regular
meeting
between
open,
ssf,
doc
and
our
toc,
or
something
like
that
too
right.
G
So
a
quick
example
here
is
like,
for
the
longest
time
the
kubernetes
steering
has
had
a
regular
contacts
with
the
openstack
foundation,
for
example
right
so,
and
that
is
because
people
showed
up
from
one
to
the
other
and
they
were
able
to
talk
to
each
other
and
they
were
saying
hey.
We
are
seeing
similar
kind
of
problems
and
you
are
ahead
of
us.
We
are
behind
us
and
there
are
some
things
that
makes
it
easier
for
you
and
harder
for
the
other
person.
So
it's
the
people
that
ends
up
bringing
everybody
together.
G
A
Yeah
and
you
know,
from
a
linux
foundation
perspective,
you
know
people
who
come
to
us
to
start
things
and
all
this
stuff.
You
know
you
start
your
own
organization
with
your
toys
and
your
little
sandbox
and
scope
naturally
expands
and
and
creeps
up
and
there's
overlap,
and
our
goal
is
always
to
facilitate
the
conversations
and
if
people
want
to
merge
or
dissolve
or
us
that
we
could
accommodate
that.
But
I
think
it's
just
it's
almost
human
nature
to
like
want
to
start
your
own
specific
thing.
A
It
just
happens
the
way
the
world
works,
unfortunately,
but
we
do
our
best
to
kind
of
enable
that
collaboration.
I
think
you'll
see
more
open,
ssf,
cdf,
cncf
kind
of
events
over
overlapping
in
the
future.
We
have
about
seven
minutes
left,
so
anyone
any
other
will
just
go
through
the
row
of
row
of
folks
now,
cool.
H
I'll
try
and
be
as
quick
as
possible.
First
off
super
appreciate
all
the
work
you're
doing
so
thanks.
I
guess
on
that
note
is
I
I
can
obviously
see
by
the
screen
how
to
get
involved,
but
one
of
the
things
that
I
am
limited
on
is
time.
What
do
your
like
schedules?
Look
like
for
being
involved
in
the
tlc
and
the
tags
because,
like
I'm,
already
swamped,
but
I
really
want
to
do
this
stuff?
How
much
time
do
you
spend
on
this?
H
E
So
I've
always
tried
to
maintain
twenty
percent
of
my
work
is
in
the
open
source
community
and
there's
been
a
few
occasions
where
things
slow
down
within
the
talk
or
within
the
security
tag,
and
that
allows
me
to
focus
more
on
my
regular
day
job,
because
I
have
one
of
those
and
in
other
situations
like
right
before
this
conference,
I'm
spending
significantly
more
time
doing
open
source
work.
So
it's
a
balance
and.
F
F
Yeah,
maybe
I'll
I'll,
just
add
something
to
that,
but
I
would
just
say
that
it's
time
that
will
will
pay
back
as
well,
because
you
get
a
lot
of
exposure
to
a
lot
of
projects,
but
also
end
users
like
doing
due.
Diligence
for
a
project
for
incubation
is
super
interesting.
You
will
get
in
contact
with
a
lot
of
people
interact
with
different
different
types
of
projects,
so
I
I
think
it's
something
that
definitely
should
be
part
of
like
your
day,
job
as
much
as
possible.
It
shouldn't
be
like
a
side
thing.
A
L
So
there's
sort
of
two
competing
missions
right
where
you've
got
this
mission
to
be
have
a
big,
tent
right,
be
very
inclusive.
All
all
comers
are
welcome.
You
know
under
the
tent,
then
you've
also
got
the
standards
and
the
open
standards
sort
of
mission.
How
do
you
each
sort
of
balance,
those
conflicting
things?
So,
let's
say
you've
got
two
projects
that
are
in
the
same
space,
but
they've
got
competing
and
sometimes
conflicting
apis
or
protocols.
L
B
I
think
the
answer
to
that
is
healthy
competition.
We
have
many
projects
within
our
ecosystem
that
are
focusing
on
the
same
problem,
but
at
the
same
time
they
deliver
it
in
a
very
different
manner.
So,
if
you
think
about
the
process
observability,
we
have
cortex
and
thanos.
If
you
think
about
git
ups,
we
have
argusidium
flux
and
this
list
can
go
on
and
on.
The
idea
here
is
not
to
be
exclusive.
The
idea
here
is,
we
have
different
initiatives
and
they
try
to
solve
a
problem
in
their
own
way
with
their
own
resources.
B
However,
over
time
we
see
that
we
don't
have
a
monopoly
of
like
functionalities.
We
have
this
healthy
competition
and
when
you
have
healthy
competition,
you
have
innovation
by
default.
So
I
think
we're
trying
to
facilitate
that
as
the
tocs
and
have
that
in
mind,
so
just
try
to
be
as
inclusive
as
possible
as
long
as
it
follows
the
cloud
native
mission
and
as
long
as
it
follows
that
vendor
neutrality
and
healthy
community
and
contributors
and
maintainers
and
so
forth,
they're
going
to
be
welcomed
within
our
landscape.
D
Yes,
I'm
going
to
do
the
end
user
thing,
so
I
agree
that
that,
like
it
is
good
to
have
healthy
competition
everything,
but
at
the
same
time,
having
too
much
competition
leads
to
a
situation
where
you
have
too
much
overlap,
and
it's
super
hard
for
end
users
to
actually
navigate
this
theme,
and
then
you
have
those
small
islands
or
group
of
islands
which
are
not
fully
compatible.
My
personal
belief,
but
that's
not
toc
speaking
this.
My
personal
belief,
is
that
open
standards
should
be
a
lot
more
driven
throughout
cncf.
D
C
C
That
would
be
a
really
negative
message,
so
I
don't
necessarily
view
them
as
conflicting
things.
It's
more
a
thing
of
as
you
move
through
the
stages.
It
would
be.
Nice,
like
we've
all,
talked
about
to
get
closer
to
open
standards,
but
I
don't
think
it's
I'll
hesitantly
use
the
word
fair
for
lack
of
a
better
one
to
force
that
open
standard
as
like
a
criteria
for
what
for
being
welcome.
G
G
A
Yeah,
if
you
look
at
common
examples,
you
had
the
container
d
rocket
thing.
The
market
eventually
decided
to
standardize
on
container
d
and
kind
of
creo
as
the
the
dominant
solutions
envoy
gateway
announced
this
week
is
basically
taking
two
projects
and
kind
of
merging
it
into
envoy.
So
these
are
like
things
that
are
driven
long
term
based
on
end
user
and
kind
of
vendor
competition.
It's
not
forced
by
the
toc,
we'll
have
one
more
question
and
then
I
think
we'll
close
it
out,
and
then
I'm
sure
you
could
try
to
catch
everyone
here.
M
A
I
M
B
I
think
there
are
already
plenty
of
tools
focusing
on
that,
so
you
have
like
lightweight
version
of
kubernetes
and
you
have
multiple
products
for
that.
You
have
kind.
You
have
k3s,
you
can
re
like
even
cube
adm.
You
can
use
it
locally
if
you
really
try.
So
I
think
they're
like
there
are
plenty
of
those
at
the
moment.
However,
I
think
it
really
depends
where
you'd
like
to
focus
on
towards.
B
Is
it
just
like
application
deployment
or
if
you
like,
to
integrate
in
different
networking
components
or
different
storage,
that
becomes
a
bit
more
complicated,
and
this
is
mainly
because
you
have
different
providers
and
like
they
require
integration
with
a
third
party.
So
you
cannot
really
do
everything
on
your
local
machine.
This
is
just
like
if
it's
just
like
hello
world,
definitely
very
easy.
If
it's
a
bit
more
complicated,
I
think
that's
definitely
something
we
need
to
improve
if
you
want
to
do
it
locally.
So,
for
example,
let's
talk
about
load
balancer.
B
If
you
want
to
kind
of
use
a
load
balancer
service
like
there
is,
there
is
a
tool
kind
of
loose
my
mind.
Now
it's
not
metal
free
metal
will
be
that's
the
one,
so
you
can
use
that
one,
but
even
that
one
is
like
requires
a
bit
of
like
tweaking
like
making
sure
it
works
smoothly.
So
definitely
an
area
for
improvement
when
it
comes
to
the
next
level
of
bootstrapping.
Your
application,
and
not
just
you,
know,
have
a
container
running
locally.
A
Good
all
right
we're
a
little
two
minutes
over
over
time.
I
want
to
thank
the
the
toc
here
for
their
their
time.
I
want
to
just
stress:
everyone
is
generally
very
accessible,
even
though
everyone's
a
little
bit
busy
feel
free
to
reach
out,
send
an
email
slack.
Everyone
generally
will
will
respond
eventually,
it's
very
kind
of
a
great
group
of
folks.
We
have
up
here-
and
you
know
they're
here-
to
kind
of
serve
the
community
and
advice.
So
thank
you
for
your.
G
A
Elections,
elections,
elections,
yeah
final
thing,
so
we
cornelia
has
stepped
down.
You
know
from
the
toc,
so
this
means
we
have
a
extra
slot
opening
and
it's
part
of
the
governing
board
tranche
of
slots.
So
it
means
the
governing
board
helps
nominate
and
kind
of
vote
on
this.
So
if
you're
interested
in
potentially
having
an
opportunity
to
run
in
this,
please
reach
out
to
me
or
any
toc
members
and
we
kind
of
walk
you
through
the
process,
but
it's
fairly
rare
for
this
type
of
thing
to
occur.