►
From YouTube: Velero Community Meeting - May 26, 2020
Description
May 26, 2020
Status Updates
steve
finalizing things for v1.4; one bug-fix (thanks @ashish for catching) - https://github.com/vmware-tanzu/velero/pull/2560
bug in using custom CA cert for restic restores: https://github.com/vmware-tanzu/velero/issues/2562
spent some time brainstorming on multi-tenancy
ashish
1.4 testing using cluster-api as the workload to backup
Working on a blog post about get started with using CSI snapshotting. PR#2553.
nrb
1.4 testing last week
Was off Thursday/Friday
Planning to do the v1.4.0 release today, pending bug fixes
carlisia
on community support this week
PR out for initial kubebuilder migration: https://github.com/vmware-tanzu/velero/pull/2561
short video on how I use Goland for PR reviews: https://www.loom.com/share/a60b72518f5c453b97e797f6a5ba39f8
need to do lots of PR reviews
Discussion Topics
stephanie
we are looking to add an up-vote/down-vote capability to feature requests in the velero backlog as a way to more easily quantify what features the community is more interested in as a whole
we’ve filed the issue here: https://github.com/vmware-tanzu/velero/issues/2574
it could look something like this
we will be working to get this implemented and open this as an opportunity to provide quick feedback on features that you are most interested in - let us know what you think
A
Good
morning,
good
afternoon,
good
evening,
everyone
and
welcome
to
this
week's
episode
of
the
Balearic
community
meeting
and
open
discussion
today
is
May,
26
2020
and
we're
gonna
go
through
status
updates.
Of
course,
we're
gonna
talk
about
the
the
new
release
and
some
discussion
topics
so
with
that
I'm
sharing
the
Huckabee
and
the
chat,
if
you
want
to
add
anything
in
there
and
I'm
gonna
share
my
screen.
So
we
can
all
see
what
we're
talking
about.
B
Yeah,
hey
everyone.
Last
few
days,
mainly
just
finalizing
things,
41.4
I
have
one
open
bug
fix
she.
She
caught
an
issue
related
to
not
uploading
some
things
to
object,
storage
around
backup
progress,
so
the
fix
is
up
for
that
one
and
I
do
think
we
should
get
that
in
for
41.4,
I
tested
it
last
week.
It's
a
pretty
small
fix
and
everything
looked
good
I
was
looking
through
the
open
issues
that
have
come
in
and
there's
another
one
here.
B
B
Think
I
think
we
should
probably
just
get
the
fix
in
for
this
before
we
cut
1.4,
rather
than
having
to
immediately
do
a
patch
release
to
fix
this
and
I
think,
given
how
small
it
is,
it's
it's
pretty
low
risk,
but
definitely
open
to
other
folks.
Opinions,
I'll
put
a
PR
up
for
this
right
after
the
meeting.
So
everyone
can
just
look
at
it
and
assess
it.
B
Those
are
the
main
things
and
then
I
also
spent
a
little
bit
of
time
just
doing
some
brainstorming
on
multi-tenancy,
since
it's
a
thing
that
we've
we've
talked
about
for
a
while,
and
we
want
to
tackle
on
our
roadmap
just
trying
to
to
get
some
initial
thoughts
formed
and
written
down.
So
right
now,
I
just
had
some
notes
for
myself,
but
I
will
work
on
on
putting
some
one
notes
into
the
relevant
issues
over
the
coming
week
or
two.
B
B
D
C
Perfect,
it's
the
only
one
that
wins
that
discussion.
Maybe
you
can
talk
a
little
bit
about
that.
Shirley
would
make
sense
to
do
first,
given
the
impact
of
you
know,
some
of
the
big
ticket
items
like
most
attendants
in
working
parts
in
terms
of
like
sliding
them
in
the
right
direction.
That'd
be
a
good
part
of
the
discussion.
So
when
you
guys
talk
about
that,
okay
yeah
sure.
E
For
me
last
week,
I
spent
like
running
some
tests
on
the
1.4.
There
were
also
folks
who
wanted
whether
to
be
tested
against
clustered
API.
So
I
was
running
those
tests
as
well
for
people
and
then
kind
of
report.
What
I
saw
and
take
it
from
there
and
then
I
was
also
working
on,
like
a
blog
post
to
kind
of
help.
Folks
get
started
with
CSI
he's
not
shorting
capability
that
we
are
introducing
in
the
1.4
release.
So
that's
another
thing
that
I
was
doing.
E
F
F
So
that's
something
I
will
share
with
community
and
I'm
planning
to
do
the
1.4
released
today
pending
these
bug
fixes.
Excuse
me
looking
at
the
the
back
of
progress,
bug
fix
that
Steve
mentioned.
It
looks
fairly
straightforward
and
it
sounds
like
there's
only
one
other
one
for
the
rest
of
our
stores,
so
I
think
we're
in
good
shape
to
get
this
out
today
and
yeah.
That's
that's
about
all
I
have
for
today.
C
G
Hello,
so
I
am
a
community
support.
This
week,
I
have
the
PR
for
the
Q
builder
I'm,
calling
it
initial
kill
to
build
their
migration.
I
talked
about
this
before
it's
a
huge
PR.
It's
has
a
potential,
it's
not
a
top
priority
for
sure,
but
it
has
potential
to
go.
Stale
real
quickly
could
attach
so
many
parts
of
the
code
and
I
also
did
have
oh
yeah
I
did
a
little
video
showing
like
a
walkthrough
of
the
points
that
I
wanted
people
to
pay
attention,
so
that
might
be
annoying
or
that
might
be
helpful.
C
G
G
I
am
sort
of
switching
so
gold
land
and
I
was
sort
of
mesmerized
with
a
field
thing.
It's
like
I
wanted
to
show
someone
how
I
do
peer
reviews,
because
I
thought
was
really
really
good
did
the
way
obvious
code
also
has
plug-ins
for
you
to
to
do
that,
but
I
thought
woman
was
so
much
better.
So
I
did
a
little
video
if
it's
helpful
and
I
have
lots
of
peer
reviews.
I
neglected
PRS
a
little
bit
last
week,
so
I'm
gonna
get
on
top
of
that
to
you.
G
G
A
G
A
A
D
Hey
good
morning,
everyone
so
we're
looking
to
add
a
better
way
to
kind
of
help.
The
community
provide
responses
to
feature
requests
in
a
backlog
and
a
better
way
to
quantify
those
responses.
So
we've
filed
a
feature,
enhancement
request
against
our
feature:
request
template.
We
are
looking
to
add
an
upload
download
capability
to
our
feature,
request
template
to
allow
everyone
in
the
community
to
vote
for
features
that
they're
really
interested
in
it's
a
favorable
vote,
or
also
indicate
that
this
is
something
that
they're
not
interested
in
by
down
vote.
D
So
it
would
be
kind
of
an
easy
click-through
experience
for
users
and
would
give
us
a
way
to
quickly
quantify.
You
know
what's
most
interesting
to
the
community,
so
you
can
see.
Jonas
is
showing
the
feature
request
that
we
filed
here
and
we're
interested
in
hearing
their
thoughts
about
this.
It's
something
that
we're
looking
to
you
know
implement
and
trial
run
in
the
next
few
weeks
and
we're
looking
forward
to
hearing
from
you
all
on
this.
F
A
Something
like
that
what's
neat
about
this
is
that
you
can
actually
filter
on
issues
and
filter
on
PRS
on
thumbs
up
and
down
thumbs
down.
So
we
can
see
the
ones
that
have
the
most
thumbs
up
the
the
issues
that
have
the
most
thumbs
up,
which
can
then
be
useful
for,
as
definitely
said,
quantifying
which
issues
are
seen
as
important
by
the
community.
C
Yeah
I
have
a
question
on
this
is
Austin.
You
know
the
way
that
this
the
we
have
seen.
Some
of
these
communities
work
very
well
like
is
sytems,
get
uploaded
or
downloaded.
They
need
to
show
up
in
a
dashboard
that
makes
it
easy
for
people
like
you
would
use
mention
earlier
that
filtering
Jonas.
Are
we
gonna
make
that
filter
in
public
for
everybody,
okay,
yeah.
D
So
we
will
make
the
filtering
public
for
everyone
and
basically,
what
we
kind
of
want
to
get
to
is
a
community
pulse
so
every
week
on
the
community
meetings
we
can
provide
that
hope.
We
can
kind
of
go
through
it
and
say:
okay,
you
know
we
have
top
five
issues
top
ten
issues,
things
like
that,
so
we
will
make
that
public
and
we
will
have
some
sort
of
mechanism
each
week
for
highlighting
those
issues
during
the
discussion.
C
Yeah,
but
people
probably
won't
do
that,
so
maybe
you
need
to
put
some
specific
page
in
there
on
our
website.
Awesome:
hey!
You
guys
want
to
know
where
the
millat
mobis
core
visit
this
github
project
board.
If
you
want
to
influence
the
Valera
roadmap
and
you
wanna
see
what
kind
of
things
people
also
want
and
see
if
they
align
with
your
needs,
go
here
and
take
them
to
the
filter
view
cuz,
otherwise,
another
up
you're
gonna
figure
out
to
sort
of
a
thumbs
up
to
see
what
other
people
are.
Looking
for,
yeah.
A
Yeah,
we
we
want
to
make
sure
that
everyone
knows
where
to
go
and
how
to
interact
so
having
this
in
contributing
guide.
Just
as
a
simple
eight,
here's
how
you
vote
on
issues
linked
to
all
these
filters
as
well
and
then
from
the
roadmap
MD.
Have
this
linked
as
well?
Here
are
the
other
issues
that
we'll
take
a
look
at
in
the
roadmap
in
the
future.
Yeah
perfect.
C
A
G
A
C
The
biggest
thing
is
that
you
know
for
the
people
of
a
thumbs
up
who
could
also
ask
them
here.
You
would
need
to
test
it
later
on,
or
are
you
willing
to
come
help
us
contribute
or
values
kisses,
so
there's
a
way
to
call
them
out
so
individually
know
who
the
thumbs
up.
People
are
and
can
go
back
and
track
them
down.
Yeah.
That's.
A
C
C
Here's
my
logs
so
probably
not
for
the
bugs,
but
for
the
feature
request
we
should
probably
add
it
to
the
design
review
templating,
so
I
actually
I'm
it's
under
PR
right
now,
under
the
governance
PR,
so
wait
until
I
go
through
or
just
send
me
the
text
you
want
and
I'll
update
the
PR
and
say
hey
here's
what
you
should
put
at
the
bottom
of
it
there
if
you're,
also
interested
in
this
design
sums
it
up.
For
example,
I.
A
B
C
Just
wanna
mention
that
both
the
governance,
as
well
as
the
the
road
map
PR
out
there
so
folks,
please
go
ahead
and
really
add
comments.
I
know,
Steve
has
added
comments
to
the
road
map.
I
agree
with
95%
of
his
comments.
I
think,
there's
one
that
wasn't
completely
agree,
but
I
remember
now,
which
one
it
was
so
I
I.
Don't
that
you
know
everybody
Coco
read
it.
You
know
we
kind
of
have
a
high
level
analysis
of
what
we
want
to
go
and
how
we
want
to
manage
the
project
moving
forward.
C
So
you
know
I,
think
you
know
now
that
1.4
gonna
be
good
for
us
to
actually
finalize
that
maybe
the
governor's
PR
and
then
within
the
next
few
days
also
finalized
the
roadmap.
So
take
the
next
couple
days.
Add
some
comments.
Let's
just
say
end
of
the
week
to
merge
the
PRS
is
that
a
reasonable
time
frame
four
more
days.
C
F
A
Alright
and
then
I
think
we're
done
for
today,
short
meeting
everyone's
heads
down.
Everyone
is
heads
down
getting
one
point,
four
out
the
door
making
sure
this
happens.
So
thank
you,
everyone
for
for
joining
today
and
yeah,
looking
forward
to
blasting
out
the
news
about
the
new
release
shortly
here,
guys.