►
From YouTube: K8s SIG Docs Meeting for 20210105
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,
hello,
welcome
everybody
to
the
sigdoc's
weekly
meeting.
This
is
the
first
meeting
in
a
wild
post
holidays.
I
think
we
had
about
two
weeks
off
or
so
personally
speaking
as
I
just
mentioned,
I
have
been
in
a
holiday
funk,
so
this
might
be
a
quick
sig
ducks
holiday
meeting,
but
nevertheless,
it's
great
to
see
everybody
today
is
january
5th,
2021
officially
before
moving
on.
Is
there
any
new
contributors
on
the
call?
I
see
a
lot
of
friendly
faces,
taylor
shapiro,
I
don't
believe
we've
met.
B
Problem
at
all
yeah-
no
problem-
I
am
a
software
engineer
looking
to
get
more
actively
participating
in
the
kubernetes
community,
so
yeah
nice
to
meet
you.
A
Awesome
yeah
welcome,
definitely
you're
in
the
right
spot
and
feel
free
to
ask
any
questions,
throw
anything
out
and
chat
there
if
anything's,
confusing
or
ambiguous.
I
know
we
throw
around
things
that
might
seem
normal
or
general
terminology
that
seems
standard
to
us
that
newcomers
might
find
hard
to
follow
and
we're
happy
to
make
that
easier
to
understand.
You
know
we're
here
to
help
other
folks
find
ways
that
they
can
help
cool
anyone
else
just
joining
for
the
first
time.
C
There
you
go
yay,
okay,
yeah,
I'm
just
kind
of
here,
because
I've
been
working
with
kubernetes
for
a
long
time.
I'm
an
instructor,
but
I've
never
really
contributed
to
the
project
at
all,
and
I
thought,
if
I
was
going
to
do
that
anywhere,
I'd
want
to
know
how
that
works
with
documentation,
because
I
think
that's
the
most
fun
part
is-
is
documentation.
A
Awesome
welcome
much,
like
I
mentioned,
with
taylor
as
well
feel
free
to
interject.
This
is
relatively
an
informal
gathering.
Find
us
in
slack.
Ask
questions.
You
know
we're
here
to
help
out
so
sounds
good.
Welcome,
good
to
see
some
new
faces.
A
Moving
on
to
the
updates
reminders,
so,
first
of
all,
many
thanks
to
brad
topple
for
getting
our
pr
wrangler
shift
through
our
schedule
together
for
2021.
So
a
big
round
of
applause
there
for
brad
for
folks
who
don't
know
every
week,
there's
a
pr
wrangler.
What
this
is
is
a
person
in
the
kubernetes
community,
specifically
for
sick
docs,
with
approver
status
that
essentially
make
sure
that
there's
no
prs
that
are
gunked
up
and
that
we're
actually
merging
and
approving
closing
prs,
pull
requests,
etc.
A
So
that's
a
role
that
most
approvers
or
all
approvers
should
fulfill
at
least
a
couple
times
throughout
the
year
and
brad
threw
that
schedule
together
in
many
thanks.
So
brad
put
it
together
and
brad
is
also
the
pr
wrangler
this
week.
So
it
must
be
a
glutton
for
punishment,
and
next
week
is
tim,
tim
banister,
sf
tim
on
the
call
and
proverbs
make
sure
you
know
your
pr
wrangler
shift
and
go
check
that
out
on
github
for
the
new
dates.
If
we
need
to
switch
things
around,
we
can.
A
And
moving
on
to
the
agenda
so
first
things:
first,
the
121
release
ray
or
someone
on
the
call
want
to
give
update.
D
On
that
yeah
I
have
a
few
things.
The
release
cycle
actually
officially
starts
next
week.
The
shadow
application
ends
this
friday
also
created
a
pr
to
update
the
docs
role
handbook-
that's
still
open,
I
just
created
this
morning
and
that
just
added
some
things
to
how
to
track
kep,
reviewers
improvers
for
a
tech
review
for
the
docs,
also
synced
master
into
the
dev
1.21
branch,
and
that
went
through
with
no
errors,
and
that
was
merged
also
this
morning,
and
that's
it
for
me.
A
Awesome
thanks
ray
and
for
the
folks
that
are
joining
us
today.
So
every
three
months
I
believe
it's
not
every
four
months,
there's
a
kubernetes
release
and
part
of
the
sig
doc
special
interest
group.
We
have
a
smaller
subgroup
that
is
part
of
the
sig
release.
There's
a
ton
of
cigs
but
sig
release
is
in
charge
of
actually
getting
kubernetes
out
the
door
and
the
sub
group,
the
sig,
docs
doc
sig
release
sub
group
is
responsible
for
making
sure
documentation
goes
out
the
door
with
that
release
so
part
of
our
weekly
meeting.
A
We
track
the
release
as
it
progresses
as
well
as
make
sure
there's
anything
we
can.
You
know
help
out
with
block
things
of
that
nature,
but
in
general,
and
I'm
hoping
hopefully
not
jinx
in
this
for
right
here
in
general,
we
find
that
the
release
cycle
is
pretty
calm
for
docs
early
on
there's,
not
a
ton
to
do,
and
then
really
things
kind
of
catch
on
fire
towards
the
end.
There
that's
true
cool
all
right.
A
Moving
on
for
the
blog
update
is
there
anyone
on
the
call
wants
to
give
us
an
update
on
the.
A
A
Hearing
a
whole
lot
of
nothing,
I
also
blog,
is
great.
It's
going
to
come
up
shortly,
though,
with
the
thing
I'm
going
to
talk
about
okay
yeah,
so
we
can
circle
back
then,
and
talk
about
tim's
piece
there
regarding
the
blog
all
right.
Moving
on
to
issues
in
pr's
celeste,
you
know
take
this
one
away.
E
Yeah,
so
there
are
two
prs
here
that
I'm
kind
of
bringing
to
sig
docs
in
in
kind
of
representing
the
working
group
naming
as
well,
so
the
first
is
a
fairly
large
update
to
one
of
the
tutorials.
E
The
stated
intention
of
this
tutorial
of
this
update
was
to
remove
kind
of
inappropriate
terminology
around
master
and
slave.
However,
paul
czar
also
took
the
opportunity
to
replace
mongodb
with
radius
in
this
example,
which
is
a
very,
very
large
change
now
so
from
a
working
group
naming
perspective,
this
is
good
to
go.
This
has
our
sign
off.
What
we
need
at
this
point
is
the
sig
docs
review
as
to
whether
this
is
still
excuse
me
still.
E
Okay,
stephen
augustus
has
taken
a
look
at
it
and
from
both
mine
and
his
perspective,
it
is
still
teaching
the
fundamental
kubernetes
thing
that
needs
to
be
taught
in
that
tutorial.
So
I
don't
think
it's
a
problem,
but
but
redis
and
mongodb
are
not
necessarily
equivalent
technologies.
E
So
this
needs
a
really
dedicated
technical
review.
That's
really
what
it
comes
down
to
and
we
need
to
decide
as
a
sig
whether
we
are
okay
with
this
change
or
not,
and
I
think
the
follow
up
for
honestly.
Both
of
these
is,
I
will
post
them
in
the
channel,
and
we
will
have
an
asynchronous
discussion,
but
please
be
aware
that
this
requires
a
bit
of
thought.
E
Okay,
so
the
second,
the
second
pr
in
here
is
removing
master
slave
from
the
stateless
terminology,
applications
again
from
the
perspective
of
of
sig
docs
or
from
of
working
group
naming
we're
kind
of
okay
with
the
change.
But
it
is
a
paired
change
in
terms
of
it
is
also
removing
mongodb.
E
Tldr
they
both
require
a
bit
of
thought
on
our
part
and
paul
probably
isn't
going
to
loop
background
at
this
point
to
get
these
pros
of
the
line.
So
I
think
we
also
need
to
take
over
the
pr
if
we
want
them
to
merge.
E
So
again,
kind
of
from
our
perspective,
like
the
example
still
makes
sense,
and
and
it's
not
so
much
pushback
as
it
makes
sense,
but
it's
not
using
a
necessarily
one-to-one
equivalent
technology.
E
E
A
Yeah-
and
I
know
this
came
up
a
couple
weeks
back
and
I
took
a
look
at
it
and
you
know
I.
I
fear
that
we're
going
to
get
kind
of
lost
in
this
kind
of
method,
this
discussion
about
the
technologies
being
used
or
being
replaced,
and
I
don't
think,
there's
one
sole
owner.
That's
going
to
have
the
answer
saying
yeah,
you
know,
let's
merge
this
as
this
or
you
know,
let's
talk
technology
and
talk
about
the
technology,
solutions
that
we're
using
I'm
tempted
to
say
as
long
as
there's
not
a
major
objection
or
technical
reason.
A
Why,
if
this
looks
sound
and
technically
is
accurate,
my
vote,
or
my
gut
says
we
should
merge
this
and
deal
with
any
sort
of
implications.
After
that,
I
would
imagine
that
things
like
writers
and
mongodb
in
the
example
sense
that
we're
we're
replacing
here.
I
doubt
those
are
being
ran
in
production.
I
hope
that
they're
not
being
followed
like
blindly
into
production
or
causing
any
sort
of
impact
of
that
nature.
A
E
And
I
think
this
kind
of
brings
up
another
just
general
kubernetes
issue,
which
is
who
owns
examples,
and
the
answer
is
and
frankly,
given
that
there
is
no
specific
owner.
I
think
if,
from
a
six
doc
perspective,
we
are
okay
with
them,
regardless
of
the
time.
D
A
You're
breaking
up
their
semester.
If
we
lost
you
there,
timothy
of
your
hand,
up.
F
Yeah,
I
I
want
to
emphasize
you
know:
celeste.
You
pointed
out
that
there's
some
need
for
technical
review
and
there's
a
few
unresolved
questions.
F
Things
like
paul
has
used
his
own
container
image
registry
or
his
own
container
image,
so
not
the
end
of
the
world,
but
we
would
typically
use
a
kubernetes
container
image
and
a
kubernetes
container
repository,
sorry
registry.
F
E
Yeah,
I
agree-
and
this
is
why,
like
we're,
gonna,
have
to
take
over
these
prs
to
get
them
over
the
line
and
probably
take
paul's
image
and
use
a
kubernetes
container
image,
etc,
etc,
etc.
E
E
A
I
I
don't
want
to
go
on
the
record
that,
even
though
I'm
on
recording
saying
it
but
yeah
no
I'll
take
a
look
at
those,
and
I
agree-
and
I
appreciate
the
heads
up
tim.
I
completely
agree
if
they're
using
a
personal
repo
or
anything
like
that,
there's
still
technical
review
to
be
had
still
the
the
docs
review
to
be
had,
but
I
I
think
we
take
away
the
discussion
about
mongodb
versus
rightist.
This
is
moving
in
the
general
direction
of
greater
good.
F
F
A
Yeah,
that's
an
excellent
point
tim
and
I
would
encourage
folks
who
have
a
little
bit
of
time
to
kill,
take
a
look
at
the
pr
that's
proposed
and
just
walk
through
the
examples
see
how
it
works
on
your
machine.
You
know
it's
a
lot
of
the
ways
that
I
do.
My
technical
testing.
G
F
A
Yeah
that'd
be
great
that
way,
so
folks
aren't
having
to
go
in
the
pr
and
looking
at
the
changes
they
can
look
at
the
proposed
change
in
a
preview
website
and
just
follow
those
directly
through
you
know.
Some
of
the
folks
are
new
joining
us
in
the
call
is
100
okay
and
encouraged
just
to
comment
on
one
of
these
pr's.
As
a
complete,
flyby
saying,
hey,
look.
I
went
through
these
instructions,
things
broke,
things
didn't
break
things
and
while
things
didn't
go
well,
that's
incredibly
valuable.
A
You
don't
need
to
know
any
fancy
terminology
or
hashtags
or
slashes
or
any
of
that
stuff.
Just
a
drive
by
saying,
hey.
I
followed
these
instructions
and
they
worked.
Is
awesome
so
I'll,
throw
that
out
there
as
well
there's
no
magic
or
beauty
behind
reviewing
the
technical
aspect
of
of
those
pr's
cool
anything
else
in
that
celeste
or
do
we
hit
it.
A
Now
I'll
be
messaging,
you
guys
and
make
some
progress
on
that
as
well.
F
Sure
yeah,
let
me
just
I
don't-
have
to
write
things
on
screen,
but
I
know
what
roughly
what
it's
about
yeah.
So
this
is
an
issue
from
the
steering
committee
really
raised
by
jordan
liggett
and
it's
about
the
announcement
banner
mechanism
and
it's
also
about
the
announcement
banners
so
outside
of
sig
docs.
The
steering
committee
has
agreed
that
the
steering
committee
is
responsible
for
for
banners
and
sort
of
the
public
image
of
the
kubernetes
project.
F
So
as
far
as
I'm
concerned,
that's
a
settled
discussion
steering
committee
is
entitled
to
to
make
that
that
choice
and
I'm
happy
with
it,
but
we
need
a
mechanism
to
make
that
possible,
and
so
just
earlier
today,
erv
one
of
the
chairs
put
in
place
the
last
piece
for
one
of
two
prongs
of
of
my
approach
to
fixing
this,
and
so
my
two
prongs
for
fixing.
This
are,
first
of
all,
a
mechanism
to
automatically
trigger
a
netlify
deploy.
F
That's
now
live,
and
so
I'm
going
to
circle
back.
I
will
come
back
to
the
announcement
banners,
but
I'm
going
to
go
back
and
talk
about
the
blog.
This
change.
That's
that's
shipped
means
that
if
you
put
a
blog
article
up,
it
will
now
automatically
publish,
I
will
drop
an
announcement
in
slack
as
well
to
make
that
clear
and
I'll
mention
it
in
the
blog
channel.
F
F
Yeah,
okay,
maybe
maybe
I
should
go
high
level
all
right.
What
we're
going
to
do
is
we're
going
to
have
a
pr
that
looks
at
what
the
date
is
and
sets
the
banners
based
on
what
banners
are
configured
for
that
date.
They'll
only
ever
be
one
banner,
but
you
could
have
like
a
long-term
banner
like
we've
had
at
the
moment.
We've
got
a
long-term
banner
about
black
lives
matter,
but
then
for
kubecon,
we've
gone
short
term
kubecon
banner
and
then
go
back
to
the
long-term
banner
we've
done
that
through
human.
F
You
know
effort
and
it's
not
really
a
good
use
of
people's
time
to
be
managing
banners
like
that
when
computers
can
do
the
job
well
enough,
however,
to
make
something
honor
the
date
and
so
on.
We
need
the
builds
to
happen
automatically,
and
so
that's
that
that
pr
that's
already
landed,
that's
in
so
twice
a
day.
Netify
will
trigger
a
build
of
the
site.
Like
I
say
it's
only
landed
about
an
hour
ago,
so
I
don't
know
if
it
works,
but
it
does
for
kubernetes.dev.
F
So
I
think
it'll
work
for
kubernetes,
io
and
then
the
second
pr
that's
there
for
this
issue
is
to
put
in
place
a
new
mechanism
that
karen
bradshaw's
looked
at
jordan's
looked
out,
a
few
people
have
looked
at
that's
pr.
F
F
That
pr
might
need
a
tweak
or
two
everyone.
Who's
got
access
to.
Github
is
welcome
to
look
at
the
implementation
to
provide
constructive
feedback
to
ask
questions
if
it's
not
clear,
but
the
idea
there
is
that
the
steering
committee
will
be
able
to
approve
changes.
Some
you
know
someone
who's
doing.
Communications
can
propose
a
pull
request
and
then
the
steering
committee
can
provide
funnel
sign
off
to
say
yes,
we're
going
to
schedule
a
new
banner
or
we're
going
to
change
the
dates
or
whatever
you've
got
optional.
Css
you've
got
optional
titles.
F
C
A
A
F
No,
no
thanks
so
jim
and
evie
have
today
been
helpful,
unblocking
the
the
automatic
deploys
given
the
time
of
year,
I'm
not
feeling
blocked
on
this.
I'm
feeling
that
I've
I've
been
supported.
So
thank
you.
A
Awesome
cool
I'm
making
a
note
here
to
bring
that
up
weekly.
I
do
agree
that
until
that's
totally
merged-
and
I
think
it's
good
just
to
touch
point
on-
even
if,
at
the
very
least
for
general
awareness,
cool
any
other
issues
or
pr's
before
moving
on
that
folks
want
to
discuss
about
that,
might
not
have
been
included
in
the
agenda.
F
Mention
that,
because
I'm
working
on
this,
I'm
not
working
on
the
really
good
work
that
philippe
martin
was
doing
around
the
api
reference
documentation
and
when
I
have
a
bit
more
time.
I
I
hope
to
look
back
at
that
again,
because
it
was
really
good
work.
A
Cool
yeah,
I
agree
to
that
and
if
folks
have
a
link
to
the
api
refwork
that
philippe
was
doing
and
could
throw
in
the
chat,
I
could
link
that
in
the
agenda
or,
if
you
just
want
to
throw
it
directly
in
the
agenda,
that
would
help
out
cool
I'll.
Take
that
out
awesome
why
I
would
move
too
quick.
You
do
have
the
next
item
here
under
discussion
for
the
pr
wranglers
tim.
Was
this
just
about
the
absence
of
the
pr
anglers
or
is
there
something
further?
You
want
to
talk
about.
F
Yeah,
so
basically
I
put
that
on
before
brad
did
the
work,
so
thanks
brad.
A
A
A
All
right
now,
I
heard
a
bunch
of
a
bunch
of
folks
speaking
up
hope.
Everyone
had
a
great
holiday
and
looking
forward
to
2021
talk
to
y'all
later
goodbye.