►
From YouTube: Intro + Deep Dive: Kubernetes (Docs) SIG - Zach Corleissen, Linux Foundation & Rael Garcia, CAPSiDE
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Intro + Deep Dive: Kubernetes (Docs) SIG - Zach Corleissen, Linux Foundation & Rael Garcia, CAPSiDE
This session covers Kubernetes (K8s) documentation. We'll do an overview of the docs--how they're organized, and how they're maintained--then contribute to the docs ourselves. During the introduction, we'll look at the docs repository (kubernetes/website) and how we organize content. We'll also look at the website stack: how we preview and publish docs to kubernetes.io. We'll talk about the docs workflow: how SIG Docs does the work to review and publish docs. During the deep dive, we'll explore the docs contributor guide and do some hands-on contribution. Remember that contributing to docs is a pathway to Kubernetes membership!
https://sched.co/MPlA
A
A
Doc's
is
the
largest
kubernetes,
sig
I
say
this
with
some
pride
and
perhaps
with
some
skepticism
from
your
part.
How
could
documentation
be
the
largest
sig?
The
answer
is
that
everyone
is
a
part
of
it,
but
we'll
also
come
back
to
that
in
a
moment
and
we'll
say
more
about
the
size
of
documentation.
But
for
now
we'll
talk
a
little
bit
about
why
Doc's
matter
and
Doc's
matter,
because
Doc's
drive
adoption
without
good
documentation
without
any
documentation.
A
A
Adoption
matters
because
in
open
source,
adoption
changes
the
balance
of
power
in
a
community,
the
more
people
who
adopt
and
begin
using
kubernetes,
because
it
is
an
open
source.
Software
project
means
that
all
of
a
sudden,
instead
of
just
being
a
user
of
kubernetes,
you
are
a
developer
of
kubernetes
as
well.
You
are
a
part
of
the
community,
and
that
means
that
all
of
a
sudden,
you
are
not
just
a
passive
consumer,
you
are
someone
who
changes
the
shape
of
kubernetes
the
features
that
are
included.
A
Doc's
also
signal
and
drive
inclusion
when
we
come
into
an
open
source
project.
One
of
the
first
things
that
we
need
to
know
is
what
kind
of
a
community
is
this
like?
Is
this
a
community
where
I
can
be
a
safe
person,
and
the
code
of
conduct
helps
to
drive
that?
But
if
the
code
of
conduct
is
not
in
alignment
with
the
documentation,
if
what
we
say
we
do
versus
how
we
actually
do
it.
If
these
things
don't
match,
then
there's
not
a.
A
There
is
a
feeling
of
danger:
there's
no
perception
of
safety,
so
Doc's
Drive
inclusion,
safety
and
inclusion
and
inclusive
communities
create
and
contribute
to
inclusive
Doc's.
When
we
as
contributors
feel
safe
in
a
community,
we
create
documentation
that
reflects
our
values
that
reflects
who
we
are.
A
So
fun
fact
about
kubernetes
documentation.
Right
now
we
have
nine
different
localizations.
We
have
English
nine
other
languages
and
two
more
languages
currently
in
development,
and
this
is
pretty
awesome.
We
spent
the
last
year
paying
down
technical
debt
and
making
it
possible
to
host
kubernetes
documentation
in
a
multitude
of
localizations
and.
A
So,
to
give
you
a
sense
of
the
impact
of
sig
Docs,
our
website
kubernetes
io
in
April,
we
averaged
1.2
million
pageviews
per
week,
that's
kind
of
big
every
time,
I
think
about
it.
My
impostor
syndrome
has
a
giant
flare
up,
but
it's
pretty
amazing
to
realize
that
the
impact
of
sig
Docs
individually
impacts
1.2
million
pageviews
per
week,
so
the
work
that
we
do
in
documentation
matters
a
great
deal,
Doc's
matter.
A
So
but
I'll
we'll
cover
a
little
more
of
our
about
our
tooling
and
our
how
our
website
is
built
in
the
deep
dive,
but
I
just
want
to
mention
briefly
that
our
our
workflow
at
our
tool
chain
for
the
website
is
pretty
straightforward.
We
build
the
website
using
that
lafay
from
a
github
repository
and
contributors
to
the
website
to
documentation
work
in
the
repository.
The
same
way
that
feature
developers
work
in
other
repositories.
A
In
kubernetes
we
have
more
or
less
an
identical
workflow,
so
we
are
very
much
a
part
of
the
kubernetes
community
and
contributing
in
any
kubernetes
project
makes
it
possible
for
you
to
contribute
to
documentation
just
as
easily
we
use
prowl.
There
is
nothing
unique.
We
don't
use
a
different
set
of
bots,
so
the
same
prowl
commands
that
you
use
in
other
kubernetes,
sick
repos
are
the
same
ones
that
we
use
in
website.
A
So
one
of
the
things
that
we
do
in
cig
Docs
is
that
we
support
the
kubernetes
quarterly
release
cycle.
As
everyone
knows,
kubernetes
releases
on
a
quarterly
basis
and
sig
Docs
drives
and
coordinates
all
of
the
documentation.
Every
user
facing
feature
change
a
future
edition
that
is
required
to
have
a
documentation
update
and
if
you
are
a
feature
developer,
actually
just
a
really
quick
show
of
hands
who
here
has
developed
a
feature
for
kubernetes?
It's
worked
on
a
feature
who
here
is
interested
in.
A
So
I
mentioned
earlier
that
Docs
is
the
largest
kubernetes
sig,
and
that
is
because
everyone
is
a
member.
If
you
use
the
website,
you
are
participating
in
sig
Docs.
If
you
find
something
on
the
website,
that
is
not
accurate
and
you
say:
hey!
That's
wrong.
I
got
a
complain
about
that.
I've
got
an
opening
issue.
You
remember
sig
Docs.
If
you
develop
a
feature
that
has
a
user
facing
impact,
you
remember
sig
Docs,
if
you
open,
if
the
pull
request
to
fix
a
typo
or
a
broken
link,
you're
a
member
of
sigdoc
s--.
A
So
we
are
the
largest
sig
because
we
are
the
world.
We
are
everyone.
We
are
everywhere.
We
see
everything
just
kidding.
We
only
see
most
things,
but
in
this
case,
while
we're
the
largest
cig
size,
is
misleading.
Right
now
we
out
of
Olives
cig
docks.
We
have
two
full-time
and
one
part-time
technical
writer
dedicated
to
documentation
quality.
So
while
we
have
a
lot
of
people
involved
in
documentation,
our
ability
to
meaningfully
improve
and
do
things
like
make
better
information
architecture
make
sure
that
our
site
UX
is
good
or
conforming
to
accessibility
standards.
A
The
golden
ratio
for
technical
writers
to
developers
usually
one
to
seven
to
one
to
twelve,
depending
on
how
much
user
fate
user
facing
feature
development
is
happening
if
you're
doing
a
lot
of
user
facing
development,
probably
closer
to
one
to
seven
one
technical
writer
for
every
seven
developers,
if
it's
mostly
back-end
stuff
I,
have
probably
closer
to
one
to
twelve
right
now
in
kubernetes,
the
ratio
of
technical
writers
to
feature
developers
is
closer
to
one
to
150.
So
that
makes
it
a
little
difficult
to
do.
A
So
individual
contributors
make
existing
content
better
and
individual
contributors
do
this
by
things.
Like
writing
new
content.
If
you're
a
future
developer,
you
can
help
localize.
If
you
speak
another
language
other
than
English,
and
you
want
to
make
documentation
available
in
your
language,
you
can
help
localize
if
you're
a
CN,
CF
partner,
a
company
that
is
a
member
of
the
CN
CF.
You
can
also
contribute
by
hiring
more
technical
writers.
A
It's
a
theme
that
I
will
repeat,
as
often
as
I
can
get
people
to
listen
to
me,
a
higher
more
technical
writers.
Please,
and
even
if
you
don't
hire
more
writers,
provide
support
for
developers
who
do
documentation
if
you
have
developers
who
are
working
in
an
open-source
project,
but
you
don't
allot
time
for
them.
That's
kind
of
that's
a
that's
exploitative!
A
Our
contributors
are
amazing
in
cig,
Doc's
I
have
the
privilege
of
being
someone
who
helps
open
the
world
to
kubernetes
and
making
it
as
easy
as
possible
for
as
many
people
as
possible
to
learn
kubernetes
to
begin
contributing
themselves
and
to
grow,
and
that
is
a
powerful,
powerful
thing
and
it
wouldn't
happen
without
individual
contributors
who
helped
make
everything
go,
who
helped
make
the
website
work,
who
contribute
to
back-end
development
who
contribute
to
content.
So
thank
you
and
now
I'm
gonna
hand
it
over
to
Ryo
who
will
do
our
deep
dive?
Okay,
thank
you.
B
So
I
journeyed
the
kubernetes
project
in
the
last
investments,
as
a
member
before
banette
become
a
manga
I
was
only
reviewing
helping
checking
how
the
accomodation
war
go
into
all
the
documentation
to
see
how
it's
managed.
But
how
is
the
concepts
splitted
at
was
different
subject
and
after
being,
that
was
the
best
way
to
get
into
the
kubernetes
community
was
going
through
documentation
and
afterwards
using
a
managed
solution
or
or
your
custom
solution
or
reading.
On-Premises
documentation
is
the
core
thing
to
allow
everyone
in
this
room.
B
Everyone
this
that
use
governmentís
to
really
take
advantage
of
all
that
kubernetes
provides.
So
how
we
working
in
six
dogs
is
through
a
stool
set
to
deploy
web
pages
as
code
and
also
to
allow
the
same
flows
that
we
use
to
call
contributions
in
documentation.
So
every
contributors
has
the
same
framework
to
make
pull
request
and
be
part
of
contributing
to
the
code.
So
how
many
people
in
this
room
knows
here?
B
Oh
okay
and
how
many
people
knows
that
what
is
a
static
frame,
work
for
webs
like
Jekyll
or
or
similar,
so
you
go
and
the
other
frame
was
allow
having
plain
text.
Content
written
in
markdown
be
rendered
plus
building
artifacts.
So
you
have
your
code
and
you
go
through
a
pipeline
that
builds
an
artifact
with
the
content,
the
style,
the
images
bugs
everything
into
a
regular
web
page
that
can
run
in
Apache
in
jinks
or
any
other
web
server,
and
this
page
will
be
a
static,
not
dynamic.
B
Everything
is
plain
text
and
where
is
the
best
place
to
store
plain
text
that
word
likes
code?
That's
github!
All
the
projects
right
now
in
cornetist
runs
in
github.
We
have
more
than
one
hundred
ninety-two
projects
currently
and
fifty
one
thousand
contributors
across
all
of
them.
For
example,
the
website
has
40
hundred
forty
three
issues
open.
B
B
That's
just
allow
us
to
work
on
project
milestones.
For
example.
Currently
we
only
manage
the
kubernetes
totai
website.
That
is
the
mind,
but
kubernetes
has
a
lot
of
projects,
for
example,
could
cut
all
of
severe
of
control,
as
you
wish
mini
cube
kind
customize,
this
a
lot
of
tooling
around
kubernetes,
so.
B
B
Last
thing,
github
is
where
we
store
the
code.
Google
is
the
framework
that
we
used
to
build
as
an
artifact.
The
page
but
native
lie
is
the
content
delivery
network
that
distributes
and
builds
the
web
page.
Every
time
you
make
a
pull
request,
continue
generation
by
block
will
be
triggered
and
an
artifact
with
your
version
of
the
website.
So
the
upstream
more
you
close,
your
changes
will
be
deployed
in
an
ephemeral
environment,
so
you
can
check
before
public
put
pub
like
pull
icing
the
size.
The
decide
online.
B
If
the
changes
that
we
are
ok
are
good,
doesn't
break
the
changes
and
also
for
the
very
words
and
approval
that
we
wrote
to
you.
Pull
requests
can
check
how
it
will
look
on
the
on
the
print
on
the
main
page.
After
this
project
was
completed,
you
will
merge
the
content
into
master
and
another
pipeline
will
do
the
same
thing:
build
an
artifact
and
update
the
main
site
for
kubernetes.
B
It
usually
takes
less
than
5
minutes
to
get
your
content
after
amell's
and
that's
another
thing
that
is
important
when
you
have
this
kind
of
size
of
committee
building
automation
around
all
your
parents
trying
to
remove
the
human
factors
as
much
as
possible,
because
it's
hard
to
manage
it's
hard
to
put
government
in
this
case
of
validation.
So
everything
has
to
be
done
by
a
robot.
In
this
case,
we
have
kubernetes
bot
in
gift-wrap
that
is
running
on
prowl
prowl.
B
That
is
our
continued
innovation
in
Jane
that
we
build
the
kubernetes
for
from
from
the
6a
testing
team
from
this
one.
Anyone
knew
what
was
net
applied
before
first
time
native
fly,
it's
free
for
open-source
projects.
So
if
you
want
to
have
your
website
public
is
you
can
use
the
same
thing?
It's
it's
a
great
tool
and
it's
helping
a
lot
to
kubernetes
because
it
handles
1.2
million
page
fish
per
week.
So
it's
ready
to
grow
to
scale.
B
So
now
you
have
the
toolset,
you
know.
What
do
you
need
to
use
to
be
part
and
build
the
kubernetes
project,
how
you
can
start
contributing
to
cover
natives?
Anyone
wants
to
buy
what
is
the
first
thing
that
you
should
do
if
you
want
to
jump
over
to
the
six
dog
group,
yet
that's
correct
documentation.
If
you
want
to
be
part
of
documentation,
you
need
to
know
the
documentation.
So
the
first
thing
you
need
to
know
is:
go
through
the
website
view
all
the
pages.
B
You
will
reach
one
two
point
million
pageviews
per
week,
so
your
content
can
be
there.
You
only
need
to
know
where
to
put
it.
If
that
looks
right,
you
have
to
since
the
first
reading
the
contributors
guy
from
from
the
SiC
contribute
experience.
Then
you
will
know
how
to
get
in
the
community.
They
could
have
come
to
that.
We
have
and
all
the
steps
that
you
need
to
get
things
started
once
you
need
a
committee.
The
next
thing
is
reading
our
contributor
garland.
B
You
will
see
how
we
manage
all
the
deployments
and
the
style
guides
that
we
use
to
to
keep
everything
written
in
the
same
way
and
also
old
meetings.
How
we
manage
changes
and
all
the
pipeline
so
I'm
just
know
how
to
achieve
it
and
how
to
be
part
of
dogs.
If
you
are
still
interested
that
all
this
information
next
thing
is
go
interest
like
I,
probably
kubernetes
has
the
most
the
biggest
channel
in
there
slack.
You
have
kubernetes
users
with
more
than
I
think
we
are
almost
70,000
uses.
B
70,000
users
in
a
slight
channel
can
be
overwhelming,
but
everyone
in
the
chalice
is
willing
to
help,
so
don't
be
afraid
of
joining
getting
to
know.
People,
if
you
are
interested
in
a
particular
subject,
go
to
the
SiC
channel,
see
Chris
talking
get
to
know
the
chairs,
the
people
that
is
more
active
this
week,
because
it
is
a
huge
project.
You
can't
have
weeks
with
a
lot
of
interaction
and
take
a
holidays
next
week,
so
get
to
know
people
and
ask
be
part
of
the
all
the
conversations
reached
by
the
direct
message.
B
Some
forgive
you
need.
Some
assistance,
don't
hesitate,
it
was
for
help
because
everyone
in
this
community
is
willing
to
help
who
from
this
room,
are
you
always
like?
Is
there
anyone
that
is
not
coronated
a
slug?
Raise
your
hand?
If
you
are
not
in
a
slack,
then
we
will
go
there
and
we
will
add
you
to
a
slack.
B
It's
important.
You
can
look
around.
You
don't
need
to
be
part
of
the
discussion.
Just
get
the
chat,
you
will
learn
a
lot
I'm
in
users
in
English
and
I've.
Seen
Spanish
and
I
am
the
sick
of
Amazon
Web
Services.
Everything
of
Asia
amazing
work
loud,
not
as
a
contributor
battle
as
a
learner,
but
I
love
problems
that
people
have
that
throws
should
there
and
all
the
knowledge
can
be
useful
for
you
for
your
daily
kubernetes
Tings
or
at
support,
adding
documentation,
improving
documentation.
B
B
B
Like
hands-on
from
hangout
zoo
meetings,
just
to
help
setting
things
apps
you
to
have
like
working
with
our
ways
of
troubleshooting
a
conflict,
so
if
you
have
a
brain,
we
did
the
same.
As
for
help,
look
in
the
sick,
Channel
look
in
the
stickety-boo
experience.
We
have
a
lot
of
documentation
of
if
this.
If
the
recognition
doesn't
work,
we
can
improve
it
and
in
the
meantime
we
can
help
you.
Can
we
do
meetings
on
daily
basis?
B
So
it's
not
a
problem
to
run
a
ten
minute
chat
over
the
Skype
first
thing,
then
you
need,
or
you
like,
lose
the
fear
of
get
for
the
ripple.
You
have
this
big
button
there
that
allows
you
to
have
a
copy
in
your
name.
Space
in
your
economy
says
because
master
is
restricted
to
owners.
Only
owners
and
the
bot
can
write
in
to
master.
Everyone
else
need
to
go
to
his
fork
and
then
make
seconds
when
you
have
a
1000
well,
most
mostly
2000
users.
B
B
Everyone
perfect
this.
This
is
the
discover
it.
Don't
you
have
your
wrapper.
You
have
to
do
let
the
report
to
work
on
him
is
not
really
required.
You
can,
with
the
last
version
of
you
cup,
you
can
edit
things
in
the
process,
so
you
can
edit
the
file
with
the
with
the
web,
busy
editor
makeup,
wrench
their
makeup
on
request
and
do
all
the
flow
without
leaving
the
browser.
In
case
you
are
working
on
a
table
or
your
talent
or
you
need
to
look
just
to
add
a
quick
fix.
Go
to
a
page.
B
Add
the
quick
fix
on
the
website,
make
the
progress
and
more.
But
if
you
want
to
make
a
bigger
contribution
or
you
need
to
change
the
page
or
error,
you
want
or
request
some
interaction
or
just
you
are
more
comfortable
with
working
with
you.
The
return
there
are,
for
example,
for
Vista
Visual
Studio
code,
a
we
have
a
lot
of
plugins.
That
has
a
spell
checkers
translation
on
the
same
editor,
so
you
can
select
a
phrase
translate
to
your
language
and
then
like
try
to
work
if
the
phrase
doesn't
make
sense.
B
You
have
the
ripple.
You
have
everything
locally.
The
good
thing
that
having
all
the
content
in
mark
them
is
that
you
can
read
offline.
The
content
you
can
get.
The
page
is
a
readable
page.
If
you
are
some
disability
and
unique
some
tool
like
expect
a
text-to-speech
or
some
helper,
it's
plain
text.
You
can
put
the
text
in
your
tool
and
be
able
to
read
the
language
everything
all
the
image
has
has
captions
so
can
provide
some
contents.
B
If
you
can
see
the
image,
but
there
is
also
a
way
to
have
locally
offline,
all
the
content
and
the
content
can
be
built
locally.
You
don't
need
you
don't
need
the
notify.
You
will
show
a
bit
more
on
that
afterwards,
so
you
have
the
website
locally.
You
know
what
to
change.
The
next
thing
is
creating
a
brand.
B
This
is
important.
Kubernetes
with
to
twelve
thousand
comet
is
a
quite
a
set
project.
You
can
find
I
think
25
melt
away.
Probably
so
your
master
keep
sedated
like
a
lot.
The
safest
way
to
work
with
any
public
repo
in
a
pair
of
animal
social
project
is
to
have
your
own
branch
work
on
your
branch
and
make
your
history
in
that
branch.
If
there
is
a
conflict,
is
easier.
B
If
you
are
working
on
on
a
brand
that
you
are
working
master
and
a
lot
of
the
initial
problems
that
the
false
have
when
I
start
include
when
they
start
contributing,
is
they
work
on
on
brand
and
they
get
so.
You
know
when
two
thousand
people
is
working
in
the
same
branch
that
can
lead
some
some
problems.
B
That's
you
mean
check
out
the
new
branch,
make
the
comments
work
on
the
content
that
you
want.
It
is
not
a
bad
practice.
Have
several
problem
commit
during
the
the
work
in
progress,
because
it's
easier
to
you
to
see
all
the
things
that
we
are
doing
and
keep
track
of
all
the
changes,
but
after
the
review
process
is
recommended
to
squash
all
the
commits
in
in
a
single
one
and
live
all
the
common
message
in
a
lease,
because
again
is
that
12,000
commit
project?
B
So
if
we
can
save
sub
comet,
it
will
be
worth
it
in
the
long
time.
So
you
have
your
repo,
you
have
your
branch,
you
come
with
your
changes.
Everything
looked
what
at
least
individuals
to
your
code
or
the
deduce
how
you
can
check
how
it
looks
locally
without
tree
in
all
the
pipeline.
Google
is
a
tool
that
can
be
run
locally.
It's
a
binary
with
lingo
you
can
dole
out
the
binary.
Is
there
is
a
docker
image
that
you
can
run?
B
If
you
don't,
you
prefer
run
inside
a
container
and
I
would
seen
of
you
go?
Is
that
watches
the
changes?
So
you
can
spawn
our
process.
Have
this
in
background
I
start
working
on
the
code.
Every
time
you
add
a
new
page
or
you
add,
content
Google
will
will
rebuild.
In
the
background
the
page.
That's
really
really
useful
to
see
how
the
changes
will
be,
because
markdown
has
some
format
and
it's
hard
to
see
how
it
looks
without
rendering
the
page.
B
As
you
can
see
here,
we
have
thinking
about
eight
languages,
part
one
is
English
with
1000
pages
and
the
next
one
is
China
and
Korean
with
2200,
and
we
are
the
fourth
one
Spain
when
haven't
eaten
97
pages.
That's
not
bad
at
all,
because
Governors
project
in
Spanish
has
been
dead
for
two
months,
I
think
so
there
is
people
willing
to
help.
There
is
a
lot
of
contributors
that
are
working
the
project.
You
see
that
people
know
that.
B
That
is
like
the
only
true
way
of
learning
something
when
you
are
able
to
explain
to
someone
that
is
not
used
to
the
concept,
and
you
learn
a
lot
here,
because
you
read
its
phrase
like
10
12
times,
and
you
have
to
like
put
yourself
in
the
situation
of
someone
that
doesn't
know
as
much
as
you
and
can
be
hard.
But
then,
when
you
start
like
getting
the
mood,
you
see
things
that
you
thought
you
knew,
but
you
don't
need
as
well,
as
you
think,
makes
you
thought
sorry
and
the
same
for
the
different
projects.
B
We
have
some
foreskin
from
the
French,
the
French
professors
and
the
people
managing
the
phrase
localization
and
the
Spanish
will
have
a
couple
of
faults
that
came
to
the
last
Spanish
event.
I
think
Jose,
Luis
and
David
also
was
part
of
the
Spanish.
So
people
is
here,
people
is
willing
to
and
high
quest
experience.
Can
you
say
how
do
you
feel
when
you
saw
your
content
in
a
1
to
4
million
page?
B
You
can
make
a
footprint
in
the
kubernetes
project,
a
foot
read
that
can
be
so,
but
thousand
of
million
of
people.
Another
important
thing
that
we
found
when
we
started
the
Spanish
localization
project
is
people
jump
it
into
the
slag
channel
for
the
Spanish
user,
been
a
graceful
for
the
content,
saying
that.
B
They
felt
that
they
can
they
wouldn't.
They
were
then
able
to
explain
the
problems
in
English,
because
kubernetes
is
a
complex
project
and
when
you
have
to
troubleshoot
not
being
able
to
do
in
your
own
words,
it's
a
hard
problem,
so
you
can
or
try
getting
into
the
English
Channel
and,
having
probably
a
hard
conversation
trying
to
get
you.
B
Let
the
other
people
know
what
you
are
trying
to
say
or
give
up
and
move
to
another
project
or
move
to
another
tool
or
or
lose
a
lot
of
time,
crocheting
being
to
explain
in
your
own
words,
the
problem
is
key
for
building
a
huge
community
as
kubernetes,
so
your
site
looks
promising.
Your
new
page
is
their
next
step.
B
This
is
how
it
looks
locally
when
we
spin
logo
you
get
less
air
pump
in
that
port
and
you
can
see,
is
the
same
webpage
but
locally
right
also
for
cinder.
If
you
need
to
read
the
documentation
of
line,
you
can
spin
up
the
observable
and
with
the
same
thing
as
it
is
aligned
with
all
the
content
with
other
format,
with
all
the
examples,
so
your
page
looks
promising
and
it's
ready
to
go
to
the
1.2
million
page,
make
a
boat
request.
How
you
can
make
a
porter
case
when
you
push
to
your
brains.
B
Github
will
know
that
upstream
is
the
your
target.
So
we'll
show
you
a
button
this
one
to
start
the
pull
request
process,
the
cool.
The
pull
request
will
try
to
merge
your
changes
into
upstream
and
will
provide
a
process
of
validation
to
go
to
all
the
steps
required
to
add
things.
Public
publish
it
first
thing
they
will
find.
Probably
the
the
Linux
Foundation
contributor
license
agreement.
Kubernetes
is
an
open
source
project,
I
think
released
under
the
Apache
2.0
license,
but
the
foundation
covering
protecting
cover
needs
to
keep
the
project
open-source
and
agnostic
from
a
provider.
B
It's
declared
a
foundation
that
isn't
a
soup
project
of
the
new
foundation,
so
your
code
or
your
contributions
need
to
be
subject
to
those
agreements,
as
a
company
was
an
individual.
So
if
you
are
already
in
the
in
the
new
foundation,
you
will
get
a
green,
green
bar.
Otherwise
we
had
this
error
of
and
if
you
click
in
details,
you
will
see
you
will
get
like
directed
to
this
page
and
you
will
find
like
the
license
that
you
are
going
to
sing
and
all
the
process
required
to
fulfill.
B
There
are
two
types
of
licensing
contributors
as
individual
or
as
a
company.
If
your
company
has,
for
example,
a
team
of
open
source
contributors,
you
need
to
go
to
the
corporate
license
to
cover
anyone
from
your
company
to
push
into
kubernetes.
If
you
are
an
individual
contributor
is
another
document
that
it's
okay,
it's
only
your
contributions
as
company.
Also
individual
will
go
to
the
same
process.
B
You
can.
It
is
a
pretty
straightforward,
but
it's
required
to
keep
kubernetes
open
source.
Otherwise,
if
you
don't
sing
this
make
a
contribution,
you
can
break
the
agreement
of
the
new
foundation
so
to
resisted.
You
are
member
of
the
confrontation
and
you
sing
that
the
the
contributor
listens
agreement
next
thing:
Netta
flag
will
kick
him
and
the
project
site
in
this
criminal
empire
dome,
as
you
can
see,
is
the
pro
preview
and
the
port
request
number
and
every
time
that
you
make
and
you
commit
this
site
will
be
revealed.
B
So
you
can
check
how
it
looks
in
the
in
the
real
page
before
managing
this
will
allow
data
be
was
to
kick
in
and
their
progress
to
kick
in
and
check.
If
everything
looks
promising,
the
review
process
is
managed
by
the
bottom
corner.
This
bot
will
choose
between
the
pool
of
reviewers.
Two
members
will
assign
this
this
job,
because
contributing
requires
some
commitment,
but
it's
to
be
expected,
you
need
to
be
per,
be
constant,
be
be
there.
So,
if
you
already
were
you
need
to
go
through
this
process,
as
always
is
a
best
effort.
B
If
you
can,
you
can
settle
a
select
another.
We
were
talk
with
the
sake
and
there
is
a
problem,
but
try
to
get
your
your
part
done
is
the
very
worst
process
can
be
sometimes
can
be
long
if
you
just
if
it's
your
first
contribution,
you
need
like
to
get
used
to
how
the
style
of
documentation
works,
the
agreements
and
the
glossary
we
follow
and
so
don't
feel
like.
You
are
not
good
enough.
B
B
Yeah,
okay,
if
another
good
thing
of
very
good
processes
that
you'll
learn
a
lot
as
I
said
before.
Miss
me.
Something
is
obvious
to
you,
but
it's
not
that
obvious
for
anyone.
So
having
more
people
involved.
Three,
the
viewers
to
the
process
will
allow
you
to
improve
your
understanding
of
the
particulars
concept.
Even
you
can
be
wrong
and
put
a
thing
that
is
not
true
and
giving
the
this
discussion
between
members
can
help
you
a
lot
on
improving
your
knowledge
of
this
particular
subject.
B
If
everything
looks
good,
you
will
get
this
level
from
from
the
reviewers.
This
means
looks
LASIK
to
me,
meaning
that
the
reviewer
go
to
all
the
process
and
confirms
that
the
document
is
correct.
Fulfills,
the
style
guide
of
the
six
dogs
is
well
written
is
can
be,
is
easy
to
read
and
fit
into
the
webpage.
B
B
B
Have
some
numbers
here
in
my
notes:
Chinese
the
first
one,
one
thousand
more
than
one
thousand
million
speakers.
Twenty
percent
of
the
population
speaks
English,
Chinese,
20
percent.
That's
a
lot
and
it's
not
the
main
language
of
the
are
you
see
before.
It
only
covers
200
pages
from
1000.
That's
a
problem,
and
we
need
to
solve
this
problem.
The
next
one
is
a
Spanish
with
force,
yeah,
460
minutes
speakers,
six
percent
of
the
population
and
knowing
English
is
not
binary.
B
B
I've
been
training
this
world
a
lot
that
means
making
the
site
or
the
tool
or
the
application
compatible
with
multi-language,
because
it's
not
built
in
I
was
talking
yesterday
with
the
force
from
the
control
line
in
the
face
group,
the
cup
kata
could
control
groups
et
al
and
its
supports
English.
It
supports
localization,
it
coral
has
Korean
implemented.
So
if
you
want
to
join
or
start
working
on
code,
you
can
go
to
the
six
in
the
I
and
s
targeting
cup
cattle
within
in
Spanish
and
again,
a
lot
of
people
use
cook
at
all.
B
B
Localizing
is
not
only
translating
yeah.
You
have
a
lot
of
machine
learning,
algorithms
that
are
able
to
put
things
in
look
in
a
dictionary
hash
map
and
replace
things
and
yeah
I,
look
into
phrases
and
try
to
get
moccasins
and
trying
to
find
false
friends
and
all
that.
But
that's
not
the
point
of
like
rising
the
commendation.
B
B
Words
need
some
thought
this,
and
not
only
like
using
your
language
as
efficient
as
possible
and
using
the
tools
that
your
particular
language
provides
to
to
to
speak,
also
taking
account
culture,
fit
phrases
that
maybe
are
a
problem
in
some
countries
or
that
can
be
misleading
or
are
false.
Friends.
You
have
to
put
a
lot
of
thought
in
India,
translation.
B
B
I've
been
talking
about
why
the
portal
localizing
localization
with
other
people
here
in
this
in
this
conference
and
in
telegram
in
LA
in
our
challenge
for
us
is
easy
as
an
end
users
to
using
this,
because,
but
we
have
like
the
possibility,
dream
or
a
scholarship
to
learn
the
language
and
go
through
and
we
are
confident
with
reading
English,
but
that's
the
case
for
only
10%,
probably
of
the
committee.
The
other
90%
probably
doesn't
speak
Spanglish
or
has
problems
understanding
English.
B
So
we
need
to
think
on
them
and
not
only
on
us,
because
I
know
what
I'm
reading
I
cut
I
could
avoid.
For
me,
if
I
mean
if
I
was
selfish,
I
could
not
do
this
and
keep
living
my
life
and
going
through,
because
I
am
able
to
understand
the
content.
But
we
need
to
think
on
everyone
else,
because
this
is
a
community.
Kubernetes
is
in
this
situation,
thanks
to
the
community
and
that's
the
main
driver
of
kubernetes.
Not
only
that
all
there
is
amazing,
it's
brilliant,
but
the
community
is
what
makes
coordinated.
B
You
can
have
a
good
understanding
of
English
I
just
ignored
your
main
language
documentation,
but
you
can
sue
me
in
the
middle,
so
read
the
English
documentation
and
if
something
doesn't
look
right,
you
can
go
back
and
fail
back
to
your
language
and
improve
your
language
or
improve.
Even
the
English
I
think
that
that
can
confirm
is
after
starting
all
these
localizations.
B
We
improve
it
a
lot
being
this
augmentation,
because
we
have
like
thousands
of
reviewers
from
different
countries
for
the
Qin
TV,
with
different
levels
of
English
understanding
with
different
culture,
and
all
this
feedback
improves
the
original
documentation.
So
it's
not
only
for
the
minor
ease
of
the
the
local
communities
of
the
language
community.
It's
also
good
for
the
upstream
community
and
in
the
last
in
the
last,
in
the
opposite
side
of
the
spectrum.
Have
people
that
doesn't
know
English
and
they
only
can
start
working
on
Cuba
needs
a
sort
of
the
tooling.
B
If
the
tools
is
in
art
in
their
language,
coral,
you
have
this
well
eight
languages,
you
can
see:
German
Spanish,
French,
Hindi,
Hindi,
Indonesian,
Italian,
Japanese
Korean
for
two
years
and
Chinese
and
all
those
languages
happy
birth,
I.
Think
in
the
last
three
four
months,
Portuguese
started
with
Felipe.
That
was
aware
that
Spanish,
a
good
localization
project
was
starting
and
he
jump
in
I
jump
in
thanks
to
Remy
Leon
from
from
the
French
documentation.
That
tell
me
a
lot
to
get
you
started
so
keep
the.
B
If
you
have
a
language
that
is
not
here,
feel
free
to
start
a
new
project
to
get
get
in
touch
with
with
me,
with
zag
of
any
other
fall
from
the
six
dog
and
as
for
help,
you
can
also
check
the
the
initial
put
a
quest
that
we
made
during
during
our
starting
of
the
you
will
see
all
the
documents
that
are
required
for
the
initial.
All
the
conversation
that
we
have
with
currency
go
seek
the
cause
Nev's
about
how
we
did
things.
B
You
can
see
also,
we
have
a
website
a
section
only
for
a
started.
Localization
so
feel
free
to
get
your
language
here
and
be
part
of
the
community
and
build
a
community
around
documentation,
because,
as
I
told
you
before,
the
most
important
thing
when
it
is,
is
the
community
I
I
won't
get
tired
of
the
repeat
this
phrase
as
Zack
about
how
more
technical
reviews
it's
important
and
contributing
to
granny.
This
is
not
only
about
code.
It's
about
banality.
This
is
a
slide
from
Nikita.
B
Do
you
remember
the
amazing
fault
that
word
in
the
keynote
yesterday
talking
about
how
they
started,
but
that
it's?
What
is
kubernetes
I,
currently
serve
thanks
to
be
graceful
with
the
people
that
get
him
to
the
committee.
Provide
feedback
provide
support
fulfill
the
color
codes,
be
helpful.
Make
constructive
criticism
participate
in
this
Christian?
As
I
said,
six
docs
is
the
largest
group
in
kubernetes,
so
jump
into
the
same
meetings.
Jump
with
Lestat
live
like
channels
not
only
live.
B
Your
language
I've
been
working
a
lot
with
the
Hindi
Chalon
thread,
workgroup
that
is,
and
I
have
no
idea
of
Hindi.
But
I
have
a
lot
of
things
to
share
about
localizing,
about
reading
phrases
of
in
English
and
getting
the
core
concepts
of
each
one.
So
don't
be
afraid
of
getting
bullied
in
in
the
other
parts
of
the
sixth.
B
It's
not
only
the
website.
Kubernetes
has
thousands
of
way
to
get
into
the
community.
You
have
the
Disco's
channel.
You
have
this
lack
overflow
tag.
You
have
twitter,
you
have
a
lot
of
ways
to
be
part
of
your
language.
Last
month
we
started
the
virtual
discussions
and
we
added
Spanish.
If
you
have
something
to
share,
go
there
and
start
a
thread,
it's
important
to
build
community
around
language.
So
you
have.
B
You
can
have
regular
discussions
in
Spanish
in
this
like
channel,
not
only
in
the
English
Channel,
as
we
are
seeing
right
now,
use
your
language
in
in
the
slack
channels.
Don't
try
to
enforce
English.
There
are
a
lot
of
people
that
six
percent
of
the
operation
in
Spanish
so
use
your
language
in
the
community,
not
just
English
and
I.
B
You
have
a
sixty
group
of
people
working,
but
if
you
want
to
have
a
good
interaction
with
the
people,
you
need
to
be
close
and
you
need
to
have
few
people,
and
there
are
thousands
of
meetups
around
the
world.
I
was
talking
with
Philippa
from
the
from
the
Portuguese
documentation
he's
living
in
London.
So
it's
hard
for
him
run
this
kind
of
event.
B
Some
contacts
in
the
local
communities
to
allow
you
to
run
these
kind
of
events
from
London
I,
also
working
in
the
contribute,
experience
SiC
that
and
we
are
trying
to
build
a
framework
for
this
kind
of
events,
so
provide
the
flight
deck,
provide
them
like
the
script
to
go
forward.
They
all
the
same
application
that
we
ran
all
the
channels.
Everything
to
share
this
knowledge,
because
you
don't
have
to
keep
your
knowledge
inside
you,
knowledge
is
meant
to
be
shared.
It's
critical.
B
All
them
is
not
good
to
keep
everything
to
you
to
be
the
holding
webber
of
your
company
or
of
your
committee.
The
most
important
thing
that
you
can
do
is
share
with
others.
You
knowledge
and
build
a
community
around
the
knowledge,
because
kubernetes
is
what
it
is.
Thanks
to
thousands
of
people,
it
was
only
made
by
one
two
three
people.
B
You
will
need
right
now,
a
much
smaller
project
focus
on
a
particular
set
of
problem
that
those
initial
contributors
had
so
share
the
knowledge
and
lamp
from
others,
because
not
everything
is
the
way
that
you
think
it
is
and
opening
to
other
folks,
other
communities,
other
cultures
all
genders.
It's
important
to
share
and
like
build
a
common
knowledge.
B
What
kinds
of
demands
we
run
in
in
kubernetes
on
that?
First,
one
is
contributor
hackathon
who
went
to
the
contributors
hackathon
from
this
room,
one
two,
three
four!
So
it's
working
it's
getting!
People
involved,
we
run
I,
think
about
22
pull
requests
in
the
same
evening.
In
the
same
evening,
it's
important
yeah,
it's
a
lot
of
requests,
but
the
police
people
are.
A
B
Inside
the
community
they
already
make
his
pull
request.
They
know
how
it
works.
Some
of
the
public
works
are
ready
in
interaction
deployed
and
accessible
to
everyone
and,
after
the
event,
I've
been
seen.
I
seen
a
lot
of
new
product
waste
from
the
sames
folks
that
started
that
day.
So
it
helps
to
bootstrap
this
contribution
and
then
keep
provide
support,
be
as
provide
feedback
as
to
them
how
it's
work.
It
is
working
if
they
are
stuck
if
they
have
some
problem
contributing
after
the
event
tell
2/6
go
to
experience.
B
There
are
a
lot
of
parties
Nikita
that
will
help
you
improve
your
teaching
skills
and
help
you
build
a
better
community
around
your
your
local
committees,
just
to
be
graceful.
All
the
people
that
came
to
the
event
more
than
20
an
important
thing.
Not
all
of
them
are
computer
scientists.
We
can
see
here.
B
Emilia
Emilia
is
a
teacher
in
a
public
school
and
is
it
kubernetes
contributor
has
no
idea
of
goal,
has
no
idea
of
programming
languages,
but
has
a
lot
of
knowledge
about
teaching,
don't
be
afraid
if
you
don't
know,
go
or
if
you
don't
know.
Python
of
you
know,
technology
at
all,
at
the
end
is
language
we
are
trying
to
solve
and
localize
a
weapon
to
localize
content
and
teach.
B
So
if
you
are
going
to
teach,
you
are
welcome
to
to
contribute
to
documentation
and
everyone
is
able
to
teach
everyone
from
the
most
expert
one
to
the
most
junior
one,
so
don't
be
afraid
of,
of
contributing
and
not
only
to
documentation
to
content,
also
teach
cover.
Needless
to
to
default.
In
your
community
we
run
a
serious
office
to
the
jams
who
went
to
history
jams,
two
of
them
20
people.
It's
like
a
good
fit
from
20
people
to
are
there
out
here
sorry.
So
what
we?
What
we
do?
B
We
get
a
concept,
for
example,
pot,
and
we
spend
two
hours
two
and
a
half
hours
talking
only
about
pot
in
a
discussion,
so
we
had
a
concept
we
asked
to
the
thought
they
came.
Everyone
makes
his
point
and
tries
to
solve
the
problem.
Then
we
try
to
get
it
done.
If
it
fails,
we
try
to
explain
why
it
failed
if
it
works.
We
move
to
the
next
concept
last
week
with
it
the
same
thing,
but
for
replica
set
to
another
two
and
a
half
hours
talking
about
replica
set.
B
We
had
I
think
more
than
45
examples
and
the
scrip
is
in
in
github.
I
will
show
you
everything
that
I
used,
because
all
I
do
is
pulling
you
cut
everything
everything
even
the
things
that
use
for
me
my
platform,
my
code.
Everything
is
public,
so
you
can
cut
me
or
you
can
use
through
to
to
build
your
own
project,
and
we
will
try
to
run
this
series
as
long
as
it
takes
if
we
need
to
spend
5
hours
talking
about
replica
set.
B
It's
ok
I
learned
a
lot
about
a
bigger
sets
during
working
on
this
on
this
series,
and
the
important
thing
is
learning
and
keeping
the
the
pace
that
the
people
needs
and
that's
the
most
important
thing
you
teach
to
allow
other
people
to
learn.
The
important
people
are
the
others,
not
you
so
take
their
time,
I
mean
if
you
need
crab.
If
you
want
to,
let
think
this
this
thing
I
started.
I
will
be
more
than
happy
to
help
and
that
John
any
question.
C
C
C
B
B
You
can
not
internal
translate
everything.
For
example,
you
will
use
coop
cattle,
apply,
coop
cattle,
deep
to
cut
a
note.
The
replica
said:
I
think
that
they
in
in
documentation,
everything
that
is
from
the
kubernetes
namespace-
is
written
in
the
kubernetes
in
the
same
way,
in
a
english
in
this
case,
because
you
will
use
the
tools
that
way
when
we'd
say
about
localizing.
This
tool
chain
is
help
messages,
so
you
ran,
could
cut
all
apply
and
you
get
an
error
message
that
error
can
be
in
Spanish
or
kami.
Both
you
can
say
like.
B
Ok,
let's
make
both
or
you
can
like,
have
a
flag
and
get
the
language
the
same
error
only
in
English,
if
you
want,
but
the
the
thing
is
that
if
you
are
in
Spanish-
and
you
get
a
message
in
Spanish
about
what
what
was
the
problem,
maybe
you
can
fix
the
problem
right
away.
Instead
of
going
to
Google
Translate
or
to
the
stack
overflow,
so
the
thing
is
making
easy
of
not
changing
the
language.
B
There
is
really
is
it's
not
useful
at
all
like
change
the
burbs
of
the
actions
of
the
tool
chain,
because
it's
hard
and
not
all
the
languages,
have
the
same
work
and
I
think
that
it
is
not
the
problem
we
are
trying
to
solve.
The
problem
that
we
are
trying
to
solve
with
the
International
internationalization
is
to
have
the
users
that
if
they
have
a
problem,
they
can
get
better
understanding
because
they,
the
error,
is
written
in
the
language
that
helped.