►
From YouTube: KubeVirt Community Meeting 2023-08-02
Description
Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/
A
Welcome
everyone
to
this
week's
Cube
vert
community
meeting.
It
is
the
2nd
of
August
2023..
We
will
get
started
if
you
haven't
put
your
name
down
already
in
the
attendees.
A
If
you
please
do
that,
and
similarly,
if
you
have
anything
that
you
wish
to
raise,
whether
it
be
something
for
the
agenda
or
pill
request
that
needs
attention
or
Focus
grab
or
really
anything,
please
feel
welcome
to
add
that
while
we
proceed
while
we
get
going
and
then
yeah,
if
we,
if
we,
if
you
add
a
lead,
we
and
we
miss
it,
just
call
it
out.
A
Do
we
have
any
new
members
this
week,
or
perhaps
people
that
have
lurked
before
and
haven't
introduced
themselves?
That
would
like
to
take
that
opportunity
now.
A
Hopefully,
everyone
can
see
my
screen
all
right.
This
is,
of
course,
the
version
1.1
release
all
right,
so
kubernetes
releases
in
approximately
two
weeks.
A
That
must
be
a
Tuesday
all
right,
and
that's
really
all
we
have
here
not
particularly
a
lot
happening
at
the
moment
that
I've
added
this
as
a
regular
kind
of
check-in
as
well
things
that
I
do
try
and
keep
this
events
Wiki
up
to
date.
So
this
is
the
current
cfps
that
we
have
open
case.
It
is
in
Sri,
Lanka,
Texas,
Denmark
and
open
source
Summit
in
Japan.
A
If
any
of
those
places
are
near
and
interesting
to
you
and
just
in
case
I,
do
miss
something
there's
a
lot
of
additional
community
events
in
Linux
foundation,
cncf
and
devops
days
between
link
two
there
at
some
point
either
today,
tomorrow,
Friday
Brian
Carey
has
a
talk
about
Cuba
CI
at
flock,
so
hopefully
that
all
goes
well.
A
So
the
agenda
well
I've
only
got
this,
which
is
sorry,
is
someone
having
delicious
cereal.
A
The
other
thing
we
have
here
is
there
is
a
meeting
tomorrow.
This
is
led
by
Lee
yawwood.
It's
to
talk
about,
what's
happening
with
the
changes
in
how
we
deal
with
cigs
I.
Do
not
remember
what
the
time
is.
A
Uk
time
so
mark
that
in
calendar,
if
you're
interested
in
joining
and
talking
about
yeah
how
we
deal
with
the
changes
to
sigs
and
get
approve
as
an
approvers
and
reviewers
across
the
different
Stakes,
to
help
out
with
PR
workload
and
to
kind
of
knowledge
share,
and
to
make
this
a
bit
more
efficient.
A
Thank
you,
Lee
for
spearheading
that
these
are
the
design
proposals
that
have
come
up
in
the
last
week.
I
think
I'll
just
answer
these
really
quickly.
B
A
A
Come
on
all
right,
a
proposal
for
adding
volume
claim
template
to
VM
spec
from
Shelley
card,
moving
existing
monitoring
code
to
keep
that
monitoring.
A
Yeah,
so
a
little
bit
across
the
board
was
something
for
everyone.
We
had
another
one
for
was
it
memory
hot
plug,
but
it
seems
as
though
there
is
another
one
already
open
for
them.
We
have
to
look
so
I,
think
I
think
they're
dealing
with
the
one
that's
already
open,
who
requests?
A
Right
right,
that's
the
garbage
collection.
This
looks
like
a
nice
easy
one.
If
someone
wants
to
jump
onto
that
and
sign
themselves
to
it,.
A
I
can
have
a
look
nice
one
whose
voice
was
that.
C
A
A
Next
one
well,
my
zoom
window
starts
flashing.
Ending
this
one
is
about
moving.
Oh,
that's
a
design.
Let's
suppose
these.
A
What
a
coincidence,
supposedly
adding
component
and
part
of
label
to
vert
launcher
pods
no
one's
jumped
under
this
one.
A
Doesn't
look
like
it
all
right?
Is
anyone
on
this
call
interested
in
taking
a
look
at
what
seems
to
be
an
easy
review.
A
A
What's
there,
you
are,
let's
do
that.
A
Is
that
something
that
will
be
true
also
in
the
future
that
we
can
just
ignore
anything
that
has
your
name
on
it,
because
you
are
a
master
bugger.
Yes,
all
right,
excellent
after
we've
looked
at
this
PR
did
you
have
anything
to
say
about
the
plug-in
binding
meeting
that
I
think
you
just
had.
B
Yes,
we
just,
we
went
over
the
existing
status
of
things.
What
was
done
and
what
is
planned.
B
I
can
summarize
that
what
we
did
is
many
pocs
to
learn
our
situation
and
what
we
are
doing
is
creating
the
first
binding
plugin,
which
is
slip
with
with
the
hope
that,
after
we
finish
that,
we
can
freeze
that
code
and
have
a
look
at
it
again,
but
that
was
our
first
Target
and
after
that,
we'll
we'll
take
another.
Another
task
that
we
are
doing
now
is
to
do
a
concrete
example
for
srlv,
which
has
some
special
things
that
we
didn't
tackle.
C
B
In
this
context,
I
can
say
that
there
is
a
there
will
be
a
bigger
factoring,
it's
in
progress.
It
is
in
review
on
the
networking
code
that
will
change
the
way
we
configure
networking
in
the
networking
of
the
board.
That
one
is
also
some
pre
requirement
for
the
bindings,
but-
and
it's
also
a
small
cleanup-
not
a
smaller
big,
cleaner.
A
Thank
you
for
that
and
yeah.
If
I've
made
any
mistake
with
those
notes,
can
you
please
correct
them?
Speaking
of
cleaning
up
this
one
raised
by
Vasily.
A
A
Excellent,
thank
you.
Everybody
mailing
list
review
just
one
a
little
self-serving,
but
it's
from
me
just
in
case
you
haven't
seen
it.
This
was
highlighting
recent
updates
to
our
release
information
process.
It
highlights
two
recent
PR's
one
from
Fabian
one
for
myself,
the
long
and
short
of
it.
We
now
have
a
lot
more
release
information
in
first
in
the
release,
duck
and
also
the
release
procedure.
The
release
procedure
Doc,
is
mostly
the
same
from
what
used
to
be
in
the
release.
A
Dock
Middle
East
stock
itself
now
includes
a
lot
of
versioning
life
cycle
and
scheduling,
information
which
you
might
be
interested,
particularly
with
regards
to
what
versions
of
cubvet
are
supported
with
what
versions
of
kubernetes
as
we
go
through
subsequent
releases,
and
this
one
also
has
information
on
release,
notes
and
I'd
like
to
highlight
that
if
you
have
a
a
pi
that
has
a
release,
note
text,
whether
you
raise
it
or,
if
you're
reviewing
it
and
you
notice,
it
doesn't
have
that.
A
If
you'd,
please
include
one
of
the
kind
or
relevant
Sig
labels
to
help
with
processing
those
release,
notes,
thank
you,
and
we
can
Andrea
also
raised
the
point
that
he
raised
previously
about
not
including
the
release
notes
in
the
tag
we
have
noticed.
A
There
is
some
issues
relating
to
that
hearing
my
comment
there
and
it
I
I,
agree
with
him
and
I
think
it's
worthwhile
that
we
should
be
pulling
those
release,
notes
into
a
markdown
file
in
the
Sig
release
repo,
rather
than
pushing
them
into
the
tag,
because
the
tag
is
less
permanent
than
would
like,
depending
on
when
it
is
that
you
pull
those
all
these
notes.
A
Oh
yes,
so
vastly
raised
this
last
week,
I
think
we
had
a
quick
look
at
it.
Alicia
was
the
best
first
look
at
it.
I
just
want
to
rewrite
it
because
he's
sharing
some
findings
that
he
wonders.
If
anyone
else
has
any
days
about
it,
he's
also
raised
Piazza.
Now
this
is
smelling
relevant.
Maybe
he's
got
the
information
that
he
needs,
but
I
did
want
to
bring
it
up
just
in
case
anyone
hadn't
seen
this
and
had
some
ideas
about
it.
So
I'll.
Let
you
look
at
that
in
your
own
time,.
A
And
this
one
similarly
I
think
this
is
from
me
to
mark
yeah.
This
doesn't
have
any
tension
on
it
was
only
raised
yesterday.
That's
something
you
can
surprise
and
there's
a
good
chance
that
any
Maya
will
how
to
pee
out
of
this
I
just
wanted
to
highlight
it,
because
it's
a
beautiful
PR
lots
of
information
and
plenty
of
links,
I,
think
to
behold,
and
just
in
case
that
is
not
the
plan.
A
C
B
A
Well,
yeah:
we
should
support
five
nine
and
five
eight,
while
V1
is
out.
B
A
A
I'm
sure
it's
here,
I'm
not
just
written
here,
someone
could
correct
me
if
I
am
talking
out
of
my
behind,
but
I'm
pretty
sure
we
support
the
current
version
of
the
previous
two.
C
B
B
We
can
check
it
as
a
follow-up.
A
Yeah
well,
just
in
case
is
someone
able
to
assign
themselves
to
this.
B
A
A
All
righty
I'll
just
have
a
quick
look,
no
one's
added
anything
to
the
agenda
so
now
before
we
wrap
up.
If
anyone
has
anything
that
I
would
like
to
add,
not
that's
not
on
the
agenda
and
they
didn't
want
to
add
it
for
a
reason.
Now
is
your
chance
or
if
they
wanted
to
just
say,
thanks
to
anyone
or
recognize
any
good
work,
that's
been
done
or
suggest
any
improvements
that
could
be
done.
How
we
do
things.
A
C
I
think
the
the
latest
change
changes
was
that
we
tied
the
support
for
to
the
kubernetes
support.
So
as
along
the
the
targeted
version
of
kubernetes
exists,
we
support
the
visual
product
keyword
as
well.
Right,
for
example,
release
one
is
targeted
to
127.
So
as
long
as
127
is
existing
and
is
supported,
we
should
support
release
1.0.
A
And
say
anything:
that's
matched
to
version
1.25,
which
I
think
is
version,
5.58
Cube,
yes,
exactly
yeah,
I,
wonder
and
I
think
it's
worthwhile
and
I'd
be
actually
interested
to
see
here
if
other
people
think
otherwise,
if
it's
worthwhile
actually
having
this
as
a
as
a
matrix
that
we
put
out.
That,
unfortunately,
would
have
to
be
updated
manually
with
each
release,
but
just
quite
clearly
says
which
versions
We
currently
support
and
which
versions
of
kubernetes
those
are
matched
against.
A
C
A
A
Alrighty,
well,
that's
the
case.
Thank
you,
everybody
for
joining
us
today.
Thank
you.
Everyone
who
jumped
onto
the
bugs
and
pull
requests
and
had
things
to
add
to
anything.
Hopefully,
your
crispix
with
delicious
mark,
have
a
lovely
day,
have
a
lovely
weekend
and
we'll
see
you
next
time
thanks
everyone.
Thank
you.
Thanks.