►
From YouTube: KubeVirt Community Meeting 2023-07-05
Description
Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/
B
B
A
A
Hopefully
people
saw
my
email
that
was
sent
out
yesterday.
That
was
saying
that
we
have
pushed
out
the
cupid
V1
release
I
eventually
last
week
that
there
was
a
PR
open
to
Bush
it
to
the
6th
of
July.
When
we
were
about
to
maintainers
last
week,
we
thought
that
pushing
back
entire
week
made
more
sense
and
that
was
pushed
through
and
messed
yesterday
and
so
yeah.
That
is
now
our
GA
release
date,
the
11th
of
July
and
partially
that's
around
that's
surrounding
the
ground.
A
The
messaging
and
coordinating
various
groups,
and
also
this
weekend
this
this
week
has
a
lot
of
different
holidays
in
different
places
such
as
America
and
the
Czech
Republic.
So
we
thought
the
11th
of
July
was
a
better
date
and
and
again
I
regret
any
inconvenience
that
this
postponement
may
have
caused
foreign
list.
C
All
right,
yeah
cool,
so
yeah
the
puzzle
is
pretty
much
ready
when
it
comes
to
him.
We
obviously
have
many
different
customization
options,
so
I've
pretty
much
laid
out
the
different
approaches
with
how
the
helm
chart
can
be
designed
and
implemented
and
in
turn
published.
So
I
would
want
to
have
some
more
reviews
on
this.
One.
A
A
B
Hello
again,
so
we
all
have
used
I,
think
cartagoda
here
or
at
least
heard
about
it
and
I
heard
that
Qbert
is
powering
the
killer
Coda.
That
is
contact
order
clone
so
me
and
Sandler.
We
have
been
discussing
since
last
month
what,
if,
if
we
can
have
a
open
source,
self-hosted
version
of
killer
coda
that
anyone
can
host.
B
B
Okay,
thank
you.
So
initially,
if
any
of
you
have
used
git
parts,
so
when
you
want
to
start
gitbot,
you
can
just
add
a
URL
to
the
existing
URL
and
it
will
open
that
particular
repository
in
our
Cloud
ID.
So
I
wanted
the
experience
of
a
learner
or
user
to
be
similar,
where
you
can
just
put
an
URL
to
the
end,
and
it
will
just
redirect
you
to
the
course
so
I
can
show
you
a
little
of
what
in
working
with.
So
let
me
put
the
link.
E
B
B
Okay,
so
here
we
have
everything
similar
to
killer
Coda.
We
have
a
left
pane
with
all
the
content
and
the
right
pen
that
it
has
a
iframe
that
I
have
not
developed
anything
for
it,
but
once
we
develop
the
back
end,
part
of
it
we'll
be
able
to
see
a
terminal
or
ID
here
and
then
for
now
you
can
just
go
through
the
content.
Here
you
can,
you
can
see
which
of
the
code
blocks
are
executable,
so
for
now,
I
have
just
gone
with
showing
a
green
ring
around
it,
but
letter
I.
B
We
can
add
a
some
kind
of
markers
here
like
play
button,
so
you
can
go
through
the
tutorial
and
there's
a
nice
highlight
as
well.
So
this
part
is
almost
complete,
like
there's
a
lot
of
optimization
and
Improvement
to
be
done,
but
for
POC,
I
I
would
say
it's
mostly
complete
now,
yeah
so
far,
any
questions
from
anyone
I
think
I'm
going
too
fast.
B
Okay,
so
if
no
one
has
any
questions,
so
my
idea
of
joining
this
call
was
to
get
an
idea
how
I
can
start
developing
a
back
end
which
can
create
a
VM
on
demand
and
destroy
it
when
it
is
no
longer
no
longer
used
so,
like
I
have
seen
videos
about
killer
Coda
and
the
blog
posts
that
it
works.
On
top
of
cube
word
by
demanding
a
VM.
Whenever
someone
opens
the
course
so
I'm
not
trying
to
clone
it
exactly,
but
that
would
be
a
good
starting
point.
B
Okay,
so
right
now
I'm
trying
to
write
a
controller
that
would
do
it
like,
like
I
work
in
the
tecton
community.
Primarily
my
work
is
on
technology
results.
There
we
have
a
controller,
protectron
pipelines,
controller
that
talks
to
tecton
API,
which
creates
all
the
pipelines
and
task
currents.
Then
we
can
reuse
those
API
in
other
applications
as
well.
So
my
starting
idea
is
to
do
something
like
that.
We
already
have
the
keyword,
API
and
developing
a
controller
that
can
talk
to
that
API
and
create
VMS
on
demand
and
manage
it
as
well.
F
F
So
the
Techno
yeah,
like
I,
said
I'm
not
familiar
with
those
but
I.
Just
vaguely.
Remember
that
so
I
think
we
have
techton
I'm,
not
even
sure
what
the
correct
nomenclature
and
in
this
type
is
I.
Think
it's
some
something
like
called
the
step
or
something
or
like,
like
it's
a
like
a
like
a
piece
or
something,
and
that
would
actually
create
a
virtual
machine
within
tecton.
F
B
B
E
Yeah
I,
don't
know,
I
mean
even
just
for
parts,
for
example,
and
then
we
can
see
if
we
can
use
cure
with
those
two
I
mean
because
your
front-end
needs
to
somehow
talk
to
some
some
framework.
I
mean
tactone
to
me
makes
sense.
But
my
question
is
the
other
way
around.
Do
you
have
your
preference,
or
do
you
have
already
an
idea
about
the
tool
you
would
like
to
use
and
then
eventually
we
can
see
if
you
can
use
that
frame
or
tooling,
with
Qbert.
B
All
right
yeah,
that
is
a
great
session
actually
but
right
now,
I,
don't
have
a
tool
in
mind.
My
initial
design
idea
was
to
talk
to
the
back
end
through
rest.
Api
calls
like
the
front
end
is
totally
separate
from
the
back
end
and
it
just
communicate
through
rest
apis,
so
something
we
have
to
develop
from
scratch.
If
it
doesn't
exist,.
E
Yeah
because
I
don't
know
I
think
maybe
a
keyword.
Api
is
a
little
bit
too
low
level
for
this,
so
maybe
having
something
in
between
like
Tech
Turner,
the
noise
intactor
might
be
might
be
already
something
that
can
can
obstruct
at
least
because
at
least
you
need
to
I.
Don't
know,
maybe
have
the
possibility
to
take
a
template
based
on
the
scenario
that
you
want
to
run,
and
you
want
to
start
the
VM
and
then
eventually,
when
it's
done
just
deleting
it.
So.
B
B
F
E
F
F
So
it's
playing
tricks
on
me
here
so
yeah
I
wanted
to
just
quickly
raise
this
mini
PR
that
I
brought
up.
We
were
discussing
this
morning
to
emphasize
the
value
of
draft
PRS
on
itself
in
order
to
save
resources.
If
you
are
not
yet
sure
what
whether
your
PR
goes
into
the
right
direction,
and
we
would
we
were
discussing
that
we
would
favor
something
like
like
a
default
to
a
draft.
Pr
and
I
was
researching
a
little
bit
on
that
topic
and
I.
F
What
I
saw
was
that
actually,
the
guitar
does
what
force
this
default
onto
its
people.
Somehow,
because
it
fears
that
somehow,
maybe
PR's
that
get
opened,
I
had
forgotten
to
be
put
from
drafted
to
a
normal
state
would
actually
be
somehow
forgotten,
and
the
burden
would
be
do
would
be
too
high.
I
can
somehow
agree
with
that.
F
So
so
I
thought
what
else
would
be
possible
and
I
just
came
up
with
this
idea
of
just
adding
it
to
the
template
so
that
you
have
something
like
whenever
you
open
a
PR
that
you
are
reminded
to
consider
creating
a
are,
as
a
draft
I
think.
That's
that's
an
easy
solution
to
just
remind
people
of
maybe
that
they,
if
they
are
not
completely
ready,
they
can
just
open
a
draft
VR
yeah.
Let
me
know
what
you
think
about
that.
I
think
it's
easy!
A
F
Makes
sense
yeah,
that's
true.
That's
that's
true.
I
know,
I,
know,
Jeff
that
this
default
is
obviously
being
kept
by
by
GitHub,
but
yeah.
It's
I
think
it
doesn't
work
to
just
maybe
open
it
as
first
as
a
draft
and
there
to
to
convert
it
from
a
draft
to
a
normal.
Pr
is
just
one
click
of
a
button,
I'm,
not
sure.
F
So
I'm
going
to
continue
talking
because
because
the
next
point
is
also
by
me,
so
this
one
is
the
gen
tool
that
I've
been
working
on.
So
since
we
are
looking
at
flakes,
I
wanted
to
have
a
more
condensed
picture
of
where
exactly
those
flakes
are
hurting
us.
Somehow,
so
I
generated
an
HTML,
a
tool
that
generates
a
page
that
would
help
you
to
find
the
hot
spots
and
where
the
most
flags
occur.
F
It
does
this
in
two
in
two
Dimensions.
First
of
all,
it
does
it
per
day
and
then,
second
of
all
it
does
it
per
Lane.
So
you
see
in
the
screenshot,
for
example,
in
the
overall
Aggregates,
you
see
the
flakes
that
occur
per
day,
and
then
you
see
yeah.
Then
you
can
easily
spot
exactly
when
what
exactly
the
hotspot
days
were.
So
in
this
screenshot,
it
has
been
8th
of
June
with
10.10
percent
of
the
of
the
all.
F
The
of
all
the
failures
that
have
been
there
and
yeah
per
Lane
also
would
tell
you,
for
example,
that,
like
the
sick,
compute
Lane
has
been
one
of
the
top
hot
spots
with
49
failures.
Somehow
also,
it
has
something
like
it
Aggregates
if
you
scroll
a
little
bit
or
if
you
go
back
to
the
pr
Andrew
and
let's
go
a
little
bit
down,
then
you
see
the
protest
Aggregates,
which
tells
us
something
about
the
what
the
top
flaky
tests
are.
F
Somehow
you
would
probably
see,
for
example,
like
this
one,
the
top
flaky
test,
and
that
screenshot
is
just
this
test
that
has
a
share
of
7.45
of
the
failures
of
on
overall
lanes
and
it
hurts
in
the
125
Sig
operator
Lane
the
most.
So
we've
been
trying
out
this
tool
in
our
weekly
meetings
and
it
helped
a
lot
and
yeah.
Maybe
so
it
helps
other
people
also
to
look
at
that,
so
if
they
are
working
against
flex
and
so
on,
so
to
see
where
we
stand.
F
F
G
F
What
yeah,
just
just
one
last
thing
that
I
forgot,
I'm
I'm,
just
going
to
I,
put
as
part
of
this
PR
I,
put
up
a
a
periodic
job
that
will
recreate
this
link
that
you
see
here
at
the
full
example
that
will
create
recreate
this
this
page
on
a
daily
basis,
so
that
we
always
have
this
handy
and
can
see
where
it
hurts
us
now
I'm
going
to
stop
talking.
Thank
you.
A
F
A
A
It's
one
of
the
the
best
things
I
could
see
on
a
Wednesday
afternoon
is
saying
that
all
the
pull
requests
have
all
the
attention
they
need
and
if
anyone
is
feeling
that
the
pull
request
is
not
getting
attention
to
Zeus
and
I'm,
a
big
fat
liar
now's
your
chance
to
throw
it
in
there
and
we
can
all
have
a
look
at
it
and
I'll
move
on.
But
if
you
do
add
something
we
can
come
back
to
it
at
the
end
of
the
meeting
in
the
mailing
list.
A
A
G
G
A
F
No
I,
actually
sorry
sorry
to
to
chime
in
here.
I
just
saw
this
this
morning
and
I
think
it's
actually
a
new
strategy
that
was
that
was
added
and
in
the
end
of
last
year
or
something
I
was
completely
surprised
because
I
didn't
know
that
either
so,
but
I
don't
have
a
good
take
I,
don't
understand
it
well
enough
to
to
be
able
to
to
be
able
to
document
it
and
to
help
Marcelo
and
how
to
put
it
but
yeah.
F
H
A
Surprise
that
Daniel,
let's
do
what
studio
you're
welcome
to
take
this
on.
But
if,
if
you're
able
to
ping
me
the
pr
that
introduce
this,
then
I
can
follow
up
with
the
author,
and
it
would
be
a
good
reminder
as
to
when
we,
when
we
do
add,
features
to
things.
It's
always
good
to
update
the
documentation.
D
A
A
A
I
believe
this
was
from
Miguel
and
I
think
this
was
kind
of
a
is
Miguel
on
the
line,
rather
than
maybe
butchering
what
this
is
about.
He
is
not
I
think
it's
just
a
bit
of
an
FYI
about
a
new
feature.
With
regards
to
this.
You
can
read
this
in
your
own
time.
I
just
thought.
I
would
highlight
it
here,
so
that
people
can
can
see
it
and
learn
about
it,
and
then
we
had
another
design.
There's
a
design
suggestion,
not
a
design
proposal.
A
H
Yeah,
this
is
like
the
the
future
that
was
being
requested
a
few
times,
and
the
current
status
is
that
it's
I
like
there
is
a
working
proposal
and
the
back
end
has
like
some
some
rough
edges.
That
needs
to
be
fix
it,
but
the
most
important
part
is
like
the
the
front
end
like
the
how
cluster
admins
would
like
to
configure
and
expose
their
OSB
devices.