►
From YouTube: Velero Community Meeting - March 29, 2023
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
Meeting
on
March
29th,
first
for
some
overall
status,
we
have
reached
the
FC
Point,
probably
1.11,
last
Friday,
so
we
are
doing
some
posts
of
the
testing
and
women
finish
the
testing.
We
will
see
how
many
bugs
and
how
many
bugs
and
whether
we
need
to
fix
that
fix
them,
and
then
we
will
be
able
to
know
the
RC
update
or
time
and
for
way
1.12.
That
is
the
next
release.
A
We
have
started
the
plan,
and
so
we
are
collecting
the
requirements
for
for
candidates
for
with
1.12.
So
if
you
have
any
requirement
one
to
get
into
a
1.0,
just
add
the
1.12
candidate
label
at
the
this
is
shown
here.
A
That's
it
for
the
overall
status
and
for
not
for
some
individual
update.
Myself
is
working
on
some
money
tasks
for
way.
One
more
11
and
also
I
have
tested
tested.
The
I
did
more
POC
I
integrates
with
the
r
r
II
code,
and
currently
the
basic
workflow
could
could
finish,
I
mean
so,
but
there
are.
There
was
still
some
code
changes
because
the
data
uploader
data,
uploads
Dr-
is
it
a
matter
to
download
the
data
flow
CR
during
install?
A
B
A
Okay,
thanks
yeah
I
mean
folks
are
the
manual
testing
yeah.
This
is
okay.
C
Or
from
myself,
kubernetes
version
up
to
1.25
in
in
Italy,
on
Main,
Branch
and
and
the
second
is
also
working
on
1.11
menu
test.
That's
all
from
my
site.
D
Yeah,
so
there
was
some
a
couple
of
other
additional
PRS
relating
to
the
item
operations
that
got
merged
with
last
week.
New
bug
reported
from
the
testing
this
week
have
a
dunk
fix
up
there
under
review.
I
made
some
changes
in
response
to
review
comments
today,
so
hopefully
that'll
be
good
to
go,
and
then
I
also
have
the
example
plug-in
for
backup
out
of
Maximum
stratum
action
V2,
and
we
need
that
merged.
A
Okay,
thanks
I
will
attack
the
the
pr
game.
I
think
it
has
already
been
ready
for
review
of
performers.
Yes
and.
C
E
A
Okay,
I
think
that
comments
are
never
attract
that
and
I'll
get
back
yeah
and
anyone.
Anyone
else
has
some
update.
A
If
not,
I
will
go
to
the
discussion
topic
section.
There
are
one
topic
for
myself
and
it's
about
to
deprecate
the
graphical
path
for
fasting
backup
as
we
as
we
know.
We
in
1.10.
We
have
included
the
copy
of
past
and
we
have
run
that
for
for.
A
Question
well
and
together
with
the
rest
of
the
parts,
but
the
rest
part
is
still
with
as
a
default
path
for
fastest
backup.
So
now
we
propose
to
start
the
concrete
application
process
for
for
this
functions,
backup,
for
example,
we
can
first
make
The
copier
pass
as
a
default
pass
and
besides
that,
I
think
we
also
need
to
finish
the
available
application
are
processed
that
has
been
included
in
this
PR
so
and
then
we
can
merge
the
APR.
D
A
D
Gonna
say
we
definitely
need
the
deprecation
process
finalized
first,
because
once
we
have
that,
then
we
know
you
know,
for
example,
once
we
deprecate
it,
you
know
if
we
deprecated
rustic
and
1.13,
for
example,
the
process
would
determine
you
know
what
release
we
could
remove
it
in
or
if
it
was
112
and
again,
the
process
would
talk
about
how
long
we
need
to
keep
that
deprecated
functionality
in
place
before
we
actually
remove
it.
A
Yeah,
so
so
there
are
two
things:
first
is
to
make
consensus
consensus
within
this
PR
and
merge.
That,
and
another
thing
is
we
start
The
copier
Parts
at
the
default
path,
and
for
that
for
this
one,
what
so?
What
is
our
our
opinions
like?
Can
we
do
that
in
way
1.11
or
we
do
that
in
1.12.
F
D
We
need
that
we
need
the
deprecation
process
merged
before
we
can
deprecate
rustic.
We
don't
have
to
have
rustic
deprecated
to
make
copy
the
default,
because
we
could
make
copy
the
default
in
1.12
for
1.11,
for
example,
and
then
in
the
following
release:
dabricate
rustic,
we
don't
have
to
do
those
at
the
same
time.
Necessarily
it
might
actually
make
sense
to
make
to
make
copy
the
default
first
and
don't
deprecate
rest
to
get
and
then
in
the
next
release.
Deprecated.
F
Okay,
yeah
yeah
yeah,
but
for
this
the
application
University
I
think
there
are
two
things
we
are
talking
about
is
make
The
copier
as
the
people
that
pass
another
one
is
by
which,
by
win,
we
can
I
mean
remove
the
DraStic
yeah,
but
but
by
looking
into
the
process,
I
think
we.
F
If
this
deprecation
process
was
emerged
and
approved,
pool
and
merge,
it
I
think
we
should
follow
up
that
process
to
launch
the
deprecation
discussion
by
file
a
ticket
in
the
GitHub
ticket
in
the
GitHub
and
to
identify
what
we're
doing
by
when
we
can
okay
I
mean
by
when
we
will
launched
that
application
and
in
which
release
we
can
totally
remove
that.
So
I
think
discuss
the
detail
in
that
ticket
once
we
file
that
right,
yeah.
D
Yeah,
the
deprecation
policy
is
a
general
policy
that,
because
that
will
state
you
know,
for
example,
oh,
if
we
have
to
keep
you
know
a
deprecated,
API
or
functionality,
you
know,
must
stay
around
for
two
releases
or
whatever
we
Define
there.
That's
a
general
policy
for
anything
to
defecate.
Then
we
can
have
a
specific
discussion
around
deprecating,
rustic
and
there's
something
we
would
propose.
D
Okay,
we
want
to
deprecate
Rustic
and
you
know
1.12
or
1.11
or
whatever
version,
and
then
we
can
use
the
deprecation
policy
to
decide
based
on
what
version
We
deprecated,
what
version
can
we
remove
it
in
I
think
making
copy
of
the
default?
Is
it
I
mean
obviously
a
necessary
part
of
this,
because
you
know
if
you
removed
and
once
it's
deprecated
clearly
it
needs
to
not
be
the
default
anymore,
but
we
can
make
Kobe
the
default
earlier.
D
D
You
know
because
we've
had
it
in
110
already
but
I'm,
just
thinking
the
the
discussion
of
when
we
would
make
copria
the
default
is
really
kind
of
separated
from
deprecating
rustic
because,
for
example,
we
could
choose,
although
this
isn't
the
plan
to
make
copia
default
and
never
remove
rustic
and
keep
them
both
together.
Obviously
we
don't
want
to
do
that.
I
mean
I'm,
just
saying
technically,
those
are
separate
decisions
to
make.
D
F
D
But
saying
that
rustic
is
deprecated,
because
you
know
we
could
say
hey,
we
want
to
keep
both
of
these
forever,
but
we
want
rustic
to
you,
know
copy
a
bit
to
be
the
default,
so
those
are
kind
of
two
separate
things,
but
obviously
we
have
to
make
copy
the
default.
You
know,
but
by
the
time
we
we
deprecate
rustic,
because
we
don't
want
the
default
to
be
a
deprecated
API.
A
Yeah
yeah,
so
so
it
looked
like
the
point
is
whether
we
want
to
add
the
the
change,
the
default
value
as
part
of
the
application
process,
all
of
the
the
changing
default
value
thing
just
like
we
are
doing
for
erratic
it's
some
common
thing
as
the
process
of
the
application.
If
not,
we
can
do
that
separately
right.
If
so,
the
current
point
is
whether
we
want
to
add
that
thing
into
the
current
application
process.
Yeah.
D
Well,
the
this
replication
process
doesn't
even
reference
drastic,
because
this
is
a
general
deprecation
process.
This
is
how
does
Valero
handled
with
deprecating
any
feature
so
I
think
this
is
a
general
policy.
We
need
to
determine
first
before
we
then
propose
a
separate.
You
know,
GitHub
issue.
I
could
be
an
issue
to
discuss
specifically
following
the
new
deprecation
policy.
We
now
propose
to
deprecate
Rustic
in
this
release,
but.
D
Here
this
PR
is
a
general
policy
for
deprecation
of
any
feature.
It
doesn't
necessarily
reference
resting,
in
particular,.
A
D
A
Yeah,
okay,
so
I.
It
means
that
we
can
do
that
separately.
So
the
next
question
is:
do
you
want
to
do
that,
since
it's
really
I
mean
the
v1.11
I'm
for
rustic.
D
And,
did
you
mean
in
terms
of
deprecating,
or
do
you
mean
in
terms
of
making
copy
of
the
default.
D
Yeah
I
I,
don't
have
a
strong
opinion
on
that
one
in
terms
of
when
we
should
make
it
the
default,
but
I
just
know
that
we
need
to
make
it
at
some
point
before
we
deprecate.
F
Yeah
I
I
think
I
think
giving
one
1.11
is
already
you
you
already
have
seen
and
we're
coming
to
rc1
I
think
make
this
deeper
the
the
path
change.
We
need
to
think
about
more
about
that
you,
if
there
are
any
other
impact
for
this
release,
so
I'm,
not
sure
that
that's
just
my
opinion,
I
think
I
think
you
need
to
may
need
some
discussion
around
that
before
yeah.
Changing
the
people
of
data
past.
E
Let's
keep
it
optional,
we
can
do
it
as
a
default
in
112
right
because
for
data
more
we'll
always
be
using
copia.
There
is
no
option
right.
F
Yeah
but
but
if
we
yeah
that's
a
good
point,
so
if
we
introduce
the
data
mover
in
next
release,
1.1
trial,
so
by
that
time,
I
think
it
makes
a
data
pass
either
default
to
copy
or
maybe
more
makes
sense
right.
Yep.
E
A
Okay,
yes,
it's
an
open
question,
so
we
can
sing
that
further
so
before
before
we
we
decided
that
we
want
to
change.
Are
you
1.11
at
if
you
finally
want
to
change
that?
Let's
see
if
there,
if
there
is
anything
wrong
requirements
on
that,
and
so
so
it's
at
the
current
situation
based
on
the
Discovery
just
now,
we
of
did
some
work
both
of
those
some
are
some
work
on
weapon,
1.12
and
so
I
think
we
can
continue
for
this
one
for
the
WM
process.
Pr.
A
We
can
continue
on
that
and
we
we
we
can
mark
that
in
the
early
stage
of
the
weapon
hotel
and
so
that
we
can
do
other
tasks
based
on
that.
F
Yeah
so
first
to
get
is
a
process
PR
get
merger,
it's
something
we
need
to
work
on.
You
can
understand
and
I
think
there
are
some
comments
from
even
right,
so
you
navigate
the
result.
So
maybe
we
can
follow
up
that,
probably
with
E1.
If
there's
any
other,
things
need
to
resolving
on
the
spr.
A
Uce:
okay:
let's
work
out
it's
PR
offline,
so.
F
E
A
Yes,
thanks
wow,
actually,
most
of
the
scenes
are
based
based
on
the
discussions.
I.
A
Some
some
parts,
some
new
parts
like
we
may
for
the
result,
part
we
have
some
new
things
like
when
we
may
want
to
get
the
data
uploader
CR.
That
is,
we
want
some
essential
information
during
the
result
from
the
backup
right,
so
we
don't
want
to
Resort
the
VR
I
mean
the
data
upload
CR
directly
into
the
cluster,
because
that
is
only
useful
for
during
the
result,
so
we
just
want
to
get
the
information
from
the
CR
and
then
create
create.
A
Another
object
currently
will
create
a
conflict
map
and
a
config
Mark
to
include
only
the
essential
information
from
the
background,
and
then
that
is
that
will
have
the
result.
That
is
one
change.
E
Basically,
then,
you
just
read
the
status
of
backed
up
CR,
create
a
config
map,
then
based
off
that
config
map,
you
create
the
downloads
here
right,
yeah.
A
Yeah,
that's
it,
okay,
that
is
the
process
and
the
other
things
we
have
added
or
clarify
some
requirements
on
the
data
data
data
download
plugin
I
mean
during
the
result
that
because
the
data
did
more
well
create
the
PV
for
that
PVC.
So
we
have
added
some
clarification
for
the
for
the
previous.
For.
A
We've
added
a
selector
and
a
label
that
is
that
that
is
the
data.
More
will
add
the
label
for
the
grading,
the
PV
and
the
to
prevent
the
Purity
form
automatically
bounded
by
the
accumulative
system
or
the
PVC
need
to
add
this
on
a
selector.
That
is
actually
we
have
a
way.
That
is
what
we
are
doing
in
a
code,
but
it
is
not
it's
not
covered.
A
It
was
not
covered
during
our
our
discussion,
because
maybe
we
thought
that
with
the
detail
but
later
we
think
it
is
necessary
to
clarify
in
this
dog.
So
we
added
that
and
finally,
the
final
thing
is
like
about
the
backup
deletion
so
because,
when
we
delete
the
backup,
we
need
to
delete
the
the
sample
the
sample
in
the
in
the
backup
reportedly
I
mean
the
data
right.
A
So
we
added
one
part
about
the
power
deletion
that
the
processor
is
something
like
about
great
Delete,
delete,
item
action
and
then
to
handle
the
to
handle
the
deletion
of
the
data
upload
CR,
and
then
it
will
further
delete
the
data
from
the
backup
repository
yeah
I.
Think
that
is
a
new
things.
Yeah.
E
A
Okay,
so
we
can
continue
review
on
the
pr
and
everything
is
of
the
design.
New
and
old
are
all
included
in
the
pr.
So
thanks-
and
we
can
continue
in-
reveal
that
cool.
A
Okay,
that
is
any
any
other
thing
one.
We
want
to
discuss.
A
Okay,
if
not
I,
think
we
can
change
up
here
thanks
everyone
and
have
a
good
day
and
night,
bye-bye.