►
Description
Kubernetes Public Steering Committee Meeting for 20230710
A
My
name
is
Crystal
blecker
I'm
going
to
serve
as
your
host
a
reminder
that
these
Theory
committee
meetings
are
recorded,
we'll
be
posted
to
YouTube
as
well
as
we
abide
by
this
cmcf
and
kubernetes
code
of
conduct.
Please
be
excellent
to
each
other
if
you
need
any
Refreshers
on
that.
Go
check
out
the
code
conduct
in
the
community
repo.
C
B
B
B
E
Hi,
so
Jeremy
was
not
able
to
make
this
call
today,
but
Rita
and
I
are
here
and
I'm.
Super
I
just
want
to
say.
I'm
super
excited
about
this,
because
it's
so
important
and
the
the
discussion
that
Rita
and
Rita
can
speak
to
how
the
discussion
went
at
kubecon.
But
at
the
contributor
Summit
the
discussion
was
very
active,
very
interested
and
I.
Think
people
are
pretty
excited
about
this
Rita.
D
A
B
The
next
thing
is
the
sort
of
a
whip
PR
of
proposing
Sig
at
CD
the
chart.
All
that,
like
isn't
you
know,
nothing
is
a
good
State
but
they're,
essentially
looking
for
an
ack
from
steering
at
this
point
to
like
okay,
Etsy
D
is
cool
with
this
kubernetes
steering
is
good
with
this.
Now,
let's
actually
move
forward
and
figure
out.
You
know
all
the
details.
B
A
B
H
H
B
A
A
thought,
instead
of
maybe
us
enumerating
like
an
entire
list
of
all
the
things
they
need
to
do.
Is
there
anything?
Maybe
we
posed
the
question
back
to
them?
Is
there
anything
that
you
want
to
do
that
would
be
outside
of
our
normal
documented
processes
for
a
sake,
because
we've
already
got
like
30.
A
If
there's,
if
they're
looking
for
exceptions
to
what
our
Norms
would
be
because
they've
already
been
doing
a
thing,
then
that
could
can
and
should
be
something
that
maybe
we'll
review
at
that
time
or
pull
in
others
to
review
like
the
the
GitHub
admin
team
or
or
testing
testing,
or
the
case
infra,
or
something
like
that.
Yeah.
I
Yeah
I
think
we
need
to
point
that
out,
though,
and
maybe
even
point
to
some
of
the
things
that
we
think
might
look
like
like
the
GitHub
org
is
an
obvious.
Like
start
that
conversation
because
normally
we'd
be
expecting
sigs
to
be
starting
new
projects
under
owner
kubernetes
or
donating
them
there,
but
that
maybe
doesn't
make
sense
here.
I
I
think
if
we
nudge
them
in
the
direction
of
like
outline
which
exceptions
you
want
and
and
suggest
a
few
starting
points.
We
can
probably
get
something.
B
A
C
Yeah,
what
I
would
want
to
see
is
I
think
there
have
been
documents
and
lots
of
conversations
over
the
last
few
months.
What
it
would
be
great
to
see
is
is
an
actual
Charter
for
Sega
CD.
There's
lots
of
tbds
here
so
I
think
I
I
think
you
know
holistically.
What
they
are
trying
to
accomplish
in
the
context
of
a
sake
would
be
useful.
F
And
wearing
my
SRC
hat,
we've
been
wanting
this
for
a
while.
This
is
definitely
a
welcome
change.
But,
having
said
that,
I
think
in
our
last
SRC
call,
we
did
actually
talk
about
what
constitutes
those
like
requirements
for
six
and
sub
projects,
meaning
over
time.
If
people,
if
there
aren't
enough
maintainers
where
they
can
need
the
SLO
for,
say,
CBE
things
right,
do,
do
they
graduate
out
of
a
sub
project
or
a
Sig,
don't
know,
but
that's
one
of
the
things
that
I
think
could
come
up
more
in
the
future.
C
A
A
C
I
B
I
H
C
So
yeah
so
I
would
I
would
say
that
you
know
I
think
when
we
had,
you
know
instantiated
the
101
track.
It
was
because
the
the
conceptually
like
101
is
always
going
to
matter
and
I
think
I
think
we
kind
of
fall
under
the
like
steering
plans
to
exist
for
the
future
right
and
and
it's
and
they're
you
know
for
the
the
58
of
or
whatever
the
number
is
of
new
attendees
for
kubecon
I
think
this
is
a
relevant
session
to
happen.
C
A
G
A
Three
there's
three
kind
of
opportunities
that
steering
has
if
we
want
to
put
messages
out
there,
the
first
being
at
the
contributor
Summit
we've
been
having,
and
it's
been
highly
requested
to
continue
to
have
a
an
AMA
session
at
contributor.
Summit
people
find
that
that
valuable,
but
that's
more
kind
of
an
internal
internal
thing.
A
As
far
as
how
the
project
goes,
we've
had
this
maintainer
track
spot
where
we've
done
an
Ama
or
some
kind
of
session
to
educate
people
on
who
steering
is
and
what
we
do
and
then
the
third
one
is
the
video
updates
from
the
from
the
kubernetes
project
that
can
go
into
that.
Video
recording
that'll
go
get
played
on
the
the
keynote
stage,
one
of
the
days
of
kubecon.
A
So
there's
those
are
the
three
opportunities.
If
all
of
them
are
helpful,
we
could
do
all
three
if
some
of
them
aren't
helpful
or
aren't
proving
things
that
we
can
drop
them.
But
at
least
at
this
point
to
me,
like
I've,
seen
benefit
from
holding
the
sessions.
That's
at
least
my
my
right,
but
I
I
wasn't
able
to
attend
the
the
last
one.
G
I
think
all
the
three
formats
have
their
own
benefits
with
the
session
at
kubecon.
I
believe
like
we
could
field
like
the
audience,
would
feel
like
good
questions
to
us,
and
that
is
a
broader
audience
who
may
not
be
able
to
like
join
the
contributor
Summit
and
the
keynote
video
update
gives
a
view
of
what
we
are
doing
on
priority.
But
then
they
don't
get
to
ask
us
any
questions
at
that
stage
and
they
can
come
to
our
session
basically
to
ask
questions
so
I
feel
like
we
should
still
submit.
It's
awesome.
C
B
I
I
am
plus
one
on
all
three.
The
the
big
thing
that
keeps
coming
up
you
know
again
and
again
is
a
lot
of
people
frankly
have
have
no
idea
what
we
do
or
it
gets
confused
with
like
the
TOC
or
you
know,
essentially
some
of
the
stuff
that,
like
Sig
Arch
winds
up
covering
I'm,
not
sure
you
know
what
else
we
could
potentially
do
to
like
sort
of
Market
the
session
better
to
try
and
potentially
get
better
attendance.
B
C
So
Tim
had
mentioned,
you
know,
value
prop
and
I.
Think
for
for
us.
As
a
group,
we
need
to
Define
what
that
is
right
and
walk
backwards
from
that.
We,
if
we
don't
have
that
walking
in
we're
kind
of
going
to
be
like
all
right,
here's
the
session,
here's
the
usual!
You
know
thing
right.
If
there's
something
there's
some
goal
that
we're
trying
to
achieve.
You
know
for
that.
Kubecon
then
that
is.
That
is
what
we
walk
back
from,
but
we
should.
We
should
state
that
value
prop
before
we.
I
C
I
I
H
I
Think
they
have
different
availability
like
if
you're
at
work
right
now,
because
you
need
to
be
doing
your
day
job
and
you
can't
attend
these
meetings.
That
is
a
different
kind
of
not
being
able
to
attend
like
they
both
have
that
problem,
like
the
Zoom
call,
isn't
actually
accessible
to
everyone
either.
B
I
Yeah,
but
that
is
a
good
point
too
I
think
we
should
make
sure
that
we
I
think
there's
enough
interest
across
this,
that
we
should
make
sure
that
we
reserve
the
slot,
even
if
we
don't
quite
have
it
worked
out
yet
I
know.
Some
of
us
will
also
be
looking
at
the
slots
for
some
of
the
other
things
on
things.
So.
I
C
I
I
C
B
G
A
E
I
I
just
wanted
to
thank
the
steering
committee
for
taking
a
look
again
at
that
attempt
to
form
that
working
group
I
know
it's
been
a
long
haul,
but
I
think
what
I
heard
I
want
to
make
sure
I
understand
it
is.
We
do
have
a
commitment
to
at
least
review
from
the
remaining
members
of
steering
correct,
I'm
gonna,
consider
right,
fantastic.
B
I
A
A
Would
be
we
have
our
private
meeting
next
week,
which,
actually,
let
me
look,
do
we
have
all
seven
of
us
here
today?
I
think
we
do.
Yes,
I
think
it's
been
a
little
while,
since
we've
had
all
seven
in
the
room
at
the
same
time,
what
what
I
suggest
first
off
is
everybody
here
from
steering
planning
to
attend
our
private
meeting
next
week.
A
So
what
what
I'd
suggest?
Why
don't
we
put
annual
reports
as
the
first
item
next
week
for
us
to
go
over
so
that
everybody
everybody
has
you?
You
now
have
five
business
days
to
go
through
and
take
a
look
at
the
current
status
of
your
your,
your
your
sigs
and
working
groups
and
all
that
kind
of
stuff
ping
ping
and
poke
people
as
you
can
this
week,
and
then
we
can
go
through
everything
that's
outstanding
next
week
on
on
that's
the
first
thing
on
our
agenda.
C
G
G
B
I
H
See
the
values
for
the
readership
the
the
really
really
broad
set
of
potentially
interested
technically
in
coupling
towards
the
project.
This
is
a
really
hard
project
to
approach
and
comprehend.
What's
going
on
so
having
something,
that's
curated
to
be
more
understandable
of
what's
going
on
in
aggregate
versus
just
a
set
of
Sig
silos,
I
think
that's
a
really
important
editorial
for
our
our
user
base
and
and
that's
where
it
gets
tricky
trying
to
harmonize
and
maybe
cut
certain
things
out
or
say.
H
G
E
Yeah
to
Tim's
Point,
we
had
two
relatively
new
to
kubernetes
community
members
approach,
see
Cloud
providers,
slack
Channel
lately
and
say:
where
do
we
jump
in
and
we
thought?
Oh
dear,
like
There
Are
Places,
you
should
jump
in
probably
trying
to
work
on
a
cloud
provider
is
not
the
easiest
or
best
first
good
issue,
and
so
Michael
and
I
ended
up
going
and
finding
some
good
first
first
issues
from
KK
and
a
few
other
repos
a
few
other
Sig
repos.
But
it's
like
I
know.
You
know.
I
E
I
G
So
one
other
benefit
that
I
have
seen
of.
The
Consolidated
report
is
getting
like
having
that
report
in
public
helps
getting
buy-in
for
people
who
want
to
contribute
to
upstream
and
where
we
need
help
and
I
could
have
I
got
like
a
few
managers
like
agreed
for
their
reports
to
contribute
Upstream
in
the
critical
areas
that
we
need
help
with.
So
having
that
report
even
for
last
year
would
help
in
this.
But.
I
G
F
B
B
I
I
mean:
would
it
work
to
like
write
a
just
like
brief
message
and
Link
out
to
the
reports?
Do
we
actually
need
to
summarize
all
of
them?
I
I
also
worry
about
the
editorial
voice
on
that
and
like
what
we
exclude
like.
We
asked
the
sigs
to
write
this
up.
If
we're
gonna
pass
it
along
and
like
skip
stuff.
That
doesn't
seem
great.
A
That's
actually,
at
least
in
in
my
past
experience.
Ben,
that's
the
benefit
of
yeah.
This
is
is
the
bit
of
editorial
view
on
it,
where
it's
like
you
could
any
anybody
could
go
and
read:
36
individual
Sig
reports
to
identify
what
the
the
areas
of
need
in
the
project
are,
but
it's
way
easier
and
simpler
to
have
one
report
that
highlights
hey.
These
are
the
areas
where
we
actually
need
things
and,
like
here's,
the
significant
areas
of
need
and
here's
the
significant
wins
of
the
project,
because
there's
gonna
be
plenty
of
stuff.
A
C
I
A
So
I'm
going
to
make
a
suggestion:
let's
see
how
people
feel
about
this
as
homework
for
next
week.
In
addition
to
the,
in
addition
to
poking
your
other
folks,
I
think
it'd
be
helpful.
If
folks
take
a
look
at
our
previous
annual
report
like
annual
Consolidated
one
that
was
was
linked
from
last
year.
If
you
have
not
already
and
because
then
we
can,
if
based
on
last
year's
report,
we
can
then
look
at
it
and
figure
out.
Okay.
A
Are
there
places
or
things
that
we
can,
that
would
get
streamlined
so
that
it's
not
as
much
of
a
burden
for
us
to
to
generate
and
understanding
like
I
think
reading
the
last
Consolidated
annual
Port
will
also
give
people
a
sense
of
like
the
time
commitment
that
is
required
in
order
to
compile
it,
because
that's
the
other.
The
other
question
that
we'll
have
to
look
at
next
week
is
like.
C
I
I
I
think
that's
part
of
why
we're
struggling
to
get
people
to
to
do
it.
It's
kind
of
it's
like
writing
a
cat.
It's
imposing
there's
a
huge
template
and
there's
some
pretty
high
time
commitment
things
for
people
to
do.
It
doesn't
seem
like
they
should
need
to
do
like
collecting
a
list
of
members
or
something.
I
G
I
I
think,
if
I'm
looking
at
this
as
a
Sig
lead
and
looking
at
what
I
need
to
do,
if
there's
anything
that
you
can
just
automate
away
for
me,
I
would
split
it
into
like
a
separate
file
or
something
so
that
I'm,
just
looking
at
okay
I
need
to
answer
these.
These
couple
questions
and
and
I'm.
This
is
more
manageable
right
now
it's
a
lot
in
that
document.
A
We
also
found
here's
some
automation
that
wasn't
working
the
way
that
the
automation
was
intended
to
work
and
people
found
it
by
reviewing
what
we
generated
for
them
and
to
be
like.
Oh
actually,
that's
not
correct.
Let
me
let
me
fix
this
so
having
having
a
human
eye
on
that
and
then
be
able
to,
for
posterity
record,
might
have
some
value
like
definitely
a
good
topic
for
us
to
discuss.
But
there
are
some
reasons
why
we
might
still
want
to
do
the
way
we're
doing
it,
but
we
can.
I
Put
an
item
for
next
time:
I
would
say
that
psychologically,
at
least
to
me,
I
would
split
those
into
it
like
like
make
it
a
folder
put
in
another
file
or
something
so
that
when
I'm
looking
at
the
document,
I
need
to
fill
out
it's.
This
is
what
I
need
to
go
generate
and,
and
it's
and
it's
a
smaller
file.
I
We've
even
talked
about
this
with
enhancements.
This
is
a
similar
problem,
but
like,
if
you're
doing
some
trivial,
like
process
thing
in
the
project,
and
you
just
want
to
drive
consensus.
You
have
like
the
entire
prr
thing
to
look
at
and
even
just
saying,
not
applicable
to
all
of
it
takes
a
while
and
that
that
causes
like
activation
energy
issues
for
people
you
just
you
open
up
that
file
and
you're,
like
nope,
there's
no
way
I'm
doing
another
account
I
think
we
have
a
similar
problem
with
annual
reports.
I
H
Tim
I
feel,
like
we've,
tried
to
optimize
for
the
the
starting
point
of
oh
it's
hard
when
you
have
a
blank
page,
what
should
I
write
now
sure
I
agree
with
you've
been
as
a
lead.
You
should
know
your
current
pain
points,
your
current
successes,
but
also
maybe
you've
started
for
forget,
and
the
tools
then
became
a
way
of
reminding
somebody
of
here
are
some
things,
but
at
the
worst
case
that
ends
up
just
being
hey
if
you're
interested
in
kubernetes.
H
I
Well,
but
in
our
current
state
we
have
six,
just
not
turning
in
anything,
so
I.
Don't
think
I
think
that
it
would
be
better
to
encourage,
like
you
know,
first
step,
give
us
your
like
pain
points
and
and
where
things
are
going
well
tell
us
about
the
state
of
it,
and
then
you
know
the
next
year
is
like.
I
Can
you
reveal
that
our
like
list
of
caps
and
like
editor
editorialize
that
and
if
you
don't
get
to
that
like
that
to
me
at
least
that's
less
of
a
problem
than
if
you
don't
give
us
anything
and
we're
not
even
hearing
from
you
about
like
where
your
pain
points
are
or
what's
going
well,
I
have
a
major
stick
that
still
hasn't
written.
Anything
and
I
would
really
like
to
know
how
that
Sig
is
doing
and
I.
I
I
Yeah
I,
don't
know,
I
I
think
it's
it's
sort
of
a
multi-purpose
document
rate
like
one
of
the
purposes
is,
is
informing
people
and
and
giving
six
a
chance
to
to
get
that
message
out.
But-
and
it's
also
to
an
extent
for
us
to
have
some
idea,
you
know
how's
the
project
going.
Where
do
we
need
to
be
doing
things
and
that's
the
one
that
really
concerns
me,
because
sigs
have
other
ways
that
they
can.
They
can
do
Outreach.
I
You
know
like
we
talk
about
good,
first
issue
or
things
like
that,
but
the
feedback
mechanism
getting
it
back
to
steering
you
know,
I
think
the
annual
reports
is
one
of
the
few
things
we
have
where
we
actually
take
a
look
at
what's
what's
up
with
the
six
and
when
we're
not
getting
anything
at
all.
That
seems
pretty
bad
and
we
should
fix
that.