►
Description
In this new "Learn from our maintainer" series, Carlisia shows how quick the developer build/run/test workflow can be when you run the Velero server locally. She does a detailed (read long!) show and tell of how to setup this workflow. She starts from the beginning, from installing the Velero CLI and installing Velero in a local (Kind) cluster, and explains all the commands and flags as she goes along. She also explains and shows (almost) everything that happens in a Kubernetes cluster as the result of changes to code and to configurations as she switches to bundling code changes in an image and pushing it to a cluster. Octant 0.12.0 is highly featured in this demo!
A
My
cat
just
decided
to
participate,
and
this
is
absolutely
the
quickest
way
to
run
the
run
as
a
lot
of
people
know
who
work
with
communities
and
in
darker
having
to
build
an
image.
It
takes
a
little
bit
of
time
and
in
this
way
we
take
that
out
of
the
equation
and
we
just
run
a
binary.
One
restriction,
though,
is
that
if
you
are
manipulating
changing
codes
to
manipulate
any
persistent
volume
related
operation,
then
this
doesn't
work
is
running
locally.
You
don't
have
access
to
that.
A
You
really
have
to
build
an
image
and
test
your
code
in
an
actual
cluster.
That's
not
like
a
local
kind
cluster
or
mini
cube.
So
with
that
said,
my
setup
is
I.
Have
a
kind
cluster
I
already
have
it
running?
I'm
not
gonna,
going
to
show
you
how
to
install
that
and
I
also
have
a
medial
instance.
I
stand
alone
me
no
running
in
in
a
darker
in
my
local
docker
and
I'm,
also
not
going
to
show
you
how
to
do
that,
because
there
is
a
QuickStart
guide
on
the
menial
websites.
A
A
A
If
I
see
what
there
are
four
parts,
if
you
are
a
total
newcomer,
you
should
know
that
this
is
all
there
is
once
you
put
up
a
cluster,
you
should
see
that
cubes
cubes
system
namespace
and
pretty
much
nothing
else.
Once
we
start
a
little
will
have
its
running
its
own
namespace,
which
will
be
named
the
lair.
Oh
so
going
back
here.
A
I
have
a
little
to-do
list
for
the
things
that
I'm
going
to
do
so.
First
things.
First,
so
we'll
install
the
level
on
my
kind
cluster
but
I'm
the
first
for
me
to
run.
Luckily
I
have
to
do
this
step.
I
have
to
install
using
the
Valerius
document
and
I'm
going
to
tell
you
what
each
one
of
these
things
are.
A
So
the
provider
is
AWS
and
you
might
find
it
odd
because
we
are
not
using
AWS
at
all,
but
that
is
because
the
the
interface
for
AWS
and
for
me
neo,
are
is
they
are
the
same.
The
interface
is
the
same
for
both,
so
the
plugin
for
AWS
will
work
with
me,
neo
and
by
the
way,
the
what
we
do
with
the
menu
is.
We
use
it
as
a
storage
location
to
store
the
backup
files.
Like
we
package
all
of
the
content
of
the
resources
from
the
cluster.
A
We
package
it
up
in
the
backup
form
that
the
little
understands
and
we
push
it
to
the
a
s3
bucket
in
in
my
case
here
hope
you
mean
you
buckets
I'm,
saying
I'm
not
gonna,
be
using
wallop
snapshots
because
I'm
not
so
that
just
avoids
the
filler
up
from
creating
things
that
I'm
not
gonna
need
the
secret
file.
So
this
is
pointing
to
a
natural
file
that
has
the
credentials
for
the
menu
instance,
which
is
my
case,
the
the
one
that
comes
with
a
mini
Oh,
a
mini
one.
Two
three
is
of
no
significance.
A
You
are
allowed
to
know
that.
There's
no
big
deal
I
when
I
did
setup
mineus
following
that,
the
instructions
on
the
meaning
of
documentation,
I
names,
my
buckets
Acme
developments-
and
this
down
here
are
the
is
the
other
configuration
needed
for
filler
to
setup,
an
object
that
we
call
back,
backup,
storage,
location
or
backup
store
location.
A
Sometimes
we
say
that
and
they
will
the
buckets
as
part
of
that
as
well
and
because
I'm
not
giving
it
a
name,
is
going
to
be
created
with
the
name
default
and
it's
going
to
be
marked
as
the
default
buckets.
So
the
little
needs
one
known:
abacus,
I'm,
sorry,
backup,
storage
location,
so
if
it
needs
one
backup,
storage,
location,
that
is
the
default
one.
A
A
For
example,
if
my
me,
my
Mina
could
be
running
inside
the
cluster
itself
and
I
could
create
a
service
for,
and
what
I
would
put
here
would
be
the
the
address
for
the
cert,
the
name
right,
the
DNS
for
service,
but
because
I
have
mini
running
outside
of
the
cluster
in
all
my
local
machine.
One
thing
that
you
could
that
you
could
think
that
should
go
here
is
localhost
with
9000
port,
but
that
would
not
work
because
then
Valera
would
look
for
low
low,
the
the
cluster
localhost
and
that's
not
what
we
want.
A
A
Here
we
go
and
you
go
to
network
in
my
case,
I
am
connected
connected
through
Wi-Fi
and
I
will
find
it
right
here.
This
is
the
address
and
by
the
way,
if
you
get
up
and
move
to
a
coffee
shop
where
you're
going
to
connect
through
their
Wi-Fi,
this
IP
address
will
change
it's
sort
of
obvious,
but
not
so
just
heads
up
and
then
because
if
you
are
going
to
run
this,
then
you
have
to
change
that
URL.
A
Alright,
so
what
happens?
Is
I
was
cleaning
up
my
hard
drive
and
I
deleted
the
little
binary,
but
this
gives
me
a
chance
to
tell
you
how
to
install
the
Valero
because
we
need
to
we
need
to
have
installed
before
we
can
do
anything
with
the
lower.
So
if
you
have
a
Mac,
this
is
the
easiest
quickest
way.
A
So
you
can
see
there
on
the
screen.
Is
the
one
point
3
point
2
version?
That
is
the
latest
release
we
have
so
now
just
to
double
check.
We
have
a
there.
We
go
so
this
error
here
is
just
saying
he
was
looking
for
a
server
version,
but
it's
not
installed
on
it's,
not
the
sort.
It's
the
server
version
of
the
lower
is
not
running
anyway,
so
you
wouldn't
find
it.
So,
let's
run
the
install
command
again.
A
A
One
of
the
flags
here
is
image
and
you
can
specify,
for
example,
prior
version
of
a
little
or
your
own
image
that
you
have
somewhere
your
envelope
image
that
you
have
pushed
to
it.
It's
some
registry,
so
you
can.
You
can
do
that,
but
if
you
don't
specify
you
will
get
automatically
the
latest
wish
in
no
case
again,
it's
one
point
three
point
two
I
think
all
right,
so
we
installed
that
on
a
server.
Let's
make
sure
it's
running.
This
is
how
I
I
do
it.
A
So
that's
the
Valero
part
that
was
a
spun
up
as
as
as
a
result
of
to
put
a
little
deployments
back-
and
he
says
it's
running
I'm,
just
going
to
trust
that
it's
running,
usually
I
will
go
one
step
further
and
create
a
backup
make
sure
that
you
look
at
the
log
and
make
sure
that
there
are
no
errors.
But
in
fact,
let's
look
at
the
log
oops.
Sorry,
this
way,
I'm
going
to
look
at
the
log
using
octants,
which
is
another
open-source
tool,
and
this
is
a
very
fresh
release
of
octant.
A
Work
loads
here,
so
what
I
want
to
do
is
look
at
the
PI
in
the
Valero
PI
in
here
it
conveniently
I
can
look
at
the
log
for
that
part.
I!
Don't
like
this,
that
it
displays
timestamp
by
default,
actually
just
like
a
feature
request
for
them
to
make
this
cloth
by
default,
and
so
here's
showing
all
containers-
and
just
so
you
know
the
little
the
little
deployments,
but
this
is
specified.
Obviously
the
valar
image
for
it
to
run,
but
also
at
least
one
plugin,
because
without
the
plugin
we
can't
do
anything.
A
The
plug-in
has
the
logic
to
connect
to
a
an
s3
storage
and
store
your
backup,
but
the
lot
of
pipes,
the
log
from
the
plug-in
directly
to
a
Valera
to
the
vlog.
So
you
will
never
see
anything
here.
So
in
essence,
if
you
select
our
containers
or
if
your
selections
falero,
you
will
see
the
same
thing.
So
the
log
here
looks
pretty
good.
I,
don't
see
error
and,
let's
see
log
level
info.
Okay,
that's
the
default!
A
A
A
Let
me
just
see
by
your
checklist
here:
I
showed
that
we
did
and
we're
just
about
to
put
up
the
local
server
all
right,
so
we
don't
have
the
little
running
inside
the
cluster
anymore.
Now,
when
the
learner
installs,
it's
sort
of
I,
think
of
it
as
like.
Two
two
aspects
of
a
little
one
is
the
Valera
server
that
runs
all
the
time
in
the
other
part,
is
the
feller
X.
The
way
the
father
extends
governor
is
by
using
custom
custom
resource
definitions.
A
So
if
I
do
get
CR
DS,
we
have
all
these
here,
DS
that
were
installed
when
I
went
in
her
stall
and
when
I
brought
the
replica
down
to
zero.
Of
course,
the
sergey's
stayed
there
as
expected.
So
when
I
run
the
little
locally
I
we
buried,
my
local
binary
is
going
to
be
pinging
the
Valero
API
and
for
the
class
that
there
you
know
the.
So,
if
you
see
on
the
right
side
of
my
screen,
it's
my
cluster
is
in
contact.
A
So
I,
don't
need
to
specify
the
cluster
is
whatever
class
is
in
context
is
what's
going
to
use,
so
it's
going
to
ping
that
cluster.
Nothing
I'm.
Sorry,
it's
going
to
go
is
going
to
run
in
work
with
the
API
for
the
focal
binaries
in
that
cluster.
Those
here
days,
I
in
the
cluster
in
desktop
other,
is
going
to
create
backups
in
keep
up
all
these
resources,
but
the
operation
on
the
resources
of
the
code.
The
logic
is
going
to
be
run
running
locally.
A
So
basically
we
keeping
the
states
of
the
CR
DS
in
a
cluster
and
then
the
other
piece
is.
Whenever
we
create
a
backup
or
create
a
restore,
then
we
interact
with
the
menial
instance,
which
is
not
even
in
the
cluster
right.
So
from
the
perspective
of
interacting
with
the
s3
storage,
it
really
doesn't
mean
doesn't
matter
if
we
are
running
locally
or
we
run
a
server
inside
the
cluster.
A
A
So
this
so
does
the
server,
even
though
it's
running
locally
knows
how
to
access
that
mean
your
instance
and
I'm
going
to
point
this
to
my
credentials
file
while
I'm
at
it
I'm
going
to
change
the
lock
level
from
info,
which
is
defaults
to
the
bug,
because
I
want
to
see
more
things.
Usually,
when
I'm
developing
I
skipped
an
important
piece
of
information.
This
little
V
here
is
an
alias
that
I
have
that
points
to
that
binary
that
I
just
showed
and
if
you
are
curious,
because
so
because
I
would
be
curious.
A
This
is
my
IDE
and
I
run
a
fish
shell.
But
of
course,
whatever
show
you
use,
you
have
you'll
be
able
to
do
that.
Also,
my
config
files
are
on
on
my
repo
called
dot
files.
In
my
repo
is
my
github
here's.
The
name
is
my
first
name
kaliesha
and
I
have
a
repository
called
that
files
that
has
all
my
configuration.
So
this
little
V,
as
you
see
here,
just
points
to
this.
So
if
I
didn't
have
the
V
I
could
just
put
this
big
string
now.
A
A
One
point
two
point:
three
gosh
I
forgot,
but
one
point
to
something
or
one
point:
three:
something:
yes
1.3.1.
It's
one
point
three
something,
and
so,
if
I
see
Valero
I
run
that
version
if
I
run
V
I
run
whatever
version
with
whatever
local
changes
I
have
on
my
branch,
I
hope
that
makes
sense,
so
lock
loved
one
changing
and
lock
loves
optional.
A
It
needs
to
know
where
in
the
world
is
the
plug-in
that
it
needs
to
run
because
it
needs
at
least
one
you
can
have
multiple,
but
so
you
need
one
and
I
have
clones
the
plug-in
repo,
because
I
also
work
for
that.
So
it's
running
it's
it's
placed
part
in
parallel
with
my
Valero
project,
so
I
just
do
dot
dot,
slash
the
name
of
the
repo
or
name
of
the
folder,
and
the
important
thing
here
is
to
make
sure
you
have
a
slash
at
the
ends
but
other
than
having
the
slash
at
the
ends.
A
A
Targets
in
that
built
binary
for
the
plug-in
and
if
you
notice
he
puts
is
different
from
the
Valero,
maybe
will
change
should
change
this
to
make
it
consistent,
so
the
plug-in
outputs,
the
binary
just
like
right
here
at
the
output
folder,
where,
as
the
Valero
outputs
to
its
outputs
and
whatever
a
path
that
represents
what
machine
you
running
on
hope
that
made
sense,
but
don't
worry
about
it.
This
is
the
whole
thing
we're
going
to
copy
this.
A
A
Excuse
me
I
see
that
the
bug
this
is
what
I
was
looking
for.
All
of
these,
the
tbu
is
short
for
the
bug,
so
I
stop
I'm,
definitely
getting
to
the
bug
logging
and,
if
I
change
anything
on
my
codes
close
this,
and
this
is
a
codes
that
I
have
that's
working
progress,
I'm
working
on
my
on
a
branch
that
is
not
a
master
branch.
This
code
has
now
is
not
even
on
on
PR
status,
but
I
see
I
have
here
debacle
easier,
so
this
should
be
appearing
in
the
log
because
I
that's.
A
Yeah
there
were
database,
so
it
builds
my
code
Isis.
This
is
definitely
not
production
code.
You
imagine
so
that
code
that
we
were
looking
at
is
a
controller,
so
it
just
runs
continuously
and
everyone's
know.
I
looked
through
through
that
function,
it's
actually
a
new
controller
that
I'm
building
well.
Unless
for
the
for
the
it's
a
bit
to
me
to
be
sorry
another
day,
I'm
so
tired
to
be
very
complete,
that's
it
there!
A
A
So
when
I
clear
this
I'm
going
to
run
I
just
air
up
one,
what
once
or
twice
and
now
I
should
see
that
change.
I
made
sorry
picked
up
the
the
previous
one,
oh,
except
that
it
didn't.
You
know
why
I
do
this
very
frequently,
because
I
didn't
want
make
local
yeah
so
I
changed
the
code.
I
stopped
the
server
in
rain
server
again,
but
I
never
they'll
rebuild
the
binary.
A
And,
and
and-
and
so
here
is
Callie's
a
demo,
it's
going
to
pop
in
again
because
keeps
keeps
looking
looping
cool,
so
you
know
you
keep
developing
and
you
keep
changing
your
codes.
You
just
do
this
over
and
over
again,
but
the
good
news
is
that
it's
super
quick.
Now
what
if
you
so
the
way
I
develop,
is
I
just
a
bit
triple
sure,
especially
if
I'm
making
a
big
change.
I
want
to
run
the
stuff
on
in
the
cluster
and
see
what
it
looks
like
there.
A
Let
me
go
to
my
oh,
yes,
I'm
just
going
to
copy
this,
because
I'm
lazy,
let's
clear
this
so
the
first
time
so
I
accused
that
local
further
server
change
the
code
once
more
and
now
I'm
going
to
say
what
what
I'm
going
to
do
is
up
the
replica
for
the
Valero
deployment
by
one
I
only
need
one
so
from
0
to
1,
because
only
0,
it's
not
running
first
thing.
I
do
I
want
to
see
the
pods
you
boot
up
and
happening
so
quickly.
A
Alright,
so
it's
running,
however,
the
the
point
nothing
in
this
back
of
the
deployment
changed.
The
only
thing
that
changed
is
was
that
it
was.
It
was
running,
it
was
not
running
and
I
was
running.
I
didn't
change
anything
even
though
I
changed
my
code
locally.
It
hasn't
made
its
way
there.
Yet
so
I'm
going
to
show
you
so
one
way
that
I
would
I
could
have
put
I
could
could
have
put
that
code.
There
I
was
doing
stop.
A
A
There
is
a
one
line
command
that
continue
to
do
that,
which
is
this
line
here,
but
before
I
put
it
there,
I
have
to
build
it
because
remember
I
changed
the
code,
but
I
didn't
do
anything
with
the
codes
and
for
me
to
to
be
successful
with
this
updates
in
the
cluster,
I
have
to
build
the
image
and
push
the
image
that
I
build
to
a
registry,
and
then
it
will
be
available
for
me
to
tell
Valora
hey
this.
Is
the
image
just
pull
this
image
from
this
location?
A
So
this
is
how
we're
going
to
do.
Let
me
just
explain
what
are
we
are
looking
at,
so
the
the
actual
command,
the
actual
like
I'm
gonna,
say
commands
there
it's
gonna
be
running
is
make
so
it's
make
container
for
a
manifest.
These
are
three
different
targets
in
our
make
file.
Now
I
am
going
to
be
sending
this
information
to
this
make
command,
and
this
information
is
going
to
be
processed
in
the
make
file.
So
when
the
image
is
done,
it
will
have
the
information
that
I
want.
So
one
information
is
the
registry.
A
A
So
this
is
the
tag,
the
manifest
platforms.
I,
you
don't
need.
We
don't
need
a
per
se,
but
if
you
do
specify
it
will
just
run
for
you
we'll
just
build
this
one
as
opposed
to
not
passing
I,
think
builds
for
it
builds
more
than
one
and
we
don't
need
more
than
one
ok,
so
I
can
copy.
This
now
go
to
my
terminal.
A
A
A
A
A
The
letter,
whatever
platform
you're
running
what
we
did
specify
this
right
remember
the
manifest
another
demo
is
the
tag
that
I
gave
to
it,
and
it's
done
so
one
thing
that
I
like
doing
it's
really
double
checking.
If
it's
there,
let
me
make.
Let
me
make
this
a
little
smaller,
okay,
so
the
image
it's
there.
A
One
thing
to
note
is
well
actually
alright.
One
thing
couple
things
to
note:
one
thing
to
note
is
what
we
did
just
now.
Is
we
modified
the
valorous
back?
The
verse
back
before
was
singing
the
image
for
Valero.
You
sow
in
the
custom
right,
you
can
fetch
it
from
the
Valero
repository
in
this
image.
Called
Valero
in
the
tag
is
one
point
three
point
something
that
I
forgot
now
we
said:
no,
you
forget
about
that.
Now.
A
I
wanted
to
pull
this
new
image,
so
the
part
is
no
longer
valid
the
part
for
the
deployment,
so
it
will
build.
It
terminates
that
part
that
original
part
and
builds
a
new
one
and
that's
what
just
what
we
were
looking
at.
So
now
we
have
a
new
part
and
just
because
I
like
to
really
really
show
we're
going
to
go
into
the
valorous
back
the
Valero
deployments
when
I
look
at
the
e
mo
and
I
expect
to
see.
A
A
So
what
I
so
the
image
there,
but
does
that
image
contain
my
codes
for
me
to
do
that
I
mean
I
can
go
in
the
command
line,
but
I
really
like
octant
I
like
to
look
through
here
so
I'm,
going
to
turn
off
the
timestamp
and
what
was
the,
let
me
be
I
want
to
change
this
I
changed
it
a
couple
times,
so
I
just
want
to
make
sure
I
get
the
right
shrink
so
right
now
this
filter
is
case-sensitive
and
I
didn't
know
that
I
spent
some
time
figuring.
That
out.
A
A
I
know
why
so
two
possibilities,
one
I
built
an
image,
but
the
image
didn't
pick
up
my
code
change,
maybe
I
messed
up
somewhere,
because
really
this
is
why
I'm
looking
at
a
log
or
two,
which
is
the
spoiler
I,
know
ahead
of
time
that
this
would
not
work
even
if
I
did.
Everything
right
is
that
when
I'm
running
fella
on
the
on
a
cluster
the
default
is
is
info
and
because,
when
they
installed
earlier,
they
stuff
the
stuff
like,
and
let
me
actually
double
check
that
that
is
correct.
A
A
Is
this
it
I
never
actually
said
it
from
from
the
from
here
is
a
global
flag?
This,
maybe
will
do
it
I'm,
not
sure
I.
Don't
think
so,
I'm
not
clear
on
that
one
at
any
rate
that
that
message
will
never
show
up
because
I
was.
It
was
long
as
a
debug
message,
so
it
will
just
not.
Even
if
the
image
picked
up
this
code
change,
it
will
not
show
up
so
I'm
going
to
show
you
how
to
change
how
to
make
the
log
show
that
at
a
debug
level
and
and
in
ends.
A
A
So
I'm
going
to-
let
me
just
copy
this
case
again
by
type
when
you
can
copy
and
paste
so
actually
just
to
I
mean,
should
be
obvious,
that
the
reason
why
we're
not
saying
that
it
has
nothing
to
do
with
octant,
it's
just
the
log.
So
it's
the
same
log
that
we
would
see
here
is
the
same
log
that
we
were
looking
I'd
misspelled
ads
all
right
so
level
info.
This
is
the
same
thing.
A
We
were
looking
at
it's
a
lot,
so
I
don't
expect
just
trust
me
I,
don't
really
like
when
people
say
that
I
just
trust
me,
okay
did
I
copy
this.
Let's
make
sure,
and
so
this
is
going
to
give
me
the
for
the
Valero
deployments,
I'm
going
to
look
for
where
that
server
command
is,
and
so
there's
nothing
there
as
far
as
Lagos,
because
the
coal
just
understands
well,
if
nothing
has
been
specified,
is
because
we
are
doing
the
info
level
so
I'm
going
to
copy
this.
A
Somebody
told
me
that
that
might
be
to
cultural
irrelevant
for
some
cultures,
I,
don't
know
how
else
I
would
say
that
just
for
fun,
I
want
to
look
at
the
Y
mo
for
Valera
from
wedding
octants,
which
should
look
exactly
the
same.
It
should
contain
the
change
I
just
made,
and
here
it
is
alright.
So
now
I'm
going
to
go
to
pods.
This
is
going
to
be
a
new
part,
because
the
the
deployment
was
changed.
Gonna
go
to
logs
and,
let's
see
level
info.
A
A
A
And
there
it
is
and
if
I
say
only
show
the
lines
that
correspond
to
the
filter
I
will
see.
That
means
that
controller
has
looked
through
that
code,
one
two
three
four
times,
and
if
we
wait
a
while,
don't
be
another
one
popping
in
here
I
want
to
see
a
new
one.
There
we
go
all
right,
so
that
is
how
you
push
a
local
change
to
a
little
cluster.
A
A
Think
I
could
bring
the
circle
back
to
running
it
locally,
but
I
don't
think
it's
necessary.
It's
almost
an
hour
anyway.
Just
one
last
thing
is
all
the
information
that
I
used
to
do
everything
that
I
did
is
contained
mostly
here
in
this
area
of
the
power
of
the
commentation
so
built
from
source
really
get
into
details
about
the
makefile
and
how
to
make
different
for
different
targets
and
run
locally.
A
Also,
has
the
information
that
I
used
the
reason
for
this
video
was
just
to
have
like
an
end-to-end
demonstration
and
also
for
the
menial
configuration
there.
Is
this
evaluation
install,
it
doesn't
say
menial
so
might
be
hard
to
find,
but
the
QuickStart
evaluation
shows
how
to
use
menial,
but
in
this
case
is
saying,
deploy
menial
using
this
spec
that
we
have
in
our
example
folders
folder,
which
is
going
to
make
mini,
run
it's
going
to
create
the
namespace,
the
menial
deployments
and
the
service
may
be
another
thing.
A
I
forget
it's
going
to
create
a
service
to
connect
the
meaning
to
well
just
to
give
you
this
DNS
name.
They
you
didn't
use
as
a
URL,
but
I
do
any
rate.
You
can
browse
and
learn
more
and
if
any
question,
if
you
have
any
questions
pop
on
the
federal
channel
on
the
kubernetes
lag
or
or
open
the
ticket,
we
welcome
back
to
you
with
answers
to
your
questions.
It
was
great
to
do
this.
It
was
a
lot
of
fun
again.