►
From YouTube: Jenkins X Office Hours (2018-08-09)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
It's
a
it's
a
community
thing,
so
more
feedback
and
more
involvement
from
anybody
other
than
people
that
talk
too
much,
but
most
of
us
on
the
call
then
it'd
be
really
good,
yeah,
so
I
think
today,
but
we've
got
we've
got
probably
two
things
we
can
show
that
Gareth's
can
to
maybe
talk
to
some
of
the
work
he's
been
doing
around
I.
Think
a
tutorial
for
for
Jenkins
exons
uke
I
could
probably
talk
through
some
of
the
prior
stuff
that
I've
been
been
looking
at.
A
B
I'm
highly
caffeinated,
today,
very
very
caffeinated
indeed,
you've
been
through
this
with
Steph
around
chat,
Museum
I
have
been
doing
I've
been
doing
a
variety
of
random
things
yeah,
so
the
chart
museum
stuff
was
interesting,
is
actually
a
really
good
way
into
not
only
the
sort
of
the
projects
itself,
but
also
sort
of
like
our
deployment
and
like
our
infrastructure
and
how
maybe
it
differs
from,
like
a
you,
know,
sort
of
linear
install
so
yeah
I
kind
of
rolled
all
of
that
stuff.
Up
the
background
to
this
is
basically
we
one
we
serve.
A
D
Yeah
sure,
okay,
apologies
because
I'm
sat
in
quite
a
noisy
place.
Cardiff
City,
Centre
environment,
trying
to
cheer
on
Guerin
Tomas
used
about
to
do
is
a
victory
lap
of
Cardiff
for
their
Tour
de
France,
so
I'm
sat
in
the
quietest
place
that
I
can
find
everywhere
to
really
see
so
yeah
I've
been
working
on
a
tutorial
that.
D
Come
through
yeah
I
can
see
that
okay
great,
so
these
at
the
moment,
we've
got
two
tutorials
up
both
based
on
TKE
and
they
both
use
for
the
cloud
shell
feature,
and
they
seem
to
be
fairly
recent
feature
that
we've
added
to
add
inbuilt
tutorials
into
cloud
shell
I'm
just
going
to
show
you
one
of
those
now
so
we
click
on
one
of
these.
It's
gonna
launch
your
cloud
trap
assumes
you
already
the
loved
him,
then
account
of.
D
Boots
to
the
right
place,
if
you've
already
got
the
second
term,
you've
already
got
it
open,
it's
gonna
ask
you
to
update
it
and
then
it
more.
It
actually
loads
the
tutorial
on
the
right-hand
side
of
the
page,
and
it
allows
you
to
rethink
so
really
started
it,
because
I
have
dismissed.
That
and
I
can
start
bouncing
through
this
tutorial,
and
it
gives
me
prompts
and
what
I
need
to
do.
You
can
make
these
as
complex
as
you
need
to
so.
D
A
E
D
An
example
when
I
think
well
I'm
a
really
nice
and
people
do
as
you
can,
click
on
this
basting
cloud
share
button
and
it
will
actually
copy
and
paste
the
command
into
your
shell.
You
just
hit
enter
and
it
runs
and
that's
going
to
go
off
and
install
cloud
shell,
sorry
little
JX
with
the
latest
version
and
any
other
dependencies
there.
It
takes
about
30
seconds,
roughly
maybe
a
little
bit
less
today
and
once
that's
complete.
D
It
seems
like
a
really
really
powerful
feature
and
something
that's
quite
new
in
I
haven't
there's
a
few
things
where
you
seem
to
be
able
to
launch
like
a
local
dev
proxy.
So
if
there's
something
you
are
booting
under
or
inside
cloud
shell,
you
could
then
get
it
to
open
up
a
web
browser
window
to
that
that
local
app
but
I
haven't
got
too
far
into
that
yet,
but
in
terms
of
just
generally
building
out
tutorials
I
think
it's
a
it's
a.
A
Yeah,
it's
really
good
news
for
first
and
the
workshops
we've
been
running
and
for
people
who
just
want
to
get
going
fast
without
having
to
download
any
binaries
binary
or
if
they
have
some
odd
restrictions
as
well.
So
I
love
people,
but
I
have
locked
down
laptops
corporate
laptops.
This
is
a
good
another
good
way,
big
way
to
kind
of
keep
the
toys
at
Jenkins
X.
Okay,
oh.
D
B
B
So
you
basically
get
you
obviously
get
the
chart.
Museum
itself
like
the
essence
of
the
destructive
API
is
actually
you
can.
You
can
obviously
query
that
in
order
to
push
stuff
up
to
it,
but
if
you
make
the
putter
the
bucket
public
with
that
little
sort
of
sync
job
running
in
the
background,
it
means
that
you
can
literally
just
give
people
the
public
address
of
the
bucket
itself.
So
in
terms
of
get
requests
and
with
that
kind
of
stuff,
you
don't
even
actually
need
chalk
museum.
B
B
Yes,
so
that
was
all
doubtless
will
done.
Other
things
I've
done,
oh
yeah,
I
did.
This
was
just
because
I
saw
a
couple
of
people.
It
was
partly
for
my.
It
was
probably
for
myself
just
because
I,
like
the
idea
of
having
I've
been
able
to
sort
of
debug
specific
versions,
and
it's
particularly
people
that
are
committing
and
doing
piles
and
stuff,
like
that.
B
Also
I
saw
a
couple
of
issues
raised
about
Jack's
version
on
on
the
Jake's
repo,
so
I
kind
of
rewrote
part
of
the
makefile
yesterday,
and
also
added
a
bunch
of
tests
and
other
stuffing
to
jx4
for
the
versioning.
So,
basically
now
we,
if
you,
if
you
are
a
contributor,
then
if
you
clone
the
Jax
repo
and
you
start
building
locally.
B
Basically,
if,
if
your
master
branch
is
on
the
tag,
then
you'll
just
get
tagged
version,
but
if
it's
not,
then
you'll
get
a
a
suffix
dev
version
with
the
the
dev
suffix
and
and
commit
hash.
So
you
can
always
see
which
version
you're
using
and
you
won't
get
prompted
to
update
constantly
anymore,
if
you're,
if
you're
on
a
death
build
which
is
just
kind
of
like
a
little
thing,
really
that
I
just
thought
would
be
nice
to
have
nice
having
their
great.
B
C
A
B
I
think
this
is
yeah
just
yeah
one
other
little
thing
which
just
sort
of
developer
ease
type
thing
which
I've
just
been
quickly
playing
around
with
earlier,
which
was
shell
completions,
because
JX
is
quite
a
sort
of
complex
binary.
We've
got
lots
of
commands
now
and
it's
really
different
to
remember
and
type
so
I,
just
added
in
a
little
basically
another
command
that
lets.
You
generate
fashioned
Zoosh,
completions,
I
thought.
B
B
Imagine
that
the
maxis
happenings
are
pretty
pretty
scared
about
giving
out
surviving
level
kind
of
privileges
to
everyone.
So
it
seems,
like
seems,
like
a
you
know,
had
a
good
conversation
from
unity
about
you
know
what
what
they
would
like
and
what
they
want
to
see
in
it,
and
it
definitely
seems
like
they.
You
know,
having
kind
of
even
just
sort
of
fairly
fairly
basic
set
of
role
losing
in
the
beginning.
Maybe
you
noted
before
just
kind
of
like
admin
developer.
B
B
A
Awesome,
no,
we
look
forward
to
see
no
thanks.
You
so
is
there
anybody
else
on
one's
there
to
share
anything.
I
can
show
some
stuff
around
proud,
but
given
the
opportunity
for
anybody
else,
James,
don't
you
be
quiet.
C
C
I
think
it
was
announced
after
the
last
office
hours
so
in
between
the
last
office
hours
in
this
office
hours
is
now
a
care
native
thing,
which
is
basically
a
talk
like
a
group
of
bits
of
open
source,
backed
by
the
usual.
You
know,
red
hat.
We
will
pivot
all
ordinary
service
and
the
idea
is
a
double
source
project.
Around
serverless
is
the
main
focus
and
it's
trying
to
have
a
Cuban
--'tis
native
service
platform,
really
that
runs
on
top
of
Cuban.
C
It
is
in
the
normal,
kubernetes
modular,
microservice
kind
of
way,
there's
really
three
parts
just
to
Kennedy.
If
there's
the
webhook
piece,
there's
the
serving
piece
and
there's
the
build
piece,
the
serving
piece
is
using
SEO,
so
that's
kind
of
cool,
so
it's
combining
sto
with
a
service
kind
of
sir
living
mechanism.
So
you
could,
for
example,
have
no
content
is
running
and
then
they're
HTTP
request
and
come
in.
You
can
then
scale
up
a
container
to
service
a
request
and
then
tear
it
down
again.
Nice
elastic
serverless
style,
running
of
containers.
C
So
that's
really
cool
the
bit.
That's
really
interesting
for
my
Jenkins
X
perspective
is
care
native,
but
can
you
to
build
I
should
say
K
native
build
is
very
similar
to
things
like
code,
ship
and
circle,
CI
and
various
of
the
CI
tools
and
concourse,
and
that
almost
everything
apart
from
Jenkins
these
days,
tends
to
use
docker
containers
and
simple
steps
in
time.
If
it
says
I
go
again,
it's
very
similar.
You
define
a
pipeline
in
terms
of
steps.
Each
step
is
a
docker
container
in
the
command
in
the
container
and
you
chain
them
together.
C
So
he
follows
that
kind
of
similar
patterns
and
lots
of
CI
tools.
That's
out
there.
Most
particularly
interesting,
though,
is
it's
a
fairly
small
controller.
It
takes
a
cid
to
define,
builds
and
then
he's
got
the
control
of
it
turns
those
see
how
these
into
into
pots.
What's
really
interesting,
which
I
found
quite
surprising
when
the
first
saw,
but
then
the
more
I
thought
about
the
more
awesome
it
appears.
C
Kennedy
build
is
turned
into
a
single
port
and
each
step
is
an
init
container
in
the
container
so
that
each
step
is
then
discarded.
It
runs
until
the
Cuban
AIDS
waits
for
the
unit
contento
to
start
and
complete
each
init
container
has
a
exit
code,
unique
passes
or
fails,
and
then,
if
it,
if
it's
good,
it
goes
to
the
next
step
next
step
next
step,
so
he's
kind
of
really
using
Cuban
aids
to
implement
the
pipeline
engine,
which
is
kind
of
interesting,
because
the
building's
just
a
regular
pod
there's
nothing.
C
C
Incidentally,
the
command
JX
logs
we've
had
for
a
while
into
the
show,
so
there's
a
command
Jaya
clocks,
which
lets
you
iteratively
output,
the
log
of
a
pod,
and
usually
you
give
it
like
the
name
of
a
deployment
or
something
and
it'll
pick
the
newest
pod
for
deployment
and
tailor.
Log
I
did
a
patch
last
week
to
Jake's
logs,
which,
if
you
want
to
tail
the
logs
of
ki
native,
you
just
do
J
X
logs
and
then
give
it.
The
label
name
build
name
which
is
the
current
default
level
under
care
native
bill
pod.
C
Then
it
will
basically
find
the
latest
kennedy
build
pod
and
then
log
each
in
it
content,
knowing
that
there
was
each
step
in
order,
so
you
can
just
tale
a
log
ready
simply
because
that's
one
of
the
problems
right
now
is
trying
to
find
out
what
the
logs
are
for.
Kiddie
activity
is
not
immediately
obvious,
so
anyways,
that's
a
bit
of
a
rumble
kennedy.
C
It
looks
really
interesting,
given
the
backing
of
Kennett
Eve
and
it's
the
server
less
and
serve
unless
he's
pretty
hot
right
now,
in
general
software
development
scene,
I
can
see
lots
of
people
investing
a
lot
of
time
and
effort
into
polishing
care
native
right.
Now,
it's
very
simple
and
basic,
and
you
just
run
a
couple
of
commands
and
that's
kind
of
it
cave
itself
doesn't
have
a
weapon
thing
yet,
which
maybe
segues
into
your
stuff
James
be
proud,
but
he
does
look
like
if
I
was
a
betting
man,
I
kind
of
said.
C
This
is
looking
like
a
long
term
strategic
pipeline
engine.
What's
interesting
is
you
can
embed
it
in
Kennedy
build
any
little
tool,
whether
it's
a
shell
script,
a
jenkees
file,
any
kind
of
language
or
processing
engine
or
whatever
it
can
be
bash
scripts?
You
could
be
Perl
Python,
PHP
whatever,
so
this
is
just
orchestrating
the
high-level
docker
images.
The
actual
detail
of
those
images
could
do
whatever
you
want.
C
The
other
thing
that's
interesting
by
the
way
about
kinetic
versus
things
like
Argo,
if
using
Argo,
each
each
step
is
a
separate
physical
pod
and
so
that,
if
you
want
to
share
state
between
steps,
you
have
to
like
sync
everything
to
s3
your
menu
or
something,
and
then
sync
it
back
again.
The
next
step,
with
connective
of
Kennedy
build
pod
is
all
the
steps
are
in
one
pod
and
each
step
has
a
workspace
folder,
which
is
mounted
in
the
air
for
every
unit
container.
So
you
can.
C
You
can
just
share
content
between
each
steps
without
doing
anything
non
sinking,
anything
which
is
kinda
nice
Kennett.
If
is
really
interesting,
it's
definitely
one
to
watch.
Another
thing.
Well,
I
should
have
probably
got
these
links
ready.
Well,
I'll
tell
you
what
shall
I
switch
to
you?
James
and
you'd
talk
about
prowl
and
then,
when
that's
finished,
I'll
mention
some
of
the
other
bits
and
bobs
in
the
Kennedy
jinkies
ex
world.
Yes,
I
didn't
talk
about
this
and
I've
got
I'll
need
to
look
at
the
URLs,
so
I
can
show
you
my.
A
A
So
so
you
could
tell
me
when
you
can
see
this
yet
okay,
great
so
prowls,
really
interesting
and
one
of
the
challenges
I
think
we've
we've
been
trying
to
solve
I
think
with
around
having
pipelines
on
on
kubernetes
is
ensuring
that
we
have
a.
We
don't
have
a
single
point
of
failure.
A
It
is
proud,
proud,
is
being
used
on
by
the
communities
projects
also
other
related
projects
too,
like
sto
and
K
natively,
using
it
as
well.
What's
kind
of
interesting
is:
is
we
we're
looking
at
adding
adding
this
in?
We've
got
this
actually
running
already
for
our
own
services,
4jx
to
a
certain
degree,
I
really
want
there's
a
diagram
here.
It's
under
the
Kubla
t's
testing
for
is
the
meet,
is
the
prow
git
repository
and
there's
a
little
diagram
here?
That
will
see
this,
but
just
thought
I
wanted
to
go
through
very
quickly.
A
There's
a
lot
of
parts
of
prowl
there's
a
lot
of
terms,
lots
of
different
names
and
you
get
used
to
them.
A
lot
of
them
are
implementation.
Detail
you
junk,
as
X
are
trying
to
initially
hide
these
at
these
implementations,
but
you
can
go
down
and
have
a
look
as
usual.
If
you
want
to
so,
we
have
events
coming
through
github
say
a
pull
request
is
opened
and
we
will
that
event
is
sent
over
to
this
web
hook
handler.
This
is,
can
be
highly
available.
A
You
have
multiple
replicas,
cubing
suspect
occurs,
so
we
can
perform
upgrades,
for
example,
and
bowling
up
place
to
the
hook
handler
controller
and,
and
we
won't
miss
any
event,
come
from
get
up
now.
What
this
does
this
event
then
sends
and
creates
a
custom
resource
definition
into
Cuban,
a
tease
of
a
crowd,
prowl
job,
and
we
have
a
patroller
here
which
is
called
plank,
and
this
will
then
actually
start
up
the
pod
and
actually
perform
run
the
the
actions
in
the
prowl
configuration.
A
There
are
communities,
pots
effects,
so
you
just
other
documents
name
and
then
your
commands
that
actually
that
prowl
job
runs.
So
it's
really
kind
of
cool.
This
is
simple
highly
available,
so
we
get
them
scalable
as
well,
and
it's
being
used
by
the
way,
the
most
largest
projects
on
github
most
active
projects
on
github.
So
you
note
scaling
that
way.
A
A
A
Hopefully,
we'll
get
some
reviews
on
that
and
get
better
understanding
if
that
works,
we'll
get
that
one
most
in,
but
in
short,
we
should
be
able
to
have
in
Jenkins
X
at
support
for
prowl,
so
highly
available
web
hook,
Handler
and
the
venting
and
spinning
creating
key
native
jobs
being
able
to
actually
use
these
using
the
CLI
at
the
Jack,
Celia
or
actually
familiar
with
now.
I
can
give
a
little
bit
of
a
quick
demo.
It's
not
not
amazing,
but
I
can
just
kind
of
show
something
else.
A
So
we've
started
using
it
slightly
on
JX,
but
not
fully
implemented
yet
well,
it
does.
First
of
all,
when
you
raise
a
pull
request.
Actually
we
have
proud
plugins,
so
you
can
actually
see
we've.
Actually,
it
analyzes
the
size,
for
example,
as
labels.
Lots
of
these
controllers
actually
perform
actions
based
on
the
labels
on
the
pull
request,
for
example,
there's
some
called
tied,
which
will
automatically
merge
a
pull
request
if
it
has
all
the
appropriate
labels
and
doesn't
have
other
labels
such
as
hold
or
working
progress,
for
example.
A
So,
let's
actually
just
start
by
I've,
got
a
test
repo
pal
test
I'm
on
the
branch
I'm
going
to
create
a
pull
request
from
my
branch
written
progress,
so
I'm
going
to
give
it
a
work
in
progress
title
because
we're
gonna
show
see
one
of
the
plugins.
That
power
has
gonna,
create
a
pull
request
from
my
working
progress
branch
into
my
master
branch.
A
So
that's
going
to
go
away
and
have
a
little
think
so
that
sense
an
event
into
into
the
handler,
and
that's
then
commented
back
on
the
pool
request
we've,
because
we
had
work
in
progress
in
the
PR
title
so
actually
added
a
label
of
do
not
merge.
That
means
that
if,
if
it
was
accepted
or
approve
them,
if
it
was
all
the
correct
labels
were
added
to
it,
tied
won't
actually
automatic
merge.
It
until
that
label
has
been
removed
makes
sense.
A
We've
also
added
this.
It's
also
added
this
comment,
so
we
don't
have
a
known
as
file
in
here
yet,
but
a
known
as
file
contains
people
owners
of
the
repository
and
reviewers
that
can
actually
be
recommended
in
automatically
assigned
to
that
pull
request,
and
we
can
see
this
is
a
bit
haven't
quite
figured
out
quite
yet,
but
we've
automatically
run
the
test.
We
didn't
actually
want
it
to
run
that
straight
away.
So
I've
got
to
fix
that
off
figure
that
out,
but
the
idea
is.
A
Should
work?
Oh,
it's
already
started
here.
We've
got
a
this.
Is
a
que
native,
build
pod
that
actually
started
within
that
container.
It's
actually
cloned
the
source
that
source
code
that
pull
request.
It's
actually
running
the
unit
test
for
that
for
that
test
project,
and
then
it's
it's
successful.
So
we
should
see
that
the
status
update
should
go
to
successful
on
that
on
that
pull
request
should
go
any
second.
What's
that's
going?
A
It's
got
other
things
like
other
kind
of
seems
to
be
developer
workflow,
so
people
again
familiar
with
like
looks
good
to
me,
for
example,
I'm,
not
sure
if
I
can
actually
be
logs.
It's
my
own
pull
requests.
I'll,
see
the
status
checks
actually
passed.
The
job
succeeded
so
I'm,
just
one
about
very
quickly.
A
C
Yeah,
we're
just
gonna
show
something
really
out:
I
guess
for
the
next
office
hours.
I
should
try
a
real
demo
of
creative
with
jiggies
X,
so
I
don't
actually
have
a
real
demo
right
now,
but
I
was
just
going
to
mention
two
little
things
that
happened
last
week.
If
I
quickly
share
my
screen,
which
tie
into
what
James
is,
should
just
share
my
screaming.
We
have
a
little
controller.
C
We
have
a
little
controller
command
which,
if
you
type
J
X
controller,
builds,
we
kind
of
need
to
pack
easy
serve
as
a
hand
chart
which
we
haven't
quite
done
yet.
But
if
you
basically
run
this
command
line,
J's
controller
build
it
watches
for
all
of
the
pods
generated
by
K
negative
and
any
pods
which
start
or
stop
or
steps
happen
or
whatever.
We
basically
mirror
the
can''t
of
step
statuses
into
the
CID.
We
have
right
now
for
looking
at
pipeline
if
I
open
the
shell,
a
second
bigger
one.
C
Second
I
should
have
done
this
earlier,
make
a
bigger
big
shell
if
you
type
Jake
get
activity
and
I'll
filter
by
demo.
This
is
gonna
list
all
of
the
pipelines
which
I've
just
been
working
on
right
now,
because
he
here's
a
pipeline.
This
is
a
Jenkins
pipeline,
but
here's
a
pipeline
where
we
checked
out
some
code.
We
did
a
release,
release
there
is
there
one
and
then
we
did
the
promotion
and
blah
blah
blah
blah
usual
kind
of
stuff
and
what's
happened.
C
Just
gonna
call
should
have
turned
off
my
phone
before
this,
so
we
do
the
normal
JX
gets
activity
stuff,
which
really
is
just
using
a
Cuban.
If
you
see
are
the
end
of
the
currents,
if
you
do
cube,
CTL
get
act
will
see
here's
all
the
different
pipeline
activities
which,
if
I
look
at
my
last
pipeline,
you
TTL
get.
C
Oh
oh
I,
think
tomorrow
this
is
the
Y
Amal
of
the
CR,
the
pipeline
activity,
which,
where
we
define
various
metadata
like
what's
the
released
name,
was
the
get
URL.
What's
the
branch
was
the
tags
and
so
far,
and
also
what
all
the
steps
are
now
what
this
new
jeg
vil
controller
does
is.
C
Whenever
you
run
a
pipeline
a
kinetic
build,
we
generate
the
same
CR
DS
for
Jenkins
pipelines
and
creative
pipelines,
which
basically
means
we
can
use
one
tool
to
visualize
all
the
pipelines,
either
from
the
command
line,
all
the
vs
code
and
IntelliJ
and
Eclipse
plugins
all
use
the
sense
they
are
thee.
So
it
doesn't
really
matter
if
you're,
using
a
Jenkins
pipeline
or
a
K
native,
build
pipeline.
C
The
sense
that
developer
tooling,
the
CLI,
the
rest
api,
the
ID
plugins
and
the
copies
web
console
all
of
those
visualize
things
in
the
same
way,
which
is
kind
of
nice,
and
so
hopefully
yep.
All
the
same
tooling
should
apply
whether
using
Jenkins
for
doing
a
pipelines
or
whether
using
1080,
which
you
can
work
the
same.
One
of
the
little
thing
I
thought
I'd
mention
is
here's.
A
quick
example
of
this
is
a
kinetic
build
resource,
as
you
can
see
the
top.
It's
part
of
the
ki
native
version
and
the
kind
is
build.
C
So
this
is
a
CR
D
which
defines
a
build
instance,
and
this
is
just
the
git
repository
in
the
branch
or
whatever,
and
here
I've
just
got
a
single
step
called
release
and
I'm
using
the
Jenkins,
X
maven
builder
and
then
Li
the
step
last
week
called
Jake
step
release.
So
this
is
I'm
slightly
cheating,
I
thought.
Well,
what's
the
quickest
way
of
getting
drinkies
extra
work
in
jegi
six
pipelines
to
work
inside
k
native?
C
Let's
just
write
a
big
goober
step
that
just
as
everything
to
do
a
release
which
just
chains
together
all
of
the
internal
pipeline
steps
so
rather
than
writing
a
really
big
pipeline
and
I
just
cheated
and
just
did
one
command.
So
basically,
another
cover
is
what
that
does
is
the
same
as
I
current
Jenkins
file,
it
you
know,
sets
of
get
there's
a
clone,
it
generates
a
version
and
it
tags
everything
there
pushes
everything
and
there's
all
the
promotion.
So
that's
a
one
command
line
version
of
what
drinkies
fast
do
I.
C
Have
you
notice
it
also
mounts
Takasaki
and
sets
up
the
secret
from
Arin
settings,
but
this
entire
blob
of
Yama
works
in
Canady
for
doing
a
kinetic,
build
to
do.
Release
pipeline
projected
Zechs,
which
you
can
I,
was
quite
surprised
how
simple
this
was.
So
you
know
we
we
should
be
allowed.
Let
people
choose
really
did
they
want
to
stick
with
their
Jenkins
server
and
keep
everything
in
the
Jenkins
file
that
they
want
to
go
yeah,
ma
land-use
care
native,
all
pipelines
and
use
whichever
or
maybe
even
combine
them?
C
C
If
people
started
to
use
Kennedy
pipeline
steps,
how
could
we
maybe
make
it
simpler
to
use
the
two
things
together
to
use,
say
I
and
CD,
like
we
do
in
Jamie's
eggs,
with
configurable
steps
and
with
things
like
Bill
Paxton,
whatever
I
walk
into
this
holler
make
sure
you
have
a
little
read
offline
if
you
like,
but
the
basic
idea
is
prototype
code
that
lets
you
take.
We
have
a
Jenkins
XAML
file,
which
is
optional,
which
can
just
define
which
Bill
pack
you
only
use.
C
So
given
the
Bill
pack,
we
can
generate
the
can
if
you've
build
yeah
more
completely
from
a
library
of
Bill
packs.
So,
rather
than
having
to
copy
and
paste
these
big
EML
files
into
all
and
you
get
repost,
we
can
just
reference
them
in
your
git
repo
or
you
could
specify
override
various
different
pipelines
in
Jenkins
X.
We
tend
to
have
different
logical
pipelines
like
the
pipeline
that
runs
on
a
pull
request.
The
pipeline
that
doesn't
release.
C
We
can
separate
those
into
different
yells
or
blocks
of
yellow
and
let
people
completely
override
them
in
each
repo
or
inherit
them.
We
could
maybe
even
look
at
doing
things
like
pre
post
steps,
so
you
might
say
I
want
to
reuse
the
standard
release
pipeline,
but
before
I
push
the
docket
image.
I
want
to
do
this.
A
C
Whether
you
want
to
copy
and
paste
the
whole
thing
every
time
or
you
want
to
reference
it
by
name
or
whether
you
want
to
just
add
certain
pieces
before
after
things,
we
should
be
able
to
let
people
just
define
very
dry
bits
of
llamó,
which
is
very
concise,
but
it
gives
you
the
full
power
to
you
know
completely,
do
whatever
you
want
and
every
project.
So
you
know
it's
just
a
bit
of
a
ramble.
I'll
put
all
of
these
links
into
the
Google
Doc.
A
C
It's
quite
surprising
how
nicely
fit
into
jinkies
X
as
well,
and
we
didn't
really.
We
weren't
really
expecting
connected
to
turn
that
we
just
figured
that
you
know
one
day
there
would
be
some
kind
of
Cuban.
It
is
like
thing,
but
it
was
quite
surprising
how
quickly
we've
just
been
able
to
you
know
we
use
our
IDE
plugins,
our
CLI.
We
can
even
actually
reuse
our
bills,
it's
like
in
it.
C
It's
been
quite
surprising
how
quickly
just
fit
in,
and
it
was
a
spooky
timing
because
we're
just
looking
at
prowl
and
almost
within
the
same
time
can
it
have
arrived
and
kidney
from
prow
became
a
thing
and
jinkies
X
and
prowl
and
Kim
jig
is
extinct
in
it
all
kind
of
happened
with
him.
We
could
do
which
it's
still
very
early
and
I,
wouldn't
recommend
anybody
really
go
into
production
with
Kenya.
C
If
you
build
it
anytime
soon,
but
he's
certainly
looking
like
it
could
be
a
nice
simple
option
and
that's
another
thing:
we've
always
kind
of
figured
at
some
point.
It
might
be
nice
to
have
a
SAS
option
for
Jenkins
X
so
that,
if
you
just
want
to
use
jenkees
X,
but
you
didn't
want
to
run
any
infrastructure
or
manage
anything
yourself
use
something
like
Kerchak
or
whatever
for
all
of
you
over
these
pipelines
in
many
ways:
code,
ship
and
Connecticut.
C
Basically,
the
same
pipeline
they're
just
running
docker
commands
things
like
code,
ship
and
circle
Co
they
hosted
kinetic,
runs
in
your
cluster,
so
I
think
the
kala
true
thing
fits
very
well
with
the
potential
size
version
of
Jenkins
excellent
point
where
you
might
want
to
use
code
shape
or
Google
Cloud
building
or
something
like
that
for
your
releases
and
but
still
have
the
same.
Ux
of
junkies,
X
I
think
it's
a
really
interesting
time.
I
mean
everything's
changing
very
rapidly
in
this
space.
These
days,
it's
it's
fun
and.
A
C
Exactly
and
the
other
thing-
that's
really
interesting
is
so
right
right
now:
okay,
prowl
isn't
quite
finished
in
jinkies
expertise,
kind
of
close,
but
you
have
the
option:
use
Jenkins
for
releases
at
prowl,
for
promotion
use
Jenkins
for
releases
and
promotion.
So
you
can
pick
and
choose
which
tool
you
wish
that
you
could
use
prowl
for
web
hooks
Jenkins
for
releases
of
it.
C
So
you
completely
pick
and
choose
what
you're
going
to
use
for
web
hooks,
what
you're
going
to
use
for
doing
releases
where
you
can
use
for
doing
promotions
and
you
can
plug
and
play
exactly
what
pieces
you
wish
when
we
do
multi
clusters,
I,
really
kind
of
prefer.
The
idea
of
prowl
in
you
know
staging
in
production,
because
you
want
a
simple
lockdown
promotion.
Workflow
well
pipeline,
build
step
that
hardly
does
anything
and
never
really
changes.
C
You
just
lock
that
down
and
then
you're
done
you
kind
of
don't
want
a
developer,
centric
tool
that
lets
you
spin
up
an
import
projects
whenever
you
feel
like
running
in
production,
you
kind
of
want
that
in
your
dev
cluster,
so
I
think
all
these
different
options
is
going
to.
Let
people
choose
exactly
what
they
want
their
infrastructure
to
be
like.
C
Maybe
prowl
is
used
in
production
and
staging
just
for
promotion,
only
like
no
docker
bills,
no,
releasing
anything,
just
just
promoting
released
stuff
and
then
maybe
use
completely
Jenkins
in
development,
or
maybe
use
a
hybrid
Jenkins
on
some
projects,
Kay
native
on
others
or
whatever,
and
pick
and
choose
based
on
the
app.
What
you
want
to
use
but
have
the
whole
thing
integrated
together.
I
think
that's
a
really
compelling
thing:
I
mean
Kennedy:
it's
not
going
to
be
a
good
fit
for
lots
of
things.
C
A
A
C
And
plus
we'd
probably
want
to
do
a
cron
job
as
well,
so
as
well
as
just
the
web
hook
thing,
but
for
promotion
at
me
so
for
promoting
cheeky
sex.
You
probably
just
want
to
go.
You
know
every
hour.
Let's
do
a
reapply
just
in
case
that's
gonna
drift,
and
you
know
some
of
these
does
something
crazy
in
production.
Let's
just
keep
reapplying
what
sink
it
in
case,
weird
happens,
gonna
think
so.
C
Yeah,
yeah
I
think
the
combination
of
prowl
and
cron
jobs
looks
a
good
one,
and
you
know
one
day:
maybe
KNAT
will
have
its
own
web
book
thing
that
might
use
some
a
pro
or
whatever.
Whether
who
cares
it
does
really
matter.
We
could
switch
to
someone
the
web
cookie
thing.
Maybe
there
could
be
a
simpler
leaner,
meaner
web
book
thing
that
that
is
big
just
for
promotion,
so
it's
hard-coded
to
do
one
job
only
ever
or
something
like
that.
That's
all
great.
C
We
were
talking
to
somebody
this
week
who
they
have
their
own
custom
built
web
hook
thing
for
production,
which
has
been
through
their
security
checks.
Whether
any
is
like
fine,
if
you
wanna,
if
you
only
use
some
custom
web
hook
thing
and
your
own
choosing,
you
know
some
land
or
whatever
crack
on
you
know.
It's
all
good,
so
I
I
think
that
modularity
of
jinkies
X
is
gonna,
serve
as
well
in
the
future
and
let
people
you
know,
tweak
things
and
configure
things
to
sue
exactly
what
they
need,
rather
than
this
one-size-fits-all
monolith
and.
A
C
I
think
also
having
we
should.
This
came
up
on
a
chatroom.
Today,
people
were
asking
about
insects,
vinegar,
I,
think
one
of
the
really
nice
things
about
having
a
Cuban
ate
its
native
solution.
For
all
of
this
is
it's
all
micro
services,
all
the
way
down
using
Cuban.
It
is
to
connect
everything
together.
So
if
you
want
to
change
a
web
hook
handler
or
a
cron
job
handler
or
a
low
bass
or
a
thing,
I
think
you
just
switch
a
piece
and
infrastructure.
C
E
So,
let's
have
a
short
introduction
to
this
single
sign-on
stuff.
So
what
we
try
to
achieve
is
to
make
this
single
sign-on
setup
quite
easy
for
kubernetes
applications
and
we
try
to
paste
all
the
all
the
pieces
on
well-known
open
source
components.
So
one
of
the
main
component,
it's
Dex,
which
is
a
open
ID
connect
provider
federated
which
has
connectors
to
many
identity
providers.
You
can
see
here,
like
it,
github
get
la
Microsoft,
Azure,
Active,
Directory,
Google
and
so
on.
E
So
basically
it's
a
proxy
towards
this,
and
it's
quite
a
nice
lightweight
go
rittany
go
starts
quite
fast.
Also
it
has
a
nice
GRDC
API.
If
you
look
here,
you
can
manage
it
over
T
RPC
and
the
idea
of
the
single
sign-on
operator
is
to
have
a
operator.
We
takes
over
all
these
setup
steps
to
to
configure
a
single
sign-on
for
a
selfie.
E
So,
and
so
let
me
think
if
it
is
Jake
is
a
single
sign-on
operator,
I
got
I
wrote
a
bit
of
documentation
and
yeah
I
can
show
it
currently
I
managed
to
everything
with
Genki
sex.
So
we
have
a
text
installation.
We
have
a
single
sign-on
operator
installation
and
we
have
a
body
like
:
HTTP
service,
for
which
we
want
to
set
up
a
single
sign-on.
So
if
we
check
the.
E
Staging
environment
we
have
country,
three
boats
running
and
I
have
feared
a
lot
from
the
single
sign-on
operator.
Maybe
we
should
have
a
look
into
the
single
sign-on
CRT,
so
the
basically
the
operators
listen
to.
So
what
is
the
this
CRT
and
when
the
CRT
is
created,
it
takes
over
all
the
steps
to
set
ups
SS.
Also,
if
we
look
inside
of
the
CRT,
basically
we
see
this.
E
E
Also,
we
can
define
the
upstream
service,
so
we
just
need
to
define
the
name
of
the
service
for
which
we
want
to
set
up
the
single
sign-on.
Then
we
need
a
domain
because
the
services
or
the
single
sign-on
for
the
service
with
the
public
exposed
under
this
domain,
and
then
it's
just
typical
like
proxy
to
commit.
E
We
want
use
for
single
sign-on
proxy
and
then
some
cookie
specific
configuration
like
how
long
we
want
to
keep
the
cookie
if
it's
sent
over
HTTP
or
you
have
these
kind
of
things,
so
that's
it
so
I
can
now
go
and-
and
just
let's
put
this
to
watch
the
post
what's
going
on
so
we
have
this
here
now
I
create
this
is
all
resource.
Oh,
that
is
created
now,
we'll
see
that
first
operator
has
created
the
Open
ID
Connect
client,
into
the
Dex
using
G
RPC
API.
E
Now
it
deploys
the
process
of
proxy,
it
waits
for
the
proxy
to
get
ready.
So
we
still
the
pod
is
not
yet
running
so
it
waits
until
the
proxy
is
up
and
running
when
the
Proteas,
it's
ready,
it
will
expose
the
proxy
publicly
using
the
expose
controller.
It
runs
the
expose
controller
as
a
job,
and
we
see
now
it's
the
service
was
running
now
it
runs.
The
expose
controller,
complete,
post
controller
is
running,
is
ready
now
what
it
does.
It
gets
the
public
endpoint
of
the
SSO.
E
D
E
E
E
Its
using
github
so
I
have
this.
Now
the
the
X
login
window
show
up
shows
up
so
now
I
can
choose
github
I
already
logged
in
on
once
so.
I
have
also
the
text
configure
to
work
on
you
with
gentillesse
X
organization.
So
I
have
already
grant
access
to
this.
So
now,
when
I
say
authorized
so
I
locked
in
so
now,
I'm
locked
in
so
you
see
now
the
SSO
HTTP
shows
up.
It
returns
the
code.
E
E
So
we
have
this
cookie.
So
what's
created
for
T
surface,
we
see
this
our
name
whatever
we
configure
it.
So
now,
if
I
go
back
so
when
you
now
I
can
do
whatever
I
want
so
I
can
so
cook
it
setup.
I
can
log
in
again
whatever
so
now
if
I
delete
a
cookie
I
log
in
again,
so
it
shows
me
again,
the
login
setup
and
whatever
so
now.
E
Basically,
on
this
side,
so
I
wrote
a
bit
of
documentation
here
how
to
install
basically
Isis
operate,
that
we
kind
of
not
really
fork
the
eggs,
but
we
create
our
own
text
repository
based
on
the
upstream
repository,
because
we
wanted
to
set
up
Jenkins
eggs
to
do
like
continues
the
deployment
of
text
into
the
kubernetes,
and
we
have
our
own
chart
based
on
the
open
source,
stable
charts.
Here,
it's
just
the
decks,
which
has
a
few
jobs
here.
So
one
of
the
jobs
it
generates,
the
GI
PC
certificates.
It's
a
self
signed
certificate.
E
Any
stores
is
certificate
into
into
some
secrets.
The
problem
is,
if
the
extras
in
a
different
name,
space,
we
need
to
copy
these
certificates
from
the
death
namespace
into
the
ceiling
to
the
SSO
operator
and
into
the
SSO
operator
chart.
There
is
a
there
is
a
job
which
can
be
enabled
like.
If
you
deploy
a
sis
operator
in
a
different
lens
based
in
text.
We
can
enable
this
job
and
the
job
it
will
copy.
E
The
GRDC
certificates
from
the
X
namespaces
with
SS
operator
name
is
present
and
the
SS
operator,
which
will
be
able
to
connect
towards
stacks
so
by
by
default.
If
you
deploy
both
in
the
same
namespace,
you
don't
need
to
enable
this
so
the
rest
operator
R
will
it
will
be
able
to
detect
the
situation,
fetch
the
client
and
server
so
that
client
certificate
and
public
certificate
of
this,
because
it's
a
self-signed
certificates,
though
yeah.
E
That's
it
yeah.
We,
if
you
don't,
want
to
use
Jenkins
X
to
manage
the
operator,
you
can
also
use
scaffold
and
help
to
install
it
and
then
share
a
bit
of
details.
How
you
can
create
and
run
the
like
a
CRT.
So
one
of
probably
so
next
thing
thing
to
fix
is
to
to
see
how
self
manager
in
TLS
work
together
that
we
can
expose
the
X
over
TLS
and
also
create.
This
is
a
proxy
which
is
exposed
over
a
TLS
endpoint
that
everything.