►
From YouTube: Kubernetes Community Weekly Meeting for 20220616
Description
Kubernetes Community Weekly Meeting for 20220616
A
Hello,
everyone
and
welcome
to
the
june
2022
kubernetes
community
meeting
today
is
june,
16
2022.
Thank
you
for
joining
or
watching
the
recording.
A
few
things
before
we
get
started.
This
community
meeting
is
live
streamed
and
will
be
posted
publicly
on
youtube.
So
please
be
mindful
what
you
say
is
be
recorded.
A
This
is
an
official
meeting
of
the
kubernetes
project
and
we
abide
by
the
kubernetes
code
of
conduct,
which
boils
down
just
to
be
excellent
kind
and
respectful
to
each
other.
I'm
your
host.
Today,
my
name
is
ray
lojano
professionally.
I
work
with
sousa
by
way
of
ranch
labs,
I'm
also
the
sigdoc's
co-chair
and
wear
a
few
other
hats
in
the
community.
A
So
you
might
see
me
around
we'll
make
a
note
or
do
a
call
for
if
anyone
could
volunteer
to
be
a
note
taker,
we
don't
have
a
anyone
that
has
volunteered
yet
so
please,
if
you
can
take
notes
I'll
paste,
the
link
to
the
read,
write
agenda
and
that's
in
the
agenda,
but
if
you're
only
looking
at
the
agenda,
if
you're
only
you're,
not
taking
notes,
please
don't
use
that
link.
Please
use
the
read
only
link
and
paste
that
link
in
the
channel
as
well.
A
So
please
use
the
read
only
link
because
I've
once
with
google
docs
if
we
have
a
lot
of
people
taking
that
in
the
read
and
we
write
copy
it
kind
of
slows
it
down
so
and
thank
you
very
much
for
taking
notes.
As
a
reminder.
Please
meet
yourself
when
you're,
not
speaking,
so
we
have
a
number
of
topics
on
the
agenda
today
they
were
gathered
from
the
community
as
topics
that
are
a
general
community
interest.
A
So
we
we
encourage
people
to
add
agenda
topics
as
well
when
they
think
that
the
topic
is
might
is
a
topic
that
the
community
should
pay
attention
to
or
have
visibility
on.
So
please
reach
out
to
sig,
say
contributor
experience
on
slack
if
you
do
have
a
topic
for
the
next
month's
community
meeting.
So
let's
start
off
with
the
release
updates
and
I
want
to
introduce
you-
release
lead
for
kubernetes
1.25
cc.
I
want
to
hand
it
off
to
cc.
B
Hi
hi
everyone
thanks.
My
name
is
cc
huang
and
I'm
currently
working
at
google.
It's
been
absolutely
an
honor
to
become
the
release
lead
for
1.25,
and
we
are
currently
at
week
four
now
and
I'll,
be
giving
some
updates
for
the
current
release.
The
major
updates
is
that
we
delayed
the
1.25
enhancement
phrase
until
june
23rd,
which
will
be
the
next
thursday,
and
there
are
few
major
milestones
people
might
want
to
keep
in
mind.
B
A
All
right
just
a
reminder,
as
cece
mentioned,
the
next
major
milestone
is
enhancements
freeze
on
thursday
june
23rd.
Please
opt
in
your
enhancements
if
you
want
them
to
be
included
in
the
125
release
all
right.
Now,
let's
move
on
to
the
agenda
topics.
Our
first
topic
is
on
container
registering
so
I'm
just
hand
this
off
to
laura.
C
Hi
folks,
my
name
is
laura
santaria.
I
am
with
sig
contributor
experience
and
I'm
from
palumi
I
and
I'm
here
just
to
ask
folks
about
the
registry.k8.io
we're
asking
everyone
to
start
moving
their
their
traffic
to
registry.kx.io
if
they're
doing
any
kind
of
ci
builds
or
any
kind
of
other
releases
instead
of
k8s.gcr.io.
C
The
reason
is:
is
that
funding
basically
money?
It
would
be
really
really
helpful
if
you
all
could
encourage
your
your
organizations
to
make
that
change
so
that
we
don't
have
to
continue
paying
for
gcr
images.
There
are
some
links
in
the
agenda.
I'm
happy
to
take
questions.
I
am
not
technically
the
person
that
ran
all
of
this,
but
I
became
an
expert
in
five
minutes.
I
did
not
stay
in
a
holiday
inn
express
last
night
so
but
questions
comments
feel
free
to
leave
them
in
the
chat
discussions.
C
D
In
addition
to
making
sure
we
don't
run
out
of
money
in
credits
by
the
end
of
the
year,
the
other
nice
thing
is
essentially
like
a
bunch
of
the
various
cloud
providers
are
hosting
copies
of
these
images.
In
their
you
know,
various
regions
and
availability
zones
and
all
other
fun
stuff.
So
now,
when
you
pull
an
image
instead
of
like
always
going
to
gcr-
and
you
might
now
hit
essentially
your
locally
cached
copy,
so
it
should
be
a
lot
faster.
In
addition
to
you
know
not
costing
us
money.
D
Prepared
but
I'll
just
say
really
quickly
at
the
moment
it
is
still
a
redirect
just
to
google
cloud,
but
in
the
near
future
we
hope
to
enable
that
so
that
when
you're
coming
from
aws
you'll
be
receiving
a
copy
local
to
your
region
and
aws
and
in
the
future
we
have
room
to
do
more.
Things
like
that
and
the
community
can
will
control.
A
A
C
A
A
C
D
Quick
tilde
on
that
one,
if
all
authoritative
fork
exists,
we
can
update
where
we
point
it
to,
but
we
at
this
time
don't
have
any
intention
of
maintaining
it
upstream.
We
literally
could
not
get
people
to
maintain
it
and
it's
honestly
a
disservice
to
everyone.
If
we
host
something
and
don't
archive
it
where
it's
not
getting
security
updates,
not
getting
issues
aren't
being
resolved.
So
it's
again,
if
someone
else
wants
to
take
over
for
it
and
continue
to
maintain
it.
That's
wonderful!
E
Hey
everyone.
The
last
time
I
was
here
was
that
a
month
ago,
or
was
that
two
months
ago
I
don't
know
time
two
yeah
right.
Two
months
ago
I
talked
about
how
we
were
rounding.
The
finish
line
with
our
annual
report
summary
good
news
is,
it
is
out,
it's
live
and
there
are
a
ton
of
action
items
for
community
members.
I'm
to
share
my
screen.
Let
me
see
if
I
can
do
that
here
and
I
can.
E
I
also
hope
I
have
my
notifications
off
you'll
see
y'all
will
see.
I
get
some
wild
stuff
anyway.
So
if,
if
you're
curious
about
where
to
find
the
report,
obviously
there's
a
million
different
places
where
I
think
the
easiest
slug
is
cncf,
dot,
io,
slash
and
then
from
there
you'll
see
it's
the
very
first
link-
and
this
is
our
in
a
report
summary
and
for
those
that
were
not
on
the
call.
The
last
call
just
give
like
a
quick
rundown
of
what
it
is
and
why
we
do
it.
E
This
is
a
summary
of
37
different
reports.
Those
37
different
reports
come
from
community
groups.
Those
community
groups
are
sig
special
interest
groups,
working
groups
and
some
user
groups
as
well,
and
we
take
all
that
information
and
combined
it
and
create
themes,
a
help
wanted
section
accolades
across
the
project
and
more.
This
is
a
great
report
to
give
to
folks
that
you
work
with
that
might
be
working
on
cloud
native
strategy
or
cloud
native
participation
or
kubernetes
participation
or
anything
along
those
lines.
E
But
it's
a
great
kind
of
bird's
eye
view
into
what's
been
going
on
in
the
last
year,
as
well
as
some
things
that
are
ahead
of
us.
So
I
just
wanted
to
call
out
some
some
of
the
tidbits
of
the
report.
I'm
not
gonna
go
through
all
of
it
because
surprise
and
true
kubernetes
fashion,
it's
also
like
37
pages.
E
So
there
is
a
table
of
contents
in
the
beginning
too,
for
your
reading
pleasure,
but
we
do
call
out
some
terminology
in
the
beginning.
If
we
have
any
new
folks
on
the
line
and
and
aren't
understanding
some
of
the
acronyms
that
I'm
saying
right
now,
but
they're
right
there
so
scrolling
down,
we
have
a
ton
of
accolades
because
we
want
everybody
to
celebrate
with
us.
E
This
is
a
community
of
70
000
people
in
it
with
a
few
hundred,
what
I
call
maintainers,
which
are
our
owners,
people
who
are
reviewers
and
approvers
in
these
files.
So
all
the
things
that
these
folks
have
done
for
us
in
the
last
year
deserve
accolades
praises
tweets.
So
if
you're
wondering
what
you
should
tweet
ever,
you
can
start
here
start
with
praise
right.
E
A
lot
of
these
things
have
to
do
with
all
the
security
efforts
that
are
going
around.
It
has
to
do
with
the
people,
the
contributors
and
the
maintainers
who
are
sticking
around
and
showing
up.
We
work
on
some
very
large,
complex
problems
at
this
stage
in
our
project
journey
and
the
folks
that
stick
around
with
us
are
are
everlasting
and
awesome,
and
we
appreciate
every
single
one
of
you.
E
E
E
Independent
contributors
still
play
a
critical
project,
play
a
critical
part
in
this
project.
Y'all,
that's
something
that
should
be
allotted
and
also
accoladed
for
these
folks
that
show
up
who
do
work
for
us,
not
necessarily
on
their
daytime
employer
hours
or
maybe
it's
weekend
hours
or
they
don't
necessarily
have
support
that.
A
lot
of
us
do
have
at
our
day,
jobs.
E
The
other
theme
that
we
saw
was
that
niche
contributor
documentation
is
still
some
of
the
hardest
to
keep
fresh
and
to
keep
alive.
Obviously
you
know
tragedy
the
commons
and
so
many
of
these
places,
but
we
noted
that
this
can
actually
be
not
only
an
opportunity
for
us,
but
there
could
be
other
programs
and
onboarding
programs,
and
things
like
that
that
we
could
use
to
help
out
with
this,
and
groups
can
sort
of
build
roles
and
stuff
around.
E
You
know
getting
around
getting
this
kind
of
documentation,
updated
and
stuff
like
that,
when
I
say
niche
contributor
documentation
too,
I
don't
necessarily
mean
our
ginormous
contributor
guide,
which
is
located
on
kate's
dot,
dev,
slash
guide,
I
mean
the
stuff,
that's
in
the
devel
folder,
that
each
sig
has
that
specializes
in
things
that
need
that
operations,
and
things
like
that
that
that
are
required
for
that
sig.
For
you
to
know
as
a
contributor,
especially
as
someone
who's
doing,
reviewing
and
improving.
E
E
E
E
That's
how
you
build
trust
here,
so
please
feel
free.
If
you're
listening
to
this
and
you're
wondering
how
you
can
you
know
climb
this
contributor
ladder,
if
you
will
start
by
reviewing
things
that
are
in
the
pr
queue
and
give
your
advice
and
feedback
to
the
folks
that
are
authoring
and
that
helps
out
the
folks
who
are
ultimately
approving
these
things
and
it
goes
faster,
the
nine
to
five
contributor
is
almost
over
and
we
have
to
adjust.
E
So
how
do
we
adjust
as
a
project,
especially
when
we
still
have
100,
plus
caps,
that
aren't
in
general
availability
yet,
and
we
also
have
tons
of
ginormous
large-scale
projects
that
need
focus?
That's
something
that
we
are
thinking
about,
and
then,
last
but
not
least,
in
the
growth
area.
Is
this
reporting
process
and
its
summary?
This
needs
some
work.
It
took
us
six
plus
months
to
do
this.
You
all
six
plus
months.
E
E
Many
of
these
areas
have
under
five
unique
reviewers,
which
is
definitely
you
know
as
far
as
project
health
is
concerned
is
is
concerning,
but
the
sigs
took
the
time
and
took
some
time
out
for
y'all
to
read
through
these
and
explicitly
tell
you
where
they
need
help.
Obviously,
we
have
help
wanted
issues
good,
first
issues,
etc.
E
So
this
is
really
important
for
folks,
like
I
said
that
are
doing
strategy
and
things
like
that
at
your
at
your
organizations.
These
this
is
stuff.
That's
on
deck.
We've
done.
This
is
sort
of
like
a
road
map
area.
If
you
will
for
all
of
these
all
of
the
our
little
micro
communities
here
in
kubernetes.
E
I
would
I
say
bo
I'd,
say:
equal,
equal,
roadblock,
equal
blockers
with
the
collecting
of
the
information
from
already
overburdened
individuals,
and
then
the
second
one
is
the
creation
of
this
actual
report,
because
all
of
the
data
is
coming
in
in
different
ways.
So,
like
some
of
it's
has
links
some
of
it's
not
so
bob
and
I
spent
a
tremendous
amount
of
time
cleaning
this
up
and
making
it
readable
and
that's
kind
of
where
the
automation
and
the
generator
development
and
things
like
that
will
help
us
out
a
ton.
E
D
One
other
thing
that
I
definitely
would
like
to
see
more
of
is
most
of
the
groups.
The
people
that
work
in
it
were
the
leads
when
a
lot
of
this
can
be
farmed
out
to
you
know
other
members
in
the
community,
especially
when
it
comes
to
providing
more
context
on
some
of
the
areas
there
like
that
you
need
help
or
some
of
the
the
big
initiatives
that
context
really,
you
know,
helps
when
trying
to
talk
about
an
area
that
needs
help
or
an
initiative.
D
E
I
also
think
that
again,
I
don't
like
to
always
put
stuff
on
automation
and
like
building
up
generators
and
things
like
that,
but
I
do
think
that
once
we
have
a
lot
of
that
infrastructure
built
for
those
said
leads
and
things
that
we
can
then
move
those
conversations,
meaning
like
the
steering
has
with
the
leads
to
more
important,
ambiguous
topics
like
identifying
their
needs
at
a
high
level
like
doing
road
maps
and
stuff
like
that.
But
I
think
we
spend
a
lot
of
the
conversations
right
now
on
just
the
administration
that
that's.
E
Why
for
us,
I
feel
like
it's
also
not
valuable,
but
I
mean
from
a
steering
committee
perspective
in
general.
This
is
still
very
valuable
to
us.
We
just
don't
necessarily
think
it's
valuable
to
anybody
else.
It's
valuable
to
us,
because
every
year
it
opens
up
conversations
with
leads
about
things
like
their
terms
and
also
things
like
the
archiving
of
projects.
Aka
like
service
catalog,
it's
opened
up
a
good
way
for
us
to
you
know,
communicate
health
and
maturity
and
things
along
those
lines
with
folks
who
are
already
extremely
busy.
E
But
again
like
is
this
valuable
to
the
community
like
sure
it's
valuable
to
a
group
of
seven
individuals,
but
how
do
we
make
this
better
for
y'all?
How
do
we
make
this
better
for
people
who
are
making
decisions
at
these
major
players
that
are
putting
folks
on
staff?
Like
that's
the
I
think,
that's
the
real
stuff
that
I
would
like
to
get
to
the
bottom
of
with
this
report.
D
Like
one
other
comment
like
if
you
can
share
this
report
like
it's,
it's
not
just
for
the
people
on
the
call
share
it
with
you
know
higher
level
leadership
to
see
what
they
would.
You
know
see
what
they
want
in
a
report
like
that,
what
would
be
valuable
to
them
to
potentially,
you
know,
allocate
resources
to,
or
you
know,
the
types
of
risks
that
they
want
to
see.
A
A
And
you
so
this
report's
very
important
there's
a
lot
of
places
that
folks
can
help
out.
So
please,
I
reiterate,
if
you're
a
new
contributor
or
not
or
veteran
contributor,
please
check
out
the
help
wanted
section
and
the
annual
reports
all
right.
Let's
move
on
to
talk
to
our
third
topic,
which
is
the
kubecon
eu
meetings
and
sustainability
and
more
hand
it
off
to
bob.
D
Hey
folks,
so
we've
talked
a
lot
about
sustainability
and
reliability
on
these
calls
in
the
past
and
we
sort
of
had
I
forgot.
There
was
an
email
thread
that
started
that
sort
of
like
really
led
to
the
a
like
unconference
session.
That
was
hosted
at
kubecon
eu
and
there
were
some
very
fruitful
conversations
that
came
out
of
that.
It
was
essentially
vojtek
and
antonio
up
on
stage
that
sort
of
started.
D
D
D
You
know
a
couple
like
the
life
cycle,
labels
that
can
serve
as
better
key
indicators
for
us
that,
like
hey,
we
should
not
be
accepting
features
into
this
space
as
well
as
potential.
You
know
not
just
for
us
that
that
potentially
want
to
add
these
features
ourselves,
but
also
surface
it
up
to
the
larger
groups
that
are
invested
in
the
project.
Like
hey,
you
know,
we
should
not
be
adding
anything
more
here
until
we
can
shore
up
our
you
know,
coverage
and
make
sure
that
this
area
is
healthy.
D
Now,
one
of
the
big
blockers
to
you
know
showing
this
stuff
up
and
making
sure
it's
healthy
is.
We
do
have
a
lack
of
you
know,
reviewers,
a
lack
of
approvers
paris.
You
know
was
just
talking
about
this,
so
we
have
the
two
things
that
sort
of
tell
us.
You
know
where
there
are
problems
and
the
answer
to
solving
those
problems
is
largely
mentoring.
We've
done
the
mentoring
cohorts
in
the
past.
D
They
have
been
very
successful.
The
this
is
not
one-on-one
mentoring.
This
is
you,
we
are
taking
a
group
of
people
and
we
are
focused
on
getting
them
to
a
specific
spot.
We
want
to
you
know
in
a
release
cycle.
We
want
to
make
them
reviewers
of
over
this
area,
maybe
in
over
the
next
release
they
become
approvers
in
that
area.
D
The
big
thing
is
that
does
require
time
and
investment
from
the
the
current
people
that
are,
you
know,
approvers
the
subject
matters
in
that
space,
but,
like
we
see
this
is
like
the
like
pretty
much
the
only
long-term
solution
to
fixing
those
areas
and
and
creating
a
more
sustainable
path
forward.
With
all
this,
I
think
that
covers
the
tldr
anyone
else
that
was
there
at
the
unconference
have
any
other
comments
or
notes.
F
F
F
F
H
H
H
H
G
G
G
Some
of
the
challenges
that
we
have
on
boarding,
and
so
the
release
team
is
currently
like
a
really
good
place
for
people
to
rotate
in
and
out
to,
you
know,
get
to
know
some
of
the
areas
of
the
project
and
they
get
to
know
how
kubernetes
gets
released
and
some
of
the
features
that
go
into
it.
But
it's
it
has
been
kind
of
hard
of
making.
Some
of
those
people
stick
and
also
like
encouraging
them
to
you
know,
do
more
long-lasting
contributions,
particularly
in
securities.
G
I
don't
know
if
I
I
mean
we've
seen
some
of
the
members
of
the
release
team
rotating
into
other
cities,
but
we
sometimes
lose
track
of
them
and
we
don't
know
what
their
success
story
is
over
there.
But
but
from
that
session
we
got
like
new
ideas
and
we
are
going
to
be
trying
out
some
new
ways
of
onboarding
new
radius
managers
in
the
next
two
releases.
Hopefully
we'll
get
more
successful.
A
And
just
to
add
to
that
the
release
team,
I
myself
it
was
introduced
to
contributing
to
this
project
by
the
release
team
and
they
went
on
to
other
sigs
as
well.
I
know
there's
other
several
other
folks
here
on
this
call
that
now
have
been
members
releasing
before
and
also
did
the
same
or
also
progress.
A
D
A
Okay,
that's
it
for
our
topics
in
the
agenda.
So
the
next
agenda-
I
guess
not
really
a
topic
but
for
kept
call
outs.
I
did
add
in
the
artifact
distribution
cap
or
kubernetes
enhancement
proposal,
which
has
which
is
the
cap
that
describes
the
registry
move
shout
outs
this
month,
so
we
have
a
slack
channel
for
shout
outs.
So
as
a
community,
we
like
to
praise
others
for
their
contributions
and
and
for
those
who
do
go
above
and
beyond.
A
A
Laura
santamaria
shouts
out
to
joseph
sandoval,
paris,
pittman
and
myself
for
the
april
community
meeting
parish
thanks
mada
for
country
numbers
for
the
annual
reports.
I
did
a
shout
out
for
the
124
release
team
and
for
release
managers.
The
release
team
and
release
manage
they
do
they
put
out
a
lot
of
efforts
for
each
release
and
that's
three
times
a
year
ben
elder
shouts
out
to
sasha
greenert
for
automating
branch
release
branch
fast
forwards.
A
Antonio
o'gea
shout
out
to
watch
tech
for
reducing
thousands
of
routine
leakages
from
the
during
the
api
server
shutdown.
James
labrax
shout
out
to
mickey
boxall
for
all
the
work
for
the
1.24
cncf
release.
Webinar
tim
banister
shouts
out
to
mark
rossetti
for
the
overhaul
on
the
kube
names
on
windows,
documentation,
paris,
paris,
fitment
shouts
out
to
tim
bannister
for
editing
vienna
reports
ray
lahanna
for
the
last
minute
polish
madoff
for
the
maintainer
stats
dims
for
the
maintainer
tool
as
well
and
eddie
zane
for
stepping
in
helping
six
to
get
the
reports
published.
A
Pushkar
drogo
car
shouts
out
to
watch
jack
for
fixing
a
big
ci
job
ben
elder
shouts
out
to
eddie
zane
for
stepping
up
against.
You
help
run
the
sick
testing
meeting,
madoff
shouts
out
to
patrick
ollie
for
growing
the
number
of
reviewers
in
k
logged
and
carlos
santana,
shout
out
to
veronica
lopez
for
going
above
and
beyond,
for
cutting
the
125
alpha.1
release
and
updating
the
125
timeline,
josh
shouts
out
to
pooja
deb,
roger
caslin,
chris
schwartz,
nigel
for
big
contributor
summit
and
kubecon,
eu
and
valencia.