►
From YouTube: Velero Community Meeting - Oct 5, 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,
slash
open
discussion
today
is
october
5th
2021,
we
got
a
bunch
of
attendees
and
we
got
a
bunch
of
status
updates,
and
then
I
have
a
discussion
topic
that
I
want
to
talk
to
you
about.
If
you
have
any
other
discussion
topics,
please
feel
free
to
add
those
in
there
per
usual,
we'll
go
through
status
updates.
First,
so
first
up
we
got
valero.
1.7
has
released
fantastic
work.
Everyone
who
wants
to
talk
about
the
1.7
release.
B
Yeah,
I
could
do
that.
I
put
that
point
in
yeah.
I
just
wanted
to
make
sure
that
folks
here
were
aware
that
the
release
had
gone
out
so
so
the
highlights
for
for
this
release
are:
we've
now
switched
to
distroless
images.
B
So,
hopefully,
one
of
the
main
kind
of
driving
factors
behind
that
was
to
try
and
reduce
the
security
vulnerabilities
that
are
generally
are
fined
in
the
images
we're
hoping
now
with
using
this
distrolus,
that's
going
to
be
much
reduced,
so,
hopefully
books
feel
more
confident
in
the
images
that
are
being
used
and
also
as
well.
It
reduces
the
size
of
the
images
quite
a
bit,
which
is
a
nice
benefit
and
then
also
as
well.
B
We
have
a
new
debug
command,
which
is
going
to
hopefully
really
help
help
us
whenever
we're
trying
to
diagnose
valero
issues.
B
Valor
debug
is
a
command
which
will
gather
up
the
valero
resources
so
like
the
pod
logs
and
the
backup
and
restore
resources,
as
well
as
the
the
the
logs
associated
with
those
as
well,
and
create
one
lovely
tarball
which
can
be
sent
to
the
blur
maintainers
to
help
us
diagnose
issues
so
yeah,
then
the
rest
of
that
is
all
other
changes
which
I
won't
go
into,
but
if
you're
interested
feel
free
to
dive
into
those
releases
a
bit
more.
B
So
thank
you
very
much.
Everyone
who
contributed
I
do
like
night
high
github
gives
you
a
little
contributors.
Like
summary,
so
you
can
see
all
the
folks
who
who
had
commits
that
went
into
their
release.
A
Yeah
I
love
this.
I
I
saw
this
is
a
beta
release
that
they
blogged
about
yesterday.
I
think,
but
it's
been
there
for
a
little
while,
but
I
didn't
see
a
blog
post
about
it
until
yesterday.
It's
apparently
part
of
their
new
release
feature
in
github,
where
you
can
get
all
of
these
things,
like
the
all
the
contributions
by
just
clicking
on
a
little
button.
B
Oh
right,
that's
great
yeah,
because
right
now
we're
generating
all
of
this
manually
to
kind
of
go
through
and
look
at
all
the
pr's.
But
if
github's
going
to
do
that
for
us,
that
would
be
amazing.
So
thanks
for
pointing
that
out,
we'll
look
into
that
for
our
next
release.
Yeah.
A
I
think
it
could
be
something
that
we
can
tie
the
the
release
mechanism
into,
especially
for
the
release
notes.
It
pulls
in
a
bunch
of
information.
I
mean
the
highlights
and
everything
has
to
be
written,
of
course,
but
the
like
the
all
changes
here
and
also
they
also
call
out
new
contributors,
so
they
identify
people
who
have
done
their
first
contribution
to
a
project.
Excellent
yep,
great
neat,
I'll
I'll,
add
a
link
to
the
blog
post
here.
So
you
can
check
it
out
later.
A
This
is,
this
is
great.
Does
anyone
have
any
any
questions
or
comments
about
the
1.7
release.
C
All
right
yeah,
so
I
had
community
support
last
week,
did
a
few
things
I
think
bridget's
actually
stuck
with
it
this
week.
So
we
need
to
sync
up
on
that.
I'm
still
working
on
the
item,
snapshotter
working
on
the
restore
paths
right
now
and
I'm
off
at
cubecon
next
week.
So
I
don't
know
who
else
is
physically
attending.
I
put
something
in
the
slide
channel
but
didn't
hear
anything,
but
you
know
my
big
sense
to
schedule
a
time
to
meet
up
there.
A
I
no,
I
will
not
be
attending
kubecon.
The
plan
was
for
me
to
go
to
kubecon,
but
it's
I'm
going
to
raleigh
for
all
things
open
right
the
week
after
and
we
have
a
birthday
party
sandwiched
in
between.
So
I
didn't
want
to
fly
back
and
forth
and
do
a
bunch
of
things.
C
A
If
you
want
to
send
over
a
few
things
where
you
know
you
will
be,
we
can
make
sure
that
those
get
scheduled
both
in
slack
and
on
twitter,
so
people
can
reach
out
that
way.
Okay,
I'm
also
speaking
at.
C
A
It
over
and
I'll
get
everything
scheduled.
Okay
I'll!
Do
that
thanks,
awesome
yeah!
I
I
think
yeah
so
I'll,
be
attending.
Of
course
virtually
and
I.
B
A
B
So
I,
with
one
seven
overnight,
starting
to
look
forward
to
the
1.8
work
that
we're
scheduling,
so
I've
mostly
just
been
starting
some
kind
of
initial
background
work,
particularly
with
the
day
mover
work.
That's
coming
up
for
this
release,
and
I'm
also,
hopefully
gonna
sync
with
fong
this
week
on
the
plug-in
versioning.
He
did
just
ping
and
the
channel
right
before
to
say
that
he
was
gonna,
be
picking
that
work
up
again.
B
So
I
will
sync
up
with
him:
I'm
also
going
to
be
out
for
two
weeks
and
I've
got
some
pto
coming
up.
Unfortunately,
I'm
not
going
to
be
at
kubecon.
I
love
the
idea
of
travel
and
to
see
some
folks,
but
it's
not
an
option
this
year,
so
anyone
who's
attending
help.
You
have
a
lot
of
fun
and
yeah
look
forward
to
next
year.
A
All
right,
so
speaking
of
next
year,
I'm
going
to
dive
into
a
discussion
topic
here
for
kubecon
eu
see
if
peace
will
start
for
kubecon
eu
on
october
25th,
so
we'll
have
kubecon
next
week,
vmworld
right
now
for
those
who
are
attending
vmworld
and
then
kubecon
next
week
and
then
it'll
be
a
week
of
lag
and
then
they'll
start
the
the
cfp
process
there
so
most
likely
they'll
close
that
I'm
guessing
end
of
november,
or
something
like
that.
I
usually
have
it
open
for
like
four
or
five
weeks.
A
So
I
would
love
to
see
a
cfp
here
for
valero.
We've
had
some
some
talks
at
previous
previous
conferences,
so
it
would
be
fantastic
if
we
could
get
some
cfps
in
there
too.
Do
you
have
any
ideas
of
what
we
could
tackle.
C
I
think
we've
got
two
on
my
list
so
far.
One
is
we're
doing
some
work
with
sonoboy
to
actually
verify
health
and
cluster
before
and
after
backup,
and
so
that's
kind
of
an
interesting
convergence
between
the
two
is
to
be
able
to
say:
hey
we're
actually
conforming
with
cluster.
I
know
that's
terribly
interesting,
but
we'll
see
about
that
and
the
other
is
just
to
push
forward
with
like
the
astrolabe
stuff.
As
a
talk.
A
That's
great
and
for
those
who
weren't
here
for
for
last
week's
episode
of
the
community
meeting
astrolabes
a
very
important
project
going
forward.
Please
watch
that
recording
so
yeah.
Those
are
two
really
good
ones
for
sure
any
anything
else.
Anyone
can
think
of.
A
Right,
so
those
are
two
really
good
ones,
though,
definitely
want
to
dig
into
those.
C
Yeah
and
actually
the
other,
the
other
one
that
that's
been
kind
of
floating
around
for
a
while,
is
backup
and
restore
operator
driven
applications
and
the
challenges
and
how
to
fix
things.
We
were
proposing
to
do
that
last
one,
but
I
don't
think
we
put
together
a
very
good
summary.
A
Nice
thinking
scott,
would
you
be
interested
in
doing
a
talk
around
valero
and
and
the
work
you're
doing
with
openshift
or
anything
like
that?
A
Yeah,
that's
possible,
give
it
much
thought
yeah,
but
maybe
something
we
could
think
about.
Okay,.
A
I
think
they'll
they'll
keep
the
the
regular
requirement
that
you,
you
can
submit
two
sessions
with
your
name
on
it,
but
you
can
only
be
approved
for
one:
that's
usually
how
it
goes,
so
it
definitely
works.
Well
if
we
want
to
spread
it
out
a
bit
to
get
more
speakers
in
a
more
more
diverse
speaker
set,
and
also
we
get
a
bigger
chance
of
having
more
toxins.
D
It's
just
quick,
I
I
added
more
stuff
on
the
design,
so
if
you
want
to
take
a
look
and
move
forward
with
the
approval
or
more
feedback
of
design,
it's
really
appreciated.
D
I
think
at
this
point
the
only
missing
not
missing,
but
what
I
wish
you
put
more
details
is
how
I'm
going
to
implement
the
interfaces,
how
to
persist
the
logs
with
in
light
of
dave's
uploading
phase,
but
that's
the
just
implementing
those
interfaces.
That's
pretty
much
and
after
that,
you
guys
can
take
a
look
appreciate.
It
give
feedback
now
work
on
it.
D
If
you
want
to
go
back
all
the
all
to
the
bottom
of
the
file
that
you
see
how
how
we
implement
how
we
load
a
little
bit
up,
that's
how
pretty
much
we
envision
how
to
run
those
plugins
pretty
simple,
but
that's
what
we
got
so
far.
D
Yeah
once
the
design
is
approved,
I'm
more
than
happy
to
to
do
the
implementation
have
a
mock-up
and
probably
gonna,
be
me
or
my
co-worker
chris-
that
has
a
version
already
running,
we'll
work
on
that.
B
Okay,
so
this
first
change
is
from
dan
fung
he's
one
of
the
engineers
who's
helped
working
with
us
on
bolero
in
vmware.
So
she
has
added
this
change
to
our
engine
tests
to
make
sure
that
we're
using
the
correct
versions
of
the
plug-ins
for
different
versions
of
valero.
So
recently
she
does
a
test
to
check
the
upgrade
process,
and
part
of
that
is
making
sure
that
we
need
to
use
the
correct
versions
of
the
plugins
as
well.
So
thank
you
very
much.
B
B
Sorry,
I'm
just
like
reading
this
like
super
quickly
to
like
make
sure.
So
this
is
a
new
value,
that's
been
added,
and
then
this
I'm
guessing
it's
making
sure
that
we
can
use
it
correctly
in
the
helm
chart.
So
thank
you
very
much.
Kevin.
B
Yeah,
this
is
a
dog's
fix
again
from
kevin,
where
our
our
the
docs
for
the
helm
chart
were
incorrect
in
that
the
command
was
specifying
the
chart
name
in
the
wrong
place.
So
this
updates
those
docs
so
that,
if
you
copy
paste
this,
it
will
work
correctly.
So,
thank
you
very
much
for
that
fix.
B
And
then
this
one
is
from
daniel,
and
this
is
for
fixing
there's
a
new
job
in
the
the
helm
chart
which
upgrades
the
crd,
so
this
allows
resource
requests
and
limits
to
be
set
on
the
container,
that's
running
that
upgrade
job
and
the
cleanup
job
as
well.
So
thank
you
very
much
for
that.
A
Thank
you
bridget
all
right,
that's
it
for
today's
meeting.
Thank
you
all
for
joining,
have
a
fantastic
rest
of
the
week
enjoy
cubecon
physically
or
virtually
next
week.
We'll
pause
next
week's
community
meeting
due
to
kubecon,
so
please
enjoy
have
fun
and
we'll
see
you
in
two
weeks.