►
From YouTube: Kubernetes SIG Docs monthly APAC meeting for 20210126
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,
hey
everybody,
welcome
to
the
sig
docs.
This
is
the
apec
friendly
timed
meeting
nice
to
see
everyone.
I
am
jim
angel.
It
is
january
26
already,
which
is
crazy
or
27th
depending
on
where
you
are
in
the
world
and
first
let
me
open
this
up.
I
don't
believe
we
have
any
new
contributors
nate,
I
believe
you
are
returning.
Is
that
correct?
A
I
am
returning
yeah
I've.
I've
been
here
a
couple
of
times
perfect
and
I
have
seen
you
around.
I
see
you
you
know
face
to
face,
and
it
makes
sense
now
appreciate.
Well
welcome
back
and
good
to
see
everybody
so
moving
on
to
the
updates
and
reminders,
this
week's
pr
wrangler
is
brad
topple
and
so
brad
actually
created
the
pr
wrangler
schedule
and
didn't
have
someone
scheduled
for
this
week,
and
I
believe
his
statement
was.
A
If
I
broke
it
now,
I
got
to
buy
it,
and
so
brad
has
stepped
up
to
take
over
the
pr
englership.
Much
appreciated
next
week
is
celeste
borgen
and
I
know
celeste
is
aware
of
the
pr
wrangler
shifts.
But
if
you
are
not,
you
can
click
on
the
link
in
the
agenda
to
keep
up
with
the
pr
wrangler
shifts
that
are
upcoming.
B
Yeah,
so
a
few
things
I
put
in
chat,
the
integration
branch
for
the
dev
1.21
was
created
and
it
is
healthy.
One
of
the
shadows
is
going
to
conduct
the
branch
sync
later
this
week.
Also
tim
made
the
notes
for
major
for
the
under
major
notes
for
release,
notes,
he's
going
to
add
in
the
api
the
new
api
generation.
B
To
that.
So
that's
going
to
be,
I
guess,
promoted
to
everyone
in
the
release.
Yeah,
the
only
other
things
that
I
will
do
a
there's,
a
tomo
configuration
file
change.
I
need
to
do.
I
actually
created
the
pr
last
week,
but
I
kind
of
did
it
incorrectly.
So
I
closed
it.
It
did
not
merge
it
and
I'll
do
it.
After
once,
the
the
shadow
actually
does
the
branch
sync.
A
A
Is
awesome
good
to
hear-
and
I
did
want
to
bring
up
divya
message
me
on
slack
and
wanted
to
talk
a
little
bit
about
the
communication
process,
potentially
at
next
week's
sig
docs
meeting,
and
so
I'm
raising
awareness,
if
folks
have
interest
there,
that
conversation
should
hopefully
take
place
next
week.
Really.
The
essence
is
at
the
end
of
the
release,
at
least
especially
this
previous
release.
It
was
a
little
hectic
when
it
came
to
publishing
the
blog.
When
does
this
go
out
the
door?
A
When
is
this
merging,
and
there
was
a
lot
of-
I
guess-
avoidable
problems
that
maybe
could
have
been
solved
a
little
bit
of
planning.
So
just
having
a
discussion
on
how
can
we
plan
a
little
better
going
into
that
cycle
and
it's
one
of
those
areas?
That's
a
little
bit
of
a
blurred
area
between
sig
release,
sig
docs,
the
release,
communications
team,
the
release,
docs
team,
and-
and
so
I
look
forward
to
talking
more
about
that.
B
Yeah
one
thing
to
add
to
I
think,
for
this
release:
that's
going
to
be
a
theme
that
we're
trying
to
make
those
teams
that
are
very
end
of
the
cycle,
heavy
so
that
we
don't
have
to
rush
for
a
lot
of
those
tasks
like
for
like
for
the
blogs
and
for
release,
notes
for
the
for
the
major
themes
it
has
been
in
the
past
very
last
minute
rush.
So
I
think
that's
going
to
be
one
of
the
good
takeaways
from
this
release.
A
Nice,
I
look
forward
to
that
and
I
also
like
it
seems
like
a
lot
of
the
release.
Activities
are
becoming
more
opt-in
and
it's
requiring
a
lot
more
active
participation
from
the
other
cigs,
which
saves
a
lot
of
folks
from
docs
and
released
from
having
to
chase
contributors
for
the
enhancements.
A
So
I
like
that
cool
moving
on.
I
just
added
this
and
I
don't
mean
to
put
you
on
the
spot
yoko,
but
korean
localization
update.
If
you
feel
comfortable,
giving
an
update.
C
Sorry
sure,
as
you
know,
korean
localization
team
has
a
branch
strategy
and
we
make
new
milestones
for
every
two
weeks
or
slightly
changed
three
weeks.
Currently,
we
are
working
on
third
localization
branch
of
120
and
tomorrow
we
will
change
the
branch
to
post
one.
So
we
are
also
clean
status.
A
Awesome,
thank
you
and
would
you
mind
putting
that
the
new
leader's
name
in
the
chat
sign
copy?
I
don't
want
to
screw
up
the
spelling
you
you
need
a
little
sorry,
the
reviewers,
oh,
the
reviewer
yeah.
So
if
you
could
put
in
a
oh,
no
reviewer,
if
you
could
put
the
name
in
the
agenda,
that
would
be
very
helpful
for
me.
C
Why
not
I
I?
I
should
check.
A
His
english
yeah
no
problem
at
all.
I
appreciate
the
update.
Is
there
anything
that
we
can
help
with
from
a
sig
doc's
perspective?.
C
A
I
will
discuss
it
later.
Perfect
sounds
great
yeah.
That's
that's
been
a
really
a
great
help,
starting
the
sub
project
for
localization,
giving
a
opportunity
to
have
those
direct
discussions
there
yeah
yeah,
look
forward
to
that.
That
sounds
good
all
right.
Moving
on
so
for
the
blog
update,
I
have
no
updates
personally.
Does
anyone
have
any
updates
they'd
like
to
share
about
the
blog.
A
Not
hearing
a
ton,
we
will
think
that
things
are
chugging
along
and
so
moving
on
to
issues
in
pr.
So
I
have
a
few
agenda
items
that
I
added.
I
wanted
to
raise
awareness
about,
but
there's
not
really
too
much
to
discuss
so
the
first
one
being
fixing
the
calendars
and
I've
spent
a
lot
of
effort
trying
to
consolidate
all
of
our
calendars
to
one
shared
google
calendar,
and
I
think
someone
accidentally
deleted
this
apec
friendly
meeting
from
the
segdocs
official
calendar.
One
of
the
main
contributors
it
very
well
could
have
been
myself.
A
I
have
no
clue.
I
definitely
am
pretty
reckless
with
my
calendar.
If
it
was
me
that
is
my
fault,
but
nevertheless
I'm
going
to
add
the
apac
friendly
meeting
back
to
the
calendar,
I'm
going
to
invite
the
sig
docs
localization
sub
project,
as
well
as
the
main
mailing
list
for
sig
docs,
and
this
is
really
just
a
long-winded
way
of
saying
you're
going
to
get
spammed
via
email
and
I'm
sorry
in
advance
with
the
calendar
invites.
A
The
one
thing
I
wanted
to
bring
up
is:
I
think
it
was
six
months
ago
it
might
even
even
have
been
closer
to
a
year
from
now.
I
know
I
was
talking
with
a
lot
of
the
localization
teams
as
far
as
figuring
out
a
way
to
generate
content
reports
from
google
analytics
for
korean
localization
for
the
various.
I
think
you
know,
however
many
different
localizations
we
have
sending
the
information
the
analytics
that
is
required
to
make
informative
decisions
based
on
what
what
pages
are
popular.
A
What
pages
would
be
worth
translating
and
it
sounds
like
it'd-
be
very
helpful
for
the
localization
teams.
Originally,
we
were
looking
at
creating
a
single
analytical
report
that
had
multiple
languages
on
it,
but
it
didn't
have
enough
information
to
be
effective,
and
so
I
have
this
problem
of
essentially.
A
Do
we
send
a
bunch
of
emails
out
with
a
bunch
of
individual
reports,
or
do
we
send
one
with
lacking
critical
information
and
ultimately,
I
think
the
best
solution
for
the
localization
teams,
as
well
as
sig
docs,
is
going
to
be
send
out
a
specific
report
per
localization
via
email
and
then
before.
Turning
on
the
floodgates
and
before
opening
up
this
automation
sending
out
instructions
on
how
to
filter
them
in
gmail
filterman
outlook,
maybe
some
different
options
there.
A
So
it's
more
of
an
opt-in
as
opposed
to
everybody
getting
10
emails
every
month
or
you
know
15
emails
of
different
reports.
So
I'm
open
for
suggestions
if
somebody
has
a
better
solution.
I've
kind
of
molded
over
this
for
a
little
too
long
now,
but
I
can't
think
of
a
better
way
other
than
just
sending
these
reports
out
to
the
localization
email
group
and
then
have
it
be
opt-in,
essentially
any
thoughts
on
that.
C
Yeah,
it's
not
ideal,
but
I
think
the
those
statistics
is
not
used
to
frequently,
for
instance,
yeah
in
case
of
korean
localization
team.
We
maybe
need
in
in
half
a
year
or
before
a
presentation
or
conference,
so
it
it's
not
I'm
not
sure
we
need
to
automate
or
provide
access
to
all
of
us.
A
Yeah,
I
like
the
the
feedback,
and
I
appreciate
the
thought,
because
if
we
can
send
it
out,
you
know
once
every
six
months,
maybe
that's
a
little
better
to
manage
than
once
every
month
or
something
more
noisy.
So
I
appreciate
that
and
this
might
be
something
worth
bringing
up
at
the
localization
monthly
meeting.
I
know
that
will
be
held
the
first
monday
of
february,
which
is
coming
up,
so
I
might
bring
it
up
there.
The
other
thought
is
initially.
A
I
was
thinking
of
using
the
subproject's
email
address,
so
there's
a
kubernetes
dash,
localization,
docs
email
address.
One
other
option
could
be
creating
a
unique
group
just
for
the
reports
that
way
you
completely
separate,
everybody
doesn't
want
to
be
involved,
and
if
you
want
to
get
these
reports,
you
join
into
a
unique
email
which
might
might
make
more.
A
C
Actually,
korean
localization
team
initiative
translating
blog
content
gesso,
we
usually
focus
on
the
technical
document.
Well
in
case
of
blog
document,
blog
content.
It
includes
author's
name,
so
we
thought.
Maybe
if
we
can
include
the
translator's
name
in
the
blog
content,
then
it
might
be
useful
for
encourage
encouraging
contributors
to
translate
the
blog
content.
A
Cool,
I
I
think
that
sounds
very
reasonable.
I
look
for
other
folks
to
have
comments
or
opinions
towards
it,
but
it
makes
sense
that
if
the
author
is
partaking
in
in
the
translation,
there's
no
reason
not
to
give
them
credit
for
the
work
that
they
put
in.
In
my
opinion-
and
I
don't
know,
does
anybody
feel
any
different?
I
feel
like
this
should
be
generally
a
thumbs
up.
A
C
A
A
Yeah-
and
I
think
it
would
also
be
good,
especially
for
the
localization
meeting,
to
bring
this
up
for
other
folks.
That
might
be
translating
the
blog
as
well.
I
think
it
applies
to
any
language.
If
somebody
puts
in
the
work
to
translate
a
blog
to
another
language,
I
believe
they
should
get
credit
for
assisting.
A
A
A
You
all
right
and
then
moving
on.
I
do
have
a
reminder
here
that
we're
eventually
going
to
have
a
date
for
the
q4
review
and
q1
and
2
planning
we're
almost
out
of
q1
entirely.
So
it's
more
just
a
q2
planning,
q4
q1
review,
so
there'll
be
a
date
coming
soon.
I
just
need
to
talk
with
some
of
the
other
tech
leads
on
making
a
decision.
A
Ultimately,
we
look
to
have
a
date.
You
know
around
two
weeks,
three
weeks
out
in
advance,
to
give
folks
an
opportunity
to
review
where
we're
currently
at
add
any
comments.
They
want
to
talk
about
and
adequately
plan
and
schedule
for
that.
So
just
a
general
reminder,
I'm
dragging
my
feet
on
that
and
we'll
have
more
updates
here
shortly,
and
that
is
everything
on
our
agenda.
Does
anyone
else
have
anything
they'd
like
to
discuss
today.
D
Hey
I'm
wondering,
if
is
appropriate
for
me,
to
give
a
quick
show
of
the
kubernetes
api
browser
I
just
recently
announced
in
the
channel.
I
would
love.
A
D
D
Okay,
this
is
a
kubernetes
api
browser,
the
basic
the
reason
I
developed
this
is
that
I
felt
a
need
to
do
api
browsing
in
an
interactive
way,
because
you
know
the
kubernetes
api
is
a
huge
collection
of
resources,
api
groups
or
all
different
versions
and
definitions,
and
that
the
definitions
are
mostly
embedded.
D
So
there
are
quite
some
efforts
on
that.
I
just
want
to
show
what
show
you
what
I
have
done
and
that
we
can
figure
out
how
what
we
will
do
with
this.
So
in
this
version
0.4.0
we
have
api
versions
7.13
to
the
latest,
one
for
each
and
every
version.
We
have
resources
and
definitions
and
operation
based,
for
example,
if
I'm
joining
in
into
the
resources.
D
D
D
For
example,
you
have
to
specify
a
name,
but
this
kind
of
details
are
missing
in
the
current
api
specification.
So
I
I
worked
on
this
so
for
create
get
an
update.
You
will
get
different
schema.
You
click
one
of
them.
You
get
the
details
of
the
definition
of
that
resource,
the
api
version.
D
This
is
not
very
worthy
compiled
from
the
the
official
one
right,
sorry
and
you
you
will
have
object
method
clip
of
for
create.
I
have
carefully
reviewed
all
the
descriptions
of
all
resources
ever
since
1.13
to
make
sure
everything
is
accurate.
I
compared
all
the
definitions,
according
to
their
validation
logic,
so
this
reference.
This
data
is
more
accurate
when
compared
to
the
official
striker.json
file,
if
you're
wondering,
for
example,
the
the
whole
structure
of
the
the
a
resource,
you
can
click
this
button.
D
D
If
you
want
to
switch
to
a
different
version
of
the
definition
click
this
button,
you
will
have
different
versions.
For
example,
the
same
resource
has
been
defined
in
many
api
versions,
maybe
in
different
api
groups.
You
can
switch
to
that
version
very
quickly,
and
if
you
want
to
compare
comparison,
you
can
do
that.
D
You
see,
okay
between
these
two
versions.
I
got
two
new
fields,
so
this
is
a
comparison.
If
you
want
to
do
a
whole
comparison
ever
since
the
many
versions
ago,
you
can
copy
this
button.
This
is
a
history.
D
Okay,
now
we
know
the
mutating
webhook
resource
was
added
in
1.15
and
it
has
never
been
changed
until
later
version
1.20,
we
became
two
two
more
fields,
so
this
is
about
a
resource
exploration.
If
you
want
to
try
it
by
yourself,
you
can
click
this
button.
This
will
give
you
the
an
editor
in
this
editor.
This
is
a
microsoft,
manicure
editor.
You
can
try
your
things
here
and
edit
it
and
explore
the
result
at
csn
or
number
and
download
it
locally.
D
Similarly,
you
can
also
explore
the
operations
it's
a
red
group
and
whatever-
and
in
this
tool.
I
also
added
some
quick
hot
pages.
For
example,
here
you
see
verb.
What
what's
that
you
will
create
this
question?
Mark
okay,
there
will
be
some
actual
nations
about
about
request,
verbs,
how
they
are
mapped.
D
Okay,
this
screen
is
too
small
click
this
button,
it's
a
full
screen.
So
here
you
get
a
full
reference
of
all
the
verbs
you
you
will
see
in
the
apis,
so
that
is
basically
basically
all
the
things
you
will
get.
If
you,
okay,
we
have
so
many
definitions
in
kubernetes.
D
All
right
deployment
everything
so
so
that's,
basically
almost
all
about
this
tool,
so
so
this
is
designed
to
be
very
interactive
and
it
was
also
designed
to
be
friendly
for
mobile
devices.
If
you
click
this,
this
is
how
you
will
see
it
on
a
mobile.
D
A
Awesome
yeah,
that's
incredible!
I'm
curious,
so
I
see
the
value
where,
where
this
can,
you
know,
do
a
lot
more
exploratory
searching
and
a
lot
more
discovery
than
what
we
have
currently
today.
A
I'm
curious
where
you
envisioned
this
incorporated
into
kubernetes
website
alongside
you
know
some
of
the
existing
reference
documentation
or
like
what
we've
just
merged
with
with
the
the
reference
generation
and
pulling
those
onto
one.
Would
this
be
separate,
or
I
guess
what
is
your
current
opinion
on
everything.
D
You
know
there
are
many
existing
tools
for
people
to
explore
open,
open
api
specification,
for
example,
swag
apis,
regular
viewer,
all
those
kind
of
things
they
focus
on
the
operation
definition,
but
in
kubernetes
the
most
difficult
part
for
users
or
developers
are
the
big
structures
so
that
that
is
the
focus.
D
I
believe
this
tool
will
be
very
useful
for
our
users
and
developers
and
I'm
working
on
open
source
the
whole
thing
so
that
it
can
be
hosted
somewhere.
So
if,
as
for
where
to
host
it,
that
would
be
a
community
decision.
I
don't
know,
I
don't
have
a
good
idea.
A
Got
it
so
almost
entirely
separate
from
kubernetes
website,
at
least
that's
what
I'm
hearing
as
an
open
source
tool?
If,
if
developers
wanted
to
explore
more
about
the
api,
is
that
correct.
D
Yeah,
okay,
it
is
currently
published
as
a
container
image.
If
you
host
the
image
on
accommodated
website,
the
whole
whole
service
will
be
part
of
the
kubernetes
website.
A
Got
it
yeah?
I
think
that
there's
a
wider
discussion
to
be
had
with
the
community
if
we
do
want
to
merge
those
together.
I
know
that
there's
been
a
lot
of
effort
to
consolidate.
So
one
of
the
things
that
has
happened
over
the
past
two
or
three
years
with
kubernetes
is
there's
been
the
release
notes
website
that
was
created,
which
is
filtering.
The
different
release,
notes
on
a
separate
url.
A
I
think
it's
rel.k
dot,
io
rel
notes,
maybe
and
then
in
addition
to
that,
there
was
download
kubernetes,
which
was
recently
brought
back
into
the
kubernetes
org
for
downloading
the
different
components
of
kubernetes,
and
then
there's
also
the
kubernetes
devks.dev
website
for
contributor
documentation,
which
is
not
managed
by
sig
documentation
as
you're
you're
well
aware
of,
and
so
what
I
really
want
to
make
sure
that
what
we're
doing
here
is
consolidating
where
we
can
and
I
would
like
to
see
you
know
as
much
things
as
we
can
under
kubernetes
website,
where
it
makes
sense.
A
A
B
A
Cool
and
before
we
wrap
up
here
is
there
any
other
topics?
Folks
like
to
discuss
jimmy,
I
like
how
you
surprised
me
with
that
awesome
demo
at
the
end
of
the
meeting
here
I
thought
we
we're
going
to
wrap
up,
and
that
was
incredible.