►
From YouTube: Online Meetup: "Jenkins on Kubernetes: Getting started" by Marky Jackson (Apr 17, 2020)
Description
Presenter: Marky Jackson, Anchore
One of the strongest sides of Jenkins is that it has a scaling feature almost out-of-the-box, but these features need additional configuration and the infrastructure layer. There are many ways to implement Jenkins scaling: to build parallelization, on-demand agents, etc. One of the powerful options available right now is Jenkins scaling on top of Kubernetes and in this presentation. Marky, an active Kubernetes and Jenkins contributor, will show you how to do just that.
This presentation covers the following:
* How to get Jenkins running natively on K8s?
* Provisioning on-demand agents with Kubernetes Plugin
* Live Demo
Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/269888701/
Slides by Marky: https://docs.google.com/presentation/d/1r3S3T8VXePv7qwPAo5dlFe1PgaHS3ui4dR-Vjlo8XXE/edit?usp=sharing
Demo: https://github.com/markyjackson-taulia/jenkinsci-on-kubernetes
Note: There are a few areas where the sound has been removed via editing
A
Yeah
baby
reporters
now:
oh
thanks
for
coming
to
the
Jenkins
online
Meetup.
They
have
special
guest
market
Jackson.
He
will
be
present
and
just
talk
about
the
Jenkins
on
kubernetes
and
it
will
show
how
to
get
started.
Is
it
if
you
have
never
participated
in
joining
us
online
Meetup?
It's
a
online
platform.
We
using
the
jenkees
community.
We
have
several
dozens
meetups
around
the
world,
but
we
all
straight
organized
online
events,
especially
at
least
once,
and
for
that.
A
This
meetup
is
basically
organized
by
contributors,
so
everybody
there
volunteers
their
own
time
and
we
try
to
do
our
first.
We
talk
about
developer
tools
about
the
best
practices,
about
Fusion
changes
everywhere,
and
the
main
objective
is
to
show
and
tell
so.
We
won't
have
so
presentations.
We
won't
have
marketing
pitches
instead
of
data.
We
won't
focus
on
real
experience
and
we
invite
everyone
to
contribute
by
comments
or
by
joining
next
to
meetups
and
again.
A
The
topic
today
is
about
Jenkinson
kubernetes,
I'm
not
sure
how
many
of
you
already
use
kubernetes,
but
in
definitely
it
gets
more
and
more
popular
and
in
the
jenkees
project.
Of
course,
we
want
to
ensure
that
the
Jenkins
Frances,
mostly
on
kubernetes
and
Jenkins,
is
a
part
of
the
business
ecosystem.
There
is
a
lot
of
ongoing
work,
including
roadmap.
We
want
to
include
more
topics
and,
of
course,
you
also
want
to
talk
about
what
happens
and
how
to
use
edging
brothers.
A
So
basically
we
interested
about
anything
if
you
interested
to
tell
you
war
stories,
key
studies
or
show
how
to
automate
your
flow
Sagi's,
Jenkinson
kubernetes.
We
are
welcome
such
discussions.
I
use
the
automation
world,
but
it
may
also
mean
CRA.
Cde
develops
whatever
Jenkins
can
help
everywhere,
and
if
you
want
to
do
some
specific
thoughts
or
if
you
want
to
get
more
information
means
for
couches
watching
but
not
saturated.
It's
a
separate
project
which
is
available
or
just
going
about
integration
is
different,
kubernetes
tools
or
called
provider.
A
Three
issues
that
industries
do
so
for
all
these
topics
we
are
going
to
have
tops.
We
have
actually
a
series
of
these
meetups
right
now
or
there
is
around
five
and
we
are
looking
for
more.
So,
if
you're
interested
to
present
your
experience,
please
let
us
know,
but
it's
a
boxy
Aneesh
guiter
channel,
and
that
is
also
a
janky
CIA
channel
in
the
kubernetes
slug.
You
can
use
one
of
these
channels
to
contact
us
and
we
can
talk
about
presentations
or
if
you
want
to
request
a
particular
topic.
A
We
are
also
happy
to
help
and
work
together
for
options.
That's
it
for
me,
lately
have
in
Marquis,
who
will
present
how
to
get
started
on
kubernetes
mark
is
negative
contributor
in
the
Jencks
community
is
also
a
realtor
in
Pinellas
community
and,
of
course,
it's
a
pleasure
to
have
him
at
this
Meetup
I
believe
Marquis
will
present
himself
later
dismal
details
and
if
you
have
any
questions
during
the
presentation,
that
is
the
zoom
chat.
B
B
B
B
For
those
that
don't
know
me,
my
name
is
marquise
Jackson
I'm,
a
software
engineer
working
on
open
source
integrations
with
Angkor
I
am
a
Jenkins
core
maintainer,
as
well
as
the
plug-in
maintainer
for
many
plugins,
the
kubernetes
plugin,
the
prometheus
plugin
and
many
more
I'm
a
kubernetes
org
member
I
work
with
the
country
Becks
and
most
recently,
I
was
made
a
release.
Engineer
associate
you
can
find
me
on
github
at
Marquis,
Jackson
Talia
or
on
Twitter
at
Marquis,
Jackson
5.
B
Also
at
LinkedIn,
I'm,
not
gonna,
go
ahead
and
read
that
all
for
those
that
don't
know
me,
one
of
the
things
I'd
like
to
make
very
known
is
I
love
to
answer
people's
questions.
It
makes
me
feel
good
to
help
people-
and
just
you
know
if
you
have
a
question
that
you
don't
want
to
ask
here
or
don't
feel
comfortable
asking
in
a
public
setting,
and
you
want
to
do
it
privately.
My
messages
are
open
on
Twitter
and
you're.
More
than
welcome
to
message
me
I,
try
not
to
do
a
lot
of
the
helpdesk
things.
B
So
you
know
I
expect
that
everybody's
done
the
level
of
research
before
you
ask
the
question,
but
if
you
want
to
just
chat
and
say
hi
I'm,
a
super
friendly
person
for
those
that
do
know
me
we'll,
say:
I'm
a
friendly
person.
So
what
are
we
going
to
talk
about
today?
The
presentations
gonna
cover
a
light
and
I
specify
a
very
light
overview
of
qumran
Eddie's
and
the
kubernetes
plugin
and
the
reason
I
say
a
very
light.
B
I
won't
be
going
into
the
real,
deep
technical
weeds
of
what
kubernetes
is
or
what
Jenkins
is
I
will
cover
how
to
set
up
and
configure
Jenkins
on
kubernetes
I
will
show
you
how
to
use
the
kubernetes
plugin
I'll.
Do
a
code.
Walkthrough
that'll
show
you
some
of
the
yeah
moles
that
I
will
be
using
for
this
I'll.
Do
a
demo
of
that
and
then
we'll
close
up
with
some
questions
and
answers
mm-hmm.
So
let's
go
ahead
and
get
started.
B
What's
kubernetes
like
everybody
knows
what
I
would
hope.
What
kubernetes
is
it's
a
pretty
hot
topic
in
the
tech
sectors,
but
kubernetes
or
as
k8s
as
some
people
call
it
it's
a
project
that
was
spun
out
of
Google.
It
was
an
open-source
next-generation
container
scheduler
that
was
designed
with
lessons
learned
from
developing
and
managing
a
project
internally
at
Google
called
Borg
and
Omega,
and
essentially,
what
that
does.
Is
it
abstracts
away
the
layers
of
Hardware
of
the
nodes
and
provides
a
uniform
interface
for
application
and
scheduling
of
resources
in
a
shared
pool?
B
Why
would
you
want
to
put
Jenkins
on
kubernetes
or
use
some
of
the
agent
ability
for
scalability
in
kubernetes
work,
like
I
just
said,
scalability,
containerization
and
also
infrastructure
as
code?
One
of
the
things
that
I
didn't
mention
in
here.
That's
really
critical
to
to
understand
is
when
you
think
about
kubernetes
and
jenkins.
One
of
the
ideas
here
is
a
cost
savings.
So
doing
putting
jenkins
in
kubernetes
also
is
a
benefit
in
a
cost
savings,
so
the
kubernetes
plugin
I,
am
one
of
the
maintainer
x'.
B
The
gentleman
named
Carlos
Sanchez
wrote
that
plugin,
which
basically
allows
the
running
of
dynamic
agents
in
at
uber
Nettie's
cluster.
By
doing
that,
what
you
do
is
you
lower
the
cost
of
having
to
spin
up
agents
everywhere?
It
helps
you
with
the
ability
to
set
that
up
as
infrastructure
as
code
and
then
I've
also
included
a
link
to
where
that
repo
for
that
plug-in
is.
I
will
also
say
that
I
won't
go
into
the
real,
deep
technical
ways
that
you
can
use.
B
This
plugin
I
will
keep
it
at
a
very
high
level,
just
for
rent
running
dynamic
agents
and
kubernetes,
but
there's
all
kinds
of
different
ways
that
you
have
the
ability
to
use
the
kubernetes
plugins
such
as
setting
up
our
diamo
gamal
templates
and
all
kinds
of
things.
If
you
look
at
the
readme
on
the
plugin,
there's
all
kinds
of
examples.
B
So
before
we
get
into
the
demo,
which
is
what
the
crux
of
this
is
going
to
be,
I
want
to
talk
about
some
assumptions
in
this
demo
number
one.
In
order
to
run
this
demo,
you
have
a
kubernetes
cluster.
You
have
to
have
the
cube
CTL,
which
is
the
command-line
interface
that
allows
you
to
communicate
with
that
kubernetes
cluster.
B
You
have
to
have
the
code
I've
included
a
code
repo
here
where
I
have
made
it
public
the
code
that
I
will
be
using
here
for
this
particular
demo,
I'm
going
to
be
using
mini,
cube
and
it'll
be
running
on
the
latest
1.18
version.
You
do
have
the
ability
to
run
this
on
any
type
of
cluster,
an
example
in
the
kubernetes
community.
When
we
do
a
lot
of
our
testing,
we
use
kind,
which
is
kubernetes
and
dr
I've
included.
B
If
you
install
the
kind
platform,
there's
a
command
on
how
you
can
create
a
1.18
cluster,
and
then
you
can
run
through
this
demo,
so
I
am
going
to
get
started
into
the
demo.
I
will
go
ahead
and
give
me
just
a
second
as
I
move
through
some
of
these
screens
here.
So
I
want
to
talk
about
a
before
we
get
into
the
code
walkthrough,
which
is
right
here,
I'd
like
to
talk
about
a
few
things
that
we'll
be
using
in
here
and
I
want
to
give
them
a
little
bit
of
attention
before
we
start.
B
You
we'll
be
talking
about
is
the
Jenkins
image
that
we'll
be
using
for
our
agents.
Now
I
wanted
to
talk
a
little
bit
about
this
in
depth,
because
there's
a
lot
of
work,
that's
going
on
around
this.
As
you
know,
there
has
been
a
lot
of
a
lot
of
commentary,
a
lot
of
full
requestion
in
removing
some
of
the
terminology.
That's
used
in
Jenkins.
This
is
the
repo
that
we'll
be
using
for
our
template.
I'd
like
to
make
a
note
in
this
particular
section.
The
terminology
that
was
previously
used
has
now
been
deprecated.
B
A
B
B
So
one
of
the
one
of
the
things
that
has
been
done
here
is
changing
of
the
terminology.
So
a
lot
of
the
images
that
have
been
previously
used
have
been
deprecated
in
terms
of
naming
and
the
new
naming
is
now
the
inbound
agent
across
the
Jenkins
ecosystem.
There
are
there's
a
lot
of
work,
that's
also
where
people
are
changing.
B
The
terminology,
I'm
really
proud
of
the
work
that
the
entire
community
has
done
around
this
and
I've
noticed
it's
happening
a
lot,
another
open
source
project,
so
one
of
the
things
that
I
will
strongly
ask
people
to
do
is
when
you're
posting
comments
in
chats
try
to
be
mindful
and
empathetic
of
the
language
that
you're
using
and
the
language
that
the
Jenkins
community
is
using.
So
with
that,
let's
go
ahead
and
get
into
a
little
bit
of
the
code.
I
am
going
to
share
my
editor,
which
is
a
little
bit
easier
to
do.
B
The
base
image
is
a
very
simple
image.
This
is
not
meant
to
be
an
image
that
you
use
in
production.
I've
added
some
comments
into
the
image
here,
the
things
to
be
cleaned
up.
These
would
be
great.
First
issues
that
I'd
love
to
help
mentor
people
if
you
wanted
to
get
involved
and
try
to
understand
something.
B
I've
created
some
comments
in
here
for
cleaning
some
of
this
up,
I'm
gonna
spend
a
little
bit
of
time
on
the
are
backe
amel
and
the
reason
being
is
because
I
want
to
talk
about
some
of
the
pieces
that
are
involved
here.
So
we're
doing
three
things
in
this
chunk
of
code
number
one
we're
creating
a
service
account
very,
very
simple:
that
service
account
is
named
Jenkins.
B
B
We
then
create
a
cluster
role
binding,
which
binds
that
service
account
to
this
cluster
role.
Now
the
reason
I
wanted
to
spend
some
time
in
discussing
this
is
because
a
lot
of
people
may
be
confused
about
how
Auerbach
is
set
up.
So
there's
two
types
of
are
back.
There
is
what
you
would
call
a
role
or
a
cluster
role
when
you
define
something
at
the
cluster
role.
This
is
at
the
root
level
of
the
cluster
for
development
work.
This
may
be
good
to
do
because
it
helps
you
get
around
things
quicker
for
production.
B
B
We
then
have
our
service
and
there's
our
service.
Our
service
is
pretty
straightforward.
I
will
cover
this
one
part,
and
that
is
for
this
demo.
I
am
using
a
node
port.
A
node
port
is
good
for
quick
and
easy
development.
A
node
port
is
not
too
what
you
should
use
in
production.
So
please
note
that
this
demo
is
for
development
only.
You
should
not
use
this
in
production.
B
Finally,
we're
covering
the
deployment.
The
deployment
is
a
very
straightforward
piece
of
work
here.
It
basically
will
call
our
image
it'll,
set
some
Java
Ops
arguments
and
then
we're
gonna
set
a
volume
which
is
locally
an
empty
empty
directory
again.
This
is
only
for
development.
I
would
not
use
this
in
production,
so.
B
B
Welcome
I
apologize
for
the
small
text,
so
a
very
simple,
straightforward
deployment.
I
will
stress
that
the
again
this
is
only
I
know
you
keep
hearing
me
say
this
is
only
for
development
and
not
production.
The
reason
that
I'm
saying
that
is
there
so
sometimes
a
tendency
to
say.
Oh,
this
works
great
in
in
my
local
testing.
I'm
just
gonna
move
this
straight
to
you
know
production
for
my
company
I've
seen
that
happen.
This
is
not
the
code
you
should
be
putting
in
production.
B
B
B
B
B
We
can
see
that
the
service
was
created
and,
finally,
what
we're
going
to
do
is
we're
going
to
create
the
deployment
again.
We're
always
doing
this
in
the
namespace
I'd
like
to
make
to
point
that
out
that
it's
always
good
to
ensure
that
you
use
the
namespace
command
so
you're
by
default.
If
you
don't
use
the
namespace
command,
what
this
will
do
is
it'll
put
it
in
the
default
namespace
and
you
don't
want
their
applications
running
in
the
default.
Namespace.
B
B
Missed
one
little
piece
here,
one
of
the
things
that
you're
going
to
need
to
do
is
you're
gonna
need
to
get
the
mini,
cube
IP,
and
this
will
tell
you
the
IP
that
your
local
mini
cube
is
running
on
you'll
need
that
to
be
able
to
get
into
the
cluster
I
actually
missed
another
piece
as
well:
I
apologize,
one
of
the
things
I
showed
you
in
that
deployment
was
the
we
were
using
a
node
port.
So
what
do
you
have
to
do
here?
B
B
Just
like
that,
we
now
have
Jenkins
running
in
kubernetes,
so
we're
gonna
move
to
the
next
part
of
the
demo.
One
of
the
things
that
I
wanted
to
show
you
in
the
code
that
we've
created
in
the
docker
file
I
have
already
pre-installed
some
plugins
and
one
of
those
plugins
you'll
see
I've
installed
is
I've
already
installed
the
proven
eTI's
plugin,
so
we're
gonna
go
ahead
and
get
kubernetes
plug-in
configured
recently
that
there
was
a
change
made
to
the
plug-in.
B
It
is
no
longer
in
the
global
configuration
so
for
this
plug-in
you'll
come
into
the
build
executor,
status
and
you'll
see
cloud
configure
cloud.
This
is
where
you
will
start
that
configuration
so
we're
going
to
go
ahead
and
add
a
new
cloud
which
will
be
kubernetes
we're
going
to
configure
this.
The
first
thing
that
we
need
to
do
is
we
need
to
add
the
kubernetes,
our
URL
for
the
kubernetes
URL.
We're
gonna
go
ahead
and
run
a
man
command
which
is
keep
CTL.
B
B
We
see
that
the
connection
is
successful.
The
next
thing
we
need
to
do
is
for
the
communication
in
the
kubernetes
cluster
to
be
able
for
the
Jenkins
control
plane
to
connect
to
the
Jenkins
URL.
We're
gonna
need
to
go
ahead
and
get
the
actual
IP
of
the
pod
that
is
running
Jenkins.
Oh,
that
will
just
be
a
few
commands.
B
B
And
8080,
so
where
are
we
Rossum
there?
We
now
have
our
Jenkins
set
to
communicate
with
the
coop
within
the
kubernetes
cluster
I'll
just
go
ahead
and
apply
that
and
we'll
move
to
the
next
thing,
which
will
be
the
app
configuring.
A
pod
template
will
add
the
pod
template
for
this
particular
one
I
am
going
to
give
it
a
name
of
inbound
agent
will
set
up
the
deep
the
details.
So
we
know
we
created
this
in
a
namespace
called
Jenkins.
We're
going
to
need
to
give
the
agent
an
actual
label
in
this
particular
demo.
B
B
B
B
Finally,
want
to
just
make
sure
that
I
set
every
agent
to
terminate
and
give
me
just
a
second
which
is
right
here,
and
what
this
allows
you
to
do
is
when
the
kubernetes
plugin
launches
an
agent.
You
have
the
ability
to
save,
keep
that
agent
or
to
terminate
the
agent
once
the
job
is
done
for
cost
savings.
I
want
to
make
sure
that
I'm
terminating
these
things
so
they're
never
running,
and
for
that
we
are
done
making
our
configuration
so
I
will
go
ahead
and
apply.
B
I
will
save
this
and
I'm
gonna
go
ahead
and
now
build
up
a
new
job.
So
I'm
gonna
do
a
very
generic
job.
Here,
I'm
going
to
call
this
demo
I'm
going
to
use
a
freestyle
project,
you
do
have
the
ability
to
use
pipelines
for
this.
For
this
particular
demo,
I
am
NOT
going
to
use
pipeline
for
future
demos.
We
do
have
some
coming
up
in
May,
one
what
I
will
be
doing
and
for
subsequent
demos.
Everything
will
be
in
a
pipeline
for
this
demo.
I
just
wanted
to
keep
it
as
generic
as
possible.
B
B
As
soon
as
I
can
spell-
and
it's
very
straightforward-
we
will
save
this
I'm
going
to
turn
auto
refresh
on
and
I
am
going
to
build
this
job.
The
first
thing:
you'll
notice
when
I
built
this
job,
that
it's
sitting
and
it's
waiting.
So
let's
come
back
here
and
let's
watch
that
agent
get
created,
so
you
can
see.
We
have
now
created
the
inbound.
B
B
B
So
what
did
we
learn
here?
Kubernetes
allows
for
a
robust
way
to
provide
jenkins
scalability.
It
allows
the
ability
to
run
many
more
built
plans
in
parallel.
It
also
allows
the
ability
to
automatically
replace
or
replace
corrupted
Jenkins
instances
and
a
spin
up
and
removes
agents
based
on
need,
which,
in
turn
saves
cost.
B
A
A
A
I'm,
not
sure,
okay,
so
what's
next
from
meetups,
it's
a
question.
I'd
work
in
private
and
Yael
briefly
answer
that,
if
you
don't
mark
mark
so
leap
on
a
series
of
meetups
right
now
we're
talking
these
speakers,
we
have
some
reviews.
Generally,
we
want
to
have
one
meet
up.
Maybe
every
two
weeks
we
have
one
meet
up
a
monster
from
excuse
day.
It
will
be
about.
B
A
Computational
SCOTUS
job,
they
said
for
jobs,
management
and
this
whole
three
issue
was
mentioned
in
bachata
multiple
times
so
stay
tuned
for
the
next
meetups
and
we
will
be
increasing
complexity.
We
will
be
doing
deep,
dives
moving
the
next
meetups,
so
there
will
be
a
lot
of
interesting
content
there.
We
hope.
B
A
B
Jenkins
X,
so
this
is
its.
This
is
Jenkins.
X
allows
for
a
very
good
ops
nature
when
I,
say
get-ups,
you
can
actually
create
your
pipeline
directly
from
a
get
repo.
This
is
more
native,
very
different.
Jenkins
X
also
offers
the
ability
to
spin
up
the
cluster
and
in
some
ways
that's
what's
so
super
awesome,
but
this
was
what
I
meant
for
this
demo
was
to
be
a
very
native,
no
no
tools
underlying
other
than
really
many
q
being
used.
A
A
It
can
do
a
lot
of
different
things
and
you
can
also
run
infirmities,
but
the
use
cases
at
the
moment
are
different,
but
we
can
probably
also
do
continues
deliberately
miss
Jenkins
Combinator's,
but
at
the
same
time
you
look
up
configure
a
lot
on
your
own
Jenkins
X
provides
many
features
out
of
the
box.
That's
correct!.
B
B
A
What
do
you
find
if
you
can't
hold
them
up
for
a
second
yeah?
That's
perfectly
fine!
Okay,
so
you
may
have
noticed
some
conversations
and
the
junk
is
convenient
that
we
actually
working
on
the
public
road
map
for
the
project.
So
this
roadmap
is
it's
just
a
draft.
It
works
a
lot
of
icons
and
we
will
be
putting
more
content.
A
Specific
Burnett
is
there,
but
one
talk
about
the
mutation
that
the
clinician
is
of
also
on
our
roadmap
and
right
now
we
in
the
process
of
discussing
items
we
would
like
to
put
there
and
no
cheating
if
you
open
the
mailing
list
associated
mr.
this
trait,
you
can
see
that
there
is
a
special
road
map
item
I
at
least
owe
Jenkinson
permettez
documentation,
which
would
a
lot
of
solution
pages.
A
C
B
Is
that
is
an
awesome
question
and
I
would
super
awesome
question?
So
why
did
I
choose
a
deployment?
This
was
mini
cube
and
a
deployment
really
works.
Well,
with
mini
cube.
Why
would
you
use
a
stateful
set
if
you're
doing
a
production,
Jenkins
deployment?
You
would
want
a
staple
set
in
not
a
deployment.
So
why
did
I
choose
a
deployment,
because
this
was
just
mini
cube
based
if
I,
when
we
do
future
demos
and
I
actually
show
spinning
up
a
cloud
environment
with
kubernetes
for
Jenkins
I
will
not
use
a
deployment.
B
I
will
use
a
stateful
set.
I
have
the
code
available
already
for
that
particular
demo,
where
it
will
be
a
stateful
set
and
ingress
controller,
ingress
object
and
things
of
that
nature.
Very
good
question,
but
again
for
development.
I
just
chose
to
use
a
very
simple
for
mini
cube
deployment,
ammo,
okay,
another.
B
B
You
do
have
the
ability
to
say
in
the
pod
retention
configuration
that
I'd
like
this
pod
to
stay
and
not
be
terminated,
and
then
you
can
run
multiple
jobs
on
there,
but
I
felt
that
for
the
for
the
demo
purpose,
having
the
pod
go
away
once
I
was
done,
served
a
more
better
purpose
than
leaving
it
there.
But
you
do
have
that
ability
in
the
configuration.
B
What
does
it
actually
mean?
So
the
what
what's
highlighted
on
the
screen
here
is
the
actual
location
of
the
Jenkins
inbound
agent.
So
what
I'm,
using
in
my
configuration,
is
the
location
for
that
I
chose
to
name
everything
for
the
name
of
the
pod
template,
as
well
as
the
label
inbound
agent,
just
sort
of
keep
everything
unified.
B
However,
you
can
choose
whatever
you'd,
like
the
only
thing
that
you
can't
you
should
not
delineate
from
is
the
image
that
you
use
for
the
pod
template
should
come
from
the
repo
that
is
on
the
screen
right
here,
and
why
is
that
that
has
the
jnlp
remoting
capability
in
there,
which
allows
the
agent
to
talk
back
to
the
two
Jenkins
and
you
need
that
communication.
So
that's
already
built
into
this
that
that's
why
we
use
this
image
yeah.
So
if.
A
A
B
A
B
Very
very
good
question,
so
the
first
thing
that
you
want
to
do
is
create
a
service
account
as
you'll
notice,
I
created
that
service
account
and
then
on.
The
second
part,
I
created
spa
resources
where
I
allowed.
What
that
service
account
can
do
so,
for
my
demo,
I
as
I
explained
I
did
everything
at
the
cluster
level
role.
If
you
want
to
be
more
secure,
you
should
never
do
anything
at
the
cluster
level
role.
B
You
should
always
do
it
at
the
namespace
that
way,
it
doesn't
have
the
ability
to
affect
any
other
namespace
in
that
cluster.
That's
one
piece
of
it.
The
second
thing
is
having
authentication
set.
When
you
talk
about
our
back
I
created
a
service
account
and
that's
internal
to
the
cluster.
It's
best
to,
if
you're,
going
to
use
internal
authentication
that
you
separate
everybody,
every
service
account
should
have
be
individual,
and
that
could
be
communication
within
that
are
back
for
the
er.
B
Your
cluster
or
your
cluster
role
should
be
specific,
that
you
know
what
it's
doing.
Finally,
I'll
say
in
terms
of
cluster
management
from
a
security
standpoint
having
auditing
turned
on
on
the
AP
of
cube.
Api
so
you're
able
to
see,
not
only
so
you
have
your
our
back,
you
know
what
you're
allowing
people
to
do,
but
to
also
be
able
to
log
and
monitor
what
people
are
doing,
and
to
do
that,
you
want
to
have
the
auditing
turned
on
and
in
future
demos
I
can
show
how
to
turn
that
on.
B
It's
really
really
easy
to
do,
and
then
you
can
use
a
whole
different
whole
set
of
tools
to
be
able
to
log
that
cube
a
cube
api's
to
see
what
auditing
but
to
see
what
people
are
actually
doing.
Are
they
trying
to
create
a
namespace,
even
though
they
don't
have
the
ability,
there's
also
other
open-source
tools
out
there?
That
will
alert
on
such
things
like
that
the
example
is
BALCO
is
a
tool
that
will
alert
when
your
certain
cube
auditing
is
it's
been
here.
Hopefully
that
answers
your
question.
B
A
You
there
are
some
other
questions
about
security
yeah.
So
if
something
wasn't
answered
in
the
chat,
okay
and
the
last
question,
we
had
a
in
the
list
before
to
go
to
the
chart.
If
my
pipeline
trigger
has
other
jobs
and
the
way
it's
cured
finished,
that
means
that
I
will
need
two
different
ports.
It's
possible
to
configure
deals
to
the
same
port.
Yes,.
B
So
in
that
lake,
in
the
configuration
of
the
pod
template,
you
can
specify
yeah
I'm
gonna
have
sort
of
a
serialized
I'm
in
a
daisy-chain
jobs
together
and
in
my
egg
my
example.
One
of
the
questions
would
ask
why
that
I
use
two
pods
as
opposed
to
one
there's
another
good
example
of
why
you
would
use
two
pods,
because
you
may
want
to
jobs
to
run
on
two
separate
pods.
So
you
do
have
the
ability
to
do
that.
A
B
This
particular
example:
I
used
an
empty
directory
which
it's
basically
putting
it
in.
You
know
I
think
I
specified
slash
10,
so
you
have
the
ability
to
do
that.
If
you're
using
a
cloud,
let's
say
you're
setting
your
kubernetes
cluster
in
a
cloud
infrastructure
and
you
have
Jenkins
running
in
there.
You're
gonna
want
to
set
the
saf3
WS
you're
gonna
want
that
on
some
a
persistent
volume
and
that
persistent
volume
fights
back
to
an
EBS
volume
and
then
their
data
is
getting
saved
on
the
EBS
volume.
B
So,
for
example,
if
your
Jenkins
I
don't
call
it
a
master,
I
call
it
a
control
plane.
So
if
your
Jenkins
control
plane
goes
down
and
then,
if
you're
using
a
stateful
set,
it
spawns
another
instance,
the
configuration
is
already
there
and
then
it'll
automatically
create
that
that
persistent
volume
claim
which
is
tied
to
for
a
good
AWS.
The
same
is
true
in
Google.
A
B
Environment,
you
can
set
the
max
number
that
you'd,
like
you,
can
be
as
many
as
one
you
can
do
as
minimum
as
one
or
you
can
set
I
only
want
50,
pods
I've
worked
in
some
organizations
where
we
have
jobs
that
will
spawn
many
many
more
jobs
and
with
that
I
think
at
one
particular
time
we
had
one
that
would
spawn
something
like
400
different
jobs,
and
we
have
that
ability
using
the
kubernetes
plugin
crazy.
But
it's
available
do
one
of
the
things
that
you
have
to
be.
You
have
to
be
mindful
of.
B
When
you're
spawning
agents
in
kubernetes,
you
have
to
make
sure
that
you're
not
taxing
the
cluster.
What
do
I
mean
by
that?
If
you
only
have
so
much
memory
and
CPU
on
that
cluster,
but
you're,
you
know
you're
spawning.
You
know
15
parallel
jobs
that
are
running
some
machine
learning
pipeline.
That's
it
you
could
bring
down
the
cluster,
so
it
really.
It
really
benefits
you
to
understand
what
you're
trying
to
do
in
terms
of
the
overall
cluster.
B
So
with
that
I
think
it's
always
good
to
have
requests
in
limits
and
I
would
also
strongly
suggest
that
anybody
that's
doing
this
and
thinking
about
doing
it
in
production,
I
would
think
about
not
only
a
namespace
level
requesting
limits
but
setting
a
cluster
wide
requesting
limits.
That
way,
you
know
that
if
somebody's
using
a
namespace
and
they're
spawning
a
none
good
like
a
massive
amount,
they're
not
gonna
bring
the
whole
cluster
down.
B
A
B
I
want
to
be
careful
when
I
answer
this
question,
because
I'm
one
of
those
people
that
likes
to
tinker
with
things
I
will
say
the
ability
is
there
to
do
it.
Yes,
you
can,
should
you
do
that
or
production?
No,
don't
do
that
for
production.
If
you
want
to
try
starting
off
with
dad
a
dad,
a
dev
environment
and
making
sure
that
you've
ironed
out
every
problem,
I
would
start
there.
B
Why
am
I
so
hesitant
to
say
yeah
go
ahead,
just
do
it,
because
the
the
inbound
agent
docker
image
has
been
tested
with
Jenkins
connectivity
in
mind.
So
that's
all
it
worries
about
when
you
start
to
try
to
do
something
different
in
there.
The
ability
to
ghost
I
call
it
going
south
or
go
astray
is
is
high
and
you
may
not
get
the
same
level
of
support
if
you
were
just
using
the
base
image
from
the
open
source
community
yeah.
B
A
Yeah
one
thing
which
was
mentioning
if
you
don't
want
to
extend
their
jinkies
official
images
on
your
own.
That
is
also
depository
Jenkins,
general
P
agents,
and
there
is
a
number
of
images
inside
and
one
of
the
images
since
we're
talking
about
Titan.
And
so
it
is
an
image
for
Python,
3
and
python
2.
And
you
can
see
that
this
image
is
well.
You
really
need
to
clean
up
the
Nemean,
but
it's
actually
based
on
the
official
inbound
agent
and
ingest,
install
additional
tools
and
the
network.
B
A
In
flight
that
work
is
in
flight
yeah,
we
don't
clean
it
up,
but
yes,
some
of
them.
We
just
saw
already
available,
and
you
know
there
are
common
use
cases.
We
could
provide
official
images
in
the
community
for
that
and
they
thought
you
can
easily
extend
them
because
it's
quite
easy
to
do
it.
Doctor.
B
So
when
you
do
the
migration,
what
I
would
strongly
suggest
doing
is
what
I've
done
in
other
companies
is
I
write
a
script
to
do
the
migration
I
don't
manually,
do
it,
especially
when
it
comes
to
I've,
dealt
with
a
lot
of
doing
EBS
volume,
migrations
and
that
can
be
super
super
complex.
It's
best
to
control
it
with
a
script.
What
are,
how
would
you
do
that?
Script
I
have
found
personally
that,
if
I
write
it
in
Python,
especially
using
AWS
I
can
use
the
photo
3
library,
it
makes
it
more
seamless.
A
B
You
can
yes,
depending
on
how
the
the
control
plane
is
configured.
One
of
the
things
that
I
would
strongly
suggest
doing
is,
if
you're
going
to
move
Jenkins
into
kubernetes
that
a
you
know
exactly
what
your
requests
and
limits
are
going
to
be
on
Jenkins
on
kubernetes,
so
understanding
what
the
jobs
are,
that
you're
going
to
run,
how
you
really
have
to
start
doing
a
tree
of
decisions
on
how
you
set
your
requesting
limits
up,
but
I
have
seen
it
become
a
problem.
The
problem
has
been
rectified
by
setting
the
request
in
limits
and.
B
A
great
question,
and
it's
one,
that
a
lot
of
people
struggle
with
so
I
will
tell
you
the
different
ways
that
I've
done
it.
Production-Wise
I've
used
three
different
ways.
The
first
way
would
be
having
a
general
sort
of
script
and
the
script
will
just
go
in
a
you
know:
copy
up
a
full
directory
tar
it
up
and
put
it
somewhere.
That's
one
way
to
do
it.
The
second
way
to
do
it
is
there's
a
lot
of
plugins
that
you
can
use
one
of
the
most
widely
used.
B
Plugins
is
a
plug-in
called
thin
backup
and
then
so
then
backup
gives
you
the
ability
to
set
a
cron
like
schedule
and
control
what
you
want
to
backup.
You
may
just
want
to
backup
your
jobs
directory.
You
may
just
want
to
backup
your
jobs
directory
in
your
credentials
file.
You
may
want
to
backup
the
whole
ball
of
the
whole
thing,
and
that
that
you
have
that
flexibility
to
use
the
thin
backup
I
have
used
that
thing
back
up,
especially
in
conjunctions
with
s3.
B
So
you
can
write
a
script
that
will
you
know
the
job
runs
on
thing.
Backup
you'll
have
a
script
that
will
go
grab
that
what
so,
how
does
think
back
over?
Let
me
take
a
step
back
then
backup
will
go
based
off
of
your
configuration
in
your
schedule
and
will
grab
everything
and
zip
it
up
once
it's
done
with
the
zipping,
it
will
actually
then,
after
a
certain
amount
of
time,
will
tear
it
up
and
make
it
an
archive.
You
can
then
clean
that
up,
so
what
I
have
done
in
the
past
is
I.
B
Had
a
I
had
a
script
that
will
go
through,
it
knew
the
schedule
to
run
so.
If
I
said,
I'm
gonna
take
a
backup
every
day
at
1:00
a.m.
it
knew
I'm
gonna
run
every
day
at
1:15
a.m.
I'll.
Take
that
zipped
file,
I'll
tar,
it
and
I'll
put
it
in
s3
and
then
I'll
send
out
an
email
saying
your
backup
was
successful.
If
the
job
fails.
B
B
There
is
a
especially
if
you're
in
kubernetes
again,
these
are
all
open
source
tools
that
you
can
use.
But
if
you
wanted
to
back
up
your
kubernetes,
you
there
is
a
tool
out
called
Valero
and
Valero
will
allow
you
to
back
up
full
name
space
items
that
includes
EBS
volumes.
Let's
say
if
you're
using
AWS,
so
that's
a
cool
tool.
Yet
there
you
go
Valero
backed
up.
This
was
a
tool
I
forget
who
put
this
tool
out
originally
I
want
to
say
it
was
hep
deal,
but
I
always
messed
that
up,
but
I
use.
B
A
B
A
C
A
B
I
raised
the
animals
in
my
KS
cluster.
It
means
it
created
a
storage
claim
towards
that.
Okay,
so
one
of
the
things
that
I
would
suggest
not
doing
is
using
this
demo
for
a
cloud,
because
this
is
more
meant
for
local
device.
Local
development.
It's
not
meant
to
use
what
you're.
What
you're
referring
to
me,
Raible
Eve,
is
it's
called
a
volume
claim
template
I
what
I
have
code
and
I
was
gonna,
save
it
for
another
presentation,
but
essentially
what
happens
is
is
one
of
the
earlier
questions
is.
B
Why
did
you
use
a
deployment
over
a
stateful
set
in
a
stateful
set
when
I
would
build
something
in
a
cloud?
The
staples
that
gives
me
the
ability
to
use
something
called
a
volume
claim
template
and
what
the
volume
claimed
template
now
do
is
what
you're
saying
there.
It
will
not
track
your
file
system
and
then,
when
that
pod
goes
away.
Let's
say
your
control
plane
for
Jenkins
goes
away
and
responds.
B
B
But
to
answer
your
question
here,
what
you
want
to
use
is
for
that
type
of
a
deployment
is
a
stateful
set
that
has
a
volume
claim
template
setup
with
that
I
I'll
I,
don't
want
to
put
the
code
out
there
yet
because
I
feel,
given
the
code
without
explanation
will
create
more
questions
than
I.
Think,
should
you
know
it
would
be
fair
to
the
person
wanting
to
use
it.
B
I
will
say
that
in
a
very
soon
presentation,
coming
up,
I
will
be
doing
this
very
same
demo,
but
on
a
cloud
infrastructure
that
will
use
a
stateful
set
with
the
volume
claim
template
and
in
there.
If
you
want
to
ping
me
offline
I
can
help
walk
you
through
setting
that
up
I'd
be
more
than
happy
to
do
that.
To
get
you
sort
of
moving
in
the
right
direction.
B
A
B
Personally,
I,
don't
think,
there's
anything
wrong
with
it.
One
of
the
things
that
I'll
say
that
may
create
complexity
is
now
you
have
to
track
how
that
sidecar
is
going
to
communicate
all
the
permissions
through
that
it
also
becomes
an
attack
vector.
So
if
you
have
that
sidecar
running
and
it
has
certain
level
privileges
that
could
be
a
problem,
you
have
now
allowed
that
in
a
production
level,
environment
I
would
say
that
sidecars
are
extremely
beneficial
if
they
are
built
in
such
a
way
that
security
was
in
the
forefront
of
your
design.
A
B
Yeah
we
could
take,
we
could
take.
We
could
take
a
few
more
told
me,
I,
told
me
hold
on
I
saw
you
turn
your
camera
on,
and
I
I
want
to
answer
your
question,
but
I
just
want
to
get
to
one
person's
before
yards
and
I'm.
Just
trying
to
find
it
Bala
asked.
Is
there
a
way
to
recover
a
deleted
job
in
Jenkins,
so
the
beauty
of
of
recovering
a
deleted
job?
Is
that
config
dot
XML?
B
If
you
still
have
the
volume
available,
you
then
have
the
ability
to
recover
that
deleted
job.
It
would
mean
that
you
would
need
to
do
sort
of
a
restore
there
and
I've
seen
various
ways
to
do
this,
but
one
of
the
most
easiest
ways
to
do
it
would
say
my
EBS
volume
it
has
my
job's
directory,
which
has
the
config
dot
XML.
Even
the
next
build
number,
and
all
of
that
things.
All
you
would
need
to
do
is
is
a
there's.
A
Q
CTL
command.
That'll.
Allow
you
to
copy
over.
B
B
Your
question
was:
will
this
be
published?
Is
that
right,
yep?
Okay?
Yes,
this
will
be
published.
Obviously
we
have
to
go
through
and
do
some
clever
editing
because
we
got
zoom
bombed.
But
yes,
this
will
be
published
to
the
Jenkins
YouTube
I
think
we
do
I
think
we
have
a
jam
playlist.
But
if
you
go
to
youtube
you
look
up.
Jenkins
you'll
see
a
chance
of
actual
subscription.
An
actual
link
to
the
Jenkins
that'll
have
a
playlist
that
you
can
you
can
subscribe
to,
and
this
will
be
there.
B
A
So
yeah,
you
can
see
my
terrible
video
choices
right
now,
but
yeah.
What
I
wanted
to
show
you
that
it's
official
channel
and
there
is
a
lot
of
playlists
away-
a
publish,
actually
everything
so
not
only
online
meetups.
We
also
have
special
just
do
the
meetings
and
other
topics.
So
if
you
want
to
participate
in
our
wider
community
and
see
what
happens,
you
see
some
demos
or
work
and
progress
stuff?
You
can
go
here
and
his
junk
is
online
with
a
playlist,
and
this
way
we
will
get
it
posted
some
I.
B
B
We
need
that
more
than
ever.
So
please
don't
hesitate
to
ping
me
to
say
hi
to
me
if,
when
conferences
start
again,
if
you
ever
see
me
come
up
I'm,
a
very
approachable
person,
I
will
say:
I'm
super
identifiable
because
I'm
the
only
guy,
that's
tattooed
all
over
the
place.
So
don't
think
I'm
scary
or
on
please
talk
to
me
message
me
I,
love
to
hear
from
people.
B
A
A
Thank
you
so,
just
to
whomever
is
interested
to
see
more
content
about
Jenkins
and
kubernetes.
The
next
step
is
actually
next
Tuesday
4:00
p.m.
UTC,
and
we
will
have
Nicole
I
hope
they
will
talk
about
running
jenkins,
fully
configured
test
code
is
job,
is
LJ
cast
and
helm
three,
and
the
welcome
to
join
this
session.
So
looking
forward
to
meet
you
there,
yeah
thanks,
so
I
will
stop
the
recording
I
finally
find
this
button.