►
From YouTube: K8s SIG Docs Meeting for 20230307
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
Alrighty
today
is
the
7th
of
March
2023..
It's
the
7th
of
March
in
Europe
in
the
United
States.
It
may
be
the
8th
of
March
in
a
couple
other
places
where
people
might
be
joining
from
and
welcome
to
the
bi-weekly
sync
docs
meeting
the
community
meeting
that
we
have
every
two
weeks.
My
name
is
Natalie
I'm
one
of
your
co-chairs
and
we
also
have
Ray
lahano
as
part
of
the
meeting.
Also
another
co-chair,
who
can't
actually
speak
in
today's
meeting.
A
Ray
is
nicely
doing
a
bit
of
multitasking,
which
is
great
being
able
to
be
here
but
and
not
be
have
to
be
muted.
The
whole
time
I've
added
the
agenda
into
the
into
the
chat
where
you'll
be
able
to
see
I'm
just
going
to
re-add
that
again
for
folks
who
are
joining
and
given
that
this
is
a
sick,
docs
community
meeting
for
communities.
That
does
mean
that
we
abide
by
the
kubernetes
code
of
conduct,
which
paraphrasing
just
means
be
kind
and
respectful
to
one
another.
A
That
is
in
these
kinds
of
meetings,
in
our
slack
channels,
in
agendas
and
so
on.
For
today's
meeting
we
do
have,
as
I
mentioned
a
little
earlier,
a
bit
of
a
light
agenda.
So
as
we're
going
through.
A
If
folks
have
things
they
want
to
add,
feel
free
to
do
so,
but
I
will
make
a
call
out
at
the
end
of
our
meeting
in
case
folks,
have
other
topics
that
they'd
like
to
bring
up
alrighty
so
without
any
further
Ado
we'll
get
started,
and
what
I'd
want
to
do
is
just
check
if
we've
got
any
new
contributors
and
joining
with
us
in
the
call
that
would
like
to
speak
up
and
say,
hello,
I
have
a
feeling.
No,
but
gonna.
Ask
the
question
anyway.
A
Looks
like
we're
all
usual
folks,
beating
around
stick
docks,
which
is
great,
but
for
folks
who
are
maybe
watching
this
in
the
future,
feel
free
to
always
come
and
attend
a
sydocs
meeting.
If
you're
new,
we'd
love
to
have
you
and
help
you
get
some
of
your
contributions
in
for
the
community
alrighty.
Let's
go
through.
Some
of
the
other
agenda
points
that
we
have
in
terms
of
our
usual
meeting
meeting
etiquette.
A
As
you
may
know,
we
do
have
PR
wrangling
as
part
of
sigdocs,
which
is
generally
folks
who
are
on
the
on
the
agenda,
should
I
say
on
the
schedule
for
trying
to
get
contributions
and
PR's
through
our
pipeline.
In
this
week's
PR
Wrangler
is
Brad
Topol,
who
has
a
Depeche
shadowing
him
for
this
week
for
those
on
the
call
or
who
are
watching
and
who
are
interested
in
the
shadow
program
for
PR
wrangling.
You
can
find
it
specifically
in
the
link
in
our
agenda
under
PR
wrangling
shifts.
A
You
can
also
contact
myself
or
Ray
any
of
the
seek
docs
chairs,
and
we
can
also
help
you
set
up
a
shadow
wrangling
spot
and
then
next
week's
PR
Wrangler
we've
got
Tim
who's
on
the
line.
Tim
will
be
next
week.
Fine
girl
as
well,
and
we'll
also
make
sure
that
every
every
bi-weekly
chat
that
we're
doing
either
in
slack
or
in
the
meetings
that
we're
updating
focus
on
who
the
ring
was
up.
A
So
big
thanks
to
Wranglers
for
this
and
next
week,
and
with
that
I
want
to
go
quickly
into
the
information
that
we've
got
for
the
current
release.
That's
happening,
which
is
released.
A
1.27
wrangling
is
going
to
be
important
to
get
a
lot
of
stuff
through
release
as
well,
but
specifically
here,
there
is
no
a
big
update
in
terms
of
docs
having
I
had
a
quick
check
of
the
latest
release
meeting
with
Mickey,
noting
that
the
current
status
for
doxy
is
green
and
that
the
specific
update
was
all
good
smiley
face.
So
that
sounds
great
on
the
doc's
end.
A
But
I
do
want
to
read
a
couple
of
points
here
that
Ray
has
mentioned
in
terms
of
some
of
the
great
content
and
information
and
resources
that
have
been
created
as
well
before
that,
just
to
quickly
go
through
a
couple
of
dates
to
remember
code
freeze
coming
up
very
soon.
In
a
week,
March
15th,
the
22nd
of
March,
is
test
freeze
and
then
the
4th
of
April
for
us
will
be
really
important.
That's
when
the
docs
review
and
completion
deadline
is
also
set
for
this
release.
A
Okay,
now
we've
raised
quick
updates
here
and
Mickey
and
Ray.
They
did
several
syncs
for
the
main
branch
syncing,
the
main
branch
into
the
dev
1.27
Branch
we've
got
Linked
In
the
agenda,
the
merged
and
opened
PRS
for
that,
and
I
also
want
a
big
shout
out
to
Ray
generally
for
a
just
being
a
great
Emeritus
advisor
on
the
release
front,
both
generally
for
the
release
process,
but
also
specifically
for
docs.
A
Where
he's
been
doing
a
tremendous
tremendous
job,
and
we
can
tell
that
because
of
these
really
great
resources
that
he's
helped
to
create
so
specifically,
you'll
see
it
linked
in
the
agenda.
He's
created
a
YouTube
playlist
on
how
to
sync
main
into
Dev
for,
like
a
future
release.
Branch
and
doing
that
by
video
is
just
such
a
I.
Think.
A
That's
such
a
really
great
help
as
well,
so
feel
free
to
take
a
look
at
that,
especially
for
folks
who
are
looking
into
possibly
doing
some
work
as
as
a
release
Shadow,
which
could
be
also
really
great
for
that
as
well.
And
then,
finally,
he
raised
the
last
update
visit
draft
PR
to
update
the
instructions
to
the
release.
Doc's
handbook
for
folks
who
are
not
aware,
there's
been
a
few
retros
that
have
happened
from
the
last
release.
A
A
So
a
big
thanks,
Ray
thanks
for
linking
that
information
there
in
the
agenda,
I
want
to
stop
talking
and
just
double
check.
If
anyone
has
anything,
they
want
to
add
or
comments
that
they
want
to
jump
in.
On
a
couple
of
those
things
that
Ray
has
mentioned
there.
A
Nope
other
than
maybe
Asylum
Round
of
Applause,
another
big
plus
one
thanks
to
Ray
for
that.
For
that
great
content
and
then
let's,
let's
move
right
along.
So
we've
got
just
a
couple
of
small
extra
bits
on
the
agenda,
but
before
I
get
into
the
questions
and
discussion
points
I
just
want
to
quickly
check.
Does
anyone
have
any
issues
or
PR's
that
they
would
like
to
bring
up
in
the
meeting
today
before
I
get
to
myself
and
Chris
nigga's
points
there.
A
Nope,
that
sounds
like
a
no
no
worries
at
all
then
moving
on
very
swiftly
to
the
next
part
of
the
agenda.
We
had
our
monthly,
really
monthly
localization
meeting
yesterday.
Those
are
localization.
A
Subproject
meetings
take
place
once
a
month
and
I
wanted
to
put
information
there
that
Abby
Abigail
McCarthy,
who
is
our
localization
sub
Project
Lead,
will
be
going
on
leave
for
the
next
few
months
and
she's
welcoming
me
a
new
person
to
her
family
and
and
and
so
myself
and
Seeker
will
be
taking
over
for
that
time.
A
While
she
takes
them
that
much
needed
leave
we'll
be
taking
over
and
helping
out
with
the
localization
subproject
Seiko
is
actually
doing
some
great
work
and
will
likely
be
very
interested,
I
believe
in
hopefully
being
taking
on
a
a
sub-project
co-lead
role,
and
so
this
will
be
great
work
for
Seko
to
jump
in
here
with
the
Community
Management
and
a
lot
of
the
meeting
management
there
and
I'll
be
jumping
in
for
any
kind
of
approval
and
things
that
need
to
happen
in
terms
of
the
localization
stuff.
A
So
just
putting
that
out
there
as
a
general
FYI.
If
you
need
anything
for
localization
in
terms
of
just
anything
at
all,
feel
free
to
reach
out
to
myself
and
Seiko
first
off,
as
Abby
will
very
rightly
be
M.I.A
for
the
next
little
while
and
if
there's
anything
else
that
we
can
help
you
with,
or
always
the
Stig
docs
localization
localizations.
That
slack
channel
is
always
a
great
place
to
go
to
First.
A
All
right
done
a
lot
of
talking
today,
thanks
for
bearing
with
me
folks
but
I,
do
want
to
move
on
to
another
agenda
item
that
someone
else
has
Chris
negus
I'd
love
to
hand
it
over
to
you.
With
this
specific
discussion
Point
around
taking
on
a
larger
writing
project.
Please
take
it
away.
B
Yeah
thanks
see
I
I
feel
like
I've
just
been
out
of
the
loop
here
for
a
while
and
I
wanted
to
come
back
and
see
if
there's
something
useful
I
could
do
other
than
just
you
know,
editing
PRS
and
you
know
responding
to
issues
so
I
noticed
that
we
have
this
this
project,
this
sheet,
72
that
has
a
list
of
of
sort
of
larger
long-term
issues
that
they
want
to
take
on
and
I
would
like
to
take
on.
B
You
know
one
of
those
maybe
or
something
else
that
needs
to
be
done.
So
I
was
hoping
to
have
a
little
discussion
on
what
would
be
most
useful.
There
are
a
couple
things
that
I
maybe
have
a
little
more.
You
know
interest
in
or
a
little
more
understanding
of
that.
That
would
be
most
helpful
but
I'm.
Looking
looking
for
feedback
here,
what
people
think.
A
C
I
guess
it
depends
Chris
on
on
your
appetite
for
doing
sort
of
time,
pressured
things,
because
we
have
a
couple
of
time
pressured
things
and
we
have
some.
B
Other
things
how
how
what
time
pressure
I
mean
as
in
like
tomorrow
or
a
week
or
a
month,
this.
C
Month,
so
really
in
March,
there's
two
things
that
the
kubernetes
project
needs
to
do.
We
have
to
not
run
out
of
money
and
Sig
docs
is
part
of
that
is
helping
people
to
not
pull
images
from
GCR.
B
I
am
very
familiar
with
this
issue,
actually
because
we're
doing
some
of
our
own
documentation
on
that
at
AWS.
So
yes,
so
what
specifically
do
we
need
to
do
about
that
for
on
the
kubernetes
side?
Well,.
C
There's
a
bunch
of
things
so
I
mean,
for
example,
if
if
someone
wanted
to
collate
a
a
sort
of
a
cheat
sheet
or
a
word
but
like
a
hey,
there
are
a
few
Cloud
providers.
Who've
got
official
guidance
on
how
you,
as
a
kubernetes
cluster
operator,
can
make
best
use
of
cloud
services
I
mean,
for
example,
if
you
were
on
AWS,
you
could
use
ECR,
you
could
set
up
pull
through
caching
and
there
may
be
some
official
AWS
guidance
to
link
through
we.
C
If
you
take
that
approach
Chris,
you
know
we
we
want
to
frame
this,
not
as
shaming
people
or
you
know,
being
being
didactic.
It's
like
you
know.
It's
still.
C
It's
trying
to
be
both
Bob
Geldof
on
the
stage
at
live
age,
shouting
about
money
and
look
it's
up
to
you,
here's
what
we'd
like
you
to
do
and
you
have
to
you-
have
to
just
to
square
that
Circle
and
it's
super
important.
So
that
is
a
thing
that
would
be.
You
know
great
to
get
help
with.
B
B
Yeah,
that
would
be
a
good
one.
Do
you
happen
to
know
who
I,
who
would
be
a
contact
for
those
I
could
price?
You
know,
look
it
up
if
you,
if
you
don't
but.
C
A
Wondering
if
Ben,
if
Ben
and
Elder,
might
be
someone
on
the
Google
end,
that
would
definitely
be
an
another
great
person
to
reach
out
to.
B
A
If
you,
if
you
need
a
quick
find
of
who,
which
Benjamin
Elder
I'm
speaking
of
okay.
D
And
on
the
cncf
side
you
may
want
to
reach
out
to
Jeff,
chica
Jiffy
might
be
able
to
help
with
some
of
that
as
well.
What.
D
Sika
SCI,
a
or
s-I-c-a.
B
Okay,
great
and
and
Tim,
were
you
thinking
in
terms
of
actually
docs
going
into
kubernetes
stocks
or
blogs
or
reaching
out
other
ways?
What's
what
are
the
thoughts
on
that.
C
My
my
opinion
I,
like
I,
trust
you
Chris,
like
you
know,
the
people
who
come
to
this
meeting
have
got
I
I've
got
judgment
about
what's
right
and
you
know
go
with
what
feels
right.
Okay,.
B
Okay,
yeah,
that
sounds
good
I,
think
that's
very
valuable.
I
know
this
has
been
an
issue
for
a
long
long
time.
I
know
I,
remember,
Eddie,
Zane,
working
on
this
and
Eddie
zanesky
a
long
time
ago,
trying
to
say
hey.
We
can't
this
is
not
sustainable,
so
yeah
I'm,
very
glad
to
help
on
that.
You
said
there
was
another
one,
though
what
was
the
other
issue
you're
going
to
mention.
C
Captain
code,
it
gets
turned
off
a
few
days,
apart
from,
like
the
dates
didn't
come
out,
particularly
well.
The
the
catacota
switch
off
date
is
at
the
end
of
this
month,
and
the
GCR
thing
is
the
third
of
April
so
pretty
close,
and
then
we've
got
cubecon
and
then
the
release
coming
up
busy
times.
Okay,.
A
So
on
that
it
was
it's
technically
off
for
everyone
else
other
than
kubernetes,
but
then
the
kubernetes
access
is
now
also
being
shut
off,
so
it'll
be
completely
shut
down,
as
it's
being
repurposed
for
I.
Think
paid
plans
as
part
of
O'reilly's
General
kind
of
learning
platform
got.
D
A
Question
I
definitely
don't
think
you've
dropped.
The
ball
I
think
we
were
very
concerned
about.
Firstly,
just
getting
the
communications
out,
which
we've
mostly
done
where
we
are
on
that
is
I.
We
were
looking
to
hopefully
have
a
banner
on
site,
but
obviously
with
the.
A
That
Banner
kind
of
superseded,
so
is
that
not
happening
the
next
step?
Is
we've
had
a
we've?
Had
this
information
go
into
the
kubernetes
newsletter,
Cube
weekly
I
believe
it's
called
so
that
went
out
recently
I
believe
only
the
week
of
the
blog
post,
which
was
a
couple
weeks
back
and
then
the
last
thing
to
do
is
just
to
email.
Thank
you
and
then
the
last
thing
to
do
is
to
kind
of
email
all
of
Dev,
which
I'll
be
doing
soon.
A
I
was
kind
of
waiting
on
the
banner,
but
that
never
ended
up
eventuating.
So
so
we'll
go
ahead
with
that.
But
then
that
means
that
comms
wise
we're
generally
done
with
what
we
had
planned
to
do
outside
of
doing
a
bit
more
friendly
spamming
on
slacks,
although
I
do
have
a
hand
up
from
Tim
one.
C
Thing
I'd
love
to
do
just
just
for
English
for
now
and
let
the
localizations
pick
things
up
in
their
own
process
is
a
doxy
page
info.
So
we
we
can
and
we
do
it
a
couple
of
not
many
pages
but
I.
Think
three
or
four
pages
have
got
a
special
wide
at
the
top
of
the
page
thing
saying
something:
important
and
I
would
chuck
one
of
them
at
the
top
of
all
the
pages
where
catacoda
is
now.
C
It's
going
read
this
article,
that's
what
that's
what
we
should
put
up:
okay,
As,
a
detail
on
that
Nate,
it's
a
short
code
in
markdown,
but
some
of
the
pages
you
will
need
to
edit
are
HTML.
So
you
will
need
to
work
out
what
it
renders
to
and
then
paste
that
in.
But
that
is
not
that
hard
yeah.
A
So
so,
to
answer
your
questionnaire,
that's
generally
where
we
are
where
communication
has
generally
taken
place
and
then
the
next
aspect
of
that
work
is
that
actually
do
the
removal
of
the
tutorials
and
the
link
through
themselves
and
in
the
general
issue
which
I
will
find
in
a
second
and
pop
into
our
meeting
agenda.
But
then
we
do
have
a
list
out
of
actually
all
the
pages
affected
that
have
them
on
there,
too.
So
at
least
finding
where
all
that
will
be
is
centralized
at
the
moment.
Yeah.
A
C
Well,
it's
it
so
I
think
you
know
mate,
you're,
you're
sort
of
you've
picked
up.
You
said
you'll
pick
up
the
catacomba
piece
and
that's
great
and
Chris.
You
said
you've
got
some
capacity
and
that
that
registry
explanation
piece
and
like
not
everyone's
on
a
cloud
provider.
You
know
there
is
a
bare
metal
story
to
tell
as
well,
but
a
lot
of
people
are
in
the
cloud
and
we
can
see
where
the
money's
going,
because
we
can
look
at
the
IP
address
it
ranges
and
so
on
so
getting
that
story
out
about.
C
C
That's
always
really
important
to
tell,
however,
if
anyone's
watching
this
on
YouTube
and
thinking
well,
that's
great
I
missed
the
meeting.
What
else
could
I
work
on
then
14725
document
TLS?
We
have
a
really
long-standing
issue
that
I
recommend
is,
in
my
opinion,
documents
setting
up
TLS
for
a
workload.
It
is
such
a
crucial
task
and
we
do
not
yet
document
it
well.
C
So
if
if
someone
comes
along
and
and
there
is
a
one,
more
person,
who's
got
capacity
to
pick
up,
you
know-
and
it's
not
a
small
task
to
do
it's
a
big
big
piece
of
work.
But
if
someone's
got
capacity
on
that,
that
would
be
a
great
one
to
pick
up.
C
B
C
A
Yeah,
but
it
would
be
something
that
would
probably
be
a
little
bit
more
effort
in
terms
of
the
of
the
work
specifically.
So
even
starting
on
that
now
means
you,
wouldn't
you
wouldn't
probably
be
finished
in
it
very
very
soon,
so
to
speak.
Maybe.
B
Not
as
much
of
the
time
you
know
crunch
on
this
one
as
well,
yes
right.
A
A
Thanks
thanks
to
Chris
for
bringing
that
up,
I
think
it's
it's
one
of
those
things
where
we
might
have
some
things
that
we
want
to
do
long
term,
and
then
we
also
have
to
be
a
bit
reactive
when
things
are
taking
place
that
are
a
little
bit
outside
of
our
control.
So
the
image
registry
and
then
with
katakura,
is
definitely
two
of
those
areas
that
I
think
have
kind
of
superseded.
Other
plans
that
we
may
have
had
for
for
work.
A
So
thanks
thanks
a
bunch
for
being
willing
to
jump
in
amen.
I'll,
add
in
also
the
general
issue
into
the
notes
in
a
moment,
but
I
wanted
to
quickly
open
up
to
check.
Does
anyone
have
any
other
last
agenda
topics,
issues
or
PR's
that
they'd
like
to
bring
up
today.
A
Going
once
going
twice
all
right,
then
we've
had
a
really
great
Speedy
meeting
and
I
wanted
to
thank
everyone
for
taking
part
I
will
post
information
that
I've
just
mentioned.
For
example,
the
general
issue
tracker
for
the
catacota
shutdown
and
also
I've
got
the
TLs
documentation
work.
A
That
Tim's
also
mentioned
I'll
pop
that
in
the
notes,
as
well,
for
example,
for
you
Chris
to
find
for
later
on
big
thanks
to
everyone
again
and
another
big
shout
out,
and
a
big
thanks
to
Ray
for
a
lot
of
the
great
release,
content
that
you've
been
working
on
really
great.
To
see
that.
Thank
you
for
sharing
and
we'll
see
you
all
again
in
two
weeks.
Thanks
for
joining
bye-bye.