►
From YouTube: K8s SIG Docs Meeting for 20230207
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
welcome
to
the
February
7th
2023
kubernetes
digox
meeting
I'm
your
host
today,
my
name
is
Ray
lajano
before
we
start
I
want
to
remind
everyone
that
this
meeting
and
buys
by
the
cncf
code
of
conduct,
which
boils
down
to
be
kind
to
and
excellent
to
each
other
and
also
just
be
aware
of,
if
you're
not
familiar
with
the
code
of
conduct,
there's
a
link
on
the
agenda
that
I'm
sharing
to
to
to
be
just
to
be
respectful
of
each
other
as
well
before
we
start
I
want
to
welcome
any
new
contributors
to
this
call.
B
A
Right
with
see,
life
and
Larry
faces
welcome
back
everyone,
let's
start
with
the
meeting,
so
this
week's
PR
Wrangler
is
me
and
Carol
is
shadowing.
So
if
you
have
any
PRS
and
I've
already
introduced
myself
on
the
slack
channel
for
Sig
docs
to
introduce
myself
as
this
week's
PR
Wrangler,
please
let
me
know
and
I
will
get
to
reviewing
them.
Next
week's
PR,
WR
Wrangler
is
streaming
and
also
we
have
the
link
here
shown
on
the
agenda
to
the
pr
Wrangler
shift
as
well
any
comments
or
questions
on
that.
A
For
those
who
don't
know
what
PR
wrangling
is
a
PR
wrangling,
we
do
have
a
documentation
document
page
on
kubernetes.io,
about
PR
Wranglers.
It's
it's
the
approver
who
is
assigned
we
rotate
approvers
by
week,
going
into
who
triage
issues,
review,
pull
request
and
so
forth.
A
All
right,
moving
on
to
the
release
agenda
to
the
main
agenda
released.
Some
1.27
is
the
current
release
in
cycle.
It
is
I
think
the
target's
release
date
is
April.
11Th
and
I
got
this
from
the
release
team
meeting
notes
and
the
current
status
is
green.
We
did
create
the
integration
branch,
which
is
a
pull
request
to
merge.
A
The
dev127
branch
into
main
I
do
notice
that
it's
not
healthy,
that
it
does
need
a
sink,
so
I
actually
do
plan
to
create
a
video
on
how
to
create
a
sync
for
anyone,
who's
new
to
the
docs
release
team
or
anyone
who's
interested
in
learning
about
how
we,
how
we
do
our
work
for
releases
on
the
documentation
side,
so
I'll
do
recording
on
that.
A
A
All
right
and
going
into
issues,
nprs
I
have
one
here
from
Shannon
I,
don't
see
Shannon
on
the
line,
but
I
did
I
did
see
this
in
the
comments
on
this
is
an
issue
for
it
to
Bluetooth,
upgrade
update
the
style
guide
or
the
or
the
use
of
titles
and
headings.
We
do
have
a.
We
do
use
title
case
in
the
front
matter
on
a
page,
but
for
headings
we
use
sentence
case
I.
A
Remember
that
there
was
a
PR
to
update
that
to
update
that
a
style
guide
off
to
take
a
look
to
see
if
that
was
that
has
merged.
So
this
looks
like
and
and
we're
not
consistent.
Not
all
pages
follow
this,
so
I
did
see
like
a
a
blog
post
recently
to
that
had
the
title
the
front
matter
as
sentence
case.
A
C
A
Okay,
it's
like
in
me
like.
Are
you
neutral
to
just
not
changing
the
existing
ducks
with
the
with
the
title
and
the
front
matter
to
represents
case
to
title
case
or.
A
Sounds
good
thanks,
Tim
all
right,
I
have
one
and
it
is
about
the
releases
page,
so
just
want
to
give
a
little
show
and
tell
on
this.
So
this
is
the
release
download
page
here,
although
we
have
so
there's
a
change
to
where
the
upshink
kubernetes
container
images
are
where
they're
stored
at
and
they're
now
restored
at
registry.kates.io,
and
so
folks,
who
are
using
Upstream.
A
Kubernetes
images
should
use
this
registry
instead
of
the
kate's.gcr.io,
and
as
you
see
here,
we
have
that's
in
the
text
here,
but
it
actually
links
to
the
Google
Cloud
console
so
I
know.
I
know
we
had
a
I
pasted
a
link,
a
discussion
in
the
Sig
release,
Channel
also
reference
that
into
the
Sig
docs
Channel
as
well.
A
So
I
will
make
a
PR
to
remove
the
links
here
since
there's
no
longer
a
in
browser
interface
to
look
at
these
at
the
container
images
that
are
on
that
are
red
shootout
kit,
so
dot
IO.
So
please
take
a
look
so
just
look
out
for
that
support
request
and
that
should
also
be
back
ported
to
the
other
Branch.
The
other
versions
that
we
have
like
for
125,
124,
123
Etc,
so
any
comments
or
questions
on
that.
A
All
right,
I
have
other
two.
More
pull.
Requests
to
review
that
have
been
I've
had
requests
for
in
this,
for
the
heat
Patrol
Auto
completes
do
want
to
set
some
time.
I
do
like
to
to
test
this
out
just
to
make
sure
before
I
I,
add
in
a
an
lgtm
or
approved
or
make
any
comments.
So
I'll
take
a
look
at
this
and
to
make
sure
this
is
accurate,
looks
pretty
straightforward,
so
keep
an
eye
for
that,
and
one
more
I
think
this
is
on
Lisa.
A
This
is
this:
pull
request
is
on
leases
to
improve
the
lease
concept
page.
C
A
A
All
right
we'll
take
a
look
at
the
logs,
so
yeah.
A
All
right
does
anyone
else
have
any
one
more
here,
there's
from
Abby,
there
is
a
pull
request
for
draft
translation.
Script
pull
requests.
I
did
see
this
and
I
wanted
to
test
this
out
before
I.
Add
some
comments
about
this,
mostly
with
the
mostly
with
the
script
that
was
added
here.
D
Yeah
for
sure
we,
this
was
something
it's
been
kind
of
open
for
a
while,
and
we
chatted
about
it
in
the
localization
meeting
yesterday,
it's
from
Soko
on
the
Korean,
localization
team
and
I
think
it's
just
looking
for
more
reviews
and
possibly
to
approve
and
merge.
If
we
think
it's
ready,
it
is
a
draft
version
of
what
the
script
will
look
like,
so
that
folks
can
try
it.
D
We
also
have
an
improvements,
PR,
not
PR
issue,
and
we
have
a
lot
of
known
improvements
that
we
want
to
make
on
it
as
well.
But
this
is
just
to
get
a
draft
version
of
it
together
and
available
for
folks.
A
And
we
do
have
a
blog
post
for
that
live
as
well
with
the
image
registry
freeze
and
focuses
the
latest
blog
post.
Currently,
as
at
the
time
of
this
meeting
and
like
I
mentioned
before,
we,
there
is
a
change
from
the
old
registry,
which
is
keeps
that
g-star.io
to
registry.kate.io
and
well,
like
I
mentioned
before
how
the
current
release
Cycles
was
1.27,
so
1
1.27
is
released.
A
It
will
not
be
published
to
the
old
registry,
so
you
will
have
to
get
1.27
to
registry.kate.io
and
there's
also
further
discussion
that
I'm
not
too
well
versed
in
about
on
how
to
treat
Kate's
dot
kates.jcr.I
also
Tim.
If
you
want
to
add
any
more
comments
to
this.
C
C
So
as
a
project,
we
have
to
do
things
that
we'd
rather
not
do.
We
would
rather
have
the
big
cloud
providers,
give
us
lots
of
money,
and
then
we
can
serve
images
and
everyone's
happy.
C
That's
not
on
the
on
the
option,
and
you
know
communicating
is
going
to
be
a
big
part
of
this,
because
if
we
didn't
worry
about
our
end
users,
we'd
just
turn
off
the
images
and
it'd
be
great,
but
we
do
and
the
people
who
communicate
with
the
endless
users.
That's
the
you
know
various
different
bits
of
kubernetes,
but
docs
is
a
big
part
of
it.
C
So
I
guess
as
a
call
to
action,
which
is
that
if
you
see
a
change
coming
in,
which
is
about
helping
people
switch,
please
prioritize
work
on
that.
If
it's
an
article
about
why
you
should
switch
or
a
tutorial
on
making
changes.
Anything
like
that
and
you
see
that's
ready
for
review
or
whatever
it's
going
to
really
really
I
see.
I
will
yield
to
my
honorable
honorable
friend,
Mr
Wellington.
E
Hello,
just
a
question
about:
do
we
I
haven't
been
following
the
the
release
super
closely
this
cycle?
E
Is
there
already
a
I,
don't
imagine
this
would
be
a
kept
level
change,
but
is
there
a
a
release
level
issue
to
make
this
change
and
do
we
have
documents
that
are
referring
to
the
old
one
and
if
so,
this
old
URL
I
mean,
and
if
so
will,
will
there
be
a
forward
on
this
or
do
we
need
to
go
through
and
comb
comb
through
our
docs
for
this
particular
URL
and
make
updates?
C
Okay,
so
what
we're
talking?
What
the
big
changes
that
we've
got:
a
new
layer
serving
system
which
uses
a
proxy-
and
it's
quite
you
know
reasonably
well
designed
and
it
serves
from
AWS
by
default
and
falls
back
to
gcp
and
has
room
for
other
providers
like
it
uses
AWS
right
now,
but
it
may,
if
there's
a
very
explicit,
do
not
rely
on
how
it's
done.
It
will
change
and
then
we've
got
the
old
thing
and
the
old
thing
is
the
problem.
So
the
old
thing
is
cates.gci.ao.
C
A
And
I
believe
this
is
not
tied
to
to
the
release
like
coupled
in
like
in
term
in
terms
of
octave
in,
as
you
can
see
here,
the
this
will
be.
This
will
be
frozen
on
April
3.,
the
releases
in
April.
It's.
F
A
A
Thank
you
all
right,
I,
okay
and
I.
The
previous
PR
that
I
mentioned
was
part
of
that
change,
as
well
in
terms
of
documentation,
level
change.
But
this
is.
This
is
beyond
documentation,
level
changes,
more
of
of
user
behavior
and
users
changing
to
the
registry.kates.io.
So
that's
I
know
we.
There
is
a
banner
proposed
as
well.
That's
upcoming
on
the
on
the
kubernetes
dot,
dot,
IO
main
page
to
look
out
for
that
terms
of
there.
A
Well,
even
though
we
there
will
never
be
I
believe
that
we
never
will
never
have
the
right
amount
of
communication,
we
can
always
communicate
more,
as
there
will
be
folks
who
always
who
will
miss
all
all
Communications
with
this.
A
But
we
could
do
as
much
as
we
can
to
get
this
knowledge
out
and
if
there's
any
docs
out
there,
that
are,
that
will
help
folks
to
move
to
the
new
red
sheet,
we're
more
than
welcome
to
for
those
documentations
and
then
for
this
doc
changes
and
then
we'll
get
those
reviewed
and
hopefully
approved
fairly
soon.
Similar.
C
Story
on
blog
articles,
if
someone
would
love
to
if
someone
had
you
know,
has
the
appetite
to
write
a
blog
article
about
Al
and
why
to
move
to
the
the
new
registry,
great
fantastic.
That
will
be
a
really
good
contribution
to
make.
So
we
can
point
people
out
at
a
story
rather
than
just
docs,
which
can
be
a
bit
dry.
Yeah.
B
A
Not
necessarily
there's
people
could
use
registry
in
different
areas,
it
could
be
in
a
Helm
charge,
it
could
be
in
manifest
it
can
be
in
their
cstd
pipeline.
So
there's
many
different
places.
I
mean
this
just
tells
you
the
literal
change
of
which
Redshirt
to
use,
but.
C
But
like
a
story
exactly
that
talks
about
how
to
update
your
challenge
where
to
look
in
your
source
code,
you
know
to
bring
git
and
things
that
aren't
kubernetes
stuff.
That's
a
great
story
to
add
to
this.
Okay.
A
So
the
next
one
is
next
topic
of
discussions.
The
catacote
removal
so
just
some
background,
2022,
a
rally
which,
who
purchased
catacota,
remove
public
access
to
katakota
but
kept
the
tutorials
for
kubernetes.io
on
catacota,
and
then
they
contacted
us
in
December
that
they
would
like
to
stop
access
to
katakota
from
kubernet
from
kubernetes.io.
A
And
it's
an
update
with
that.
Tim
contacted
O'reilly
and
the
target
to
remove
catacota
from
kubernetes
is
the
end
of
March.
A
There
is
a
blog
post,
that's
in
draft
from
Natalie,
and
we
should
see
a
PR
fairly
soon,
and
this
is
another
topic
that
we
need
to
communicate
to
the
community,
and
this
is
more
of
the
the
end
user
Community
as
well
as
well,
for
a
lot
of
folks
who
are
learning
kubernetes
I
know
propose
a
tweet
from
the
kubernetes
contributor
account
as
well,
but
that's
that
counts
kind
of
targets,
developers
again
and
and
contributors
to
kubernetes,
not
exactly
folks
who
are
learning
kubernetes
or
more
of
the
end
users
as
well
same
with
lwkd
last
week
in
kubernetes
developments
as
well.
A
That
kind
of
that's
newsletter
kind
of
targets,
the
the
contributor
and
developer-
may
not
be
the
main
users
of
the
catacota
tutorials.
So
this
is
another
topic
that
we
need
to
communicate
a
lot.
Also
any
questions
or
comment
some
about
this.
A
C
A
F
A
Yeah
it's
fairly
soon.
Yes,
it's
also
how
close
to
the
other
big
announcements
with
the
red
stream
or
registry
being
frozen.
C
C
The
people
like
the
registry
freeze,
doesn't
change
anything
on
the
3rd
of
April,
because
all
of
the
images
that
were
there
on
the
3rd
of
April
are
still
there
and
then
on
the
4th
of
April.
We
don't
do
a
release
and
on
the
fifth
of
April
we
don't
do
a
release
and
then,
like
whatever
the
next
releases
on
I,
know
to
have
a
look.
C
The
11th
of
April
or
whatever
I
could
go
and
look
that's
when
people
start
going
hey,
why
can't
I
get
my
new
release,
whereas
on
the
31st
of
March,
that
is
when
there's
no
more
catacola,
we
will
find
a
way
to
disappear
it
and
if
we
don't
I,
think
O'reilly
we're
like
pressing
the
button
anyway.
Yeah.
E
F
A
Yeah
I
don't
think
we
I
mean
we
can't
do
much
about
the
April
3rd
announcements,
but
the
registry,
and
that's
going
to
be
done
anyway.
A
E
I
feel
like
it's
one
of
those
things
where
yes,
it's
it's
a
very
impactful
change,
but
I
feel
like
if
we
get.
If
we
get
the
work
done
it,
it
won't
necessarily
be
that
noticeable.
A
change
like
I.
Don't
think
that
this
is
like
a
week.
E
E
A
Be
a
more
empty.
We've
got
some
more
a
month
that
doesn't
have
a
lot
of
things
going
on
with
it
so
get
started,
but
really
cycle.
A
C
The
tone
I
got
back
from
Jessie,
you
know
and
we've
not
really
spoken,
it's
still
been
emailed,
but
but
it's
like
okay,
we
can
make
that
happen.
Not
yeah.
A
Yeah,
what
do
you
think
is
more
more
by
what's
more
viable
request,
the
end
of
April,
if
you
do
request
an
extension
or
we
just
targeted.
F
A
I
keep
finding
his
April's
about
April
15th
to
sorry
to
the
21st
I,
think
it's
18th
to
21st
or
something
around
those
States
yeah.
So
I,
don't
think
we
are
better
off.
This
box
will
be
prepping
for
a
coupon
before
that
and.
C
A
C
E
Hey
because
I
imagine,
the
cncf
will
also
ask
for
a
banner.
C
Well,
hang
on
so
around
the
3rd
of
April,
we'll
have
a
banner,
that's
already
sort
of
you
know,
underway
yeah.
F
C
C
D
C
D
C
I
haven't
told
anyone
this,
but
my
thinking
is
that
when
the
banner
is
up,
we
don't
have.
You
know
that
there's
a
banner
saying
there's
no
category
anywhere
and
then,
when
that
goes,
we
switch
it
to
some
pages.
Saying
there's
no
category
on
this
page.
C
Let
me
take
out
the
the
the
announcement
Banner
that
I
put
up
I'll
stick
in
the
in
the
agenda
document,
because
this
is
not
a
I
know.
This
is
not
a
a
super
welcome
message:
I
guess.
E
F
E
C
Probably
want
a
different
Banner
or
we
want
to
like
tweak
the
banner
so
that
we
have
this,
and
then
you
know
in
the
in
the
yaml.
It's
two
different
entries,
but
I
think
we
want
the
message
to
change.
To
sort
of
like
have
have
disappeared
and
what
have
you
and
did
did
you
know
have
cease
to
function
and
whatever
just
change
the
tense?
A
All
right,
yeah
I
I,
like
the
band
idea,
I,
don't
know
how
we're
going
to
I
mean
we
could
yeah
I'm,
trying
to
think
of
how
large,
how
logistically
we're
gonna
have
the
timing-wise
for
Banner
for
this
for
the
category
removal
and
also
the
banner
for
the
registry
as
well,
you
have
to.
C
A
Is
it
do
folks
think
it's
too
many
announcements,
and
one
in
in
the
Banners
are
personally
I
think
it's
okay
to
have
multiple
announcements
in
the
banner
as
they're,
both
important
announcements.
E
D
F
D
A
Although
this
thing
doesn't
really
maintain
kubernetes.dev
I
believe
that's
a
contribute.
Experience
like
they
could
have
a
banner
on
that
sites,
which
is
more
more
targeted
to
the
audience
of
folks
who
would
use
a
red
tree
but
I
end
users.
Will
you
use
a
red
tree
as
well,
so
I
think
it's
it's
also
appropriate
for
kubernetes.io
just.
We
should
also
be
mindful
that
the
cncf
historically
I
believe
the
Friday.
A
B
A
Have
to
take
a
look:
it's
around
April,
either
April
14th
or
April
16.,
the
banner
for
couponing.
You
will
be
up.
A
And
to
my
you
don't
mind:
I'm
going
to
place
here
that
your
message
and
slacks
some
options,
some
type
of
options
we
can
have
for
the
banner.
A
All
right
all
right,
any
other
comments,
questions
or
discussion
points
PR's
to
review
anything
from
the
books.
E
In
the
meeting,
I
can
put
my
mentorship
hat
on
just
for
a
moment.
The
LFX
mentorship
program
for
term
one
March
through
May,
is
now
accepting
applications
from
mentees.
So
we've
got
I
think
about
60
projects
across
about
oh,
what
was
it
about?
So
we
got
60
proposals
from
across,
probably
about
25
or
so
projects
across
the
cncf,
including
a
couple
of
kubernetes
things.
E
So,
if
you're,
if
you're
in
contact
with
folks
who
might
be
interested
in
getting
some
paid
work
and
some
mentorship
yeah
I
should
I'll
drop,
the
I'll
drop,
the
link
in
the
in
the
I'll
drop
the
link
to
the
repo
with
all
the
details
in
this
link,
but
yeah.
That's
that's
open
up
now
and
I've.
A
Is
this
mentorship
program
great
for
new
new
contributors,
folks
who
are
interested
in
contributing
to
open
source?
Yes,.
E
Absolutely
they
we've
got
a
fairly
liberal
acceptance.
He
can
be
a
student,
you
could
be
a
mature
contributor,
you
could
be
new
or
old
hat
to
to
to
open
source
if
you're
interested
in
one
of
the
projects
and
feel
like
you
can
contribute.
These
are
paid
opportunities,
so
by
all
means
we
do
tend
to
get
a
lot
of
students,
folks
who
are
in
the
equivalent
of
sort
of
second
to
third
to
fourth
year
university.
E
Also
gotten
some
folks
who
are
a
little
older
who
are
looking
for
a
career
change,
and
this
is
a
a
an
opportunity
to
again
just
become
involved.
So
if
you
know
somebody
yeah
feel
free
to
share
it,
there's
also,
there
was
a
cncf
foundation
tweet
this
morning,
I
think
that
went
out
as
well.
So
the
the
application
period
is
about
two
weeks
and
then
it's
about
a
three-month
program.
E
Full-Time
paid
pay
and
the
pay
depends
on
on.
F
A
Other
any
other
topics
or
discussion
points.