►
From YouTube: Kubernetes SIG Arch - KEP Reading Club 20220103
Description
Discussing how the KEP Reading Club can be improved
A
Okay,
awesome
hi.
I
spoke
a
bunch
before
this,
but,
like
I
just
started
the
recording
now,
as
always
as
with
any
other
community
meeting.
This
meeting
too
follows
the
kubernetes
and
cncf
code
of
conduct,
which
boils
down
to
be
excellent
to
each
other,
and
this
meeting
will
also
be
posted
online.
So
please
don't
do
or
say
anything
that
you
don't
want
post
it
online,
so
as
a
a
quick
idea
of
whatever,
whatever
I
monologued
till
now.
A
Basically,
what
I
wanted
to
try
and
do
with
this
first
session
of
the
year
was
to
try
and
discuss
how
we
can
better
improve
the
time
we
spend
in
the
cap
trading
club
and
like
how
do
we
better
make
it
approachable?
How
do
we
increase
the
reach
of
it
and
like
but
make
sure
that
it
can
actually
help
in
a
better
manner
right
so
eddie?
So
he
was
one
of
the
people
who
came
up
with
the
idea
of
the
reading
club
right
so
eddie
and
dims
and.
A
And
himself,
primarily
the
two
people
who
had
this
idea
in
the
first
place
so
initially
when
all
of
this
started
out
one
of
the
first
things
that
eddie
also
mentioned
was
that
later
down
the
line.
So,
as
you
might
know,
each
release
in
kubernetes,
so
the
enhancement
team
maintains
a
tracking
sheet
of
all
the
announcements
that
are
being
worked
on
in
that
particular
release.
A
B
B
I
have
a
question
I
guess,
which
is
how
let's
say
someone
says
something
really
insightful
in
the
next
reading
club
and
that
video
is
goes
on
youtube
and
we
have
the
transcript.
We
have
the
video
recording,
we
have
the
conversation,
but
how
do
we
make
that
insightful
comment
be
available
to
anyone
who's
reading
the
cap,
because
if
I
was
reading
a
cap,
I
wouldn't
think
to
look
on
this
particular
youtube.
Video
for
that
comment
that
whoever
she
or
he
makes
that
comment.
So
how
do
we?
How
do
we
make
that
kind
of
thing?
Discoverable?
A
That's
a
that's
a
great
point.
I
haven't,
I
honestly
didn't
think
about
this,
so
a
little
bit
of
context
of
how
it
used
to
happen
till
now.
So
again
like
there's,
I
agree
with
you.
There's
no
way
of
making
it
visible
to
whoever's.
Reading
the
cap,
but
an
intermediate
form
of
communication
that
used
to
happen
so
far
was
along
the
lines
of
so
first
they
used
to
be
like
the
usual
thing
that
that
happened,
so
note-taking
used
to
happen
very
meticulously,
like
throughout
the
caps,
especially
when
authors
joined.
A
That
was
like
that.
That
used
to
be
a
lot
of
fun.
After
that.
What
used
to
happen
was
we
used
to
start
a
thread
on
slack,
laying
down
questions
and
then
tagging
the
authors
in
case
they
couldn't
join
in.
That
was
another
thing
and
subsequently
tagging
or
like
mentioning
the
authors
in
the
notes,
doc
itself.
A
A
Eddie
zayn
was
on
the
call,
a
few
very
interesting
points
around
a
few
cases
that
might
actually
break
the
feature
were
brought
up
and
eddie
wrote
those
down
took
them
back
to
the
cli
meeting
and
like
a
bunch
of
discussion,
happened
and
workarounds
were
like
then
implemented
from
there.
So
that
was
how
it
happened,
but
there's
like
a
huge
gap
between
a
person
who
doesn't
know
about
these
meetings
and
doesn't
attend
them
and
the
points
that
were
brought
up
right,
so
we
for
sure
need
to
think
of
a
way.
A
I
know
that
there
is
work
going
on
around
like
a
page
for
like
listing
all
the
kept
like
a
kept
website
of
sorts
that
might
soon
like
come
to
fruition.
I
know
that
gcs
bucket,
although
that
was
successfully
provisioned-
I
see
I
know
on
the
call.
Maybe
if
I'm
not,
I
I
haven't
kept
up
with
the
progress
on
that
as
of
late
so
like
he
can
correct
me.
A
If
I
from
around
here
but
like
maybe
that
can
be
a
potential
area
of
where
we
can
unify
some
of
these
comments
going
forward,
but
yeah
that
thanks.
That's
all
that's
a
great
point.
I'm
going
to
note
it
down
real
quick
in
the
meantime.
If
anyone
else
has
suggestions
or
like
anything
to
add
onto
this.
B
A
A
Okay,
so
another
thing
is
along
the
lines
of
what
I
was
talking
about
previously
right.
So
if
you
notice
that
there's
a
lot
of
work
going
on
or
like
a
lot
of,
people
also
put
a
lot
of
effort
into
helping
new
folks
get
started
in
the
community,
so
getting
started
in
the
community
can
be
like
done
in.
A
Of
ways
currently
code
non-code
community
manager,
like
all
of
that
great
all
of
those
great
avenues,
are
available
for
everyone
to
get
started
in.
What
I
have
noticed
is
that
getting
started.
I
was
fortunate
enough
to
get
a
lot
of
help
from
folks,
but
for
getting
started
in
terms
of
like
helping
with
an
actual
feature
or
doing
something
relatively
larger
than
what
I
used
to
do
before.
A
A
What
what
I'm
trying
to
do
now
is
that
how
do
we
use,
or
rather
can
we
use
this
one,
our
time
slot
to
somehow
try
and
help
more
folks
get
involved
in,
or
rather
than
even
get
involved,
like
just
help
out
in
some
form,
with
feature
development
of
any
particular
see
like?
How
do
we
effectively
communicate?
What
or
how
do
we
effectively
ask
for
assists
for
what?
A
What
what
areas
do
they
need
help
in,
because
I
don't
want
to
spam
them
as
well
right,
because
that's
not
that
that's
just
more
spam
for
everyone
else.
So
how
do
we
effectively
come
like
ask
for
ask
them
what
they
need
help
with?
Is
there
some
avenue
already
available
for
that
that
I'm
not
aware
of
and
like
bring
that
here
somehow,
maybe.
A
I
mean
one
obvious
way
is
to
just
like
ask
them
for
help.
Saying
that
hey
do
you
need
help
blah
blah
blah?
One
way
is
how
that
eddie
mentioned
saying
that
go
to
the
tracking
sheet
and
pick
out
cabs
that
you
want,
but
you
don't
necessarily
necessarily
know
that
the
kept
that
you
picked
out
are
actually
ones
that
people
need
help
with,
because
some
cabs
are
worked
with
are
worked
on
by
individuals
who
don't
really
want
help
or
like
ask
going
and
providing
help,
might
just
cause
and
cause
a
hindrance
in
some
form.
A
B
B
B
Maybe
you
know,
there's
interested
parties,
the
end
user
community,
especially,
but
but
also
cloud
providers.
Any
interested
party
might
want
to
see
an
alpha
feature
go
a
particular
direction
and
contributing
code
is
one
thing
and
getting
involved
in
that
sig.
But
another
way
to
do
it
would
be
this.
B
This
cat
reading
club
and
my
impression
is
this-
is
kind
of
a
lightweight
way
in
so,
if
you're
an
end
user
organization
that
relies
on
kubernetes,
it's
really
keen
to
see
an
alpha
feature
that
you
rely
on
go
further
than
alpha
and
there
are
you
know
there
are
loads
of
those.
Then
this
is.
This
is
probably
a
good
opportunity,
but
we
haven't
really
publicized
it,
and
so
my
specific
suggestion
is
a
blog
on
kubernetes.dev.
B
That
you
know,
introduces
the
reading
club
and
explains
what
it
is,
and
you
know
by
which
anyone
you
know
could
write
that
article
really
there's
no
there's.
No,
I
don't
see
frankly,
if
you
can
commit
to
to
to
get,
then
you
can
write
it.
I
think
it'd
be
really
good.
I'd
welcome
it.
I
I
helped
do
blog
reviewing.
So
that's
my
interest,
but
I
think
it'd
be
good.
Publicity.
A
Okay,
yeah,
that's
a
good
point,
so
you
mentioned
we
can
promote
the
cap
rating
club
as
a
way
to
contribute
and
develop
or
like
get
involved
with
alpha
and
beta
features
right.
So
can
you
elaborate
on
what
do
you
mean
by
get
involved?
So
do
you
mean
in
terms
of
helping
others,
understand
the
future
or
you
yourself
getting
to
know
that
feature
or
like
if
you
want
that
feature
using
this
as
a
platform
to
get
feedback
in
terms
of
what
do
others?
A
B
The
reason
it
should
bring
out
conflict
is
because
the
bits
where
people
don't
agree
are
the
ones
that
that
need
need
work
and
the
bits
where
everyone's
agreed
well.
We
certainly
no
need
to
rehash
those,
and
so
you
know
if
there
is
an
api
choice
to
be
made.
Let's
make
it
clear
that
we
haven't
settled
on
this
part,
or
this
part
of
the
design
has
problems.
B
Let's
identify
cases
we
haven't
addressed
so
that
we
went
we're
aware
of
what
that
thing
is
and
letting
something
just
run.
You
know,
like
we've,
had
a
problem
with
permabeater
and
pure
alfred
in
kubernetes.
I
think
where
something
has
been
good
enough
for
alpha
and
it's
and
it's
in
kubernetes,
and
then
people
are
using
it,
but
what's
the
future
of
that
and
the
longer
you
let
it
live,
the
the
harder
it
becomes
to
maintain
all
the
bigger
pain
when
it
does
eventually
get
yanked.
B
You
know,
there's
alpha
features
that
if
we
took
them
out,
people
would
be
really
that
understand,
I
think,
but
they
wouldn't
be
happy
about
it,
and
so,
rather
than
and
having
that
that
not
great
situation,
I
think
that
this
this
you
know
the
promotion
I'd
like
to
see
is,
come
and
come
and
point
out
where
people
disagree,
because
if
we
can
get
that
set
of
disagreements
down
to
a
small
enough
set,
then
we
can
make
it
we
can.
We
can
look
at
making
a
beta.
B
C
A
A
A
So
another
thing
that
I've
noticed
in
the
past
sessions
as
well
is
that-
and
this
is
including
me
so
whatever
kept
that
we
pick
up
it's
it's
likely
that
we
don't
really
have
a
lot
of
context
and
knowledge
on
it.
Unless
someone
who
is
aware
of
that
particular
piece
of
work
going
on
present
on
call
to
help
answer
those
questions
and
basically
drive
the
discussion
on
that
gap
right.
A
C
C
C
A
Yeah
availability
is
always
an
issue,
so
this
discussion
happened
like
a
while
back
as
well.
So
one
thing,
one
of
the
things
that
was
talked
about
was
sort
of
doing
a
pre-reading
of
sorts,
so
it
doesn't
really
have
to
be
in-depth
or
like
as
focused
as
we
do
it
on
call,
but
maybe
it
if
at
all,
you're
interested
just
go
through
what
the
cap
is
about.
A
If
you
need
to
or
if
you
think
that
you
need
to
like
brush
up
on
a
few
things
or
read
up
on
a
few
things
and
go
ahead
and
do
that
and
then
you
go
and
you
come
and
discuss
and
like
you,
come
and
read
together
and
discuss
it
over
here.
So
that
was
one
of
the
things
that
was
talked
about.
But
to
do
that
the
thing
is
time
is
always
a
constraint
for
most
people.
So
we
can't
expect
a
like
expect
that
to
happen
uniformly
and
consistently,
but
that's.
C
A
A
B
A
A
A
A
I
don't
know
like
we
mainly
need
to
try
and
focus
on
the
area
where
it's
the
period
of
really
start
recycle
start
to
enhancement,
freeze
and
enhancement,
freeze
to
mid
code
phrase,
so
that
area
basically
and
then
mid
code
phrase
two
code.
Freeze.
You
basically
allow
people
to
like
that's,
ideally
the
time
that
you
would
want
people
to
have
figure
out
what
they
would
love
to
work
on
and
get
context
on
it,
and
they
focus
on
that.
Basically
right.
B
B
B
A
B
B
A
C
Like
adding
on
to
tim's
point
so
basically
since
like
we
can
have
it
as
the
process
of
our
leads,
the
meetings
are
held
like
in
the
last
month.
They're
like
held
like
every
every
day
of
the
week
schedules
release
meetings.
Are
there
called
some
burn
down
meetings,
or
something
like
that?
Maybe
you
can
do
something
like
that.
You
know
for
the
reading
club
like
if
you
need
to
discuss
something
on
extensively,
we
can
maybe
old
meetings
like
maybe
buy
weekly
if
it's
needed
at
all.
A
Yeah
monthly
sounds
good
honestly
because,
like
I've
also
noticed
that
keeping
it
bi-weekly,
it
also
gets
very
increasingly
difficult
to
like
scheduled
time
and
things
like
that
with,
like
the
even
the
authors
and
like
if
the
authors
can
join,
that,
that's
there's
nothing
like
it.
So
that's
obviously
like
priority
that
we
try
and
accommodate
almost
like
as
many
people
as
we
can
so
yeah
monthly
sounds
good.
I
think
we
can
do
that
moving
forward.
A
Okay,
awesome
thanks
what
else
any
last
closing
we
still
have
half
an
hour,
but
if
there
is
nothing
else,
we
can
call
it
early,
no
worries
so
like
any
last
thoughts
or
feedback
or
like
just
anything
at
all
that
you
thought
or
expected
from
this
particular
meeting
or
like
anything
at
all
that
you
had
a
mental
model
of
what
it
should
look
like.
That's
also
good
enough.
We
can.
We
can
incorporate
that.