►
From YouTube: Velero Community Meeting - August 10, 2021
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
welcome
to
the
valero
community
meeting
today
is
tuesday,
the
10th
of
august
and
as
usual,
let's
kick
things
off
with
some
status
updates,
so
dave
you're
up
first.
B
Yeah,
so
I
actually
got
some
time
to
code
during
our
week
last
week
and
been
chugging
along.
So
I
have
the
upload.
Progress
is
all
plumbed
and
it
almost
almost
works.
At
least
you
know
very
basically,
so
I
was
hoping
to
have
a
demo,
but
I
finished
the
code
about
two
minutes
before
the
meeting
started
and
it
doesn't
it
it
doesn't
hook
up
yet,
but
I
think
by
next
week
we'll
have
something
to
talk
about.
I've
got
some
stuff
in
discussion.
I
want
to
discuss
so
that's
that's
it
for
me.
A
Excellent
thanks
dave
any
comments
or
questions
or
anything
for
dave
before
we
move
on.
A
Okay,
so
yeah
I'm
next
in
the
list,
so
just
an
update,
we're
still
working
towards
getting
a
v163
release
ready
for
release,
and
so
this
is
needed
to
provide
compatibility
with
kubernetes
122,
which
was
released.
Last
week.
A
We
were
hoping
to
get
out
in
advance
of
that
release
and
but
we've
discovered
a
few
kind
of
last
minute
issues
that
we
needed
to
fix
the
first
one
of
these
was
that
we
were
still
using
the
v1
beta
1
api
for
the
crd
readiness
check,
so
that
has
been
merged
and
then
the
following
one
is
to
skip
the
api
service
restores
for
kubernetes
managed
services.
I've
just
realized
as
well.
I'm
not
sharing
my
screen
with
the
notes,
so
I'm
going
to
go
ahead
and
do
that
sorry
about
that.
Everyone.
C
A
Let
me
just
make
a
little
bit
bigger
as
well
great
yeah,
so
so
that
this
is
the
this.
The
pr
for
skipping
api
service
restores
that
is
currently
up
for
review,
and
so
once
that's
merged.
A
D
Brilliant,
I
have
a
comment
regarding
this,
so
so
can
we
write
down
an
issue
to
make
sure
we
can
discover
such
issues
in
like
indian
automation
tests?
I
don't
quite
understand
this
yeah.
A
So
I
I
did
open
an
issue
for
yeah,
so
I
have
some
scripts
and
things
locally
that
I've
been
using
for
testing
this.
So
I
will
yeah
I'll
write
that
up
as
well
and
and
kind
of
discuss
the
the
environment
that
I
was
using
where
I
was
able
to
replicate
this
and
also
how
I
was
able
to
trigger
this
behavior.
A
So
yeah,
that's
that's
a
great
idea,
so
I
will
do
that.
Okay,
is
there
any
other
questions
or
comments
on
that.
A
Okay,
let's
move
on
you're
up
next.
E
I'm
still
working
on
the
regular
internet
test,
hit
on
s
and
find
some
new
issues
and
and
I'm
trying
to
figure
fix
them
out.
E
A
Absolutely
awesome
thanks
any
other
questions
or
comments
for
one
guy.
A
Okay,
daniel
you're
up
next.
D
There
are
some
dependency
on
the
crash
d.
I
mentioned
in
the
description
area
of
this
pr
and
I
will
follow
up
with
crafty
maintainers
to
have
them
fixed
if
they
cannot
fix
by
the
the
rc
date
of
valero.
I
will
provide
a
workaround,
but
there
is
a
bug
in
crash
d.
If
you
look
at
this
number
210.
D
Yeah,
the
filter
doesn't
seem,
there's
a
there's,
a
bug
in
the
filter,
the
way
the
filter,
the
resource
when
we
collect
when
we
use
crafty
to
collect
the
resource
the.
If,
if
this
can't
be
fixed
on
the
crashly
side,
we
need
to
you
know,
shift
this
feature
with
this
bug.
The
impact
is
that
when
we
collect
resources
like
backup,
backup,
resource
location
and
stuff,
like
that,
the
pod
and
the
backup
resource
will
also
be
collected,
so
I
think,
that's
acceptable,
but
ideally
it
should
be
fixed.
D
A
A
Okay,
is
there
any
anything
else?
I
I
can't
see
if
there's
anyone
else
on
the
call,
otherwise
we
can
move
on
to
discussion
topics
dave.
Do
you
want
to
chat
about
your
topic.
B
Yeah
something
fong
would
be,
but
I'll
catch
up
with
them
on
slack,
so
just
kind
of
a
general.
F
B
To
toss
out
there,
we
have
a
kind
of
an
ongoing
thing.
Excuse
me.
B
A
Yeah,
I
think
if
I
I
don't,
have
the
issue
number
10,
but
I
think
there
was
a
discussion
just
to
add
a
general
timeline
mechanism
to
all
of
the
plug-in
apis,
because
I
think
the
approach
that
iphone
was
looking
at
using
was
just
adding
a
context
to
the
apis.
B
B
I
think
that's
still
a
good
idea,
though
we
may
not.
You
know,
depending
on
where
we
wind
up
with
versioning,
we
may
not
be
able
to
do
that.
So
what's
happening
right
now
is.
Is
we
have
multiple
types
of
plug-ins?
B
I
know
that
there's
definitely
a
concern
about
the
volume
snapshots
taking
a
long
time,
specifically
the
vsphere
plug-in,
and
so
it's
funny,
because
the
vsphere
plug-in
is
no
longer
a
volume
snapshot.
It
actually
became
a
backup
item
action
and
restore
item
action
because
we
needed
to
back
up
and
restore
the
pvc
level.
So
I'm
seeing
that
volume
snapshotters
and
the
backup
item
action,
restore
item
action,
delete
item
actions
for
things
that
are
snapshots.
B
These
should
both
get
merged
into
item
snapshot.
So
anything
that's
current,
anything,
that's
snapshotting,
something
any
of
the
volume
the
existing
volume
snapshotters,
either
the
backup
item,
actions
which
are,
for
example,
like
csi
and
vsphere,
or
the
volume
snapshotters.
These
should
become
item
snapshotters
and
item
snapshotter.
We
can
put
the
version
the
timeout
in
from
the
beginning
and
then,
as
the
plugins
rev
they'll
support
the
timeout
anyway.
B
So
that's
and
we
can
we
can
still
go
ahead
and
add
it
to
backup
item
action,
but
I
think
that's
less
for
long's
use
case.
I
think
that's
less
critical
because
he
was
he
was
really
running
into
problems.
Just
the
you
know
the
vsphere
plug-in
just
kind
of
goes
off
for
a
long
time,
if
there's
an
issue
with
talking
to
vc
or
something
yep,
any
thoughts
from
anybody
on
this.
C
C
Question
around
the
item,
snapshotter.
Is
that
something
new
that
I
is
that
a
new
action
that
I
don't
know
about
our
plug-in.
B
Yeah,
it's
part
of
the
upload
monitoring,
so
basically,
we
didn't
have
a
good
way
to
expose
the
progress
and
because
volume
snapshot,
so
volume
snapshotter
is
a
little
is
too
limited.
We
could
have
extended
volume
snapshotter
except
csi
and
vsphere
already
moved
to
backup
item
action,
and
I
looked
at.
B
Yeah
and
the
design
documents
get
updated,
so
you
know,
as
I
actually
implement
it-
there's
of
course
issues
but
we'll
we'll
talk.
B
As
the
code
gets
closer
to
actually
working,
then
we'll
come
back
and
go
through
the
high
level
of
what
happens
anyway,
so
so
the
new
api.
So
the
idea
behind
the
api
is
it
handles
all
snapshotted,
snapshotty
type
things.
So
we
started
abusing
backup
item
action
to
make
it
run
snapshots
for
csi
and
vsphere.
But
that's
not
really.
B
What
backup
item
action
is
is
meant
to
do
because
it
it
doesn't
like
collect
everything
together,
because
it
there's
like
a
backup
item
action,
there's
a
restore
item,
action
and
a
delete
item
action,
all
of
which
are
separate
we're
going
to
have
yet
another
one
which
has
been
like
progress,
but
not
every
backup.
Item
action
actually
snapshots
something
most
of
them.
B
Don't
most
of
them
modify
our
resource,
whereas
volume
snapshot
is
very
clearly
like
yeah,
I'm
taking
a
snapshot
of
some
thing,
specifically
a
volume,
but
you
know
conceivably,
we'll
do
other
things
in
the
future
and,
like
we
weren't
doing
a
good
job
of
listing
out
the
the
vsphere
snapchat,
I
think
we
did
csi,
but
it
was
like
a
hack
so
and
like
the
cleanup,
was
kind
of
hacky
as
well.
So
I
want
to
get
those
all
merchants:
hey,
there's
phone.
F
B
We
still
want
to
have
it
on
backup,
item
action
and
the
other.
So
so
my
thinking
is
that
for
volume
snapshots
we're
going
to
be
moving
all
the
plugins
to
the
item,
snapshot
or
plug-in
api,
and
we
can
put
version.
We
can
put
a
timeout
in
that
from
the
very
beginning,
and
I
don't
think
there's
a
lot.
I
don't
think
there's
a
good
reason
to
put
it
into
the
old
volume
snapshot
or
apis
because
they
don't.
You
know
if
we're
moving
them
forward.
Anyway.
B
We
don't
really
need
that
and
the
backup
item
actions.
There's
two.
You
know
the
csi
plug-in
and
the
vsphere
plug-in
are
both
backup
item
actions
but
we'll
move
those
to
be
item,
snapshot
or
plug-in
so
they'll
automatic.
So
all
the
volume
snapshots
will
automatically
move
to
the
new
api,
and
if
we
put
the
timeouts
into
the
new
api
from
the
beginning,
then
we
just
get
that
as
we
move
everything
forward.
B
F
For
the
for
the
timeout,
I
think
you
can
for
the
the
versioning
like
the
versioning
of
the.
I
think
we
should
go
ahead
and
ask
for
the
contacts
to
enable
camera
anyway,
whether
or
not
we're
going
to
do
it
for
each
plugin
or
not
it's
up
to
us
later
for
for
their
outlets
right
dell
emc.
What
we
need
is
to
have
a
timeout
in
the
backup
snap
snapchatter.
F
If
that
backup
it
backup
action
item
being
folded
into
item
snapchatter,
then
that's
all.
We
need,
from
my
point
of
view,
I'm
kind
of
a
little
bit
selfish.
Here.
F
F
So
I
think
if
we,
if
we
have
this
item
snapshotter
ready,
then
we
can
just
use
that
for
outlooking.
F
So
far
we
always
use
these
here,
which
you
guys
gonna,
throw
into
the
items,
much
harder
right,
yeah,
and
in
that
case,
then
we
are
by
the
time
that
we
need
by
the
time
that
we
have
the
flux
in
versioning
14.
I
think
that
should
be
ready
for
us.
I
I
okay
with
that.
B
Okay,
so
just
as
attended
plan
of
record
we'll
leave
the
existing
volume
snapshot
or
api,
we'll
just
leave
that
alone,
because
that's
going
to
be
deprecated
and
obsoleted
and
we'll
definitely
have
the
timeouts
in
item
snapshotter
and
then
we'll
put
them
into
the
other.
Backup
item
restore
item,
delete
actions
item,
as
you
know,
either
we'll
get
into
one
seven
or
we'll
get
it
into
one.
Eight.
F
Yeah
I
need
to
I
need
to
read
the
item
snapshot
for
a
little
bit
more
to
make
sure
that
it's
take
care
about,
but
very
likely
it
is
like
you
said:
if
it
worked
with
the
protein,
then
we
would
be
able
to
do
that.
B
Yeah,
let's,
let's
sync
up
so
I'll-
add
that
I
have
the
context
into
the
item:
snapshot
or
apis.
B
And
and
we'll
try
and
figure,
I
need
to
figure
out
how
to
make
all
that
stuff
actually
get
through
the
grpc,
but
we
need
to
figure
that
out
anyway,.
A
Yeah,
I
think
if
we
can
get
that
into
the
I'm
snapshotter,
because
there
was
definitely
concern
that,
like
with
the
plug-in
versioning
and
then
the
timelines
as
well,
that
there
was
a
concern
that
we
wouldn't
be
able
to
get
that
in
for
one
seven.
But
if
you
think
that
we'll
be
able
to
get
the
I
am
snapshotter
in
which
would
give
us
the
timeouts
anyway.
And
it
would
be
great
to
to
solve
that
use
case.
For
this
release.
A
Great
is
there
anything
else
that
anyone
on
the
call
wanted
to
discuss
today.
F
Yeah
so
now
now
I'm
back
with
the
and
now
I'm
back
after
vacation,
so
I
think
we
can
continue
continuing
to
the
coding
for
that.
F
So
right
now,
I
think,
as
I
picture,
I
chat
with
bridget
on
glass
that
I
will
continue
adding
codes
into
my
private
branch
until
the
feature
brand
is
until
bridgette
create
the
feature
branch.
At
that
point,
let
me
know
I'm
going
to
start
merging
it
into
the
future.
Okay,.
A
Awesome
thanks
yeah.
No,
I'm
sorry,
I
didn't
get.
The
branch
created
just
been
called
trying
to
get
some
of
the
stuff
done
for
the
163
release,
but
I
I
can
create
the
branch
and
we
can
get
that
set
up
tomorrow
and
I'll
ping.
You
on
slack.