►
Description
Kubernetes Public Steering Committee Meeting for 20230605
A
Hello,
everyone
and
welcome
to
the
June
public
kubernetes
steering
meeting
as
a
general
reminder,
these
meetings
are
recorded
and
we
post
on
the
internet
sometime
later
as
soon
as
automation
kicks
off.
With
that
we
abide
by
the
cncf
code.
Account
essentially
boils
down
to
please
be
excellent
to
each
other.
B
C
A
D
D
Is
there
a
value
that
we're
really
wanting?
And
if
so,
how
do
we
better
sell
that
value
proposition
to
the
the
Sig
leadership,
or
are
there
other
paths
to
getting
that
value
or
what
I
I
do
believe?
There's
value
in
this
I
I
also
worry
going
back
across
my
years
on
the
project
that,
but
between
the
the
changes
to
the
community
meeting
and
the
frequency
there
of
report
outs
versus
this,
we
we've
lost
something
for
across
cross
kubernetes,
cohesive
cohesion,
generating
Communications.
D
This
is
important
for
the
product
as
a
whole
to
remain
cohesive,
but
it's
also
really
important
for
newcomers,
which
then
feeds
into
sustainability
versus
burnout.
If
this
is
a
large
and
complex
project,
if
you
come
to
it
new
and
it's
not
particularly
approachable
or
easy
to
understand
where
it
is
and
where
it's
heading
as
a
whole
or
its
pieces,
it's
just
it's
really
really
daunting.
A
Yeah
I,
for
some
of
it
I,
do
think
more
automation
could
help
like
actually
getting
automatically
producing
the
owner's
reports
and
things
like
that,
but
the
the
general
value
add
was
you
know
something
for
us.
Well,
a
it
was
less
work
for
them
because
remember
they
they
did
have
the
previous
reporting
out
and
just
trying
to
signal
boost
it
with
the
you
know,
the
the
greater
group
at
largest
things
you
know,
what's
been
going
on
what
went
well,
what
needs
help
the
help
being
the
the
bigger
thing.
A
A
D
One
of
the
things
in
my
mind
is
that,
in
a
way
we
do
have
that
perhaps
twice
ish
a
year
in
terms
of
the
maintainers
track
content
at
kubecon.
There's
not
a
hundred
percent
coverage
there
and
then
also
it's
not
sort
of
a
uniform
style,
some
some
present,
where
they
are
some
present.
Here's
a
topic
that
we
need
to
solve.
Since
we
have
the
people
together
in
the
room,
there's
a
lot
of
variation
there,
but
I
think
in
that
sense
there
there
is-
or
there
are
examples
where
you
can
see.
D
D
During
the
community
meeting
every
week,
somebody
was
presenting
something
and
every
week
somebody
was
like
oh
crap,
I'm
neck
and
trying
to
pull
something
together
really
really
quickly,
but
whether
three
or
four
times
a
year
or
once
a
year
in
that
Forum
or
or
the
annual
reports,
Forum
or
twice
a
year
kind
of
with
kubecon,
there
is
a
periodic
bump
and
I.
Don't
know
if
it's
so
much
as
of
a
speed
bump
versus
a
forcing
function.
A
The
other
thing
that,
like
I've,
repeatedly
told
every
Sig
that
I'm
involved
in,
like
you,
don't
have
to
do
this
yourself.
You
can
also
involve
other
members
in
your
Sig,
like
part
of
it,
is
to
be
a
status
check
with
like
the
very
sub
projects
and,
like
you
know,
potentially
a
way
to
you
know
help
bring
on
New
Leads
or
you
know,
people
to
have
that
sort
of
oversight.
C
D
A
A
D
I
wonder
if
we
should
maybe
step
back
and
start
with
what
we
think
of
as
the
the
value
proposition
for
the
project
overall,
what
that
there's
I
guess
for
me.
This
is
the
that
commonizing
cohesion
cohesive
moment
where
you
can
get
a
a
view
of
where
the
project
is
right
now
and
where
it's
headed
and
then
kind
of.
Second,
in
my
mind,
is
the
approachability
that
the
subparts
give
to
people
within
the
six
or
the
view
of
how
ones
work
in
an
area
relates
to
the
whole.
A
A
A
A
C
D
Vmware
User
Group
kind
of
the
the
notion
of
it,
which
I
think
has
largely
happened
being
subsumed
in
a
larger
cncf,
User
Group,
instead
of
being
platformer
or
provider
Focus,
which
there
was
an
attempt
to
do
that
in
the
past,
to
kind
of
work,
perhaps
for
VMware,
but
others
weren't
there
and
there's
a
broader
need
at
the
end
of
March.
We
discussed-
and
there
was
an
expectation
of
the
final
motions
of
that
transition
would
happen
later
this
month.
So
I'll
just
double
check
on
the
status
of
that
okay.
A
A
A
I
am
reaching
out
to
the
ones
that
I'm
a
liaison
for
I
just
wanted
to
highlight.
If
you
have
any
of
these
on
your
list
to
reach
out
to
them,
it
can
even
be
you
know
at
least
opening
a
PR
to
add
the
same
people
to
each
role,
but
we
should
try
and
push
that
along
and
encourage
people
to
bring
on
new
people
into
the
leadership
roles.
A
E
E
E
When
I
became
a
chair
like
how
to
how
to
make
sure
that
we
follow
the
documents
and
make
up
like
I
mean
everybody
like
most
of
the
seeks
doing
it
differently,
but
we
and
Signal
try
to
separate
shares
and
TLS
to
have
it
easier
to
get
more
people
into
chairman
position
and
not
maybe
get
all
the
permissions
at
once.
So
a.
C
E
Yeah
I
heard
then
some
some
six
Atomic
given
approvals
to
Chairman,
because
how
deals
are
set
up
like
how
groups
are
set
up
so
then,
maybe
one
interesting
conversation
and
I'm,
not
necessarily
saying
that
we
should
remove
permissions.
Removing
permissions
are
hard
like
once
given
it's
like
it's
hard
to
get
away,
but
maybe
if
it
will
be
more
formal
projects
or
maybe
more
like
once,
we
have
sales
and
shares
on
every
single
group.
C
C
B
A
It's
something
we
can
you
know
definitely
take
on
is
serverless
follow-up
on
how
to
like
reconcile
that
stuff.
I
do
think
the
first
step,
no
matter
what
is
at
least
getting
the
the
remaining
sigs
to
have
the
TL
rule
defined,
but
we
can
start
that
com.
The
conversation
now
about
you
know
how
that
might.
How
separation
will
then
impact
things
like
enhancements,
since
it
will
officially
be
since
we
we
did
break
that
up.