►
From YouTube: Velero Community Meeting - Nov 5, 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
B
Hey
everyone
good
morning
now,
I'm
just
a
kind
of
brief
PSA,
so
the
beta
for
1.2
is
out
and
has
been
out
for
a
week
or
two
we're
not
planning
to
release
the
second
beta,
just
based
on
the
small
number
of
issues
that
have
come
in
so
I.
Think
the
next
release
will
be
the
full
1.2
release
and
I'd
say
you
can
expect
that
either
towards
the
end
of
this
week.
B
If
we
feel
ready
or
sometime
next
week
and
then
yeah
for
my
personal
update,
I
mean
I've,
basically
just
been
working
on
making
sure
that
that
1.2
release
is
good
to
go.
Checking
you
know,
making
some
small
bug
fixes
doing
some
reviews
on
on
fixes
that
have
come
in
and
just
working
on,
cleaning
up
the
docks.
So
that's
really
it
and
that's
what
I'll
be
focusing
on
over
the
next
few
days.
Until
the
release
is
up.
B
I
can
do
that
actually
working
on
writing
the
blog
post
right
now,
so
I'll
just
pull
up
what
I
have
there.
You
know
the
biggest
thing
is
that
we've
we've
worked
on
taking
the
cloud
provider
plugins
that
were
within
the
core
velaro
repository,
so
the
plugins
for
AWS,
asharamji,
CP
and
we've
extracted
them
into
their
own
repositories
and
into
their
own
proper,
plug-in
container
images.
So
this
kind
of
brings
them
to
parity
with
any
other
third-party
providers.
It
means
that
they
can.
B
They
can
sort
of
evolve
independently
of
Valero
so
that
we
don't
necessarily
need
to
release
them
on
the
same.
Cadence
is
the
core
of
Valero.
It
also
has
the
added
benefit
of
making
the
Valero
binaries
smaller.
So
you
don't
to
ship
all
of
the
SDKs
in
incorp
Galera.
You
can
kind
of
add
only
what
you
need.
So
there
are
some
other
benefits
as
well
and
some
more
details
on
that
in
the
blog
post,
but
so
that
was
definitely
a
big
one.
B
We've
made
some
improvements
so
that,
if
you're
using
rustic
to
backup
persistent
volumes
that
even
if
the
pod
that's
using
the
persistent
volume
gets
rescheduled,
you
still
get
an
incremental
backup
on
the
subsequent
drastic
backup
of
that
persistent
volume.
So
just
making
things
more
efficient,
there
we've
added
some
progress,
reporting
for
for
rustic
operations,
so
for
backups
and
restores
you'll
now
get
periodic
status
updates
of
percent
complete,
and
you
can
see
that
through
the
velaro
backup
describe
and
Blair
restore
could
describe
commands.
B
So
it's
really
useful
for
for
folks
who
wanna
know
what's
going
on
with
their
rustic
backups
and
restores,
let's
see
a
bunch
of
other
things,
we
added
structural
schemas
to
all
of
our
custom
resource
definitions.
So
this
is
a
requirement
for
any
custom
resource
definitions
that
are
being
created
in
the
v1
API
extensions
group,
which
is
exists
as
a
1.16.
So
we've
added
the
schema
there,
which
basically
just
gives
us
better
validation
on
any
custom
resources
that
are
being
created.
We've
added
some
more
support
for
server-side
encryption
and
some
of
our
providers.
B
C
We
may
touch
on
Valero
there,
but
we're
not
going
to
focus
on
Valero,
that's
mostly
on
the
existing
CSI
volume
snapshot
and
also
reviewing
a
documentation
for
1.2
since
I
was
not
here
for
a
lot
of
the
writing.
Of
that.
Just
make
sure
it's
understandable,
yeah,
not
all
not
a
whole
lot
from
me
this
week.
D
So
I
readily
help
documentation,
I
cleaned
up
a
lot
of
I.
Was
there
spruced
up
and
now
he
reflects
what
you
have
to
do
for
version
1.2.
It
is
working
progress
PR
because
it's
pointing
to
the
Vader.
There
are
points
of
Vader
images,
and
once
we
do
it,
the
official
release
will
upgrade
will
update.
I
WAP
data
PR
and
submitted
for
reveal,
and
we
did
a
lot
of
Doc's
updates.
D
Steve
has
been
great
also
in
guiding
how
to
make
that
better,
I'm
really
happy
with
where
we
are
as
far
as
Docs
now
I
think
I've
mentioned
it
before
we
have
contributing
information.
Now
we
have
some
some
guidelines
for
how
to
for
things
that
we
have
to
do.
I
mean
things
that
all
of
us
heard
about.
We
have
to
do
too
for
consistency
and
just
the
usual
PR
reveals
and
Morgana's
on
the
secret
project.
A
All
right,
what
have
you
been
doing?
Hey.
E
Yeah
so
yesterday
push
to
change
to
get
AC
Audis
only
flag
for
veterans.
Also.
This
will
be
important
when
upgrading
co,
DS
users
can
use
this
command
to
just
generate
the
didn't.
You
see
IDs
and
then
pipe
that
to
something
like
keep
CTL
reply
to
update
the
co
DS
Ivan
that
been
kind
of
doing
a
mix
of
Q,
Khan,
prep
and
community
support
and
I'll
probably
be
working
with
Nolan
later
this
week
as
well.
To
sync
on
my
talk.
A
Awesome
so
just
a
small
update
from
me
later
today,
I
have
a
call
with
someone
that
is
way
more
knowledgeable
about
Jekyll
and
and
Jekyll
websites
than
I
am
so
we're.
Gonna.
Look
at
upgrading
the
other
websites
to
well.
First
of
all,
Valero
and
a
bunch
of
other
websites
to
Jekyll
Otto
should
make
some
of
the
the
bills
that
we
do
faster,
which
is
really
helpful
when
we
do
local
dev
on
the
website,
because
right
now
it
takes
like
25
to
30
seconds
for
a
build,
which
is
just
nuts.
A
Help
out
with
with
ocean
it
doesn't
really
matter
when
we
actually
push
things
and
publish
them,
but
it
would
help
immensely
when
we
do
local
dev
for
it.
So
yeah
I'm
gonna
have
a
call
later
today
and
about,
and
if
you
are
so
I'll
I'll,
let
you
all
know
how
that
goes:
we're
looking
at
upgrading
the
contour
site
first
and
then,
if
that
works
out
well,
we'll
roll
out
the
other
changes
for
the
other
websites
here,
so
something
that
came
up
last
week
on
last
week's
call.
A
Was
the
community
lunch
at
cube
con
San
Diego,
so
we
we
have
a
time
and
date
and
the
the
way
we're
planning
this
is
essentially
to
come
to
the
VMware
booth.
If
you're
going
to
cube
con,
come
to
the
VMware
booth
on
Wednesday
at
12:30
and
we'll
direct
you
to
where
we,
where
we
are
at,
will
also
occupy
a
few
a
few
tables.
So
you
can
come
and
join
us
there
and
we'll
have
some
signs.
So
you
will
see
that
the
lair
o
is
sitting
at
these
these
tables
and
we'll.
A
No
all
right,
then
I
think
I
covered
it,
and
any
questions
run
that
if
you
are
going
to
be
at
cube
con
by
the
way
please
stop
by
and
the
VMware
booths
and
chat
with
us.
If
you
want
to
check
with
us
101,
of
course
you
can
always
reach
out
and
slack
it's
the
easiest
way
to
get
hold
of
most
of
us
here.
D
Have
not
a
question
but
something
about
discussion,
a
topic
for
discussion
we
don't
have
to
do
today.
I
was
leave
for
a
niche.
There
is
an
issue,
I
think
NOLA
opened
it,
but
I'm
not
finding
it
in
any
way
that
was
proposal
to
restructure
how
we
are
named.
We
named
the
plugins,
so
maybe
we
say
plugins
providers
instead
of
simple
games
with
the
providers.
The
providers
have
plugins
and
I
added
some
comment.
There
too
does
they
ring
the
bells
when
you
want
I.
D
D
D
C
Parameter
was
a
source
of
confusion
and
yeah.
That's,
like
you
say
in
this
comment.
Currently
sealed
like
a
single
process,
can
contain
multiple
plugins
inside
of
it.
So,
for
example,
we
have
the
AWS
repo
has
two
types
of
plugins:
it
has
the
object,
storage
and
volume
snapshot,
er,
so
I
think
there's
there's
a
bunch
of
stuff
in
here.
Some
of
it
is
like
clarifying
terms
and
maybe
coming
up
with
like
a
glossary
of
our
own
jargon,
and
some
of
it
is
fixing
up
the
UX
around
install
and
probably
helm.
B
Yeah
I
think
you
know
we
can
like
plugin
is,
is
a
term
that's
you
know,
definitely
overloaded.
All
over
the
place
I
mean
it
can
mean
different
things
in
different
contexts
and
we're
probably
not
super.
You
know
precise
about
how
we
use
it
like
it
could
be.
An
individual
object,
store
implementation,
or
sometimes
we
use
it
to
refer
to
to
a
container
image
that
contains
a
binary
that
contains
multiple
implementations
of
plugins.
B
You
know
this
issue
also
covers
and
gets
at
just
the
general
install
and
configuration
flow
and
I
think
there
is
a
kind
of
a
big
open
question
of
you
know
should,
should
you
be
able
to
install
Valera
without
yet
configuring
it
for
any
particular
backup,
storage,
location
or
any
provider?
And
if
so,
then
what
happens
when
you
start
adding
or
removing
those
things?
B
After
doing
the
install
we've,
always
kind
of
historically
assumed
that
when
you're
installing
you're,
also
configuring
a
place
to
back
things
up
in
a
you,
know
some
kind
of
storage
provider
for
that,
but
I
think
given
changes
that
we've
made
over
the
last
several
releases,
that
might
not
be
the
most
intuitive
flow
anymore.
So
I
think
we
you
know.
We
definitely
need
to
look
at
that
and
think
about
what
makes
sense.
B
D
And
I
think
I
think
it
makes
it's
possible
that
once
we
start
looking
at
plugins
as
components,
I
said
all
those
like
you're
saying
Steve,
there
is
an
image
there
is
a
provider
there's
like
a
bunch
of
things
that
we
call
plugins
once
we
start
is
ambiguous
in
these
things.
It's
going
to
be
easier
to
to
answer
the
question.
What
do
we
need
to
like
really
to
the
learner
needs
to
start
out
with
this?
It
might
be
piece
parts
of
what
we
call
a
plug-in,
but
not
it
might
not
need
to
be
the
whole
thing.
B
Yeah
so
I
mean
I
think
you
know
at
some
point
like
we
need
to
decide
when
we
want
to
spend
time
on
this,
but
someone
should
sort
of
take
a
look
at
the
existing
flow
and
think
about
what
the
you
know.
What
a
wouldn't
ideal
flow
would
be
for,
install
and
configuration
and
start
to
sort.
Some
of
this
out
I
mean
there
I
think
they're
a
bunch
of
interrelated
issues
here
and
it's
gonna
be
a
little
bit
hard
to
tackle
them
one
by
one,
without
thinking
about
kind
of
the
whole
thing
altogether.
B
B
Possibly
I
mean
we
yeah
we're
also
planning
on
you
know
over
the
rest
of
this
calendar
year
when
we're
not
at
conferences
around
vacations,
just
planning
on
kind
of
looking
at
the
totality
of
our
backlog,
and
you
know
all
of
the
big
things
that
we
want
to
do
and
figuring
out
what
what
order
we'd
like
to
attack
them
in.
So
you
know,
I
definitely
can't
promise
that
we
will
tackle
this
in
1.3,
but
I
do
think
it's
an
important
thing
to
revisit
at
some
point
relatively
soon.
A
Cool
one
thing
that
Nolan
reminded
me
of
so
we
we
do
have
another
call
that
the
Valor
team
needs
to
be
on
on
next
Tuesday,
so
we're
gonna
move
this
meeting
from
12:00
p.m.
Eastern
2
p.m.
Eastern
next
Tuesday.
So
hopefully
that
is
correct
in
the
Google
Groups
calendar
invite
if
it's
not
I'll,
make
sure
to
notify
everyone
in
slack
as
well.
So
I'm
gonna
move
this
to
hours
later.
So
you
get
a
little
more
time
of
your
day
before
the
Bolero
meeting
next
week.