►
From YouTube: Velero Community Meeting - June 7, 2022
Description
#velero
A
All
right,
hello,
everyone,
my
name
is
linda
silif
and
I'm
the
community
manager
for
valero
today
is
june,
the
7th
and
that's
official
community
meeting.
So
please
follow
the
code
of
conduct
and
practically
just
behave
and
be
nice
to
the
others.
I've
pasted
it
in
the
chat
and
I'll
paste
it
once
again.
A
The
hack
indeed
link
to
the
meeting
minutes,
and
I'm
gonna
also
share
that
you
give
a
sec
yeah.
Can
you
see
that
I
hope
you
can
see
that.
A
Nice
right
so
please
everyone
who
refuses
like
add
yourself
to
the
attendees
list
and
add
your
topics
at
the
status
updates
and
the
discussion
topics
for
today.
A
So
since
I'm
first
on
the
list,
maybe
I
can
kick
off
break
the
ice.
A
little
bit,
we've
submitted
two
cfps
for
kipcon.
One
is
dual
submission
with
scott
and
the
other
one
is
panel
submission
with
red
hat
dell
and
vuemer
for
discussion,
the
topics
of
backup
and
how
secure
iran
you
are
within.
So
I'll
keep
you
posted
with
this
stuff,
since
I'm
going
to
be
part
again
of
the
review
board.
A
If
I
know
something
I'll
I'll
share
that
and
for
those
of
you
like
that
registered
already
for
kubecon,
please
visit
the
link
to
the
venue
and
travel
and
I'm
saying
that
because
right
now,
they're
still
available
hotel
rooms
with
negotiated
prices
for
for
kubecon,
but
in
these,
which
are
much
lower
than
the
regular
prices
like
150
dollars
or
maybe
more
if
you're
100
sure
that
you're
gonna
attend.
So
you
can
save
some
bucks
yeah
with
that.
I
think
I
can
give
next
one
to
eleanor.
B
Yeah,
so
I
do
have
an
update,
a
personal
update.
I've
decided
to
take
an
opportunity
and
I'll
be
leaving
vmware,
and
so
that
does
also
mean
I'll
be
leaving
the
valero
team.
Thank
you
all
so
so
much.
I
know
it's
very
bittersweet.
For
me.
I'm
excited,
for
you
know
the
new
opportunity,
but
it's
been
such
a
privilege
and
an
honor
to
work
on
the
valero
team
and
to
work
with
all
of
you
to
make
valero
the
project
it
is.
B
I
am
so
so
proud
of
where
valero
is,
and
I
I
look
forward
to
watching
where
it
goes.
So
thank
you
again
feel
free
to
reach
out
and
connect,
especially
on
linkedin,
and
I
hope
to
see
you
all
at
some
point
in
the
future,
wherever
our
paths
may
cross.
A
Once
again,
good
look
at
your
new
adventure,
and
that
was
like
I
don't
like
it
that
you
have
to.
I.
A
B
Not
now
not
for
my
next
role,
but
I
I
very
well,
I
wouldn't
be
surprised
if
I
am
in
the
future.
It
I've
been
amazed
at
how
how
many
more
roles
there
seem
to
be
in
open
source
related
things,
so
I
think
that
that
that
may
happen
in
the
future
cool
all
the
best.
Thank
you.
C
So,
for
my
part,
I
I
already
created
a
pr
and-
and
in
this
pr
we
still
have
a
problem
that
I
do
not
solve
yet.
I
should
only
create
like
a
hack
like
a
workaround
on
it,
which
is
the
the
the
fact
that
when
we
create
a
prototype,
it
will
put
when
I,
when
we
generate
the
the
using
the
proto5
that
we
create,
it
will
generate
the
content
in
a
separate
directory
that
is
not
really
fit
with
the
path.
So
I
have
to.
C
If
you
look
into
the
hack
update,
proto
dot
ss
five,
you
know
I
will
talk
about
that
half
yeah,
so
you
can
see
that
the
line
22,
23
and
24
is
my
workaround
of
the
problem,
because,
after
generating
the
code,
it
will
put
it
in
that
directory,
which
is
not
matching
with
the
directory
that
we
supposed
to
put
it
there.
You
can
see
the
if
they
put
it
in
the
plug-in
packet,
plug-in
generated,
github.com,
vmware,
etc,
etc.
Right
where
it's
supposed
to
put
it
in
the
packet
plug-in
generated
period.
C
That's
it,
but
because
of
that,
so
I
would
put
it
like
a
workaround
for
now
and
I
have
created
another
book
for
that
separate
issue
and
I
think
currently
scots
is
outside
on
that
book.
I
do
not
know
if
he
is
working
on
it
or
not,
so
that
is
just.
E
A
quick
update,
yeah
I
haven't,
had
a
chance
to
look
at
that.
Yet
I'm
hoping
that's
just
a
question
of
you
know:
fixing
the
generation
or
some
kind
of
include
kind
of
directive
thing,
but
I
haven't
had
a
chance
to
look
at
that.
Yet.
C
Yeah
so
anyway,
this
this
this
pr
by
itself,
I
think
it
still
can
still
valid
it.
Can
we
can
steal
a
merchant
and
then,
whenever
we
fix
that
problem,
then
we
can
just
remove
the
line,
23
and
24
and
hopefully
update
this
pro
update
proto.ss5
accordingly,
but
the
rest
of
the
file,
the
rest
of
the
pr
should
still
be
valid
and
you
can
go
ahead
and
review
them.
C
This
one
is
even
though
it
looked
like
a
lot
of
change,
but
most
of
the
chain
is
just
like
a
a
change
of
reference
to
it
like
another
path,
reference
stuff
like
that,
so
it's
not
made
my
major
change.
It's
just
that
I
just
have
to
change
the
the
the
reference
of
the
header
file
in
the
header
in
the
import.
C
If
you're
looking
to
like,
for
example,
this
one,
if
you
go
up
to
the
a
little
bit
a
few
more
at
the
beginning
of
the
file,
you
can
see
that
I
live
50
right
there
at
the
bottom,
like
50
right.
So
I
just
add
that,
and
from
that
on
any
time
we
reference
to
backup
action
item.
I
reference
to
that
import
before
it
was
referenced
to
valero
and
then
now
it's
just
specific
to
that.
So
most
of
the
chain
are
like
that.
It's
very
simple!
C
That's
it!
That's!
That's
all
for
my
update
yeah!
So
now,
if
you
guys
have
any
time,
would
you
please
help
review
it.
A
Anyone
else
any
topics
to
bring
otherwise
I
have
a
question:
if
someone
can
step
in
on
21st
and
and
lead
that
meeting
instead
of
me
I'll,
be
at
the
open
source
summit
at
that
time,
so
not
sure
how
I'll
be
with
the
jet
lag
still
I'll
be
still
dealing
with
the
jet
lag,
so
I'm
not
sure
how
it
will
come
out.
A
B
A
Okay
with
that,
if
you
have
any
topics,
please
add
them
in
advance.
So
people
can
take
a
look
before
the
meeting
and
if
you
have
any
community
related
topics,
please
reach
out
to
me
I'll,
be
happy
to
discuss
them,
for
example,
future
cfps
or
meetups,
or
anything
like
this,
so
I'll
be
around
and
try
to
help
out
as
much
as
I
can.