►
From YouTube: Online Meetup: Jenkins Operator for Kubernetes
Description
Tomasz Sęk from VirtusLab shows how to manage Jenkins in with the Jenkins Operator for Kubernetes: https://github.com/jenkinsci/kubernetes-operator. This is a recording of the Jenkins Online meetup on May 11, 2020.
In presentation Tomasz will explain how operator pattern helps to manage Jenkins in Kubernetes. We will take a look at the operator pattern and its use cases. A closer look at the Jenkins Operator will show the operator pattern in practice. Then we will go through day-to-day operations automation that the operator provides like deployment, configuration and repair of a Jenkins instance. After this presentation you will know how a non-cloud native application can be run in an immutable, scalable and secure way.
* Slides: https://github.com/jenkinsci/kubernetes-operator/blob/master/assets/Jenkins_Online_Meetup-Jenkins_Kubernetes_Operator.pdf
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/270363389
* Q&A: use the project's chat: https://github.com/jenkinsci/kubernetes-operator#community
A
Hello,
everybody,
my
name
is
Tomas
sang,
I'm
cloud
engineer
at
Vitas,
lab
I
work
with
AWS
and
Azure
on
my
daily
basics:
I'm
maintainer
of
kubernetes
distribution
for
one
of
our
clients.
These
days,
I
must've
write
software
in
da
lang
and
infrastructure
as
code
in
terraform.
So
let
me
tell
you
a
story:
there
will
be
a
dragons
and
the
epic
fights
and
once
upon
a
time
there
was
a
Jenkins
snowflake
and
no
one
knew
how
it
worked.
A
The
Jenkins
has
been
deployed
manually
on
random
ec2
instance,
but
some
one
person
that
was
no
longer
working
at
the
company
we
didn't
have
full
control
over
it.
There
was
no
jenkees
admin
credentials
and
no
assist
key
SSH
keys
to
the
instance.
Everyone
just
closed
the
fingers
very
continuing
to
work.
In
the
meantime,
our
team
of
four
heroes
was
sent
to
kill
this
beast.
A
There
were
various
problem
to
solve.
The
Jenkins
version
was
very
old
and
and,
as
consequence
not
secure,
it
was
running
and
on
top
of
infrastructure
built
by
hand,
as
was
nearly
impossible
to
recover
Jenkins
home
directory
and
the
result,
its
backup
was
huge.
The
agents
didn't
automatically
scaled.
The
number
of
builds,
so
it
was
either
wasting
resources
or
not
having
enough
enough
of
them.
A
A
Fortunately,
there
was
still
no
outer
scaling
and
too
many
things
were
done
by
hand.
As
a
bonus,
we
gained
new
problems
with
terraform,
State
inconsistency
and
unstable
scripts
that
were
hard
to
write
so
enter
the
kubernetes.
The
team
of
four
met
a
wise
druid.
He
told
them
about
magical
artifact
called
kubernetes,
so
they
went
on
a
quest.
The
challenge
was
to
assemble
all
the
pieces
together.
A
A
A
So
hive
driven
development
right
again
with
ham
2.0,
it
was
supposed
to
make
things
easier,
spoiler
alert
it
didn't.
There
is
a
whole
article
written
by
my
colleague
about
it.
A
little
is
thinking
twice
before
using
help
2.0
should
be
have
so.
This
solution
was
more
complex
but
solve
more
problems.
Out
of
scaling
and
same
healing
were
now
available,
so
recovery
was
almost
automatic.
A
A
A
Managing
Jenkins
is
complex
and
automating.
It
makes
things
10
times
harder
to
properly
express
the
domain
itself
necessary
to
use
real
programming
language,
a
golang
with
the
operator
pattern,
where
the
answer
operator
is
a
program
that
controls
whole
lifecycle
of
another
program.
So
in
this
case
we
have
BOTS
running
in
kubernetes
managed
through
various
api's,
so
the
operator
is
kubernetes
native
its
rounds,
a
separate
software
and
has
application
specific
knowledge
and
extends
kubernetes
api
with
custom
research
definition
mechanism.
A
A
A
The
operator
compares
the
actual
state
with
the
desired
state.
The
difference
is
the
number
of
replicas
operator
updates
the
stateful
set
to
adjust
the
replicas
number.
Then
the
kubernetes
tasteful,
set
controller
deletes
one
kafka.
Pod
operator
framework
helps
to
build
operator,
especially
the
SDK,
with
operator
SDK.
You
can
bootstrap
a
new
operator
even
if
five
minutes,
then
you
can
go
straight
into
design.
Your
custom
custom
result
definition.
A
Next
steps
would
be
to
implement
the
control
loop
and
start
watching
some
resources
operator.
Sdk
encourages
a
specific
deployment
flow.
So
after
building
the
foundation,
we
start
the
infinite
loop
of
local
test
end
to
end
test
and
publishing.
The
end
result
is
a
set
of
manifests
and
the
container
image
operator
framework
also
provides
operative
lifecycle
manager.
It
can
be
used
to
deploy
operator
to
clusters
at
scale
operator,
lifecycle
manager
uses
class
catalogs
as
the
source
with
operators
the
biggest
cluster
catalog.
Is
the
operator
hub
that
IO.
A
A
Now
is
the
time
for
the
final
battle.
Also
we
on
the
one
side,
we
have
a
dragons
and
the
other
side
we
have.
The
Fellowship
of
the
operator,
as
you
can
see,
logo
of
the
Jenkins
operator
is
combined
from
four
different
loggers,
so
the
blue
guy
is
the
goofer
is
the
mascot
of
the
golang
programming
language.
The
suit
comes
from
the
Jenkins,
the
kubernetes
logo
can
be
seen
on
the
plate
and
the
grand
V
is
like
Vitas
love,
my
company
and
as
Alex
showed
us
before.
A
A
A
A
The
user
phase
is
responsible
for
applying
all
of
the
users
configuration
so
the
base
face
and
when
we
successfully
run
all
base
configuration
groovy
scripts
using
Jenkins,
API,
oh,
and
also
we
do
a
lot
of
more
stuff
example
with
plugins
and
and
so
on,
the
user
face
and
when
all
of
the
user
configuration
has
been
applied
and
backup
works
with
for
the
Jenkins
job,
history
and
artifacts.
Only
so,
let's
go
through
some
Jenkins
custom
resource
examples.
A
B
A
A
A
A
C
A
A
A
A
A
A
A
A
Another
feature
is
notifications,
integration
with
multiple
providers,
starting
with
kubernetes
events,
email,
slack,
Meagan
and
Microsoft
teams.
It
will
allow
for
better
visibility
of
the
Jenkins
state
to
the
users.
The
most
important
events
will
be
broadcasted
to
the
configured
providers,
with
the
count.
Good
logging
levers.
A
A
A
So,
first
of
all,
we
have
to
create
the
kubernetes
nice
place
called
Jenkins.
Then
we
applied
the
the
Jenkins
custom
resource
and,
as
you
can
see,
on
the
screen
after
applying
the
operator,
create
a
bunch
of
kubernetes
resources,
including
pod,
with
Jenkins
masters,
two
services,
one
for
HTTP,
one
for
for
agent
service,
account
secrets,
config,
Maps,.
A
A
So,
as
you
can
see,
the
base
configuration
phase
is
complete
and
the
user
configuration
phase
is
complete
because
I
didn't
specify
any
custom
think
so
took
the
same
time
as
the
base.
So
when
you
see
this
in
logs,
that's
mean
you're
drinking
is
free,
fully
operational
and
you
can
look
to
the
junkies.
A
So
I'm
using
the
password
extracted
from
the
sacred
secrets
area
and
as
you
can
see,
there
is
no
warnings.
There
is
no
warnings
on
the
plugins
or
plugins
are
up
to
date
and
now
I'm
going
to
configure
something
manually,
because
the
Jenkins
created
by
the
operator
is
immutable.
What
does
it
mean,
for
example,
if
I
change
something
manually
like
this,
so
I
now
I'm
changing
the
master
executors
to
one?
If
I
will
lead
this
part,
this
change
will
punish.
I
will
see
you
I
will
show
you
in
a
second.
A
And,
as
you
can
see,
another
plot
is
running
so
I
cut
the
video
to
speed
up
the
the
presentation
and,
as
you
can
see
again
and
the
operator
applies,
the
base
configuration
with
groovy
scripts
and
user
face
is
complete,
so
Jenkins
you
can
log
into
the
Genki.
So
let's
refresh
the
website
and
as
you
can
see,
there
is
no
job
which
I
created
previously
and
during
that
cue,
the
build
executors
set
to
zero.
A
A
So
now
I'm
going
to
apply
the
I
will
modify
the
Jenkins
custom
resource
with
all
the
stuff
like
I
mentioned
previously.
So,
as
you
can
see,
I
configured
the
notification
for
the
slack
and
operator
gives
me
information
that
something
has
changed
in
the
configuration.
So
it's
going
to
restart
the
Jenkins
master
pot.
So
now
it's
creating
the
Jenkins
master
Potter.
A
A
We
use
the
same
trader
shell
as
before
and,
as
you
can
see,
the
scheme
desking
has
changed.
We
have
we
set
the
system
message
from
the
configuration
is
called
plug-in.
We
said
master
executors
from
the
groovy
scripts
and
we
set
the
seed
job
which
creates
that
creates
three
different
jobs
so
to
showcase
the
backup
resource
feature
I'm,
going
to
run
this
build
the
kubernetes
plugin.
A
A
A
And
now
we
stream
anything
because
I
said
only
echo
hello
world
there.
So
we
run
this
job
successfully
and
we
have
one
built
in
this
job
so
now
I'm
going
to
delete
the
Jenkins
master
part
and
after
recreate
the
Jenkins
master
pod.
This
job
history
should
be
resisted
because
we
call
we
configured
the
backup
and
restore
feature.
A
And
now
I'm,
going
to
edit
D
the
config
map
with
Ruby
scripts
and
I
want
to
change
the
amount
of
master
executors
example.
I've
been
changed
to
something
which
is
not
should
be
not
done
and,
as
you
can
see,
we
get
notification
from
the
Genki
separator
in
the
in
the
in
the
slack
that
tried
to
run
this
groovy
script
and
it's
encourages
some
error
and
you
can
see
start
rise
because
we
said
the
verbose
mode
for
the
notification
feature.
A
A
C
A
A
Now
I
want
to
show
you
the
the
the
github
repository
as
I
said
like
earlier.
We
have
community,
so
you
can
join
our
slack,
feel
free
to
just
come
and
say
hi
and
ok.
This
project
is
bad
or
good
grades.
So
it's
up
to
you
so
also
we
have
community
call
of
every
Thursday
on
Google
needs,
so
you
can
talk
to
us
person
as
some
questions.
Maybe
you
have.
A
Basically,
we
can
gather
some
feedback
from
you
do
to
make
this
better
for
the
other
users.
We
also
in
the
gift
Cup
have
project,
so
you
can
see.
What's
going
on
in
the
project,
was
a
project
in
progress
right
release
and
what
is
closed?
Maybe
we
can
change
the
priority
of
the
issues.
So
if
you
have
some
issues,
please
please
feel
wronged.
So
we
can
have
discussion
for
it.
Also,
we
have
a
website
for
the
Jenkins
operator.
We
have
nice
documentation
there.
If
you
see
some
gaps,
you
can
just
feel
the
issue.
A
We
will
try
to
make
this
better
and
nice
think
you
can
is
the
schema
for
the
Jenkins
CR.
So
if
you
have
problems
with
the
avaya
Dacian,
you
don't
know
it's
possible
or
not.
You
can
just
look
at
click
on
the
link
and
see
ok,
so
the
back
up
looks
like
this
and
what
the
Philips
I
need
to
field.
Basically,
ok,
so
that's
all
for
me
and
I'm
waiting
for
the
questions
for
from
you
guys.
B
Thanks
so
much
for
the
presentation
for
participants
again
cliche
your
feedback
in
the
Google
form.
We
will
really
appreciate
that
because
it
will
help
us
to
improve
the
meetups
and
we
also
feedback
astonish,
also
appreciate
that
and
let's
go
through
some
questions.
We
answer
some
a
synchronously,
but
we
still
have
some
on
the
list.
B
A
Yes,
so
in
our
roadmap
we
want
to
first
of
all
focus
on
the
refactoring
and
as
an
improvements
and
refactoring
means
that
we
want
to
split
the
user
face
into
a
few
custom
research
definition
as
user
asked
at
this.
So
this
will
be
done
in
the
near
future,
because
we
face
that
the
Jenkins
custom
resource
now
is
huge.
We
want
to
make
it
late
light,
basically
yeah.
So
this
is
the
answer.
We
will
do
that.
A
B
B
A
A
On
my
list,
I
have
to
deployed
new
version,
one
point
4.0
which
have
more
discs
this
compatibilities.
For
example,
I,
don't
remember
everything
from
the
list,
but
this
one
from
seamless
upgrades.
So
it's
in
zero
point.
Four
point:
zero
is
available,
so
we
will
update
this
when
we
will
update
the
tracker,
hop
dot,
IO
catalog
for
deterring
separator.
B
A
A
Be
careful
because
the
Jenkins
operator
also
needs
to
apply
this
configuration
for
the
Jenkins
API,
so
you
have
to
give
to
the
Jenkins
operator
account
admin
permission
in
this,
for
example,
LDAP
or
or
out.
It
is
up
to
you
what
do
you?
What
do
you
want
to
you
to
be
able
to
apply
those
configuration
for
you
without
that
operator,
won't
be
able
to
configure
your
Jenkins.
B
A
Want
to
add
to
this,
because
we
also
talked
about
the
authorization
method
for
the
Genki
separator
to
the
Jenkins
and
I
think
we
have
to
extend
this
model,
because
now
we
have
two
strategies-
and
we
have
to
add
more
to
to
the
basic
user,
can
define
all
this
authorization
and
authentication
mechanism
delivered
by
the
plugins
in
the
Jenkins.
So
it
will
be
improved
in
the
future.
B
A
C
A
You
don't
know
what's
going
on
if
the
backup
has
been
restored
successfully
or
there
is
some
problems
with
scaling
or
screens
down.
So
you
don't
know
if
your
Jenkins
is
running
or
not,
but
with
the
operator
it
keeps
configuration
the
drinking
running
all
the
time,
so
it's
checking
okay.
This
is
okay
check
and
move
to.
Another
list
have
to
have
to
check
so
with
the
junkies
you
have
more,
you
can
be
more.
A
So
you
can,
you
can
knew
that
your
drink
is
running
basically.
So,
if
the,
if
something
is
going
wrong,
the
Jenkins
writer
can
send
a
notification
to
you
that
okay,
something
is
wrong.
I
can
do
something,
so
you
have
to
check,
but
but
with
the
hand
job
you
don't
know
what
the
status
of
the
Jenkins
is.
B
A
So
Karen,
so
we
set
the
Jenkins
master
executors
to
zero
for
the
security
reasons,
so
everything
should
be
run.
The
kubernetes
plugin
as
a
separate
pot
under
the
need,
so
so
that
that
does
the
Astor.
Please
we
thought
about
something
like
managing
agents
by
the
operator
and
connect
them
to
DJ
Kings,
which
is
configured
by
it
by
the
operator.
So
so,
for
example,
we
have
some
kinds
of
use
case,
so
we
have
four
Scala
SBT
and
it
has
to
be
run
for
some
part
of
time
had
to
be.
A
Too
fast
compiled
things
and
with
the
kubernetes
plugin
you,
you
run
the
agent
as
you
run
the
build,
and
you
don't
have
this
opportunity.
So
we
thought
about
some
kind
of
static
engine,
but
this
is
not
easy,
but
it's
doable
to
you
in
operate.
So,
for
example,
we
can
extend
and
create
separate
custom
research
definition
for
major
managing
the
Jenkins
agents.
Basically,.
B
A
A
There
is
how
how
the
jenkees
works,
so
you
have
one
master
and
everything
is
down
by
side
and
making
this
high
availability,
for
example,
spin
two
of
them-
it's
not
easy,
so
we
have
talks
about
it,
but
basically
it's
not
easy
to
do
that.
Basically,
if
we,
if
we,
we
know
how
to
do
that,
we
first
you
will
implement
this
to
make
the
Jenkins
be
more
available
for
the
users.
B
A
So
this
my
answer,
I,
don't
know
if
how
the
process
is
and
what
we
can
gain
what
we
have
to
do
to
to
to
join
DC
and
CF.
There
is
I
know
there
is
some.
You
have
to
example.
There
is
some
checklist
and
you
have
to
make
all
this
all
these
things
from
the
list
before
you
can
join
with
this
project.
Yeah.
B
So,
just
to
clarify
the
column
state
from
the
Jenkins
governance
that
point
Jenkins
project
itself
is
a
part
of
continuous
delivery
foundation
and
continues.
Delivery
foundation
is
also
part
of
Linux
Foundation.
So,
basically
we
have
a
lot
of
communications.
We
see
in
CF,
but
Jenkins
itself.
It's
a
in
another
foundation
regarding
James
Cooper,
not
separator
right.
Now
it's
formally
donated
to
the
Jenkins
project,
but
in
the
future
its
evolution
may
really
depend
on
how
project
goes
forward.
B
A
So,
as
you
can
see,
the
presentation
I
use
the
the
official
Jenkins
image
LTS,
so
we
don't
build
some
custom
docker
image.
I
know
there
is
some
practice
with
break
some
plugins
in
the
docker
image,
so
it's
possible
from
in
the
in
the
operator,
but
a
not
so
basically
it's
up
to
the
user.
How
to
how
to
how
to
want
to
do
that?
Basically,
so
we
from
our
perspective,
we
have
to
do
everything
that
we
put
in
the
Jenkins
er,
so
install
plugins
and
whatnot.
A
B
A
Course
you
can
have
multiple
instances
of
the
Jenkins,
as
you
have
multiple
instances
of
the
Jenkins
ER,
so
one
good
practice.
We
learned
that
it's
good
to
have
one
Operator
for
one
rankings,
because
in
the
operator
you
have
a
lot
of
information,
the
locks
or
D
notifications.
So
it's
make
the
work
easier
when
you
have
an
operator
and
one
Jenkins,
but
for
example,
if
you
have
another
nice
space,
you
can
deploy
another
operator
with
another
junkie,
so
it
would
work
physically.
A
This
V
1
alpha
to
eat
I
know
it's
maybe
can
be
confusing
the
users
that
changing
version
for
the
customers.
Definition
is
painful
in
the
kubernetes
because
you
have
to
somehow
translate
one
version
to
another.
So
the
version
one
supports
v1
file,
2
and
version
2,
suppose
V
1,
alpha,
3
or
whatnot,
and
you
somehow
you
have
to
or
manually
change
the
the
Jenkins
custom
resource
and
we
for
now
don't
have
tool
which
will
automatically
detect
that,
for
example,
we
run
teaching
a
perturbation
to
and.
A
Jenkins
customer
resource
API-
and
this
occurs
only
one
in
the
past,
so
we
have
to
change
some
map
from
the
list
and
this
breaking
chance.
So
we
have
to
introduce
the
new
version
and
it
doesn't
mean
that
it's
not
production
already.
Our
customer
runs
this
in
the
production
successfully.
So
don't
look
at
it.
B
A
A
B
Ok,
thank
you
thanks.
So
much
to
the
presentation
and
thanks
to
all
who
ask
questions
during
this
Meetup
and
looking
forward
to
seeing
the
drink
is
coming
in
just
a
quick
heads
up.
We
have
a
next
meetup
on
Friday,
so
mark
you
will
be
talking
about
securing
Kyojin
concisely
continue,
but
one
is
untrue.
So
Marky,
would
you
like
her
to
quickly
introduce
it
before
we
close?
B
C
Can
everybody
hear
me:
okay,
yes,
hello,
everybody!
We
will
be
demoing
the
Jenkins
pipeline
plug.
Excuse
me.
We
will
be
demoing
the
anchor
scanning
Jenkins
plug-in,
which
will
allow
you
to
scan
items
within
your
job
items
being
docker
containers
and
then
get
alerting
for
that.
It's
very
in
line
and
it's
a
really
awesome
tool
to
use
for
dev,
stepa,
deb,
SEK
hops,
and
that's
what
I'll
be
presenting
look
forward
to
seeing
everybody.