►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from April 17-21, 2023. 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.
Kubernetes Steering Committee AMA - Moderated by Christoph Blecker, Red Hat
Speakers: Bob Killen, Nabarun Pal, Benjamin Elder, Tim Pepper, Christoph Blecker, Stephen Augustus
The steering committee is tasked with decision-making and oversight with all things related to Kubernetes. This panel discussion is a chance for some navel gazing on where we are today, what got us here and where we are headed to next. This will also be a chance for the steering committee to meet face to face with their constituents in the community and wider ecosystem. https://github.com/kubernetes/steering
A
A
A
A
So
if
you
have
been
around
the
kubernetes
community
for
even
a
moment,
you'll
probably
know
we
have
plenty
of
these
things
called
special
interest
groups
or
sinks.
Each
of
these
cigs
either
has
a
domain
specific
interest
or
they
have
a
horizontal
interest
in
the
community.
So
domain
specific
ones
are
where
things
like
node
or
Network
sigs
that
are
responsible
for
a
particular
part
of
the
kubernetes
code
base
and
the
kubernetes
stack.
A
And
then
we
also
have
horizontal
sigs
that
have
more
wide
reaching
mandates
across
the
community
in
order
to
collaborate
between
lots
of
different
people,
doing
lots
of
different
things
on
a
particular
subject.
A
couple
examples
of
those
would
be
Sig
architecture,
that's
the
arc,
so
that's
the
architectural
direction
for
the
entire
project
or
sign
contributor
experience
that
is
responsible
for
the
contributing
flow
and
the
both
the
experience
of
new
contributors
onboarding
into
the
project,
as
well
as
providing
services
to
experienced
contributors
like
those
who
are
leading
these.
A
These
different
cigs,
we
also
have
bodies
called
working
groups.
Working
groups
are
time-bound
collaboration
efforts
within
the
community
that
are
focused
on
a
specific
set
of
outcomes.
Their
goal
is
to
spin
up
to
provide
a
forum
to
meet
and
collaborate
on
a
particular
effort,
and
then,
when
they're
complete
in
that
effort,
then
they
spin
down.
A
A
We
have
the
code
of
conduct
committee,
which
is
responsible
for
overseeing
our
code
of
conduct,
response
efforts
and
doing
things
like
helping
resolve
issues,
provide
resources
and
ultimately
providing
a
a
place
for
people
to
go
to
ensure
that
we
are
a
friendly,
safe
place
for
folks
to
collaborate,
and
then
we
have
the
steering
committee.
The
steering
committee
is
the
top
governance
body
within
the
project,
where
we
do
two
things
number
one.
We
are
the
key
liaison
between
the
kubernetes
community
and
The
World
At
Large.
A
So
those
are
things
like
our
relationships
with
the
cncf,
our
relationships
with
other
open
source
communities
as
well
as
anytime.
There's
like
an
external
query
at
somebody
who
doesn't
know
who
to
talk
to
within
the
in
the
community.
They
will
typically
come
to
kind
of
steering
first
and
we
can
direct
them
to
the
right.
The
right
folks.
A
The
other
thing
that
we
do
is.
We
are
ultimately
the
body
that's
responsible
for
governance
inside
the
project,
so
that
includes
setting
things
like
you
know:
the
rules
around
sick,
Charters
approving
when
new
sigs
are
created
and
any
responsibility
that
we
haven't
delegated
out
to
a
Sig
to
ultimately
be
responsible
for
Falls
up
to
the
steering
committee.
We
are
not
a
technical
body.
A
We
strive
basically
across
the
board
anything
that
we
can
find
the
right
people
and
delegate
to
we
will,
but
for
anything
that
there
isn't
a
solution.
Already
and
we
need
to
kind
of
figure
out
a
particular
problem
as
far
as
who
should
or
the
right
stakeholders
to
address
it
and
things
like
that,
those
kind
of
all
roll
up
to
the
the
steering
committee.
A
B
I
want
to
give
context
that
I
asked
the
same
question
in
the
cncf
code
of
conduct,
working
group,
brainstorm
and
I
feel
like
it's.
So
it's
worthwhile
asking
it
here.
I
recognize
that
the
majority
of
the
membership
of
this
of
the
student
Community.
Obviously
it's
Community
voted
in,
but
the
majority
other
than
number
one.
Congratulations
recently
on
being
elected
is
North,
American
based
and
I'm
wondering.
B
Is
there
any
kind
of
room
for
having
some
kind
of
minimum
requirement
of
having
a
member,
possibly
from
another
geography
outside
of
North
America,
as
the
group
has
continued
to
be
voted
in
by
the
by
the
community?
I
ask
because
there's
a
lot
of
different
perspectives
and
a
lot
of
different
geographies
that
I
feel
like
sometimes
have
to
be
fitted
into
a
North
American
mindset
that
sometimes
we're
not
really
possibly
looking
at
in
the
right
way.
C
I
think
there
is
a
possibility,
because
here
a
few
years
back,
so
there
is
a
possibility
for
people
from
other
geographies
to
be
involved
and
get
elected
to
the
steering
committee.
I.
Think
the
Mantra
which
works
is
like
keep
on
like
contributing
to
other
areas
of
the
communities
where
you
get
more
visibility.
And
then
you
eventually
like
grow
up
the
ladder
and
then
yeah.
A
So
what
what
I'd
say
is
that
we
are
a
representative
democracy
inside
of
kubernetes.
We
have
seven
seats
on
the
steering
committee,
but
we
represent
tens
of
thousands
of
Developers
I.
Don't
think
that
there
is
necessarily
A
Way
to
lock
in
and
guarantee
that
specific
groups
within
the
project
are
going
to
be
directly
represented
on
this
body.
A
But
not
there
isn't
a
guarantee
that
people
from
all
the
geographies
that
we
have
within
the
kubernetes
community
are
going
to
necessarily
have
the
time
to
do
it.
We
have
had
folks
like
nebrun,
who
have
been
elected
Nikita
previously,
so
we
have
had
folks
outside
of
North
America
that
have
got
elected
for
their
contributions,
but
putting
restrictions
and
guarantees
is
tough.
The
one
restriction
that
we
do
have
on
steering
in
order
to
make
sure
that
we
continue
to
represent
the
community's
voices.
A
There's
maximal
representation
rules
on
the
steering
committee,
so
I
believe
it's
no
more
than
one-third
of
the
community.
No
more
than
one-third
of
the
committee
can
be
from
the
same
employer
at
the
same
time.
So
in
a
seven
member
body,
that
means
no
more
than
two
seats
can
go
to
the
same
employer
while
our
while
are
like
in
our
kubernetes
values
document.
One
of
the
things
that
we
say
very
clearly
is
company
over
or
community
over
company.
A
You
know
another
very
common
saying
that
goes
around
is
like
different
companies
but
same
team.
We're
here
to
to
represent
the
community
and
we
all
kind
of
like
take
off
our
corporate
employer.
Hats
like
we
all
have
employers
that
that
you
know
at
least
to
a
degree,
pay
us
to
be
here,
but
we
don't
represent
their
interests
at
the
steering
committee
level,
we're
here
to
represent
and
do
what's
right
for
the
community.
A
If
we
put
restrictions
on
like
oh
the
seventh
seat
on
the
committee,
has
to
go
to
somebody
outside
of
North
America
that
it
might
not
always
go
to
the
right
person
who
has
enough
time
to
be
able
to
to
fully
execute
on
that
job,
I'd
like
I
would
be
more
I
would
be
more
kind
of
looking
towards.
What
can
we
do
to
more
purposefully
engage
with
folks,
so
they
know
what
we
do
and
are
interested
in
running.
D
So
yeah
so
every
at
the
end
of
every
steering
committee
election.
What
we
do
is
a
retrospective
with
the
election
officers
right
that
gives
us
a
Time
an
opportunity
to
like
reflect
on.
Do
we
like
the
platform?
Do
we
like
how
we
engage
with
the
community
to
get
people
involved
and
interested
in
in
running?
D
D
E
Got
a
couple
thoughts,
so,
first
of
all,
thank
you
for
raising
this
I
think
it's
an
important
issue,
so
you
you
specifically
called
out
North
American
I'll
jokingly,
refer
to
Christoph,
he's
North
American,
but
he's
not
us
American
and
on
yeah.
On
a
few
occasions,
though,
this
has
come
up
where
he
has
been
able
to
represent
an
international
audience
in
a
way
that
us
Americans
weren't,
quite
aware
of
so
there
is
a
little
bit
in
navaroon.
E
Also
now
brings
a
different
perspective,
but
this
has
been
a
huge
issue
for
the
project,
even
just
even
if
we're
all
in
the
same
nationality,
exact
same
culture,
we
have
different
time
zones
and
it's
a
big
problem.
The
release,
team
and
Sig
release
have
done
a
good
job
over
the
years
of
modeling
trying
to
shift
the
times
around.
But
it's
hard
I
know
on
another
committee.
Now
everyone
had
a
lot
of
challenges
around
time
zone
I
know
Nikita
with
steering
had
challenges.
It's
a
big
deal.
E
We
as
a
steering
is
responsible
for
defining
and
defending
the
values
of
the
project,
but
values
become
human
squishy
things
and
we
all
have
to
step
to
valuing.
Having
empathy
for
others
who
are
somewhere
different
and
and
sharing
some
of
the
consequences
of
that
and
it's
a
challenge,
I,
don't
know
that
we
can
prescriptively
define
something
but
I,
also
kind
of
like
the
idea
of
maybe
picking
a
few
things
and
codifying
them
and
see
seeing
what
happens.
It
wouldn't
be
a
a
terrible
thing
to
try
and
then
one
last
thing
looking
at
us
here.
E
F
I'm
new
to
Siri
again
I'm,
really
interested
in
ideas
for
this
one
thing
I'd
say,
is
that
you
know,
as
long
as
it
is
a
community
elected
position
with
only
maximum
representation
from
the
employers
for
Optics
and
so
on.
One
of
the
difficult
things
is
even
getting
people
visibility
from
other
employers
at
our
sick
testing.
Talk
that
I
gave
we
wound
up
with
four
googlers,
because
one
of
them
joined
Google.
Since
we
planned
the
talk
and
it
was
hard
to
find
other
people
that
were
willing
to
come.
Do
this.
F
Even
some
people
that
want
to
come
their
employers
won't
send
them.
I'm,
really
interested
in
ideas.
I've
been
working
a
lot
to
try
to
bring
up
leadership
in
my
Sig
and
I
have
mostly
wound
up
with
other
people
like
Google,
because
I'm
struggling
to
get
other
people
engaged
it's
hard
to
get
employers
behind
people,
and
some
of
the
big
employers
are
very
North
America
based.
G
So
one
least
quick
comment
going
back
to
like
the
the
Retro
and
some
of
the
ideas
were
originally
brainstorming
to
try
and
get
people
more
exposure,
like
we've
done
sort
of
steering
amas
for
people
that
are
potentially
running
for
steering
to
come.
Ask
questions,
but
there
isn't
really
a
good
place
for
the
community
to
ask
the
steering
candidates
that
people
are
running
to
ask
questions,
so
you
do
sort
of
naturally
bias
towards
the
the
people
that
you
know
some.
You
know
hosting
some
again
like
amas
for
some
of
the
panelists.
G
C
Can
we
make
some
sort
of
policy,
may
not
be
a
mandating
policy
but
suggestions
to
sigs
on
how
they
can
learn
from
what
has
been
done
already
in
the
past
to
promote
like
people
from
other
geographies
to
at
least
they
come
up,
show
up
in
the
six
and
show
just
show
up
and
then
become
like
and
then
even
in
this
committee.
We
have
to
also
work
on
like
how
do
we
work
on
asynchronous
communication?
How
do
we
have
lazy
consensus?
C
Sometimes
some
things
become
like
really
time
bound.
You
have
to
like
get
decision,
maybe
possibly
in
a
couple
of
hours
where
you
can't
have
like
possibly
include
like
everyone,
but
in
most
situations
in
all
across
the
community.
Probably
we
can
like
replicate
what
has
been
done
and
like
good
learnings
from
running
release.
Teams
running
mentorship
programs
and
I
I
believe
that
is
how
we
can
have
like
representation
across
geographies
and
any
other
criteria
that
you
define.
Geography
is
just
one
one
of
them.
H
I
think
Navarone
answered
the
question
that
I
was
thinking
about
was
so
we've
been
talking
about
this
problem
since,
like
when
I
was
on
the
steering
company,
which
was
I,
don't
know
like
two
years
three
years
ago,
we've
mostly
been
talking
about
the
problems.
What
ideas
do
you
have
in
mind
to
solve
this
like
there
will
be
a
next
election
coming
like
another
election
coming
up
next
year?
How
will
you
ensure
that
we
have
a
diverse
candidate
for
the
election
or
be
geography
is
beat
I,
don't
know
whatever
right
like?
H
E
C
F
Can't
like
publicly
endorse
anyone
else,
but
we
can
go
talk
to
people
and
encourage
them
to
participate
and
I.
Think
that's
something
that
we
all
need
to
be
thinking
about.
Doing
is
like
who
do
we
go
encouraged
to
participate,
and
how
do
we
help
them
understand
like
what
to
do
to
to
get
to
that
point?.
E
F
Yeah,
as
a
googler
We
call,
we
even
we
joke
about
this
internally
Google
Standard
Time,
because
they
used
to
literally
even
set
the
servers.
This
way,
it's
just
completely
permeates
and
it's
very
hard
to
to
get
people
to
undo
these
things,
but
we
have
to
push
on
that.
We
we
need
to
as
the
economy
slows
down,
we,
we
cannot
be
picky
about
where
people
are
from
where
they're
coming
from.
We
need
contributors
from
everywhere
and
we
need
to
make
it
easier
to
participate.
G
We
start
the
meeting
on
like
our
normal
meeting
is
Wednesday
at
noon.
Pete
or
CET,
and
then
we'd
start
the
meeting
on
Tuesday
the
the
slack
meeting
on
Tuesday
and
conclude
it
on
like
Thursday
night,
where
each
topic
was
basically
a
slack
thread
and
then
we'd
take
all
the
the
slack
threads
and
roll
them
up
into
meeting
notes
to
try
and
and
just
be
more
sort
of
like
async
friendly.
There
are
options
for
us
to
explore
there.
G
The
other
thing
is
like
I,
really
think
that
the
the
gateway
to
steering
in
general
is
our
like
Sig
in
working
group
leadership.
So
like
making
sure
that
we
have
a
pipeline
getting
diverse
candidates
into
these
leadership
positions
is
the
eventual
path
to
like
steering
these
other
things.
We've
been
trying
to
do
it
for,
like
We've,
seek
contribute.
Experience
is
running
a
mentor.
A
leadership
Mentor
cohort
right
now
to
try
and
bring
more
diverse
people
into
our
leadership
positions.
D
So
yeah
again
I,
don't
think
we
have
any
Perfect
Solutions
for
this,
but
there
are
like
when
I
was
thinking
about
the
sick
release,
stuff
and
the
timing,
and
for
you
know
when,
when
Tim
and
I
were
doing
it
I
think
for
years
we
were
just.
We
were
like
okay,
well,
the
release
meetings
at
this
time,
and
we
didn't
realize
that
we
were
just
kind
of
biasing
towards
Google
Standard
time
without
thinking
about
it.
D
You
should
be
actively
looking
to
to
sponsor
leaders
right,
not
just
on
not
just
on
the
group
level,
but
on
a
personal
level.
You
you
do
need
that
by
the
time
we
get
to
the
steering
committee,
AMA
we're
pretty
deep
into
the
process,
and
those
are
you
know.
Those
are
folks
who
already
knew
they
wanted
to
do
it
and
not
so
much
the
folks
who
needed
the
extra
push
to
say
that
they
can
do
it.
So
I
think
that
we
need
to
take
a
more
active
stance
in
doing
that.
A
A
One
thing
that
we
have
been
talking
about
and
trying
to
push
forward
is
the
concept
of
terms
in
those
leadership
roles
as
well.
So
steering
already
has
terms
there's
like
an
election
cycle,
and
we
all
have
a
a
particular
term
that
we
are
we're
elected
for
and
taking
on,
but
in
those
Sig
leadership
positions
like
I
will
freely
admit.
I
I'm
guilty
of
this
too
I've
been
a
contrivex
TL
for
six
years,
something
like
that
which
is
Good
from
a
stability
standpoint.
F
Briefly,
thank
you
terms
have
been
one
of
my
pet
issue
for
a
while
now,
when
I
got
nominated
in
the
Sig
ever
since
then,
I
realized
that,
like
this
is
broken,
you
know
we
have
all
this
wonderful,
ranked
Choice
voting
maximum
representation.
We
have
all
these
things
for
steering,
but
then
steering
turns
around
and
delegates
most
things
to
the
sigs
and
the
way
cigs
tend
to
run
things
is
someone
decides
to
step
down?
They
nominate
someone
in
the
mailing
list.
F
It's
a
public
announcement,
no
one's
going
to
show
up
and
say
no,
that
person
is
now
the
chair,
that's
it
and
it
is
for
as
long
as
they
want
it.
There's
no
way
to
rotate
people
out
so
in
lieu
of
that,
with
a
close
rate
of
the
Charter
One
thing
that
we
tried
this
year
very
recently
in
sick
testing
is
that
there
isn't
a
actual
hard
cap
set
on
these
positions,
so
just
trying
to
find
some
people
willing
to
do
it
and
add
more
people
and
not
keep
it
to
the
same
two
or
three.
F
While
we
figure
out
how
we
checkpoint
and
rotate
out
people
just
go
ahead
and
bring
on
some
new
ones
immediately,
I
think
that
we
have
got
to
get
people
visibility,
but
I
also
need
people
willing
to
step
up,
because
even
in
these
other
positions
reaching
out
to
people
that
have
been
participating
in
the
groups,
it
was
hard
to
find
people
willing
to
take
on
these
positions.
And
if
you
don't
take
on
positions
of
visibility,
you're
not
going
to
get
elected
to
the
steering.
I
Yeah,
so
I
want
to
shift
gears
a
little
bit
here
so
cubecon,
contributor
Summit.
These
are
great
places
to
facilitate
these
Broad
community-wide
discussions.
But
what
I
want
to
know
is
how
can
we
keep
that
going
because
what
I've
noticed
ever
since
keepcoin
EU?
That
was
my
first
coupon.
So
that's
my
point
of
reference.
So
what
whatever
I've
noticed
since
then,
is
that
we
have
these
really
important
discussions.
I
We
have
these
real
problems
that
we
need
to
try
and
address,
but
once
kubecon
is
done,
the
broader
Community
sort
of
either
loses
track
loses
context
and
then
so
on.
So
how
do
we
keep
that
discussion
going
because
I
love
the
community
and
I
want
to
do
my
part
in
helping
out
with
these
problems
in
some
small
way
or
the
other
right?
So
how
do
we
facilitate
that?
I
G
So
I
think
the
at
least
with
kubecon
EU
this
year.
The
biggest
thing
is
that
we
didn't
assign
notetakers
and
we
didn't
actually
record
the
AIS
from
the
very
good
discussion
that
was
honestly
like
a
our
our
bad
is
organizers,
I
think
going
forward
a
we
do,
have
those
notes
and
we
do
need
to
like
post,
like
post
cubecon
actions
and
to
turn
them
into
issues,
turn
them
into
AIS,
and
things
like
that.
That
can
be
tracked
and
work
assigned
and
worked
on.
G
F
For
terms
there's
an
issue
from
performance
during
the
that's
open
that
we
just
need
to
bring
the
discussion
back
to
if
you're
interested
in
that
topic,
I
can
also
tell
you
that
now
that
I
can
see
kind
of
some
of
the
backlog
and
talk
to
folks
on
steering
about
some
of
the
things
that
they're,
you
know
not
publicly
discussing,
or
things
have
come
up
with,
like
code
of
conduct
or
whatever
that.
Unfortunately,
at
the
moment,
these
folks
are
spending
a
lot
of
time
doing
very
visible
or
non-visible
firefighting.
F
So
we,
you
know
we
could
use
some
help,
reminding
us
to
keep
coming
back
to
these
things.
As
I
could
tell
you
my
whole
week
this
week
has
just
been
trying
to
stop
the
kubernetes
project
from
shutting
down
all
of
our
infrastructure,
because
we're
about
to
exceed
our
gcp
credits
like
next
week
and
getting
getting
the
cncf
and
other
folks
to
take
this
seriously
and
and
fix
this
and
we're
okay
now.
F
But
we
have
just
been
running
around
talking
to
people
trying
to
sort
that
out
and
it's
not
very
visible,
and
it
makes
it
easy
to
forget
about
the
other
things
that
were
you
know
the
other
important
things
we're
working
on.
You
know
I,
don't
know
about
everyone
else,
but
it's
hard
to
keep
on
top
of.
F
So,
if
you
can
come
back
to
one
of
these
things
or
or
file
an
issue
or
email
steering
or
just
anything,
to
bring
us
back
to
these
topics,
I
mean
some
of
it
needs
to
be
on
us,
but
also
understand
that,
like
there's
a
lot
of
things
going
on
that,
not
everyone
can
see
for
various
reasons
talking
to
the
cncf
and
their
closed
governing
board
session
or
whatever.
That
is.
I
A
Other
other
very
common
ways
to
engage
with
us,
so
I
got
some
of
them
up
on
the
screen.
As
far
as
our
our
email
lists,
when
our
meetings
are
all
our
meetings
are
recorded,
our
check
slack
Channel,
there's
also
a
couple
with
some
of
these
broader
discussions
around
like
how
should
we
govern
like
sigs
and
to
share
thoughts
and
best
practices
between
sigs
there's,
a
chairs
and
tech
leads
channel
in
slack
as
well,
where
all
of
our
kind
of
different
Sig
leaders
and
that
kind
of
stuff,
bounce
ideas
back
and
forth.
A
Most
of
our
sigs
are
self-governing
and
kind
of
set
some
of
these
policies
themselves.
But
then
there
are
discussions
between
okay.
How
do
we
share
best
practice
between
everyone
and
how
do
we
take
a
working
best
practice
and
codify
and
say
no?
Actually,
this
is
not
a
requirement
because
we
we
need
this
kind
of
ubiquity
across
the
community.
D
Yeah
to
to
Ben's
point
I
think
there
is
a
lot
of
time
consuming
and
emotional
work
that
happens
behind
the
scenes.
I
would
say
that
that
is
70,
if
not
more
of
the
job
and
and
like
sometimes
we're
able
to
reveal
what
is
actually
happening,
and
sometimes
these
are
conversations
that
are
happening
over
months
over
years
that
until
we
get
the
resolution,
we
we
can't
pop
out,
you
know
show
work
around.
It.
D
I
think
you
know
in
terms
of,
if
we're
talking
about
not
just
steering
like
one,
we
have
our
again,
we
have
the
repos.
We
have
the
mailing
list.
There
is
also
the
funding
repo
for
specifically
talking
about
funding
something
within
the
community.
Steering
helps
steering,
helps,
capture
and
and
execute
on
those
actions.
The
I
think
in
terms
of
like
any
time,
you're
coming
to
a
talk,
an
event,
a
contributor
Summit.
What
have
you
think
about
your
outcomes?
Right,
not
just
outcomes
for
you
outcomes
for
the
community.
D
We
are
all
in
this
together.
So
if
there's
something
that
you
want
to
see
happen
happening,
keep
pinging
people
about
it,
make
sure
it's
visible,
make
sure
you're
vocal
about
it.
There
are
lots
of
places
to
do
it
depending
on
the,
depending,
on
the
sake,
the
working
group.
What
have
you,
but
we
do
need
to
make
sure
that
we
are
keeping
the
work
as
visible
as
possible
and
that
we're
all
like.
We
should
all
know
that
we're
empowered
to
help
do
that
work.
So
it's
not
just
it's
not
just
a.
D
E
And
we
represent
all
of
you
so
hold
us
accountable.
It's
easy
to
open
an
issue
on
GitHub
Drive
conversation
there.
It
has
been.
It's
even
have
alluded
to
and
not
really
explicitly
stated
is
a
body
we
try
to
operate
from
a
consensus
basis.
So,
at
the
point
that
we
make
a
statement
on
something
on
behalf
of
the
project,
we
want
it
to
carry
weight
and
be
authoritative.
E
That
would
be
a
good
thing,
but
there
are
also
some
of
these
things
that
are
quite
fraught
and
we
have
to
be
a
little
careful
and
sensitive
on
how
we
discuss
and
explore
the
possibilities,
because
we,
we
don't
know
everything
and
it's
easy
for
each
of
us
individually
to
put
our
foot
on
our
mouth
or
perhaps
do
that
on
behalf
of
the
project.
So
there's
a
weird
balance
there
but
push
us.
We
we
report
to
you
the
community.
J
A
When
the
kubernetes
project
started,
we
had
a
much
larger
committee.
There
was
an
original
bootstrap
committee
that
was
just
a
whole
bunch
of
different
Community
leaders
getting
in
a
room,
just
kind
of
set
the
initial
Charter
and
figure
out.
How
do
we
govern
ourselves
because
we
had
no?
We
didn't.
We
didn't
really
have
a
lot
of
of
past
information
to
kind
of
go
on,
so
we
kind
of
had
to
Blazer
Blaze
our
own
trail
and
figure
out
how
we
were
going
to
govern
ourselves.
A
We
eventually
decide
to
scale
down
to
seven
seven
as
a
special
number
within
the
kubernetes
community
so
and
we
wanted
to
have
kind
of
an
odd
number.
So
if
we
needed
to
vote
on
things
that
we
would
be
able
to
kind
of
make
a
decision
to
move
forward,
it
has
actually
come
up
before.
Do
we
need
to
add
more
people
to
the
committee
in
order
to
expand
the
work
that
we've
done?
A
We've
also
had
discussions
around
reducing
the
size
of
steering
and
having
more
people
kind
of
out
in
the
community,
doing
things
and
reducing,
maybe
the
scope
of
what
steering
does
so.
We've
had
discussions
kind
of
both
ways,
but
every
time
we've
had
those
discussions
at
least
historically
we've
always
kind
of
come
back
to
No.
7
is
the
right
number,
at
least
for
now,
but
all
of
those
things
as
far
as
like
the
membership
and
makeup
of
the
community
are
all
kind
of
open
to
us.
A
To
kind
of
you
know
decide
what
our
what
our
destiny
is
and
do.
We
have
the
right
number
of
folks
kind
of
on
this
committee,
but
unless
we're
going
to
have
a
committee
of
tens
of
thousands
of
folks
we're
never
going
to
be
able
to
be
a
hundred
percent
of
the
community,
so
there's
always
going
to
be
some
degree
of
like
we
need
the
help
from
the
community
in
order
to
drive
things
forward.
E
I,
like
the
idea
of
having
broader
representation,
it
could
also
drive
us
more
towards
some
of
that
asynchronous
communication
and
written
communication
planning
is
an
example
on
a
couple
of
occasions,
and
we've
actually
tried
to
set
this
as
a
regular
meeting
point.
But
the
code
of
conduct
and
steering
committees
have
tried
to
have
joint
meetings
and
across
those
12
people.
It's
almost
never
happened
because
it's
impossible
to
get
together,
but
that
is
the
proof
point
that
if
we
want
to
do
more
representation,
we
got
to
shift
how
we
do
it
and
it's
it's
possible.