►
From YouTube: Online Meetup: Jenkins Operator on Openshift
Description
Openshift has been making Jenkins available to it’s users as a primary CI/CD tool for a few years. Our users and customers are happy with it because it seamlessly integrates with the Openshift ecosystem. This talk will showcase the Jenkins Operator on Openshift. The Operator allows users to manage and use their Openshift supported Jenkins instances. We are excited to share new features that have been added to the Operator since our last Jenkins Online Meetup on the Openshift Operator for Jenkins.
References:
* Slides: https://docs.google.com/presentation/d/1As3eMYEiyBsEILfpvEMjpP1s-pJ0OeyVAuPZtXrjAGA/edit?usp=sharing
* https://github.com/jenkinsci/kubernetes-operator
* Jenkins Operator for RedHat - https://github.com/redhat-developer/jenkins-operator
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/271690719/
About the speaker: I work at Red Hat as a Software Engineer in the Jenkins Team. I maintain Openshift specific Jenkins plugins with my team and contribute to Tekton and Helm on the side. In my free time, I play guitar, do programmatic art using processing or go for a run.
A
My
name
is
Vaibhav
I
work
at
Red
Hat
and
the
open
chef
team.
So
in
OpenShift
me,
along
with
my
teammates,
we
maintain
the
Jenkins
or
ecosystem
of
plugins
and
though,
and
also
maintain
the
Jenkins
image
for
open
shift.
So
this
is
something
that
we
give
to
our
customers
so
so
that
they
can
use
Jenkins
alongside
with
her
with
openshift.
So
that's
that's
about
me.
Let's
get
started
with
the.
A
A
This
talk
will
cover
what
all
stuff
comes
after
that
and
what
are
the
new
things
in
the
roadmap
that
we
have
discussed
and
also
how
this
operator
and
integrates
it
open
ship
and
how
this
is
a
helpful
in
the
open
shipped
in
a
moment.
So,
let's,
let's
so,
let's
start
with
a
little
bit
of
a
story.
First,
imagine
that,
like
I
I,
think
everyone
here
knows
what
Jenkins
is
so
in
Jenkins
we
have
pipelines
and
we
can
create
a
lot
of
pipelines
and
we
can
spin
up.
A
Let
me
go
into
present
mode,
so
we
can
spin
up
a
lot
of
pipelines
and
once
these
pipelines
are
spun
off,
we
can
configure
them
based
on
how
we
want.
We
can
have
them
periodically
spin
up
whenever
they
whenever
we
want
and
we
we
can.
Also.
Oh,
we
with
all
this
all
the
stuff
that
it
does.
We
also
need
to
do
a
lot
of
housekeeping
with
it.
We
need
to
see
to
it
that
there
is
a
little
power
backup
and
restore
happening,
and
certain
kind
of
for
date,
two
level
jobs
that
we
need
to
do.
A
Usually
these
jobs
are
done
by
the
administrators
who
who
are
proficient
in
Jenkins
and
who
knows
who
knows
Incans
in
and
out,
and
they
are
the
ones
usually
to
do
these
tasks
now
in
an
event,
if
the
admin
is
not
there
or
there
is
a
requirement
which
needs
to
be
fulfilled
for
the
for
these
day-to-day
two
level,
tasks
to
be
done
on
a
on
a
continuous
basis.
What
do
we
do
then?
A
So,
let's,
let's,
let's
just
understand
who
this
admin
is,
this
admin
is
operating
Jenkins
and
he
knows
how
to
operate
Jenkins,
and
that
is
what
the
Jenkins
operator
for
kubernetes
is
basically
in
the
kubernetes
and
moment
where
everything
is
based
off
of
boards
and
containers
and
Jenkins
runs
in
pods
it.
It
is
so
it
is
possible
for
us
to
create
something
that
can
actually
manage
those
Jenkins
instances
and
manage
the
Jenkins
instances
themselves
and
do
the
hand-holding
for
the
backup
and
recovery
and
configuration-
and
you
know,
do
these
jobs
periodically
by
themselves.
A
Is
it's
a
piece
of
code
which
kind
of
helps
in
patching
all
these
things
together
and
making
the
entire
workflow
happen,
for
example,
if
I
need
to
backup
and
restore,
there
needs
to
be
some
code
written
that
does
this
backup
and
restore
for
Jenkins
in
a
specific
way.
So,
for
example,
I
need
to
backup
all
the
plugins
that
are
being
used
and
wire
loop,
Jenkins
plugins.
It
will
take,
take
that
all
stuff
out
and
then
it
will.
It
will
do
that
stuff
by
itself.
A
Now
that
is
just
the
Jenkins
operator
now,
if
you
want
more
in-depth,
in-depth
understanding
on
what
operators
are
of
B
Sharma
has
done
a
brilliant
talk
on
operators,
101,
which
kind
of
goes
through
the
basics
of
these
operators
and
kind
of
covers
them.
But
in
this
talk
we
talk
about.
Where
have
we
come
from
the
last
time?
And
what
do
we
look
whatever?
What
we
as
openshift
engineers,
are
trying
to
bring
to
the
table?
So,
let's,
let's
understand
how
the
Jenkins
operator
on
open
shift
came
along.
A
So
if
you
look
at
this,
so
the
Jenkins
operator
on
open
shift
is
not
an
entirely
new
concept,
because
Jenkins
has
been
provided
to
open
shift,
open
shift
users
for
some
time
or
the
open
source
were
in
office.
Here
you
can
see
or
template
or
the
O
which
is
created
for
Jenkins
it
creates,
so
it
creates
certain
resources
which
are
necessary
for
configuration
of
Jenkins,
and
these
resources
are
created,
including
the
image.
So
the
image
also
here
these
are
created
so
that
open,
show
specific
processes
are
possible
to
be
done
through
Jenkins.
A
Now,
what
do
I
mean
by
that?
So
so
in
in
Jenkins,
so
as
you
saw
the
template
over
there
in
Jenkins,
why?
Why
do
we
even
have
Jenkins
in
open
shift?
So
what
so?
Basically
when
we
need
to
do
entire
build
pipelines
in
kubernetes
itself,
Jenkins
is
one
tool
which
has
the
level
of
extensibility
that
no
other
tool
has
so
the
Jenkins
Jenkins
has
a
kubernetes
plugin,
which
we
have
used
to
create
the
open
shift,
sink
and
open
shift
client
plugins
these
plugins
integrate
with
Jenkins
and
open
shift
and
help
to
create
our
pipelines.
A
Now,
if
I,
so,
let
me
I'll
show
you
an
example
of
a
build
config
and
build
in
a
while
when
I'm,
showing
the
operators
so,
but
that's
just
to
kind
of
get
an
understanding.
How
Jenkins
integrates
with
open
chef
is
through
builds
and
build
conflicts
where
buildconfig
is
basically
the
configuration
of
a
Jenkins
pipelines
of
the
build
configure
the
Jenkins
strategy.
Now
we
also
provide
some
extra
images
or
with
which,
which
are
as
which
are
basically
pod
templates.
These
images,
which
are
used
in
these
poor
templates
for
kubernetes
plugins.
A
These
images
are
for
node.js
and
maven
and
they
can
be
used
as
as
like
a
base
for
or
doing
the
builds,
and
these
basically
act,
like
agents
users
can
go
ahead
and
create
their
own
agents,
be
based
on
the
base
that
we
that
we
give
in
the
Jenkins
repo.
So
the
Jenkins
repo
is
situated
in
in
over
here
github
slash,
open
ship,
Jenkins
or
users
can
go
here
and
they
can
go
to
the
sea.
These
are
the
agent
images
that
we
give.
So
these
are
the
ones
and
they
are
used
in
the
pod
templates.
A
So
after
that,
let's
talk
about
why
we
are
moving
to
the
Jenkins
operator
now
Oh,
considering
now
based
on,
would
have
said
you
might
have
got.
An
understanding
of
Jenkins
is
already
tearing
open
shoot,
but
why
the
operator
now
with
the
takedown
coming
through
and
the
deprecation
of
Jenkins
on
open
shift
or
doesn't
doesn't
mean
that
people
will
stop
using
Jenkins.
A
A
lot
of
people
will
continue
using
Jenkins
because
they
have
a
lot
of
pipelines
that
they
would
like
to
that
they've
heard
from
a
long
time,
and
they
would
like
to
either
migrate
into
a
new
Jenkins
solution
or
just
keep
things
as
they
are.
So
for
that
we
are,
or
we
are
helping
out
with
the
Jenkins
operator
and
trying
to
create
a
bit
creative
mode.
A
Enterprise-Level
solution
with
the
maintainer
or
for
the
Jenkins
operator
Tomas,
and
we
are
working
together
to
have
a
more
enterprise
region
is
operator,
so
that
application
and
the
need
for
new
solution
has
brought
us
to
the
Jenkins
operator
on
open
ship.
And
apart
from
that
also
like
we,
we
need
to
manage
Jenkins,
better,
manage
drinkin's
and
do
a
lot
of
other
things
we
couldn't
do
before
like
have
a
mutable
or
immutable
and
womans
which
can
be
replicated
so
that
the
user
user
don't
see,
changes
all
the
time
and
when
ori
updates
things
like
those.
A
So
that
is,
that
is
how
the
vision
of
open
shift
and
jenkins
has
gone
towards
the
Jenkins
operator.
Let's
move
on
to,
though
so
in
the
demo
I
will
kind
of
go
through
go
through
all
this
again.
This
is
just
to
kind
of
get
an
idea
right
now.
Let's
so,
let's
talk
about
the
operator
itself
and
what
the
operator
does
and
look
at
some
examples
of
those
stuff.
A
Cre
is
basically
an
API
endpoint
that
we
define
from
before,
so
that
the
operator
can
latch
on
to
it
and
then
this
unknown
request
on
that
API
endpoint.
That's
that's
how
you
can
see
it,
so
we
can
see
that
the
these
ones
have
already
been
created
by
us
to
create
this.
If
you
go
to
the
Jenkins
Jenkins
CI
communities
operator.
A
A
A
Let
me
just
do
something
similar,
so
a
CR
is
basically
an
instance
of
the
CRD
and
considering
we
are
on
openshift
right
now
we
will
look
at
an
open
ship,
specific
CR,
because
open
ship,
if
you
might
not
know,
is
a
distribution
of
communities
that
is
not
exactly
distribution.
It's
like
a
stro
of
kubernetes
with
by
Red
Hat,
and
it
has
some
increased
security
policies
in
such
because
of
which
there
are
certain
configurations
that
need
to
be
kept
in
mind,
so
the
image
that
will
run
with
this.
A
A
Yeah
so
yeah
it
is
built
from
the
open
shop
Jenkins
repo
from
here.
This
is
where
it's
built
from
from
Jenkins
/
and
yeah.
Basically,
this
is
the
image
that
we
are
using
here,
and
this
is
the
Jenkins.
This
is
the
environment
configuration
that
we
give
for
the
Jenkins
or
which
is
necessary
for
an
open
ship,
and
why
do
we
do
this?
A
And
how
did
we
manage
this
before
so
in
this
year,
which
is
which
gives
all
this
configuration
allows
us
to
give
the
configuration
for
Jenkins
this
this
we
used
to
give
it
before
in
a
form
of
a
template.
Now,
if
you
know
what
oh
hello,
art
is
open
chef
template
is
basically
a
help
chart
before
charts.
Hell,
charts
are
cool,
so
this.
This
is
something
that
in
which
you
can
define
what
all
resources
you
want
or
deployment
config.
So
this
config
config
map
secrets
anything.
A
You
want
PVCs
Peavey's
that
you
would
want
to
create
and
the
environment
variables
and
the
parameters
that
you
would
pass
with.
The
processing
processing
of
the
template,
which
will
replace
it's
almost
like
I,
have
ensured,
but
so
this
is.
This
is
what
we
used
to
give
before,
but
now
that
we
are
open
shift
is
moving
towards
a
more
kubernetes
centric,
a
way
of
doing
things
we
are
moving
from
this
to
the
operator
and
in
the
operator
we
are
kind
of
basically
replicating
this
as
a
seer.
A
A
A
This
board
is
for
the
Jenkins
operator,
which
I
started
way
before,
and
the
Jenkins
example
board,
which
also
started
way
before,
because
because
of
this
presentation,
let's
let's
and
the
thing
is
the
best
way
about
the
best
thing
about
this-
is
it's
very
easy
to
deploy
an
operator
on
open
sure?
All
you
need
to
do
is
go
to
the
open
shift
console
and
then
in
the
operators
or
sidebar
in
the
go
to
the
operators.
Drop-Down
go
to
operator
hub
and
in
operator
hub,
just
search
for
Jenkins.
A
Sorry
for
the
dogs,
I,
don't
know
so
go
to
the
operator
hub
search
for
Jenkins.
You
can
see
that
this
is
saying.
Install
in
the
project.
Jenkins
operator,
test
or
project
means
namespace
in
openshift,
so
go
here,
and
you
can
see
that
it's
already
installed.
I'm
not
gonna
uninstall
it
because
it
takes
times
at
times.
So
you
can
see
all
the
information
for
the
operator
operator
is
given
here.
Currently,
you
can
see
that
the
operator
is
on
0
dot,
4
dot,
1
RC,
but
actually
in
upstream
we
are
only
released
to
0.40.
A
So
what
we
are
doing
here
is
where
we
keep
reiterating
based
on
the
latest
code
base
or
till
we
reach
the
release.
Now,
why
do
we
do
this?
We
do
this
because
the
at
at
times
or
the
few
things
like
recently,
we
didn't
have
any-
are
also
open
to
get
to
its
route
smoking.
We
had
to
actually
go
through
peers
and
then
once
that
got
most,
we
thought.
Okay,
it
makes
sense
to
do
one
asean,
but
it
will
actually
only
do
a
final
release
of
this.
A
A
Oh,
you
see
that
the
Jenkins
example
is
operator
is
installed,
and
you
can
also
see
that
the
Jenkins
example
is
installed
and
if
I
go
into
the
installed
operators
and
go
over
here
in
I
can
actually
just
create
a
Jenkins
instance
from
saying
create
instance
here,
but
I
think
it's
already
running.
So
I
will
just
go
ahead
with
playing
around
with
this.
So
this
Jenkins
example
that
is
created
there
is
a
route
treated
for
it
as
well,
routers,
basically
in
or
endpoint
for
a
service.
It's
like
ingress.
So
this.
A
A
A
A
It
creates
a
build
basically.
So
this
is
the
build
that
is
created
Jenkins
pipeline
and
this
syncs
with
the
example.
You
can
see
that
this
board
is
created
and
this
board
is
nothing
but
the
Jenkins
agent.
This
is
the
agent
board
that
is
created
through
the
pod
template
in
köppen.
It
is
plug
in
Omega
the
mechanism
through
that
and
then
once
this
is
created,
let's
go
over
here
and
see
what
what's
up.
A
Guess
it
failed.
But
basically
this
saw
build,
got
started,
it
got
synced
and
it
was
started
over
here.
So
the
Jenkins,
basically
the
build
and
build
configurable
to
line
up
together
with
the
Jenkins
operator
created
jenkins
instance
and
the
OpenShift
workflow
for
jenkins
using
the
operator,
is
working
properly.
Now.
A
Let
me
go
back
to
the
so
we
are
done
with
this
one.
So,
let's
go
so
that
that
was
the
demo
now.
Let
me
actually
talk
about
the
architecture
and
the
roadmap,
so
what
happened
right
now
basically,
was
though
we
created
our
jenkins
CR,
which
was
which
was
this
already,
which
was
created
and
the
Jenkins
CRO
or
when
it
is
vanished.
A
A
Then,
in
the
user
e
translation,
it
installs
all
the
groovy
script
cast
scripts
and
it
all
the
it
does
the
configuration
on
that
level
for
Jenkins
and
then
it
reconciles
based
on
if
there
is
any
change
in
the
Jenkins
here
now,
Oh
this
architecture
kind
kind
of
can
be
linear
in
a
way
and
is
known
to
cause
issues
because
of
the
different
nuanced
things
it
does
so
currently
on
the
roadmap.
There
are
a
few
things
that
we
are
looking
at
to
make
this
better.
A
There
is
a
pod
created,
but
not
a
deployment
created
for
the
Jenkins,
so
this
is
the
first
first
hurdle
that
we
have
to
go
through.
So
this
we
don't
have
a
deployment
for
the
Jenkins
ignite,
but
this
is
the
first
hurdle,
and
this
is
important
because
then
things
like
sto
and
all
which,
which
do
like
injection
through
admission,
buy
books
on
your
mutation
where
books
they
can,
they
can
be
used
with
Jenkins,
because
recently
we
are
a
issue
which
which
was
around
this
then
after
that
the
other
thing
we
are
the
other
things
we
are.
A
We
are
planning
for
our
or
the
air-gapped
enrollment.
The
air
captain
moment
includes
him.
Jenkins
image,
controller
I'll,
just
explain
the
concept
so
India
captain
moment
basically
or
the
customer
shouldn't
have
to
all
the
users
should
have
to
have
access
to
internet,
but
they
should
be
able
to
use
their
Jenkins
asses,
no
need
to
install
any
plugins
or
like
connect
to
the
Jenkins.
Oh
oh
plug-ins,
repo,
and
then
try
to
miss
to
download
it
because
at
times
the
repo
repo
isn't
even
online,
and
there
are
problems
so
to
overcome
these
things.
A
Like
the
first
solution
that
we
are
working
on
on,
our
team,
Akram
is
working
on
is
with
is
the
Jenkins
image
controller,
which
helps
to
create
immutable,
Jenkins
images
with
the
plugins
pre-installed,
so
that
the
user
doesn't
have
to
wait
for
the
plug-ins
to
get
downloaded
every
time
the
CR
starts
up
a
new
CR
is
created.
This
is
the
Proficio
which
is
happening
right
now,
then
the
next
one
is
have
a
local
update
center,
which
would
be
nice
to
have,
but
we
still
have
to
figure
out
how
we
would
go
about
this
then.
A
After
this
we
are
thinking,
though
another
another
main
thing
that
we
are
focusing
on
is
the
current
user
reconciliation.
So,
as
I
said,
the
user
reconciliation
is
the
stuff
that
happens
after
the
base.
Reconciliation.
Basic
translation
is
like.
Oh,
the
operator
basically
sets
a
base
for
the
Jenkins
to
be
spun
upon.
A
So
what
do
I
mean
by
base
I
mean
all
the
config
maps
that
need
to
be
created
over
the
all
the
config
laps
that
need
to
be
created,
although
the
poor
spec
that
needs
to
be
instantiated
and
all
that
stuff,
the
user,
a
constellation
is
where
the
groovy
scripts,
the
cask
and
restore
and
backup
occurs.
So
our
main
issue,
issue
or
improvement
that
we
need
to
do
here
is
basically
modularize
the
entire
system.
Otherwise
it
acts
a
lot
like
a
monolith,
so
we
need
to.
We
are
working
on
that.
A
Another
thing,
as
you
just
saw
OpenShift
support,
is
what
we
are
working
on
so
currently.
As
of
now
this
Jenkins
image
controller
chain,
refactor
Jenkins,
see
our
reconciliation
or
deployment
instead
of
pod
is
actively
being
worked
on
and
the
other
stuff
we
will
get
to.
But
this
is
this
is
an
honor
road
map
for
this.
You
I,
hope,
I'm,
hoping
that
we
kind
of
are
able
to
come
up
with
a
good
design
and
a
good
solution
for
the
end
users
which
moves.
A
Oddly,
oh,
we
are
in
like
which,
which
would
be
enterprise,
level
customers
who
don't
want
to
move
away
from
Jenkins
and
want
to
keep
using
Jenkins,
but
it
would
be
nice
to
have
some
kind
of
overarching
operator
of
of
this
sort
to
manage
things
because
in
the
new
communities
and
communities
like
infrastructure
age
like
it's,
become
like
almost
a
necessity
to
have
so
Jenkins
of
briefly.
So
the
last
thing
quality
branch
pipeline
support.
This
is
something
we
we
will
tackle
once
the
basic
stuff
gets
over.
A
A
For
any
questions
or
feedback,
you
can
just
follow
these
and
then
know
you
can
come
to
the
overto.
Slavo
is
a
slack
where
we
can
answer
any
questions
you
have
for
the
operator
and
we
we
love
those
suggestions,
keep
them
coming
and
every
Thursday
we
have
a
community
call
I.
It
is
so
if
you
want
to
join
the
community
call
or
get
more
information
on
it,
you
can
go
over
here.
The
communities
operator,
rapper,
Jenkins,
shear
communities
of
crater
and
go
down
over
here
the
very
end
you
can
see
a
part
called
every
Thursday.
A
B
C
A
C
A
That
we
are
actually
trying
to
figure
out
a
process
to
like
keep
keep
it
coming
like
half
version
specific
Jenkins,
operatory
images
Oh.
What
you're
doing
right
now
is.
We
are
just
pushing
images
which
are
rich,
which
we
just
run
on
the
latest
one
because,
but
as
we
so
currently
we
are
in,
we
are
not.
A
A
A
So
if
you
have
an
image
that
you
want
to
update
to,
so
if
you
consider
of
like
image
1
and
image
2,
so
you
are
at
one
right
now
with
plugins
set
1
and
you
have
you
want
to
go
to
image
to
which
has
increased
Jenkins
version
and
plug-in
set
2,
which
is
updated,
plug-in
said
you
would.
All
you
have
to
do
is
use
this
image
controller
in
the
operator.
This
is
a
new
feature
that
will
roll
out
soon.
A
You
should
be
able
to
just
say
something
like
you
like
image,
image,
build
or
image,
deploy
or
something,
and
this
this
deployment
will
be
replaced
by
this
new
deployment
of
for
these
Jenkins
board
without
any
damping.
So
to
fix
this
issue,
that's
why,
as
I
said
earlier,
we
need
to
move
from
the
pod
to
the
deployment
way
of
doing
things
currently.
So
this
first
thing
or
that
I
mentioned
for
the
roadmap
this-
and
this
need
to
be
completed
for
being
able
to
achieve
that
through
the
operator.
B
B
C
Think
the
bothers
so
the
valve
on
this
slide,
you
mentioned
air-gapped
environments
and
I-
think
Erica
Jenkins
is
already
challenged.
I
can't
imagine
the
challenge
doing
air-gapped
kubernetes.
Are
there
any
insights
you
could
share
with
the
audience
about
what
your
experience
has
been
learning
how
to
do
air-gapped
environment
support
or
what
are
the
things
you
would
guide
people
who
are
developing
for
kubernetes
to
think
about
hey!
Consider
this
in
case
someone
is
trying
to
be
air-gapped
with
your
deployment.
A
So
I
I
for
one
have
an
especially
worked
on
Oh,
explicit,
air-gap,
environment
of
sorts,
but
in
OpenShift
we
kind
of
try
to
what
we
do
is
we
get
all
the
resources
in
a
cluster
like
adara
needed
for
a
cluster
and
keep
it
localized
to
that
cluster.
So
we
or
download
all
the
images
from
before
so
in
the
or
in
the
cluster
of
the
cust
customer
or
the
user,
and
we
keep
it
installed
over
there
and
a
next
time
when
there
is
an
open
shift
or
update
to
open
ship.
A
Now,
with
the
operator
itself,
the
Jenkins
operator
itself,
the
problem
of
air
gap
is
mostly
with
all
the
plugins
I
think,
because
I
am
not
the
best
guy
to
talk
about
the
sacrum
would
would
know
much
better,
but
the
main
problem
is
of
the
plugins,
because
right
now,
whenever
a
new
Jenkins
image
spins
up,
it
tries
to
install
out
of
all
the
plugins
or
by
downloading
it
from
the
Internet.
Now,
in
a
case
where
someone
cannot
download
all
those
plugins,
they
would
need
those
plugins
baked
into
their
image
from
before.
A
This
is
one
way
of
like
air
capping
it
because
then
just
there
is
no
need
for
the
Jenkins
to
install
anything
else.
At
that
point
in
time,
correct
and
the
other
way
to
air-gap
it
in
case
there
is
a
need
for
plugins
is
to
have
like
a
local
update
center
for
that.
So
if
there
is
a
local
update
center,
the
Jenkins
instances
can
just
connect
to
it
and
then
update
it
from
there.
B
Yeah,
look
what
this
under
it,
what
we
generally
recommend
no
updates,
and
that
has
its
own
limitations.
For
example,
there
are
two
installer
plugins
which
can
resemble
million
or
Gradle
from
the
Internet,
and
in
this
case
we
didn't
generate
look
what
did
centers
for
these
tools,
it's
totally
possible,
but
right
now
all
these
centers
on
the
reference.
A
A
C
And
then
then
I
had
another
one
is:
can
you
control
the
resource
consumption
that
Jenkins
is
allowed
to
use
so
that
one
of
your
users
does
not
inadvertently
allocate
hundreds
of
agents
or
or
is
that
not
a
common
common
problem?
You
have
to
confront
how
how
do
you
deal
with
resource
consumption
allocation
using
the
operator?
That's.
A
C
C
Was
what
I
was
wondering
is
if
I
define
a
declarative
pipeline
that
allows
that
tries
to
do
50
things
in
parallel
and
suddenly
is
over
taxing
my
kubernetes
cluster
or
my
openshift
cluster?
Is
there?
Is
there
a
defense
for
that,
or
is
it
rather
allow
qu
the
OpenShift
safety
measures
that
are
already
there?
They
are
enough
to
protect
it.
So.
A
There
are,
there
are
measures
on
community
side
too,
like
oh,
oh,
like
what
is
the
maximum
amount
of
requests
and
requests,
so
the
a
certain
user
can
make
or
in
terms
of
Oh,
CPU
and
memory,
but
or
rather,
or
how
much
request
the
port
can
make
through
it.
This
definitely
needs
to
be
looked
into
further,
but
kubernetes
has
it
from
before.
A
How
that
would
translate
to
a
user
is
something
need
to
figure
out,
because
the
operator
would
use
the
service
account
for
the
operator
and
is
there
some
kind
of
impersonation
that
we
are
talking
about?
That
would
happen
in
the
middle.
This
is
something
or
maybe
we
need
to
figure
out,
because
so
then,
when
the
user
would
use
a
communities
instance,
they
would
basically
impersonating
else,
though
the
service
account
would
be
impersonating
as
the
user,
and
then
it
would
try
to
execute
everything.
C
So
I
think
what
you're
saying
is
that
kubernetes
has
a
very
already
a
very
good
safeguard
against
the
Jenkins
service
over
allocating
resource
right
that
that
kuben
it,
but
but
the
there's
not
an
immediately
obvious
way
of
saying
I
want
to
limit
a
specific
user
who's
using
a
piece
of
that
service
did
I
did
I
understand
your
description
correctly.
Yeah.
A
C
There
was
one
more
that
just
arrived
in
the
Q&A
asking
about
is
anyone
using
the
H,
a
Gen
can
so
I
assume.
That
means
high
availability
is
trying
to
implement
high
availability
Jenkins
using
the
operator.
Their
concern
is
they
have
to
when
they
upgrade
Jenkins
or
a
plug-in.
They
have
to
restart
Jenkins.
A
A
C
Yeah
I'm
not
I'm,
not
sure
what
that
would
what
that
would
mean
in
this
context
of
H
a
Jenkins
itself
does
require
a
restart
in
order
to
upgrade
its
plugins
right.
Therefore,
that
that's
sort
of
the
nature
of
Jenkins
Oleg
do
you
have
some
insights
to
offer
there
and
what
the
question
may
in
fact
be
asking.
B
So
I'm
all
so
much
because
okay,
reheated
and
other
similar
tools
they
allow
to
achieve
itchy
but
to
achieve
achieve,
but
provisioning,
multiple.
Yet
so
the
high
availability
by
provision,
multiple
masters.
So
basically
you
have
CDs
and
on-demand.
For
example,
when
you
modify
the
instance,
then
you
can
provision
new
Jenkins
with
new
configuration.
A
B
Yeah,
usually
it's
about
bit
or
about
instance,
going
down
so,
for
example,
what
will
be
present
in
a
few
years
ago
and
drinks
deliver
some
it's
multi-tenant
Jenkins,
so
one
basic
drink,
its
mustard
consists
of
multiple
instances.
We
share
context
and
one
one
instance
goes
down.
Then
you
don't
notice
that
in
this
case,
I
think
it's
rather
rapid
related
to
updates,
but
in
a
breed
of
for
a
Jenkins
master
in
the
current
six
Iroquois
restart,
so
you
can
achieve
for
eg
only
system
level,
but
not
on
the
level
of
for
a
particular
master.
A
C
B
C
B
Okay
looks
like
there
is
no
more
questions
again,
we
will
stop
with
the
recording
and
after
that
we
were
just
don't
whisper
admissions
to
everyone
who
is
on
the
call,
so
we
can
have
more
discussion
of
the
record
Phoenix
again,
for
we
have
for
the
presentation
it's
much
appreciated
and
we
are
looking
forward
to
see
how
inspirator
evolves
and
are
working.
If
you
just
go,
get
bail
soon,.