►
From YouTube: KubeVirt Community Meeting 2022-09-21
Description
Meeting Notes: https://docs.google.com/document/d/1kyhpWlEPzZtQJSjJlAqhPcn3t0Mt_o0amhpuNPGs1Ls/
A
We're
gonna
re-share
the
document
link
for
the
new
people
that
joined
if
everyone
can
go
ahead
and
jump
into
the
dock
and
log
their
attendance.
Whether
you're
in
please
feel
free
to
add
anything
that
is
top
of
mind
for
you
to
the
agenda
agenda,
notes,
open
floor
or
any
PRS
or
bugs
that
need
called
out
for
special
attention
today
and,
of
course,
anything
that
might
benefit
from
some
extra
discussion
in
the
mailing
list.
A
A
B
Hey
yeah
this
so
This
merged
I
want
what
I
just
wanted
to
do
was
to
if
we,
if
we
have
everyone,
we
have
a
few
folks
I
wanted
to
see.
B
If
we
could
have
a
discussion
on
this
because
just
to
walk
through,
what's
expected
from
the
timeline,
so
I
don't
know
it's
Daniel
here
or
do
you
have
so
I
I,
don't
know
if
we
have
everyone,
but
that's
okay,
if
we
don't
what
I
just
wanted
to
raise
at
the
very
least
was
you
know
what
what
this
means,
what
this
change
means,
and
so
very
simply
the
you
know
everyone's
familiar
with
the
current
we'll
leave
schedule
for
Qbert
is
monthly,
and
so
the
the
change
in
this
proposal
means
that
it's
going
to
Hubert's
gonna
follow
the
kubernetes
release
schedule.
B
So
this
is
going
to
be
three
times
a
year,
and
so
this
can
operate
on
a
15-week
cycle
where
we
go
through
this
15-week
cycle
and
we
have
a
bunch
of
checkpoints
along
the
way
and
then
eventually
we
release
and
and
the
15-week
cycle
is
basically
designed
to
follow
the
same
thing
that
kubernetes
is
doing,
but
it's
also
meant
to
Trail
kubernetes,
and
so
that's
what
I'm
trying
to
show
in
this
diagram
here
is.
You
can
see
that
you
know,
as
part
of
as
part
of
the
this
discussion
that
kubernetes
is
going
to
be.
B
You
know
like
it's
one,
two,
six,
for
example
as
week
34
in
the
year
the
kubernetes
starts.
B
It's
one
two
six
cycle,
that's
sort
of
it's
week,
one
of
its
15
week,
release
cycle,
and
then,
as
part
of
that,
you
know
that's
when
right
around,
where
kubert
would
want
to
start
its
release
cycle
for
the
the
next
upcoming
release
and
then
the
conclusion
for
kubernetes
126
would
be
so
near
the
end
of
the
year,
which
is
in
December
December
5th,
which
is
the
week
the
last
week
of
their
cycle,
and
then
qbert's
release
would
follow
that
with
within
a
few
weeks.
B
So
basically,
so
the
takeaway
is
that
a
three
releases
a
year
and
the
thing
I
did
want
to
discuss
is
like
if
we
had.
If
we
had
the
right
focuses,
you
know
how
we
should
Target
this
or
sort
of.
When
should
we
start
doing
this
and
this
even
though
this
change
has
emerged,
should
we
target
the
next
release,
which
I
think
is
one?
It
might
not
be
zero
five
seven,
it
might
be
zero
five
eight.
B
Should
we
target
it
toward
this
toward
this
to
this
date.
So
it's
really
a
question
of
okay.
Do
we
have
the
infrastructure
in
place
to
to
do
this,
and
you
know
any
steps
that
we
are
missing
to
you
know
if
we
can
enumerate
any
subsurmacy
to
actually
to
do
this
so
I,
it
was
really
an
old
sort
of
an
open
question
or
discussion.
If
we,
you
know,
what's
the,
what
are
the
next
steps
to
really
start
executing
on
this
plan?.
B
So
I
don't
know
if
we
have
everyone
here,
I,
don't
know
if
Daniel's
here
or
if
we
have
others
that
want
to
comment.
Do
people
think
that
makes
sense
like.
B
Should
we
look
at
doing
the
next
so
the
next
so
we're
December,
21st
so
I
guess
the
assumption
is
that
there
would
be
a
release
at
the
end
of
the
month
here
with
probably
the
125
release,
I
think
that's
what's
going
to
correspond
to
should
the
next
release
be
following
so
no
releases
until
we
do
till
one
two
six
would
be
the
change,
but
if
we
don't
do
this,
it
would
be
we
wait
till
next
year
we
wait
till
127
to
start
our
cycle.
B
A
B
Sure
yeah
I
it's
in
the
release,
note
since
it
just
merged,
and
so
what
else?
What
I
want
to
do
is
to
you
know,
follow
up
I,
want
to
go
to
this
meeting
and
then
follow
up
on
the
mailing
list
as
well.
But
what
I
and
very
least
want
to
make
sure
is
that
you
know
not
only
do
people
understand
this
change.
I
also
want
to
make
sure
that
you
know
we're
prepared
to
execute
on
at
night.
B
I
have
a
feeling
that,
like
we,
since
we're
already
releasing
monthly
I
mean
it
seems
like
we
would
be,
but
I
just
want
to
make
sure
that
you
know
if
there
is
any
opinion
as
okay,
we
need
to
change
something
before
we
suddenly
do
this.
C
C
That's
going
out
we'll
have
you
know
three
to
four
times
that
and
is
there
a
way
we
can
better
categorize
those
release,
notes
in
GitHub
so
that
we
can,
when
it
comes
to
automating
those
release,
notes
they
already
get
filtered
into
distinguishable
categories.
C
B
Yeah,
it's
a
good
question,
so
these
are
the
kind
of
things
that
I
I
definitely
want
to
raise.
It's
like
you
know
what
are
other
things
like
with
the
the
this
change.
That's
going
to
affect
a
bunch
of
things.
So
do
we
need
to
make
sure
our
tooling's
in
place
to
make
sure
that
this
is
going
to
be
best
for
the
end
user,
so
yeah
I
mean
this
would
be
one
of
them,
so
I
guess
I
mean
I,
don't
know
I
mean
I.
B
B
Okay,
well,
I
can
make
a
note
of
that
Andrew
and
we
can
maybe
that's
something
that
sort
of
is
an
argument
of
okay.
Let's
you
know,
let's
work
on
building
this
before
we
do
before
we
kind
of
sort
of
commit
to
this
release,
and
we
do
have
time,
but
I
mean
it's
just
something
that
the
very
least
we
should
consider.
C
The
well
the
release,
notes,
I
I,
wouldn't
call
the
release,
notes
a
blocker
for
moving
to
the
release
schedule
now,
because
just
because
they
don't
have
something
in
place
now
doesn't
mean,
like
it'd,
be
a
one-off
manual
cost.
While
we
put
into
place
for
this
December
release
from
0.57,
you
know
it's
six
to
release
notes,
it
would
be
fun,
but
it
also
wouldn't
be.
Like
a
you
know,
the
end
of
the
world.
You
know
what
I
mean
yeah.
B
C
Yeah,
that's
it
one
thing
that
we've
been
asked
as
well.
Just
to
help
with
the
messaging
of
this
I
guess
is:
do
you
have
the
bandwidth
to
write
a
short
blog
post
about
this?
We
can
put
it
on.
B
Yeah
I
can
write
a
podcast
for
this
I
I
want
to
so
I'm
gonna
write
an
email
about
it,
just
with
the
description
of
like
kind
of
why,
just
because
in
case
people
didn't
read
the
description
in
the
pr
just
to
have
it
on
the
mailing
list
and
that's
fine
I
can
put
it
in
a
blog
post
as
well.
So
in
terms
of
like
you
know
like
so
in
terms
of
getting
this
out
there
like
we're
in
September.
B
B
So
let's
say
I
do
a
blog
post.
We
have
the
mailing
list
thread.
You
know.
Is
that
enough
to
say
like
okay,
we're
going
to
make
this
change
now?
B
You
know
I
I'm,
just
I
want
I'm
wondering
I
want
to
hear
some
dissent
to
like
someone's
saying.
No,
we
can't
do
this
now,
like
I,
want
to
hear
some
reasons.
Why?
Otherwise,
to
me
it's
like.
If
I
don't
hear
anything,
then
it's
like
well,
then
I
I
prefer.
Then
we
should
just
go
for
it.
I
think
it's
fine,
but
I'm
not
hearing
anything.
D
Hey
Ryan
Brian
here
yeah
we're
talking
about
this
earlier
on
the
week
and
there's
a
bit
of
a
lead
time
when
delivering
the
kubert
CI
providers.
So
at
the
moment
we
don't
have
a
provider,
that's
testing
the
125
version
of
kubernetes,
okay.
So
there's
just
that
little
bit
of
lead
time
there
that
we
need
to
kind
of
shorten
that
lead
time
so
we're
looking
at
maybe
delivering
providers
with
release
candidates
of
kubernetes
versions
so
that
we
have
a
provider
ready
in
time
to
test
Cube
vert
against
the
latest
version
of
kubernetes.
B
Okay,
so
the
release
of
125
was
around
end
of
August,
okay,
so
like
I,
and
so
my
estimates
were
like
that
this
could
take.
You
know,
like
you,
know,
a
bound
right
like
four
weeks
or
so
like
it
could
take
a
little
bit
before
we
have
a
provider
so
like
I.
Have
that
so
I
have
that
kind
of
in
the
estimates
like
it'll
take
a
little
while,
like
we're
I
kind
of
have
a
range
of
like
a
certain
amount
of
time
that
we
expect
that
before
we
do
release
yeah.
So
that's
that's
fine!.
D
D
B
For
this,
yes,
so
for
this
one
I
would
say:
I,
don't
I,
don't
think
we
should
do
the
I,
don't
think
we
should
sort
of
do
start
like
what
I'm
saying
is
like
we
wouldn't
start
our
Cadence
or
we
wouldn't
start
our
the
next
release,
which
is
the
one
that
I'm
saying
it
would
be
in
December.
We
would
start
working
toward
that
one
today,
so
we
would
continue
with
the
current
release
process,
which
would
be
the
end
of
the
month
for
for
just
for
for
September
and
then
starting
in
October.
B
B
That
makes
sense
so
like
we
didn't,
we
wouldn't
so,
like
the
same
the
silica,
let
me
ask
this:
in
the
the
current
release
for
the
next
release
of
Qbert
is
going
to
be
end
of
September
right
and
that
would
be
targeting
kubernetes
one.
Two
five
right,
that'd
be
one
of
the
support,
supported
kubernetes
versions.
D
Yes,
hopefully,
hopefully,
we'll
have
a
provider
in
time.
Okay,
there
should
work
on
going
on
the
provider.
So
it's
not
not
available
yet.
B
Okay,
so
the
so
what
I'm
saying
is
the
this
release
would
be
the
same
as
normal
and
then
the
next
one
is
going
to
be
is:
where
is
is
where
we?
You
know
we
do
the
next
release
in
December,
so
that
would
be
the
that'd,
be
the
change
so
I.
What
I'm
saying
is
nothing.
Nothing
needs
to
change
now
or
this
month.
C
B
C
B
Yeah,
so
this
one's
always
shorter
because
of
the
holiday
it's
in
December,
so
this
one's
always
a
little
bit
tricky
so
and
also
taking
into
account
too
that,
like
you,
know,
kubernetes
targets
early
December
same
because
they
you
know
the
opportunity
of
it
slipping
so
that
they
can
try
and
squeeze
it
in
before
the
for
the
holiday
so
take.
This
is
fully
taking
into
account
that
potentially
them
slipping
and
then
us
you
know
having
to
be
in
the
middle
of
the
holiday
and
then
pushing
all
the
way
you
know
until
December.
B
B
So
I
so
Brian
in
terms
of
this
provider,
so
so
okay,
like
at
least
from
my
expectations
to
kind
of
get
back
to
that
point.
It's
like
I
expect
there
to
be
a
range
of
time,
not
only
because
I
of
kubernetes
releases
being
delayed
but
I
understand,
there's
a
lot
of
work
that
goes
into
the
provider
and
getting
it
to
work.
So
it's
gonna,
be
you
know
whatever?
Whenever
that
release
is
available,
you
know
that
begins
our
you
know
our
our
work
towards
you
know.
B
We
have
our
release
candidate
that
we
would
have.
You
know
right
around
the
time
or
right
right
a
little
before
the
Caribbean
is
released
right
around
it
and
then,
whenever
the
kubernetes
is
released,
you
know
we
we
do
exactly
what
we
do
today.
We
work
on
it
or
at
least
a
release
provider
and
then
and
then
it's
sort
of
the
same
method.
B
After
that,
it's
a
you
know
it's
about,
I,
think
it's
a
when
we
said
it's
the
week
a
week
of
everything
passing
in
CI,
no
bugs
no
major
changes
and
then
a
release.
D
Foreign
yeah
that
sounds
good
and
we're
looking
to
kind
of
speed
up
the
provider
provisioning,
the
provider
for
for
keyboard
CI
by
testing
with
against
release
candidates
for
kubernetes,
so
graphs,
so
that
we
can
kind
of
get
any
issues
out
early
and
hopefully
have
the
provider
a
bit
quicker.
Then.
B
Okay,
okay,
great
okay,
I
mean
how
so
any
other
thoughts
like
you
know
any
of
the
concerns
like
I'm,
not
so
like
December
like
December,
January
timeline.
So
out
so
we'll
say.
The
next
release
of
cubert
is
beginning
of
October,
October,
1st
and
then
that'll
be
the
last
one
on
the
monthly
Cadence.
B
The
one
following
that
is
going
to
be
switching
to
this
four-month
Cadence
this
15-week
Cadence,
and
that
release
would
be
following
kubernetes
one,
two,
six,
so
roughly
December
to
January
tampering.
C
B
All
right
so
I
don't
hear
any
major
descent,
so
I
think
that
I
think,
like
I,
think
that's
fine,
let's,
let's
March
toward
that
that
goal
I'll
I'll,
spread
it
across
the
mailing
list
and
blog
posts
to
get
the
word
out
to
everyone.
What
the
plan
is.
A
All
right,
then,
okay,
Andrew,
do
you
want
to
jump
into
the
Oktoberfest
item.
E
C
Yeah
so
earlier
this
week,
I
sent
out
an
email
primarily
targeted
at
the
different
repo
reviewers
maintainers
about
the
what
what
we
would
need
to
do
in
order
to
make
and
to
opt
in
any
of
our
repos
back
top
of
that.
C
So
I
presume
everyone
knows,
but
if
you
don't
have
to
invest,
there's
an
initiative
run
primarily
but
I,
think
by
digital
ocean
and
they
celebrate
and
reward
people
contributing
to
open
source
projects,
and
so
it's
an
opportunity
to
get
a
bunch
of
eager
people
who
I
haven't
necessarily
contributed
to
Cuba
before
contributing
on
generally
the
lower
hanging
fruit,
so
I
suggested
the
user
guide
as
a
good
example
of
that
and
I
think
we've
got
some
I
think
channels
on
the
line.
C
I
think
we
have
some
good
potential
issues
as
well
to
help
out
with
the
website.
C
So
I
don't
have
any
confirmation
yet
about
any
of
those
repos
opting
in
we
are
setting
up
the
labeling
infrastructure
of
rather
Daniel
is
setting
up
their
labeling
infrastructure
to
make
it
all
happen
once
you
know
once
in
the
maintain
as
many
rebirth,
so
yep,
let's,
let's
do
it-
I've
got
some
issues
here
if
that
goes
ahead,
I'm
just
kind
of
like
preparing
you
all
now
that
it
would
be
really
great
if
we
could
have
some
volunteers
to
help
triage
some
of
the
issues.
C
C
If
they're
not
then
write
a
a
contained
and
concise
issue
to
support
it
and
then
tagging
it
with
the
ACT
over
first
label,
all
going
through
the
considerable
amount
of
issues
in
Cuba,
Cuba
and
then
kind
of
like
triaging
ones,
that
would
be
appropriate
for
for
new
users
and
self-contained
and
well
described
so
I'm
just
going
to
put
them
out
there
now,
and
that
was
it.
Thank
you.
A
Year
next
week's
Cooper
community
meeting
I
will
be
in
San
Francisco
for
a
work
event.
So
hopefully
someone
on
this
call
is
interested
and
willing
and
filling
in
for
me.
Otherwise,
I
will
be
mailing
out
to
the
mailing
list.
Looking
for
a
volunteer.
B
I
I
would
happily
volunteer
to
do
it.
I
haven't
done
it
before
and
I'm
relatively
new
to
the
community,
but.
A
Sure
are
you
able
to
ping
me
on
kubernetes
slack
and.
A
A
A
A
Pr's
mailing
lists
and
Bug
scrubs
if
there's
something
that
you
have
a
burning
desire
to
bring
up.
Please
add
that
to
these
lists,
otherwise
we'll
filter
through
them
and
see
what
we
can
find
I'm
going
to
go
ahead
and
start
with
mailing
list
review
since
Andrew
kindly
placed
some
stuff
up
here.
A
E
Harris
I
believe
we
have
two
kind
of
problems,
so
one
of
the
problems
actually
General
not
really
specific
to
SRV.
Okay,
we
are
hitting
like
memory
limits
and
I'm
on
it.
I
probably
will
have
a
PR
tomorrow
for
that
one,
and
the
second
issue
is
something
about
make
others
or
being
not
able
to
reach
some
kind
of
network
connection,
I'm,
not
sure,
not
sure
if
you
are
actually
investigating
English.
D
I
think
there's
there's
an
upstream
issue
for
the
MAC
address
issue
Google
with
the
sriv
plugin
okay,
but
that
that's
a
fact
that
we've
been
carrying
for
a
while
and
yeah.
The
issue
you
mentioned
with
the
memory
is:
is
the
main
at
the
moment
we're
also
seeing
some
flakiness
in
the
storage
Lanes
as
well,
but
so
there's
the
re-test
emerged
at
the
moment
is
quite
high.
So
just
if
you
have
PR's,
please
be
patient.
There's
a
couple
of
legs
at
the
moment.
B
Vnc
is
slow
issue.
I
kind
of
messed
up,
I
replied
with
suggesting
that
the
guest
agent
would,
you
know,
improve
the
mouse
coordination
and
I
forgot
to
reply
list.
So
I
just
replied
directly
to
Finland.
A
A
A
A
E
I
would
probably
suggest
to
somehow
different
the
GPU
on
the
on
kubernetes
level,
so.
D
A
It
says
what
you
expect
it
to
happen:
do
not
release
GPU
resource
when
vm1
stopped
so
once
I'm
reading
it
as
if
vm1
and
vm2
are
in
contention
for
the
same
GPU
VMware,
but
vm1
started
and
claimed
the
GPU
first.
A
A
A
E
Yeah
I'm
pretty
sure
that
the
cloud
interview
only
around
once
so
after
the
restart
you,
the
changes
are
not
persistent.
For
example,
if
the
user
is
using
container
discuss
root
disk,
then
it
may
happen
that
all
the
configuration
is
gone.
A
Yeah,
there's
definitely
I
wonder.
Maybe
we
can
at
least
ask
for
the.
A
A
E
Ryan
I
think
your
iron
dropped,
I'm,
sorry,
sixth
scale
I
think
it
would
be
the
best
person
to
answer
this.
A
A
Come
back
to
that,
let's
see.
A
E
I
saw
something
very
similar:
oh
I
see
that
the
message
air
limited-
my
log
is
exceeded.
E
E
Oh
probably.
E
E
I'm
not
sure,
maybe
we
can
improve
the
documentation
a
little
bit.
A
See
PR's
issues
and
mailing
list
so
I
think
should
be
good
to
go
there.
You
do
thank
you
for
volunteering,
for
next
week's
community
meeting
I
see
European
in
kubernetes,
slack
and
I
will
touch
base
with
you
and,
as
always,
thank
you
all
for
attending
and
participating
I
will
see
you.
We
will
see
you
same
time
same
place
next
week
and
I
will
see
you
again
the
week
following
have
a
great
week.