►
From YouTube: GSoD 2020 Documenting Jenkins on Kubernetes Dec 9, 2020
Description
Zainab Abubakar shares her experiences Documenting Jenkins on Kubernetes as part of Google Season of Docs 2020. Her project is described at https://www.jenkins.io/sigs/docs/#jenkins-on-kubernetes .
A
A
A
B
Okay,
so
I'm
going
to
start
with
presenting
a
slide
just
a
little
bit
of
information
on
the
product
and
the
project
overview
and
what
we're
able
to
achieve
then
we'll
branch
to
a
short
demo
before
coming
back
to
discuss,
challenges,
lessons
lens
and
then
a
q
and
a
session.
So
I'm
going
to
start
with
the
slides.
B
You
can
find
me
on
twitter
and
github
at
the
same
codes,
so
today
we're
going
to
be
discussing
the
problems,
statements
for
this
project
and
what
informed
this
google
season
of
docs
project
we're
going
to
look
at
how
we
plan
the
solution.
I
broke
down
this
part
into
two
because
it
was
majorly
two
phases
for
me:
that's
before
getting
accepted
into
google
season
of
docs.
What
were
the
things
I
did
to
prepare
for
this
project
and.
B
We
needed
to
prepare,
after
getting
accepted
before
the
documentation
development
phase,
we're
going
to
look
a
little
bit
at
the
documentation
development
phase.
What
did
we
do
before
we
branch
to
a
short
demo
discuss
challenges,
lessons
lengths
and
a
q
and
a
session?
So
let's
start
with
the
problem
statement.
B
Considering
that
jenkins
on
kubernetes
is
a
popular
teams
team
for
jenkins
user,
and
that's
why
we
took
up
this
project
so
planning
the
solution
before
I
got
accepted
to
google
season
of
docs.
I
went
through
the
list
of
project
ideas
and
I
was
particularly
enthralled
by
this
particular
project
to
document
jenkins
from
kubernetes.
So
the
first
thing
I
did
was
to
make
some
research
find
out
a
lot
about
jenkins
on
kubernetes,
see
if
it
was
something
I
could
actually
do.
I
could
actually
take
up.
B
So
I'm
one
of
the
reasons
why
I
chose
this
project
was
because
I
had
an
interest
in
jenkins
because
in
the
organization
where
I
work,
we
currently
use
jenkins
and
spin
anchor
for
our
ci
cd
pipelines,
and
I
had
a
thrill
in
setting
up
jenkins
when
I
had
the
opportunity
to
so
seeing
this
project
was
more
like
an
opportunity
for
me
to
understand
more
of
jenkins
and
to
get
more
into
devops.
So
I
did
my
research
and
I
worked
on
my.
B
B
B
So
in
this
structure
I
gathered
all
the
links.
I
had
all
the
links
that
I
had
found
from
my
research.
I
gathered
them
into
the
structure
to
help
me
work
on
the
content
when
the
time
came
so
after
working
on
the
structure
yeah
after
working
on
the
structure,
I
submitted
my
proposal
so
when
I
got
accepted
into
google
season
of
dogs,
these
were
the
things
we
did
in
preparation
for
the
project,
so
pre-planning
of
the
project.
In
this
phase.
B
This
was
where
we
discussed
and
agreed
on
communication
channels.
This
was
where
we
discussed
things
that
would
probably
be
necessary
for
the
projects
like
permissions
and
other
useful
tools
or
resources.
That
would
be
useful
for
the
jenkins
on
kubernetes
project.
After
that
we
discovered
knowledge
transfer.
What
were
the
knowledge
sessions
that
I
was
going
to
need?
What?
Where
was
I
lacking
in
knowledge
to
be
able
to
properly
work
on
this
project?
B
And
this
was
where
we
agreed
to
have
knowledge
sharing
sessions
on
helm
and
katakuda
during
the
google
season
of
docs
program,
refined
project
goals?
So
here
we
kind
of
expanded
on
my
proposal
and
the
structure
I
had
created,
so
we
looked
at
it
and
my
mentors
looked
at
it
and
we
decided
on
the
content
that
we're
necessary
to
be
there
and
the
ones
that
were
in
there
and
we
kind
of
like
also
rated
according
to
the
most
important.
B
B
Now
during
the
documentation
development
phase,
I
broke
this
down
into
three,
so
the
first
part
is
the
knowledge
sharing
session.
So
here
I
had
the
opportunity
of
having
two
knowledge
sharing
sessions
from
two
very,
very
knowledgeable
people,
one
of
them
being
my
mentor
and
orga
admin
and
the
other
person
trusting
the
first
person
maki
maki
jackson
is
my
mentor.
B
He
gave
a
session
on
helm
and
katakuda,
and
the
second
person
charleston
was
is
a
member
of
jenkins
community
and
he
also
gave
me
a
knowledge,
I'm
sharing
session
on
him,
which
really
helped
me
in
properly
documenting
jenkins
on
kubernetes.
After
that,
I
and
the
mentors
worked
on
a
skeleton.
So
this
was
where
the
initial
structure
that
I
created-
and
I
am
my
mentors
refined
during
the
planning
phase-
this
was
where
it
actually
came
to
life.
B
B
Here,
I'm
just
going
to
show
some
of
the
sections
that
we
added
to
jenkins
that
I
will
do
during
the
in
the
skeleton
so
we're
able
to
work
on
some
during
the
google
season
of
dogs
program,
but
some
of
them
are
still
currently
pending,
which
we
still
intend
to
complete,
as
time
goes
on,
with
the
help
of
the
mentors
and
community
and
other
people
out
there.
Who
would
like
to
contribute
to
jenkins
on
kubernetes.
B
No
sorry
that
would
be
money
chain
or
system
administration,
okay,
so
under
system
admission
yeah.
So
this
is
an
example
of
a
section
that
we
were
not
able
to
complete
during
the
google
season
of
dogs
program,
as
you
can
see,
is
still
showing
a
work
in
progress,
but
hopefully
with
time
we
intend
to
complete
this
then.
B
So
now
we're
going
to
go
through
a
short
demo
on
installing
jenkins
on
kubernetes,
using
jenkins
operator
and
in
this
demo
we're
going
to
use
the
documentation
that
I
worked
on,
we're
going
to
follow
the
documentation
through
and
through
and
see
that
the
documentation
actually
works,
yeah,
okay,
so
under
the
installing
jenkins
section.
So
before
I
go
to
the
demo,
I
just
like
to
give
a
brief
summary
of
the
sections
that
I
was
able
to
add.
B
So
I
was
able
to
add
section
on
installing
jenkins
on
kubernetes
and
in
this
section
it
covers
three
methods.
We
have
using
helm
using
j
using
a
set
of
yamu
files
and
using
the
jenkins
operator,
so
in
this
demo
we're
going
to
be
working
with
the
installing
jenkins
with
jenkins
operator
section.
So
I'm
just
going
to
bring
up
my
terminal
yeah.
B
B
Okay,
so,
okay,
so
first
of
us,
was
the
jenkins
operator.
So
the
jenkins
operator
is
a
kubernetes
native
episode
which
manages
operations
for
jenkins
on
kubernetes.
It
is
easy
to
install
with
just
a
few
manifest
and
it
allows
users
to
configure
and
manage
jenkins
on
kubernetes.
So
some
of
the
advantages
that
the
jenkins
operator
provides
is
that
it
provides
an
out-of-the-box
integration
with
kubernetes
that
you
have
the
kubernetes
plug-in
pre-configured.
B
B
B
B
Okay,
I
think
we
have
a
section
just
above
here
that
shows
how
to
create
yeah
equivalent
is
cluster.
So
if
you
don't
already
have
a
kubernetes
cluster,
you
can
just
come
up
to
this
section
and
follow
the
steps
here
to
achieve
that.
So
I
already
have
that
installed
on
my
pc.
So
I'm
not
going
to
need
to
do
that.
B
B
I
just
want
to
make
sure
that
we
can
see
the
content
on
the
documentation
and
also
on
my
terminal
as
I
go
so
from
the
output
here.
We
can
see
that
it
has
installed
two
crds
here,
jenkins.jenkins.io
and
jenkins
image,
george
jenkins
io.
So
after
doing
that
successfully
we're
going
to
deploy
jenkins
operator
so
to
deploy
jenkins
operator,
there
are
two
options
here
that
we
could
use.
B
We
could
decide
to
use
yaml
files
or
the
helm
chat,
but
for
this
demo
I'm
going
to
be
using
helm
chat
to
install
the
jenkins
operator.
So,
what's
a
hem
chart,
a
helm
chart
is
a
packet
package
manager
for
kubernetes,
and
it's
format
is
called
a
chat.
Hem
charts
basically
provide
a
push
button
deployment
for
push
button
and
function
to
deploy
and
delete
applications,
so
it
makes
the
adoption
of
kubernetes
apps
easier.
It
helps
you
to
manage
your
kubernetes
applications
and
easily.
B
So
since
I
already
have
helm
installed,
I'm
just
going
to
go
straight
to
configuring
helm
on
the
documentation
yeah.
So
where
is
it
yeah
exactly
so,
since
I
already
have
helm
installed?
Okay,
so
before
I
configure
him
I'll
create
a
namespace
for
the
operator
so
also
on
the
documentation,
we
have
a
section
that
explains
how
to
create
a
namespace.
So
I'm
just
going
to
run
that
command
cube
c
t
l
create
namespace.
So
I'm
going
to
be
doing
my
deployment
in
the
jenkins.
A
B
Okay,
so
I
already
have
this
installed
on
my
box.
So
that's
why
I
didn't
install
jenkins
already
exists
with
the
same
configuration.
So
if
you
don't
already
have
this
before
it's
going
to
show
you
that
your
hem
chat
has
been
added.
So
I'm
going
to
move
on
to
the
next
step,
which
is
to
install
the
jenkins
operator
in
the
jenkins
namespace
and
we're
going
to
be
using
yeah.
B
B
Yes,
so
you
can
see
that
my
jenkins
operator
was
successfully
deployed.
So,
as
I
was
saying,
you
can
hide
labels.
You
can
add
annotations
to
customize
your
installation,
that's
to
customize
the
official
jenkins
value
in
this
installation.
I've
used
the
values
in
the
official
helm,
charts
repository.
I
didn't
make
any
changes,
but
while
you're
doing
yours
depending
on
your
needs,
you
can
customize
the
values
using
labels
while
deploying
so
after
we
successfully
installed
the
jenkins
operator.
B
B
B
B
Yes,
so
we
can
see
that
my
jenkins
example
instance
is
up
and
running.
My
epitope
jenkins
operator
instance
is
running.
My
jenkins
example
instance
is
also
running,
so
this
jenkins
example
is
the
instance
I
just
created.
So
if
you
check
the
file,
you
can
see
that
the
name
of
the
file
here
is
example.
B
So
that's
why
it's
jenkins
example,
if
you
named
your
own
file
jenkins,
is
going
to
be
jenkins
jenkins.
If
you
named
it,
jenkinski
is
going
to
be
thank
you
for
joining
so
depending
on
what
you
named
it.
So
my
pod
is
not
yet
ready,
because
normally,
when
you
do,
this
jenkins
is
going
to
it's
going
to
install.
B
B
Yeah,
so
we
can
see
it's
installing
plugins
and
this
is
not
done
yet.
So
that's
why
our
port
is
in
that
state.
So
for
you
to
be
able
to
access
your
jenkins,
obviously
you
need
to
get
the
login
credentials
to
do
that
and
to
do
that.
We're
going
to
run
this
so
secret
name
here,
jenkins
operator,
credential,
credential
name
so
credential
name
here
being
the
name
you
used
in
your
jenkins
instance
file,
as
I
explained
earlier.
So
in
this
case
my
credential
name
is
going
to
be
example.
A
B
Yeah
so
mark
you're
right
there
so
because
my
plugins
has
not
installed-
and
this
takes
this
plugin
installation
takes
a
lot
of
time
here
because
of
my
internet,
internet
connectivity
and
all
that.
But
once
the
plugin
is
installed
successfully,
you
should
be
able
to
get
your
credentials
and
you
can
connect
to
jenkins
using
either
mini
cube
through
the
service
or
you
can
put
forward
and
access
the
actual
kubernetes
cluster.
B
A
B
Okay,
so
it's
still
not
opiates
and
I'm
going
to
assume
that
it's
still
installing.
So
what
I
wanted
to
explain
is
there
are
some
instances
where,
when
you
describe
your
port
here,
because
jenkins
is
not
yet
ready
to
handle
requests
is
still
installing
plugins.
You
might
see
a
one
in
here
or
an
arrow
here
that
tells
you,
readiness
proof
filled
unable
to
connect.
So
what
this
means
is
that
jenkins
is
up,
but
it's
not
yet
ready
to
handle
requests.
B
So
basically,
kubernetes
has
three
types
of
health
checks.
The
startup
check
the
readiness
check
and
the
liveness
check,
so
the
startup
check
is
basically
to
check
if
the
application
has
started
and
if
it
has
it
moves
to
the
readiness
group.
So
the
readiness
check
checks
if
the
application
is
ready
to
handle
request.
If
it's
ready,
then
kubernetes
sends
requests
to
this
port,
but
if
it's
not,
then
kubernetes
keeps
trying.
So
when
an
application
fails,
a
readiness
check,
kubernetes
doesn't
delete
the
port.
B
It
just
keeps
retrying
until
the
pod
is
ready
to
handle
request.
Why
the
last
one,
which
is
a
liveness
check,
is
when
kubernetes
checks
the
application
to
see.
If
it's
actually
up
so
when
an
application
fails,
aliveness
checks,
kubernetes,
deletes
that
port
and
creates
a
new
instance,
because
it's
assumed
that
the
application
is
good.
So
I'm
going
to
end
my
demo
session
here
and
yeah,
so
we're
going
to
continue
with
this
slide.
B
So
what
are
the
challenges
I
faced
during
during
this
project?
So
I
think
the
major
challenge
I
faced
was
using
a
windows
laptop.
So
there
were
a
lot
of.
I
had
some
difficulties
running
some
commands,
but
the
good
side
of
this
challenge
is
that
it
gave
me
the
opportunity
to
actually
work
on
different
environments
and
test
the
documentation
on
different
environments
to
ensure
that
whoever
is
using
a
windows,
pc
or
a
linux
pc
would
be
able
to
scale
through
and
use
the
documentation
without
having
any
issues.
B
B
So
what
are
the
lessons
lent?
I
learned
more
about
the
jenkins
project.
I
learnt
more
about
kubernetes,
helm,
10ks
operator,
and
this
product
also
helped
improve
my
technical
writing
skills
communication
skills
because
I
had
to
communicate
with
my
mentors
constantly
and
even
from
the
exploration
phase.
B
I
shared
my
proposal
with
them
to
review
and
make
comments
on,
and
suggestions
on
what
information
they
think
would
be
best
to
add
to
this
documentation,
so
this
project
definitely
improved
my
collaboration
skills
also,
so
that
would
be
all
for
me.
So
can
ask
your
questions
and
I'll
be
happy
to
answer
them,
and
if
I
can't
I
know,
one
of
my
mentors
will
be
able
to
help
me.
Thank
you.
A
Thank
you
zenob,
so
we
do
have
one
question
online
actually
and
this
one
I
confess
we
may
have
to
call
on
the
mentors,
I'm
not
sure.
So
the
question
asked
was
how
how
can
we
manage
adding
new
plugins
and
upgrading
plugins
after
the
jenkins
installation
is
done?
Can
we
manage
jenkins
plugins
as
code?
A
B
Okay,
so
I'll
just
give
a
little,
so
my
mentors
can
help
me
complete
it.
So
I
know
when
you're
using
helm
to
install
jenkins.
As
I
said,
there
are
two
instructions
you
can
use.
You
can
use
that
either
use
the
helm,
install
or
helm
upgrade
so
with
the
helm
upgrade
command.
You
can
use
that
to
add
additional
plugins
and
even
additional
functionalities
to
your
jenkins
instance.
So
I
think
my
mentors
can
take
too.
E
Long,
you
are
exactly
correct
if
you
add
that
to
your
your
template
for
your
charts
in
helm,
you
can
then
run
the
helm
update
and
it
will
update
those
plugins.
You
could
add
a
little
bit
extra
and
keep
that
in
git
and
use
get
opt
so
anytime.
There
is
a
change
to
the
repo
some
type
of
web
hook
and
delivery
will
push
those
changes
out
to
a
given
cluster.
A
E
B
Well,
for
me
to
be
able
to
use
when
I
think
one
thing
that
helped
me
was
actually
a
lot
of
research
trying
this
trying
that-
and
I
actually
had
to
when
I
see
a
particular
command
in
linux.
I
try
to
research
if
there's
a
corresponding
command
in
windows
and
if
there's
not,
I
find
an
alternative.
So,
for
instance,
there
is
a
command
here.
I'll
just
go
to
thought.
I
am
sorry.
B
Yeah,
so,
okay,
I
just
want
to
give
an
example
of
how
I
was
able
to
walk
around
some
of
the
issues
I
had
okay,
so
yes,
for
instance,
this
section
on
getting
credentials.
So
when
I
try
to
run
this
command
on
my
windows
box,
I
I
get
an
error
that
base64
is
not
installed
or
does
not
exist,
or
something
like
that.
B
So
what
I
don't
do
is
I
take
out
the
base64
part
and
actually
get
the
secret
in
b64,
and
I
just
go
to
basis
for
encode.com
and
I
decode
them
the
secret
by
myself
just
to
get
work
around
that.
I
know
there
probably
might
be
better
solutions,
but
but
that's
just
basically
how
I
do
it.
So
when
I
find
a
stumbling
block,
I
just
do
some
research
and
hopefully
we're
able
to
work
around
that.
A
Excellent.
Thank
you
thanks.
Thanks
very
much
windows
is
so
were
you
an
expert
in
kubernetes
before
you
started
this
project?
What
what
was
it
like
for
you
to
begin
on
a
project
like
this?
Were
you
already
deeply
skilled
with
kubernetes,
and
so
it
was
just
doing
what
you'd
already
done,
or
did
you
have
a
bunch
of
things
you
had
to
learn.
B
So
I
wouldn't
say
I
was
deeply
skilled,
though
I
wasn't
at
least
I
had
some
background
knowledge
of
kubernetes
because
again,
where
I
work
currently
at
intersewage,
we
use
kubernetes
a
lot.
That's
where
we
deploy
our
applications,
so
I'm
familiar
with
creating
deployments,
creating
config
maps
and
doing
some
edits,
I'm
literally
to
commands
like
that.
So
I
was
already
familiar
with
that
before
I
started
working
on
this
project,
but
obviously,
when
I
started
working
on
this
project,
I
had
to
do
more.
B
A
Thank
you
so
now
now
the
install
guide
lists
three
different
forms
of
install
methods,
helm,
base,
yaml
and
operator.
Are
there
any
guidance
you
want
to
give
the
audience
on
when
they
would
choose
one
of
those
versus
the
others,
particularly
for
somebody
who's?
Not
a
kubernetes
expert
me,
for
instance,
I'm
not
expert
in
this.
Is
there
one
I
should
prefer,
rather
than
another.
B
Okay,
so
well
I'll
just
say
this
is
a
personal
evaluation.
I'm
not
going
to
say
is
in
general,
so
what
I
think
is
before
you
decide
on
which
method
you
want
to
use.
You
need
to
analyze
your
midterm
goals.
Do
you
want
to
be
able
to
deploy
faster?
Do
you
want
to
change
your
continuous
deployment
pipeline
regularly?
B
Or
do
you
just
want
something
simple
to
begin
with
and
then
focus
on
the
details
later?
So,
when
you're
able
to
answer
these
questions,
then
you
can
then
decide
on
okay,
hey
I'm
going
to
use
yaml
files,
because
if
you're
going
to
be
using
yaml
files,
I
think
I'll
advise
that
it's
on
small
projects
cause
you.
B
You
know
you're
going
to
have
to
be
setting
up
things
like
your
deployment
service,
ingress
percent
volumes
and
all
that
you're
going
to
have
to
have
to
be
applying
files
for
all
that,
and
if
you
have
a
lot
of
apps
that
you're
managing
on
kubernetes
or
you
have
a
lot
of
things
that
you
want
to
do
or
your
project
is
very,
very
large.
At
the
end
of
the
day,
this
could
become
difficult
to
manage
so
depending
on
how
large
your
application
is,
or
the
projects
you're
working
on.
B
A
C
C
B
Okay,
so
well
surprises,
I
wouldn't
really
say
surprises
just
that
I
had
some
issues
that
I
didn't
envisage
from
the
beginning,
which
is
normal
with
every
developer.
You
know
that
when
you're
writing
code
or
you're
working
on
anything,
technical
issues
tends
to
come
up
that
you
didn't
plan
so
I'll
say.
Yes,
I
had
that
but
surprises.
Well,
I
don't
know
because
maybe
because
I
I
already
knew
okay,
I
was
working
with
kubernetes
and
I
already
saw
kubernetes
as
a
huge
project
and
jenkins
another
huge
project.
B
So
I
already
had
expectations
that
I
was
going
to
see
a
lot.
I
was
going
to
learn
a
lot,
so
I
wouldn't
say
I
was
so
surprised,
then,
for
advice
on
people
that,
like
to
work
on
open
source
project
I'll
say
if
you
want
to
you,
need
to
be
ready
to
do
your
research,
because
you
don't
want
to
get
on
the
project
and
be
asking
questions
that
are
already
available
questions
on
information
that
is
readily
available
for
you
already.
So
you
need
to
do
your
research
first.
B
Try
to
engage
with
the
community
ask
questions.
When
you
have
issues
it
will
help
a
lot
and
try
and
because
I
think,
when
I
try,
when
I
start
contributing
to
open
source,
I
was
shy
actually
to
ask
questions.
I
was
in
outreachy
19
round
and
I
think
that
was
one
of
my
takeaway
from
that
program
to
ask
questions.
B
Even
if
I
should
be
asking
questions,
it
should
be
something
about
projects,
not
something
about
it,
but
the
truth
is
we
are
always
learning,
no
matter
how
experienced
you
think
you
are
issues
will
pop
up
along
the
way
that
you've
not
come
across,
and
sometimes
you
might
have
even
come
across
them
before,
but
you
can't
just
remember
how
to
solve
it.
So
it's
important
that
you
ask
questions.
You
know
how
to
ask
questions.
B
It's
important
that
you
learn
to
collaborate
because
there
can't
be
open
source
without
collaboration,
so
I
think
that's
that's
it.
For
me,
research
ask
questions,
collaborate
and
write
and
also
once
you
write,
try
and
push
it
out
for
as
much
people
as
you
can
to
review,
because
when
you
finish
writing
it
might
look
perfect
to
you.
But
someone
looking
at
it
from
another
angle
might
see
issues
and
things
that
you
didn't
see.
B
C
B
So
I
think
he
was
mostly
independent
because
I
know
other
google
season
of
dogs
writers
bought
with
other
projects,
so
what
they
were
working
on
was
not
really
related
to
what
I
was
working
on.
So
working
on
this
project
was
majorly
me
mentors
and
obviously
I
had
some
help
from
other
members
of
my
organizations
who
were
very
knowledgeable
in
jenkins
and
kubernetes.
A
B
A
E
B
Thank
you
so
much
marky
and
thank
you
very
much
to
the
mentors
for
being
so
so
patient
with
me
and
being
always
ready
to
help.
It's
really
really
motivated
my
success
in
this
project.
A
lot.
The
fact
that
I
knew
that
mentors
were
always
there
when
I
needed
help
and
there
was
no
putting
me
down.
I
never
felt
bad
at
any
point
in
time
when
I
had
issues
because
the
atmosphere,
the
reception,
was
very,
very
welcoming.
Thank
you
so
much.
D
All
right,
I
like
to
echo
marky's
comments:
yeah
cuz,
like
a
lot
of
what
I
was
gonna,
ask
her
about
like
getting
started,
continuing
writing
in
the
project.
I
think
we
did
a
great
job
of
like
explaining
the
process
of
how
to
work
with
the
documentation
and
get
out
there
and
the
importance
of
working
within
the
community
and
asking
questions
and
stuff
that
was
great
and
yeah.
Everything
was
wonderful.
It
was
a
great
experience,
so
congrats
the
documentation,
looks
wonderful.
A
All
right,
so
I'm
going
to
go
ahead
and
stop
the
recording.
What
we
like
to
do
at
this
point
is
we
intentionally
stop
the
recording
so
that
we
can
open
it
up
for
anyone
to
ask
questions
we'll
make
everyone
live,
z,
knob!
If
you
want
to
switch
off
the
screen,
sharing,
we'll
we'll
just
go
and
let
the
cameras
work,
okay
and
and
I'm
going
to
go
ahead
and
stop
the
recording.
Then
we
can.
We
can
actually
ask
questions
openly
in
the
forum.