►
From YouTube: Velero Community Meeting - March 15, 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
Hello,
everyone
today
it's
a
March
15th.
This
is
a
Valero
community
meeting
first
for
some
overall
status
update.
We
have
already
another
patch
for
way
one
content
with
1.10
that
is
with
1.10.2
and
and
we
have
included
some
fixes
and
for
for
service
and
for
other.
You
can
get
the
full
list
in
this
link
from
this
link
and
the
four
way
one
part
11.
A
We
we
have
made
more
progress,
so
we
are
getting
closer
to
the
to
meet
the
target
of
FC,
and
hopefully
we
can
decide
see
date
today
in
the
meeting
or
later
for
for
some
individual
updates
myself
from
my
site.
A
The
data
moment
design
had
been
ready
for
review
and
the
design
has
included
the
details
for
both
the
building
data
moment
and
also
the
plugin
data
moment,
and
it
also
integrates
the
the
design
to
included
the
design
to
incredit
increase
integrated
to
the
latest
backup
item
action
and
result
in
action
V2.
A
So,
let's
start
to
reveal
it,
and
my
network
is
to
integrate
the
data
moment,
POC
that
we
have
made
in
the
in
the
previous
to
integrate
it
with
the
latest
API
and
the
Highway
2,
and
that
will
have
to
help
us
to
further
verify
the
functionality
of
food
Beauty
and
also
verify
the
functionality
of
the
plugin
V2.
A
I
will
update
if
there
are
more
progress
on
that.
That's
foreign.
A
A
B
Yeah
I
believe
me
has
been
working
on
the
implementation
for
the
resource
policy
to
speak.
Some
more
skip
some
volume
from
backup,
I
think
Wonka
is
reviewing
the
pr
and,
from
my
side,
I
I've
resolved
an
issue
regarding
the
concurrent
snapshot.
Api
call
issue
in
AWS
and
working
on
some
PR
reviews,
including
on
code
changing
device
and
in
the
remaining
of
the
week
or
before
FC
I'll,
be
working
on
a
few
dark
issues
under
my
name.
B
Targeting
1.11
and
I
will
also
remove
the
code
related
to
the
item
snapshotter,
which
was
introduced
earlier
by
Dave
for
a
progress
monitoring
which
end
up
being
incomplete
and
we
decided
to
choose
the
piv2
so
I
believe
those
code
is
no
longer
needed
and
since
we
have
more
time,
I'll
remove
them
in
one
diagram.
That's
all
from
iPad
thanks.
C
First
of
all,
just
I'm
good
to
hear
that
you're
removing
those
parts
that
was
on
my
list
of
things
to
deal
with
eventually,
but
I
hadn't
gotten
to
it
yet
so,
but
yeah,
that's
right!
Everything
that
was
intended
with
that
we're
now
doing
with
the
biab2.
So
none
of
that
is
needed
anymore.
In
fact,
there
actually
wasn't
any
code
in
the
controllers
that
actually,
that
was
ever
merged
that
uses
that
anyway,
so
I'm
just
going
to
get
rid
of
that
now.
C
Okay,
so
yeah
relating
to
the
biav2
follow
NPR,
where
I
implemented
the
suggestions
that
we
did
not
get
in
the
original
PR
that
was
merged
recently
I
had
that
wait
for
additional
items
to
be
ready,
PR
that
I
had
last
week.
It's
now
ready
for
review,
because
if
I
got
the
required
changes
in
related
to
Emily's
VR,
where
she
added
the
resource
timeout,
which
I'm
using
in
this
PR
so
this.
So
this
has
been
updated
now
to
include
that
new
resource
timeout
field.
C
So
this
should
be
ready
for
review
I'm
working
on
the
restore
item,
action,
V2,
monitoring,
controller
changes,
probably
halfway
through
those
changes
today.
C
Hopefully
I
will
get
that
PR
out
either
tomorrow
or
you
know,
certainly
by
the
end
of
the
week,
but
I'm
hoping
to
get
it
sooner
rather
than
later
this
week,
because
I
am
in
the
middle
of
that
right
now
and
I
will
also
update
that
plug
an
example
to
also
include
a
restorative
action,
V2
plugin
for
testing
purposes
at
the
same
time,
so
that
again
that'll
be
a
draft
PR
until
that's
merged.
A
Yeah
well
review
to
the
pr.
Actually,
the
house
started
and
I'll
leave
a
comment.
If
any
and
Denver.
E
Okay
from
us
that
first
I've
been
working
on
investigating
some
failures
of
nightly,
and
one
of
the
failure
is
a
random
failure
on
Azure
pipeline
and
from
the
recent
recent
rounds
of
Natalie
results.
It
seems
it
has
been
fixed
by
Jung
who
is
PR
and
the
second
is
I.
I
I've
been
working
on
at
a
PVC
select
in
order
in
test.
The
pr
is
ready.
That's
all
from
my
side.
D
F
F
It
also
needs.
Please
take
a
look
of
this
PR
again
and
try
to
merge
it
as
soon
as
possible
to
let
it
to
have
more
time
to
do
some
regression
and
functional
test,
and
the
second
one
is
the
support
notary,
Queen,
selector
PR.
F
F
I
think
that's
the
problem
in
the
API
machinery
Library,
please
scare
scroll
down
a
little
bit.
Andrew
already
reached
a
issue
in
the
API
machinery,
but
there
isn't
a
fix.
Yet
the
problem
is,
there
is
a
two
can
of
slackers
in
the
API
machinery
and
the
first
one
is
label
selector.
It
doesn't
support
the
not
equal
and
the
second
one
is
selector
that
supports
what
support
not
equal,
I.
Think
the
problem
is
the
two
libraries
isn't
synced,
so
I
tried
to
use
the
selector
to
instead
of
label
selector.
F
F
B
Yeah
I
think
that's
a
gap
in
Valero.
We
don't
have
a
a
mechanism
to
you
know,
convert
the
CR
from
one
version
to
another
and
considering
Valero
crd
is
already
V1.
B
We
probably
need
to
bump
up
to
V2
according
to
the
convention,
so
I
think
I
already
I'll
open
an
issue
and
we
try
to
explore
some
solution
in
the
next
meta
release.
So
so,
from
my
opinion,
I
think.
Probably
it's
okay.
We
differ
this
one
to
to
filter
really
I
didn't
expect.
This
is
requiring
such
big
changes.
I
noticed
you
changed
like
28
files.
B
D
B
More
than
than
I
expected,
if
there's
a
limitation
in
the
API
machinery,
we
probably
I
I,
think
since
this
is
not
any
regression,
this
is
just
an
old
problem
that
have
been
existing
for
a
long
time.
It's
okay,
we
delayed
further
and
I
think
what
what's
more
important
is
how
we
evolve
these
CRS
Scott.
Have
you
involved
in
you
know
the
earlier
days
of
Valero,
where
we
convert
the
CR
from
one
version
to
another,
like
from
B1
Alpha
One
to
B1
beta
one
V1
base,
one
to
V1.
C
No,
not
since
I've
involved,
if
any
of
that
was
happening,
it
was
before.
I
was
with
the
project.
A
B
Okay,
I'll
I'll
try
to
find
if
there's
anyone
used
to
work
in
Valero
still
in
VMware.
If
not,
we
will
need
to
think
about
this.
This
has
been
a
problem
because
we
have
been
adding
new
fields
to
the
CR,
which
has
already
been
one.
That
is
not
a
good
practice,
so
we
need
to
fix
that
I
think
so.
Yeah.
C
B
B
C
I
I'm
actually
not
sure
whether
adding
an
option
if
it
is
ever
a
problem,
although
I
I,
don't
have
experience
with
other
projects
on
that
I
mean
it
was
commonly
done
in
terms
of
I
I
know
when
you
break
compatibility,
that's
definitely
a
problem
in
terms
of
otherwise.
It's
not
obviously
whether
you
know
that's
actually
even
an
issue
as
long
as
what
you're
adding
is
optional.
C
You
know
when
we
do
things
like,
for
example,
actually,
finally
remove
that
you
know
default
volumes,
thoracic
that
that
would
actually
be
a
compatibility,
ranking
change.
You
know
yeah.
B
Yeah
I
think
I'll
always
decisual
and
let's
discuss
it
in
some
future
community
meeting
there.
That
will
require
some
thinking
like
if
we
only
remove
one
field
that
they
qualify
with
one
platform
V1
to
B2,
Alpha,
One
I,
personally,
not
sure
and
like
how
many
different
versions
will
should
Bolero
support
I'll,
do
some
investigation
and
write
an
issue
but
certainly
I
need
to
discuss
with
other.
You
know:
maintainers
I
don't
have
experience
in
that
Iris
either.
So.
A
B
A
B
F
A
And
see
any
any
further
update.
B
G
F
A
The
next
part
the
this
current
topics,
and
so
we
want
to
decide
to
activate
it
right.
Then
you.
B
Right
right,
yeah,
so
I,
don't
think
you
really
want
to
rush
to
submit
the
pr,
because
that
will
require
I
think
that
will
require
some
back
and
forth
like
adding
comments
through
resolving
or
follow
up
yours,
and
we
may
need
more
time
to
make
sure
the
existing
regression
test
passing
our
internal
pipeline.
So
I
also
communicate
this
to
pradeep
I.
Think
it's
okay
with
FC
ads
end
up
by
the
end
of
next
week.
So.
C
Yeah
I
think
that
makes
sense.
I
mean
I
still
want
to
have
the
pr
out
this
week.
So
we
have
the
full
time
to
you
know,
review
it
and
modify
it.
The
good
thing,
too,
is
since
there's
no
other
PRS
that
are
depending
on
this
one.
C
We
should
be
able
to
just
resolve
it
and
make
the
changes
within
the
1pr
and
not
have
to
do
follow-on,
but
it's
just
going
to
take
some
time,
like
you
said,
to
review
and
make
changes,
and
you
know
all
that
so
hopefully
I'll
have
that
PR
in
a
mid
to
late
week
this
week
and
then
we'll
have
the
time
but
yeah
you're
right.
It's
going
to
take
until
you
know,
certainly
beyond
the
Friday
Friday,
before
it's
totally
ready
and
merged.
C
C
A
If
not
I
think
we
can
finish
off
here
for
this
meeting
and
thanks
everyone
and
have
a
good
day
and
a
good
evening
thanks.
Thank
you.
Bye,
bye,.