►
From YouTube: Velero Community Meeting - Dec 14, 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
A
Okay,
so
status
updates
for
myself,
I
got
the
actual.
Let's
see
am
I
sharing
did
I
share
my
screen
properly.
I
did
not.
Let
me.
A
Share
that
okay
and
let's
see-
and
I
haven't
finished
up
my
thing
but
so
for
myself-
I
got
the
prs
for
the
item.
Snapshots
gz
merge.
So
that's
an
addition
to
the
velo
backup
that
will
contain
the
information.
It's
it's
a
it's
analogous
to
the
volume
snapshots
that
currently
exist,
but
this
will
be
for
snapshots
that
are
taking
taken
by
item
snap
shutters.
So
eventually,
this
should
include
all
of
the
different
things
that
have
been
snapshotted
volumes
and
other
stuff,
so
that
got
merged.
A
B
Yeah
so
so
I've
been
out
for
a
little
bit
working
on
some
other
things
and
also
just
yeah
working
on
some
health
stuff
as
well.
But
I
am
I'm
currently
working
on
the
astrolabe
crd
design,
focusing
on
that
and
then
also
looking
at
as
part
of
that,
looking
at
the
data
mover
design
for
bolero.
B
So
I
think,
like
our
goal,
was
to
have
a
design
dock
in
during
the
one
eight
for
the
one
eight
release,
so
I'm
hoping
to
get
at
least
a
draft
of
that
up
by
the
end
of
this
week.
So
we
can
get
reviewed
and
in
before
rc.
So
that's
my
focus
for
this
week.
A
A
Complete
is
scheduled
for
next
monday,
so
that'll
be
when
we
cut
off
any
new
any
new
features,
and
so
it
should
only
be
bugs
that
we're
finding
at
that
point,
so
we'll
kind
of
lock
down
the
branch
or
lock
down
main
for
a
while
and
then
the
I
forget
the
exact
date
for
the
release,
but
it
should
be
sometime
in
early
january
when
we
finish
up
one
eight
and
get
that
released,
that's
kind
of
it
for
today,
any
anything
else
we
want
to
discuss.
C
I
said
a
quick
question
relating
to
the
one
eight
I
haven't
been
following
this
as
closely
but
the
in
terms
of
the
content
there.
I
can't
remember
whether
the
plug-in
versioning
is
something
we
were
expecting
to
get
in
or
did
that
get
bumped.
C
A
It
should
make
one
nine.
I
think
we
just
need
to
to
finish
it
up
and
and
get
it
in.
B
So
I
think,
like
the
initial
design
dock
that
had
gone
night,
daniel,
had
some
comments
on
that.
So
the
the
approach
and
and
what
exactly
versions
will
look
like
is,
is
changing
a
little
bit.
So
I
need
to
incorporate
his
feedback
into
the
document.
So
that's
that's
kind
of
part
of
the
the
reason
behind
the
bump
as
well.
Yep.
D
D
As
of
yesterday
night,
I
addressed
one
question
mark
from
daniel.
I
added
this
on
the
design
dock.
I
agree
that
a
mechanism
to
bypass
the
execution
of
plugins
besides
unloading
and
loading
plugins,
I
know
that
it's
a
little
bit
disruptive
every
time
that
you
load
and
unload
the
plugin,
so
I'm
just
adding
something
simple
as
an
annotation
on
the
objects
like
the
name
of
plugin,
slash
the
hook
equal
skip
and
that
would
suffice
to
bypass
the
execution
plugins.
D
So
just
you
know
make
sure
I
address
the
last
comment.
If
someone
else
has
more
comments,
I'm
more
than
happy
to
add
on
the
design.
Just
remember
this
design.
This
is
not
the
actual
code
right,
so
I
I
guarantee
when
we
start
to
do
the
code
in
the
merge
request,
you're
going
to
have
more
discussions,
but
you
know
my
understanding
that
for
design,
I
think
that
we're
pretty
solid.
A
A
Let's
see
so,
I
think
that's
about
it.
Eleanor
actually
is
asking
me
a
question
about
the
wiki,
but
she
hasn't
shown
up
for
the
meeting
so.
A
Yeah,
so
I
guess
we're
just
going
to
call
it
early
and
I
think
we
have
one
scheduled
in
the
beijing
time
zone
next
week,
but
I'll
be
present,
but
I
know
a
lot
of
other
people
are
going
to
be
on
holiday
already.
So
if
I
don't
talk
to
you,
you
know
happy
holidays.
Merry
christmas,
happy
new
year
talk
to
you
in
january.