►
From YouTube: Auto DevOps Setup and Usage - Product Walk Through
A
All
right,
hello,
my
name
is
Kenny
Justin
I'm,
the
director
of
product
for
ops,
I'm,
going
to
be
recording
a
product
walkthrough.
Today,
it's
the
first
in
a
series
of
walkthroughs
and
by
myself,
so
I'll
do
a
little
bit
of
talking
to
myself
as
I
go
through
the
process.
Let
me
start
by
sharing
my
screen.
A
A
B
A
Now
I'm
familiar
that
I
need
to
attach
Quran.
It
is
kubernetes
cluster.
In
order
for
Auto
DevOps
to
run
our
DevOps
Oh
automatically
build
test
and
deploy
our
application
based
on
predefined
CSD
communication.
Very
configuration
learn
more
about
our
DevOps,
maybe
I
just
don't
need
to
learn
more
just
enable
it
defaults
to
our
DevOps
pipeline
yeah.
That
seems
very
small.
Just
don't
need
to
do
incremental.
A
A
A
B
A
A
A
B
A
A
A
C
C
B
A
B
A
A
A
A
A
A
A
Looks
like
prometheus
is
installed
still
waiting
for
this
wildcard.
For
this
end
point
that
I
can
use
for
my
DNS
entry
looks
like.
Was
it
the
next
thing,
so
the
QuickStart
said:
grab
that
IP
address
I'm
gonna
use
that
when
I
enabled
on
a
device
which
I
actually
already
did
but
I
guess,
I'm
gonna
go
back
and
it's
that
configuration
so
that
it
points
to
the
right
domain.
A
A
A
So,
okay,
save
those
changes.
That's
been
changed.
No
Google
I
installed
from
atheists
now
at
least
I
get.
These
charts
for
cluster
helps
that's
kind
of
cool.
Let's
go
back
so
in
the
QuickStart
guide.
It
was
telling
me
after
I've
done
that
I
should
get
a
new
pipeline.
So
let's
check
out
and
see
if
my
pipeline
is
running
liked
pipelines
so
that
pipeline
the
initial
pipeline
completed.
Let's
look
at
other
pipelines
now
that
is
the
only
one.
A
A
A
A
A
A
We
should
see
it
deploy
to
production,
just
see
what
happens
if
I
look
at
the
environments
that
I
have
today
high
production,
but
no
deployments
yet
that
makes
sense
see
if
I
look
at
metrics
I
have
an
environment
for
production.
No
data
found
that
makes
sense.
There's
no
environment,
we're
not
collecting
any
data
for
this
production
environment
from
Prometheus
cool.
A
A
A
Your
hair
tracking,
no,
this
is
gonna.
Take
me.
Let
me
just
check
on
these
pipelines
still
running
taking
some
time.
Let's
go
explore
over
here.
Cable
error,
tracking
operation
settings
I
have
something
about
incidents.
Well,
that's
cool
I
can
just
jump
to
me
to
settings
operations.
I
can
create
an
issue
for
each
alert,
triggered.
There's
no
template,
but
just
I
could
add
some
templates
here.
Tracking
I
could
linked
to
a
century
server
and
tracing.
We
said
I
could
also
link
to
a
Jaeger
server
external.
A
C
A
Just
connect
add
a
note
for
myself,
while
we're
waiting
that
we
should
consider
adding
home
ingress
and
prometheus
by
default
when
attaching
clusters,
especially
since
I,
saw
that
we
have
uninstall
so
I
presume
we
could
make
that
kind
of
an
opt
out.
We
automatically
install
them
and
then
can
remove
them.
B
A
A
A
A
A
A
A
A
A
A
B
A
A
Any
data
or
there's
just
not
any
data
at
the
moment,
can
change
the
time
period
in
the
environment.
It's
cool.
Let's
go
back
to
this
look
at
the
terminal,
let's
just
make
sure
there's
something
there
all
right
there
we
go.
This
is
my
application.
It's
deployed
to
this
address
has
the
content
that
I
was
expecting
from
this
kind
of
hello
world
app.
A
A
You
I
got
no
errors
but
I'm,
starting
to
see
some
data
weight
and
C's
been
low.
We
should
fill
up
some
way
to
test
this
by
putting
some
more
load
than
just
me.
Refreshing
on
my
browser
might
be
good
for
the
next
speedrun'
okay,
so
alright
is
also
gonna.
Look
at
this
Web
terminal,
so
this
is
a
terminal
for
that
and
oh
man,
it's
a
dockerfile.
B
A
B
B
A
B
A
So
I
have
a
commit
and
a
merge
request.
Pipelines
kicked
off
that
pipeline
is
gonna,
run,
have
these
different
components:
I'm
hoping
yeah,
there's
a
review
up
in
here.
That
includes
a
desks
key,
an
on
a
review
up
and
then
we'll
see.
If
all
that
runs
and
then
when
we
successfully
merge
after
the
pipeline
runs
that
updates
the
production
map.
B
C
B
A
A
A
B
A
B
B
B
A
A
A
A
A
C
C
B
B
A
C
C
B
A
Said
it
sent
me
the
artifact:
that's
that
perform
is
such
a
son
file.
I
could
look
at
it.
What
I
would
have
expected?
That's
show
up
somewhere.
Maybe
it
shows
up
in
the
merge
request,
but
since
this
pipeline
was
run
without
one
I
didn't
see,
it
I'll
see
if
it
shows
up
in
these
later
ones.
Okay,
this
hi
everyone
is
deploying
to
review
app
just
like
before
there's
no
deployment.
Now
it's
waiting
to
see
the
rollout
finish.
A
A
B
A
A
A
C
A
B
B
C
A
A
See
them
March
without
completely
or
on
different
files.
So
this
one
again
I'm
going
to
hit
merge
from
pipeline
succeeds,
but
I
want
to
make
sure
happens,
is
that
after
these
commits
pipelines,
run
that
there's
a
post
March
pipeline
that
deploys
to
production
and
that
we
see
both
of
those
changes
in
our
production.
A
A
A
A
B
A
A
A
A
C
B
A
B
A
B
A
A
A
B
B
B
B
A
A
A
A
A
C
B
C
B
A
A
A
A
A
Wonder
why
that
showed
up
when
it
did
okay,
but
in
summary,
Auto
DevOps
I,
think
worked
as
described
a
couple
of
kinks
in
just
the
process,
but
otherwise
easy
for
me
to
use
a
template.
I
have
that
attached
a
kubernetes
cluster
and
have
that
deploy
and
not
only
just
deploy
the
application
but
run
a
series
of
tests
for
me,
as
well
as
when
I'm
doing
merge,
request,
get
me
review
apps
to
review
the
changes
in
a
pseudo
production
environment,
so
cool
I
will
use
these
notes
and
create
a
set
of
follow-up
action
items
I.