►
From YouTube: Velero Community Meeting/Open Discussion - July 20, 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
Hello,
everyone
and
welcome
to
the
valero
community
meeting
today
is
july:
20th
2021.,
if
you
have
any
status,
updates
or
anything
that
you
want
to
talk
about.
Please
add
them
in
here,
but
with
that,
let's
start
with
some
status
updates.
B
Hi
everyone.
So
this
morning
I
finished
the
1.6.2
release,
and
so
that
is
not
available.
That
includes
some
security
fixes
that
were
finding
some
of
the
kubernetes
api
libraries.
So
please
upgrade.
I
still
have
a
few
more
follow-up
tasks
to
do.
Following
this
release,
we
need
to
upgrade
the
plugins
to
use
this
new
version
as
well,
and
so
I
started
on
that
last
week
and
then
scott
pointed
out
that
I
would
need
to
do
it
again
once
we
actually
release
162.
B
So
I
will
make
a
start
on
that
today
and
get
that
out
that
won't
take
very
long
other
than
that.
I
so
tomorrow,
I'm
going
to
be
pairing,
my
phone
on
getting
some
of
the
plugin
versioning
work
done.
These
are,
you
may
have
starting
out,
which
is
great
apologies
for
not
being
as
involved
there.
As
I
hoped
I
would
be
able
to
just
a
few
other
things
going
on.
B
So
I
will
so
I'm
looking
forward
to
getting
being
able
to
contribute
to
that
work
and
then
the
other
thing
that
is
kind
of
top
of
mind
for
me
is
we
need
to
get.
I
need
to
review
the
the
pr
from
genting
which
upgrades
the
crvs
to
v1,
so
we
get
that
in
and
then
I
think,
we'll
be
doing
another
patch
really
shortly
once
that's
merged
and
then
that
will
allow
valero
to
work
with
kubernetes
122..
B
A
Awesome,
thank
you,
bridget
any
questions
or
comments
for
bridget
any
questions
or
comments
regarding
the
minor
release
here.
A
All
right,
so
a
quick
update
from
me.
We
had
our
first
community
meeting
in
beijing
in
the
beijing
time
zone
last
week
went
really
well.
We
had
a
lot
of
a
lot
of
really
good
discussions
and
around
different
different
topics.
So
super
super
happy.
Thank
you.
Everyone
who
joined
in
really
happy
to
see
everyone
able
to
to
join
in
during
that
time,
so
yeah
really
really
nice.
A
The
other
thing
that
I
wanted
to
talk
about
today
is
our
new
maintainers.
So
we
last
week
after
the
community
meeting
last
week,
bridget
here
nominated
wang,
kai
yin
and
daniel
young
to
become
maintainers,
and
that
was
approved
and
merged
according
to
our
governance
structure
as
well.
So
thank
you
and
welcome
daniel
and
wankai
to
the
maintainer
team.
Here
in
valero.
B
I
was
just
gonna,
say
yeah,
it's
really
really
great
to
have
them
on
board.
So
I
there
was
pr
from
daniel
he's
put
up
some
work
for
the
blair
debug
work
and
onecast's
been
making
really
great
progress
on
the
et
testing
this
week.
So
I
think
there'll
be
lots
of
fun
things
to
share
from
him
soon.
A
And
on
the
community
meeting
last
week
we
also
introduced
dan
phong,
who
will
be
focusing
on
testing
for
valero.
So
she
will
do
a
lot
of
end-to-end
testing
work
and
making
that
work
even
better
with
within
vlara,
so
really
excited
and
looking
forward
to
that.
A
All
right
does
anyone
have
any
other
status
updates
or
any
questions
any
anything
that
they
would
like
to
bring
up
on
today's
community.
C
I
just
said
a
quick
thing
talking
to
dylan
about
this.
This
earlier
kind
of
relates
to
the
indian
testing.
You
mentioned
one
thing:
I
realized,
you
know
right
now.
We
have
a
few
end
in
testing,
not
a
whole
bunch,
and
you
know
we
have
a
pr
from
one
of
the
people
on
our
in
our
group
to
add
some
indents
a
test
around
namespaces
to
make
sure
annotations
are
included,
and
one
thing
I'm
realizing
is
that
you
know
right
now:
there's
not
a
clear
path
around.
C
C
I
think,
if
we're
not
careful
of
getting
to
the
point
where
the
tests
are
very
disorganized
and
haphazard,
and
it's
really
unclear
how
to
figure
out
what
goes
where,
how
to
add
a
new
test,
we
may
need
to
put
some
thought
around
and
how
to
organize
those
and
how
to
approach.
You
know
adding
new
tests
and
where
they
could
go
and
all
that
so
I
just
figured
I'd
mention
that.
B
Yeah,
that's
a
really
good
point,
scott.
I
think
that's
something
that
we've
been
kind
of
aware
of,
especially
as
well
as
we
want
to
add
more
configuration
options
as
well
to
the
tests,
yeah
and
more
command
line.
Flags
is
going
to
get
very
unwieldy
very
quickly.
I
do
have
some
thoughts
around
that
area,
but
maybe
this
is
something
I'll
bring
it
up
with
some
of
the
the
new
maintainers
who
are
going
to
be
focusing
on
ets.
B
Maybe
we
can
come
up
with
like
a
design
or
something
just
to
like
put.
C
B
To
have
some
documented
guidance
on
on
adding
new
tests,
but
that's
really.
C
I'd
actually
commented
on
one
of
the
pr's
I
reviewed
about
this.
You
know
I
don't
want
this
to
inhibit,
adding
things
now,
because
there
aren't
that
many
tests.
So
you
know
it's
fine
to
just
add
things
now,
but
when
we
do
put
those
guidelines
in
place,
we
may
want
to
shuffle
tests
around.
At
that
point
I
mean
getting
to
the
point
where
it's
disorganized
and
it's
hard
to
find
things
in
one
sense
is
good.
It
means
we
have
more
tests,
but
then
we
need
to
actually
fix
that
and
you
know
get
that
in
place.
B
Okay
I'll
take
that
next
time
and
then
to
bring
that
to
the
the
other
team
members.
And
hopefully
we
chat
about
the
next
community
meeting.
C
A
All
right,
then,
we're
going
to
dive
into
shout
outs.
We
got
one
shout
out
here.
This
is
for
jacebosh
devmain,
who
did
a
x
for
the
installed
valera
flag
for
the
end-to-end
tests,
so
this
is
great.
Thank
you.
So
much
jay
really
really
appreciate
it.
A
So
with
that
short
meeting
today,
thank
you.
Everyone
for
joining
have
a
fantastic
rest
of
the
week.
Everyone
and
see
y'all
on
slack.