►
From YouTube: KubeVirt Community Meeting 2020-03-04
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
B
And
yeah
I
were
talking
in
the
select
channel,
but
I
found
that
I
was
a
story,
no
Gaede
in
a
story
on
top
of
it,
and
then
I
found
that
there
were
some
selinux
errors
and
that
seminar
was
not
with
favor
a
chorus.
We
Python
it's
it's
ship
already,
but
I
think
as
I
could
see
in
the
okay
the
repository
it
won't
be
ship
as
well
in
the
future.
So
maybe
we
can.
We
will
have
some
issues
with
look.
A
At
the
code
after
you
had
brought
this
up
and
I
realized
that
not
only
in
the
process
of
applying
types
for
the
vert
launch
or
not
process
the
default
one
we
apply.
We
also
check
for
labeling
and
do
some
relabeling
of
files
and
that,
of
course,
we're
using
us.
He
manages
well
for
that,
and
so
there's
several
different
places
where
we
rely
on
the
existence
of
that
binary.
I
thought
that
it
would
have
been
shipped
with
vert
handler
am
I
wrong
about
that,
because
I
would
have
thought
it
would
have
been
in
the
container.
B
I
paste
the
error
and
never
was
saying
that
Tim
and
that's
when
was
not
done
day
on
the
operating
system.
Once
once
I
installed
a
the
policy
called
util
package,
everything
was
working
fine
again
on
the
node
itself.
Yeah
I
know
that
but
yeah
it's
an
immutable
operating
system,
so
you
have
to
reboot
the
server
and
probably
when
you
update
the
operating
system
it
one
bishop
again,
so
we
would
have
to
reinstall
it.
A
Unfortunately,
Roman
is
unwell
and
unable
to
join
us
today,
so
he
can't
speak
for
himself.
I,
don't
know
the
state
of
that
PR
per
se.
You
do
have
a
link
there,
so
we
can
follow
that
after
or
even
right
now,
but
the
yeah
I
really
I'm,
still
coming
back
to
that
Bert
handler
is
the
the
entity
that
does
the
SE
manage
different
activities
as
a
privileged
process,
but
it
should
have
been
using
its
own
file
system.
So
I'm
really
surprised
that
doing
something
to
the
host
affected.
It
so
I'm
curious
about
how
that
played
out.
C
For
this
year
we
have,
we
were
planning
to
use
facilities
that
were
rented
for
the
OpenShift
Commons
gathering
that
they
want
to
put
a
zero
events
around
Cape
Con.
Last
week,
though
they
well
this
week
anyway,
they
they
just
due
to
this
virus
outbreak
thing.
They
change
the
operative
Commons
addition
to
a
beautiful
event,
meaning
that
there
are
no
physical
locations
anymore.
So
we
are
working
to
find
an
alternative,
so
yeah.
D
A
A
A
However,
we're
having
trouble
with
Travis
it's
just
a
transient
networking,
they're
still
working
through
that
I,
just
you
know,
need
to
rebuild
a
few
times,
but
once
that's
done,
we
will
have
the
build
artifacts
attached
to
github
and
can
actually
do
an
official
release,
but
it
is
tagging
the
repo
so
we're
somewhere
between
twenty
six
point,
one
and
twenty
six
point
two
right
now
and
as
far
as
the
changes,
basically,
stability
of
bug
fixes
nothing
earth-shattering.
So
any
questions
on
that.
E
No,
it's
just
a
remark
on
the
on
a
similar
side.
We're
also
planning
to
do
release
a
little
bit
late
for
you
about
for
God
about
it,
0:27,
which
I
tected
the
first
release
candidate
and,
if
all
goes
well-
and
nobody
is
screaming
here-
and
it
might
become
the
release
for
this
money
in
a
few
hours
or
tomorrow
or
Thursday
and
there's.
A
E
E
A
Well
then,
we
do
it
this
week,
let's
get
it
up.
A
That
is
not
expected.
I
will
update
the
what
he's
referring
to
is
in
the
github
releases.
Page
admins
can
see
if
releases
a
pre-release
or
if
there
are
official
releases,
and
we
just
didn't
complete
the
process
and
hit
the
button.
So
apologies
for
that.
We
will
clean
up
our
repo
and
it
will
be
showing
up,
as
the
official
latest
release
soon.
E
E
E
What
could
be
interesting
items
look
at
in
the
future
and
to
see
some
how
we
can
bring
this
agenda
into
into
this
forum
because,
like
we
have
individual
contributors
which
are
fixing
their
stuff
and
providing
patches
read,
it
is
one
of
the
largest
ones,
but
we
have
other
stakeholders
right
were
contributing
patches
and-
and
I
would
just
I-
I
would
like
to
see
that
we're
making
more
transparent.
Who
is
you
know,
who's
working?
What
who's
interested
in?
What
so
I'll
see?
A
D
Fabian's
been
talking
to
air
chang
over
on
our
side
about
some
of
this
stuff.
Also,
we'll
have
we'll
probably
have
some
proposals
for
y'all
to
see
as
far
as
what
we
think
are
some
improvements
with
additional
layers
of
armor
and
what
what
the
stuff
we're
doing.
So
we
have
a
kind
of
like
a
our
own
hardened
version
of
Kenya.
That
is
proving
a
little
bit
challenging
to
incorporate
into
the
Qbert
kubernetes
set
up.
A
D
D
So
we've
kind
of
like
moved
our
are
like
engineer,
workstation
workloads
to
the
cloud,
but
we
still
have
a
bunch
of
like
third-party
stuff
that
we
have
to
run
that
we
can't
put
on
for
an
introduction
and
that's
that
stuff
is
here
to
stay
so
we're
looking
to
move
off
of
unity
and
the
Python
2
to
3
conversion,
stuff
kind
of
pushed
us
over
the
edge
there
to
start
looking
for
other
stuff.
So
Cooper
seemed
to
be
the
place
to
be.
As
far
as
modernizing
the
virtual
machine.
You
know
question.
E
Somewhat
biased,
no
that's
interesting,
I
think
I
mean
the
the
benefit
here.
Is
that
you're
really
following
to
the
use
case
of
Qbert
right,
so
we're
also
focusing
on
enabling
legacy
world
oats,
which
sometimes
have
bought
requirements
on
the
underlying
VM
ABI,
but
I
would
actually
take
a
step
back
because
what
the
zoo
security
things
we've
been.
E
Looking
at
that
recently
and
I
think
I
mean
Eric
pointed
that
out
right
that
we
have
like
what
Arabic
rules
we've
granted
too
many
permissions
and
I
mean
we
progress
on
that
side
and
Vladek
and
jet,
which
are
around
here
they're,
looking
currently
at
containing
the
launcher
a
little
bit
more.
So
what
you
miss
running,
and
especially
looking
at
the
ethylene
oxide,
but
it
sounds
like
you're
more
interested
in
Fr,
more
instead
of
acid
onyx
yeah.
D
So
we
already
have
a
bunch
of
experience,
hardening
virtual
machines
with
AB
armor
and
we've
kind
of
a
few
years
back.
We
we
we
forked,
can
you
we
like
completely
stripped
it
down
right
and
it
saved
us
a
lot
of
time
in
the
long
run
and
one
of
the
like
between
the
stripped
down.
Can
you
the
lockdown,
app
armor
profiles
and
doing
things
like
you
know,
running
every
single
instance
as
its
own
user,
that
type
of
stuff
we
saved
ourselves
a
lot
of
time
in
it.
D
Just
we
could
ignore
the
vast
majority
of
of
Kenya
vulnerabilities
and
it
just
it
saved
us
a
lot
in
the
long
run
to
do
that.
Work
and
we'd
like
to
kind
of
like
take
that
stuff.
That's
already
like
that,
you
know,
are
sparse.
A
cop's
folks
are
already
happy
with
right
and
kind
of
like
okay,
we're
introducing
all
this
new
infrastructure.
You
know
they're
worried
about
it,
we're
kind
of
a
big
target
right,
so
they
worry
about
these.
D
You
know
the
third
party
stuff
that
we're
buying
so
part
of
convincing
them
that
you
know
that
deploying
Qbert
was
a
good
idea
was
kind
of
like
okay.
We
have
this
security
model
that
we
know
you
like
already
right,
we'll
kind
of
like
move
this
to
the
new
stuff
right
that
way,
everybody's
happy
so
app
armor
was
part
of
it.
It's
not
that
they
couldn't
be
convinced
to
do
something
different.
It
was
just
real
like
we
already
knew
that
they
would
they
liked
our
former
set
up.
D
So
it
was
much
easier
from
like
a
development
and
political
standpoint
to
kind
of
like
pushed
us
along,
so
we
can
get
the
green
light
on
developing
this
stuff,
so
we're
in
the
process
now
of
kind
of
figuring
out
the
right
way
to
deploy
this
and
integrating
it
with
our,
like
instance,
and
node
lifecycle
management,
so
yeah
we're
gonna,
think
of
it
right
now.
We
think
we'll
probably
have
about
3000
virtual
machines
running
by
the
end
of
the
year
on
it.
So
it's
not
a
tiny
deployment,
it's
not
huge,
but
it's
good.
E
That's
interesting,
yeah
and
for
sure
something
to
continue
on
and
because
I'll
be
interest
or
I.
Think
more
here
will
be
interested
to
you,
but
you
know
your
insights
about
the
security
status
of
the
launcher.
I
mean
if
I'm
or
will
be
good,
to
contain
possibly
qumu,
but
there's
more
and
I
mean
we
especially
here
at
reddit.
Currently
wonder
about
you
know:
how
can
we
contain
the
launch
range
and
a
little
more
so
getting
some
additional
thoughts
from
your
side
will
be
helpful.
They're,
nice,
oh.