►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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
So
this
is
kind
of
tradition
for
us
where
we,
basically
you
know,
have
been
doing
these
kind
of
toc
meetings
at
kubecon
as
just
a
way
to
you
know,
introduce
kind
of
how
the
toc
works.
You
know
these
aren't
these
people
that
are
just
magically
hiding
and
all
this
wonderful
stuff,
it's
an
open,
open
process,
and
so
on
so
generally
we'll
go
through
kind
of
like
a
brief.
Intro
of
you
know
how
the
toc
works,
then
open
up
for
questions
and
kind
of
see
where
things
go
from
there.
A
So
you
know,
you
know,
saw
this
a
little
bit.
You
know
today,
you
know
cncf's,
all
about
kind
of
making
cloud
native
computing
ubiquitous
and
the
toc
is
basically
there
to
kind
of
guide
the
technical
side
of
the
organization
ensuring
that
projects
are.
You
know,
you
know
essentially
cultivated.
You
know
accepted
and
kind
of
guiding
them
through
that
wonderful,
you
know
process,
we
have
11
lovely,
you
know
individuals.
A
Unfortunately,
just
two
of
us
were
able
to
join
today
and
you
know
I'll
have
them
kind
of
maybe
introduce
them
and
introduce
themselves
and
talk
a
little
bit
about
kind
of
your
background
and
and
what
you
work
on
and
then
we'll
kind
of
go
through
our
journey
of
how
the
toc
operates
for
about
10
minutes
and
then
maybe
open
it
up
for
for
questions
for
folks
and
if
we
end
early
and
go
to
the
party
even
better.
So.
B
B
So
I've
been
doing
kubernetes
for
about
five
or
six
years,
and
then
I
spent
about
18
months
at
weave
works,
which
is
the
company
that
coined
the
term
git
ops,
which
is
really
kind
of
an
extension
of
devops.
For
a
platform
like
like
kubernetes
and
very
recently,
just
in
the
last
two
or
three
months,
I
have
joined
amazon.
C
Okay,
so
I'm
ricardo,
I'm
a
computer
engineer
at
cern
in
geneva.
I
work
on
our
cloud
deployments.
We
run
a
large
private
cloud
on
premises.
We
also
use
public
clouds,
I'm
mostly
focusing
on
kubernetes
and
containerized
environments,
but
I
do
also
a
lot
of
networking
and
software-defined
networks
and,
more
recently,
some
machine
learning
to
support
our
scientists.
So
a
lot
of
accelerators
and
integrating
all
of
this
in
kubernetes.
C
Before
that,
I
did
a
different
other
things
in
cern
as
well.
I
was
a
developer
for
what
we
call
our
worldwide
lhc
computing
grid,
which
is
a
kind
of
large
distributed
environment.
That
is
a
pre-cloud
something
that
would
be
very
different
if
it
would
be
redesigned
today,
but
that
puts
a
lot
of
resources
at
the
disposal
of
our
scientists.
C
Yeah
and
more
recently,
I
started
working
on
the
cncf
research
end
user
group,
which
kind
of
tries
to
get
together
all
the
members
of
end
users
of
the
cncf
that
has
have
similar
requirements
regarding
batch,
like
workloads
and
accelerators
and
yeah,
and
since
february
this
year,
I'm
in
the
toc
as
a
end-user
representative.
So
I
help
out
in
this
area.
A
And
I
guess
chris
anazek,
I
have
the
fun
job
of
serving
as
cto
of
the
oregon.
My
team
basically
supports
the
toc
and
kind
of
our
technical
side
of
the
house
and
ensure
our
projects
are
healthy
and
and
stable,
so
governance
structure.
You
know
we'll
kind
of
go
through
and
talk
a
little
bit
of
how
we're
governed,
because
a
lot
of
people
kind
of
get.
This
kind
of
you
know
confused.
I
think
it's
a
little
bit
of
you
know
inside
baseball,
but
I
think
it's
kind
of
important
to
understand
how
the
organization
actually
runs.
A
So
we
have
kind
of
three
main.
You
know
parts
of
cncf.
You
know
we
have
the
governing
board,
who
basically
these
are
your
essentially
funders
right.
You
know
these
are
the
people
that
are
members
of
the
organization
they
pay
in.
That
money
is
basically
pulled
together
to
go
sustain
the
project.
These
people,
who
are
on
the
governing
board
generally
have
no
say
in
how
the
technical
projects
work
they're
just
there
to
come
together
and
decide
how
the
budget
is
spent.
A
So
we
could
basically
put
on
wonderful,
wonderful
events
like
this,
like
kubecon
or
fun,
security
audits
and
so
on.
So
you
know
it's
it's
mostly
vendors,
but
there
are
a
mix
of
end
users
like
you,
know,
apple
and
spotify,
part
of
the
governing
board.
The
toc.
You
know
which
is
here.
This
is
the
technical
body.
It's
a
completely
separate,
you
know,
organization,
you
know
from
the
governing
board.
It
handles
all
the
technical
decisions,
those
projects
get
accepted,
which
projects
you
know
get
archived
and
we
purposely
separate.
A
A
They
may
employ
some
of
these
individuals,
but
you
know
it
is
the
maintainers
at
the
end
of
the
day
and
the
toc
who
make
the
you
know,
technical
decisions,
you
know
overall,
and
then
we
have
this
third
kind
of
structure,
the
end
user
community,
which
essentially
is
end
user
organizations.
People
who
don't
sell
cloud
native,
you
know
services
or
products
right.
These
are
the
actual
consumers
of
the
technology
like
like
an
apple
or
cern
where
ricardo
works
for
and
aws
is
a
vendor.
A
We
give
a
special
space
for
the
end
user
community
to
basically
work
together.
Collaborate
share
practices
and
essentially
safe
space
may
not
be
the
right
word,
but
basically
it's
an
area
for
them
to
essentially
not
have
vendors
involved,
but
they
have
a
formal
role
in
governance.
So
end
users
get
to
elect
people
on
the
toc
and
they
have
representation
there,
and
so
these
are
kind
of
the
three
main
tier
structure
of
cncf.
You
know
for
us
that
kind
of
work
in
the
organization-
it's
very
obvious,
but
a
lot
of
people
sometimes
get
confused.
A
That,
like
oh,
do
people
like
pay
to
get
a
toc
here.
How
does
this
work
influencing?
It's
completely
separate?
You
know
on
purpose
we
kind
of
separate
technical
governance
from
funding
governance
which
people
get
a
little
bit
confused
by
and
we
also
give
end
users
a
special
voice
in
the
organization.
A
So
one
of
the
things
that
toc
puts
together
is
something
we
call
the
toc.
You
know
principles.
These
are
essentially
things
that
the
toc
kind
of
abides
by
and
kind
of
you
know
their
decision.
You
know
how
they
think
about
making
you
know
decisions,
so
this
was
put
together.
You
know
a
while
ago
by
some
of
the
early
toc
members,
but
generally
we
consider
the
cncf
as
a
kind
of
project
centric
organization,
if
you
notice
that
you
know
if
you're,
older,
kubecon,
there's
project
logos
all
over
the
place,
projects
are,
for
you
know.
A
First
and
foremost,
you
know
you
know
at
the
center,
less
so
of
the
organization
projects
are
self-governing.
You
know
one
thing,
a
lot
of
people,
you
know
coming
from
different
foundations.
Organizations
get
a
little
bit
confused.
Is
each
project
gets
to
kind
of
build
their
own
governance
model
of
how
they
run?
You
know.
A
Kubernetes
is
very
different
from
an
envoy
than
a
container
d,
then
a
link
or
d
and
so
on,
and
we
just
find
that
as
a
convenient
way
where
each
project
is
going
to
be
different,
they
should
be
governed
a
little
bit
different.
It
just
has
to
be
documented
in
public.
The
toc
looks
for
very
high
quality
high
velocity
generally
projects.
You
know
that's
kind
of
what
they
generally
look
for.
Sometimes
they
make
bets.
We
have
this
kind
of
no
king
maker's
role.
We
allow
for
competing
and
overlapping
projects.
A
If
you
notice,
we
have
things
like
container
d
and
creo
linker
d
and
envoy.
All
these
things
kind
of
overlapping
compete
in
some
way.
We
don't
mean
to
like
pick
a
project
and
have
that
one
be
like
the
only
one
true
way
to
do
things
we
do
allow
for
competition,
we're
not
a
traditional
standards
body.
We
don't
basically
deal
with
old
school
standards.
Sometimes
we
have
specifications,
but
the
idea
is
we
only
promote
technology
or
specifications
that
actually
have
real
world
usage
and
so
on.
So
there's
some
other
things.
A
A
You
know
maturity
models.
We
have
three
main
levels
of
you
know:
projects
that
the
toc
kind
of
works
within
the
kind
of
decides
where
to
guide
projects
through
sandbox
incubating
graduated
three
main
levels.
We
kind
of
use
that
crossing
the
chasm
analogy.
I
mean
concordia
talked
about
this
a
little
bit,
but
essentially
you
know
sandbox
projects.
These
are
like
early
stage
projects.
We
kind
of
expect
them
potentially
to
either
be
successful
or
die.
A
There's
no
guarantees
incubating
things
are
a
little
bit
more
mature
and
we,
you
know,
make
a
little
bit
more
guarantees
there
and
then
graduated
or
projects
that,
like
your
company,
should
be
able
to
bet
on
with
no
concerns
or
worries
and
there's
a
whole
kind
of
process
to
guide
these
projects
through
this
potential
you
know
maturity
set
of
levels
a
lot
of
time.
When
we
do
these
meetings,
people
are
asking
like.
How
do
I
get
a
project
and,
like
you
know
how
this
work?
It's
a
fairly
simple.
A
Sandbox
is
very
easy,
generally
to
kind
of
get
into
there's
certain
kind
of
qualifications
that
you
have
to
meet
as
part
of
the
sandbox
application
and
they're
generally
reviewed
on
a
one
to
two
months
basis.
But
it's
meant
to
be
kind
of
very
lightweight.
We
don't
do
a
lot
of
marketing
support
for
sandbox
projects,
but
the
goal
is
to
kind
of
make
it
easy
to
kind
of
get
in
and
get
cultivated
within
the
organization,
incubation
and
graduation,
the
bar
is
significantly
higher.
A
A
You
know
I'm
not
going
to
go
into
this
in
in
detail,
because
I
think
cornelia
did
a
fantastic
job
of
not
talking
about
the
tags
if
you
attended
keynotes,
but
essentially
what
we've
done
is,
as
the
cncf
has
grown
into
over
100
projects,
it's
just
very
hard
to
potentially
have
just
a
toc
focus
and
support
all
of
them.
So
we
broke
up
into
different
kind
of
focus
areas
based
on
what
people
were
interested
in.
So
we
have
things
that
cover
security
storage,
run
time,
observability
and
so
on.
It's
all
broken
apart.
A
You
know,
based
on
what
people
you
know,
care
about,
and
focus
on.
These
tags
basically
serve
as
kind
of
an
advisory
function.
They
help
the
toc
with
potentially
reviews
and
provide
input
based
on
their
kind
of
specialties,
because
not
everyone,
the
toc,
may
be
an
expert
on
say
observability,
and
this
has
kind
of
helped
us
scale
as
an
organization
has
been
super.
A
I
think
useful
from
my
perspective,
so
I'm
gonna
kind
of
you
know
go
through
I'm
gonna
kind
of
skip
and
gloss
over
the
you
know
tags
if
people
have
any
particular
questions
on
each
of
these
things,
we're
happy
to
kind
of
go
through
them,
but
I
think
cornelia
did
a
good
job
kind
of
covering
some
of
these
in
the
keynote
which
is
also
in
line.
You
know,
I
think,
really.
You
know
we
kind
of
want
to
treat
this
as
more
of
kind
of
an
interactive.
You
know
discussion.
A
A
But
you
know
the
whole
idea
is
to
make
this
kind
of
an
open
in
discussion
to
get
input
from
the
community
and
help
us
evolve
and
become
a
better
organization.
So
you
know
question
to
our
probably
to
to
toc
members.
So
you
know,
we've
grown
from
you
know
one
project
from
kubernetes
to
kind
of
you
know
that
was
kind
of
a
kernel
and
we've
expanded
to
you
know
nearly
120
projects
that
cover
all
kind
of
aspects.
A
You
know
do
you,
you
know
like
what
do
you
think
is?
Potentially
you
know
missing.
You
know
in
that,
like
landscape
of
projects
that
you
know
we
need
to
kind
of,
you
know
potentially
seek
or
go
after
or
you
know,
maybe
you
have
from
your
end
experience
working
with
you
know,
customers
or
end
users
or
from
actually
you
know
usage
within
your
organization.
What
do
you
think
kind
of
holes
are
or
missing?
Currently
you
know
in
kind
of
the
large
landscape
that
we've
built
out
in
this
organization
over
the
last
six
years.
B
I
think
we
talked
about
this
recently
and
I'm
trying
to
remember
what
we
talked
about
then,
but
I
certainly
have
you
know
some
thoughts
along
those
lines.
I
think
that
one
of
the
areas,
if
I
recall
correctly,
that
we
talked
about
was
it
really
tracks
against
what's
happening
in
the
industry
as
a
whole,
and
one
of
those
things
of
course,
is
more
and
more
more
and
more
distribution,
and
I'm
talking
about
the
edge
and
yeah.
B
B
C
Yeah,
so
maybe
maybe
also
because
of
my
background,
I
think
one
area
that
is
also
kind
of
interesting
is
all
the
ml
machine
learning
things
so
a
lot
of
projects
around,
but
it's
it's
not
really
clear
where
they
fit.
Even
if
we
go
to
the
tags,
when
we
start
reviewing
machine
learning
projects,
it's
it's
like
do
we
go
run
time
or
which,
which
advisory
group
fits
the
best,
because
it
kind
of
covers
a
lot
of
things.
C
I
think
that
area
will
also
be
quite
important
and
the
other.
The
other
part
is
this
trend
to
to
manage
things
that
are
not
necessarily
related
to
containers
within
this
kind
of
cloud
native
world.
Integrating
resources
like
projects
like
crossplane,
what
they
are
trying
to
do
all
this
kind
of
bringing
to
to
this
ecosystem,
things
that
are
were.
A
A
There
anything
else
like
particularly
from
you
know
you
work
basically
at
a
research
lab
right.
You
know
I
remember
back
in
the
university
we're
like
working
on
things
like
slurm
and
using
that,
like
as
a
whole
like
if
you
ever
attend.
You
know
an
hpc
conference
like
super
compute.
It
seems
like
a
whole,
weird,
parallel
universe
of
folks
that
are
doing
distributed
computing
at
scale
and
have
been
doing
it
for
a
while,
and
then
you
come
to
kubecon.
C
Yeah,
this
is
something
that
we
we
also
deal
internally,
because,
as
the
trend
goes
to
to
running
things
on
kubernetes,
then
why
not
do
all
the
rest
as
well.
If
we
have
all
the
experience
and
knowledge
on
it,
there
are
some
barriers
that
are
more
technical
things
like
there's
a
lot
of
efforts
with
things
like
rootless
containers
to
run
like
in
hpc
environments,
which
are
kind
of
more.
I
don't
know
more
tight
in
comparison
to
to
what
we
do
elsewhere
and
other
things
like
fair
share,
more
advanced
scheduling
in
these
tools.
C
These
are
all
things
that
are
ongoing.
I
saw
a
couple
of
talks
actually
here
at
kucon,
related
to
advanced
scheduling,
adding
things
like
fairness
and
better
priority
definitions
on
scheduling.
So
this
this
is
coming.
I
don't
know,
I
don't
know
how
much
will
be
like
in
the
core
of
something
like
kubernetes
or
or
other
projects
that
will
will
be
plugged
in,
but
there's
a
place
ruthless.
A
C
B
Which
scares
me
too,
but
I
think
what
you're
talking
about
what
I
think
is
really
interesting
in
this
hpc
space.
Is
that
there's
all
sorts
of
protocols
in
place
for
being
able
to
treat
this
highly
distributed
system
which
we
have
to
have,
because
we
need
it
for
scale
as
a
single
system
and
and
most
of
what
we
do
when
we
still
talk
about
kubernetes.
We
talk
about
scheduling
things
on
a
cluster,
but
what
happens
now
when
we
need
to
schedule
our
hpc
workloads
across
clusters
and
maintain
state
across
those?
It's
it's
a
it's
a.
C
A
Yeah
definitely
like
if
you
ever
have
attended
kind
of
both
events.
It's
just
so
strange.
It's
like
literally
parallel
with
worlds
that
just
don't
talk
to
each
other
as
as
much
so.
What
kind
of
one
more
question
before
we
kind
of
turn
over
the
audience
and
one
one
theme
that
has
kind
of
come
up
in
this
conference,
at
least
that
I've
been
you
know
talking
to
a
lot
of
you
know,
end
users
and
and
even
vendors.
This
whole
notion
of
like
security,
seems
to
be
top
of
mind.
A
For
for
everyone
right,
you
know,
securing
the
supply
chain
definitely
seems
to
be
a
theme.
You
know
from
your
perspective,
on
on
the
toc.
Do
you
see
you
know?
What
are
your
thoughts
on
how
we
can
enable
projects
you
know
within
our
eq
system
to
be
essentially
more
successful?
You
know
at
this.
What
can
we
kind
of
do
to
kind
of
improve
the
situation?
We
do
have
some
practices
in
place.
A
We
do
some
security
audits,
but
it
just
feels
you
know
we
have
our
own
set
of
projects
in
cncf,
120
or
so,
but
then
all
those
120
or
so
products
depend
on.
You
know
tens
of
thousand
dependencies
that
have
different.
You
know
levels
of
security
and
something
you
know
I
think
about
now
on
on
probably
like
a
daily
basis
and
definitely
has
kind
of
permeated
a
portion.
You
know
of
of
of
this
conference.
B
Yeah
I
mean
one.
The
first
thing
I
would
say
is
of
course,
there's
the
security
of
security
audits,
of
the
projects
that
that
we
have
within
the
cncf,
but
I
just
actually
attended
the
pancake
breakfast
this
morning
and
the
topic
was
security
there
and
what
what
is
so
interesting
is
that
I
think
that
this
whole
security
space
in
general,
the
way
that
enterprises
are
still
thinking
about
it
is
they're.
B
B
How
do
you
audit,
when
things
are
constantly
changing
security,
used
to
have
this
notion
of
well
we're
going
to
get
everything
super
stable
and
then
we're
not
going
to
change
it
and
that's
how
we're
going
to
ensure
security?
But
now
what
does
security
mean
in
a
constantly
changing
world,
and
so
I
think,
I
think
that's
one
area
where
we
can
certainly
do
an
awful
lot.
B
I
had
posed
the
question
this
morning
of
kubernetes,
be
I
and
again,
convergence
is
one
of
my
favorite
words
in
cloud
native,
because
in
distributed
systems,
that
is
the
pattern
that
works
and
that's
why
kubernetes?
One
of
the
reasons
why
kubernetes
got
so
ubiquitous
is
because
it
it
changed
the
fundamental
model
to
this
model
of
convergence,
and
it
has
a
language
for
the
decl
declared
the
desired
state.
B
B
A
So
you
know
I'm
happy
now,
I
think,
to
kind
of
turn
over.
Maybe
the
audience
for
some
questions,
there's
basically
a
few
kind
of
wrap-up
things
in
terms
of
you
know.
I
just
want
to
make
sure
people
aware
that
toc
generally
is
very
open
for
people
coming
in.
I
know
sometimes
people
new
to
the
community
get
a
little
bit.
A
You
know
they
they
get
a
little
bit
worried.
Sometimes,
oh,
I
don't
know.
If
I
can
approach
him.
I
guarantee
you.
If
you
kind
of
reach
out
to
folks,
everyone
is
very
welcome,
maybe
maybe
a
little
bit
busy,
but
overall
everyone's
kind
of
open
and,
and
you
know
willing
to
kind
of
help
out
as
as
time
a
lot.
One
important
thing
to
note
is:
I
do
want
to
kind
of
encourage
folks
that
we
do
have
elections
basically
coming
up
in
2022.
A
B
B
You
wrote
a
book
on
cloud
native
patterns,
you're
ready
and
I
was
like
really
and
she
said,
yeah
you're
ready
and
that's
how
I
came
to
do
it.
So
for
all
of
you
who
are
thinking,
I
would
love
to
do
that
someday.
I'm
not
ready,
there's
a
really
good
chance
that
you
are
ready
and
step
forward
or
work
with
somebody
to
step
forward
and
if
it
doesn't
work
the
first
time
that's
okay,
too,
but
I
just
really
want
to
encourage
all
of
you
because
most
of
you
probably
think
that
you're
not
ready.
A
B
Good
question:
I
can
certainly
answer
that,
so
the
toc
itself
does
not
choose
the
tag
chairs.
We
approve
them
and
I
can't
think
of
a
single
instance
where
we
haven't
it's.
The
tag
chairs
are
nominated
in
and
selected
by
the
tags
themselves
and
in
virtually
every
case,
it's
they
make.
The
decision
be
based
on
somebody.
B
Who's
been
already
contributing
to
the
tag
and
has
been
involved
in
the
tag
and
shows
the
passion
for
the
charter
that
the
tag
has
and
they
bring
them
forward
and
just
as
a
as
a
point
of
governance
in
case
there
is
some
kind
of
conflict,
that's
the
really
the
role
that
the
toc
would
play,
but,
as
chris
said,
even
when
it
comes
to
governance
that
whole
process
by
design
there's
it's
a
whole
bunch
of
autonomy
is
built
into
those.
So
we
are
the
toc
that
approve
things,
but
things
work
pretty
well.
A
D
B
E
C
C
B
D
F
A
Is
amy,
but
we
have
staff
that
you
know
essentially
facilitates
all
kind
of
the
process
stuff
we're
all
about.
You
know
public
voting
and
public
responses.
You
know
there's
been
times
where
I
would
say
by
the
time
something
gets
to
a
vote,
there's
a
lot
of
consensus
built,
but
we
do
allow
community
members
to
essentially
also
vote,
but
toc
members
are
the
ones
that
have
binding.
You
know
votes
at
the
end.
Now
that
I
think
about
it
is
from
an
external
perspective.
A
If
you
just
join
that
list
and
you're,
seeing
like
plus
one
and
b's
fly
by,
or
you
know
like,
maybe
we
need
to
kind
of
document
that
and
make
that
a
little
bit
more
transparent
of
what
these
things
mean,
because
that's
kind
of
this,
this
language,
that
we've
kind
of
codified
you
know
on
our
own,
obviously
inspired
from
the
apache
foundation
and
so
on.
You
know
how
they
vote.
B
And
I
would
encourage
everybody
to
if
you're
interested
in
a
topic,
and
you
want
to
cast
a
vote.
Please
do
because
we
as
that's
something
that
we
actually
depend
on
as
a
technical
oversight
committee
is.
That
is
one
of
the
ways
that
we
get
the
pulse
of
what
you
all
what
the
the
community
as
a
whole,
because
by
the
time
it
goes
to
vote
we've
we've
had
we
we've
had
discussion
internally
within
the
toc
publicly.
B
We,
the
the
tags,
have
done
some
due
diligence.
The
projects
have
done
some
due
diligence.
There
has
been
a
an
open
call
for
comments
on
the
incubation
proposal,
for
example.
So
that's
one
ability
one
way
for
the
the
broader
community
to
have
input,
but
then,
when
it
comes
to
that
final
vote,
we
all
I'm
sure
you
do
as
well.
We
that's
that's.
Definitely
a
bit
of
a
pulse.
C
C
E
At
it,
though,
it's
it's
really
just
trying
to
define
the
projects
around
the
operating
system.
If
you
may
right,
so
it's
sort
of
centralized.
So
my
question
to
you
is:
have
you
ever
looked
out
in
the
on
the
outside
of
this?
So,
for
instance,
one
obvious
one
would
be
the
verticals
so
different,
verticals,
like
banking
retail.
A
The
way
the
kind
of
linux
foundation
works
is
generally,
it
is
a
foundation
of
foundations
right,
so
cncf
is
one
we
have
our
own
like
little
landscape.
You
know,
I
don't
know
if
many
people
know
about
this,
but
there's
a
website
called
landscapes.dev
right.
If
you
go
there,
we
actually
have
a
lot
of
different
other
landscapes
for
different
organizations.
So,
like
the
graphql
foundation,
has
a
landscape.
Hyperledger
has
a
landscape
finos,
which
is
the
fintech
open
source
foundation
of
valencia.
A
Has
the
landscape
lfai
foundation
has
land
so
there's
a
lot
of
different
landscapes,
there's
actually
ones
that
have
been
built
by
external
folks
that
want
to
do
this.
So
if
there
was
another
community
out
there
that
wanted
to
go,
take
advantage
of
the
technology,
and
so
on
that
we
built
they
could
go,
build
their
their
own
landscape.
A
I
mean
that
whole
project
really
came
out
of
you
know
the
late
dane
khan
and
I
just
tracking
all
this
crap
in
spreadsheets
and
kind
of
got
sick
of
it
and
making
a
joke
one
day
like
what
happens
if
we
open
sources
and
make
the
community
do
it
for
us
and
it
kind
of
worked
out
at
the
end
of
the
at
the
end
of
the
day.
But
the
code
is
all
open,
source
and
available
for
anyone
to
to
take
and
take
and
play
with.
We've
got
a
few.
C
A
G
Okay,
thank
you
for
taking
my
question
and
yeah.
We
can
still
make
the
event,
so
I'm
from
apple.
So
my
question
was
yeah.
I
am
a
kubernetes
contributor
and
the
main
in
the
sixth
scheduling
six
scalability.
As
we
are
now
developing
more
advanced
features.
It
often
requires
collaboration
coordination
across
the
sea
or
different
working
groups,
even
sometimes
like.
We
are
have
some
badge
support.
A
Can
you
help
us?
Can
you
help
bridge
these
two
communities?
Together
we
held
meetings,
we
had
tc
members
kind
of
bridging
and
kind
of
helped
collaboration
and
open
telemetry
was
born
and
I
think
the
world
is
is
better
for
it.
But
generally
these
things
kind
of
happen
from
enough
people
showing
up
and
making
requests
of
the
toc
and
they'll
kind
of
kind
of
guide,
and
you
know
deal
with
that.
But
it
has
to
come
from.
You
know
the
communities,
you
know
themselves
we'll
bring
people
together
and
do
our
best
to
to
resolve
things.