►
From YouTube: Velero Community Meeting - August 6, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi,
everyone
ain't,
no
welcome
to
another
episode
of
the
Valero
community
meetings.
My
name
is
Jonas
Rosslyn
I'll,
be
your
host.
Today,
I'm
gonna
put
up
the
meeting
agenda
here.
For
you
all
to
see,
we've
got
a
bunch
of
stuff
that
we
want
to
cover
today
and
we
also
want
to
cover
the
beta.
That's
coming
up.
So
just
share
my
screen.
A
A
B
So
the
first
thing
here
is:
we
added
CPU
requests
limit
settings
are
in
the
valera
install
command.
So
now
you
can
see
that
you
can
provide
these
flags
for
both
the
Valera
pod
and
the
Resta
quad,
and,
and
that
way
you
can
configure
the
limits
and
requests
that
you
need
a
new
environment
when
you
run
a
filler
install,
and
so
that's
the
first
thing
and
then
the
next
thing
was
the
backup,
the
sauceless.
B
So
currently,
if
I
did
get
back
here,
I
have
two
backups
and
if
I
do
a
described
on
this
nginx
back
up
here,
I
get
some
information
back
about
that
back
up,
but
I.
Don't
quarry
easily
see
what's
actually
in
this.
So
now,
if
I
run
details
here,
I
actually
get
a
list
back
of
order
sources
that
were
backed
up
as
part
of
this
backup.
So
now
it's
this
output.
When
you
do
details
and
in
the
bucket
you
can
see,
this
is
stored
in
a
JSON
file
so
for
a
particular
backup.
B
You
can
see
there's
now
this
resource
list
Jason
file
here,
which
contains
that
metadata
for
all
the
backups
that
were
taken
prior
to
the
current
version
or
the
version
is
to
be
released.
I
suppose
this,
when,
as
far
isn't
available,
you'll,
see
a
message
like
they're
saying
the
back
open
source.
This
was
not
found
and
that's
probably
because
you're
the
backup
was
taken
with
an
auto
version
that
did
it
create
that
metadata
but
yeah.
So
that
features
now
there
and
that's
all
I,
have
any
questions
on
that.
So.
C
B
That's
a
good
question,
and
so
we
don't
set
any
limits
or
default
limits
and
requests
for
the
rustic
pot,
because
we
found
that
that
varies
quite
a
lot,
depending
on
the
size
of
volumes
that
you're
backing
up
or
the
type
of
volumes.
But
for
the
Valera
pods
we
did
some
research
and
we
kind
of
found
it
I.
B
D
E
And
those
the
default
values
that
we
came
up
with
will
be
the
defaults
that
are
used
if
you
run
bolero
install
without
specifying
the
flags,
so
so
will
now
create
it
with
those
default
values.
But
if
you
find
you
need
to
tune
it
for
your
particular
use
case,
you
can
always
just
specify
the
Flags
override
them.
Yeah.
A
E
Today
you
can
do
this
using
the
namespace
mappings
flag
on
the
velaro
restore
create
command,
so
you
can
essentially
take
a
backup
of
namespace
one
and
then
restore
it
using
this
namespace
mappings
flag
into,
for
example,
namespace
two,
and
so
that
would
give
you
a
copy
of
the
namespace
and
all
the
objects
that
are
within
that
namespace.
But
the
problem
with
this
is
that
if
your
namespace
is
using
any
persistent
volumes
and
persistent
volume
claims,
falero
doesn't
currently
know
how
to
essentially
create
a
second
copy
of
the
persistent
volume
that's
being
used.
E
So
when
it,
when
it
does
a
restore
into
the
new
namespace
into
the
map.
Namespace
the
PVC
that
gets
created
there
just
tries
to
claim
the
same
persistent
volume,
that's
being
used
in
the
source
namespace,
and
that
doesn't
work
because
you
can't
have
multiple
PVCs
claiming
the
same
PV.
So
this
has
been
an
issue
for
folks
who
have
been
trying
to
use
the
the
namespace
mappings
flag
to
create
copies
of
namespaces,
so
I
put
up
a
design
doc
for
for
addressing
this
and
basically
enabling
velaro
to
create
copies
of
Peavey's.
E
In
this
particular
scenario,
the
the
original
issue
is
linked
here
in
the
introduction
and
there's
a
bunch
of
commentary
there
from
users
and
some
discussion
about
what
the
user
experience
should
look
like
for
this.
But
what
I've
proposed
in
this
document
is
basically
doesn't
require
any
additional
flags
to
be
specified
by
the
user.
E
Velaro
can
essentially
detect
that,
if
you're
using
the
namespace
mapping
flag-
and
there
are
persistent
volumes
that
are
being
restored-
and
they
already
exist
in
the
cluster
valera
will
detect
that
it
should
create
a
copy
of
that
pv
to
be
used
by
the
second
namespace.
So
had
some
feedback
from
this
already
from
some
of
the
folks
who
have
been
interested
in
getting
this
implemented
and
in
general,
it
seems
like
the
approach,
makes
sense
and
is
going
to
solve
the
issues
for
folks,
but
certainly
if
anyone
else
has
interest
in
this
use
case.
E
E
E
Maybe
you
have
a
cluster
where
you're
running
both
production
and
testing
workloads
and
you
want
to
maybe
take
a
copy
of
the
production
namespace
and
create
a
test
copy
of
it
either
so
that
you
can
test
out
some
new
functionality
or
do
some
debugging
of
an
issue
in
the
production
environment.
That's
that's
definitely
a
common
one.
We've
seen
you
know
you
could.
Oh
there's
also
make
them
up
if
you
have
maybe
a
shared
development
cluster
and
you're
you're,
trying
to
create
kind
of
additional
copies
of
namespaces
for
for
individuals
to
use
for
their
development
process.
F
Had
a
quick
question
about
I'm,
just
I'm
wondering
last
use
case,
which
is
kind
of
more
relevant
to
what
we're
doing
where
you
know
we're
actually
doing
a
migration
to
a
new
closer.
So
in
that
case
we
might
change
a
namespace
and
the
original
may
not
actually
be
there,
but
it
might
I
mean
it
depends
on
why
we're
doing
that.
I'm
assuming
this
is
something
that
would
work
whether
or
not
the
original
TVs
were
there
yeah.
E
D
A
Awesome
I
think
that
ties
well
into
the
next
topic
here,
the
beta
that
is
coming
out
very,
very
soon
Steve.
You
want
to
talk
a
little
about
the
beta
yeah.
E
So
we've
been
working
on
burning
down
the
scope
for
version
1.1
and
we're
we're
just
wrapping
up
the
last
handful
of
issues,
so
we're
planning
to
to
ship
a
beta
release
for
1.1,
probably
within
the
next
day
or
two
days,
but
I
would
say
definitely
by
the
end
of
this
week,
so
we'll
definitely
send
out
notifications
on
the
mailing
list
and
the
slack
Channel
etc.
When
that
goes
out,
so
we
definitely
love
it.
E
If
you
know,
if
anyone
has
time
and
can
do
a
little
bit
of
testing
on
that,
that'd
be
great
and
you
can
check
out
some
of
the
new
features
that
we've
shipped
also
to
release
notes
that
covers.
All
of
that
will
also
be
be
testing
it
ourselves
for
for
a
short
period
of
time
and
then
once
we
feel
confident
in
the
quality
of
that
will
will
shift
the
official
1.1
release.
E
A
A
One
thing
that
we
talked
about
at
a
previous
community
meeting
here
last
month
was
the
Valero
users
survey
and
I
just
want
to
bring
this
up
again,
so
people
can
see
it.
This
is
a
this
is
a
really
good
way
for
everyone
on
the
call
of
the
entire
Valero
community
to
give
the
libertines
feedback
on
what's
important
and
how
Valera
is
being
used
and
how
the
community
sees
kubernetes,
TVs
and
backups
and
everything
the
user
survey
is
online
here
right
now
we
have
a
bunch
of
really
good
answers.
A
We
have
a
free
form
of
this
well,
at
the
end
where
you
can
tell
us
what
you
would
like
to
see
in
future
revisions
and
future
versions
here
of
Valero.
This
really
helps
when
we
do
planning
for
future
releases
of
Valero
and
future
enhancements.
So
please,
head
over
and
take
the
Valero
survey.
If
you
head
over
to
the
Lord
I,
owe
you
have
a
link
to
the
survey
up
here
to
the
right
as
well,
so
you
can
easily
find
it
there.
A
C
A
E
Carthew
D
submitted
a
pull
request
to
add
support
for
Valero
to
log
in
JSON
format,
rather
than
the
kind
of
default
text
format
that
we
get.
So
we
have
a
new
CLI
flag
to
the
Valero
server
command
that
you
can
use
to
specify
this.
This
was
something
that
I
think
he
had
developed
for
for
his
use
of
Valero
and
wanted
to
contribute
it
upstream.
So
we're
super
happy
to
have
that
contribution
and
hopefully
benefit
some
other
users
as
well.
So
thanks
a
lot.