►
From YouTube: Kubernetes SIG Docs monthly APAC meeting 20200128
Description
For more info see https://git.k8s.io/community/sig-docs
A
A
A
This
week's
PR
Wrangler
is
Steve
Perry
and
next
week's
Wrangler
is
Caitlyn
Bernard,
so
really
quickly
on
PR
Wranglers,
so
tuned
a
lot.
A
poopa
was
up
last
week
to
be
a
Wrangler
and
I
didn't
see
any
activity
from
him.
I
didn't
you
know
when
I
pinged
him
with
the
weekly
reminder
in
slack
it
didn't
get
a
response
for
anything.
So
just
has
anyone
heard
anything
from
him?
A
No
okay,
so
in
that
case
we
will
need
to
open
a
couple
of
PRS
and
remove
his
ability,
his
approver
status,
hopefully
just
temporarily,
but
the
signature
Dex
and
the
steering
community
has
asked
that
we
be
really
proactive
about
keeping
our
approver
permissions
nice
and
tight.
We
generally
do
a
really
good
job
of
that.
So
I
would
like
for
us
to
keep
doing
a
good
job
of
that.
So.
A
You
know
it's
either
Jim
and
myself,
we'll
have
to
approve
it.
It's
probably
easier.
If
someone
else
opens
it,
you
like
Jim
and
I,
are
gonna
have
to
do
the
handoff
one
way
or
another.
Someone
else
can
open
that
PR,
but
I,
don't
know
what
do
you?
What
do
you
think
Jim?
Can
we
can
we
delegate
that
and
just
approve
it
or
should
when,
should
you
or
I
open
that
and
then
they
take
each
other
for
the
approval?
I?
Don't.
B
B
Think
that
they'll
be
grief
just
because
it's
a
decision
based
on
confer
backs
and
it's
not
necessarily
a
permanent
decision
or
anything
I'm,
happy
to
open
it
or
run
but
I.
Think
it's
more
of
a
delegation
of
responsibilities
and
the
reason
I
saying
Brad
is
considering
your
role,
as
you
know,
shadowing
to
be
in
that
okay.
C
C
C
You
know
my
one
comment
would
be
that
we
feel
like
we
have
enough
process.
So
what
if
it
turns
out
hypothetically,
he
was
on
a
cruise
for
a
week
or
something
I
didn't
know
and
he's
like
welcome
back.
What's
that
we
welcome
it
back,
welcome
them
back,
okay.
So
it's
it's
kind
of
a
I
like
the
way
you're
phrasing
it
it's
it's
a
it's
an
easily
revert
able
step,
but
it's
a
very
proactive
step
to
get
attention.
C
C
B
To
be
totally
honest
and
clear,
with
everybody,
I've
missed
a
week
doing
the
PR
angular
shift,
and
this
mistake
that
has
been
made
before
and
I
think
that
that
type
of
response
is
a
new
type
of
response
to
be
a
little
more
proactive
and
cleaning
up
that
approvers
and
owners
file.
But
I,
don't
think
it's
necessarily
out
of
line,
especially
with
the
attitude
of
hey,
we're
glad
to
have
you
back,
but
we
want
to
be
active
on
who's,
approving
who's,
not
approving,
and
if
you're
not
actively
doing
what
you
said
you'd
be
doing.
A
One
of
our
approvers
in
China
had
missed
his
Pia
Wranglers
shift
and
hadn't
responded
for
a
while.
It
did
the
same
thing.
I
opened
there
at
PR
to
do
disabled
as
approver
status
and
said
hey.
Let
me
know
that
you're,
okay,
when
you're
ready
to
come
back.
Let
me
know
you're
welcome
back
at
any
time
and
I
think
maybe
like
three
weeks
later
I
he
responded
and
said:
hey
sorry,
I've
been
absent
for
work.
I'm
gonna
be
absent
from
work
for
a
while,
but
I'll.
Let
you
know
when
I
can
come
back
so
yeah.
A
C
A
A
It's
like
I
have
not
checked
in
with
him
at
all
in
this
release
cycle,
yet
I
know
it's
a
little
early
in
the
cycle
for
docks,
but
I
did
see
the
discussion
around
merging
versus
rebasing.
That
happened
a
couple
weeks
ago.
So
Jim
do
you
know.
Was
there
any?
Did
you
hear
any
follow
up
after?
After
all
of
that,
the.
B
Last
that
I
heard
from
beneath
was
there's
gonna,
be
the
forceful
rebase
of
the
release
branch
to
overwrite
the
Chinese
localization
changes
so
there'd
be
no
longer
any
conflicts.
I
haven't
followed
up
to
see
if
that's
still
the
case
or
not
afterwards,
but
I
was
helping
beneath
with
that
out
and
letting
me
know
that
it's
okay
to
make
that
change
and
that's
the
agreed-upon
direction.
B
There
is
the
release
engineering
tooling,
and
we
had
the
meeting
around
using
that
tool,
as
opposed
to
doing
it
manually
so
I
still
very
much
still
work
in
progress
and
pulling
the
bits
and
pieces
together
to
start
working
on
that,
but
I'd.
Imagine
that
picking
up
steam
here
shortly
I
have
a
CKA
exam
to
take
on
Friday,
it's
kind
of
taking
so
many
efforts,
I'm
looking
forward
to
that,
and
once
that's
out
of
the
way
I
feel
like
the
KL
tooling
for
release
engineer
will
be
one
of
my
top
priorities
to
get
through.
B
A
A
A
D
D
A
E
So
I'm
mentioning
it
in
this
meeting
because
it's
kind
of
it's
kind
of
an
admin
thing,
it's
kind
of
quite
wide,
reaching
and
I
think
I've.
We
need
to
rebase
to
click
on
it.
I
missed
the
last
meeting,
but
I
kind
of
want
to
get
like
an
opinions
on
it
as
much
as
I
want
to
get
Oh.
You
know
that
the
the
actual
review
is
probably
not
the
important
thing
here
like
what
do
people
think
about
doing.
This
am
I
saying
the
right
thing.
A
E
B
Think
it's
a
great
great
proposal,
speaking
me
personally,
this
is
no
reflection
on
anything
here
about
this
whole
request
template
it's
a
lot
of
words
in
the
sense
of
if
I'm
doing
a
pull
request.
I
might
be
quick
to
just
ask
through
it
or
delete
it
or
make
it
change
very
quickly
to
just
move
on,
but
I
would
imagine
if
you're,
a
first-time
contributor
that
opinion
might
change
or
that
that
preference
might
change
I,
don't
know
if
there's
a
way
to
trim
down
the
amount
of
hard
coded
versions
are
in
there.
B
While
you
do
touch
us
every
release,
it's
a
very
manual
process,
a
yard
tweaking
each
one
of
those
versions,
you're
increasing
or
decreasing.
If
there's
a
robot,
no
problem,
but
since
it's
not
I,
don't
know
if
there's
a
cleaner
way
to
lay
this
information
out
and
with
me
not
doing
the
work
and
he'll
act,
it
was
suggested
alternative.
I'm,
happy
to
see
this
merge
well.
E
C
D
E
D
A
A
We
had
some
folks
notice
that
when
people
went
to
kubernetes
io
/
security,
they
were
directed
to
the
Chinese
version
of
that
page
and
they
were.
There
was
no
way
to
access
the
English
content,
because
every
time
that
you
visited
it
would
forcibly
redirect
away
to
the
Chinese
version.
So
after
some
digging
there's
a
complete
description.
A
Of
the
underlying
issue
in
was
it
18
8
9,
5,
no
18
896,
but
basically
the
way
that
Hugo
handles
aliases
means
that
Hugo
is
completely
agnostic.
If
multiple,
if
multiple
files
have
the
same
alias
in
it,
and
they
both.
If
you
lead
an
alias
with
a
slash
that
points
to
like
a
top-level
domain
alias
and
that
will
it
will
create
a
redirect
to
point
to
that.
But
Hugo
does
absolutely
no
validation
of
whether
there
are
conflicting
aliases,
whether
one
or
more
localizations
or
pages
have
an
alias
to
that
particular
slug.
A
So
Hugo,
basically
just
it
renders
those
aliases
before
it
renders
any
content.
So,
whichever
alias
it
renders
last
ends
up
being
the
one
that
wins.
So
it
would
render
English
first
and
then,
because
Chinese
also
had
a
leading
slash
in
front
of
the
security,
alias
it
rendered
Chinese
over
the
top
of
that.
A
So
basically,
the
TLDR
from
this
is
when
you
create
aliases,
remove
the
leading
slash
so
that
way
that
when
people
go
to
see,
for
example,
if
people
want
to
see
a
security
warning
in
in
French,
they
can
see
that
specific
security
warning
and
they
don't
get,
for
example,
forcibly
redirected
to
English
content
and
the
other
way
around.
If
people
yeah
just
basically
make
sure
to
not
to
use
a
leading
slash
when
you're,
creating
an
alias
make
sure
that
that
contacts
at
localization
that
an
alias
is
specific
to
a
localization.
B
A
That
is
not
going
to
work.
I'm
not
getting
screen
previously
I
have
way
too
many
screens
open
to
try
and
navigate
but
yeah.
If
you
look
at
the
poll,
requests
18,
8
95,
you
can
see
just
compare
the
diff
and
you
can
see
the
difference.
Many
thanks
to
Christophe
lekker
for
fixing
that
and
also
bringing
it
to
our
attention.
A
B
B
Oh
now,
VMware
series
Duffy
was
working
through
an
example
on
the
API
server
and
I
know
that
Duffy
in
the
past
has
worked
a
lot
with
Ian,
cold
water
as
well
on
security
presentations
and
at
the
end
of
those
presentations.
They
have
quick
links
to
security
documentation.
So
things
like
our
back
things
like
general
security
context,
vulnerability
CBE's.
So
what
I
saw
was
someone
trying
to
use
a
link
that
maybe
they
were
comfortable
with
using
that
no
existed
in
this
case,
it
was
case
that
IO
slash
our
back,
so
I
was
like
hey.
B
This
would
be
a
really
quick,
alias
to
put
in
case
that
IO
slash,
our
back.
Will
relief
will
redirect
back
to
the
are
back.
Documentation
makes
a
lot
of
sense,
Jim
and
Karen.
Both
brought
up
some
very
excellent
points
about
this,
potentially
opening
Pandora's
box
of
for
creating
aliases
for
documentation
and
they're,
not
really
where
the
pages
live.
Do
we
want
to
get
into
this
mess
of
you
know
this
documentation
really
is
this
URL,
but
now
we
actually
have
this
alias
here.
B
You
know
I'm,
not
necessarily
in
love
with
the
solution
or
the
PR,
as
really
just
a
quick
fix,
but
I
realized.
This
is
something
that
should
not
be
decided
by
one
individual
or
one
PR
mm-hmm,
and
that
we
should
really
have
the
conversation
as
a
team
about
do
we
want
to
add
in
those
short
links
and
and
furthermore,
from
the
redirects
issue
that
you
brought
up
a
few
bullet
points
earlier.
B
Maybe
it's
not
even
the
right
place
to
have
that
redirect,
instead
of
having
it
in
the
actual
overall
static,
redirect
area,
maybe
it's
better
suited
for
the
individual
page
itself,
as
opposed
to
where
it's
at
today.
So
two
questions
are:
do
we
want
to
make
short
links
in
the
efforts
of
security
and
simplicity
for
slide
decks
and
things
that
nature
is
that
where
we
want
to
draw
the
line
or
in
the
second
part
being?
Is
that
the
right
approach?
Oh.
A
A
A
A
Guess
I
like
the
idea
of
making
making
it
immediately
clear
in
the
content,
the
URL
where
that
content
is
so.
If
people
want
to
look
at
that
file,
they
can
see
without
having
to
open
the
the
the
underscore
redirects
file.
What
it's
redirecting
to
like
the
underscore
redirects
file.
Isn't
a
self
disclosing
file.
A
You
have
me
if
you
know
it's
there,
you
can
look
at
it,
but
there's
nothing
to
tell
you
in
if
you're
looking
at
the
content
of
a
file,
there's
nothing
to
tell
you
that
the
sub
redirects
file
is
where
the
content
gets
assigned
as
a
particular
redirect
so
I
like
the
idea
of
having
using
an
alias
in
the
front
matter
of
a
file
to
disclose
the
redirect
for
that
file.
I.
Think
that
makes
a
lot
of
sense.
B
A
A
If
we,
if
we
make
an
issue
about
it,
I
mean
the
work,
is
actually
fairly
straightforward.
It's
tedious,
but
it
is
straightforward.
There's
not
a
lot
of
ambiguity
in
the
tasks
so
like
we
could
I
mean,
would
technically
qualify
as
a
good
first
issue.
It
wouldn't
be
a
pleasant
first
issue,
but
it
you
know
it
does
meet
the
criteria
for
a
good
first
issue.
A
C
B
Cool
so
I'll
open
up
an
issue,
this
kind
of
aligns
with
the
security
Doc's
approach.
As
far
as
consolidating
our
security
information,
these
links
might
change,
they
might
move,
it
sounds
like
keeping
them
on
the
front
matter.
There
at
least
keeps
them
in
the
same
documentation
open
up
the
issue
open
up
the
length
of
PR,
then
to
set
issue
with
the
minor
change
in
that
way.
I
think
this
becomes
more
of
you
know,
I
hate
to
say,
hey
Seth.
B
This
is
your
problem
now,
but
but
it
becomes
more
of
an
initiative
for
the
the
security
sub
project
and
as
that,
that
starts
getting
cleaned
up.
I
I
see
this
being
a
very
minor
issue,
but,
like
I
said,
I
wanted
to
make
sure
that
this
is
team,
consensus
and
not
Jim,
saying
here's
a
great
idea,
for
you
know
one
minute
fix
and
then
why
the
heck
are
we
doing
this?
You
know
so
I
appreciate
the
comments.
A
A
A
Okay,
Korean
localization,
ft
June
is
not
able
to
make
it
tonight
very
sad,
but
go
go.
Go
live
your
best
life,
but
he
did
leave
us
an
update.
They
have
a
new
reviewer
which
is
cool
and
they've
finished,
localizing,
one
that
16
so
a
Korean
localization
team
and
let's
see
they
are
two
milestones
deep
into
localizing,
one,
that's
17,
which
is
amazing
and
they
have
a
local
offline
meetup
for
docs
localization
on
February
13th,
presumably
in
Seoul,
so
awesome
job,
good
work,
Korean
team.
A
B
B
The
link
is
now
posted
in
the
meeting
minutes,
and
my
action
item
from
here
on
out
is
deleting
all
of
the
archive
emails
or
all
the
archived,
Google
Docs,
pointing
them
to
this
repo
and
then
updating
the
current
to
point
for
the
previous
meeting
minutes
to
be
in
that
repo
a
little
bit
further
than
just
having
that
repo
merged
with
their
old
meeting,
there's
also
a
readme
inside
of
that
repository.
So
once
20:20
becomes
2021.
Whoever
wants
to
create
that
next
archive
of
documentation
will
have
a
ability
or
process
to
do
so.
A
A
F
Tim
weighed
in
and
I
cleaned
up
the
document
accordingly
and
they
had
great
feedback
and
then
one
thing
you
added
was
if
there
was
a
way
to
have
like
a
dollar
amount
and
a
vendor,
and
it's
a
straightforward
explanation.
So
I
added
the
sentence
as
best
I
could,
but
without
actually
going
getting
a
better
quote.
I,
don't
know
how
to
put
a
vendor
or
dollar
amount
in
the
variable
brackets,
which,
by
the
way
I
like.