►
From YouTube: Summit 2022: Welcome and State of KubeVirt
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
everyone
to
the
second
online
kubert
summit,
so
a
big
welcome
to
the
entire
kubert
community.
A
In
just
a
moment,
fabian
deutsch,
our
lead
developer,
is
going
to
be
introducing
the
event
and
telling
you
what's
going
on
in
cooper
right
now
before
then,
a
few
things
number
one
you'll
notice
that
chat
panel
on
the
right.
If
you
have
questions
for
the
speaker
in
the
presentations
throughout
the
day,
feel
free
to
ask
them
in
the
chat
panel
and
the
moderator
of
the
session,
I
will
hold
on
to
them
and
ask
them
the
speaker
at
the
appropriate
time
I
during
q
and
a
for
the
various
sessions.
A
You
are
actually
welcome
to
ask
your
question
out
loud.
If
you
wish
to
do
so,
please
simply
type.
I
have
a
question
to
ask
out
loud
in
the
right
hand,
column
and
in
the
chat
window
that
is
and
again
the
moderator
will
give
you
a
chance
to
ask
that
aloud
during
the
q
a
portion
of
each
session.
A
A
So
please
treat
your
fellow
community
members
with
respect
and
with
that
let
me
introduce
fabian
deutsch,
although
I
don't
really
need
to
introduce
him
to
this
audience,
because
you
all
know
him
so
fabian.
You
want
to
get
started.
B
Josh,
thank
you
very
much
and
yes,
I'm
I'm
here
to
serve
us
right,
and
so
let
me
get
to
my
first
slide.
So,
yes,
a
quick
hello
to
everybody
and
thanks
for
taking
the
time
to
join
us
today
and
thanks
to
josh
and
the
team
to
actually
make
this
happen
right
not
only
to
josh
and
the
team
who's,
helping
us
with
the
infrastructure,
size
and
planning,
but
also
to
to
all
the
speakers
who
invest
the
time
to
prepare
sessions
for
today
that
all
of
you
can
enjoy
not
only
today
but
also
for
tomorrow.
B
Yes,
so
thanks
again
about
myself,
my
name
is
fabian
deutsch,
I'm
an
engineer
at
redhead
and
just
with
keyboard
for
a
while
and
happy
to
do
this
small
intro
to
the
summit,
but
I
think
the
real
heroes
are
are
all
of
you
and
contributing
to
keyboard,
not
only
source
code
but
helping
us
with
a
lot
of
things
in
the
community.
B
All
right
next
slide.
Please
that's
just
me
doing
it
all
right.
So
this
is
our
second
annual
kubert
summit.
The
last
one
took
place
roughly
a
year
ago.
I'm
actually
not
sure
about
the
exact
dates.
The
version
back
then
was
version
38
right,
a
leading,
zero
right,
so
we're
still
not
and-
and
the
version
we
have
today
is
0.50
right,
so
we're
still
not
with
a
stable
version,
but
we're
still
moving
forward
rapidly.
So
what
happened
in
the
last
year?
Technically,
let's
focus
on
the
technical
aspects.
First,.
B
While
the
world
out
there
kept
doing
what
it
did
in
the
last
two
years
right,
we
continue
to
to
build
features
for
the
storage
area,
the
virtualization
networking
areas
in
keyword.
This
happened
often
in
the
core
key
for
kubert
repository,
but
also
many
repositories
around
it
right.
So
it's
a
keyboard
project
and
the
qubit
project
by
now
is
more
than
than
the
cubic
keyboard
repository.
B
B
We
saw
enhancement,
the
storage
area
where
we
were
continuing
to
work
on
hot
plugging,
while
hot
plugging
is
still
not
and
who
knows,
if
still
not
available
in
kubernetes,
but
for
cuber,
because
it's
such
a
classic
virtualization
feature,
storage,
shot,
block
memory,
cpu
and
networking
hub
clock
as
well.
By
the
way
we
looked
at
it
and
we
had
alexander
contributing
this
feature
in
in
many
days
of
work,
and
it's
great
to
see
that
we
have
a
a
nice
flip-flop
solution
in
place
by
now
or
which
seems
to
work
fairly
well.
B
On
the
other
hand,
we
have
snapshots
while
offline
snapshot
line
at
first.
We,
it
was
then
followed
by
online
snapshots,
which
was
which
is
nice,
because
today,
we're
then
able
to
to
snapshot
a
vm
that
is
running
also.
One
of
these
features
that
are
expected
from
virtualization
management
platform
for
core
compute
features,
I
think
notable
highlights-
are,
for
example,
venuma.
B
Last
year
we
implemented
enuma,
which
allows
to
effectively
reflect
the
whole
cpu
and
core
topology
into
the
vm.
That's
specifically
interesting
to
high
performance
workloads
which
do
a
lot
of
computing,
and
the
second
feature
that
we
worked
on
throughout
the
year
and
it's
again
it's
not
a
complete
list,
but
the
second
notable
feature
is
vgpu
slicing,
for
example,
while
the
support
to
do
pci
device,
pass-through
and
mediated
devices
pass-through
landed
a
while
ago
in
the
past
year,
there
was
additional
work
in
order
to
configure
that
in
a
nice
way
as
well
right.
B
So
today,
if
you
have
the
right
drivers
on
your
nodes,
you
can
leverage
keyboard
in
the
keyword
cr
in
order
to
configure
these
graphics
cards
in
your
nodes
and
slice
them
up
into
virtual
slices.
That
can
then
be
assigned
to
vms
and
cuber
is
providing
this
end-to-end
solution
right.
The
slicing,
the
exposure
as
kubernetes
resources
and
the
third
part,
the
consumption
into
vms,
enabling
workloads
right
is,
is
what
happens
so
far:
right
hotline
snapchat's
new
pneuma
slicing.
So
we
saw
a
lot
of
use
cases
coming
in
and
that
drove
the
development
of
the
features.
B
Another
notable
group
is
actually
scale
right
and
while
I,
while
there
were
many
fixes
in
the
scale
area,
the
actually
the
the
bigger
thing
that
happened
is
that
we
established
under
I
mean
that
people
established
big
scale,
which
is
fantastic
right.
So
we
have
six
scale
which
is
meeting
once
a
week
which
is
looking
at
different
aspects
of
of
cuber
right.
So
we
want
people
right.
B
B
There
were
many
pr's
about
it,
which
reworked
very
I
mean
very
old,
but
very
new
code
areas
in
kubert,
but
they
have
in
common
that
they're
security,
sensitive
and
the
effort,
but
security
is
to
eventually
get
to
vm
pods,
which
run
unprivileged
and
is
not
as
rude
and
can
run
with
random
uids
assigned
to
containers
for
security
reasons,
and
this
required
a
couple
of
bit
of
refactoring
across
the
code
base,
and
this
is
progressing,
but
we're
certainly
not
done
yet,
but
it's
good
that
there
are
also
no
known
blockers
which
which
will
stop
us
from
achieving
that
goal.
B
There
were
also
a
few
features
that
support
cubated
operations
right
interesting
gears,
for
example
the
eventual
updates
right.
So
while
the
keyboard
operator
had
is
there
for
a
while-
and
I
think
it's
them
actually
nice
component
right
to
really
adopt
the
operator
pattern
and
encode
operate
on
operational
knowledge
into
a
software
component.
On
the
other
hand,
to
be
honest,
I
wonder:
isn't
it
a
two?
You
know
a
two
two
bladed
sword
like
like
so
many
swords
out
there.
B
I
guess,
but
isn't
the
problem
that
maybe
some
admins
will
will
rely
too
much
on
operators
to
the
operations
for
them,
but
I
think
that's
more
of
a
philosophical
discussion
than
a
technical
one,
long
story
short
with
eventual
updates.
We
finally
have
some
logic
that
is
not
only
updating
the
control,
control,
plane,
components
like
word
handler
and
the
controller,
but
also
ensuring
that
the
word
launchers,
which
are
running
your
vms,
will
be
updated.
Eventually.
B
Also
bleeding
into
the
operations
area
is
our
work
on
metrics
and
run
books
run.
Books
specifically
are
interesting,
because
it's
great
that
we
had
metrics
it's
great,
that
we
alerts,
but
in
the
end,
do
they
help
users
not.
This
is
necessarily
right
as
a
user,
if
I'm
woken
up
at
night
and
telling
me
cuber
is
down,
but
I've
got
no
idea
why
it
happened
and
what
to
do
that
is
where
run
books
come
to
the
game.
Right
run
books
tell
a
user,
an
operator
for
kubernetes
class
of
cuber
cluster
of
what
to
do
all
right.
B
So
these
are
like
things
that
happen
in
the
core
keyword
qubit
code
base,
but
the
nice
thing
is
that
there
happened
so
much
more
in
the
broader
ecosystem,
not
in
the
kuber
ecosystem
alone,
but
actually
the
cncf
ecosystem
right.
B
Sorry,
that
was
actually
argo
for
tech
done.
We
have
all
kinds
of
automations
around
vms.
Obviously,
we
also
have
a
good
collaboration
with
actually
the
library
project
right,
our
peers
that
we're
building
upon
liberty
and
cumu
and
there's
a
small
side
project
that
I
want
to
call
out,
because
there
was
so
much
so
many
thoughts
went
into
that
area,
which
is
called
past
right.
B
We
have
that
problem
of
we
want
to
hook
vms
to
the
kubernetes
network,
and
we
have
solutions,
obviously
there
today,
but
we
we
also
have
the
feeling
that
there
might
be
some
more
work
needed
to
make
that
great
right
and
past
is
one
of
these
small
tools
that
is
being
researched
by
stefano
in
this
case
and
I'm
curious
to
see
how
these
small
things
will
eventually
net
in
cuber
to
make
it
even
better
and
and
find
the
right
trade-off
between
traditional
virtualization
and
the
declarative,
cloud-native
feature
of
the
aspects
of
kubernetes.
B
Another
big
chunk
of
work
or
things
that
happen
is
actually
the
cluster
api
provider
for
cuberd
right.
So
with
cup
k,
which
is
its
own
project
and
can
find
it
on
slack
with
all
new
community.
That's
interested
to
to
bring
the
cluster
api
to
keyboard
right
so
to
leverage
cubeverd
in
order
to
bring
up
new
tenant
kubernetes
clusters
on
top
of
kubernetes
using
kubernetes.
B
B
Speaking
about
the
features
that
we
drive
right
in
the
use
case,
that
cost
us
to
implement
them.
I
think
what
we
saw
if
we,
if
we
step
back
from
the
technical
side,
is
people
right.
People,
people
are
are
the
audience
of
the
project.
Sometimes
they
are
bots
right
and
they
help
us
to
do
other
stuff,
but
we
see
continuous,
continuous
stream
of
contributions,
first-time
contributors
right
from
from
across
the
board
to
the
keyboard
code
base.
But
I
want
to
call
out
we
as
a
project
with
a
community.
B
We
live
not
only
from
code,
we
need,
we
need
more
right.
We
we
need
community
members
to
help
on
the
user
guide
right
to
see
that
it's
great
right
to
tell
people
how.
How
is
cuba
used?
What
are
best
practices
in
order
to
use
keyword
right
and
to
pay
attention
to
it,
to
to
keep
it
updated
and
to
keep
it
accurate?
The
same
is
true
for
bugs
right.
We
have
a
lot
of
issues
open
on
qubit
cuberd
and
I
think
would
be
great
if
we
can
encourage
more
people
to
support
us
on
these.
B
I
hesitate
to
call
it
outer
skirts
of
the
project
because
in
the
end,
they
are
as
important
as
the
code
right,
but
to
help
us
to
to
to
tidy
up
these
areas
and
make
it
make
it
a
clean
and
open
well-maintained
project
across
the
board.
Right,
not
only
on
the
on
the
feature
side.
B
B
We.
We
saw
a
couple
of
community
members
stepping
up
in
the
past
year
to
say
that
they
adopted
kubrick
as
well.
I
think
we
have
that
list
in
the
cube
repository
and
we
have,
for
example,
platform
nine,
which
is
doing
a
lot
of
stuff
with
keyboard
right.
It's
great
to
see
the
managed
platform
platform,
nine
and
it's
nice
to
see
that
google
antos
right
has
seen
or
is
now
adopting
more
of
keyboard,
so
the
rancher
will
have
a
talk
from
them
and
I'm
looking
forward
to
that.
B
One
has
also
gone
with
kubert
and
picked
up
cubert
and
associated
project.
So
it's
great
to
see
that
we
see
integrators
and
vendors
picking
up
keyword.
What
I
would
like
what
I
think
we
we
need.
We
all
need
to
do
is
to
encourage
our
users
to
step
up
and
tell
them
or
have
them
tell
us
what
their
user
stories
are
right.
What
are
their
use?
Cases
so
that
we
can
really
really
get
close
to
them
and
help
them
to
solve
their
problems.
B
So
I
did
not
touch
it
yet,
but
there's
obviously
also
the
the
fact
that
cuba
is
the
cnc
of
sandbox
project
right,
but
in
the
second
half
of
last
year
we
actually
opened
the
pr.
So
we
started
the
process
to
see
if
cuber
is
getting
to
the
cnc
cncf
incubator.
B
There
are
a
couple
of
requirements
on
the
project
to
get
into
that
stage
and
we
worked
on
them.
Several
people
worked
on
the
right.
It's
a
it's,
a
whole
team
that
was
working
on
this
process
to
get
kubernetes
incubator
and
we
there
were
a
lot
of
answers.
Provided
was
great
working
with
the
cncftoc
to
really
also
challenge
us
in
in
some
areas
and
to
keep
us
honest,
it's
great
to
see
that
and
the
voting
is
open
right.
So
if
you
and
I
did
update
the
slides,
but
I
failed
to
reload,
there's.
B
The
slides,
if
I
share
them
later
on,
feel
free
to
to
look
at
the
pr
on
github
and
the
at
the
cncf2c
to
to
look
at
the
due
diligence
document
and
share
your
feedback
there
as
well.
If
you
have
questions
about
the
project
about
its
governance
model,
then
yeah,
please
share
it
with
us,
I'm
looking
forward.
B
So
where
do
we
go
from
here?
It
was
a
quick
wrap-up
of
what
we
did
right,
and
I
mean
many
of
the
details
from
what
I
just
showed
from
the
high
level
right.
You
will
find
them
in
the
upcoming
sessions
today
and
tomorrow.
Don't
forget
to
sign
up
for
tomorrow
as
well
right.
So
if
you
join
now
well
done
for
tomorrow,
please
sign
up
again
to
make
sure
that
you
can
join
these
sessions
as
well,
and
what
what?
Where
do
we
want
to
go?
What
what?
Where
should
be?
We
could
be
going
right.
B
The
world
is
open
with
many
ways
we
can
take,
or
many
paths,
if
you
ask
me
right,
think
we're
here
to
solve
real
world
problems,
and
I
think
we
saw
also
by
by
reconsidering
what
adopters
we
saw,
people
that
go
all
in
with
containers.
They
finally
start
to
see
the
problem
that
cuba
is
solving,
that's
great
right.
B
If
you
ask
me,
there's
probably
a
limit
to
where
kubernetes
should
scale,
but
regardless
of
what
that
scale
is
and
how
operators
want
to
run
kubernetes,
we
should
follow
right
in
reasonable
bounds
and
I
think
would
be
interesting
to
see
how
far
can
we
go
and
what
makes
sense,
but
we've
got
the
scale
which
is
taking
care
of
that
and
that's
great
because
we
get
trusted
writing
because
people
put
us
into
production,
that's
also
putting
the
burden
on
us
to
be
operational
right
so
that
you
can
operate
us
the
whole
move
of
metrics
and
alerts
and
run
books.
B
B
Ultimately,
we'll
probably
continue
to
close
feature
gaps
right
compared
to
existing
virtualization
management
platforms,
and
maybe
this
year
or
in
the
upcoming
year.
We're
also
going
to
see
that
we're
going
to
lead.
Maybe
the.
B
The
innovation
in
this
area,
because
so
far
to
be
honest,
we
catch
up
with
a
lot
of
features
that
already
existed.
I
think
will
be
interesting
if
we
make
that
flip
right
and
say
all
right,
we've
got
so
many
features.
So
what
is
next
right?
What
can
help
us
in
this
context
and-
and
I
think,
seeing
these
innovations
coming
up
that
will
be
interesting.
I'm
really
curious
to
see
what
it
will
be.
I
don't
know
all
right
and
with
this
this
is
a
small
wrap-up.
B
Before
we
get
to
the
queued
a
I
really
encourage
you
join
the
sessions.
I
think
there's
great
content
in
here
from
integrators
and
from
the
development
side.
That's
great,
and
now
I'm
really
looking
for
some
questions
and
hope
to
provide
some
answers.
A
Okay,
we
have
just
a
couple
of
minutes
for
questions,
so
you
can
ask
a
question
in
the
chat
or
you
can
say.
I
have
a
question
to
ask
aloud
and
I
will
turn
on
your
mic.
B
A
A
Yes,
this
is
bevy,
which
is
a
video
and
online
meetup
platform
hosted
by
the
cloud
native
computing
foundation,
because
we
are
a
cncf
project
and
thank.
B
A
Mistakenly,
like
gpu
yeah,
josh
yeah
in
our
session
and
live
migration
is
later
today,
so
yeah
definitely
ask
that
question
again
exactly.
B
So
what
else
do
we
have
incubation
proposal?
Thanks
for
the
link
tag
down
and
argo
cd
is
the
second
tool
that
was
mentioned
tacton
to
really
do
to
automate
the
workloads
and
argo
cd
is
more
focused
on
which
can
also
help
you
with
infrastructures
code
right
define.
What
you
want
to
have
in
argo
city
is
ensuring
that
it's
getting
deployed
on
kubernetes.
B
I
need
to
think
about
that
question
right.
I
don't
I'm
not
sure
if
it's
the
single
feature,
I
think
it's
it's
more
about
the
project
right.
Where
do
we
want?
Where
do
we
go
right?
Do
we
manage
to
to
stay
to
stick
to
the
pace
we
have
and
at
the
same
time
strive
for
the
stability?
Because
again,
as
I
said
before,
I
think
people
start
to
trust
us
and
we
get
somewhere
and
we
should
live
up
to
that
trust
right.
I
think
we
want
to
be.
B
A
Okay
and
and
with
that
you're
introducing
the
next
two
speakers,
so
we
will
I
get
started
with
howard
jang's
talk
in
just
a
couple
of
minutes
folks,
so
so
stick
around
yep.
Thank
you
very
much.
Thank
you.