►
From YouTube: Kubernetes SIG Docs monthly APAC meeting for 20220125
Description
For more info see https://git.k8s.io/community/sig-docs
A
So
this
meeting,
like
every
other
meeting
in
the
kubernetes
community,
is
governed
by
the
kubernetes
code
of
conduct,
which
essentially
boils
down
to
please
be
nice
to
one
another,
and
this
is
basically
going
to
be
an
every
month
occurrence
in
on
Zoom,
because
APAC
friendly
meetings
are
typically
held
only
once
in
a
month,
and
we
want
four
people
from
the
APAC
time
zones
to
be
able
to
get
together
and
have
discussions
regarding.
You
know,
sick
dog
stuff.
A
So
that
being
said,
let
me
just
share
my
screen
and
yeah,
just
a
second
all
right,
so,
hopefully
everyone's
able
to
see
my
screen
and
for
per
the
link
that
I
have
pasted
on
chat.
If
everyone
can,
you
know,
enter
in
their
names.
That
would
be
great.
But
if
anyone
I
see
that
you
know
all
of
you
all
are
pretty
new
here.
So
if
anyone
wants
to
go
ahead
and
give
an
introduction
of
themselves,
that
would
be
a
good
start
and
from
there
maybe
we
can
take
things
forward.
B
Yeah
sure
I
can
go
ahead,
so
hey
everyone,
my
name
is
Kunal
Verma
I
am
currently
a
sophomore
pursuing
my
bachelor's
in
IIT
from
India
I've
been
contributing
to
the
kubernetes
community.
Since
the
past
few
months,
like
I've,
been
involved
in
the
Hindi
dogs
localization
and
also
in
the
sick,
contrabass
I've
been
involved
in
the
meta
contributors
blog
series
for
the
APAC
region
as
well.
B
C
So
thank
you,
Divya
for
that
and
for
the
past
few
and
for
the
past
few
months,
I've
I'm
trying
to
contribute
here
and
there
in
the
sick
in
the
sick
dogs
and
I,
also
made
one
contribution
in
the
Hindi
localization.
So
I'm
actually
very
happy
to
meet
you
all
and
look
forward
to
meeting
you
sometime
in
person
and
this
Association
through
meetings.
So
thank
you.
A
D
A
I'm
sure
I'm
starting
a
contribution
Journey
pretty
soon,
because
there
are
a
lot
of
issues
to
work
on
in
not
only
in
the
kubernetes
documentation
space
but
otherwise
as
well.
So
don't
worry,
you
won't
be
a
fly
on
the
wall
for
a
lot
of
time.
Don't
worry
about
that
so
yeah!
So,
just
just
before
we
go
ahead
and
you
know
discuss
anything,
that's
there
on
the
agenda.
A
This
is
a
quick
reminder
that
this
week's
PRM
Wrangler
is
still,
as
you
already
all
know,
him
probably
and
next
week's
PR
Wrangler
is
Jim.
Who
is
the
co-chair
for
documentation?
You
also
probably
know
him
so
basically,
PR
Wrangler
is
but
folks
who
are
responsible
for
reviewing
and
approving
your
PRS
for
that
particular
week.
A
And
what
technically
tends
to
happen
is
that
there
are
a
couple
of
Shadows
or
not.
There
are
there's
one
Shadow
or
who
typically
tends
to
work
alongside
the
pr
Wrangler
and
has
been
since
the
past
couple
of
months,
so
that
a
lot
more
people
can
actually
come
in,
and
you
know
help
with
this
PR
angling
process.
So
reviewing
is
open
to
everyone,
but
the
actual
LG
tming
and
approving
the
pr
is
not
open
to
all
the
pr.
A
Wranglers
are
the
ones
who
will
be
able
to
approve
for
lgtme
or
PRS.
So
hopefully
that
was
clear,
but
if
there
are
any
PRS
that
you
all
have
open
in
the
English
localization,
which
is
not
a
localization
per
se,
but
in
the
English
language
Tim
is
the
person
you
will
be
required
to
reach
out
to
for
any
approvals
or
reviews
on
your
PR
for
this
particular
week.
A
A
You
know,
updates
in
the
space
But
as
and
when
people
you
know
check
in
into
this
docs
and
later
on.
During
their
day,
they
will
be
updating
this
section.
So
as
of
now,
we
don't
have
any
updates
for
the
1.24
release
side
in
the
docs
in
the
coms
aspects,
and
there
are
no
issues
in
PR's
right
now
that
require
attention.
Please
let
me
know
if
there
are
by
entering
your
or
you
all
can
voice
out
right
now.
A
A
Okay,
so
moving
on
this
is
General
discussion
items
so
I'm
sure
for
those
who've
been
around
for
quite
some
time.
You
are
aware
that
there
has
been
an
official
Google
group,
sick
dogs,
leadership,
announcement
that
has
gone
out
a
couple
of
weeks
back,
Jim
posted
it
and
the
link
to
that
particular
announcement
is
given
here.
A
So
this
details,
a
lot
of
changes
in
the
current
leadership
for
sick
rocks,
Ray,
ABI
Natalie,
you
know
Irish
and
a
lot
of
folks
are
joining
us
in
various
capacities.
They
are
detailed
here,
so
I'm
not
going
to
discuss
every
person's
deep.
You
know
official
title
but
check
that
out
and
they
will
be,
you
know,
sharing
or
co-chairing
the
documentation.
Efforts
for
kubernetes,
starting
I
believe
February.
A
Their
PRS
are
yet
to
be
open
for
official
access
related
stuff,
but
the
documentation
leadership
is
changing
and
Jim
who
was
the
and
who
is
the
co-chair,
will
be
stepping
down
starting
the
first
quarter
after
an
official
Handover
of
responsibilities.
So
thank
you,
Jim
and
if
there
are
any
questions
y'all
can.
Let
me
know
about
this
announcement.
It's
there
on
Google
Groups,
as
well
as
on
the
slack
channel,
so
you
can
go
ahead
and
check
that
out
yeah.
A
Okay,
so
another
thing
that
I
wanted
to
bring
up
for
discussion
is
the
docusam
deprecation
bit.
As
you
all
all
know,
it's
a
pretty
big
thing
in
the
kubernetes
community
and
in
the
container,
slash
container
orchestration
community
that
you
know
the
optician
is
being
this
deprecated
and
actually
removed
in
1.24.
So
there's
a
lot
of
efforts
that
are
being
pursued
by
cncf
and
kubernetes
communities
to
ensure
that
this
transition
is
as
smooth
as
possible.
A
A
Just
a
second,
let
me
stop
sharing
and
start
sharing
once
again,
so
there's
this
project
over
here
for
the
question,
and
there
are
some
backlogs
backlog
PRS
that
have
not
been
assigned
if
there.
If
this
is
something
that
you
feel
is
an
issue
that
you
all
can
triage
and
help
with.
Please
feel
free
to
assign
yourself
that
particular
PR
and
work
on
it.
A
Documentation,
so
you
can
check
that
board
out
and
if
there
is
something
that
Peaks
your
interest,
please
go
ahead
and
assign
yourself
and
you,
if
it's
slightly
Advanced,
but
there
are
people
who
are
there
to
help
you
out.
So
don't
worry,
but
yeah.
The
good
first
issues
are
typically
lower
hanging,
fruit
and
easier
to
fulfill.
So
if
you
haven't
worked
on
documentation-
or
you
know,
aren't
exactly
familiar
with
Docker
and
kubernetes,
and
gender
good
first
issues
would
be
the
ones
you'd
pick
up
as
opposed
to
ones
that
are
not
labeled.
A
B
A
Topushim
is
basically
just
okay:
how
to
explain
it
so
Docker
as
a
container
runtime
is
not
going
to
be
used
within
kubernetes
any
longer
starting
1.24
like
the
shin
support.
Shim
is
basically
a
connecting
bridge.
This
is
the
most
easiest
way
I
can
put
it,
but
that
connecting
bridge
that
enables
kubernetes
to
use
Docker
as
a
container
runtime
is
going
to
be
removed
from
kubernetes
support,
starting
1.24
and
the
the
basic
thing
is
that
doc
or
you
cannot
use
Docker
along
with.
A
You
cannot
use
Docker
as
a
container
runtime
starting
1.24
version
of
kubernetes.
It's
deprecated
since
quite
some
time,
meaning
there
is
support,
but
it's
not
completely
removed
as
of
yet.
But
if
you
are
going
to
use
is
1.24
version
when
it
gets
released,
you
will
not
be
able
to
use
Docker
along
with
as
a
container
runtime,
and
that
is
the
basic
thing.
Did
you
understand,
or
was
it
clear
enough?
Yes,.
E
Hi
I'm
pranshu,
so
the
PRS
that
you
just
showed
right
now
so
yeah.
Are
they
like
steel
or
I,
mean
I,
don't
understand
what
we
have
to
do
them
after
we
assign
ourselves
to
those
PR
like
those
PRS
are
not
opened
by
us,
so
the
person
who
is
working
on
them
will
be
making
the
changes
to
what
will
be
our
role
in
those
PRS.
A
Right,
so
that's
a
good
question
so
that
particular
board
that
I
showed
you.
It
is
for
the
dockershim
deprecation
project.
So
it's
our
project
generally,
but
the
removal
of
the
question
that
is
going
to
go
in
in
one
door
to
four
release
now.
The
thing
here
is
when
you
assign
yourself
that
particular
issue
from
the
board
like,
for
example,
let
me
just
open.
Oh.
A
D
A
A
E
A
No,
no,
so
even
no
so
this
is
these
are
issues
that
are
there
now.
If
you
are
looking
at
in
general
issues
on
the
kubernetes
website,
there
are
several
issues
on
the
kubernetes
website
as
well,
and
these
these
issues,
if
you
go
and
check
there
are
you
know,
different
things
that
are
required
as
part
of
each
issue.
So
there's
there's
a
bug
or
there's
a
small
Amendment
and
spelling
or
grammar
that
is
required,
so
you
just
have
to
click.
The
issue
speak
with.
A
A
A
A
A
A
The
seven
pin
messages
so
yeah.
This
is
not
just
a
second
yes
item
yeah,
so
six
in
the
six
pin
ones
there
are.
There
are
several
messages
that
have
been
mentioned
as
to
what
you
all
can
do
so
there's
the
sick
dogs
official
calendar
and
you
can
also
start
with
reviewing
PRS,
but
you
have
to
go
through
the
reviewing
and
approving
guide
before
you
go
ahead
and
see
the
style
guide
as
well,
because
there
are
certain
things
that
we
have
to
adhere
to,
while
even
you
know
actually
reviewing.
A
Then
there
are,
you
know,
there's
a
contribution
guide
wherein
you
can.
Actually,
you
know
check
how
to
contribute
and
what
are
the
various
things
that
aren't
contributing
and
there
are
prioritized
issues
as
well.
So
a
list
of
resources
has
been
given
in
the
pinned
messages
for
the
sick
dogs,
Channel
and
as
I
mentioned.
Sorry,
as
I
mentioned
in
the
you
know
the
question,
but
as
well,
that
is
sort
of
priority
based
issue
right
now.
A
A
A
D
D
A
Yeah,
so
the
thing
is
again:
it's
it's
something
that
I
learned
personally
should
not.
It
does
not
necessarily
need
to
work
for
everyone.
No,
but
what
I
started
off
doing
is
AI
also
started
reading
the
documentation
along
with
contributing.
So
if
there
are,
if
there
is
so,
for
example,
if
there
is
something
like
this,
that
I
don't
understand,
I
make
it
a
point
to
Google
as
well
on
the
site
to
understand
what
happens,
and
you
know
what
exactly
is
the
change
being
requested?
A
A
If
you
want
to
start
learning
things
alongside
this,
it
would
be
best
that
you,
actually
even
you
know,
go
through
that
just
by
dims
and
also
you
know,
start
doing
a
bit
of
r
d
on
Google
as
well.
That's
how
I
learn
it
does
not
need
to
work
the
same
way
for
everyone,
but
this
is
this
is
what
I
can
suggest
now
as
for
what
needs
to
make
what
needs
to
be
changed?
What
needs
to
be
you
know
amended.
A
Everything
in
a
good
first
issue
is
documented,
so
that
a
beginner
can
actually
just
look
at
the
issue
and
directly
make
those
changes.
The
reason
why
they
are
put
out
is
because
there
are
small
issues
that
require
that
have
like
a
big
impact
on
the
documentation,
but
it's
it's
not
possible
for
everyone
in
the
sick
talks.
Maintainers-
and
you
know
you
know
all
of
all-
of
the
people
to
work
on
the
good
first
issues
be
warned
for
new
contributors
to
come
in
and
help
and
learn
as
well.
A
A
Okay,
so
if
nobody
has
any
further
questions,
I
think
we
can
call
it
a
wrap
for
today,
any
anything
that
you
all
might
have
you
all
can
post
on
sick
talks
or
slack,
and
you
know
if
there
are
questions
around
any
you
know
PRS
or
any
issues
you
all
can
directly
post
it
on
sick
dog
slack.
One
of
us
will
definitely
respond.
Bases
are
availability
and
yeah.