►
From YouTube: Velero Community Meeting - May 7, 2019
Description
The Velero team talks about the v1.0.0-beta.1 release, rustic integration moving to "beta", stabilizing the Helm chart and more.
A
All
right,
hello,
everyone
welcome
to
the
valera
community
meeting.
It's
May
7th
2019
happy
to
be
here
and
talk
through
a
few
things
that
we
have
on
the
agenda.
Just
a
reminder.
We
are
recording
this
meeting
and
it
will
be
posted
publicly
on
YouTube
after
the
conclusion
of
the
meeting.
So
just
keep
that
in
mind
as
you're
speaking
or
asking
any
questions.
I
will
go
ahead
and
share
the
agenda.
A
All
right,
so
we
have
a
relatively
short
agenda
today.
So
guessing
we
won't
use
the
whole
hour.
Folks
can
get
a
few
minutes
back
for
their
day.
So
the
first
thing
we
wanted
to
talk
about
is
is
what
we've
been
working
on
and
the
the
big-ticket
item
that
we
have
the
covers
that
are
first
beta,
has
been
released,
so
I'm
gonna
hand
it
off
to
Nolan
to
talk
a
little
bit
about
the
beta,
for
if
you
want
yeah.
B
So
this
first
beta
is
actually
fairly
small
over
the
Alpha
that
alpha
2
that
we
had
previously.
We
added
some
new
phases
for
backups
and
restores
so
that,
hopefully,
that's
a
little
bit
clearer
for
users.
We
sped
up
some
rustic
operations.
We
found
some
issues
with
the
install
command
as
people
were
using
them,
so
we
fixed
those
up,
including
disallowing
certain
characters
and
bucket
names
and
making
sure
we
get
the
the
right
images
downloaded.
B
B
Gcp
wicked
we're
now
allowing
disks
to
be
restored
from
a
separate
project
as
long
as
the
IM
account
has
access
to
it
a
sure
we
have
more
accurate
disk
information
for
doing
restores
and
then,
finally,
as
part
of
the
install
command,
we've
removed
the
configs
directory
inside
the
release.
Tarball,
and
that's
just
examples
so
you'll.
B
A
And
so
we
definitely
want
to
continue
to
invest
in
that
and
spend
some
time
just
ironing
out
any
of
the
the
issues
that
remain,
but
just
given
the
the
short
amount
of
time
that
that
integration
has
existed
relative
to
the
rest
of
the
codebase.
We
weren't
quite
comfortable
well,
one
onion
GBA
as
a
one
dot.
Oh
it
is
you
know
for
folks
who
have
used
it.
A
All
right
great,
so
talk
a
little
bit
about
what's
coming
up
and
obviously
you
know
we've
been
talking
about
this
for
the
past
several
meetings,
so
the
main
thing
we're
pushing
towards
is
that
v1g
a
release
we're
targeting
to
to
push
the
release
out
on
May
21st?
So
that's
just
I
believe
exactly
two
weeks
away
from
today.
So
we're
pretty
excited
about
that.
A
Oh
we're
not
done
with
the
project
where
we're
gonna
start
looking
at
1.1,
1.2
and
and
obviously
starting
to
think
towards
a
2.0,
and
so
we
will
start
picking
outpost,
1,
dot,
o
planning.
Shortly
after
that.
That
view
1
release
We
certainly
have
a
bunch
of
items
that
are
in
the
backlog,
already
future
requests
that
have
been
submitted
by
users
and
ideas
that
we've
had
within
the
team,
but
just
to
mention
a
couple
of
the
things.
A
You
know
started
talking
about
this
and
looking
at
the
state
of
the
upstream
work
and
starting
to
do
a
little
bit
of
PSU
work,
but
we
certainly
have
a
lot
more
investigation
and
planning
and
and
designed
to
do
here.
So
this
is
a
big
item
that
will
be
picking
up
after
one
dot.
Oh,
we,
we
just
talked
about
the
the
rustic
integration,
so
this
is
definitely
another
area
that
we
want
to
focus
on.
A
Sure
that
we're
comfortable
calling
that
integration
GA
and
so
we
anticipate
spending
one
or
or
maybe
a
couple
of
releases
working
on
doing
some
stabilization
there
and
then
beyond
that
they're.
There,
as
I,
said
a
number
of
different
issues
that
are
in
the
backlog,
and
you
know
we're
continuing
to
think
about
where
we
want
Valero
to
go
as
we
as
we
look
ahead
to
2.0
and
beyond,
and
so
we're
at
this
point
definitely
open
to
ideas
from
the
community
from
users.
A
So
if
there
are
any
particular
areas
where
you'd
like
to
see
more
development,
if
there
are
any
particular
features
that
you
that
you
think
are
missing,
please
just
reach
out
to
us
on
slack
through
github.
In
this
meeting.
However,
you
want
to
reach
out,
but
we're
definitely
interested
in
hearing
your
feedback.
A
C
Absolutely
we
would
love
to
get
feedback
on
how
you're
using
Valero.
We
have
an
issue
opened
up
for
that
13:27.
The
link
is
here
in
the
in
the
notes:
we'd
love
for
you
to
lay
a
comment
on
that
issue
and
let
us
know
how
you're
using
Valero
and
and
how
it's,
making
your
life
better.
That
would
be
fantastic
and,
like
Steve,
said
we're,
you
know,
gonna
start
doing
be
1.1
planning
so
really
interested
in
what
you
would
like
to
see.
A
Great
thanks
and
then
yeah
as
I
as
I
just
mentioned,
you
know,
come
join
us
and
slack
we're
in
the
in
the
kubernetes
slack
organization
under
the
Valero
channel.
So
come
join
us.
You
know
if
you,
if
you
aren't
necessarily
ready
to
make
a
code
contribution,
but
you've
been
using
Valero.
It's
really
helpful
to
us.
If
we
have
folks
in
there
who
can
help
answer
other
users
questions
so
we'd
love
to
see
you
in
there
and
and
then
yeah.
A
Let
us
know
what
features
you're
interested
in
seeing
going
forward
and
then
finally,
I
just
wanted
to
cover
some
shoutouts
for
some
some
contributors.
We've
had
a
couple
of
of
contributions
since
the
last
meeting
that
we
had,
and
so
the
first
one
here
is
from
Syl
our
who
contributed
support
to
basically
for
Valero
to
be
able
to
support
availability
zone
based
discs
for
Azure.
A
So
this
is
a
relatively
new
capability
for
azure
to
have
disks,
be
within
a
specific
availability
zone
and
with
this
PR
we
Valero
now
has
the
ability
to
properly
backup
and
restore
these.
So
that's
definitely
a
great
addition
for
agile
users
and
we're
looking
to
use
this
new
feature.
So
thank
you,
so
our
and
then
Fabio,
who
is
a
repeat
contributor,
added
I,
believe
his
third
PR
to
add
some
validation
to
the
Valero
back
up
download
command.