►
From YouTube: Velero Community Meeting - March 21, 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
Hello,
everyone
today
is
March
21st
and
my
name
is
Julian
vasilev.
Does
the
community
meeting
for
Bolero
so
please
follow
the
code
of
conduct
with
that
said,
I'm
gonna.
Add
the
link
to
the
meeting
notes
for
today.
A
So
add
yourself,
add
your
topics
if
you
have
anything
to
add
for
the
discussion
or
updates
with
that,
I
can
see
that
we
have
some
topics
already
added
by
Scott
and
by
onsho.
So.
B
A
Righty
there
you
go
hope
you
can
see
that
I'm
gonna
make
it
a
little
bit
smaller,
so
we
can
fit
every
screen.
Okay,
go
head,
Squad.
B
Okay,
so
yeah
a
good
week
for
getting
code
merged,
which
is
good
because
we're
getting
close
to
the
feature
complete
I
had
two
more
follow-on
PR's
from
the
previously
merged
backup
item
action,
controller
work,
some
bug
fixes
some
and
then
some
kind
of
late,
late,
breaking
changes
to
kind
of
improve
some
things.
B
We
just
set
the
default
frequency
of
running
that
async
action
controller
to
be
more
frequently,
I.
Think
it's
10
seconds
down
instead
of
two
minutes,
so
it'll
be
more
responsive
in
the
the
interface,
then
the
restore
item,
action,
controller
work
that
Pi
was
submitted.
B
B
So
everything
of
mine
that
is
needed
by
feature
complete
is
now
merged.
I
do
have
the
example
plugins
PR,
which
he
uses
the
new
features
from
backup
by
the
maximum
restore
item
action
that
lets.
You
basically
set
annotations
on
resources
to
sort
of
simulate
a
long-running
action.
So
you
can
see
the
workflow
happen
to
backups
and
restores
I
need
to
update
that
now
that
the
the
work
is
merged
on
the
controller
side
to
point
to
main
it
was
pointing
to
my
PR
fork
for
test
purposes.
B
So
I
will
update
that
this
afternoon,
which
means,
by
the
end
of
today
eastern
time
that
PR
will
be
ready
to
review
and
we
do
need
that
merged
before
we.
It's
not
needed
for
the
Valero
release
itself,
but
it's
needed
to
write
the
end-to-end
testing
for
the
item
operations.
So
we
do
need
to
get
that
merged
relatively
soon,
so
I
can
get
that
end
to
end
work
but
in
place,
because
the
goal
for
the
end-to-end
testing
is
to
get
that
merged
by
I.
B
A
Nope,
okay,
next
one
answer:
take
it
away:
do
you
need
the
screen
to
share
something
or.
C
No
I
I
think
it's
fine,
so
the
second
and
third
PR
that
I've
put
here
I've
gone
through
multiple
Community
meetings,
walking
through
those
three
hours
and
requesting
for
review
on
the
Json
substitutions.
One
Daniel
had
few
comments.
I
have
addressed
those
basically
moving
from
the
ReUse
to
write
an
action
to
to
the
actual
restore
flow,
I've
updated
the
third
one
up
to
the
third,
the
proposal
for
the
third
one
for
the
second
one
I,
it
was
basically
a
PR
which
included
two
things.
C
First,
was
selection
of
volume,
standard
classes
and
also
introducing
a
plug-in
inputs
field
in
Valero.
So
there
was
a
bit
of
disagreement
in
the
previous
discussion
we
had
so
I
have
split
it
into
two
proposals
so
that
the
second
one
is
kind
of
agnostic
of
the
plug-in
input
screen.
Then
we
kind
of
at
least
drive
it
to
closure
through
annotations.
So
that
is
the
update
on
the
second
and
third
one.
So,
basically,
I've
made
changes
as
per
the
discussion.
C
We
had
last
time
and
Daniel
also
acknowledged
acknowledged
over
chat
that
so
we
can
go
through
it.
The
first
one
is
for
is
the
proposal
for
introducing
a
plug-in
inputs
field
in
all
these
backup
restore
and
schedule.
Crs,
the
the
motivation
I
have
tried
to
capture
as
part
of
this
PR.
Basically,
there
are
a
bunch
first
example,
being
a
selection
of
volume,
structure,
classes,
others
being
very
various
plug-in
specific
operations
where
we
are
facing
issues
tweaking
the
plugin
Behavior
or
passing
more
inputs
to
the
plugin.
C
We
kind
of
proposed
this
kind
of
proposed
this
approach
of
a
new
field
in
the
CR
instead
of
having
an
annotation
heavy
route
that
we
have
taken
so
far,
so
I
have
a
request
to
the
community
like
whoever
owns
plugins,
maybe
within
their
company
or
maybe
the
OSS
versions.
You
can
perhaps
put
comments
on
this
PR
with
the
use
cases
that
you
have
so
that
we
can
build
enough
of
a
use
case
for
this
proposal.
C
The
plugin
inputs
proposal
I
have
walked
through
all
of
these
three
in
previous
meetings,
so
I
can
add
more
context
if
needed,
but
yeah.
That
is
a
request
from
my
side
and
for
overall
for
the
three
PRS
I'll
request,
other
folks
to
also
please
go
through
them
and
give
give
a
review.
That
would
be
great.
That's
it.
A
Thank
you
N1
to
comment
on
this
stuff.
A
No
okay,
in
that
case,
we're
out
of
topics
for
today.
Anyone
else
wants
to
add
anything
for
for
today's
agenda
or
any
questions.
B
I,
just
I,
actually
so
just
a
quick
thing
from
what
I'm
remembering
I'm,
not
looking
at
the
right
now
but
I
believe
this
end
of
this
week
is
the
intended
date
for
the
feature
complete
that
was
delayed
from
March
10th
to
the
24th.
As
far
as
you
know,
is
that
still
the
case
I
haven't
heard
anything
that
suggests
we
would
be
pushing
off
again
but
I
think
it's
worth
asking
asking.
B
Yeah
because
we
discussed
last
week,
we
agreed
that
we
were
going
to
push
it
or
last
time
you
know
to
the
24th,
because
which
is
two
weeks
beyond
the
original
one
I
just
given
that
we're
three
days
away
from
there
now
I've
haven't
seen
any
comments
on
our
on
on
slacks,
so
it
sounds
like
people
think
that
they're
good
to
go
but
I
guess
it'll
be
good
to
see.
You
know,
and
you
know
obviously
the
other
maintainers
aren't
on
this
call
right
now,
but
would
be
good
to
kind
of
get
a
feel
for.
B
B
I
know
these
designs
we
want
to
get
in
as
well,
but
it's
a
little
bit
of
a
different
schedule
because
we're
not
you
know
Building
images
from
those
at
this
point,
but
obviously
I.
You
know
again.
That
is
also
a
focus.
We
need
to
get
some.
You
know,
reviews
on
those
design
proposals
I
mentioned
as
well,
but
specifically
about
the
features
that
we're
delivering
with
111
as
I
guess.
My
questions
about
more
about
that.
B
Yeah,
just
just
you
know
it's
worth
having
that
kind
of
conversation
just
to
confirm.
We
still
think
we're
on
track
or
we
know
we're
not.
You
know
we
need
a
few
more
days,
hopefully
not
but
again,
good
to
know
that
before
Friday,
if
we're
gonna
have
to
be
on
Friday
for
that,
because
that
has
consequences
for
the
fc1
and
you
know
GA
as
well.
A
B
C
C
B
14Th
is
just
in
time
for
kubecon.
B
So,
according
to
this
road
map,
the
end
of
the
current
week
is
feature
complete.
Then
April
4th,
where
I
see
one
and
obviously
you
know
everything
kind
of
goes
from
there.
A
B
As
long
as
we
can
get
everything
that
we,
you
know,
need
feature-wise
merged
by
the
end
of
this
week,
we
should
be
on
track
for
that.
Obviously,
you
know
still
time
for
bug
fixes
and
all
that
you
know
through
rc1
and
others.
A
All
right
talking
about
kubcon
any
of
you
will
be
at
the
redhead
boot
talking
about
openshift
and
in
particular,
if
someone
has
a
questions
about
Valero
or.
D
Oh
I
meant
to
sign
up
for
that.
Yeah
I
need
to
go
back
to
that
email
and
look
at
that.
A
D
A
Because
I
spoke
with
for
deep
last
week
and
he'll
be
at
the
viewmer
boot
prepare
to
talk
about
this
stuff.
Okay,.
D
A
A
Yeah,
yeah
or
I,
don't
know
so
yeah
and
I'll
be
at
the
harbor
Booth
as
well
and
view
more.
So
we
can
I.
B
A
Know
have
a
some
some
kind
of
relation.
Do
you
point
to
the
people
where
there
are
people
to
talk
about
Bolero.
D
Yeah
so
I
think
previously
weren't
sure
if
pradeep
was
going
to
be
able
to
make
it
to
kubecon.
D
He
gonna
have
time
to
hang
out
with
the
Valero
crew
yeah.
D
All
right,
we're
gonna,
also
have
some
cute
some
of
our
quality
Engineers
there,
nice.
A
As
well
yeah,
so
once
we
have
some
some
number
because
I
think
from
our
site
by
our
side,
I
mean
VMware,
it's
gonna
be
me
and
and
pradeep
so
from
your
site.
I
think
so
far
from
that
call
is
us
and
in
Squad
and
the
QA
folks.
So
when
we
have
some
concrete
numbers,
we
can
plan
something
and
I
know
also
Satya
from
podcaster.
A
I
wanted
to
to
meet
and
greet,
and
also
any
anyone
from
from
Microsoft
from,
like
your
sub
team,
available,
bolero
and
and.
C
A
A
Right,
okay,
cool
anyone
else,
any
any
anything
else
to
to
add
for
today's
topics.