►
From YouTube: KubeVirt Community Meeting 2021-02-03
Description
Recording of the KubeVirt community meeting on 2021-02-03
A
Okay,
welcome
everyone.
This
is
the
kibber
community
meeting
on
3rd
of
february
2021
as
a
reminder
feel
free
to
add
yourselves
to
get
in
this
list
in
the
meeting
minutes
document
and
also
again
as
a
reminder,
if
you
don't
have
edit
access,
I
see
a
couple
of
anonymous
people
you
just
have
to
log
in
as
identify
yourselves
as
a
member
of
the
keeper
dev
group.
If
you're
subscribed
to
that
group,
you
have
edit
access
automatically
with
that
said,
let's
jump
in
so
far.
A
B
B
So
the
question
came
up
regarding
whether
one
or
not,
we
want
to
follow
the
same
scheme
that
we
have
with
what
the
website,
which
is
we
do
our
work
in
a
feature
branch
and
then
merge
to
source,
and
then
automation
handles
the
rhetor,
the
rendering
from
the
source
branch
and
renders
to
the
master
branch
pep.
And
I
discus
having
a
discussion
yesterday.
B
We
think
we
like
folks
to
work
in
a
feature
branch
and
then
merge
to
master
and
then
automation
handles
taking
code
in
the
master
branch
and
rendering
to
a
another
branch
that
will
be
served
by
github
pages
by
default.
Github
pages
serves
gh
pages
branch,
and
so
I
think
that's
what
we
would
like
to
use-
and
we
just
have
like
to
have
one
more
consensus
from
the
community.
A
Yes,
I
I
would
even
go
beyond
that
and
actually
ask,
does
anyone
have
any
objection
to
this?
I
guess
the
only
concern
here
was
that
there
is
another
repo
on
the
cuber's
work
at
the
moment,
which
is
github
pages
and
that's
the
the
website.
Keyboard.Io
and
repo
uses
a
branch
called
source
for
the
source,
and
you
know,
keep
if
we
keep
using
master
here
that
that
would
be
kind
of
inconsistent.
A
B
A
A
There's
a
link
here
in
the
meeting
minister,
but
let
me
copy
that
to
the
chat
as
well
just
one
second,
so
the
the
schedule
for
the
different
sessions
was
published.
Yesterday,
it's
available
here
great
sessions,
great
content,
several
sessions,
I
mean
we
target
both
users
and
contributors.
So
you
will
see
each
of
the
sessions
I
mean.
I'm
sure
you
will
find
a
few
that
are
interesting
for
you
so
feel.
Free
to
register
and
attend
registration
is
from
the
same
page.
Everyone
attendance
is
free.
C
D
C
F
C
F
F
A
A
A
You
know
how
to
contribute
and
explain
precisely
this,
this
policy
doc
and
by
the
way
chris,
you
might
want
to
add
a
plug
here
on
the
pr
that
you
have
open
about
this
topic,
but
anyway,
so
that
the
plan
was
to
have
initial
plan
was
to
have
a
session
about
this
cover,
how
to
contribute
and
discuss
all
those
processes.
However,
we
did
receive
many
good
content
proposals,
session
proposals
and
well,
and
we
had
to
make
a
choice,
so
we
actually
had
to
reject
a
few
proposals.
A
So
one
of
the
proposals
that
was
not
actually
a
formal
proposal,
but
it
was
kind
of
a
general
interest
session.
Was
this
one,
and
this
was
dropped
in
favor
of
proposals
contributed
by
by
well
by
the
community
that
sounded
more
interesting,
that
this
one
does
that
make
sense
we
did
keep?
We
did
keep
a
couple
of
sorry
just
to
complete.
We
did
keep
two
two
sessions
of
this
type
of
predefined,
hopefully
general
interest
sessions,
which
are
actually
three
well.
The
first
one
is
the
welcome
session.
A
So
those
are
the
sessions
that
we
kept
like
by
default,
but
how
to
contribute
session
was
dropped
from
the
schedule,
even
if
we
extended
actually
the
schedule.
For
you
know
we
had
two
more
hours
and
initially
planned
to
accommodate
for
more
sessions,
and
we
also
asked
the
presenters
to
spring
the
session,
so
they
are
all
limited
to
half
an
hour
total.
So
even
then
we
couldn't,
we
didn't
have
space
for
all
that
content.
A
A
If
not,
we
will
switch
to
bug
scrub
for
about
20
minutes,
which
is
what
we
have
been
doing.
The
past
few
meetings
attendance,
the
regular
that
ends
the
the
regular
meeting,
but
attendance
is
encouraged
to
anyone
who
wants
to
contribute
to
that
bug,
scrubbing
and
better.
I
see
your
thing
you're
here
you
you
want
to
drag
that
sure.
A
G
All
right,
the
first
one
was
reported
two
days
ago
about
an
issue
with
networking
which
race
that
may
be
related
to
srv.
But
I
went
into
this
and
saw
that
it's
just
a
confusion
around
the
masquerade
binding
and
the
fact
that
it
assigns
this
look
like
the
address
to
the
guest.
So
I'm
waiting
for
the
reporter
of
this
to
answer.
If
that's
all
right.
G
I
E
D
I
I
A
G
I
H
B
G
G
G
E
G
D
G
A
Yeah,
I
just
let
the
note
that
I
think
I'm
talking
from
memory,
but
I
believe
that
our
colleagues
in
china
that
have
a
community
meeting-
I
think
they
mentioned
that
issue
and
they
are
reviewing
that.
So
I
think
I
saw
that
on
their
reading
notes
so
yeah,
let's,
let's
leave
it
as
this
and
and
see
if
feedback
comes
in
next
week
or
later,
thanks
by
the
way,
I'm
sorry
to
interrupt.
But
I
just
realized
something
sorry.
Next
week
the
cuber
summit
is
happening,
so
I
should
have
added
an
note
here.
H
H
B
G
J
G
G
G
G
G
G
G
E
G
G
E
G
B
G
E
D
G
G
G
K
G
G
G
G
G
I
I
G
I
H
A
G
D
G
Yeah,
I
guess
you
get
what
you're
getting
at,
but
it's
like.
We
want
to
revisit
that,
those
that
were
back
scrubbed
anyway
to
see
if
there
was
any
update.
I
think
I
I
was
trying
to
avoid
like
labeling
and
bulls
and
all
of
this
to
not
bring
too
much
process
into
this.
If
we
can
handle
it
like
naturally
but
yeah,
maybe
it
would
be
a
terrible
idea
to
have
some
system,
I'm
just
not
sure
how
to
build
the
system
or
what
should
the
process
look
like.
A
Maybe
one
one
option
that
would
go
beyond
the
box
chrome
itself,
but
I
don't
know
if
the
project
has
considered
using
some
sort
of
priority.
Labels
of
I
think
other
kubernetes
projects
do
have
levels
that
assign
a
priority
for
issues,
and
you
know
one
of
the
goals.
Let's
say
then
one
of
the
goals
of
the
box
crop
becomes
make
sure
that
the
labels,
those
priority
labels,
are
correct,
and
then,
if
they
are,
you
you
can
skip
a
side
effect
is
that
you
can
magically
identify
which
has
been
triaged
or
not,
and
what
status.
A
G
A
Another
process
yeah
I
mean,
and
I
should
clarify
that
those
priority
labels
don't
necessarily
like.
For
example,
there
is
a
priority
label,
something
like
a
waiting
information
or
something
like
that,
and
you
know
there
have
been
a
couple
of
instances
today
of
issues
that
are
waiting
for
evidence
or
something
like
that
that
then
you
can
easily
skip.