►
From YouTube: 2021 05 03 Docs Office Hours
Description
Jenkins on Kubernetes project - Y.R. Sudhakar and Jenkins Configuration as Code plugin blog post from Dheeraj Singh Jodha.
A
Even
if
sudacar
is
not
here.
Let's
talk
about
it
anyway,
just
to
get
your
insights
on.
Where
should
the
kind
these
kinds
of
information
be
put
etc?
Then
I
put
a
placeholder
in
for
j
cask
for
dhiraj.
She
code,
africa.
I
think
meg
you
and
I
should
probably
talk
through
and
kristen.
We
should
talk
through
what
that
was.
Oh,
I've
got
a
and
I've
got
the
retrospective
scheduled.
A
retrospective
poll
has
been
sent.
A
A
So
so
kristin,
the
one
that
I
think
is
is
would
be
most
powerful
for
us
to
discuss
with
you.
Here
is
the
jenkins
on
kubernetes
topic.
So
one
of
the
things
that
sudakar
suggested
was
hey.
Let's
include
some
additional
kubernetes
concepts
in
the
installing
jenkins
on
kubernetes,
deeper
intro
to
the
helm,
charts
and
then
the
the
big
one
was
use.
The
plugin
installation
manager-
and
this
is
updating
plugins
with
plugin
installation
manager
and
managing
plug-in
updates
as
code
right,
pull
requests
etc.
A
C
A
A
A
D
B
B
C
A
A
B
A
B
A
B
Get
started
okay,
so
I
would.
I
would
think
it
would
be
nice
if
that
section
made
a
mention
it
shouldn't.
I
mean
the
jks
documentation
would
be
separate,
but
just
because,
if
you're
doing
this
stuff
you're
going
to
hear
about
that
and
just
the
questions
say
you
can't
do
them
just
what
you
said
and
I
loved
you
I
just
I
don't
have
to
talk
to
you
about
the
word
brittle.
I
just
got
pinged
on
it.
B
A
A
Okay
good,
so
then,
then
then,
we've
got
installing
jenkins
on
kubernetes
agreed
using
plug-in
installation
manager
into
the
plug-in
managing
plug-ins
page.
Now
then,
his
next
proposal
was
using
configuration
as
code
and
now
we're
back
to.
I
would
love
to
have
configuration
as
code.
Where
do
we
put
it?
Does
it
belong
in
system
administration
because
of
its
its
ability
to
configure
things
all
the
way
up,
so
is
it
closer
to
reverse
proxy
config
and
monitoring
and
backup
and
restore,
or
is
it
closer
to
tool,
management,
plug-in
management
and
time
zones.
C
C
D
A
A
Good,
okay,
all
right,
okay
and
then
the
the
final
topic
was
the
kubernetes
solutions.
Page
and
the
solutions
pages
are
here,
and
this
is
a
case.
We
don't
even
have
a
kubernetes
solution
page.
Yet
so
we've
got
java,
we've
got
python,
but
nothing
for
kubernetes.
So
this
has
been
one
absolutely
it's.
It
just
goes
in
there.
B
A
A
B
A
B
A
Yeah
and
so
so
meg,
I
guess
my
question
was
okay:
we've
got,
we've
got
a
page
page
now
on
managing
nodes
or
managing
agents.
What
we
don't
have,
though,
is
any
concept
of
ephemeral
agents
and
static
agents.
That's
been
presented
in
the
documentation
and-
and
that
was
one
that
that
that
lack
of
that
conceptual
gap
right
now
seems
like
a
great
thing
to
put
inside
managing
nodes.
A
A
A
B
Yeah,
I
think
so.
I
have
one
quick
question.
I
don't
know
we
need
to
go
into
it,
but
something
that
I
see
is.
It
might
be
nice
to
end
that
section
with
a
tour
of
managing
jenkins
that
just
has
notes
about
these
tasks.
You're
going
to
do
you
know
this
is
going
to
be
like
backup.
I'm
thinking
is
going
to
be
quite
different
on
kubernetes
than
it
would
be
on
a
traditional.
You
know,
and
we
don't
we
don't
necessarily
want
to
rewrite
that.
But
say
you
know
or
unless
it's
something
that
it's
just
totally
different.
B
B
C
B
E
A
F
F
F
A
And
so
specifically,
when
you're,
when
you're
describing
developer
documentation
for
jks,
this
is
things
like
how
to
make
my
plugin
able
to
use
jcask?
Is
that
the
kind
of
thing
that
you're
you're
envisioning
there
share
with
us
further
on
the
kinds
of
things
you'd
see
in
developer
documentation?
Would
it
be,
I
want
to
add
some
new
feature
to
jcask,
or
is
it
rather?
I
want
my
plugin
to
support
jcask.
F
F
A
Good,
okay
and
so
that
first
one
using
configuration
using
configuration
as
code
seems
like
an
a
good
one.
We
cover
it.
We
would
like
to
cover
in
the
jenkins
on
kubernetes
work,
so
yeah
agreed
so
see
jenkins
on
kubernetes
project.
So
that's
a
good
one
and
that's
that's
focused
focused
on
on
users,
so
at
least
is.
Did
I
understand
you
curriculum?
You
said
using
jcask
in
my
instance.
That's
me
as
a
jenkins
administrator.
How
can
I
best
use
configuration
as
code
to
help
my
life
be
better
and
easier.
F
A
A
A
A
A
B
And-
and
I
don't
know
what
the
valid
values
I
mean
we
kind
of-
we
already
lied.
It
was
all
in
the
background
that
the
ui
would
keep
you
from
doing
something
really
stupid
and-
and
it's
just
you
know
the
for
the
first
time
somebody
demonstrated
this
to
me.
They
went
through
all
the
screens
on
the
configuration
that
I'd
seen
a
hundred
times
and
it
all
looked
fine,
and
then
they
opened
up
this
file
and
there's
all
now
granted
a
certain
amount
of
it.
B
A
Yeah
and
I
think
what
you're
what
you're
describing
is
the
reality
that
we
we
we
rely
very
nicely
on
view
configuration
to
tell
me
this
the
setup
of
my
current
configuration
and
to
give
me
a
valid
configuration.
So
it
in
fact
knows
this
is
how
I
define
a
jdk
installation,
and
it
looks
like
that
and
I
can
copy
and
paste
that
right
into
my
configuration
file.
A
C
B
A
A
We're
going
to
change
the
git
configuration,
and
so
I
go
in
here
and
I
I
make
changes.
Okay,
I'm
going
to
it's
now
going
to
be
get
2
is
the
program
that
and
that
will
now
be
saved
the
next.
When
I
click
save
here.
That
thing
will
then
appear
as
a
change
and
I
can
go
grab
it
out
of
the
out
of
that
saved
file.
A
C
B
B
A
A
C
A
C
A
Let's
talk
retrospective
one
more
time,
kristin
you
were,
you
were
in
the
friday
session,
though
weren't
you
yep,
yep,
yeah,
so
we've,
I
hope
well,
but
here
here
again,
here's
a
chance
for
us
to
look
one
more
time.
So
we
what
we
did
during
the
friday
session,
we
asked
each
of
the
the
those
attending
so
onigne
esther
and
cynthia
each
of
the
three
attended
and
we
asked
them
specific
questions.
A
B
A
C
A
Started
a
section
here
in
this
document
on
retrospective,
so
here
it
was
okay,
everybody
give
your
comments.
What
went
well
and
what
were
the
problems
you
encountered
as
a
contributor
as
a
mentor,
and
what
should
we
do
differently
right?
What
should
we
improve
right
now?
I'm
I'm
happy
to
add
more
text
here
if,
if
meg,
if
you
would
like
to
give
comments
or
kristen
you're
welcome
to
do
them
here,
I
can
type
for
you.
B
A
B
A
B
And
then
for
us
now
I
mean
we
could
have,
should
we
have
at
the
beginning,
started
out
and
said:
okay
you're,
for
we
should
have
sent
benchmarks
too
or
milestones.
That
sort
of
we
expect
this
to
happen.
So
so
we
weren't
there
in
the
second
week
on
ninja
had
submitted
20
prs
and
a
couple
of
the
others
were
still
reading
the
documentation.
B
B
Sort
of
talked
about
in
the
end
should
just
I
mean
and
there's
two
ways.
One
of
it
is
that
maybe
we
want
to
learn
to
learn
that
in
open
source,
you
get
some
rough
instructions
and
you
go
out
and
you
figure
it
out
and
we're
very
you
know
and
call
for
help
if
you
do
if
it
doesn't
work,
but
but
they're
young,
this
is
all
new.
B
You
know
I
think
most
of
them
were
new
to
devops
and
to
jenkins
a
bunch
of
them
were
new
to
java.
There
was
so
much
stuff
that
it
might
have
helped
if
they'd
seen
you
know
this
is
what
you're
gonna
do
first
and
then
we
would
have
had,
and
the
big
one
that
we
should
have
hit,
then
is
when
they
got
to
the
point
of
adding
new
information.
Is
how
do
you,
research
this.
B
B
So
they
can,
they
can
ask
they
should
review
the
code
and
see
what
they
can
figure
out
from
the
code.
I
get
the
feeling
that
people
don't
very
often
add
comments
that
are
useful
right
and,
as
a
writer
I
love
admin,
are
developers
who
put
copious
comments
in
their
code,
but
they're
few
and
far
between
yeah
look
at
the
code.
Look
for
comments,
talk
to
the
pipeline
owner
or
maintainer,
or
the
plug-in
maintainer
and
google
out
there
and
see
what
you
find
in
other
blogs
and
stack
flow
and
stuff.
E
B
B
B
Right,
I
mean
another
thing
that
I
wonder
is
if
we
should
give
them
like
the
first
week
is
getting
set
up
and
getting
everything.
Maybe
we
should
have
a
second
week
where
they
work
in
pairs.
I
don't
know
if
they
would
like
that,
that
I
mean
some.
Some
of
these
plug
games,
like
a
lot
of
these,
are
big
enough,
that
the
two
of
them
could
work
on
it
together
if
they
would
like.
Would
they
like
that?
I
don't
know.
C
D
B
C
Versus
like
more
of
a
student
status-
and
I
mean
I
mean
that
mo
from
the
idea
of
like
okay
go
out
and
discover
versus
very
much
a
like-
hey,
like
let's
get
onboarded
quickly
or
like
or
like
a
little
bit
more
of
a
handholding
onboarding
process,
because
I
I
did
I
like
me
personally
being
the
mentor.
I
think
I
you
know
it's
hard
to
remember,
sometimes
how
it's
like
to
join,
openly,
join
communities
and
you
know,
speak
or
talk
on
channels.
It's
really
intimidating
at
first.
It.
D
C
It's
very
very
intimidating,
especially
if
you
are
coming
in.
As
you
know,
a
student
you're
like
oh
my
gosh.
These
people
have
so
much
so
much
more
experience
like
what.
If
I
come
in
and
say
something
that
you
know
they
may
not
be
right,
I'm
embarrassed,
and
it's
just
I
mean
like
we
don't
get.
You
know
we're
all
like
yeah
like
come
on
in
and
join
and
talk,
but
it
just
having
that
reinforcement
and
just
maybe
a
little
bit
more
personal
encouragement
might
encourage
them.
C
B
C
Right,
I
agree.
I
agree
back
that
this
would
have
it
feel
like
we're
just
starting
to
get
going
and
just
with
those
like.
Oh
so
you
have
those
sessions
a
little
bit
earlier
and
also
just
kind
of
maybe
also
that
will
help
with
the
perspective
of
not
really
knowing
where
they
are,
because
it
took
a
long
time.
To
even
I
mean
the
documents
were
awesome
mark
that
you
set
up
like
they
were
so
great,
but
it
would
help
maybe
have
them
communicate
where
they
are
kind
of
as
a
check-in
basis.
C
C
C
B
A
The
the
duration
is
absolutely
a
choice
that
they're
making
they
chose
30
days
for
this
one
intentionally
because
they
wanted
to
avoid
collision
with
google
summer
of
code,
and
they
were
very
wise
to
do
that
because
if
they
told
me
we
want
to
do
two
months,
I'd
have
had
to
say
I'm
sorry.
I
cannot
give
you
the
month
of
may,
because
I
will
that's.
I
begin.
We
begin
the
mentoring
for
google
summer
of
code
mid-may.
B
A
C
B
B
B
Just
the
nature
of
the
learning
curve
that
maybe
two
months
would
be
a
better,
so
we
really
we
had
that
good
third
week
and
then
the
fourth
week
we're
starting
to
do
retrospectives
and
wind
down.
So
we
really
ended
up
with
only
kind
of
one
week
now
we
might.
We
did
things
differently.
We
might
have
gotten
two
weeks
out
of
that,
but
that's
still
not
a
lot.
A
A
What
if
we
asked
each
participant
to
show
something
at
every
mentoring
session,
you
must
show
me
a
screenshot
of
something
or
share
your
screen
to
show
how
you're
doing
this
as
a
way
to
encourage
them
to
interact
with
us.
But
even
then
that
may
be
too
simple.
They
they
won't
interact
and
they
just
show
it
and
say:
they're
done.
B
B
Luckily,
because
I
I
had
stuff,
I
could
have
showed
what
it
what
we
were
talking.
I
don't
even
know
what
it
was.
I
could
have
done
it,
but
I
really
wanted
one
and
onyonye
jumped
in
and
she
did
it
and
did
a
brilliant
job
of
it,
but
I
had
a.
I
also
had
a
feeling
the
others
rapidly
started
to
get
scared
because
they
were,
I
think
they
had
a
little
bit
of
a
notion
that
they
were
competing
with
each
other
and
you.
C
B
A
Not
not
not
effectively
right
telling
telling
chico
to
africa
hey
in
addition
to
the
500
that
you're
giving
them
for
this
one
month
of
work.
You
also
need
to
provide
them
equipment
that
they,
I
don't
think,
there's
any
way.
It
would
work
right.
There's
they're,
just
not
going
to
be
able
to
do
it.
They
they
pre-qualify
them
to
assure
they
have
adequate
equipment,
and
in
this
case
the
adequate
equipment
worked.
Okay,
but
adequate
internet
is,
you
know,
hey
it's
spotty
internet,
it's!
It's!
The
internet.
C
B
C
A
Right
right,
right
and
and
the
idea
is,
let's
motivate:
let's
encourage
that
hey,
we
we're
all
going
to
encounter
problems
and
everybody's
we're
going
to
have
many
of
the
problems
will
be
different,
unique
to
you
and
we
talk
okay.
Well,
and
I
wonder
if
that
maybe
we
do
it
two
steps.
We
take
cynthia's
idea,
an
icebreaker
hi,
I'm
cynthia,
here's
a
little
bit
about
me
and
here's,
my
screenshot
and
the
problems
I
had
and
then
we
go
to
the
next
one
hi,
I'm
so-and-so
and
here's
my
thing.
B
A
C
B
B
A
B
B
A
Well,
and,
and
that
one
echoes
with
on
nine
and
cynthia,
both
commenting
hey,
they
wanted
to
talk
with
a
broader
set
of
people
in
the
jenkins
community.
Now
had
we
pre-registered
or
pre-subscribed
plug-in
maintainers,
we
might
have
already
achieved
that
one
so
so
that
that
one
may
be
achieved
just
by
okay.
A
If
we're
gonna,
if
we're
gonna,
invite
you
to
work
on
a
plug-in,
we
need
to
be
sure
that
the
maintainer
is
agreed
to
assist
us
during
this
one
month,
right,
yeah
and-
and
I
confess
the
reason
I
didn't
bother
to
subscribe,
the
plug-in
maintainers
was-
I
falsely
assumed
that
hey
this
is
just
documentation.
They'll,
of
course,
accept
it
and
immediately
merge
it,
and
that
was.
I
was
just
wrong
that
that
was
not
it
at
all.
B
And
even
if
they
did
that's
from
the
writer's
standpoint,
we
didn't
have
the
research
support
and
that's
what
we
really
because
I
mean
let's
face
it.
You
and
oleg
and
angelique,
and
chris
could
look
at
most
these
pr's
and
make
a
reasonably
good
guess
as
to
whether
or
not
they
were
accurate
and
okay
to
merge
right.
B
C
C
C
B
A
E
A
A
B
A
A
A
C
A
A
And
proposed
coordination-
google
doc
is
right
here
and
it's
got
a
segment
in
it
for
the
documentation
track
all
right,
and
so
I
had
put
into
this
google
season
of
docs
now
it'll
have
to
be
yeah.
It's
got
jenkins
and
kubernetes.
We've
already
talked
about
that
here.
Onboarding
improvements
and
content
improvements
were
topics
I
had.
If
you've
got
other
topics
you'd
like
please
propose
them
as
suggestions
to
this
document.