►
From YouTube: Spinnaker Basics!
Description
Speaker: Nirmalya Sen from OpsMx
Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
We will cover how to install Spinnaker, create an application and pipeline to deploy to a kubernetes cluster. In the process we will learn about Spinnaker basics.
A
A
So,
what's
continuous
delivery,
it's
the
process
of
taking
code
from
check
in
to
all
the
way
from
testing
and
staging
all
the
security
checks
and
all
that
and
finally,
getting
into
production.
So
all
that's
involved
in
that
is
termed
as
continuous
delivery,
and
currently
that
process
is
quite
manual,
lots
of
handoffs
between
people
and
so
what
platforms
like
spinnaker
allows
you
to
do
is
automate
that
process
so
that
you
can
release
your
software
changes
and
our
high
velocity
and
confidence.
A
Now,
what's
so
special
about
spinnaker-
and
you
know
these
are
my
muse
and
that's
why
I
love
spinnaker
and
you
know,
I'm
working
with
comfort
with
a
company
that
sort
of
specializes
in
spinnaker
is
that
it
supports
multiple
cloud
environments.
You
know
it's
not
just
human,
it
isn't
not
just
EWS
a
lot
of
customer
and
muhammad's
and
not
uniform.
A
There
are
different
types
of
infrastructure
and
customer
environment,
so
spinnaker
supports
multiple
cloud
environments
out
of
the
parks,
AWS
sure
Google,
Cloud,
Cloud
Foundry,
just
to
name
a
few,
and
you
know
on
flavors
of
cuban
artists
and
very
extensible
models.
If
someone
wants,
they
can
come
in
and
add
support
for
it,
I've
been
seeing
that
you
know
even
like
Ally
by
MacLeod,
who
are
we
cloud
and
basically
being
as
providers
in
spinnaker.
A
The
other
thing
it
does
is,
you
know
it
provides
a
single
pane
of
control
and
visibility.
It's
not
about
you
know
releasing
your
software
with
high
velocity.
You
can
actually
see
the
resources
that
got
deployed
in
the
process
and
you
can
see
the
status
of
them
and
you
can
even
control
some
of
that.
We'll
take
a
look
at
briefly
about
some
of
them,
like
you
can,
edit
them
even
screen.
Apps
came
down
or
rollback
for
that.
Control
is
available
to
you
right
from
the
spinnaker
UI.
A
And
finally,
you
know
if
you
want
to
use
any
such
tool
in
an
enterprise.
There
are
lots
of
policies
that
you
want
to
follow
is
like
before
it
gets
to
production.
Different
people's
have
to
sign
off
on
that
or
you
know,
different
testing
has
to
be
done.
Image
scans
has
to
be
done,
so
you
want
to
enforce
those
sort
of
policies,
and
then
spinnaker
has
a
very
good
flexible
model
to
enforce
those
Enterprise
policies,
so
all
of
those
make,
in
my
view,
a
spinnaker,
a
pretty
great
platform
for
continuance
generally.
A
So
what
does
the
spinnaker
architecture?
Look
like?
It's
some
microservices
be
based
on
architecture.
You
know,
that's
where
you
know
in
the
world
is
going.
People
are
like
refactoring
bono,
let's
stow
micro
services,
because
it's
easier
to
manage
them
and
spinnaker
is
no
different.
It
consists
of
a
lot
of
micro
services.
I'll
not
get
into
the
details
of
all
of
them,
because
this
architecture
discussion
is,
can
be
a
session
by
itself.
But
I'll
point
out.
A
A
few
of
these
things
is
the
UI
that
we
look
at
as
handle
my
deck,
and
then
this
gate
is
like
an
API
server.
The
UI
uses
it
or,
if
you're,
using
api's,
that's
also
in
tracks
with
eight.
The
main
workhorse
is
really
this
cloud
driver
that
actually
talks
to
the
divin
different
providers
like
humanities
or
ews,
and
does
the
work,
and
this
all
car
is
sort
of
the
orchestration
engine
in
there,
and
the
reason
it's
good
to
know
about
this
component
is
that
in.
A
If
something
goes
wrong
and
you
have
to
look
at
the
launch,
you
know
where
to
go.
Look
at
the
logs
form
right
and
the
other
thing
that
is
there
is
that
whole
thing
is
configured
and
controlled
through
this
component
called
halyard,
which
runs
on
the
side
and
it
can
be
used
to
configure
and
manage
the
whole
spinnaker
deployment.
A
Let's
go
into.
You
know
how
you
can
install
a
spinnaker,
so
there
are
different
installation
options
for
spinnaker
like
we
saw
just
now.
It's
a
micro
services
based
architecture,
so
the
best
deployment
option
for
spinnaker
is
to
deploy
in
some
Cuban
Ares
environment
and
that's
the
recommended
way
to
deploy
for
production
usage,
because
you
can
scale
different
components,
manage
different
components
easily.
A
There
are
published
images
from
the
community
for
spinnaker
there's
a
pretty
regular
cadence
of
new
releases
coming
out
lately,
some
people
enterprises,
you
know-
want
on
secure
images
so
they're,
even
you
bi8
based
images
and
that
are
available
and
to
deploy
it.
The
community
provides
a
healthy
aren't
using
it,
which
you
can
install
spinnaker
and
you'll,
see
I'll,
actually
use
the
home
shot
to
install
one
in
humanities
and
one
there's
also
an
operator
available
to
install
it.
And
specifically,
if
you
are
an
open
ship
shop,
you
can
go
to.
A
You
know
the
openshift
marketplace,
which
is
available
in
the
4x
versions
of
open
chef,
and
you
will
find
the
operator
there
and
user
to
install
spinnaker
with
that
sate.
You
know
if
you
have
a
VM,
you
can
definitely
do
a
single
node
installation
of
spinnaker
on
that
VM
I
know
at
least
one
of
our
customers
use
that
and
they
deploy
a
mighty
cluster
or
multi
node
deployment
of
spinnaker
on
VMs
itself.
It
can
be
done,
it's
a
little
complex.
A
You
have
to
bring
up
spinnaker
on
different
machines
and
then
say
what
runs
and
then
have
to
tell
sort
of
how
they
communicate
with
each
other.
So
it's
possible
to
do
it,
but
you
know
your
life's
made
lot
easier
and
simpler.
If
you
just
a
diplomat,
manage
it
in
a
Cuban,
it
isn't
man.
And
finally,
if
you
want
to
develop
on
it,
enhance
it
improve
on
it,
you
can
do
a
local
installation
from
github
so
going
into
how
to
install
a
spinnaker
in
cuba.
Knitters.
A
Really,
if
you
want
to
do
something
serious
with
spinnaker,
you
need
to
make
sure
you
have
at
least
20
gig
of
memory
and
six
cores
available.
If
you
just
want
to
kick
the
tires
and
see
how
it
works,
you
could
do
with
less
memory
and
cpu
course,
but
anything,
serious
I
think
that
20,
gig
and
6
core
is
what
you
should
allocate,
and
the
thing
that
you
need
to
also
make
sure
is
that
you
have
support
for
persistent
storage
in
your
queue.
A
A
Optionally,
you
can
customize
your
deployment
once
I
install
I
will
actually
walk.
You
there's
a
little
bit
through
the
spinnaker
values,
dot,
llamo,
there's
a
lot
of
customization.
You
can
do
end.
I'll
just
cover
some
of
the
very
basic
ones
and
not
get
into
the
lot
of
the
detail.
Months
and
finally,
once
you
have
that
and
you
have
help
available
and
ready
to
go
it's
as
simple
as
a
command,
helm,
installs,
vinegar
and
stable
spinnaker,
and
it
will
installing
and
within
like
seven
eight
minutes,
you
should
have
a
running
spinnaker.
A
A
And,
let's
make
sure
the
stalks,
it
shows
up
the
six
notes.
I
have
and
I
have
helm
already
installed
here.
I've
have
three
to
four
already
installed
over
here.
So
if
I
look
at
over
here,
I
have
a
values:
don't
ya
Mon
here
already
in
there
and
I'll
walk
you
through
that.
So
let
me
just
kick
off
this
install
with
the
command
that
I
just
showed
to
you,
which
is
home,
installed.
Spinnaker,
stable,
spinnaker.
A
A
B
A
Things
that
you
can
configure
is
the
version
of
spinnaker.
You
want
to
install
right.
This
one
is
going
to
install
123.
You
could
also
update
and
configure
the
halyard.
Remember
the
configuration
item
that
I
showed
in
the
architecture
side.
On
the
right
hand,
side
you
can
configure
the
image
to
use
and
the
version
of
the
image
to
use.
A
If
you
don't
have
persistence,
you
can
turn
it
off
by
using
this
flag
to
false,
but
you
know,
hopefully
all
of
you
getting
the
idea
that
without
persistence,
if
the
cluster
goes
away
and
you
come
back
up,
you
have
lost
on
your
data
right.
So
in
case
you
don't
have
it,
you
can
turn
it
off
and
use
that.
So
there
are
lot
of
other
configurations
that
you
can
do
as
you
get
familiar
with
spinnaker.
You
will
understand
and
be
able
to
do
it.
A
What
I,
also
wanted
to
point
out
is
that
that
persistence
is
that
a
couple
of
other
places,
this
spinnaker
uses
red
is
to
store
some
data
and
a
storage
which
could
be
mini
locally
or
even
could
be
external
sources
which
I'll
cover
right
once
I
get
back
to
the
slide,
and
so,
if
you
want
to
turn
persistence
off
there,
you
know
you
can
uncomment
these
lines
over
here.
That
will
turn
persistence
off
for
me
no
and
Redis.
A
That
is
used
other
than
that
this,
as
you
can
see,
there's
a
lot
of
configuration
that
you
can
change
here
and
you
know
that's
for
an
advanced
session
which
I'll
not
get
in
here,
but
just
to
point
out
that
you
know
this
is
highly
customizable,
so
it
has
triggered
of
the
installation
over
here
it's
going
on.
If
I
can
go
in
here
and
look
at
the
workloads,
it
is
basically
coming
up.
It's
triggered
of
the
halyard
which
I
was
talking
about
and
it's
bringing
up
all
the
other
things.
A
Now,
if
you
see
what
it's
telling
you
is
that
to
access
spinnaker,
you
expose
the
deck
and
the
gate
bond
right.
That
works
very
well
when
you
have,
when
you
have
a
local
system
testing
it
right.
But
if
you
want
to
expose
it
to
the
world,
you
need
to
provide
an
ingress
or
a
load,
balancer
access
to
a
track
and
that's
exactly
what
I'm
going
to
do
to
access
spinnaker.
So
I
have
a
file
here
called
spin
services.
A
Dottie
ammo
I'm,
going
to
highlight
this
thing
a
little
bit
here
and
make
the
font
also
a
little
bit
bigger.
So
you
can
see
over
here
is
that
I'm
creating
a
service
of
the
tank
load
balancer.
Luckily,
you
know
Google
Cloud
gke
would
provide
one
with
an
external
IP
access
and
it's
pointing
to
the
deck.
So
that's
what
I'm
going
to
do
is
basically
create
a
service
to
access
my
spinnaker,
so
I'm
going
to
do
a
gypsy
to
apply
my
yeah
that
final
spin
services.
A
So
it's
going
to
create
that
workload.
So
let
me
take
five
six
minutes
to
come
up.
Actually
these
are
all
up,
and
just
my
ingresses
or
the
load
balancers
getting
created.
So
let's
go
and
talk
about
a
few
of
the
spinnaker
artifacts
and
objects
and
then
we'll
come
back
here
and
look
at
spinnaker
UI,
okay,.
A
So
we
just
set
it
up.
So
let's
look
at
what
are
the
different
spinnaker
objects
that
we
should
be
aware
of?
First
of
all,
is
the
storage
provider?
You
know
we
talked
about
this
persistent
volume
right
saving
it.
So
then
it's
it's
available
and
you
don't
lose
data.
So
all
your
configuration
and
pipeline
information
is
stored.
You
can
store
it
in
some
sort
of
an
object
store.
It
could
be
your
Google
storage,
it
WS,
s3,
I
sure,
or
you
know,
a
default
out
of
the
box.
You
can
use
mini.
A
So
that's
what's
configured
to
use
speaker
also
uses
Redis
to
store
some
of
the
runtime
data,
and
you
know
if
you
want
more
performance
or
the
data
to
be
persisted,
even
because
some
of
that
run
time
data
you
want
to
look
at
it
and
analyze
and
run
some
audit
on
them.
You
could
even
use
my
sequel
for
that
and
you
know
that
we
configure
Meeny
over
there,
so
you
configured
them
in
value
store
Tiamo,
but
you
can
even
change
them
later
on
in
the
high
water.
A
So
that's
one
of
the
objects
that
spinnaker
uses
to
store
data.
The
next
is
the
most
important
one.
Is
the
cloud
providers?
That's
basically
the
workhorse
for
spinnaker
right
if
you
are
deploying
to
cuba,
netters
or
google
cloud
or
yo
AWS.
All
these
are
first-class
support
built
into
spinnaker,
and
this
is
just
a
small
list.
If
you
can
go
and
look
at
the
cloud
driver
or
even
if
you
look
at,
how
can
we
provider
I'll,
show
you
a
little
bit
how
to
get
there
and
run
some
of
these
commands
once
it's
up?
A
A
Spinnaker
provides
direct
integrations
with
your
existing
CI
system
via
changing
strategy
and
record
or
Concours
google
cloud
build.
It
provides
integration
with
them
so
from
your
spinnaker
pipeline.
You
can
trigger
some
of
these
things
and
it's
pretty
much
a
two-way
integration
in
the
census.
That,
not
only
can
you
trigger,
say
a
jenkins
charm
from
spinnaker
on
the
completion
of
a
jenkins
job.
You
can
trigger
off
a
spinnaker
title
right.
A
So
if
you
have
a
well-established
CI
system,
you
can
basically,
from
that
point
onwards,
start
your
delivery
pipeline
in
spinnaker.
So
that's
there.
That's
what
these
are
first-class
integrations
with
these
CI
systems
provide
next
is
the
artifacts.
You
know
any
any
pipeline
or
you
know
any
of
your
development
process.
You
are
dealing
with
darker
images
or
health
charts,
or
you
know,
ews
images,
Google
images
or
jar
files
in
a
maven
repository
or
github
files.
So
all
those
things
are
available.
A
Let's
go
and
look
at
spinnaker,
and
so
what
we'll
go
and
look
at
is
look
at
our
spinnaker,
we'll
walk
through
some
of
the
functionality
within
spinnaker
and
how
you
control
them.
Okay,
so,
let's
see
if
our
access
is
ready.
So
let's
refresh
this-
hopefully
it
gave
me
an
external
light.
Yes,
it
did
so.
I
have
spinnaker
now
available
and
an
external
IP
address.
So
let's
click
on
this
link.
Google.
A
Does
this
redirect
and
there
you
go
I
have
my
spinnaker
up
and
available
before
I
go
into
spinnaker
here
you
know
we
were
talking
about
hail
yard.
Where
you
run
those
Hal
commands.
Remember
all
the
screens
I
was
showing
you
there
were
these
commands
that
you
can
run
to
configure
each
of
them.
How
do
you
do
that,
so
that
is
running
in
the
spot
called
halyard?
A
A
It
will
tell
me
all
the
hell
commands
that
I
can
do
all
so
here.
I
can
manage
tracker
record,
Travis,
Jenkins,
Google,
Cloud
world
Concours
code
build
could
build,
is
new
I
mean
it
came
in
I.
Think
recently,
I,
don't
think
I
found
that
before
so.
So
that's
how
you
do
it,
and
this
is
very
useful,
so
you
won't
use
Jenkins,
you
basically
run
Jenkins.
It
will
give
you
all
the
sub
commands
available
under
Jenkins.
A
So
there's
no
Jenkins
really
configured
in
here,
so
you
can
do
actually
a
helps
to
see
the
command
available.
So
you
can
enable
or
disable
it
add
a
master
for
continuous
integration.
So
you
know
so
that
is
how
you
run
the
hell
commands
get
onto
the
halyard
pod
and
you
know,
run
run
the
hound
commands
to
configure
your
system
with
that.
Let's
get
into
spinnaker
UI,
so
this
is
the
spinnaker
that
we
just
set
up.
So
what
does
it
have?
It
has
applications
applications.
A
Are
you
know
things
that
you
build
as
an
organization's
that
your
end-users
use
like
a
marketing
applications,
sales
applications
a
shopping
card
as
an
application,
so
you
can
create
new
applications
here
so
I'm
going
to
just
create
an
applications
which
I'm
going
to
call
them
and
looks
like
this
is
an
application
already
demo
in
there.
So
let
me
create
another
one
called
demo
spider.
A
A
Now
so
it
has
basically
created
the
shell
for
this
applications.
What
do
we
have
here?
So?
What
an
app
the
view
over
here
is.
Basically
it's
a
collection
or
you
can
think
about
it
as
an
inventory
of
all
the
resources
that
make
up
your
applications
right.
You
have
clusters
which
are
like
you
know,
servers
could
be
cuban
and
it's
deployments
or
AWS
ec2
instances
or
easiest
clusters.
A
So
all
those
clusters
are
available
here
for
you
to
see
your
load
balancers
the
way
to
access
your
services
and
then,
if
you
have
to
find
any
firewalls
and
all
that,
and
if
you
actually
had
been
using
lambda
functions
and
all
that
which
you
can
use,
they
would
have
been
another
time
here
showing
up
here
as
functions
here.
If
you
had
an
account
the
different
accounts
here,
an
account
is
a
resource
infrastructure
resource
that
you
use
like
a
Cuban.
It
is
account
or
an
AWS
account.
A
So
if
your
application
is
using
multiple
accounts,
they
show
up
here,
and
so
you
can
get
to
see
lot
of
different
sort
of
aspects
of
your
infrastructure
right
from
here,
which
is
basically
like
I,
say,
is
an
inventory
of
your
application
resources
right
now.
How
do
I
create
this
resources?
You
could
always
create
them
right
from
here
manually,
but
you
know
the
ideal
way
to
do.
It
is
basically
through
pipelines.
That's
what
you
do
today,
we'll
just
go
ahead
and
create
a
very
simple
pipeline.
Let's
call
it
our
demo
pipeline.
A
So
when
you
have
a
pipeline,
there
are
a
lot
of
things
you
can
configure
in
a
pipeline.
You
can
have
automatic
triggers
that
you
can
add
to
a
pipeline.
You
can
see
the
pipeline
gets
triggered
even
as
a
cron
job
like
run
this
every
day
at
nine
o'clock.
Such
five
lines
are
used
by
some
of
our
customers.
Like
you
know,
you
know
at
nine
o'clock,
people
would
come
in
and
you
want
to
scale
up
some
of
the
resources.
A
Also,
you
can
have
parameters
defined
in
a
pipeline.
That's
what
makes
it
basically
templatized.
If
you
can
say
you
can
use
the
same
pipeline
across
teams
or
use
pipelines
to
deploy
to
different
namespaces
in
Cuba
natives
or
to
different
environments
like
stage
UAT
or
stage
2
or
C.
You
want
to
deploy
to
u.s.
East
versus
u.s.
West.
You
can
have
parameters
to
drive
all
of
those
things
now
for
us.
We
are
not
going
to
add
any
trigger
or
we
are
going
to
add
any
parameters,
so
I'm
I
just
deleted
them.
A
I
just
want
to
keep
it
simple.
The
other
thing
is
also
is
that
you
can
have
a
lot
of
notifications.
Email
integrations
with
slack
google
chat,
all
that
can
be
integrated
and
get
people
notified
when
a
pipeline
is
starting,
completed
or
failed,
and
we'll
see
that,
as
we
add
more
stages,
you
can
actually
have
notifications
and
controls
in
different
stages
too
right.
So
at
a
pipeline
level.
There's
a
lot
of
configurations
that
you
can
do.
Let's
add
a
simple
stage
here.
What
we're
going
to
do
here
is
just
deploy
a
simple
man.
A
First,
that
will
deploy
in
gemacht
server
and
create
a
service
to
access
it.
Okay,
so
we
basically
have
a
stage
added.
You
can
see
there's
a
lot
of
inbuilt
stages
available
like
a
wait
stage
that
will
just
wait
for
some
time.
You
can
undo
it.
You
can
run
a
script.
You
can
ski
save
pipelines
run
another
Python,
so
you
can
have
nested
pipelines,
so
you
can
have
an
uber
pipeline.
That's
invoking
other
child
pipelines.
A
You
can
have
manual
judgment
stages.
Well,
let's
add
one
a
manual
judgment
stage
where
you
know
someone
can
review
the
results
and
you
know
then
they
decide
if
it
should
move
on
or
you
know
you
should
abort
the
pipeline
right.
So
we
will
add
one
more
stage
here:
look
and
other
options
in
there.
So
you
can
run
a
Jenkins
Jeb
Jenkins
job
like
I
talked
about
what
we're
going
to
do
is
deploy
a
manifest
right.
So,
like
I,
said
we're
going
to
deploy
nginx
server.
A
Now
this
manifest
can
come
from
see
a
github
like
you
are
saved
your
manifest
in
github
and
all
that,
so
you
could
actually
have
the
manifest
come
from
github
or
artifactory,
and
all
that
sources
for
our
case,
we'll
just
type
in
the
manifest
here
I
have
a
simple,
manifest.
Then
I'm
going
to
pick
up.
A
A
Like
if
I
say
here
L,
so,
let's
add
a
new
stage
called
test
and
I
see
I,
don't
know
what
happened
here
or
I
didn't
select.
The
tank
apply
manifest.
Let's
say:
I
want
to
deploy
another
manifest
and
I
say
this
diplays
depends
on
the
previous
manifest
or,
let's
say,
I
want
to
make
it
deploy
on
the
first
manifest
oops.
Sorry,
what
I
wanted
to
say
was
deploy
on
the
manual
gentlemen.
A
A
So
let's
get
out
of
this
and
try
to
run
the
simple
pipeline
that
I
created
that
has
a
manual
judgment
and
then
deploys
a
manifest.
Okay,
let's
go
back
here.
There
is
my
pipeline
and
I'm
going
to
do
a
manual
run
on
that
pipeline
and
I
say
run
so
this
has
trigger
of
running
of
the
pipeline.
Like
we
talked
about
it
has
it
is
now
waiting
for
someone
to
date.
Some
action,
someone
can
go
review
stuff
and
if
they
don't
like
it,
this
is
stop
it.
A
It
will
stop
the
pipeline,
but
in
this
case
we
want
to
go
ahead
and
we'll
deploy
so
we'll
say
continue.
This
will
trigger
off
deployment
of
the
of
the
the
in
genomic
server.
We
talked
about
the
good
thing
about
this
is
that
you
can
monitor
the
progress
as
it's
going
on.
It
will
show
you
the
yam
hole
for
the
service.
That's
going
to
get
deployed,
you
can
look
at
this
over
here
now.
You
remember
our
annotation
or
the
manifest
was
very
simple,
but
you
will
notice.
A
Spinnaker
adds
a
lot
of
metadata
annotations
to
it
because
it
wants
to
manage
it.
You
can
scale
out
roll
back
and
all
that
it
does.
Why
does
manifest?
It
adds
additional
okay,
you
can
look
at
the
tar
status.
You
know
what
are
the
different
things
it
did
in
the
whole
process.
It
deployed
the
manifest
it
refresh
this
cache
and
make
sure
this
services
up
and
running
and
got
everything
available
right.
We
can.
A
A
A
When
you
have
say
a
port,
that's
not
healthy,
it's
red,
then
you
need
to
go
in
there
and
look
at
what's
going
on
so
instead
of
giving
your
end
users
or
developers
direct
access
to
your
stage
or
prod
environment,
they
can
come
in
here
and
you
know,
within
the
confines
of
this,
they
can
look
at
the
logs
and
figure
out.
What's
going
wrong
here,
right,
I
can
take
actions
on
the
pond
right.
I
can
make
edits
to
the
pods
right
here.
I
see
the
Hamill's,
and
here
I
can
I
see
them.
A
We
do
some
of
that
will
go
to
the
deployment
and
what
I
am
going
to
do
is
we're
going
to
scale
it
out
without
going
anywhere
right
from
here.
I
can
scale
this
out
from
one
to
two
after,
given
their
account
name
as
a
safety.
So
let
me
submit
this.
It's
actually
started,
deploying
it
okay
and
very
soon,
we'll
see
the
second
node
show
up
here,
I'm
going
to
close
the
sound
while
I
show
you
some
other
things
here.
A
We
created
a
service
right,
so
I
can
go
in
here
and
I.
Look
at
the
surface
that
it
got
created
so
using
this
I
can
access
this
engine
right.
So
it
shows
me
the
ingress,
internal
IP
and
and
the
ingress
URL
to
access.
So
I
can
click
on
this
and
there
you
go.
I,
have
access
to
the
nginx
server
that
I'd
applied
and
is
available
to
me
right
if
I
go
back
here,
I
scaled
it
down,
and
there
now
I
have
my
two
nginx
servers
available
to
me.
A
A
It
will
go
ahead
and
actually
refresh
the
cache
and
show
me
that
you
know
it
went
away.
So
this
is
what
I
meant
earlier
when
we
talked
about
a
spinnaker
allows
you
to
not
only
have
visibility
but
also
controlled
right.
So,
as
you
can
see
here,
you
have
a
pipeline
from
where
I
had
gone
ahead
and
deploy
my
infrastructure
things.
So
it's
managing
the
delivery
of
my
resources
right
while,
when
I
come
to
the
infrastructure,
tab
I'm
able
to
manage
that
infrastructure,
I
can
see
what's
going
on.
A
What's
their
status
and
I
can
act
on
them,
I
can
go
ahead
and
delete
them.
I
can
go
ahead
and
where's.
This
thing
I
can
go
ahead
and
and
scale
them
out.
I
can
edit
them.
You
know
make
some
changes
right
here
in
the
yeah
mode
and
deploy
them.
I
can
do
all
of
that
control
right
from
here
now.
Here
I
was
showing
you
four
cuban
artists.
I
could
do
the
same
thing
for
AWS
resources
too.
A
So
that
sort
of
in
a
very
brief,
covers
sort
of
the
spinnaker
features.
Let's
walk
through
I
walked
you
guys
through
you
know,
applications
in
spinnaker
I
walked
you
through
clusters
in
spinnaker,
which
are
like
as
I
say,
then
inventory
of
resources
in
an
application.
We
talked
about
pipelines
how?
What
are
the
different
configurations
and
pipelines?
We
talked
about
the
pipeline
stages
and
we
talked
about
pipeline
trigger
that
you
can
do
from
the
configuration
stage
where
you
can
have
github
trigger
or
a
Jenkins
job
completion
and
trigger
the
pipeline's.
A
You
can
enable
SSL
for
your
environments,
so
you
can
SSL
enable
both
the
UI
front-end
as
well
as
the
API
front-end,
and
that
commands
to
do
that.
Then
you
can
enable
authentication
right
now
you
so
I
just
went
into
the
you
are
there's
no
authentication
right,
so
you
can
enable
authentication
and
the
supported
methods
are
LDAP
or
sam'l
or
x.509
certificates.
A
So
those
are
supported
out
of
the
paths
and
you
can
also
enable
authorizations
where
the
providers
come
from
can
come
from
LDAP
groups,
Active,
Directory,
sam'l,
Google,
Groups
or
even
you
can
use,
get
up
teens
to
control
authorizations
and,
like
it's
mentioned
here,
you
can
use
it
to
control
who
has
access
to
one
applications.
What
accounts
and
pipeline
executions
like
you
may
have
a
pipeline
that
deploys
to
production,
but
you
don't?
You
want
only
the
apps
for
people
or
persons
to
be
able
to
execute
those
pipelines.
A
A
What
are
the
different
types
of
objects
that
spinnaker
allows
you
to
control?
How
to
install
it
in
a
Cuban?
It
is
a
common
is
so
it's
very
simple.
Less
than
10
minutes,
I
had
a
spinnaker
up
and
running
and
I
was
playing
with
it
and
we
walked
through
the
features
in
spinnaker
with
that
I
will
open
it
up
for
any
questions
or
any
comments
that
you
guys
may
have.
B
Ok,
so
I've
got
three
questions
in
the
Q&A
and
then
I'm
also
going
to
start
allowing
folks
to
to
talk.
So
let
me
just
address
those
questions
in
the
Q&A
first
and
then
folks
can
unmute
themselves
and
answer.
Excuse
me
ask
questions
so
here
we
go
okay.
So
the
first
question
is:
is
it
possible
once
it
has
been
bootstrapped
to
have
spinnaker,
deploy
and
update
itself.
A
That's
a
very
interesting
thing,
so
in
our
lab
or
environments,
what
we
do
is
we
use
vinegar
to
update
other
spinnaker.
So,
basically,
what
we
have
is
we
have
Hoover
or
a
master
spinnaker
that
we
use
to
update
other
Spinnaker's.
So
absolutely
that's
what
you
can
do
not
update
itself
per
se
but
use
a
spinnaker
to
update
other
Spinnaker's.
Okay.
B
A
Talk
about
that
a
little
bit
and
going
to
the
demo
I
guess
my
screen
is
still
being
shared.
Yes,
yes,
everything
is
in
spinnaker
is
cold
right,
so
you
know
we
saw
this
pipeline.
This
whole
pipeline
is
actually
stole
and
managed
as
a
JSON
file
right.
So
this
is
the
JSON
file.
Often
so
you
could
absolutely
manage
this
in
git
and
have
these
synced
whenever
key
changes
have
this
pipeline's
get
updated.
So,
yes,
you
can
have
pipe
this
as
code
and
managed
to
get
now.
A
Another
thing
which
I
did
not
cover
is
really
an
advanced
topic.
Is
this
pipeline
templates?
So
what
you
can
have
is
you
can
have
pipeline
templates
created
up
out
of
your
pipeline,
so
any
new
developer
or
a
group
coming
in
they
can
create
the
pipelines
out
of
that
pipeline
template
and
what
it
does.
Is
it's
really
a
template.
It
does
not
make
a
copy
of
the
pipeline,
so
your
actual
pipeline
references,
the
pipeline
template,
which
is
again
like
I,
showed,
is
a
JSON
file
and
it
has
parameters
and
all
that.
A
So
when
you
change
your
like
pipeline
template
on
the
pipeline's
that
were
derived
from
the
pipeline
template
inherit,
then
what
it
means
is
that
suppose
you
want
to
introduce
a
new
say,
security
scan
stage
in
your
pipeline.
You
update
your
pipeline
can
play
all
the
pipeline's
that
inherit
inherited
from
that
would
get
that
security
scan
stage.
So
that's
another
good
way
to
even
enforce
uniformity
across
different
pipelines.
A
A
Like
I
think
I
seen
in
the
beginning
is
that
Jenkins
has
is
traditionally
used
for
continuous
integrations,
and
you
should
absolutely
continue
to
do.
Do
that.
One
of
the
things
that
you,
what
I
showed
you
could
do
with
a
spinnaker
like
scaling
out
roll
back
and
all
that
you
could
absolutely
do
in
Jenkins.
But
you
have
to
write
code
for
that.
There's
no
first
class
support
in
Jenkins
for
that
right.
So
absolutely
you
can
do
that
in
Jenkins,
but
what
spinnaker
provides
is
providing
first-class
support
for
some
of
those
things
in
the
UI.
A
It
supports
roll
back
strategies,
which
is
very
important
when
you're
doing
continuous
deployment
right.
You
have
to
write
code
in
Jenkins
to
do
that,
so
you're
rolling
out
something,
and
you
find
out
that
there's
an
issue
with
the
rollout
in
production
and
you
want
to
roll
that
back
and
you
want
to
do
that
in
an
automated
way.
A
So
this
different
deployment
strategies
like
blue,
green
or
some
people
call
it
red
black,
so
you
can
employ
that
and
spinnaker
would
automatically
handle
that
those
basically
are
provided
as
first
possible.
So
some
of
those
features
which
are
in
built
into
spinnaker
makes
spinnaker
sort
of
unique
in
continuous
delivery.
Can
you
do
them
in
Jenkins?
Absolutely
you
can,
but
you
have
to
write
cold
water
and
also,
as
I
mentioned
earlier,
spinnaker
doesn't
replace
Jenkins
I
think
it
just
helps.
You
improve
the
continuous
delivery
process
to
deploy
faster
and
better.
B
A
So
Tecton
is
a
beautiful
custom
cuban
artists,
so
it
basically
manages
cuban
artists
manifests
and
manages
them
very
well.
So
it's
the
choice
that
you
have
to
make.
If
Tecton
does
your
work
up
sure,
but
it's
purely
focused
on
Cuban
artists,
whereas
if
you
want
to
have
multi-cloud
support
where
you
are
using
it
to
manage
AWS
resources,
lambda
functions,
ECS
resources
along
with
kubernetes
or
Cloud
Foundry.
A
That's
why
spinnaker
comes
into
play,
also,
not
sure.
If
Tecton
has
some
of
these
things
like
manual
judgment
stages
and
all
that
typical
in
the
workflow
process,
if
it's
there
in
Tecton,
so
then
there's
feature
parity,
but
otherwise
you
know
this
multi
cloud
support
is
definitely
a
feature
that
makes
spinnaker
different
than
that.
B
B
A
What
you
could
definitely
do
is
that
if
your
gift
changes,
you
could
have
another
pipeline
that
can
trigger
an
update,
see
you're
pulling
the
pipeline's
from
gate
and,
put
it
into
say,
you
are
using
mini
or
s3
and
move
the
pipelines
into
that
storage,
and
that
would
be
reflected
back
in
spinnaker
immediately.
So,
yes,
you
can
build
a
pipeline
to
manage
the
pipeline's
from
gate
into
spinnaker.
It's
either
a
pipeline
within
the
same
spinnaker
itself
or
a
separ
spinning.
C
D
A
Absolutely
yes,
so
actually
that
is
another
great
question
and
you
know
some
people
ask:
is
that
do
I
need
a
spinnaker
for
each
instance?
No,
you
could
have
one
spinnaker
that
you
can
use
to
manage
multiple
resources,
multiple
Cuban,
Etta's
resources,
be
them
on
Prem
or
in
the
cloud.
Only
requirement
really
is
there
be
able
to
connect
to
that
cuba
knitters
resource
from
where
spinnaker
is
running
right?
So
that's
really
the
only
requirement.
Otherwise,
you
can
use
the
single
spinnaker
to
manage
multiple
Cuban.
A
A
B
B
Well,
thank
you.
So
much
normally
I
really
appreciate
your
your
time
and
coming
on
and
being
part
of
the
CDF
community.
We
hope
to
see
more
from
Optimax
about
spinnaker
and,
if
folks
don't
know,
we
do
have
the
call
for
papers
open
for
CD
con,
which
is
happening
October,
it's
a
virtual
event,
so
we
are
taking
talks,
we'd
love
to
see
more
of
our
commute
of
our
spinnaker
community
represented.
We
also
have
an
ambassador
program
if
you
are
not
aware,
we'd
love
to
also
see
more
spinnaker
folks
there.