►
From YouTube: KubeVirt Community Meeting 2022-11-16
Description
Meeting Notes: https://docs.google.com/document/d/1kyhpWlEPzZtQJSjJlAqhPcn3t0Mt_o0amhpuNPGs1Ls/
A
B
Well,
I'll
go
really
quick,
come
more
coffee
from
pestin
I
may
have
introduced
once
before,
but
I'm
the
open
source
product
manager
and
we
have
adopted
Cube
vert
for
helping
break
back
up
persistent
workloads.
A
A
We
will
get
to
pull
requests
mailing
list
review
for
conversations
that
maybe
need
some
additional
dialogue
and
Bug
scrubs
towards
the
end.
If
you
want
to
call
any
of
those
out
specifically,
please
go
ahead
and
drop
those
below.
A
With
that
it
looks
like
Andrew,
you
have
a
plan
to
Archive
this
document
and
replace
it
with
a
new
one
to
record
meeting
notes.
Is
there
anything
more
to
that.
C
Not
so
much
I'm
I'm
hoping
it
will
be
seamless,
so
yeah
I'll
I'll,
try
and
do
it
while
everyone's
not
paying
attention
and
yeah
I.
Guess
the
only
people
that
this
will
affect
that
righteous
people
that
have
this.
C
For
whatever
reasons
the
minutes,
bookmarked
somewhere,
so
I
won't
be
able
to
update
that
but
yeah
the
meeting,
link
and
I'll
link
to
the
new
document
at
the
top
of
this
when
it
does
get
archived
yeah
I,
might
have
to
do
the
same
thing
with
the
zoom
meeting,
which
might
have
a
larger
impact,
I'm,
not
sure.
Okay,
apparently
they
expire,
and
this
expire
a
little
while
ago.
We
can
continue
to
use
it,
but
it's
no
longer
appearing
in
a
specific
Zoom
calendar,
so
I'm
still
getting
at
the
bottom
of
that
one.
D
Do
we
know
who
owns
the
current
minutes?
Because
we
could
actually
Mark
him
as
comment
only
after
it's
time
to
switch.
C
We
do
it's
actually
owned
by
pets,
which
is
one
of
the
reasons
I
see
right
then
the
other.
The
other
reason
being
is
that
it's
like
really
big,
and
it
has
tremendous
loading
issues
and
I.
Don't
know
if
that's
just
me
or
everyone
else,
but
sometimes
it
didn't
get
painful.
A
Well,
thank
you
for
taking
care
of
us
on
that
Andrew.
Let's
see
Cooper
CSI
driver
status.
Do
you
want
to
go
ahead
and
speak
about
that
yeah.
E
I
guess
I
hope
you
can
hear
me.
So
we
are
quite
interested
in
this
project.
Csi
driver
and
I
was
wondering:
what's
what
is
the
current
status?
If
it's
something
that
we
can
use
for
production
already,
I
see
there
is
no
release
yet,
and
the
other
question
is
if
first
official
release
is
possible
before
the
end
of
the
year.
Do
you
know
something
about
that
project?
Some
details.
F
Hey
there
yeah
I
I,
just
ping
is
the
person
that
I
know
who's
working
on
that
the
most
but
yeah.
So
what
are
you
looking
for
just
releases.
E
Yeah
I
just
I,
just
I,
just
wonder
if
anybody
is
using
this
already
for
let's
say
maybe
production
or
so.
F
Using
it
well,
yeah
I
can't
talk,
speak
much
to
production,
but
it's
definitely
we're
developing
it
and
we
have
plans
for
it
for
like
the
Downstream
in
the
like
hypershift
project,.
E
Actually
and
I
saw
there
are
some
references
to
openshift
like
I
saw
that
containers
that
are
responsible
to
register
the
CSI
driver
are
coming
from
the
openshift
repository,
so
does
it
mean
in
the
future?
You
will
have
a
constraint
that
is
gonna
mostly
work
with
openshift
openshift
only
without
kubernetes
or
no.
F
Yeah
yeah
yeah
I
told
them
to
join,
but
I
don't
know
if
he'll,
if
he'll
be
here
but
yeah
he's
he's
probably
the
person
that
could
help
you
the
most
getting
an
upstream
build
and
all
that.
H
E
No,
we
we
don't
plan
to
use
to
have
coffee,
it's
it's
a
different
project.
We
have
kubernetes,
we
have
our
own
components
and
toys.
Let's
put
it
that
way,
but
we
need
to
provide
storage
for
for
Cuba
nodes
right,
because
we
have
very
similar
project
like
hypershift.
G
G
F
Yeah,
it's
my
understanding
that
the
recent
work
that
has
been
going
on
there
is
TSI.
Originally
the
tenant
clusters
would
call
into
the
info
cluster
and
with
hypershift.
They
want
to
switch
things
around
where,
basically,
the
tenants
don't
directly
access
the
like.
You
know,
API
server
and
the
info
cluster.
E
I
E
It's
just
a
matter
right
now
how
well
tested
this
is,
and
I
mean
they
hold
the
CSI
driver
yeah
and
when
it
can
be
released
if
it's
possible
by
the
end
of
the
year.
But
since
Alexander
is
not
here,
yeah.
F
I
All
right
so
I've
implemented
the
basic
CSI
sanity
test,
which
is
essentially
a
unit
test
and
I've
also
implemented
the
Upstream
kubernetes
CSI
test
Suite.
E
H
I
The
the
testing
is
using
cap
K
to
spin
up
the
10
cluster
for
for
the
tests.
H
I
So
we
we,
we
have
the
tests
running
with
that,
but
there's
there's
no
like
code
dependencies
on
it.
It
can
run.
You
know
if
you
manually,
create
your
tenant
clusters
or
you
have
some
other
mechanism.
It
should
work
and-
and
in
fact,
I
I
just
created
a
PR
to
allow
you
to
use
customize
to
you
know,
set
up
your
deployments
with
for
specific
environments
to
hopefully
make
it
easier
to
be
independent
of
of
whatever
we're
using
in
our
development
environment.
E
Okay,
I
have
one
more
question
because
I
saw
there
is
the
issue
with
topological
strains
before
instance,
using
local
storage,
or
so
it's
anybody
currently
looking
into
this
issue
or.
A
All
right
and
notice,
from
Andrew
Burton,
of
course,
that
kubecon
EU
cfp
closing
date
is
this
coming
Friday.
So
if
you
have
any
meeting
any
proposals
for
talks
that
you
would
like
reviewed
or
we're
planning
to
submit
be
sure
to
bring
that
up
and
get
those
submitted,
and
we
will
support
you.
However,
we
can,
if
you
have
questions
about
any
of
that,
feel
free
to
reach
out
and
we'll
we'll
make
sure
you
have
answers
as
best
as
we
can
and
let's
see,
Sig
storage
Andrew.
C
Yeah
so
I've
been
talking
to
some
people
representing
seeing
storage,
but
only
if
the
working
you
know
just
a
service
such
as
Alexander
Michael,
looking
to
start
a
fortnightly
meeting,
Sig
storage
meeting,
and
so
it's
going
to
be
I
didn't
put
the
day
on
Monday
at
two
o'clock:
Central
European
Time,
which
is
I,
think
8,
A.M
us
eastern
time
is
that
correct.
C
G
C
Our
second
Sig
meeting,
okay,
there
cool.
A
All
right
and
there
I
was
talking
on
mute
yeah.
Are
we
also
gonna
mail
out
a
a
notice
to
the
mailing
list
once
all
that's
set
up.
C
A
A
A
All
right
and
then
Andrew
do
you
want
to
talk
about
Boston
or
anything.
C
Oh
just
in
that,
so
this
links
to
the
the
mailing
list
thread,
which
has
a
tremendous
amount
of
information
in
it.
C
Is
happening
it's
happening
first
weekend
of
February
you
do
have
to
log
into
Penta
bath
in
order
to
to
submit
so
that's
probably
the
only
Daniel
gotcha
the
Burton
I
asked
Deb
room
is
open
until
I
think
simply
December
10th.
C
Now
I
will
warn
people
that
the
this
Dev
Rim
is
only
it's
a
half
day,
different
I
think
in
the
past
it's
been
a
full
day,
Dev
route
and
so
yeah
the
The
Proposal
times
will
be
limited.
Foreign.
A
Thingy,
anyone
on
the
call
have
any
experience
building
out
the
Prometheus
monitoring.
D
A
C
Oh
cat
yeah
can
I
get
you
to
copy
the
template
and
cop
paste
the
template
and
then
change
the
date
rather
than
going
over
the
template.
A
A
And
that
gets
us
through
the
bed
scrub
list.
If
anyone
is
able
to
address
one
of
the
two
that
we
didn't
have
any
progress
on
or
responses
for
today.
That
would
be
greatly
appreciated.
A
Of
course,
this
is
your
opportunity
to
speak
up
if
you
have
any
any
last
minute
ads
to
the
agenda
or
otherwise
just
want
to
share
a
piece
of
news
or
crazy
offhand
idea
with
the
group
that
doesn't
have
to
be
official
in
the
agenda
just
for
fun.
B
I
was
at
kubecon
and
I
went
over
to
basically
the
open
little
space
where,
where
cubert
had
a
booth,
you
know
a
one-person
booth
and
and
sat
down
and
I
basically
had
one
question,
which
was:
how
do
I
learn
a
little
bit
more
about
the
roadmap
and
the
answer
was:
go:
take
a
look
at
the
epics
in
I.
Think
it
was
Red
Hats
jira!
Is
that
fair
to
say
was
that
did
I
get
that
take
away
properly.
D
We're
working
on
that
at
this
point,
the
public
or
the
project
has
been
rendered
public,
and
so
the
idea
is
that,
yes,
we
want
to
do
roadmap
items
in
jira.
However,
we've
also
been
doing
them
in
GitHub
as
well,
because
that
is
oh
okay,
you
know
completely
open.
D
So
usually,
if
we
have
an
epic,
it
will
have
a
link
to
roadmap
issue
that
will
reference,
usually
a
GitHub
link,
but
I
do
have
to
admit
that
we're
very
early
in
this
process,
there's
probably
going
to
be
large
gaps
of
things
that
were
just
rendered
internal
by
default,
because
we
hadn't
had
a
chance
yet
to
inspect
it,
make
sure
there
wasn't
anything
silly.
We
should
be
saying
there:
okay,.
C
I
want
to
say
more
possible,
probably
possible
after
our
next
release,
when
we
start
having
only
three
releases
a
year
rather
than
12
releases
a
year,
because
it'll
be
a
bit
easier
to
kind
of
like
you
know
gauge,
you
know.
A
Good
question
mark,
thank
you
for
asking
you're,
welcome
all
right
with
that.
Thank
you
all
for,
or
you
know
what
Andrew
it's
still
early.
Do
you
want
to
tell
us
anything
about
kubecon.
C
I'm,
probably
the
worst
person
to
ask,
because
I
was
more
or
less
on
the
the
showroom
for
the
entire
time,
either
helping
out
with
the
the
cubert
booth
or
looking
for
our
lost
boxes
of
Swag,
which
turned
up
but
still
as
far
as
I
know,
Missing
in
Action
or
helping
out
with
the
some
of
the
red
hat
stuff.
So
yeah
I
mean
I
can
tell
you
that
it
was
a.
It
was
a
very
big
flaw.
C
Well
spaced
yeah
having
a
I
can
give
you
a
kiosk
report,
which
is
I,
think
it
was
really
good
to
have
a
space
for
people
like
Mark
to
come
and
find
us
and
and
talk
to
people
specifically
about
cupert
rather
than
the
past.
Trying
to
like
you
know,
going
to
other
people's
booths
and
trying
to
strike
up
a
conversation
with
that.
So
I
suspect
that
something
well
I'm
very
keen
to
do
that
again
for
the
next
one,
except
probably,
rather
than
go.
The
half
day
go
for
the
full
day.