►
From YouTube: KubeVirt Community Meeting 2022-09-14
Description
Meeting Notes: https://docs.google.com/document/d/1kyhpWlEPzZtQJSjJlAqhPcn3t0Mt_o0amhpuNPGs1Ls/
A
Be
sure
and
add
anything:
that's
on
your
mind,
anything
that
maybe
needs
a
call
out
or
some
extra
attention
to
agenda
notes
or
open
floor
as
always
pull
requests
and
Bug
scrubs
and
mailing
list
reviews
are
coming
up.
So
if
there
are
any
conversations
PR's
or
bugs
that
need
some
extra
attention
drop
those
down
below
and
we
will
get
to
that.
C
A
All
right,
wow
agenda
items
and
attendants
are
being
logged.
If
there's
anyone
new
on
the
call
today,
I
would
love
to
encourage
you
to
speak
up
and
introduce
yourself.
We
had
all
like
to
welcome
you
and
hear
what
brings
you
into
the
Cooper
call
today.
C
Oh
hi
I'm
Peter,
it's
my
first
time
on
this
community
meeting
I
work
at
an
Nvidia.
Probably
you
know
Ryan,
but
probably
we
plan
to
be
more
involved
in
the
community.
So
that's
why
I'm
here.
C
Foreign,
so
I
was
here
last
week,
but
I'll
introduce
myself
because
I
think
you
were
out
I'm
Larry,
Dewey
I
work
at
AMD
also
looking
to
be
more
involved
in
the
community
and
was
also
on
last
week
to
talk
about
Hardware
enablement.
So.
A
C
D
Be
something
we
would
benefit
from
a
little
verbal
discussion
on
I:
don't
want
to
Dive
In
The
Weeds
of
the
technical.
Why?
But
just
this
has
been
a
situation
where
we've
been
taking
a
least
common
denominator
approach
in
order
to
be
able
to
accommodate
Docker,
but
we're
going
to
try
and
transition
to
a
more
secure
stance
by
default,
and
so
as
a
part
of
that,
this
is
basically
just
a
heads
up
to
the
community
that,
if
you're
using
Docker
and
you're
using
SC
Linux,
you
need
to
enable
this
feature.
Gate.
A
Got
it
do
we
have
that
adjusted
in
documents
anyway,.
D
Jed,
do
you
your
mic
work.
E
Hi,
can
you
hear
me
yeah
so
yeah?
What's
the
question?
Is
there
any
documentation
for
future
gate?
Yes
and
I?
No
I
didn't
read
it
yet,
but
yeah.
That's
a
good
point.
I
should
probably
write
something:
okay,.
F
The
the
follow-up
to
that
was
Fabian
put
out
a
request
for
volunteers
for
anyone
able
to
help
out
with
a
like
a
release,
email.
A
A
B
B
E
Would
be
really
nice
to
have
a
checklist
that
you
know,
whoever
is
handling
a
release.
You
know
as
a
volunteer
or
as
one
of
the
kind
of
principal
people
coming
back
in
to
help
and
I
also
would
like
to
add
to
that
checklist.
The
update
of
the
website,
where
we
have
the
release,
notes,
kind
of
auto-generated
by
a
script.
A
I
know
that
go
releaser
has
a
lot
of
options
for
how
to
build
all
that
out,
but
I
don't
know
what's
currently
in
Youth
and
if
it
has
equivalent
feature
set,
go
release
your
release
or
can
I
think
it
has
an
email,
interface.
I
know
it
has
like
social
media
interfaces.
B
B
We
are
using
a
custom,
made
release,
tool
and
I.
Guess
that
as
since,
since
we
haven't
completely
automated
the
release,
I
guess
that
that
the
rest
of
the
stuff
would
either
need
to
get
incorporated
into
that
release,
tool
that
is
based
in
Project
info
repository
inside
the
cupid
org.
B
We
might,
we
might
add
something
there,
but
then
we
would
need
to
create
a
keyboard
bot
account
for
for
Twitter
and
I.
Think
there
is
one
but
I
don't
know
who
owns
that
and
maybe
even
just
create
an
email,
something
like
that,
but
yeah
I
I,
guess
that
is
just
an
open
task
that
someone
needs
to
pick
up
somehow.
A
Adjusting
the
release
cycle
slowing
down
the
release
cycle
should
at
least
improve
some
of
that
and
then
automating.
The
release
like
there's
a
lot
to
do
just
with
release
stuff.
Isn't
there
yeah.
B
Actually,
actually
I
think
you're
totally
right
there
yeah.
So
maybe
maybe
my
first
first
guess
would
be
that
we
might
first
wait
until
this
agreement
on
the
Slowdown
of
the
release,
process
or
I
would
I
would
like
to
put
it
as
as
Vine
did
it
so
like
like.
We
want
to
follow
the
cupboard
release
it
in
some
way.
B
F
A
F
I,
like
that,
I
also
think
in
the
interim
channels
I
did
about
having
a
checklist
to
cover.
Those
bases
is
good,
but
for
now,
but
it'll
also
help
inform
that
how
we
automatic.
A
Is
there
a
specific
project
that
we
want
to
model
after,
like
and
just
as
an
example
to
cover
any
release
artifacts
that
we
might
be
missing
like
tweets
and
emails,
or
that
that
way
we
can
actually
start
practicing
the
checklist
and
convert
that
into
automation,
issues
going
forward.
B
So
I'm
not
quite
sure
if
I
got
that.
Sorry
for
that,
but
I
guess
I,
guess
that
what
what
I
understood
from
this
is
like
we're
thinking
about
Paving
a
path
somehow
for
automating.
All
this
and
I
think
that's
that's
a
good
idea
to
do
that
and
and
I
think
this.
This
has
been
overdue
for
a
long
time
now
so,
but
still
I
would
prefer
probably
to
to
just
wait
until
the
release
streaming
alignment.
B
Somehow
I,
don't
know
how
to
call
it
that
how
it's
called
has
settled
and
then
we
we
might
pick
this
up
again.
So
yeah
I'm,
all
for
for
Moto
making
the
release.
B
I'd
say
that
this
would
be
very
beneficial
and
I
think
that
in
the
process,
when
we
have
settled
on
this
release,
streamlining
that
we
might
still
or
also
need
to
adjust
a
little
bit
on
how
the
release
is
done
because
from
my
understanding
from
the
document,
the
cut
off
a
release
candidate
doesn't
mean
automatically
creating
another
release
bench,
but
just
to
release
tag.
If
I
understand
correctly
and
the
release
branch
is
only
cut
when
the
third
release
candidate
is
is
picked
somehow.
But
I
might
be
wrong
with
that.
A
You're
fine
I
I
was
waiting
to
see
if
anyone
else
had
anything
else
to
say:
I
think
that
you're
right
as
far
as
handling
the
conversation
around
the
new
release,
Cadence,
is
a
good
plan.
Andrew,
Burton
I
think
you
said
you,
you
wrote
creating
the
checklist.
I
think
that's
great,
just
as
a
practice
between
now
and
then
so
that
we
can
identify
what
kinds
of
things
we
might
want
to
add
as
features
to
the
automation
when
we're
ready
for
that
discussion,
and
we
can
start
practicing
cleaning
up
loose
ends
for
that.
B
All
right
and
and
like
I
said
so
that
we
don't
forget
that
I
guess
that
we
need
to
find
out
who,
who
owns
this
Twitter
Cupid,
bot
or
Qbert
Twitter
account
somehow
I
I,
don't
know
who
phones
it.
So
maybe
someone
can
try.
Oh
I
can
answer
that.
F
That
is
now
something
that
we
we
can
get
back
onto.
F
Also,
just
I
guess,
while
we're
while
we're
talking
about
these
changes
with
the
release,
Cadence
I
I,
don't
know
for
a
fact,
but
it
we
may
need
to
look
at
how
we
automate
the
release
notes.
Because
if
we're
releasing
three
times
in
a
year,
then
our
at
least
that's
going
to
become
relatively
large
I.
Imagine
and
we
may
need
to
put
some
system
of
ordering
them
so
they're
more
like
easier
to
to
go
through.
B
C
B
F
At
the
moment,
I'm
I'm
creating
a
PR
every
after
each
release.
Using
that
script
we
we
do
have
a
an
issue
that
I
think
went
stale
today
quite
Timely
in
the
project
infra
repo
about
how
we
could
incorporate
that
script
running
with
the
release.
F
B
So,
but
yeah
still,
if
I
understand
correctly,
I,
guess
that
the
release
notes
are
attached
to
every
release
candidate
somehow
and
the
second
release
candidate
might
have
additional
features
and
then
that
the
first
task-
so
maybe
it's
even
okay-
to
to
just
point
to
every
release
candidate
and
have
the
results
there.
Or
do
you
think
that
we
should
combine
the
release
notes
into
one
big
pile
of
release,
notes
that
that
span
all
the
release,
candidates,
attachments.
F
Yeah
I'll
stop
my
head.
I
would
say
that
each
release
candidate
would
get
its
own
release
notes,
but
when
we
do
a
a
major
release,
we
would
also
want
to
then
put
them
all
together.
F
A
All
right
and
then
definitely
don't
miss
chiming
in
on
the
release.
Cadence,
if
you
have
any
opinions
on
that
or
questions.
A
F
B
I
think
this
needs
more
information,
so
not
even
what
what
the
client
is.
At
least
we
have
the
client
version
and
server
version,
but
yeah.
C
Yeah,
sorry,
that
warning
is
is
just
uninformative
message
that
says
basically,
that
the
client
version
that
he
is
using
is
different
from
from
server
one,
and
it
appears
only
if
there
there
is
an
error
and
there
is
error,
searching
virtual
machine.
So
yeah
probably
we
need
some
yaml
something
else.
B
B
I
I
think
I
think
at
least
we
need
some
more
information.
What
exactly
he's
using
and
how
he's
he
sees
configuratives
virtual
machine
so
like
I
I,
think
I
think
I
would
ask
for
the
VMO
and
so
that
we
have
more
information
on
on
what
what
storage
options
he's
using,
for
example,
and
yeah.
C
A
So
I'm
actually
yeah.
It
could
just
be
a
like
the
container
desk,
ephemeral
VM.
That
might
be
something
we
should
do
is
do
we
have.
C
B
Okay
and
yeah:
that's
that's
a
good
point
by
the
way
that
we
could
probably
always
point
to
the
issue,
template
and
maybe
just
fill
out
all
the
information
that
is
provided
there,
so
that
we
can
help
them
better.
A
C
B
Yeah,
that's
mine,
I
think
I've
discovered
with
Bakken
lot
migration,
but
I'm
still
waiting
for
answers
on
that.
C
A
A
C
A
So
I
guess
resource
limits
aren't
being
applied
to
Pops.
A
A
B
Yeah
I
I
agree.
Maybe
there
might
be
something
wrong
with
the
whole
qubit
installation,
somehow
maybe
get
past
status
or
something
would
help
after
installation
or
with
the
whole
pot,
would
be
ready
somehow
and
also
I
think
also
the
PCS
trying
to
apply
VMS
back,
but
that
is
also
missing.
So
maybe
you
might
also
attach
that
the
VM
spec
is
missing
talking
about
applying
the
VM
spec,
but
he
doesn't
post
it
here.
So
I
guess
this
might
also
help
in
and
hearing
what
the
issue
is.
C
A
C
Issue
I
think
I
know:
where
is
the
issue
I,
don't
know
how
he
deployed
the
kubernetes
itself,
but
there
might
be
a
problem
with
verification
of
certificate
of
cubelet.
So
it
can't
read
the
blocks
from
the
pots
deployed
on
the
Node.
C
A
C
E
Quick
thing,
I've
noticed
some
issues
coming
up
in
the
kubefort.github.io
website
repository.
That
seemed
to
be
more
like
covert
questions,
and
we
don't
really
have
a
way
that
we're
bringing
those
into
light
and
so
I
think
one
thing
I'd
like
to
do
is
probably
go
through
those
kind
of
manually
this
time
and
say
hey.
This
works
better.
If
you
raise
this
issue
in
Cooper
covert
and
then
look
at
the
issue,
template
and
add
some
verbiage
to
the
issue
template
that
says,
this
is
for
the
website.
Only.
B
C
B
So
so
cat
you're,
suggesting
probably
that
we
should
just
update
the
bug
report
template
so
that
the
first
line
would
say
this
form
is
for
bug,
reports
and
feature
requests
for
the
cupboard
website.
Only
right
something
like
that.
Yes,
yeah.
A
B
I
guess
we
need
to
I,
don't
know
of
any
automation
that
would
probably
transfer
issue
from
one
repository
to
the
other.