►
From YouTube: Do's and Don'ts for Securing and Governing your Spinnaker Environment - Kyle Mitchell & David Beale
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
Do's and Don'ts for Securing and Governing your Spinnaker Environment - Kyle Mitchell & David Beale, Armory
Spinnaker is powerful, flexible and complex. There are multiple ways to do everything and this talk will provide real-world advice and recommendations on the best (and worst) ways to secure and govern your environment. The presenters will draw from their experience deploying, managing and supporting Spinnaker across a range of customer environments (mid-size to large enterprise) and across multiple industries from retail to banking to tech. Recommendations and specific code configurations will be presented which you can bring back to your own organization to evaluate if changes are needed or as input in your Spinnaker planning process.
A
All
right
thanks
everyone
for
coming
to
our
talk,
we're
going
to
be
talking
today
about
the
best
practices
of
Spinnaker,
with
primarily
a
focus
on
security
and
governance,
but
we'll
talk
about
a
little
bit
of
everything.
This
is
going
to
be
kind
of
like
I'm,
calling
it
a
mid-level
talk.
So
it's
not
exactly
a
deep
dive,
although
DB
will
definitely
get
into
some
details.
But
it's
not
so
high
level
that
you
can't.
A
A
So
a
bit
about
us,
so
Kyle,
Mitchell,
Technical
product
manager
for
Armory,
so
I
manage
the
Spinnaker
Enterprise
product
line
we
have
at
Armory.
We
also
have
a
hosted
Solution.
That's
a
different
product,
though
I'm
based
out
of
Calgary
Alberta
Canada,
so
came
here
for
the
balmy
weather.
It
snowed
last
weekend
for
me,
so
that
was
great,
but
I've
been
in
it.
A
B
Hey
hey
David
Beale,
as
it
says
there
Solutions
engineer,
but
I
part
of
that
I
was
a
back-end
developer,
SRE
devops!
You
know
all
of
those
things.
I've
used
Spinnaker
at
scale,
I've
been
the
one
and
only
engineer
for
a
pretty
pretty
big
company
using
Spinnaker
and
I've
used
it
in
startup
environments
too.
So
I
have
a
lot
of
experience
with
it
at
a
scrappy,
do-it-yourself
level.
B
A
So
why,
yes,
so
as
Armory
is
a
vendor
and
partner,
so
we've
have
the
lucky
opportunity
of
observing
installing
configuring
monitoring
all
kinds
of
different,
spanner
environments
across
tons
of
different
customer
environments.
Different
Industries,
as
you
can
see
up
on
the
screen,
you
know
from
e-commerce,
banking
Tech,
so
we've
basically
seen
it
all
and
we're
really
here
just
so.
You
can
learn
from
our
experience.
So
you
know
some
of
the
challenges
we've
seen.
A
Hopefully
you
can
Skip
and
avoid
so
before
I
hand
it
over
to
DB
who
will
take
us
through
the
bulk
of
the
presentation
on
the
recommendations.
Just
wanted
a
context
and
level
set
a
bit
so
as
the
slide
shows,
Spinnaker
is
powerful
but
complex,
so
I
could
get
into
that
old.
Stripe
of
you
know
great
power,
great
responsibility,
Spider-Man
thing,
but
I'll
just
vaguely
reference
it,
but
no
in
all
seriousness.
Obviously
Spinnaker
came
from
Netflix
came
from
Google
fast
forward
to
today.
We've
got
a
ton
of
you
know.
A
Brand
household
brand
names
that
are
are
running
their
business,
Apple,
Home,
Depot
Salesforce,
there's
a
bit
of
a
myth
out
there
that's
vinegar,
sort
of
on
the
decline.
It
was
kind
of
alluded
to
in
the
Keynotes,
but
you
know
hopefully
over
the
next
two
days
and
maybe
even
into
kubecon
that
myth
gets
dispelled.
A
It's
really
not
going
away.
The
the
key
feature
that
we
really
want
to
highlight
is
life
cycle
management.
So
that's
like
one
of
the
features
that
kind
of
distinguishes
Spinnaker
from
many
of
the
other
CD
tools
out
there,
and
that
is
that
you
can
in
a
single
tool,
manage
a
git
commit.
You
know
all
the
way
from
you
know
a
CI
push
to
to
production
across
multiple
clouds.
Multiple
environments,
you
don't
need
multiple
tools,
you
don't
need
to
run
things
once
and
hand
it
off.
A
You
can
have
that
in
a
single
pane
of
glass
view.
So
that's
something
sort
of
to
keep
in
mind
as
these.
You
know
these
do's
and
don'ts
are
talked
about,
and
you
know
just
a
quick
segue
into
what
DB
is
going
to
talk
about
is
Spinnaker
is,
by
definition
a
CD
tool.
It's
not
a
CI
tool
with
CD
kind
of
bolted
on
after
the
fact
is
an
afterthought.
It's
a
dedicated
specialized,
CD
tool,
so
so
yeah
with
that
context.
In
mind,
pass
it
over
to
DB
to
walk
us
through.
B
Awesome,
thank
you.
Kyle
yeah.
You
know,
I've
been
on
the
other
side
of
this
a
lot
and
I
like
things
to
be
as
interactive
as
possible.
So
if
there's
any
point
where
you
have
a
question
or
what
I'm
saying
doesn't
make
sense,
just
you
know
speak
and
we'll
talk,
but
yeah
everything.
Any
Kyle
said
it's
totally
true.
Spinnaker
is
powerful
and
flexible
and
it's
definitely
complex
but
there's
some
ways
to
make
it
simpler
and
still
secure.
B
B
Bringing
those
vulnerabilities
in
so
I.
Think
that
you
know
it's
really
important
important
to
think
of
it
like
this.
You've
got
your
code
change,
you're
testing,
your
code,
you're
building
it
you're
packaging
and
Publishing
it,
and
what
does
that
give
you
that
gives
you
an
artifact
from
that
point
on
you're
in
CD,
and
that's
really
what
Spinnaker
does
is
it
takes
an
artifact
from
a
secure
place
and
deploys
it
to
a
secure
place
now?
What
an
artifact
is?
It's
really
up
to
you?
It
can
be
a
Docker
container
like
I
talked
about
it
can
be.
B
B
And
yeah
getting
into
that
document
your
process
tag
your
images
properly
and
use
artifact
storage.
There's
a
million
different
ways
to
do
this.
You
can
have
all
of
your
documentation
in
your
code.
You
can
tag
your
images
pragmatically
using
gitshaws
or
md5
checksums
or
you
know
whatever
you
want
to
do,
but
having
this
like
defined
and
and
locked
down
is
really
going
to
be
your
biggest
value.
Add
once
you
get
into
the
deployment
process
and
then
for
storage.
B
Obviously
like
secret
management
is
like
a
pretty
like
talked
about
and
and
drilled
into
the
ground
subject,
but
you
don't
put
secrets
in
your
code:
you
don't
put
it
on
live
production
servers
unless
they're
hashed
don't
do
that
in
your
CD
either.
You
know
like
treat
all
of
your
workloads
like
they're
sort
of
production
code
or
production,
builds
and
and
make
sure
that
you're
not
like
just
directly
referencing
the
ALB
of
your
kubernetes
cluster.
When
you're
deploying
your
artifacts
to
it,
you
know
hash
it
and
then
finally
or
not.
B
B
B
It
should
be
a
part
of
your
plan
if
you're
dealing
with
like
HIPAA
or
any
kind
of
financial
compliance.
This
is
kind
of
a
no-brainer,
but
for
Less
regulated
Industries.
You
still
want
to
treat
this
like
a
piece
of
core
infrastructure
run
in
the
same
way
that
you
know
anything
else
in
your
stack
would
be.
B
This
is
a
little
bit
of
a
Broad
and
and
like
easy
to
argue
about
subject,
but
you
know,
Spinnaker
is
kind
of
only
as
good
as
the
outside
security
enforcement
that
you
have
around
it.
So
whether
you're
using
like
saml
or
you're,
using
like
I,
said
our
policy
engine
OCTA
any
of
those
Integrations
I'm
not
going
to
get
too
heavily
into
it,
because
I
don't
want
to
like
re
regurgitate
or
re-emphasize
what
Jason
already
talked
about.
But
you
know
your
your
organizational
policies
should
be
inherited
into
your
deployment
process.
B
Is
the
the
tldr
and
yeah
like
I,
said
before
Spinnaker
is
pretty
safe
out
of
the
box?
So
it's
not
like
it's
a
this
crazy,
like
like
Rogue,
open
source
application
with
no
like,
like
patterns
around
it
or
any
kind
of
historical
relevance
of
how
it's
worked
for
other
companies.
You
know
you
don't
really
hear
about
Netflix
getting
hacked
too
often
at
least
I
haven't.
B
B
Yeah,
you
know
I've
I've
seen
some
pretty
questionable
use
of
like
environment
variables.
You
know
you
can
set
environment
variables
in
Spinnaker,
it's
a
it's
a
deployment
stage
and
I've
seen
people
just
hard
code,
some
things
into
that
that
they
probably
shouldn't
and
then
I've
seen
some
pretty
really.
The
thing
that
I
wanted
to
drive
home
was
the
weaknesses
of
your
your
CI
pipeline.
That
you're,
inheriting
so
I've
seen
a
lot
of
things
where
it's
like.
B
Oh
yeah,
you
know,
we've
just
got
this
dot
m
file
with
a
bunch
of
environment
variables
that
gets
sourced
in
our
Docker
build
process
and
that's
in
VCS
or
it's
even
you
know
being
pulled
from
like
an
S3
bucket
or
something
so
I
think
you
know.
Poor
Secrets
management
is
probably
the
thing
I've
seen
the
most
of.
B
How
do
you
manage
secrets?
Well,
I
mean
you
know,
that's
pretty
subjective
right.
You
can
manage
Secrets
any
way
you
want,
but
you
know
Spinnaker
I've
seen
it
integrated
pretty
tightly
with
Vault
I've
also
seen
people
just
use
like
KMS,
storage
or
Amazon
secret
manager.
It
really
depends
on
the
platform.
I
would
just
say
treat
it
like
any
other
application
in
your
stack.
You
know
whatever
you're,
using
for
Secrets
management
and
the
rest
of
your
application,
use
that
for
your
deployments
as
well.
B
And
one
more
point
on
that:
using
a
product
like
policy
engine
and
being
able
to
set
individual
policies
for
pipelines
really
gives
you
a
lot
of
value,
because
then
you
know
a
lot
of
times
your
secrets.
Your
secret
management,
might
be
a
little
looser
in
lower
environments.
You
know
Dev
staging
you're,
not
using
production
databases.
A
Let's
go
back
yeah,
so
this
slide
just
just
to
highlight
the
message
here,
which
is
that
essentially
using
the
same
identity
provider,
groups
that
you
have
already
established
in
your
identity
provider
leverage
those
as
much
as
you
can
in
Spinnaker,
don't
try
to
recreate
them.
Because
then
you
have
a
synchronization
problem.
Where
you
know
you
add
somebody
to
a
group
and
then
it's
a
different
group
in
Spinnaker.
A
So
that's
that's
kind
of
the
whole
point
of
this
message
is
is
pushing
those
and
that's
even
why
it's
organizes
this
push
down
kind
of
concept,
so
push
from
your
IDP
into
Spinnaker
and
then
using
the
Fiat
service.
You
can
map
those
to
your
Cloud
providers
without
actually
having
the
credentials.
You
know
that
the
cloud
provider
credentials
right
in
there
and
although
we've
alluded
to
it,
I
just
found
a
hammer
at
home.
A
Is
you
know
if
you're
it
from
a
real
governance
perspective
and
I
think
this
is
in
particular
importance
for
any
kind
of
regulated
company
government
entities?
Etc.
You
need
to
have
a
policy
enforcement
because
that's
that,
if
you're
talking
to
CIO
or
your
security
team
Etc
regard
they,
you
know,
regardless
of
the
tool.
In
this
case
it's
the
CD
tool.
You
have
to
be
able
to
efficiently
enforce
the
the
organizational
policies
and
security
situations.