►
From YouTube: Documentation SIG - Tiffany Sonny, Armory
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
Documentation SIG - Tiffany Sonny, Armory
A
E
F
G
C
C
A
Super,
actually,
you
are
in
the
right
meeting
great.
So
thank
you
again
and
thank
you
for
taking
a
minute
to.
Let
me
know
who
you
guys
are
since
I'm,
so
new
to
the
overall
environment,
so
I
thought
that
the
way
that
I
would
like
to
spend
this
time
is
talking
to
you
guys
about
what
you
think
is
great
about
Spinnaker
and
what
you
think
could
make
the
docs
better.
But
I
didn't
come
just
with
that.
In
my
mind,
I
I
came
with
a
mission
statement,
because
this
is
my
mission.
A
This
is
why
I
joined
Armory,
and
this
is
why
I'm
so
enthusiastic
about
being
part
of
the
open
source
support
around
Spinnaker
I
really
want
to
to
create
Cutting
Edge
documentation
to
support
Spinnaker
I
agree
with
the
the
member
over
there.
That
said,
good
talks
generate
usage
and
I.
Don't
think
that
in
all
of
my
time
and
I've
been
working.
A
This
product
now
I
know
how
to
use
it.
I
know
how
to
make
it
useful,
so
I
really
think
that
re-architecting,
the
dock
set
is
probably
a
big
goal
for
this
project
and
something
that
I
would
like
to
see
accomplished
by
this
time
next
year,
and
my
problem
statement
on
that
is
that
I
hear
a
lot
of
feedback.
Oh
the
docs
aren't
helping,
but
there's
a
lot
of
content
there.
So
why
aren't
the
docs,
helping
and
I
think
the
reason
that
there's
a
lot
of
content?
A
But
it's
not
helping
is
just
it's.
It's
organized
in
a
less
than
ideal
way
and
I
want
to
use
this
time
to
just
figure
out.
How
do
we
reorganize
it?
How
do
we
enhance
it
and
how
do
we
continue
to
curate
a
dog
set
that
that
is,
that
is
the
pride
and
joy
of
the
product
and
not
the
redheaded
bastard
child
of
the
product,
which
maybe
it
feels
like
to
me
a
little
bit
right
now.
A
The
so
I
spent
some
time
over
the
last
few
days.
Thinking
well,
what
are
some
solutions
that
I
could
come
to
this
group
with
so
that
I
didn't
make
it
all
about
what
you
guys
think,
but
also
maybe
have
some
some
ways
to
generate
thoughts
and
ideas,
and
the
very
first
thing
that
that
occurred
to
me
is
where's
the
search.
Why
can't
I
keyword,
search
on
this
on
this
doc
set
and
I?
Think
that's
an
easy
thing
to
fix,
and
if
everybody
in
this
room
agrees
that
that
would.
A
Or
if
maybe
there's
a
reason
why
we
don't
currently
have
keyword,
search
in
the
duck
set?
Somebody
could
tell
me
why,
but
that
just
feels
like
low
hanging
fruit.
We
should
just
fix
that
right
away
like
next
week,
if
we
could
Nobody
Knows
Why
okay
show
of
hands
how
many,
but
how
many
people
think
it
would
be
good
to
have
some
keyword
search
on
the
docs
all
right,
oh
I
think
we
have
a
quorum
anything
from
the
online
community.
Okay
am
I,
talking
slow
enough.
A
So
the
next
thing
I
thought
about
that
I
would
really
like
to
see
on
each
topic
is
a
link
to
the
GitHub
issues
like
we're,
not
really
giving
the
end
user
a
way
to
say
right
away:
hey
even
hey,
I
liked
it
would
be
nice,
but
that
really
never
happens
in
documentation.
You
only
hear
of
something's
wrong,
but
but
if
we
hear
this
General
oh
the
docs
are,
you
know,
aren't
helping
people,
but
we
don't
really
have
a
good
sense
of
where
they're
struggling.
A
We
should
probably
find
a
way
to
include
a
link
to
the
Getty,
so
they
could
just
click
and
and
maybe
even
a
a
vote
like
a
like,
not
like
button,
so
they
can
say,
hey
I,
liked
it
or
I
didn't
like
it
and
then
maybe,
if
they
didn't
like
it,
then
it
leads
to
that
another,
a
path
to
that
GitHub
issues,
page
where
they
can
file
an
issue
and
and
I'll
take
a
raise
of
hands.
If
everybody
agrees
with
me
on
that,
how
many
people
think
that's
like
a
high
priority
that
would
really
help?
A
So
I
also
thought
that
I
would
like
to
improve
the
docs
by
improving
the
landing
page,
and
this
is
I
think
something
that
we're
also
thinking
about
in
the
armory
dogs
too.
How
do
we?
How
do
we
improve
the
landing
page
so
that
when
people
hit
hit
the
URL
and
they
land
somewhere,
they
can
quickly
go?
Oh,
that's
what
I
want-
and
these
are
some
of
the
ideas
these
these.
These
pipe
separated
ideas
were
the
ideas.
I
had
and
I'd
love
it.
A
A
A
G
So
so,
I'm
really
big
on
documentation,
like
I
I've,
said,
and
even
though
I
am
really
big
on
it.
I
feel
like
a
lot
of
tools
that
I
use
I,
don't
spend
any
time
in
the
documentation,
because
they're,
usually
lacking
or
they're
hard
to
navigate
like
you
were
suggesting
and
I
find
myself
like
nine
times
out
of
ten,
just
like
looking
through
the
code
and
the
only
time
that
I
think
I've
never
had
done.
This
was
actually
through
stripe
like
Stripes
how
they
document
stuff.
G
They
do
a
fantastic
job
so
and
I
I
think
you
know
like
one
of
the
things
that
you
put
up.
There
is
like
links
to
references
and
tutorial
content,
one
of
the
big
things
that
they
do
is
well.
This
is
mostly
for
like
apis
and
whatnot,
so
this
might
not
be
complete,
100
the
same
use
case,
but
when
they're
talking
about
strictly
apis
and
whatnot,
they
have
a
button
that
clicks
the
language,
and
it
shows
you
like
how
to
go
about
using
that.
G
So
that
was
like
huge,
and
that
was
the
first
time
where
I
was
like
these.
This
is
the
first
time
I've
never
had
to
leave
the
docs
page
and
go
to
code,
and
that
was
like
huge
for
me.
So
that's
something
that
I
think
would
be
really
nice
and
then
there's
like
kind
of
like
three
caveats
to
like
docs
like
you,
have
the
how
to
use
Spinnaker
right,
which
is
just
like
you
know,
like
an
everyday
person
first
coming
in
wanting
to
use
Spinnaker.
G
But
even
you
know,
even
then,
when
I
see
that,
like
links
to
references
and
whatnot
I,
think
I
think
that
could
be
really
useful.
So
that's
like
something
I
would
like
to
see
like
I,
don't
know
if
you've
ever
been
to
stripe
and
seen
how
they
do
docs.
It's
literally
the
best
thing
I've
ever
seen
in
terms
of
docs.
A
So
this
is
this:
is
my
proposed
sort
of
re-architecture
of
the
existing
dock
set
high
level?
Toc
I
think
the
biggest
problem,
even
though
I
still
I
still
think
it's
a
fundamentally
really
well
organized
doc,
set
I
think
that
the
the
biggest
problem
for
adoption
is
that
it's
not
easy
to
figure
out
what
you're
trying
to
get
and
we
can
all.
Obviously
we
can
fix
that
with
some
good
search,
but
I
thought
maybe
moving.
A
Some
of
the
more
important
topics
to
a
higher
level
would
Foster
some
some
some
better
feedback
on
the
docs
and
some
better
adoption
and
and
some
happier
users,
maybe
at
the
end
of
the
day
this
isn't
a
a
complete
list.
I
have
not
read
and
and
and
thoroughly
analyzed
every
single
topic
in
the
existing
dock
set
that
that
would
take
longer
than
I've
even
been
a
part
of
Armory,
but
from
what
I've
done
and
what
I
I
know
and
and
the
the
education
that
I
have
thus
far
about
Spinnaker.
F
I
have
another
one
from
the
virtuals
from
Shane
Emery.
One
thing
we
found
is
that
there
are
a
lot
of
hidden
features
and
code
options,
not
documented.
We
either
found
the
solution
by
Googling
or
trial
and
error.
Some
info
came
from
Armory
optimax
blogs,
Etc,
not
too
much
from
the
Spinnaker
OSS
website
or
GitHub.
A
Isn't
down
so
we
don't
really
have
a
well-curated
introduction,
page
and,
and
my
proposal
on
that
was
like
one
topic,
that
sort
of
a
conceptual
that
briefly
says
this
is
this
is
what
it
is.
This
is
why
it
is
why
you
would
use
it
what's
great
about
it
and
then
some
of
the
key
features,
and
that
would
probably
take
like
maybe
some
revision,
every
every
feature
released,
there's
probably
new
features
that
the
community
was
wanting
and
and
it
would
probably
need
to
be
updated
frequently.
A
A
That's
the
kind
of
feel
that
I
want
for
like
the
introduction
page
and
then
obviously,
maybe
some
some
related
linking
and
and,
like
you
said
some.
Maybe
a
delineation
between
oh
I
just
want
to
figure
out
what
Spinnaker
is
and
oh
I
need
to
know
how
to
do
this
thing
and
I,
like
your
idea
about
the
reference,
docs
and
I
think
that
that
we've
already
even
discussed
it
internally
that
it'd
be
good
to
have
them
divided
by
code,
so
you
can
quickly
say:
oh,
this
is
how
I
do
this
with
go.
A
This
is
how
I
do
this
with
Java.
This
is
how
I
do
it
with
JavaScript
or
whatever
the
the
use
case
is
for
that
particular
API
and
then
links
to
reference
and
tutorial
content
on
the
online
introduction
page.
That
I
think
is
always
helpful
and
then
the
next
high
level
marker
I
think
for
the
TOC
would
be
usage
right.
A
That's
the
next
place,
you're
going
to
go
okay,
I,
I
kind
of
know
what
it
is,
how
do
I
use
it,
the
biggest
the
biggest
blocker
to
my
adoption
was
installation
it
just
it
took
so
many
cycles
that
I
was
embarrassed,
that
I
wasn't
producing
any
work
for
my
company,
but
here,
a
month
ago
and
I
usually
I
started
at
a
at
a
highly
technical
company.
As
a
technical
writer
and
within
a
few
weeks,
I'm
I'm
useful
to
the
company
and
with
Armory
it
took
a
bit
longer.
A
Probably
probably
75
80
of
these
cases,
but
then
also
the
Debian
package
path
to
to
Spinnaker
and
I
I
would
love
some
feedback
on
that,
because
I
am
still
barely
able
to
install
Spinnaker.
So
anybody
who
has
more
information
can
give
me
some
more
insight
on
what
would
be
helpful
from
an
installation
perspective
that
would
be
awesome
to
hear
from
yeah
great.
D
I
would
say,
like
the
biggest
oh
sorry,
I
think
as
a
whole.
It
has
to
be
broken
down
because,
like
installing
it
as
we're
finding
is
not
easy.
Like
there's
a
lot
of
paths
to
install
I
would
I
would
I
was
wondering,
if
maybe
there's
a
path
where
we
have
like
all
right.
At
least
you
have
it
started,
and
you
have
a
UI.
A
D
Yeah
I
mean
it's:
it's
probably
like
it
almost
starts
like
with
an
overview
very
simply
like
we're
going
to
create
a
pipeline
and
just
like,
have
it
Echo
something
or
just
to
make
sure
that,
like
the
internal
processes
within
like
all
the
components,
are
working
together,
not
even
getting
technical
as
to
how
they
all
talks
to
one
another,
but
at
least
then
you
know
hey,
we
validate
your
installs
working.
You
did
an
approval
stage.
That
means
that
messages
are
flowing,
things
are
kind
of
recorded
and
your
pipeline
saved
somewhere
so
and
then
from
there.
D
You
can
then
dive
into
like
the
advanced
use
cases
like
all
right.
So
now,
let's
deploy
potentially
to
AWS
or
to
kubernetes
or,
let's
add
kubernetes
as
a
provider.
At
that
point,
because
you
you
can
start
Spinnaker
without
any
account
and
at
least
get
something
to
work
right
and
at
least
that's
one
aspect,
because
then,
from
the
other
question,
it's
like
all
right,
I
have
Spinnaker
I,
have
a
giant
cluster
I,
have
everything
running?
G
Yeah
so
when
I
first
started
on
the
speaker
team,
so
I
had
no
experience
experience
with
Spinnaker,
but
it
did
take
me
several
hours
to
actually
like
chug
through
it
and
I
like
get
it
up
and
running,
but
I
found
what
I
did
was
that
really
helped
me
is
I,
looked
at
that
graph
that
you
guys
have
on
your
website
that
was
like.
Oh,
this
service
talked
to
this
service
to
this
service.
G
I
was
like
okay,
I'll
start
with
Cloud
driver,
because
that
doesn't
need
really
anything
and
I'll
run
that
and
just
curl
it,
and
if
I
can
curl
it
and
get
art
like
you
know,
it
returns
like
a
blank
list
of
artifacts
that
I
just
curled
like
so
I
just
look
for
like
get
requests
and
I
was
just
like
curling
those
and
once
I
saw
that
that
service
was
working.
I
would
then
work
on
the
next
service
and
I
found
just
doing
it
incrementally,
like
that,
really
helped
me
getting
Spinnaker
up
and
running.
A
H
F
So
there
is
a
comment
in
the
chat
from
Ashley
and
forgive
me
I,
don't
know
all
of
the
lingo
here.
The
Debian
instructions
have
been
updated
and
mostly
work.
Now,
there's
just
an
issue
with
the
halyard
1.1.52.0
caused
by
the
spring
boot
upgrade,
but
once
that
is
fixed,
the
docks
are
actually
accurate.
The
only
issue
with
the
halyard
V
1.5
1.0
is
that
it
doesn't
create
the
home
directory
for
the
Spinnaker
user.
A
All
right,
so
this
is
where
I
was
really
hoping.
I
mean
I'll,
I'll
post
this
well,
actually
I,
don't
even
have
to
post
it'll
be
in
the
video,
but
here's
where
I
was
really
hoping
to
get
some
feedback
on.
What
are
the
big
use?
Cases
that
belong
in
the
dogs-
and
this
is
where
I
don't
have
that
depth
of
knowledge,
as
as
a
user
to
say.
A
Well,
what
are
the
top
10
things
that
you're
gonna
do
with
with
vinegar
that
caused
you
to
adopt
it
in
the
first
place
and
if
we
could
figure
out
what,
though,
if
I
could
figure
out?
What
those
are
you
guys
probably
already
know,
then
perhaps
I
could
guide
the
new
user
to
the
most
compelling
features
and
the
most
compelling
use
cases
in
a
more
efficient
way
through
the
docs.
G
So
one
thing:
that's
not
really
documented
that
I'm
pretty
sure
like
every
one
of
us,
like
probably
uses
like
it's
document,
it
has
a
page,
but
is
its
spell
like,
like
spell
like,
there's
like
no
documentation
on
like
how
to
use
that
like
how
to
use
that
in,
like
a
like
there's
a
stage
like
evaluating
variables
and
whatnot
like
how
to
use
that
how
to
like
you
know,
you
then
reference
those
like
through
spell
Expressions,
so
being
able
to
like
document
that
and
showing
like
you
know.
This
is
how
you
build
a
pipeline.
G
I
A
A
So
the
next
thing
I
was
thinking
about
is
continuous
integration.
Options
like
when
I
first
started,
I
just
assumed
that
Circle
CI
would
be
part
of
the
solution.
But
that
was
my
naiva
T,
not
understanding
that.
Well,
maybe
Jenkins
and
circle
CI
are
sort
of
our
Spinnaker
competitors.
And
how
do
you
guys
all
see
that-
and
somebody
already
wrote
this
as
a
thought-
excellent.
E
Yeah,
so
not
competitors
and
I
can
say
it's
definitely
not
up
to
date.
So
Jenkins
should
stay
I'm,
not
sure
about
Circle
CI,
but
there's
also
gate
labci,
which
is
recently
added
and
Travis.
Ci
has
also
supported,
and
I
can
volunteer
to
do
some
of
that,
at
least
because
we
did
the
gitlab
CI
integration.
E
So
we
can
document
that
and
maybe
maybe
when
we
add
new
features
it
shouldn't
get
merged
until
there's
docs,
because
I
mean
that
that's
what
happened
there
is
I,
never
did
the
documentation
and
then
it
eventually
got
approved
and
merged
and
a
few
months
later
it
was
released
and
we
just
kind
of
had
forgotten
at
that
point.
So.
A
E
A
C
I
was
just
trying
to
clarify
if
we're
talking
about
you
know
where
we
run
automated
tests
for
Spinnaker
itself,
and
that
is
GitHub
actions,
but
if
it's
possible
to
integrate
GitHub
actions
with
Spinnaker
as
far
as
like
triggering
pipelines
and
I
think
the
answer
is
no
is
coming
I.
If
somebody's
working
on
it
that's
great.
A
The
shoe
one
that
will
you
generate
one
for
me
and
we'll
get
on
that
one
too
excellent.
We
already
are
populating
the
the
year
of
work.
I
have
to
do
excellent,
though
good,
and
then
my
next
question
for
this
team
was
so
I
really
felt
like
after
the
conversation
this
morning,
and
really
probably
even
before
this
morning,
that
the
customized
content
is
nested
too
deep,
given
where
the
community
seems
to
be
going
with
adoption.
A
So
I
wanted
to
bring
that
up
to
the
surface
and
and
I
see
a
lot
of
nods,
so
I'm
gonna
I
won't
even
ask
for
a
show
hands.
I'm,
just
gonna
assume
that
everybody
agrees.
That's
that's
a
task
worth
tackling
and
then
I
didn't
know.
If
I
I,
don't
really
feel
like
that,
the
documentation
that
exists
on
building
pipelines
is
cohesive
and
that
just
could
be
my
own
ignorance
again.
D
I
mean
I,
guess
hey.
This
is
where
I
always
struggle,
because
you
know
you
can
have
a
two-stage
Pipeline
and
be
successful
with
Spinnaker,
and
then
you
can
have
a
30
stage
Pipeline
and
be
extremely
successful
too.
So
it's
almost
like.
We
have
to
guide
them
and
show,
or
rather
guide
what
you
can
do,
show
what
you
can
build
and
then
maybe
it's
like
as
simple
as
showing
a
simple
example
and
maybe
an
extreme
example
and
then
saying:
hey
We're,
not
gonna,
solve
cicd
for
your
company.
That's
what
you're,
probably
tasked
with
right.
D
We're
probably
gonna
tell
you
you
don't
need
security
scans
you're,
like
I,
can't
believe
you
said
that
that's
crazy,
you're,
an
asinine
and
like
that's.
You
need
to
have
that
in
there.
Well,
that's
great,
but
then
every
organization
does
different
things
at
different
stages
right.
So
that's
maybe
more
like
here's
what
you
can
do.
Here's
here's
a
crazy
example
like
a
full,
detailed
Pipeline
and
maybe
like
a
base
example.
D
G
And
so
I'm
I
like
to
like
Tinker
with
things
but
I,
think
it'd
be
awesome
to
have
like
a
Spinnaker
playground
even
like
that.
Just
shows,
like
example,
pipelines
that
you
could
just
like
click
and
be
like.
Oh
look
at
what
this
does.
You
know
and
then
like
actually
like
run
it,
and
it
just
like,
shows
you
what
the
output
is.
I
think
would
be
really
useful
and
just
seeing
like
the
different
use
cases
that
that
you
know
examples
that
might
people
might
want
to
see
yeah.
So
that
would
be
awesome.
Awesome.
A
I
Do
I
do
have
a
follow-up
for
that.
We
Fernando
and
myself
had
a
Google
summer
of
code
mentee
two
years
ago
and
he
created
try.spinnaker.io
and
it
was
a
way
of
running
Spinnaker
to
spin
up
give
give
users
access
for
I,
think
24
hours
or
something
like
that,
and
it
would
lock
down
the
the
permission
set
for
that
cluster
was
running
on
so
that
you
can
only
pull
down
Debbie
and
nginx
images.
So
all
you
can
do
is
run
a
pipeline.
I
A
When
I
think
of
ways
to
deploy
I
think
AWS,
gcp
and
Azure,
but
but
am
I
missing
anything
well
kubernetes
yeah
I
should
have
put
that
there
yep.
Oh,
no,
no
yeah
ways
to
deploy
your
apps
like.
Where
are
you
going
so
I
know
we
can
deploy
across,
but
is
there
a
bigger
breadth
of
possibilities?
Besides
the
three
and
then
kubernetes.
I
Yeah,
so
there's
there's
a
a
lot
of
different
deployment
options.
Kubernetes
should
definitely
be
be
up
there
as
well,
but
then
there's
a
whole
slew
of
cloud
providers
or
Cloud
targets
that
are
not
well
maintained,
so
we
we
may
want
to
actually
list
them
and
mention
on
the
docs
that
they're,
not
maintained
and
also
I,
would
I
would
also
propose
adding
a
call
to
action
on
that
page
and
say
hey
if
you're
using
this,
please
let
us
know
we
need
to
know
otherwise.
I
A
H
Right
I
think
for
the
open
shift.
There
may
be
some
changes
to
the
installation,
but
otherwise
the
deployments
pipelines
there
are
very
similar.
Some
of
the
crds
may
be
there
for
openshift,
like
routes
that
are
inherent
in
them.
Those
are
not
supported,
I
mean
they
are
supported
for
the
deployment,
but
not
exactly
the
same
built-in
way
in
the
documentation.
I
think
the
low
hanging
fruit
is
slightly
different.
H
Topic
is
more
in
terms
of
let's
say:
we
have
releases
that
are
coming
out
with
a
bunch
of
options
that
we
create,
as
there
are
some
defaults
and
additional
changes
that
we
are
doing.
They
are
in
the
release
notes,
but
they
did
not
go
back
into
the
documentation.
Yeah.
Typically,
people
go
and
search.
It's
a
Google
look
for
something
and
in
these
release,
notes
don't
show
up
right.
They
they
do
search
the
documents,
so
they
don't
see
these
options
in
there.
H
A
I
think
maybe
one
thing
that
the
community
could
do
for
anybody
who's
helping
out
with
the
docs
is,
if
you,
if
you
merge
a
feature,
if
you
merge,
if
you
push
a
PR
that
changes
the
way
that
Spinnaker
gets
used,
maybe
just
go
ahead
and
open
that
GitHub
issue.
Right
then
and
say
hey
this
is
this.
Is
you
know
this
is
the
Commit
This
is
the
pr
this
is
going
to
need
docs
just
it.
So
we
even
if
we
don't
get
it,
get
it
documented
when
that
gets
released.
A
H
Going
back
to
ocp
I
guess,
the
issue
is
also
they're
asking:
what
are
the
changes
that
one
has
to
make
to
deploy
to
openshift?
Yes,
I
think
the
documentations
exist,
sporadically
in
optimix
website,
maybe
even
Armory.
Those
are
probably
another
pieces
that
we
can
bring
into
the
main
OSS,
because
that
generally
OSS
us.
A
A
D
Cool
yeah
I
mean
this
is
something
that's
actually
interesting.
It's
something
that
I
also
kind
of
glossed
over
I've
always
used
vinegar
for
this,
but
I
also
know
that's
kind
of
an
it's
a
strong
suggestion
to
use
SQL,
especially
as
you
start
productionalizing.
It
is
what
what's
the
story
there
like.
When
do
you
make
that
cut
like
I?
Guess,
that's
where
it's
not
very
clear
to
me.
G
C
J
Here's
how
you
enable
SQL
for
Spinnaker
and
then
there's
also
more
I,
think
that
we
could
be
doing
in
to
I
guess
share
about
the
migration
story,
because
there's
still
a
path
for
you
to
migrate
like
if
you
started
on
S3
and
redis.
There
are
paths
for
you
to
migrate
over
to
SQL
and
that
path
is
currently
kind
of
like
tribal
knowledge.
If
you
will
no.
A
E
I
When
you
say
extending
Spinnaker
is
that
related
to
plugins
and
plug-in
content,
I
believe
so
yeah
I
I
I
don't
want
to
steal
the
Thunder
from
from
Ben
and
Joe,
but
they
had
a
great
presentation
yesterday
and
they
had.
They
highlighted
some
good
areas
of
improvement.
On
on
that
subject,
in
particular,
there's
a
lot
a
lot
we
can
do
especially
around
the
build
and
release
cycle
for
Spinnaker
and
best
practices
around
there,
Spinnaker
plugins.
That
is.
B
G
D
Yeah
and
I
also
I
mean
on
this
topic
too.
It's
also
worth
noting,
like
you,
don't
have
to
be
a
developer
to
extend
out
of
Spinnaker
like
I've,
been
very
successful.
We've
we've
seen
a
lot
of
success.
Out
of
you
know,
just
being
able
to
do
like
simple
things
like
web
Hooks
and
stuff
being
able
to
almost
have
like
a
path
like.
Are
you
kind
of
like
a
developer,
looking
at
a
functionality
into
core
or
you're?
Looking
to
like
integrate
with
existing
tools?
I
And
just
just
to
add
on
to
that
webhook's
great
there's
also
run
job
run,
job
stages
as
well,
and
that's
also
a
great
way.
It
truly
is
right,
whatever
language
you
want
and
you
can
get
going
and
I
think
that
that's
both
of
those
are
different
use
cases,
but
both
are
great
ways
to
extend
Spinnaker
order
just
to
even
like,
and
it's
not.
D
No
I
mean
definitely
I
think
this
is
something
I
think
we
do
have
docs
on
it,
but
it's
also
very
confusing
and
I
think
it
starts
off
like
x509
and
like
really
like.
The
biggest
thing
is
like
how
do
I
authen
into
an
environment,
because
that's
Enterprises
today,
looking
at
any
solution,
if
it
doesn't
have
SSO
I
can
already
tell
you
it's
not
on
my
list.
I
don't
want
to
manage
thousands
of
users,
and
nor
do
I
want
to
manage
a
certificate
store.
D
So
that's
one
aspect
of
it
and
then
two
there's
like
it's
almost
you
know
in
terms
of
role
base
like
I,
think
there's
definitely
some
things
within
Fiat.
That
could
be
made
less
scary
because,
like
right
now,
at
least
to
me
like
I'm
gonna,
be
honest,
I've
never
used
Fiat
like
and
I
just
know
that,
like
I've
heard
more
problems
with
it
than
before,
but
that's
also
a
very
like
outside
looking
in
and
I'm
sure,
once
you
get
used
to
it
and
you
know
how
to
operate
with
it.
D
D
D
We
should
definitely
like,
if
anything,
it
should
be
like
one
of
the
things
like
security
and
then
like
found
an
issue,
bam
and
I
think
we
do
have
it,
but
I
think
just
that
to
keep
that
top
level.
That's
that's
a
big
one,
because
it
is
an
open
source
project
and
we
all
our
companies
in
this
room
potentially
run
on
it.
So
you
know
their
security
issues
very
our
security
issue.
If
it's
valid
right
and
we
should
at
least
pay
attention
to
it,.
D
E
D
Like
a
point
of
it
where
it
says
like,
if
you're
using
this
in
production,
you
should
do
this
and
then
there's
a
section
where
it
goes,
but
this
is
really
meant
for
large
companies.
Well
I'm
a
small
company,
but
it's
still
a
production
cluster
like
am
I,
not
should
I
not
do
this,
then
I'll
go
to
this
section
and
in
that
case,
you're
going
to
Debian
route
right,
which
is
what's
kind
of
guided
there,
but
I
guess
like
the
flow
and
like
the
tonality
of
like
how
some
things
are
conveyed.
D
D
A
A
A
A
K
Although
I'm
late
I
just
want
to
say
thank
you,
everybody
in
this
room
for
being
here
because
remember
we're
at
open
source
community,
so
just
the
fact
that
you
are
sitting
in
this
room
instead
of
taking
a
nap
or
anything
else,
I
really
really
appreciate
it.
So
keep
up
the
good
work
and
I
want
this.
To
continue
and
the
great
thing
about
conferences,
you
meet
people
in
person,
but
then
over
slack
it
gets
lost.
K
A
D
Es
sorry
I'm
sure
we
all
I
guess
the
other
thing
too
is.
As
we
start,
you
know
talking
about
a
significant
change.
If
error
changing
docs
the
strategy
of
changing
it
would
be
good
to
know
because,
like
some
place,
you
know
like
I
would
use
ansible
where
they
basically
move
docs
and
now
everyone's
like
updating,
bookmarks
and
stuff,
so
like
old
versus
new
I've,
seen
a
lot
of
experiences
where
you
have
like
keep
old,
go
new
right,
or
at
least
by
version
right,
so
you
can
kind
of
see
where
it
should
go.
D
I
do
know
that
that
will
add
more
complexity
and
I
do
know
that
that'll
also
add
a
lot
of
you
know:
maintenance
right,
but
let's
be
real,
like
I
kind
of
know
where
some
things
are
having
run
it,
but
at
the
same
time
I'm
happy
to
move
forward
and
find
the
right
place
to
put
it,
but
I
think
we
need
to
like
are
we
is
this
kind
of
going
in
the
right
direction?
Having
feedback
instead
of
just
kind
of
like
sweeping
changes
like
how
that
kind
of
takes
a
whole
would
be
huge
to
know.