►
Description
Expand Your Spinnaker Pipeline to the Desktop [I] - Sean Korten, Kenzan
Commit, build, test, push, build, test, deploy, test, promote, test, repeat. You can already use Kubernetes as the common platform for your entire lifecycle, but wouldn’t it be cool to use one tool to manage it? Spinnaker is a multi-cloud CI/CD platform that works well with Kubernetes on many cloud providers. In this talk we will discuss how to turn your workstation running minikube into another cloud provider in your cloud based production Spinnaker and add it to your CI/CD pipeline.
About Sean Korten
Sean is a Lead Platform/DevOps Engineer with Kenzan, a professional services company that provides customized end-to-end solutions to a diverse group of clients. Since joining Kenzan he has contributed to the Spinnaker OSS project and helped implement it internally and with multiple clients. His primary focus for the last several years been on the architecture and implementation of continuous integration and continuous delivery. He has a long and diverse background working with development teams to 24x7 operations, racking and stacking to AWS and GCP, and a few years as a security professional in between.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
A
That
is
here
so
micro
services
we've
been
working
with
a
Netflix
OSS
stack
for
quite
a
while.
Now
we
are
a
collaboration
partner
with
spinnaker
and
have
been
since
before
the
initial
release
and
the
aforementioned
digital
transformations
where
we
come
in
and
we
help
companies
go
from,
you
know
quarterly
waterfall
monolith
releases
to
daily
whenever
micro
service
releases.
A
So
a
little
bit
about
this
talk
and
what
this
is.
This
is
a
proof
of
concept.
This
is
something
that
is
possible.
That
is-
and
this
is
shows
that
it
provides
some
value,
but
it's
not
something
that
you
would
want
to
ever.
Deploy
into
production,
as
is
I,
will
be
releasing
all
the
the
code
that
I
have
developed
as
open
source
here
in
the
next
couple
of
days
after
I
clean
up
to
get
repository,
so
you'll
be
welcome
to
hack
it
and
use
it
and
I
think
it's
I
think
it's
pretty
nifty.
A
So
what
this
is
not
this
is
not
secure.
I
have
a
plaintext
password
in
there
somewhere,
because
again,
this
is
proof
of
concept.
This
is
not
automated.
There's
some
manual
steps
involved
and
again
not
production
ready,
so
getting
that
out
of
the
way.
So
what's
the
big
idea,
the
big
idea
is
that
when
you
are
deploying
we're
using
a
pipeline,
those
pipelines
shouldn't
be
starting
in
the
cloud
because
they
really
start
when
you
do
that,
commit
on
your
or
that
code.
Change
on
your
local
machine.
A
Last
winter
I
was
working
with
a
particular
client
on
one
of
these
digital
transformation
projects
and
we
set
them
up
with
a
development
environment
and
a
production
environment
all
on
AWS.
But
then
the
developers
wanted
to
be
able
to
test
things
locally
before
they
started,
pushing
things
out
so
they're
like
okay.
A
Well,
how
do
we
bring
up
a
whole
stack
on
our
local
machine
and
we
were
using
ECS
in
the
in
AWS,
so
we
couldn't
obviously
extend
that
back
to
the
desktop,
so
they
had
use
docker
swarm
and
then
why
can't
we
use
docker
swarm
to
deploy
our
tests
in
our
production
environments,
so
that
got
me
thinking
this
like?
Wouldn't
it
be
nice
if
we
could
have
one
single
platform
to
use
everywhere
that
everybody
could
then
deploy
to
just
as
they
would
any
other
environment?
No
differences
whatsoever
and
I
have
more
notes
here.
A
So
what
is
that
platform
kubernetes
fills
that
bill
right.
You
can
run
kubernetes
on
just
about
anything
and
deploy
to
it.
The
same
way
you
would
on
you
know,
GCP
or
bare
metal
or
Amazon
who's
using
kubernetes.
Today,
all
right
lots
of
people
who
knows
what
mini
cube
is
hey
just
about
the
same
number
of
people
and
is
everybody
using
mini
cube
today,
a
few
people
or
less
okay.
A
So
what
I
think
of
kubernetes
and
when
people
asking
you
what
kubernetes
is
I
say
it's
it's
the
gnu/linux.
It
is
the
new
operating
system
for
all
your
things.
So
how
do
we
then
do
kubernetes
locally
and
that's
mini
cube,
which
just
about
everybody
here
has
heard
of
so
it's
the
Cates
or
the
kubernetes
distribution
for
your
desktop
and
it
works
just
the
same.
You
can
use
the
same
cube
control
to
do
anything
just
gotta,
get
it
up
and
running
and
runs
on
Windows.
It
runs
on.
Mac
runs
on
Linux,
so
that's
great.
A
So
there
are
a
couple
of
problems
with
that,
though,
in
that
running,
kubernetes
locally,
you're
running
anything
locally
is
not
really
part
of
the
cloud.
It's
not.
It
is
it's
the
same
platform,
but
you
were
not
on
the
cloud.
You
cannot
form
these
direct
connections
back
and
forth
between
something
behind
a
you
know,
home
firewall,
router
and
your
environment
up
in
GCP
or
AWS,
so
you
couldn't
connect
them
directly.
So
what
do
we
do
about
that?
A
So
here
is
the
deployment
that
I
created-
and
this
is
really
pretty
simple.
Like
I
said,
this
is
a
proof
of
concept.
It's
really
happy
and
I
am
creating
an
SSH
listener
and
exposing
it
as
a
service.
You
can
see
there
but
I'm
also
exposing
one
additional
port,
and
that
is
eight
four
four
four
in
this
case,
when
you
connect
to
the
API
for
mini
qubits
on
eight
four,
four
three.
A
So
that's
all
great
that
works
pretty
easily,
but
then
what
about
this
whole
spinnaker
component?
So
what
is
spinnaker
who's
heard
of
spinnaker
outside
of
the
keynote?
This
morning?
A
good
number
of
people
who
here's
used,
spinnaker
yeah,
that's
actually
I'm
surprised
that
there
or
that
many
people
that
abuse
spinnaker.
It
is
a
little
bit
intimidating
to
get
set
up
in
that
people
who
have
tried.
A
It
are
laughing
because
it's
true
and
so
we've
actually
made
a
lot
of
progress
in
getting
spinnaker
set
up
over
the
last
a
couple
of
years,
but
it's
still
not
for
the
faint
of
heart.
There
are
different
sort
of
code
labs
out
there
and
ways
to
go
and
deploy
it
and
at
the
end
of
the
presentation,
I
give
a
link
to
one
of
the
documents
online
that
will
enable
you
to
go
and
set
this
up
on
GCP
really
quickly
really
easily.
But
again
it's
not
going
to
be
a
production
kind
of
setup.
A
But
how
do
we
configure
spinnaker?
So
this
is
another
one
of
the
pain
points
right,
because
all
of
the
configuration
files
are
in
yamo
and
if
you
are
running
this
in
an
operational
model,
you
have
all
your
micro
services
broken
out
into
separate
containers
or
separate
instances.
So
there
is
a
tool
that
was
developed,
called
halyard
halyard
and
is
it
supports
gke,
as
well
as
a
local
distribution?
A
So
don't
like
this
view,
so
those
are
all
the
commands
that
I
use
to
actually
go
and
configure
micro
brew.
Nettie's
cluster
using
halyard
and
I'll,
show
you
those
again
and
we'll
walk
through
them
in
a
minute.
So
then
running
Hal
apply.
It
will
go
through
and
we'll
create
the
entire
cluster
for
you,
and
it
will
add
in
these
configurations
now
the
reason
I
wanted
to
use
how,
instead
of
going
and
hard-coding
the
the
information
about
my
mini
cube
cluster
is
because
I
envisioned
this
being
a
dynamic
thing.
A
So
what
I
want
wanted
this
to
be
able
to
do
and
I
didn't
quite
fully
automate.
This
part
was
to
connect
into
this
container
that
I
launched
on
my
spinnaker
cluster
and
then
run
the
Hal
commands
to
add
in
the
configuration
for
my
particular
mini
Clube
cluster
and
apply
that
config
change,
so
that
then
the
cluster
would
show
up
automatically
inside
of
spinnaker,
and
the
advantage
of
that
would
then
be
that
any
developer
could
go
and
add
their
own
mini
cube
into
there
automatically
using
a
naming
convention.
A
And
then
you
can
start
constructing
pipelines
to
do
your
test
and
deploy
there
and
then
either
add
that
into
an
existing
pipeline
or
have
that
trigger
another
pipeline,
which
I
think
is
the
best
way.
So
that's
another
interesting
part
of
spinnaker
is
that
you
can
have
pipelines
trigger
pipelines
or
include
pipelines,
so
it
would
go.
I
have
a
pipeline
that
I
have
dynamically
created
for
my
mini
cube,
which
is
going
to
call
my
cloud
Jenkins.
A
You
want
to
do
and
continuous
delivery
and
it
does
those
things
very
well
run
scripts
run
applications.
You
can
use
it
to
run
terraform
if
you
wanted
to,
but
those
are
things
that
spinnaker
knows
it
doesn't
do
and
doesn't
want
to
do
again.
It's
focused
very
closely
on
actually
executing
and
orchestrating
these
pipelines.
So
Jenkins
is
an
integral
part
of
that
and
many
people
ask
me
it's
like
well,
why
do
I
have
to
include
Jenkins
if
I
have
spinnaker?
That's
why?
A
So
some
of
the
other
advantages
of
spinnaker
and
I
can
show
you
a
dashboard
here
in
a
minute.
Is
that
it
provides
you
that
one
view
of
all
of
the
different
aspects
of
a
pipeline.
It's
one
place
to
view
the
whole
thing.
If
you
have
a
pipeline
of
pipelines
that
are
deploying
to
multiple
different
accounts
or
executing
tests
in
parallel,
you
can
open
up
that
view
and
you
can
click
into
each
one
of
those
pipelines
and
see
exactly
what's
going
on.
A
You
can
view
the
status
of
clusters,
whether
they
be
instances
or
in
kubernetes,
and
you
can
see
the
number
of
containers
or
pods
or
instances
that
are
in
there,
as
well
as
the
load
balancer
status.
You
don't
need
to
be
toggling
back
and
forth
between
three
or
four
different
consoles
in
order
to
get
that
view
of
what's
going
on,
and
then
another
advantage
is
that
you
do
want
to
get
down
into
those
other
consoles.
You
can,
for
instance,
with
Jenkins.
A
It
will
provide
you
a
link
to
the
exact
job
number
that
was
running
as
part
of
your
pipeline,
and
you
can
drill
directly
down
into
the
the
Jenkins
job
itself
and
see
what
was
going
on.
So,
if
that
failed,
you
can
say:
ok,
yeah
I
know
it
failed
on
this
stage.
Let
me
click
on
that
particular
job.
Go
all
the
way
down
and
zip.
That's
why
I
go
make
a
code,
change
fix
it
and
it
will
trigger
another
run
of
the
pipeline
and
off
you
go.
A
All
right,
so
here
is
the
docker
file
that
I
created
for
this
little
SSH
tunnel,
pod
I
added
in
a
bunch
of
yeah,
okay,
I
added
in
a
bunch
of
utilities
to
help
me
debugging
as
I
go
through
the
process.
Of
course
we
needed
the
OpenSSH
server
and
then
I
did
all
this
and
I'm
basing
it
off
of
a
bun
too,
because
that's
gonna
provide
the
easiest
fastest
route
to
all.
A
A
We
are
then
adding
in
a
bunch
of
different
things
from
mini
cube
into
the
pod,
and
this
is
so
that
it's
for
both
halyard
halyard
requires
the
cube
config
in
order
to
add
it
into
the
spinnaker
configuration
and
I'm,
including
the
API,
certs
and
key,
and
then
that's
the
config
file,
as
well
as
cube
CTL.
How
uses
cube
CTL
to
execute
different
commands
within
spinnaker?
Our
spinnaker
uses,
cube
CT
also
so
then
just
exposing
ports
22
and
844,
and
that's
pretty
simple
and
that's
about
it
for
that.
A
A
A
So
from
there
I
had
to
go
ahead
and
create
a
halyard
container.
I
imagined
that
these
should
be
combined.
I
didn't
quite
get
that
far
along
in
this,
but
it
could
easily
be
done
so
that
Hal
is
included
within
that
same
pod
and
I
know
that's
a
little
anti-pattern
to
have
so
much
going
on
in
one
pod,
but
it
makes
it
a
little
bit
easier.
A
A
Am
I
not
completing
there
we
go
now
well,
these
are
the
commands
that
I
ran
once
I
got
on
to
the
the
hell,
so
I
installed
them
and
here's
again
more
manual
setup
I
had
to
add
those
mini
cubed
keys
in
there.
I
had
to
do
a
number
of
different
things
that
I
really
didn't
even
talk
about
it
all.
In
order
to
get
g
c
e
g
CP
configured,
those
are
I
just
follow
the
documents
that
were
on
the
internet
for
setting
those
things
up.
A
Those
are
on
the
spinnaker
I/o
website
and
while
they
are
not
perfect
and
I
would
love
to
find
some
time
to
go
and
update
those,
they
do
work.
If
you
stick
with
it
and
I
manually
started
up
the
halyard
daemon
and
then
ran
these
different
configurations.
So
this
is
how
easy
it
is
to
actually
add
in
floud
providers.
So,
for
example,
we
added
in
registry
here
and
then
we
added
in
our
provider,
and
we
gave
it
a
name.
A
The
the
value
that
I
see
in
this
is
that
again
every
developer
can
then
have
a
cloud
native
environment
locally.
You
don't
have
to
spend
extra
money
on
compute
resources
up
in
the
cloud.
I
think
everybody
has
got
just
about
16,
gigs
or
more
on
laptops
these
days.
So
there's
plenty
of
space
in
order
to
run
it
there
plus
it
decreases
that
latency
for
connecting
the
cloud
and
it'll
leaves
any
different
security
group
rule
issues
or
any
I
am
issues
by
being
able
to
run
that
locally,
and
then
you
have
that
connected
the
cloud.
A
So
it
appears
is
one
large
environment
and
it
gives
you
a
whole
bunch
of
visibility.
I
think
for
me,
the
most
interesting
part
of
this
was
not
just
getting
spinnaker
connected
to
this,
but
it
was
the
idea
of
being
able
to
talk
back
and
forth
to
a
local
kubernetes
cluster
that
you
normally
wouldn't
be
able
to
get
to
I
I
loved
the
idea
of
not
having
any
restrictions
on
where
I
can
run
things
and
where
I
can
access
things
from,
but
so
I
thought
that
was
the
neatest
part.
A
A
You
can
really
bridge
a
whole
bunch
of
networks
just
using
simple
SSH
and
while
SSH
is
simple
to
use,
it's
probably
not
the
best.
So
I
think
there
are
better
ways
to
actually
create
these
tunnels.
That
I
look
forward
to
exploring
further
note
on
security
again.
This
is
not
secure
and
you
should
not
run
this
in
production
and
there's
the
example
of
where
that
other
things
I
would
like
to
explore.
Adding
into
this
is
something
like
telepresence.
If
you
haven't
looked
at
telepresence,
yet
it
seems
pretty
interesting
so
here
a
couple
of
references.
A
This
first
link
is
the
one
to
go
and
get
spinnaker
up
and
running
on
GCP
quickly,
painlessly
easily.
If
you
want
to
kick
the
tires
and
spinnaker
I
highly
recommend
going
and
using
that
as
I
told
my
boss,
though
he
needs
to
expect
the
expense
report.
From
my
personal
GCP
account
a
couple
of
other
references,
the
docs
on
halyard,
as
well
as
the
complete
command
reference
for
halyard,
there's
a
lot
of
different
options
and
they
are
fairly
consistent.
A
B
A
So
the
question
was:
is
he
set
up
spinnaker
and
it
wasn't
working,
do
I,
have
any
recommendations
for
setting
it
up
and
getting
up
and
running?
Yes,
that
one
link
that
I
provided
works
perfectly.
It's
this
one
right
here:
the
Google
Cloud
solutions,
continuous
delivery,
spinnaker
kubernetes
engine.
That
is
enough
to
get
you
acquainted
with
spinnaker,
then.
A
We
we've
been
meaning
to
put
out
a
document
on
how
to
set
up
a
production
spinnaker
for
a
while.
We
actually
did
work
on
a
terraform
setup
in
order
to
get
it
up
and
running
too
so
that
that
is
something
that
we
would
like
to
get
out
and
just
haven't
done
so
yet
there
are
other
documents
out
there,
but
that's
the
one
that
I
recommend
for
getting
going.
You.
A
Slack,
yes,
there
is
a
slack
channel.
There
is
a
slack
group
for
spinnaker
and
that
is
pretty
pretty
active.
I'm,
not
gonna,
pull
up
my
slack
because
there's
way
too
many
other
things
going
in
there,
but
I
think
it's
I
can't
remember
the
name
of
its
spinnaker
team,
dot,
slash,
comm
and
there's
a
bunch
of
people
on
there
from
all
the
different
contributing
companies.
Yes,.
B
A
I
am
NOT
personally,
so
the
question
was:
is
there's
a
v2
that
looks
like
it's
coming
soon
and
do
I
know
when
that's
going
to
be
released
and
no
I
haven't
been
involved
with
that
or
even
too
much
with
the
the
the
collaboration
personally
lately,
but
I
do
know
that
they're
making
good
progress
on
all
the
different
bugs
and
fixes
and
I.
Imagine
that
v2
is
just
a
saying.