►
From YouTube: Velero Community Meeting - Jan 11, 2022
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
january,
11th
2022,
please
add
yourself
to
the
attendees
list.
If
you
haven't
done
so
already,
if
you
have
any
status
updates
on
things
that
you're
working
on,
please
add
them
to
the
status
updates
and
if
you
have
any
discussion
topics,
please
add
them
to
the
discussion
topics
as
well,
and
with
that,
let's
dive
into
some
status
updates
dave
you're
up
first.
B
There's
the
button
yeah,
so
I
was
out
for
the
last
couple
weeks
on
pto.
One
thing
I
have
been
working
on
is
grpc
hashicorp,
plugins
and
astrolabe,
so
that
we
can
have
different
types
of
plugins
without
having
to
link
everything
together.
So
I'm
putting
together
a
pr
for
astrolabe
for
that.
B
No
I'll
put
a
design
dock
into
the
astrolabe
repo
with
it.
C
Yeah
I've
been
doing
some
tests
post
version,
1.8
fc.
We
have
seen.
C
Before
christmas
last
year
and
currently
preparing
for
the
rc,
we
there
are
a
couple
of
bugs
remained
so
currently
we
are
not
merging
any
prs
to
the
main
branch,
hopefully
within
the
next
few
days,
we'll
tag
an
rc
card
branch
and
after
that
we'll
start,
you
know
merging
the
pr
to
the
main
branch.
So
if
you
have
some
pr
that
requires
attention,
please
ping
us
on
the
slack
channel
and
we'll
handle
that
with
priority
after
dlc.
C
D
Yeah,
my
stature
is
almost
same
with
daniel
I'm
doing
some
manual
testing
one
eight
and.
D
Two
and
to
fix
some
bugs
from
during
testing
yeah.
A
E
Yeah,
it's
more
of
a
heads
up
and
advertisement.
I
at
the
end
of
last
year
started.
I
finally
feel,
like
I
know,
monopoly
to
start
really
answering
questions
on
the
kubernetes
slack.
Obviously,
some
are
still
too
technical
for
me,
but
you'll,
I'm
starting
with
this,
because
I've
started
to
see
some
more
product
questions
that
I
either
knew
the
answer
to
and
then
realized.
The
answer
wasn't
in
the
docs,
because
I
wanted
to
link
the
right.
Docs
page
or
I
just
didn't,
know
the
answer
and
I
couldn't
find
it
in
the
docs.
E
So
I
started
thinking
more
about
docs.
I
talked
to
abby
our
doc,
our
part-time
doc
writer.
So
she
and
I
are
gonna
kind
of
do
a
work
on
the
docs
in
the
new
year.
Partly
we're
just
gonna,
hopefully
get
more
information
in.
I
did
notice
that
some
of
the
organization
confused
me
of
the
docs.
I
think
that
we've
been
adding
for
so
long.
We
haven't
like
kind
of
taken
a
bigger
picture,
look
at
the
doc,
so,
for
instance,
like
restore,
I
was
trying
to
figure
out.
E
Where
does
it
say
that
the
that,
when
we
restore
we're
non-destructive-
and
I
couldn't
find
it-
and
there
were
like
four
play-
sections
that
talked
about
restore
and
they're,
not
even
in
the
same
place,
no
criticism,
let's
be
very
clear,
like
we
have
pretty
good
docs,
I
think
for
our
project.
But
I
also
think
that
now
that
I
am
dog
fooding
it
as
people
say
now
that
I'm
using
our
own
docs
myself
as
I
try
to
learn
I'm
having
trouble.
So
I'm.
E
Basically,
I'm
advertising
that
we
may
do
a
little
bit
of
reorganization,
the
docs,
nothing
too
big.
We
don't
want
to
do
too
much
unless
we
hear
users
needed
as
well,
but
certainly
we
will
make
changes
based
on
what
I
feel
like
I
need
as
a
basic
user,
so
the
advert
so
a
that's
an
fyi,
but
really
if
anyone
else
is
interested
in
docs,
big
or
small.
E
If
you
want
to
find
an
easy
way
to
make
contributions,
I'm
going
to
be
starting
to
make
a
lot
of
like
docs
prs,
where
it's
like
put
this
information
in
and
then
as
long
as
you
know
how
to
use
git,
you
can
make
that
happen,
but
if
you
also
care
about
table
of
contents,
just
anything
please
be
in
touch.
So
hopefully
everyone
will
see
improvements,
and
if
anyone
wants
to
participate,
we'd
love
to
have
your
participation.
A
Fantastic,
so
I
I
definitely
want
to
blast
that
out
as
well
on
both
social
media.
Our
mailing
list,
I
think,
would
be
a
good
one
to
to
target
for
this
too
yeah
and
on
slack,
of
course,
just
to
get
people's
eyes
on
it.
So
when
you
have
created
those
issues,
we
can
just
sync
up
you
and
I
and
we'll
we'll,
send
out
to
send
things
out
well,.
E
Declare,
and
by
the
way,
of
course,
I
didn't
say
this,
but
of
course
I
would
love
just
feedback
too,
if
someone's
like.
I
really
this
page,
I
really
struggle
with.
Like
dave,
I
think,
pointed
out.
The
cluster
migration
is
a
pretty
short
page
and
clearly
there's
so
many
questions,
so
we'll
increase
that
page
now
in
terms
of
the
issues
I've
been
so
far,
I've
created
one
single
small
issue
for
a
bit
of
information.
That
was
missing.
Do
you
mean
those
are
going
to
be
created?
E
As
I
answer
kubernetes
slack
questions,
so
those
are
incremental
abby
and
I
will
probably
create
some
bigger
doc
stories
in
the
next
few
weeks.
Is
that
is
that
what
you're
talking
about
that?
I
should
let
you
know.
Okay,
sounds
good.
A
Great
the
bigger
themes,
and
then
we
can
point
people
to
them.
So
one
thing
that
we've
seen
is
that
when
you
have
smaller
issues
that
are
very
specific,
it's
much
easier
for
someone
to
take
that
issue
on
and
then
just
fix
it
when
it
comes
to
docs
and
that's
general
as
well,
but
so
yeah.
A
If
you
have
the
larger
themes
and
then
we
can
break
it
out
into
small
bite-sized
chunks
like
hey,
we
need
someone
to
fix
these
10
lines
here,
just
fix
them
up
or
fix
the
table
of
contents
for
version
1.8
right
version
1.6,
because
that
is
broken
now
or
something
like
that.
Even
though
yes,
it
would
take
you
five
minutes
to
fix
it,
make
an
issue.
So
someone
else
can
do
well.
E
F
E
A
Yeah
I
can,
I
can
send
out
some
some
of
the
the
issues
that
we
created
for
contouring
when
we
launched
the
working
group
there
that.
A
Yeah,
so
you
can
see
just
how
we
formulated
things,
it's
just
very
basic,
but
it's
like
just
small
chunks.
Here's
what
we
need
help
with
absolutely.
F
A
Then
it's
easier
to
attract
new
folks.
We
can
also,
I
can
work
with
abby
on
this
and
we
can
send
it
out
to
the
write
the
docs
slack
as
well.
Oh.
A
There
there
there's
a
bunch
of
things
that
we
can
do,
especially
for
docs,
and
it's
something
that
I
definitely
wanted
so
or
I'll.
Try
not,
but.
F
A
Contributor
shoutouts,
since
we
had
the
the
fc
there
I
don't
as
daniel
was
talking
about.
We
don't
have
a
lot
of
a
lot
of
new
new
merged
things.
We
do
have
one.
So
let
me
just
share
this.
A
A
A
C
C
So,
if
you
have
any
anything,
I
wanna
you
think
it's
important,
please
reach
out
to
us
via
slack
or
open
issues.
So
we
can,
you
know,
prioritize
them
during
the
planning.
E
Thank
you
so
much
daniel.
I
think
that
was
daniel
yeah.
I
I
should
have
thought
to
mention
that,
yes,
and
not
only
that
but
we've
kind
of
in
the
past,
we've
had
our
roadmap
as
an
end
like
a
part
of
the
repo,
so
kind
of
it's
been
put
more
in
a
final
version
for
one
nine
I'm
going
to
be
using
the
wiki,
which
you
should
be
able
to
see.
E
Now,
if
you
look
at
the
top
the
wiki's
there
so
in
a
week
or
two
we're
going
to
start
to
have
a
list
of
what
we're
thinking
with
prioritization
and
you
may
see
it
changing
I'll,
try
to
label
whether
it's
still
in
progress
or
whether,
like
it's
pretty
settled
so
as
daniel
said,
like
feel
free
to
ping
me
on
slack
or
ping.
Anyone
on
slack
or
open
an
issue
and
you'll
start
to
see.
You
can
check
the
wiki
to
see
updates
on
one
night
planning
and
I'll
try
to
update
here
as
well.
A
Hello,
nor
do
you
want
to
send
out
a
survey
to
capture
more
more
feedback
from
our
users,
for
docs
are.
E
Yes,
we
could
do
that.
Have
we
actually,
I
do
have
a
question.
I
have
a
question.
If
you
don't
mind
the
mailing
list,
I've
noticed
that
every
so
often
people
submit
it
seems
like
the
mailing
list.
A
So
when
we've
sent
out
surveys
in
the
past,
yes,
we've
gotten
a
lot
of
responses.
So
the
the
last
survey
we
did
got
like
40
responses
or
something
like
that
which
was
really
good.
We
we
didn't
expect
that
many,
so
it
was
really
good,
so
yeah
I'm.
A
I
would
be
happy
to
just
build
up
a
quick
survey
with
you
too,
so
we
can
send
that
out
because
then
we'll
send
that
out
through
the
mailing
list,
we'll
send
it
out
on
twitter,
we'll
send
it
out
on
slack
and
have
people
respond
there
and
yeah
you're
requesting
for
the
mailing
list.
A
It
was
initially
created
just
for
meeting,
invites
and
a
place
for
users
to
ask
questions
not
necessarily
for
support,
but
I
mean
that's
questions
as
well,
so
it's
natural
that
you
will
have
support
questions
pop
up
on
the
mailing
list,
but
then
you
can,
you
can
start
there
and
then
you
can
say
depending
on
what
kind
of
support
question
it
is.
We
can
say:
hey,
please
open
up
an
issue
on
github
or
talk
to
us
on
slack
or
come
to
the
community
meeting
or
the
office
hours
we'll
discuss.
E
A
All
right
awesome
so
with
that,
if
we
don't
have
anything
else,
thank
you.
Everyone
for
joining
have
a
fantastic
rest
of
the
week
and
see
you
all
next
week,
thanks
see
ya.