►
Description
Presenter: Nicolaj Græsholt, Continuous Delivery and DevOps Consultant and Trainer from Eficode Praqma. You have Jenkins running in production, but would like a better way to manage it, e.g. so Kubernetes can manage it for you. Fortunately all the building blocks have already been made by the Jenkins community, but there are many elements that you need to get right. Nicolaj will show you how you can go from a completely manually configured Jenkins master to an everything as code setup in Kubernetes.
You will see how this can be achieved using JobDSL, Pipeline, JCasC and Helm3 and after this talk you'll get access to all the examples and be able to convert your Jenkins to a configuration as code setup!
Agenda:
- From a job configured through the UI to code, instantly with JobDSL
- Configuring your Jenkins with JCasC
- Installing your new Jenkins on Kubernetes with Helm3
Links:
* Slides: https://github.com/figaw/configuration-as-code-jenkins-k8s/blob/master/configuration-as-code-jenkins-k8s.pdf
* Demo repository: https://github.com/figaw/configuration-as-code-jenkins-k8s
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/270042451/
* Offline Q&A: #jenkins-ci chat in the Kubernetes Slack
A
I
am
so
thrilled
to
be
here.
Thank
you
very
much
for
having
me
so
this
talk
is
called
configurations
code
of
Jenkins
for
kubernetes.
My
name
is
Nikolai
castled
I
am
a
DevOps
consultant.
I
work
for
F
occurred
previously.
Pragma
I
help
our
customers
with
Jenkins
and
I.
Do
darker
and
kubernetes
trainings
and
I'm
a
certified,
kubernetes
administrator
and
I.
A
Absolutely
love
a
good
documentation,
examples
and
proof
of
concepts
and
creating
those
and
when
I
say
love,
that's
not
an
overstatement,
because
most
of
or
all
of
what
I'm
going
to
show
you
here
today
is
actually
stuff
that
I
have
created.
In
my
spare
time,
M
and
I
have
opened
my
DMS
on
Twitter.
So
please
be
nice.
But
if
you
want
to
talk
about
Dora
or
kubernetes
or
Jenkins
and
configurations
code,
then
please
just
send
me
a
message.
Please
don't
make
it
helpdesk
e
their
questions,
but
all
right.
A
About
this
talk,
don't
panic.
Some
of
it
is
going
to
look
a
bit
complex,
but
so
the
complex
part
was
creating
the
examples
and
figuring
out
how
to
do
it,
and
luckily,
for
you,
I
have
already
made
all
the
examples
and
you're
going
to
get
all
the
examples,
and
so
you
can
also
just
sit
back
and
relax.
You
don't
have
to
take
notes
off
of
the
slides.
There
is
a
repository
that
you
will
get
afterwards.
You'll
get
the
slides
afterwards,
so
yeah
just
enjoy
the
show
great
so
story
time.
A
So
my
story
starts
with
kubernetes,
because
kubernetes
is
the
most
interesting
thing
in
the
world
and
of
course,
I
want
to
get
involved
with
it.
So
I
wanted
I
had
a
lot
for
Tucker,
so
kubernetes
came
naturally
to
me
afterwards.
So
darker
for
containers
and
kubernetes
for
container
orchestration
and
I
wanted
to
become
a
certified
kubernetes
administrator,
because
I
wanted
to
work
with
this,
and
so
the
customers
would
hire
me
to
do
their
kubernetes.
A
A
So
I
did
my
initial
commit
almost
two
years
ago.
Well,
actually,
a
bit
over
two
years
ago,
the
the
third
of
April
and
a
month
later,
I
passed
the
certified
communities
administrator
exam
that
was
nice,
but
I
wanted
to
continue
working
on
this
project
and
I
also
had
a
job.
I
have
a
co-op,
so
I
needed
some
help
with
this
project.
A
To
get
this
going
so
I
hired
the
nice
Butler
Jenkins
running
in
Tucker
I
started
creating
my
jobs
for
my
workflows
by
clicking
around
in
the
UI,
but
that
quickly
became
tedious
to
have
backups
off
so
I
created
my
jobs
as
code
I,
converted
them
and
afterwards.
So
I
was
still
packing
up.
My
Jenkins
home
folder,
so
I
configured
my
Jenkins
with
configuration
as
code
and
lastly,
I
installed
it
with
helm
into
kubernetes.
So
I
had
everything
running
in
kubernetes
and
could
manage
it
in
the
same
place.
A
So
the
agenda
in
three
pieces:
configuring
jobs
as
code
configuring
Jenkins
as
code
and
running
our
awesome
Jenkins
in
kubernetes
in
the
end
so
step
one
configuring
our
jobs
as
code.
So
why
do
we
want
to
do
this?
Well,
we
want
the
easy
reconfiguration
right
we
don't
want
to
have
to.
If
we
lose
our
Jenkins
instance,
then
we
have
to
click
around
in
the
UI
and
recreate
our
jobs.
A
It
would
be
nice
if
we
just
had
the
specifications
and
could
just
load
them
in
to
Jenkins
our
backups
become
lighter
as
well,
because
we
don't
take
copies
of
our
job
folders
and
with
all
of
our
content
in
it.
We
just
take
a
copy
of
the
configuration
of
our
job
and,
lastly,
I
have
my
configuration
under
version
control,
so
I
can
see
who
changed
what,
when
and
from
which
value
so
I
have
the
traceability
of
who's,
making
changes
to
my
workflows.
A
So
how
do
I
do
this?
Well,
there's
two
ways:
I
can
use
Japp
DSL,
it's
tried-and-true,
we've,
no
time
to
do
it.
For
yes,
a
lot
of
Jenkins
plugins
that
extend
the
jobs
have
native
DSL.
So
it's
it's.
It's
a
great
way
of
configuring.
Your
job
source
code
there's
also
the
declarative,
scripted
pipelines.
Those
are
the
future
ooh.
There's
a
poll
interesting.
A
Yes,
so
declarative
scripted
pipelines
the
future
they
can
resume
on
master
restart
they.
The
a
declarative
pipeline
has
at
job
T
has
a
DSL
which
makes
it
easy
to
use
a
lot
of
different
plugins
and
the
script
that
pipelines
are
in
groovy.
So
if
you
want
to
do
something
that
isn't
natively
supported
in
the
plugins
or
you
want
to
do
something
a
highly
customized,
then
you
can
use
the
scripted
pipelines.
A
Instead,
you
can
also
use
a
script
block
for
the
declarative
pipelines,
but
consider
if
you're,
using
the
right
tool
for
the
right
problem,
I'm
going
to
use
jump
to
yourself
for
this
because
it
turns
out
I
can
do
an
instant
conversion
of
my
job
configure
as
click
into
a
job
configured
as
code.
It's
a
little
thing.
I
came
up
with
super
cool,
so
a
job
in
jump.
A
Dsl
I
want
my
actual
pipeline
in
a
jug
to
you,
sell
spec
I
want
a
seat
job
that
knows
about
my
job,
to
yourself
and
I,
want
to
add
the
CG
up
to
Jenkins
rather
than
at
my
job,
so
Jenkins
and
it
gets
smart
I
promise.
So
the
way
I
create
this
job
I
create
a
new
file.
Call
it
some
job
to
yourself
that
groovy
I've
the
depth,
a
cell
specification
I'm
just
going
to
assume
for
now
that
writing
job
GSL
is
trivial
and
then
I
publish
it
to
my
internal
get
somewhere.
A
A
After
creating
my
job,
I
want
to
create
my
seat
job.
So
that's
how
I
make
Jenkins
aware
of
my
job
in
job
DSL,
so
I
create
a
new
freestyle
job
from
the
Jenkins
UI
I.
Add
a
job
to
yourself,
build
step
for
the
job.
Dsl
I
just
created,
I,
save
the
seat
job
and
then
I
run
it
and
then
Jenkins
will
create
the
job
that
I
have
in
my
job
Giselle
specification.
A
A
So
the
reason
this
get
smart
is
because
so
I
have
my
single
Jeff
s,
jump
diesel
and
I
have
my
seat
job,
but
I
can
actually
create
a
number
of
seat
jobs
for
a
number
of
jobs
and
then
have
a
single
seat,
job
that
a
super
seat.
Job
that
reads
all
of
the
seat:
jobs,
so
I
get
my
entire
platform
into
Jenkins,
but
I'm
only
telling
Jenkins
about
a
single
of
these
jobs,
so
I'm
only
configuring
one
job
through
the
UI.
This
is
very
nice,
so
the
way
I
get
into
job
diesel.
A
Alright.
So
the
configure
block
looks
like
this,
so
the
intention
of
it
is
for
em
to
use
chapter
yourself
or
plugins
that
doesn't
yet
have
a
native
DSL
support,
so
either
you
for
the
get
plugin.
You
will
have
these
nice
commands
so
get
it
has
a
remote,
so
they
have
implemented
that
in
the
get
plugin.
Otherwise,
if
I
want
to
do
more,
advanced
stuff,
I
might
have
to
use
a
configure
block
for
writing
directly
to
the
XML.
This
is
cool
for
two
reasons.
So,
first
of
all,
it
says
something
about
a
Jenkins
config.xml.
A
So
it
sounds
like
my
job
is
actually
already
there
configured
as
in
in
s
code
somewhere
and
secondly,
the
configure
block
will
give
me
access
to
interact
with
this
XML.
All
right.
So
did
you
know
that
a
Jenkins
job
is
available
as
XML
through
the
slash
config.xml
endpoint?
So
this
what
it
looked
like
for?
This
is
what
it
looks
like
for
a
job
that
has
a
single
task
that
says
hello.
World
I
can
actually
go
to
the
UI
and
go
to
my
job
and
on
the
config.xml
endpoint
get
a
specification
of
my
job.
A
A
A
And
you'll
be
seeing
me
just
copying
and
pasting
a
lot
of
stuff
from
this
example
repository.
That's
because
that's
how
easy
for
you
it
is
to
use
it
as
well,
so
I
have
a
pre-configured
Jenkins.
It
just
has
an
admin
user
and
it
has
the
job
Diaz
it'll
plug
in,
because
this
exercise
is
about
a
chap
diesel.
A
A
A
A
The
step
says:
make
a
copy
of
the
template
file
I'm
going
to
do
that
and
replace
the
XML
G
up
here.
Part
with
the
contents
of
your
config.xml.
You
get
that
from
the
config.xml
endpoint
and
you'd
use
the
view
source
I'm,
gonna
use
the
view
source.
Let's
get
the
XML
copying
and
paste
it
into
this
job,
configuration
excellent
and
then
it
says:
remove
the
header
of
the
XML
document,
I'm
going
to
delete
that
and
replace
backslashes
and
dollar
signs
with
back
slashes
or
escape
them.
A
So
this
is
a
simple
job,
so
it
doesn't
have
any
back
slashes
or
dollar
signs.
But
this
is
something
I
ran
into
when
I
did
it
on
my
own
time.
Lastly,
give
the
job
another
name
that
replaced
me
jumped
yourself,
so
I'm
just
going
to
call
that
Nikolay
in
DSL
and
congratulations.
You
have
now
converted
your
job
to
jump
diesel
over
right
now.
I
need
to
add
this
to
Jenkins,
so
I
create
a
new
job.
I
call
that
a
seat
job,
it's
a
freestyle
project
I
had
a
build
step.
A
It's
I
wanted
to
process
job
to
yourself.
I
want
to
use
the
provided
diesel
script
and
I'm
going
to
paste
the
job
DSL
that
I
just
wrote,
I
save
the
job,
I
run
it
and
then,
after
a
couple
of
seconds
run,
it
says
it
generated
an
item
line.
Job
to
yourself
can
run
that,
while
it
runs,
we
can
look
at
the
configuration
if
I
can
hit
it.
Oh.
A
Sorry
about
that
I
have
a
screen
sharing
bar
in
the
top
of
my
screen.
Can
you
see
my
screen
again?
Yes,
we
can
excellent.
Apologies
for
that.
So,
looking
at
the
configuration
I
have
my
single
shell
step.
It
says
echo
hello
world
and
when
I
have
run
the
job,
it
says
echo
hello
world
great.
So
this
is
how
easy
it
is
to
convert
your
point-and-click
job
to
job
to
yourself,
and
you
can
do
this
for
any
job,
because
I
didn't
make
any
assumptions
about
what
my
job
could
do.
A
So
is
this
cheating?
Well,
no
I
am
I
changed
my
workflow.
So
if
I
have
to
change
my
job
now,
I'm
still
doing
it
through
the
UI,
but
I'm
persisting
changes
with
the
generated
config.xml
through
get
so
I.
Have
my
job
configuration
under
version
control
and
I
get
my
easy
reconfiguration
with
the
supersede
job.
A
Alright,
my
next
steps
converting
this
to
a
declarative
or
scripted
pipeline
for
the
complete
s
code
flow.
So
right
now,
I
am
making
changes
by
clicking
through
the
UI
and
that
gets
tedious
still
and
my
rapt
job.
Dsl
is
not
that
easy
to
read,
but
this
is
a
great
first
step
for
just
getting
my
point-and-click
job
s
code.
A
A
A
So
how
do
I
do
this?
Well,
that's
a
little
harder
than
simply
converting
your
jobs
of
wrapping
your
jobs
in
job
diesel,
so
I
have
to
do
one
plug-in,
sort
of
or
one
setting
at
a
time
but
I
can't
it's
an
iterative
approach,
so
I
can
I
can
just
do
it,
one
plugin
or
one
setting
at
a
time
and
then
more
and
more
have
my
jenkins
configure
this
code
and
then,
in
the
end,
when
I'm
done,
I
can
switch
the
backup
strategy
so
I'm
just
saving
my
Jenkins
channel.
A
The
configuration
of
my
Jenkins
configuration
as
code
instead
of
my
entire
Jenkins
home
folder.
That's
a
ton
of
great
examples
on
the
official
configuration
is
called
plug-in
website.
Sorry,
a
github
repository.
They
have
a
folder
with
demos
that
shows
you
how
to
configure
a
lot
of
different
plugins
that
you
might
have
installed
on
your
Jenkins.
This
is
a
very
great
resource
for
helping
you
doing
that.
A
So
so,
what's
my
first
step
for
getting
my
Jenkins
configuration
as
code
in
docker
well,
I
need
the
Jenkins
configuration
this
code
plugin
and
do
I
want
to
install
this
manually
through
the
UI.
No,
of
course
not.
I
want
to
use
pre
installing
so
I
create
three
files.
One
file
called
plugins
txt.
It
has
the
configuration
as
code
ID
of
the
configuration
is
called
plugin
and
has
the
version
that
I'm
going
to
use
I.
A
Then
create
a
Jenkins
ya'muru,
which
is
the
config
file.
Further
configuration
is
called
plugin
under
the
Jenkins
I.
Add
a
system
message
I
tell
the
system
message
to
be
configured
as
code,
so
this
is
a
nice
sanity
check
for
me
to
see.
When
has
my
configuration
actually
been
read?
Thirdly,
I
create
a
docker
file
for
building
my
custom
Jenkins
docker
image
with
my
plugins,
and
this
are
just
basic
commands
from
the
official
documentation.
A
The
only
thing
I
have
added
here
is
that
I'm
skipping
the
setup
with
that?
It's
in
the
examples,
so
you
can
check
that
on
your
own
time,
I
have
the
plug-in
configurations.
Code
and
I.
Have
my
basic
Jenkins
configurations
code
configuration
file,
I
have
built
this
docker
image
and
now
I'm
going
to
run
it.
So
stop
the
other
one
and
go
into
the
right.
Folder.
A
Don't
want
to
install
any
plugins
and
I
just
want
to
continue
as
admin
not
now
start
using
Jenkins
and
it's
configured
as
code
awesome.
So
that
was
that
simple.
Just
to
see
that
my
Jenkins
works
I
can
create
a
new
job.
You
see,
it
only
has
the
freestyle
project
because
I
don't
have
any
plugins
here.
It's
also
a
very
limited
number
of
build
steps.
I
can
do
my
echo
hello
world
and
run
it
so
I
actually
have
a
working
running
Jenkins
that
is
configured
as
code
cool.
A
So
Caviar's
for
doing
this.
Well,
when
you
are
just
installing
your
plugins
pre
installing
your
plugins
and
you
are
mounting
in
a
Jenkins
home
folder
backup,
you
will
be
overriding.
The
configuration
is
called
plugin.
So
if
you're
not
starting
entirely
from
scratch,
you
will
need
to
add
the
configurations
code
plugin
through
the
UI
through
your
manage
plugins.
Secondly,
I
am
mounting
in
the
Jenkins
said
their
configuration
into
the
Jenkins
home
folder.
A
So
step
one
starting,
my
daugher
with
Jenkins
configuration
is
code.
So
what
step
two
well
I
still
have
this
a
clicking
part
of
adding
my
supercede
job
to
Jenkins,
so
I
might
want
to
script
that
I
can
add
a
job
to
Jenkins
by
just
adding
it
to
the
Jenkins
Yama
file,
so
under
jobs,
I
can
add
scripts
and
under
scripts.
I
can
add
the
job
diesel.
So
this
is
similar
to
the
job
DSL
you
saw
before
it's
just
been
intended
to
fit
with
the
Yama
style.
A
This
means
that
I
can
actually
add
a
super
seat,
groovy
job
to
my
Jenkins
Yammer,
and
then
the
job
will
be
there
when
Jenkins
starts
up.
So
here
I
have
my
super
seat
job.
It
checks
out
some
code
from
a
git
repository
that
will
be
the
job
DSL
companion
repository
for
the
example
project.
It
uses
credentials
to
check
this
out
and
it
runs
a
single
step.
It's
a
DSL
step
and
the
DSL
step
reads
the
external
job
DSL
off
the
repository
and
uses
wildcards.
A
So
it
just
reads
all
of
the
job
DSL
and
creates
all
of
the
jobs.
It
will
also
delete
jobs
if
I
make
changes
to
the
git
repository
and
run
it
again
missing
pieces
for
this.
Well,
I
am
starting
to
check
out
code
from
a
git
repository
using
SSH,
so
I'm
going
to
need
an
SSH
key
I
configure
my
Jenkins
configuration
as
Kochiyama
as
well
to
add
this
key
on
startup,
because
I
don't
want
to
click
through
the
UI
to
configure
Jenkins,
and
this
means
I
also
need
to
add
the
credentials
binding.
A
Plugin
I
don't
want
to
hard-code
secrets
into
my
configuration
either.
So
I
am
wrapping
the
an
environment
variable
in
brackets
and
dollar
sign.
This
means
when
I'm
running
my
Jenkins
when
I'm
starting
my
Jenkins
and
it
reads
the
configuration
it'll
read
this
value
from
the
environment.
So,
if
I
put
this
environment
variable
into
my
container,
that
I'm
running
Jenkins
will
read
the
environment
variable
and
use
that
to
configure
its
credentials.
So
that's
super
cool
and
I'm
actually
also
missing
a
couple
more
because
I
am
writing.
Jump
DSL,
so
I
need
to
jump.
A
Dsl
plug-in
I
am
using
a
kid
repository,
so
I
need
the
kid
plugin
I'm
using
SSH,
so
I'll
need
the
SSH
plug-in
and
I'm
going
to
be
reading
pipelines,
scripted
pipeline
jobs,
so
I
need
a
pipeline
plug-in
or
the
workflow
aggregator,
which
is
kind
of
emits
a
wrapper
around
a
lot
of
around
a
lot
of
pipeline
plugins.
So
this
just
means
that
I
get
the
latest
version
of
a
lot
of
pipeline
plug-ins
in
production.
You
should
figure
out
which,
if
the
plugins
you
need
and
of
course,
pin
the
versions
of
those.
A
So
in
the
Jake
asked
folder
I
have
an
advanced
folder.
There
is
a
demo
folder
and
there
is
a
couple
of
configurations
and
a
couple
of
shell
scripts
that
run
Jenkins
with
these
configurations.
The
difference
between
the
scripts
out
here
and
the
scripts
in
the
demo
folder
is
that
in
the
configuration
I'm
checking
out
with
SSH
I
can
do
this
because
my
credentials
point
to
a
service
account
or
but
user.
On
my
github
that
I
have
added
to
the
repositories.
A
When
you
are
running
this,
you
will
be
doing
it
checking
out
with
HTTP,
but
then
that
made
actually
supplying
the
credentials
a
bit
redundant.
So
now
you
have
both
examples.
So
in
the
HTTP
examples
you
can
do
it
without
credentials.
In
the
SSH
example,
you
will
have
to
supply
your
own
credentials
for
your
own
repository,
alright.
A
So
for
the
Jenkins
bootstrap,
you
can
see
from
the
slides,
I
have
the
credentials
configured
I
have
my
job
configured
for
the
demo
I'm
using
script,
security
false
so
I
don't
want
to
go
through
the
commands,
I'm
running
in
my
seed
job
and
allow
those
one
at
a
time
in
production.
You
should
use
script,
security
and
I
have
my
run
script
and
my
run
script
simply
provides
the
environment
variable
with
my
SSH
key
for
the
container
when
it's
running.
A
A
A
So
caveat
for
pre
installing
plugins,
it's
recommended
that
you
create
a
base
image
with
the
plugins
that
you
need
and
that
you
don't
simply
keep
the
plugins
txt,
because
at
a
later
time
the
plugins
might
not
be
available
in
the
version
that
you
need
so
I
told
you
that
I
have
been
working
on
this
project
for
almost
like
yeah
well
over
exactly
two
years
and
when
I
put
it
down
for
half
a
year
and
picked
it
up
half
year
later
and
try
to
build
my
Jenkins
again,
I
thought
well
great
I!
Have
it
as
code.
A
So
that's
just
going
to
work
and
then
some
of
the
old
plugins
that
I
was
using
had
been
removed
from
the
from
the
from
the
public
repositories,
so
I
actually
couldn't
build
with
the
oldest
plugins
again.
The
good
part
is
that
it
forced
me
to
update
all
of
my
plugins
to
latest,
but
it's
not
a
good
thing
if
you
expect
the
plugins
to
be
around
and
actually
be
able
to
use
them
in
those
old
versions.
A
Thirdly,
there
is
the
custom
wah
packager
project
that
you
can
also
see
for
different
ways
of
packaging
Jenkins
with
libraries
and
extending
it
with
plugins
to
make
it
easier
to
reproduce
the
actual
Jenkins
that
that
you're
gonna
be
that
you
you're
gonna,
be
building
so
more
missing
pieces.
Well,
you
saw
that
I
actually
had
to
run
the
super
seat.
Job
once
and
I
had
to
do
that
manually
and
I.
Don't
like
manual
work.
So
can
we
automate
that?
Well,
we
can
give
it
a
trigger.
A
It
also
means,
however,
that
my
super
seat
job
will
be
running
every
two
minutes
and
that
feels
like
a
bit
of
overhead,
but
then
so
I
have
my
I.
Have
my
super
seat?
Job
I
have
edited
to
Jenkins
with
clicking
now.
I
have
edited
to
Jenkins
with
the
configuration
as
code
and
thirdly,
I
have
told
it
to
run
every
two
minutes.
So
you
saw
that
I
had
the
super
seat,
job
in
the
in
the
in
the
job
DSL
repository
as
well,
and
that's
because
the
seat
job
can
actually
bootstrap
itself.
A
So
I
have
one
version
of
my
super
seat:
job
that
I
have
added
to
my
Jenkins
configuration.
It
has
the
trigger
timer,
so
that
tells
it
to
run
every
two
minutes,
but
then
I
have
the
super
seat.
Job
in
my
repository
with
seat
jobs
without
the
trigger
so
I
know
that
it's
going
to
run
at
most
two
minutes
after
then
it's
gonna
override
itself,
and
then
it's
not
gonna
run
anymore.
A
A
So
the
third
part
we
have
all
offered
of
our
jobs
as
code.
We
have
our
Jenkins's
code
and
now
we
wanted
to
run
in
kubernetes
and
we're
gonna
be
using
helm
to
make
that
super
easy.
So
why
do
I
want
it
running
in
kubernetes
in
the
first
place,
apart
from
kubernetes
being
awesome?
Well,
a
unified
way
of
managing
my
applications.
So
I
told
you
that
I
want
to
have
my
counter-strike
servers
running
in
kubernetes,
so
why
not
also
just
have
my
tooling
around
and
running
in
kubernetes.
A
Secondly,
it
allows
me
to
scale
with
kubernetes
build
agents,
so
instead
of
adding
these
build
agents
to
Jenkins
and
just
have
them,
idling
around
I
could
actually
use
them
inside
my
kubernetes
cluster
at
Jenkins
to
my
kubernetes
cluster
and
then,
whenever
I
need
to
build
something.
It'll
just
be
using
the
compute
power
that
I
already
have
running.
A
And
I
can
also
use
custom
images
for
this.
So
if
my
build
agents
need
a
specific
compiler
or
version
of
a
tool,
I
added
to
the
container,
which
serves
as
the
template
for
the
kubernetes
build
agents,
and
then
my
jobs
will
be
running
inside
of
this
container
and
I
needed
to
do
stuff
with
the
Google
cloud.
So
I
added
the
G
cloud
SDK,
which
I'm
going
to
show
you
caveat
with
this.
A
So
I
was
just
able
to
add
environment
files
to
my
container
when
I
ran
it
with
the
darker
run
command
I'm
not
able
to
do
it
in
the
same
way
when
I
run
it
in
coronaries.
So
what
do
we
do
in
kubernetes?
We
want
to
configure
our
application.
Well,
we
use
config
Maps
and
we
use
secrets.
I
would
still
not
like
to
to
have
my
to
have
my
secrets.
Have
my
passwords
have
my
SSH
keys
as
code,
so
I
would
really
like
to
still
be
able
to
provide
them
at
runtime
from
the
command
line.
A
A
So
I
have
a
readme
that
tells
me
how
to
do
the
demo.
It
tells
me
prerequisites:
I
need
to
have
helm
installed,
so
I
have
helm
in
Version.
Three
three
point:
one
point
two
I
need
to
add
the
stable
repository
for
helm.
This
is
also
part
of
the
QuickStart
guide
and
afterwards
I
can
search
the
repository
and
I
can
see.
Oh
no
I
can
see
that
I'm.
Finding
a
stable,
Jenkins
help
chart
and
I
should
have
access
to
a
kubernetes
cluster,
so
I
can
do
kubernetes
get.
A
Oh
sorry,
kill
control,
get
notes
and
I
have
access.
That
is
awesome
as
well.
I
have
my
helm
SH.
So
that's
a
helper
script
for
doing
the
helm.
Installation
I
have
my
install
script.
I
have
my
own
install
script.
The
install
script
creates
my
two
secrets.
They
created
from
files
so
rather
than
cutting
the
contents
of
a
file
into
an
environment
variable
that
I
give
to
my
container
I,
just
create
a
secret
from
the
command
line
from
a
file.
B
A
Jamel
and
I
could
have
supplied
these
as
a
list,
but
then,
if
I
wanted
to
do
it
later
from
some
CI
I
would
have
to
use
a
CD
or
some
other
tool
to
edit
my
values,
Yama
file
and
in
this
way,
I'm
actually
able
to
do
it
just
from
the
command
line.
I
think
that's
kind
of
cool
the
values
file
I'm
using
for
this
deployment
looks
like
this.
I
have
my
master
I
configure
it
to
install
a
number
of
plugins.
A
A
number
of
these
you've
seen
before
a
number
of
these
are
just
a
quality-of-life,
plugins,
so
job
config
history.
What
changed
they're
being
able
to
rebuild
a
job
time?
Stamping,
output,
wonderful
plugins,
I,
specify
a
specific
tag
for
the
Jenkins
master
that
I
want
to
run
and
then
I
supply
my
Jenkins
configuration
as
code
configuration.
A
A
This
is
what
I
told
you
in
the
beginning
that
when
you
have
your
Jenkins
configured
as
code,
it's
super
easy
to
get
running
in
kubernetes
with
helm,
because
you
just
paste
your
entire
configuration,
you
indent
it
then
you're
ready
to
go
so
I
told
you
about
the
trigger
I.
Want
it
to
be
run
at
most
two
minutes
after
this
trigger
will
be
overwritten.
It's
just
here
to
auto
trigger
one
build
awesome.
A
A
And
create
two
secrets
is
gonna:
do
the
helm
install
and
with
the
output
from
the
helm,
install
so
I'm
just
going
to
copy
and
paste
these
things?
This
is
the
getting
the
secret
from
the
for
the
admin
account
this
exporting
the
pod
name
and
then
I'm
port
forwarding
to
the
Jenkins
instance
running
in
the
cloud
so
that
I
can
access
it
from
my
computer.
A
A
A
A
A
A
A
I
have
put
the
the
command
line
things
after
a
run,
command
and
I've
removed
the
pseudos,
because
I
don't
need
that
when
I'm
running
his
route
and
in
the
end
I'm
switching
to
the
Jenkins
user
again
I
have
a
build
script,
so
you
will
want
to
push
it
to
your
own
repository
I.
Give
it
a
name
I,
give
it
a
tack.
A
And
they
should
be
done
in
a
second
or
well
a
couple
of
seconds,
depending
on
how
how
fast
it
takes
for
for
the
putts
to
start
so
the
ones
we
didn't
look
at
the
off
pipeline,
so
what
yeah?
So
what
you'll
see
here
is.
Actually
it
not
really
interesting,
because
this
will
just
be
referencing
a
Jenkins
file.
It'll
tell
me
it
needs
to
check
out
the
pipeline
script
from
a
source
code.
It
needs
to
check
it
out
from
git,
and
then
it
tells
me
where
it
is
in
the
repository.
A
So
this
is
the
auth
and
jump
to
yourself.
This
is
a
git
repository
and
then
there's
a
script
path.
The
interesting
part
is
actually
in
the
script
on
the
pipeline
repository,
which
is
the
mono
repo
project
example.
So
I
could
have
done
this
as
three
different
repositories.
I
chose
to
this
one
is
then
I
only
had
to
create
one
repository.
The
earth
has
a
Jenkins
file
and
it
will
check
out
this
repository
from
source
code.
A
A
This
is
very
practical
if
you
need
to
authenticate
a
a
Google
cloud,
for
example,
so
an
example
of
using
the
Google
cloud.
If
a
tiny
example
nonetheless
I
have
my
sanity
check,
I
have
my
config
file
provider
as
well,
and
then
I
just
do
a
G
cloud
version
just
to
check
that
the
G
cloud
SDK
is
actually
installed
into
my
into
my
Jenkins
agent
and
when
I'm
looking
at
the
output
I
have
my
hello
world
I.
A
Have
my
secret
file
and
I
have
the
version
of
the
different
components
of
the
G
cloud
SDK
that
I'm
installed
I'm
doing
something
on
the
Google
cloud,
create
machines,
etc
and
in
the
end,
I
clean
up
the
VMS
another
cool
trick?
Put
it
in
a
try-catch
have
a
finally
class
that
cleans
up
because
then,
if
you
make
an
error,
it
still
deletes
your
resources
on
the
platform.
You
get
all
these
examples.
A
So
to
wrap
up
I
wanted
to
do
a
lot
with
kubernetes,
so
I
had
an
interesting
journey
that
took
two
years
and
then
last
weekend,
I
had
a
colleague
write
me,
hey
man,
are
you
still
hosting
csgo
service
in
kubernetes
and
I
wasn't
entirely
done
with
the
platform
that
I
wanted
to
build,
but
he
told
me
that
the
free
server
broke
and
I
thought
we'll
all
right.
I
have
it
running,
so
I
can
start
it
up
and
15
minutes
later.
A
B
Thank
you
very
much
for
your
great
presentation.
We've
got
a
number
of
questions.
We
answered
some
of
them
offline,
but
we
still
have
eight
questions
so
to
discuss.
So,
let's
try
to
go
through
them
and
maybe
rated
it
overrun
the
meeting.
So
the
first
question
is:
where
can
I
get
a
job?
The
second
person
conversation
rapid
rates.
There.
A
A
There
is
a
readme
and
it
has
a
detailed
guide
which
takes
you
to
a
kit
lap,
repository
I
created,
which
has
a
lot
more
detail
about
what
actually
happens
in
the
script
and
there's
also
some
things
about
verification
and
yes
go
nuts,
and
please
tell
me
if
it
works
or
does
not
I
made
it
ten
months
ago,
but
apparently
yeah.
Some
of
it
still
runs.
A
Yes,
so
that
is
an
excellent
question
if
I
was
to
get
so,
I
haven't
tried
this
out,
but
you
will
still
need
to
tell
Jenkins
how
to
talk
to
vault.
So
you
need
to
give
Jenkins
a
token
in
the
first
place,
which
means
that
these
credentials,
it's
actually
still
great
for
giving
your
Jenkins
your
vault
token
and
then
in
your
job.
B
B
A
Yes
sure
so
well,
first
of
all,
if
you
have
your
Jenkins
in
the
credentials,
then
you
have
them
in
the
credential
store
on
your
master.
So
if
you
have
access
to
the
master,
you
can
jump
through
different
hoops
to
still
get
their
credentials,
but
I
would
like
to
store
my
credentials
in
vault
and
then
just
have
a
vault
token
on
the
master
and
then
on
runtime
manage
my
secrets
in
the
different
jobs,
so
sure
I
can
I
can
see
that
it.
A
B
B
A
B
That's
one
of
the
ways
another
ways
possible
to
your
continue
using
its
master
so
that
you
can
store
changes
home
on
a
volume
for
huge.
We
have
a
lot
of
pluggable
storage
stories,
it's
already
a
possible
to
do
it
for
logs,
we
created
local
storage
whole
pipeline,
and
you
can
use,
for
example,
flu
in
D
and
the
AWS
cloud
watch,
or
elastic
search
and
yeah
for
artifact
manager.
As
Nikolai
said,
we
have
an
generation
miss
s3
and
the
in
general.
We
intend
to
keep
working
on
that.
B
They
just
published
English
roadmap,
which
has
been
developed
under
moment
and
back
to
be
useful,
but
in
principle
just
pass
volume
with
Jenkins
home
and
it
will
work
and
it
will
persist.
Adt
between
restarts
obviously
make
sure
you'll
make
pickups
using
weather
or
other
services
and
margins
and
presented
how
to
do
better
at
the
last
media.
Yes,.
A
Just
to
add,
in
the
example
repository
that
you'll
get
under
the
basic
Jenkins
in
Duggar
I
was
using
the
fresh
Jenkins
and
I
was
mounting
a
volume
onto
the
Jenkins
home,
so
this
name
of
the
volume.
This
is
the
path
inside
the
container,
and
that
meant
that
I
could
prepare
it
upfront,
so
I
could
install
the
job
DSL
plugin,
and
it
would
also
persist
my
my
jobs
through
restarts.
B
Thank
you
and
yeah
we'll
try
to
process
so
funny
and
publish
it
responses
at
the
local,
so
yeah
I'm,
posting
links
in
peril
and
hopefully
you'll
publish
all
this
information
soon.
Yes,
okay,
so
we
have
well
actually
a
number
of
questions
increases.
So
if
everybody
has
ten
extra
minutes,
we
can
keep
answering
questions
yeah
sure,
okay,
good.
B
B
Right
and
also
if
you're
interested
you
can
join,
Jenkins
configuration
has
gotta
get
a
shot
because
the
Hashi
court
revoked
plug-in
is
currently
maintained
by
Jake.
Ask
me
a
nurse.
So
if
you
have
any
questions,
just
adjourn,
the
Charter
and
other
contributors
will
be
able
to
answer
these
questions.
A
I
would
expect
it
works
really.
Well
with
it.
So
it
says
it
has
support
for
the
configurations
code
and
my
I
didn't
really
do
anything
special
with
my
jobs,
going
from
a
normal
Jenkins
to
a
Jenkins
configurations
code.
So
I
would
expect
you
to
just
like
dump
pure
config
Jenkins
yam
rule
in
there
and
that
it
would
run
out
of
the
box.
A
The
reason
I'm
not
using
a
an
operator
is
that
I
don't
need
the
lifecycle
management
of
my
Jenkins
so
doing
the
but
I
manage
the
lifecycle.
Myself
I
do
the
upgrades,
so
the
operator
can
help
you
with
that
and
then
I
expect
kubernetes
to
do
the
rest.
So
if
my
Jenkins
crashes,
then
kubernetes
will
restart
it
and
then
hopefully,
if
I've
configured
it
correctly,
it's
going
to
bootstrap
itself.
B
B
B
A
Not
at
all
that
was
just
because
I
am
running.
My
kubernetes
project
on
the
I
am
running.
My
counter-strike
servers
on
the
Google
kubernetes
engine,
so
I
needed
to
interact
with
Google
cloud
so
for
for
testing
like
spinning
up
a
new
gke
cluster
or
configuring
firewall
settings
and
I
wanted
Jenkins
to
be
able
to
do
that
for
me.
So
that's
why
I'm,
adding
the
the
the
SDK
so
that
I
can
from
the
command
line,
but
from
a
Jenkins
job
interact
with
the
Google
cloud,
there's
nothing
to
do
with
where
Jenkins
is
running
its.
A
A
B
A
B
As
a
permanent
in
Europe
must
pass
first
plug-in
credentials
by
name,
they
give
me
indeed
tries
to
most
passwords
by
default.
Mask
passwords
at
some
point.
It
had
integration
via
Jenkins
Python
can
be
used
in
some
cases,
so
the
security
warning
quote
is
circulated,
yellow
power
again
but
yeah.
If
somebody
wants
to
contribute,
please
do
so.
Unfortunately,
I
had
to
step
down
as
a
plug-in
medium
to
Southern
taken.
So
there
is
some
technical
depth
and
yeah.
The
plug-in
is
looking
for
a
new
maintainer.
B
A
I
do
so
I
am
a
one-person
developer
army
in
my
project,
so
I
just
have
the
default
admin
user,
but
you
could
add
users
in
your
Jenkins
configuration
as
code
yeah
Mel
as
well.
But
what
you'd
really
want
to
do
is
just
hook
it
up
with
your
LDAP
and
manage
your
users
from
there,
but
then
manage
the
LDAP
integration
from
the
from
the
configuration
as
code
general,
so
that
when
your
jenkins
starts
up
fresh,
you
can
just
log
in
with
your
users
and
groups,
all.
B
B
A
Yes,
oh
you
I,
think
that
when
you
create
your
so
when
I
have
my,
this
was
the
job
DSL.
When
I
have
my
scripted
pipeline
I'm
telling
it
where
to
run
so
because
I
didn't
specify
any
agents,
it's
just
going
to
run
on
the
default
agent,
but
I
would
be
able
to
in
different
steps
to
specify
which
notes
it
should
actually
be
running
on.
So.
B
A
B
Alright-
and
you
can
refer
to
the
previous
presentation
by
martin
jackson-
represented
how
to
use
kubernetes
plugin,
which
can
provision
agents
from
de
monterrey
Bernanke's,
and
there
are
the
plugins
and
revision
site
containers
or
if
you
run
Jake,
it's
an
important
many
other
options.
So
yeah
you
can
provision
them
depending
on
your
needs.
Matters.
B
B
A
Jake
asked
job
because
I
wouldn't
want
to
break
things
that
I
had
working
in
case
this
didn't
work
and
then
it
totally
worked
and
then
I
didn't
go
back
to
my
readme
and
update
the
name
of
the
newly
builded
image,
so
I'm
actually
running
the
very
first
image
I
created
when
I
did
the
demo
for
Olek,
and
he
told
me
hey.
This
is
a
cool
thing
you
should
try
out.
So
it
was
just
just
the
demo
gods
giving
me
a
hard
time
mm.
B
A
Thank
you
for
that
question.
So,
in
the
in
the
companion,
repository
called
DSL
I
have
a
job
DSL,
folder
and
I
have
my
supersede
job
and
this
loads.
All
of
the
job
DSL
in
this
job,
DSL
folder
in
each
of
these
folders
I,
have
a
joke.
Dsl
script,
which
loads
a
single
Jenkins
file
and
I,
could
have
several
job
DSL
scripts
in
this
folder
and
I
could
have
several
folders,
so
you
can
put
each
of
your
yeah
so
for
your
hundreds
of
jobs.
A
So
for
each
job
you
will
have
a
Jenkins
file
and
each
of
those
Jenkins
files
will
just
have
a
one,
a
pipeline
job
which
reads
it
from
the
from
your
source,
code,
management
and
loads.
It
with
the
script
path
and
also
like
so
this
is
called
basic
Jenkins
file
in
the
earth
example,
it's
called
Earth
Jenkins
file,
most
of
the
time.
If
you
have
it
in
different
repositories,
it
will
just
be
called
Jenkins
file
and
be
in
the
root
of
your
repository.
B
B
Thanks
say
if
you
use
just
Jake,
ask
Hamels
it's
possible
to
specify
a
folder
as
a
general
configuration
path
and
if
you
do
so
or
Jake
as
plug-in,
will
all
load
all
the
gammas,
and
it
also
has
logic
to
merge
them.
This,
logically,
is
probably
not
like
deep
rush,
but
it
does
the
job
for
many
common
pieces.
B
Yeah,
so
it
really
depends
on
your
setup,
because
if
you
have
a
cluster
of
multiple
junky
small
steps,
you
can
implement
various
things
like
interesting
for
them.
If
you
want
it's
totally
doable
I
know
there
is
no
traditional
framework
for
that
right
now.
Well,
in
hope,
this
will
person
to
block
lobbies
corrent
all
these
share
problems,
but
you
have
open
source.
It
would
require
additional
scripting.
B
So
if
we
you
want
to
do
that,
it's
possible.
If
you
just
rely
on
Jenkins
by
default,
then
you
would
have
to
accept
down
time
right
now.
Jenkins
doesn't
have
multi.
We
had
a
research
project
which
we
presented.
Peoples
haven't
eaten
at
the
contributor
summit
in
Brussels,
but
right
now
you
have
to
restart
your
instance
in
order
to
apply
a
place
for
this
configuration
and
Plato.
A
But
did
you
see
how
fast
it
was
to
start
up
a
new
Jenkins,
so
it
should
be
fairly
easy
for
you
to
to
test
out
the
new
version
of
plugins
or
test
out
the
new
version
of
Jenkins.
Take
your
configuration,
move
it
to
a
different
instance.
Spin.
It
up
click
around
in
it
verify
that
it
works
to
your
needs,
maybe
add
a
couple
of
jobs
to
it
and
even
run
them.
If
you
want
to.
A
B
A
B
It
so
thanks
everyone
for
questions
again.
We
will
try
to
process
them
and
thanks
a
lot
Nicolai
for
this
presentation.
It
was
really
useful.
A
lot
of
different
cases
and
looking
forward
see
what's
next
stay
tuned
for
the
next
changes
on
kubernetes
meetups
pleasure,
yeah
thanks,
oh
I
will
stop
the
recording.