►
From YouTube: KubeVirt Community Meeting 2023-08-23
Description
Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/
A
All
right,
it
will
get
started
in
just
a
minute.
I
have
put
the
the
meeting
link
into
chat.
Hopefully
it's
there
for
people
to
join
late.
If
you'd,
please
pop
down,
who
you
are
in
the
attendees
just
there,
which
I
haven't
done.
A
And
we
three
minutes
past
the
hour,
so
we
might
as
well
get
started.
Welcome
everybody
to
the
Qbert
community
meeting.
It
is
the
23rd
of
August,
2023.,
I,
hope
you're
all
having
a
nice
morning
afternoon
or
evening,
depending
on
where
you
are
and
as
the
time
that
we
take
the
opportunity
to
welcome
any
new
members
or
people
that
have
attended
the
spending
before
but
haven't
introduced
themselves.
If
you'd
like
to
take
the
opportunity
now,
then
the
floor
is
open
to
you.
A
Alrighty
then
we
shall
continue
on
if
you
they
decided
to
change
your
mind,
then
we're
we'll
still
be
here.
So
let's
have
a
quick
look
at
the
1.1
schedule
and
I'll
also
load
this
one.
A
So
where
are
we
23rd
of
August?
We
must
have
prepared
our
Alpha
cut
and
I
said
Daniel
Hiller
on
the
line
has
has
that
has
that
happened?
Is
the
schedule
correct.
B
A
What
all
right
so
we'll
return
to
the
schedule
in
just
one
moment.
Let's
have
a
quick
look
at
what
the
what
our
events
are.
These
are
all
still
open,
but
they
will
be
closing
soon.
Now
we've
got
kubernetes
Community
Days
in
Sri,
Lanka,
Texas
and
Denmark.
The
cfps
are
still
open.
We
also
have
open
source
Summit
in
Japan
and
down
here.
We
have
two
two
talks
that
are
going
to
be
at
kubecon
China
that
are
presented
by
Howard.
So
thank
you
very
much
Howard.
A
That
is
the
events.
I
just
wanted
to
highlight
this,
isn't
really
it's
looking
important
unless
we
wanted
to
make
it
one
the
six
six
what's
next
meeting
is
having
their
meeting
again
tomorrow.
This
will
be
their
fourth
meeting.
It
is
at
12
o'clock.
Utc
I've
got
a
link
to
the
meeting
notes
here
and
we
just
we
recorded
the
last
one
and
I
learned
that
not
everyone
was
able
to
view
the
recording
it
went
out.
A
So
I've
put
it
up
on
a
YouTube
on
our
YouTube
channel,
so
the
recording
link
is
in
that
in
the
meeting
notes
there
as
far
as
I
know-
and
anyone
can
correct
me
if
I'm
wrong,
but
that's
the
only
one
that
we
that
has
been
recorded.
A
If
we
do
other
recordings,
then
ping
me,
the
links
and
I'll
put
them
on
the
YouTube
channel,
which
segues
nicely
into
yeah
I
had
to
create
a
new
YouTube
playlist
to
catch
these,
and
so
we
now
have
a
home
for
ad
hoc,
temporary,
one-off
or
recurring
meetings
such
as
this,
so
that
we
don't
have
to
worry
about
any
permissions.
We
can
just
put
them
up
there
and
then
we
have
a
record
of
them
so
yeah.
A
If,
if
any
meetings
in
the
future
that
we
do
have,
that
should
be
recorded,
we
can
you
can
ping
the
link
and
I'll
pop
them
up
into
that
playlist,
so
they
can
be
more
more
widely
distributed.
A
B
So
the
thing
is
that
if
I
remember
correctly,
that
we
still
have
some
problems
with
one
test
on
the
second
P
plane
that
is
regarded
to
Essie
Linux,
if
I
remember
correctly,
and
so
we
couldn't
yet
make
the
128
Lanes
required,
which
we
would
want
to
add
for
before
the
processes
being
finalized.
Somehow
so
I
don't
see
lubo
online,
so
I
don't
know
if
you
can
keep
me
honest
and
that
but
yeah.
So
so
that's
that's
what
I
know
for
now.
B
So
yeah
everything
is
from
my
point
of
view
everything
is
on
track.
Besides
the
latest
128
support,
you
can
find
the
same
correctly.
A
B
Oh
one
second
I
just
noticed
that
the
failures
have
been
gone,
so
I
think
we
are
green
and
on
the
compute
for
some
days
now
so
I
think
we
can
start
on
making
them
always
run
today.
I
would
prepare
a
PR
on
that
and,
if
that
always
then
always
going
well,
then
we
can
make
a
required
pretty
soon,
which
is
which
is
great
so
so
for
now.
B
I.
Don't
think
that
we
have
a
big
schedule
problem
for
now.
I
would
just
try
to
create
the
pr
right
away
since
since
I
see
that
the
alpha
zero
should
have
been
yesterday,
but
I
think
that
we
at
least
should
have
of
the
world
28
provider
support
there.
So
actually
I
didn't
see
any
Alpha
email,
so
I
guess
it's
not
yet
branched,
but
yeah
I
would
need
to
check.
A
Okay,
moving
on,
we
have
some
things:
turning
up
the
open
floor
and
I
believe
these
all
belong
to
Howard.
How?
If
you'd
like
to
speak
to
these.
D
Yes,
hi
everyone.
This
is
a
conformance
test
on
arm
64.,
so
we
enabled
it
those
tests,
arms
84.
In
order
to
get
the
official
announcements
that
supports
rm64
from
qbiverse
community.
D
Just
as
Andrew
said,
we
will
have
two
presentations
in
kubikan
Shanghai
in
September,
so
I
really
want
to
get
the
official
announcement
before
the
presentation
and
as
far
as
I
know
they.
The
two
presentation
is
the
first
time
that
we
and
wait
away
how
to
say
way
talk
about
the
QB
words
in
open
source
community
in
China.
So
it's
really
a
good
chance
to
light
more
Chinese
user
to
know
about
QB
words,
yes
and
hopefully,
and
and
maintainer
can
review
those
PR
to
make
the
conformance
test
works
on
I'm,
64.
D
D
C
D
The
issue
not
to
the
pr
this
issue:
oh
yes,
when
we
get
two
issues
when
trying
to
enable
conformance
tests
on
arm
64.,
the
first
one
is
a
c
group
programs
and
I
found
the
test
works
not
well
on
the
bootstrap
image
which
use
podman
rather
than
Docker,
and
when
I
migrate
to
the
bootstrap
Legend
C,
which
is
using
Docker
rather
than
Pokemon.
Those
tests
works.
Well,
so
I
created
two
PR
Cube
build
a
bootstrap
latency
for
arm
64.
D
yeah,
as
you
can
see
in
this
comments,
and
another
issue,
is
that
some
Network
testing
are
using
arephan
touring
virtual
machine
to
do
the
test.
However,
often
the
average
virtual
machine
is
not
cannot
build
on
arm.
The
reason
is
that
the
build
tour
not
works
on
on
and
this
issue
can
not
can
I
cannot
fix
this
issue
in
a
short
period,
so
the
conformance
test
is
partially
enabled
on
m64.
As
you
can
see.
D
In
the
last
comments,
we
have
passed
eight
conformance
test
and
there
are
20
tests
in
the
conformance
in
total,
so
we
skip
to
12
conformance
tests
and
all
those
tests
are
used.
I
think
virtual
machine
to
do
the
test
yeah-
and
this
is
the
status
of
conformance
test
on
arm
64..
A
Wonderful,
does
everyone
have
any
comments
or
questions
for
how
about
any
of
the
issues
raised?
Ops.
A
Alrighty,
in
which
case
I
might
remove
this,
seeing
as
how
you've
captured
it
up
above.
A
Daniel
I
see
that
you're,
adding
something
so
I
might
just
jump
ahead
to
the
pull
request.
To
give
you
time
to
complete
what
you're
writing.
B
No,
it's
fine.
I
was
just
wanting
to
discuss
this
on
a
quick
matter.
I
was
just
sneaking
in
this
one,
since
I
wanted
to
get
feedback,
because
I
think
I
think
we
should
discuss
it
in
this
round,
because
most
of
the
people
would
should
be
familiar
with
how
we
should
construct
that
right.
So
I
guess
at
least
I
would
I
would
want
to
take
a
more
direct
approach
so
that
that
that
we
that
we
know
what
to
build
so
that
people
well,
so
what
people
need
actually
right.
B
So,
just
just
as
a
quick,
quick
heads
up
for
that,
Andrew
and
I
were
discussing
from
from
a
related
issue
that
we
should
somehow
build.
The
kubernetes
support.
Matrix
perversion
of
Qbert
and
so
I
was
proposing
something
like
what
Andrew
shows
here
in
in
the
upper
part,
and
we
discussed
back
and
forth
about
how
we
would
want
to
somehow
somehow
do
this
and
then
I
came
up
with
this
rather
big
Matrix
of
thousands
of
versions
of
which
most
of
those
are
out
of
support
already.
B
And
so
what
would
be
the
best
thing
to
display?
Would
we
just
put
our
focus
on
all
the
latest
versions
that
are
not
yet
end
of
life
or
what
we
want
to
include
the
latest
EOL
version
in
this
example,
for
example,
this
is
the
124
kubernetes,
or
how
should
we?
What
would
be
the
best
thing
that
we
could?
That
could
help
our
users
most,
that
that
is
my
question.
That
I
want
to
want
to
ask
here.
D
Yeah
from
my
point
of
view,
it
would
be
good
to
keep
the
older
version
rather
than
the
only
keeps
the
largest
one,
because
I
get
some
feedback
from
the
some
user
in
China
or
in
the
community.
They
are
using
all
the
version
of
QB
words
rather
than
the
luckiest
one.
D
D
I
will
send
you.
Let
me
check,
because
it's
in
the
some
issue,
page
I
need
some
time
to
check
up.
Okay,
sure.
B
So
so,
if
you
could
chime
in
on
on
the
issue
that
you're
seeing
so
it's
also
added
to
the
to
the
Community
document,
that
will
be
great
yeah
and
thanks.
A
A
That
is
Handy
because,
if
I
would
have
been
into
it,
I
was
going
to
say
that
when
we
talked
about
this
in
regards
to
like
what
we
support
in
the
documentation,
the
general
idea
was
that
yeah
we
should
stick
to
what
we
what
we
do
support.
It
is
good
to
have
what's.
A
What's
the
word
brain
fart,
the
the
slightly
delayed
versions
when,
when
gosh
applicable,
but
in
terms
of
a
support,
Matrix
I
think
it's
even
more
important
that
we
more
or
less
just
declare
what
is
being
supported,
because
this
comes
down
to
the
kinds
of
things
that
get
raised
by
the
rest
of
the
community.
That
is
then
on
the
shoulders
of
the
development
Community
to
help
those
people,
and
so,
if
we
have
a
support,
metrics
that
has
you
know,
0.56
supported
by
version
1.23
well,
I
suspect.
A
Rather
than
continue
to
support
that
I'd
love
to
hear
the
thoughts
of
dissent
on
that.
B
I
think
you're
true
and
when
we
are
looking
at
somehow
what
we
want
to
support
as
a
community.
Somehow
that's
absolutely
true,
but
you
could
look
at
it
from
another
angle
like
asking
for
a
support
metrics
that
tells
people
which
kubernetes
versions
are
supported
by
which
cuplet
version
and
actually
this
letter,
this
big
support,
Matrix,
does
exactly
that.
So
I
forgot
to
to
add
some
context
on
the
on
the
braces
that
I
put
around
the
question
around
the
check
marks
this.
B
Actually,
the
braces
actually
tell
you
which
kubernetes
versions
are
out
of
support,
so
it
should
be
probably
obvious
that,
for
example,
like
o58
is
not
supported
by
the
community
anymore,
but
still
it
would
support
one
for
24,
123
and
122,
so
to
speak.
So
I
can
to
completely
understand
that
this
is
a
lot
to
to
so
this.
This
Matrix
is
pretty
complex
because
it
has
so
many
values.
B
Maybe
we
should
probably
clarify
that
this
Matrix,
for
example,
is
just
the
kubernetes
supported
versions
for
Qbert,
and
our
support
Matrix
would
be
I,
think
the
top
four
rows,
for
example
from
that
Matrix,
and
only
the
top
four
columns.
Something
like
that.
What
you
proposed
in
an
earlier
post
on
that?
What
do
you
think.
A
Yeah
yeah
I'm,
fine
with
that
helping
people,
you
know
who
are
on
say
five
six
and
you
want
to
run
1.23
yeah
I
just
want
to
make
it
yet
highlight
underline
very
clear
that
the
in
parentheses
is
strictly
for
academic
reasons
and
that
the
the
non-parentheses
versions
are
what
the
community
currently
splits,
which
was
I,
would
have
thought
0.58.
A
We
should
support
that
because
it's
a
third
most
recent
version
right.
B
The
thing
is
that
o58
only
supports
the
kubernetes
versions,
124
123
and
122.,
officially
at
least
or
let
let
me
put
it
differently.
What
I'm
looking
at
when
creating
this,
this
Matrix
is
I'm,
looking
actually
at
the
pre-submits
file
of
the
58
version
and
looking
at
which
jobs
are
actually
always
run
and
required.
So
actually,
this
is
how
it
is
currently
in
the
in
the
actual
code
versus
how
we
think
it
should
be.
Probably
does
that.
A
I
think
that's
clear
and
it's
it's
kind
of
useful
to
I
suspect
this
will
also
become
a
lot
easier
once
we
get
1.1
out
and
then
all
of
our
convert
versions
will
be
the
month.
The
three
monthly
Cadence
matching
kubernetes,
whereas
before
that
I
think
it
gets
a
bit
complicated.
B
Yeah
yeah
I
guess
so
too.
This
might
be
because
we
have
stumbled
a
little
bit,
probably
when
introducing
providers
and
didn't
make
it
somehow
or
something
that
that
could
be
the
case.
So.
B
Again,
actually
this
this
tells
us
which
versions
are
actually
which
kubernetes
versions
actually
cupid
is
tested
against.
So
that's
how
it
looks
from
the
CI
state.
A
Yeah
super
valuable:
does
anyone
else
on
the
call
have
any
thoughts,
opinions
or
questions
that
I
would
like
to
chime
in.
A
Well,
thank
you
Daniel
for
first
of
working
on
this,
but
also
for
raising
this
I
think
it's
super
valuable
and
I.
I
totally
agree
that
having
the
like
not
just
automating
it
but
having
against
what
he's
actually
tested
against,
is
far
more
valuable
than
I.
Think
what.
E
A
Moving
along,
we
have
one
pull
request
that
I
noticed
well
two,
because
we've
got
the
one
which
is
actually
Four
from
Howard,
so
I
guess
before
we
go
along
If
people
could
please
take
a
look
at
them
in
your
own
time
and
how
it
please
feel
free
to
add
them
to
our
agenda
next
week
or
to
ping
me
on
slack
and
I'll,
add
whatever
hasn't
been
looked
at
and
we'll
try
and
get
more
eyes
on
them
in
the
four
weeks
that
we
have
left
before,
keep
going
China.
B
A
Okay,
awesome
assistant
using
side
cache
in
base
image
for
those
sidecars
and
move
them
under
command
side
guys.
So
this
was
created
yesterday.
It's
a
relatively
fresh,
don't
have
anyone
looking
into
it
at.
E
A
Moment
is
anyone
able
to
provide
a
review
for
Victor
on
this
one.
C
Hi
I
will
try
okay,
see.
C
A
Alrighty,
that
is,
that
one
taken
care
of
on
the
mailing
list.
The
only
thing
that
we
had
that
hasn't
been
looked
at
is
and
I
I
have
seen
that
this
has
had
a
lot
of
comments
on
it.
I
just
wanted
to
raise
it
as
a
just
a
general.
We
have
a
new
design
proposal.
This
is
for
migrating
videos,
with
local
storage
I
linked
to
the
there's
two
things.
E
A
Think
they
were
here.
Thank
you
very
much
yeah.
So
there's
a
few
links
in
the
email,
so
I've
linked
the
email
they're
both
in
there.
This
highly
relates
to
to
seek
compute
and
Sig
storage.
Their
asset
comes
there.
If
you
haven't
seen
this,
then
now
is
your
chance
to
provide
comment
to
lyche
for
that
design
proposal
and
as
far
as
the
bug
crows
is
concerned,
I
couldn't
see
anything
everything
looked
wonderful,
everything's
either.
Work
in
progress
has
comments,
or
those
beautiful
looks
good
to
me
and
improved
green
tags.
A
So
thank
you,
everyone
for
working
on
them.
That
brings
us
to
the
end
of
what
we
have
on
the
agenda
here.
Does
anyone
have
anything
that
they
would
like
to
slide
in
at
the
last
minute
or
just
popped
into
the
head
right
now.
C
Hey
this
is
Howard
topic
for
a
future
meeting,
I'm
particularly
interested
in
some
sort
of
a
getting
started.
You
know,
step
by
step
by
step
method,
to
take
us
from
point
A
to
point
B,
and
my
objective
is
to
run
kudvert
use
with
VMS
and
I'm
happy
to
raise
my
hand
to
help
on
that.
If
that's
a
gap,
so
just
food
for
thought
do
we
have
us
getting
started.
A
We
have
a
couple
of
things:
probably
I
mean
they're
they're,
relatively
high
level
introductions.
They
aren't
cute,
but
I.
C
Yeah
and
I
don't
want
to
take
the
meeting
sideways
if
you
feel
like
just
posting
them
or
I
can
just
look
at
this.
This
is
fun.
You
can
answer
the
question.
I'll
start
here
and
I'll
bother
you
some
more
later
after
I've
done
some
homework.
A
Absolutely
yeah,
so
we've
got
if
you're
just
interesting
in
a
like.
A
C
A
Awesome
yeah,
if,
if
things
here,
if
yeah,
if
you
definitely
see
holes
by
all
means
ping
means
on
the
slack
Channel,
you.
A
Answers
it.
Thank
you
also.
Next
week,
I
did
forget
to
promote
this
almost
I'm,
doing
that
we're
going
to
have
a
nitish
who's,
been
now
Google's
number
of
code
mentee
and
he's
going
to
come
in
next
week
and
give
a
presentation
on
the
work
he's
been
doing
on
the
generate
second
profiles,
which
now
has
its
own
repo
and
just
in
the
the
Google
summer
of
code
process
in
general.
So
that's
going
to
be
next
week.
Hopefully
everyone
can
make
it
and
we'll
enjoy
it.
A
That's
all
for
today's
meeting.
Thank
you,
everyone
for
attending.
Thank
you
for
pointing
forward
for
bringing
things
in
for
taking
care
of
bugs
piaz
and
whatnot
I
hope
you
have
a
wonderful
rest
of
your
day
weekend
and
we'll
see
you
next
week.
Thank
you
very
much.
Thank
you.
Thank.