►
From YouTube: KubeVirt Community Meeting 2023-08-09
Description
Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/
A
All
right
we're
a
little
bit
late,
so
we'll
jump
straight
into
it.
Welcome
everybody
to
the
9th
of
August,
Qbert
community,
meeting,
I,
hope
you're
all
having
a
wonderful
afternoon
night
or
morning,
Wherever
You
Are,
as
I
said.
If
you
could,
please
add
your
names
in
the
attendees
list
here
and
do
we
have
anyone
any
new
members
who
would
like
to
introduce
themselves
or
people
who
have
been
to
this
meeting
before
and
haven't
introduced
himself
and
I'd
like
to
take
that
opportunity
now.
A
A
So
I
just
said
it
was
the
ninth
book,
so
we
must
have
the
kubernetes
release
very
soon.
What
next
Tuesday
1.28
comes
out?
I
haven't
heard
anything
to
the
contrary.
That's
been
delayed
so
we'll
we'll
take
that
as
gospel.
Nothing
for
us
at
the
moment,
but
Apple
will
be
cut.
Was
that
a
week
later
so
two
weeks
time
we'll
have
1.1
Alpha
cut.
A
And
feel
free
to
jump
in
and
yeah
add
any
context
or
questions.
While
we
go
through
these
things,
if
you've
got
them,
have
a
quick
look
at
the
events,
we've
got
two
talks
at
kubecon
China,
which
I'm
very
excited
about
how
we're
changing
I,
don't
know
how
it's
on
the
line,
but
he's
talking
about
cubot
on
arm
and
he's
also
giving
the
maintenance
talk
about
what
the
Qbert
version
one
release
means
from
an
end
user
perspective.
A
We've
also
got
these
Cube
for
no
kubernetes
Community,
Days,
regionalized
events
in
Sri,
Lanka,
Texas
and
Denmark,
and
the
open
source
Summit
in
Japan,
if
you're
anywhere
near
those
places
for
the
big
dates
put
here.
So
those
are
also
relevant
cfps
and,
as
usual,
if
you're,
aware
of
event
that
you're
interested
in
or
have
submitted
to,
let
me
know
I'll,
add
it
to
the
board
and
I
can
I
can
tell
other
people
about
it.
A
We
have
a
zero
point
agenda,
so
we'll
move
on
to
the
open
floor,
but
as
always,
if
you've
got
anything
that
you
want
to
add
and
remember
at
the
last
minute
by
all
means,
throw
it
on
there
and
before
we
wrap
up,
we
haven't
come
to
it.
Please
shout
out
so
Felix
you've
got
the.
B
Yeah
so
I
just
wanted
to
let
you
know
that
we
just
published
the
ansible
collection
for
keyboard,
so
it
was
published
on
that's
for
Galaxy
and
there's
also
the
the
link
to
the
repository
and
yeah.
Any
any
feedback
would
be
appreciated.
A
For
people
like
me,
let's
pretend
I,
don't
know
anything
about
the
significance
of
this.
What
exactly
does
it
mean
in
40
seconds
or
less.
B
And
40
seconds
or
less
okay,
so
this
collection
contains
two
modules
you
can
use
with
ansible
one
is
for
enumerating
virtual
machines
on
a
cluster.
So
ansible
knows
that
there
are
hosts,
you
can
manage
and
the
other
modules
used
to
manage
the
life
cycle
of
a
VM.
So
you
can
create
a
VM
update
it
and
delete
it.
A
A
Okay,
we'll
move
on
to
the
unnamed
next
Point
next
steps
on
API
reviews,
design
right.
C
That's
me
all
I
I,
just
added
that
last
minute,
I'll
add
my
name
there,
but
I
was
I.
Have
a
design
document
out
that
I'm
hoping
to
get
some
more
engagement,
so
I
thought
I
will
raise
it
as
a
point
here.
So
this
design
doc
talks
about
enhancing
the
reviews
review
process
specifically
for
API
changes.
C
It
discusses
you
know
things
and
lays
down
strategies
for
reviewers
for
new
contributors,
as
well
as
some
automation
or
tooling,
to
help
us
catch
backward.
Breaking
changes.
I
have
actually
done
some
POC
work
as
well,
and
I
was
able
to
catch
a
couple
of
well.
Actually,
I
got
one
breaking
change
in
the
status
field
using
that
POC,
so
yeah.
If
you
scroll
down
to
line
107,
that's
where
the
link
for
the
POC
is
at.
C
So
I
was
just
hoping
for
some
guidance
on
what
the
next
steps
would
be
for
for
this
design
dog
to
move
forward.
A
I
was
hoping
someone
else
would
jump
in
there
and
I'll
give
it
another
few
seconds
to
answer
someone
to
jump
in
there.
A
Very
well,
in
which
case,
let's
have
a
look,
my
presumption
would
be
that
it's
had
some
comments
and
a
pin
some
people
asking
what
they
think
you've
accommodated
all
suggestions.
C
A
Got
up
in
your
review
list,
let's
see
if
those
people
are
on
the
line:
Stu,
Jed,
John
or
Lee,
or
any
of
you
on
the
line.
A
Wonderful
all
right
and
yeah
other
than
that
La
I
think
the
next
thing
will
be
too
yeah,
we'll
just
have
to
ping
the
people
responsible
and
get
it
approved.
A
I
think
it's
a
great
idea,
especially
if
you
haven't
raced
it
already
when,
when
you
created
this
design
proposal.
B
A
A
I'm
not
entirely
sure
where
this
Falls
does
this
speak
to
anyone
in
particular,
that
would
like
to
have
a
look
at
it.
C
Right
I
can
take
a
look
at
it.
This
Falls
right
under
the
umbrella
of
API
review,
so
be
happy
to
take
a
look.
A
A
Well,
as
expected,
the
speed
of
which
this
is
traveling
I'll
come
back
to
that,
let's
jump
onto
something,
that's
actually
loaded
fixing
aggregate
is
covered.
This
is
Super
Fresh,
so
Amazon
about
not
putting
in,
but
we
didn't
actually
have
that
many
things
to
look
at,
because
people
have
been
so
wonderful
about
reviewing
pull
requests
and
bugs
in
general,
so
I
threw
it
in
here.
B
A
I,
don't
know
if
it
goes
to
the
line,
but
an
awesome
description,
but
it
goes
to
fix
and
current
client
conversion.
B
A
A
A
That
was
Chad
right.
Yes,.
A
Thank
you
very
much
that
is,
it
actually
I
think
I
saw
I,
don't
know
if
Lee's
on
the
line
or
Felix.
If
you
can
speak
to
this,
I
did
see
that
he
pinged
the
I.
Think
the
Cuba
Dev
slack
Channel,
asking
for
something
to
be
looked
at.
I
haven't
seen
it
since
then.
Has
he
gotten
the
reviews
that
he
needs
on
that?
Do
you
happen
to
know
it
was
kind
of
a
longwithstanding
PR.
This
head
out.
A
I'll,
just
pull
that
okay,
it's
in
the
CDI
paper.
A
My
boy
doesn't
come
up
here.
I
think
it's
this
one.
C
A
A
Thank
you,
I,
don't
think
we
had
anything
in
the
mailing
list.
I
mean
I
went
through
the
bug,
scrub
and
everything
was
perfect.
Thank
you.
Everyone
taking
care
of
that.
Let's
have
a
quick
little
kid
just
to
make
sure
that
I
haven't
missed
anything.
That's.
A
Oh
yeah
I've
got
a
new
repo,
it's
currently
empty
and
so
I
didn't
see
the
point
in
announcing
it.
But
when
it
has
a
Content
we'll
we'll
make
a
mention
that
we
have
in
Eureka-
and
this
is
coming
from
the
work
done
by
our
Google
summer
of
code-
minty
I-
guess
we
call
them
nitish.
It
was
recently
joined
the
community
and
it
is
about
second
profiles
and,
as
I
understand,
it
builds
onto
the
cube.ci
in
about
a
month's
time.
A
In
the
community
meeting,
we're
going
to
have
nitish
come
in
it'll,
be
after
he's,
wrapped
up
the
Google
form
of
code
and
I'll.
Ask
him
to
give
a
quick
presentation
about
the
work
that
he's
been
doing
and
about
the
Google
summer
of
code
in
general
and
I'd
like
to
think
this
could
be
the
starting
point
for
other
people
to
perhaps
also
bring
in
a
short.
A
You
know,
two
to
ten
minute
demo
conversation
about
the
kind
of
work
that
they
do,
because
I
do
get
the
feeling
that
we
all
kind
of
tend
to
work
on
our
own
little
bits
and
the
broader
Community
only
really
sees
it.
Perhaps
when
it's
done
in
the
release
and
in
the
release
notes
so
I
thought
it
might
be
nice
to
her
for
us
to
when
when
people
are
ready
and
on
their
own
time,
if
maybe
once
a
month,
someone
could
put
their
hand
up
and
say:
hey,
look,
I'm
actually
pretty
excited
about
it.
A
You
don't
actually
have
to
present
anything
if
you're
much
happier
just
putting
like
a
wordless
but
well
intonated
demo
out
recorded,
that's
also
totally
cool.
It's
just
about
kind
of
showing
what
it
is
that
we
do
here,
I
think
is
good
yep.
Nothing
here,
there's
no
bugs
which
brings
us
to
the
end
of
today's
meeting.
A
Excellent
I'm
glad
to
see
that
proposal
is
met
with.
Oh,
it
sounds
like
no,
in
which
case
thank
you,
Edward
for
joining
us.
Thank
you,
everybody
for
looking
at
reviewing
and
taking
care
of
bugs
and
things
like
that,
participating
in
the
conversations
on
the
mailing
list
and
in
slack
for
taking
care
of
the
people
that
need
help.
Thank
you
very
much
have
a
wonderful
day
weekend
and
week
and
we'll
see
you
next
time.
Thank
you
thanks.
So
much.