►
From YouTube: KubeVirt Community Meeting 2020-12-23
Description
Recording of the KubeVirt Community meeting on 2020-12-23
A
B
B
I
have
a
desire
to
make
it
work
on
arm
64.,
and
the
outstanding
issue
is
3558
in
the
cube
vert
repository
where
it
looks
like
howard
zhang
is
working
on
getting
this
to
work.
There
was
a
update
three
days
ago
that
one
of
the
prs
for
building
the
multi-arch
test
image
of
cube
vert
is
blocked
with
a
lack
of
response
from
one
reviewer.
B
C
B
D
Yeah
yeah
and
this
for
this
pr,
the
the
only
missing
thing
is
that
it's
that
we
well
there's
another
pr
reference
to
it
in
the
project.
Infra
repo
and
it
is
modifying
the
jobs
that
publish
these
images
so
that
they
can
they
can
be
pushed
to
to
play,
because
this
is
in
parallel
with
our
our
migration
from
docker
hub
to
to
quay.
So
this
this
is
the
the
only
thing
that
that
could
be
would
be
required.
D
D
There's
also
one
another
pr
with
a
small
change
that
changed
the
the
flag,
the
default
value
of
the
of
one
flag,
so
that
it
wouldn't
require
too
many
changes
but
yeah.
At
the
end,
all
this
is
more
related
to
to
kuwait,
to
the
immigration
migration
to
quay,
because
it
doesn't
imply
that
we
start
using
this
arm.
64
images.
It
is
more
about
the
migration,
so
it
is,
it
is
not
blocking
the
start
using
the
the
the
multi-arc
images
at
the
end.
C
Sure
is
there
anything,
I
guess
what
are
your
expectations
with
this
just
trying
to
understand
what
you
would
like
to
see
come
out
of
this?
Are
you?
Are
you
hoping
that
we
publish,
I
guess,
arm
64
artifacts
with
our
releases
and
things
like
that,
or
is
it
yeah
for
testing
for
us
to
just
make
it
enable
people
to
build
it?
So
you
all
can
begin
evaluating
it
like
what
what.
B
So
the
goal
is
for
the
artifacts
to
be
built
and
published
and
released
such
that
harvester
can
now
start
testing
with
its
infrastructure,
consuming
those
binaries
and
then
producing
this
infrastructure
for
for
testing
harvester,
just
to
be
clear,
is
in
version
0.1,
so
there's
a
whole
bunch
of
testing
that's
going
to
have
to
go
on
before
it
gets
really
released,
and
here
at
equinix
metal
we're
going
to
be
working
with
them.
I
think
on
integrating
our
tinkerbell
provisioning
tool
with
harvester.
C
E
C
B
B
B
E
B
C
Okay,
it
sounds
like
there's
resources
that
are
potentially
available.
We
just
kind
of
have
to
track
all
this
down.
I,
I
think,
there's
a
path
for
us
to
get
armed
support,
preliminarily
or
just
kind
of
the
initial
support,
merged
and
kind
of
give
us
a
path
to
eventually,
hopefully,
building
artifacts
and
publishing
them
in
the
future.
F
B
I
think
that
might
be
possible
if
the
downstream
harvester
stuff
has
that
same
goal
there
there
may
be
ways
of
of
leveraging
other
projects
to
do
some
of
that
heterogeneous
testing.
But,
as
david
says,
it
seems
unlikely
that
the
first
round
is
going
to
be
heterogeneous.
It
would
make
sense
right,
I
think,
that'd
be
a
desired
goal.
F
C
Technically,
there's
nothing
prohibiting
it
from
working.
It
doesn't
fit
the
pattern
that
we're
doing
with
the
setup
of
clusters
right
now,
so
we're
setting
up
clusters
and
simulating
them
on
the
same
hard
like
one
node
like
we
have
one
node
that
we're
simulating
multiple,
no
like
it's
a
nested
cluster.
So
when
we
talk
about
doing
something
like
a
heterogeneous
cluster,
that
would
be
a
cluster.
C
That's
set
up
in
a
different
way,
maybe
already
exists
that
we
just
execute
our
tests
on,
so
that
setup
phase
would
look
different
than
what
we
have
today,
which
that
that's
a
discussion.
So
there's
some
nice
things
about
the
way
we
do
it
today,
and
that
means
that
every
time
we
we
start
when
these
simulated
clusters,
we
we
start
from
scratch
and
we
tear
it
down
and
we
kind
of
get
a
lot
of
predictability
and
stability
out
of
doing
it.
C
E
C
Would
be
great,
and
also
so
we
have
some
options
here
with
our
ci.
If
it's
just
beneficial
to
begin
introducing
these
heterogeneous
clusters
and
different
ways
of
setting
up
and
tearing
down,
we
can,
we
can
add
these
lanes
and
not
make
them
required.
So
it
would
be
something
where
we
begin
getting:
data
and
understanding
how
our
like
how
stable
it
is,
and
everything
before
we
actually
make
it
where
it's
a
gating
mechanism
for
code
to
get
merged.
So
we
have
some
options
here,
just
pointing
that
out.
A
Okay,
so
to
summarize
initial
arm,
support
seems
to
be
relatively
close,
not
as
a
initially
probably
not
as
a
first-class
citizen,
as
david
mentioned,
and
a
longer
term
goal
would
be
to
work
on
additional
features
like
multi
multi-arc,
that
are
genius
clusters.
Okay,
anything
else
around
that
topic.
B
A
A
A
This
first
ever
keep
birth,
focused
online
event,
two
half
days,
nine
and
ten
of
february,
and
the
plan
is
to
have
two
different
tracks:
two
different
audiences,
one,
more
contributor
oriented
and
another
one
more
user
oriented,
but
preparations
are
just
starting,
and
this
is
a
call
for
participation
to
the
you
know,
early
preparation
as
well.
As
you
know,
content
can
already
be
accepted.
A
C
It's
very
dense
how
much
has
changed
this
year
and
I
think
we
have
the
opportunity
to
share
a
lot
of
really
interesting
things
so
I'll
be
sending
out
reminders.
I
know
this
end
of
the
year.
I
didn't
really
necessarily
expect
to
get
any
content
before
you
know
january
1st.
Just
given
you
know
everyone's
kind
of
slowing
down,
but
I
kind
of
wanted
to
get
the.
I
think
the
goal
here
was
just
get
everyone's
minds.
Thinking
about.
A
Sure
yeah
personally
I
one
thing
that
I
I
have
on
my
to
the
list
of
things
to
check,
but
from
the
recent
release
that
the
removal
of
capnet
admin
knee
requirements
and
well
I
don't
know
this
is
probably
I'm
not
sure
if
this
is
worth
a
session.
But
it's
something
that
I
haven't
checked
yet
and
I
wanted
to
check.
But
anyway,
that
sounds
good.
Yeah.
C
That's
that's
a
really
good
topic.
I
think
the
whole
topic
of
reducing
privileges
from
the
launcher,
pod
and
kind
of
the
vision
moving
forward.
So
the
things
you
just
mentioned
about
reducing
some
of
the
capabilities
are
kind
of
part
of
a
larger
vision
that
absolutely
belongs.
It's
a
topic
as
well,
there's
just
so
many
things.
It's
gonna
be
great
cool.