►
From YouTube: KubeVirt community meeting 2021-03-03
Description
KubeVirt community meeting 2021-03-03
A
A
B
Okay,
I
should
be
seeing
my
firefox
one
down
with
the
meeting
minutes,
so
this
is
a
continuation
of
last
week.
We'll
take
a
few
minutes
to
continue
the
discussion.
The
little
bullet
point
out
of
this,
so
I
added
more
details
and
to
the
design
dock
and
for
the
bulk
api
discussion
and
the
design
doc
has
linked
in
there
all
right
so
I'll
switch
over
to
it.
So
I'm
not
going
to
go
through
all
the
details.
I
filled
out
a
number
of
things.
B
I
kind
of
I
attempted
to
mock
just
some
of
the
apis
just
to
like
and
then
put
some
examples
in
just
to
kind
of
get
an
idea,
but
if
folks
can
read
through
that
in
their
own
time
and
I'll
probably
what
I'll
do
is
I'll
send
this
out
in
the
mailing
list
too.
Just
so
it
gets
far
and
wide
and
we
can
get
some
feedback
that
way.
So
mainly
what
I
want
to
discuss
is
that
I,
I
briefly
touched
on
last
time
kind
of
the
implementation
phases.
B
I
guess
if
you
will
so
like
the
I
could
I
haven't
listed
here
in
the
high
level
features
and
have
six
total,
so
two
changes
that
I
made
since
last
time
was.
I
added
this
called
unique,
vm
metadata,
so
this
wasn't
here
before,
and
so
the
idea
here
that
if
I
want
to
create
100
virtual
machines
and
then
I
want
to
add
unique
metadata
to
each
of
them
and
the
idea
is
kind
of
along
the
lines
with
like.
B
I
was
looking
at
the
reading
through
the
content
section
and
there's
this
section
at
the
bottom
called
future
metadata.
Server
based
data
sources
and
kind
of
that.
I
I
might
understand
kind
of
the
problem
here
is
that
you
have
cloud
in
it
that,
and
you
have
a
lot
of
vms
and
you
want
to
sort
of
dynamically
populate
the
metadata
of
a
cloud
in
it
for
all
these
virtual
machines.
B
So
that's
kind
of
the
the
example
and
that's
the
only
one.
I
reference
in
the
the
section
that
they
talk
about
it,
but
I'll
go
to
that
in
a
second.
The
second
one
is
detach
so
last
time
somebody
become
about
to
detach-
and
I
think
it
actually
kind
of
makes
sense
to
be
in
its
own
phase,
which
I
think
it's
sort
of
something
that
has
a
lot
of
components
to
it.
C
C
C
B
C
B
Yeah,
so
so
this
is
where
I
want
to
go
at
least
with
this
is
that
is
that
the
assumption
would
be
an
assumption
would
be
made
that
since
you're,
since
there's
a
there's
a
template,
a
virtual
machine
there's
will
be
a
reference
to
a
secret
and
the
way
that
I
kind
of
do
it
is.
I
have
a
label
here
so
in
case
any
secret
with
a
label.
B
So
I'm
like
exercising
strict
control
over
it
could
be
the
exact
amount
like
100
secrets,
or
there
could
be
just
10
and
and
just
my
phone
would
just
kind
of
like
cycle
through
them,
and
I
mean
that
would
be
error.
So
I
I
think
it
to
me
when
I'm
getting
the
creation
or
of
any
sort
of
the
unique
metadata
would
be
an
external
step.
B
B
C
B
Yeah
yeah
yeah,
so
it
would
be
well.
I
would
think
it
would
be
like
a
robin
robin.
I.
I
think
we
don't
want
to
do
random
just
because
we
want
uniqueness,
so
we
would
just
kind
of
loop
through
the
list
and
and
just
keep
allocating
them
until
we
run
out
of
secrets
to
allocate
them.
We
just
keep
going.
If
there's
still
more
virtual
machines,
then
do
the
loop
again.
B
Does
you?
What
do
you
think
about
the
I
guess,
the
the
concept
of
sort
of
common?
I
call
it
kind
of
like
I
call
here
common
overrides
or
something
like
distribute
data.
Is
this
something
that
you
could
be
a
common
pattern?
I
mean
you
mentioned.
Ssh
keys
sounds
like
that,
might
also
be
an
area
that
this
could
be
used.
It's
not
something.
I
specifically
have
an
example
for,
but.
C
C
What
the
problem
was
that
you're
trying
to
solve
whether
it's
application,
specific
something
that's
unique
to
your
use
case
or
if
it's
something
that
we
can
tackle
more
generically
and
it
does
sound
like
it's
totally
application
specific
yeah.
I've
never
even
encountered
this
pattern
before
it's
really
interesting,
I'm
not
sure
what
to
think
of
it.
Yet
I'd
have
to
okay
yeah,
even.
A
B
B
So
it's
essentially
like
a
way
of
of
making
it
so
that
I
don't
have
to
say
say
have
like.
Let's
say
I
had
100
virtual
machines
and
this
in
the
different
vm.
I
wanted
10
with
a
certain
skew
amount
90
with
another.
This
case
would
be.
I
would
have
to
have
100
different
overrides,
because
each
one
is
going
to
be
unique.
It's
sort
of
a
way
to
like
pull
all
that.
B
D
B
I
don't
want
to
like
like
because,
because
to
me
once
they
start
asking
users
to
like,
say
we're
to
ask
user
to
write
all
these
unique
things
you
know
now
you
know
what's
to
stop
someone
to
say
like.
Oh
I,
why
can't
you
support
this
too
and
it's
kind
of
override
and
and
like
I
don't
know,
I'm
trying
to
like
make
like
very
clear
barriers
so
that
it's
there
isn't
like
sort
of
a
language
to
define
like
it's
just
like
okay,
this
is
all
or
nothing,
here's
what
I
want
to
do.
B
C
I'm
thinking
about
this
a
little
further
and
I'm
unsure.
So
what
I
would
typically
see
is,
if
you're
wanting
to
distribute
something
unique
to
a
virtual
machine.
What
I've
seen
a
pattern.
I've
seen
in
the
past
is
that
every
virtual
machine
gets
the
exact
same
cloud
in
it
and
they
would
reach
out
to
a
service
on
first
boot
to
retrieve
whatever
unique
token
or
whatever
they
need.
C
D
I
just
wanted
to
say
that
I
mean
this
is
exactly
what
I
wanted
to
to
mention
here,
because
you
are
talking
about
application,
specific
and
anything
generic,
but
we
are
managing
in
the
project
in
flux,
infrastructure
of
virtual
machines.
We
are
not
trying
to
distribute
things
inside
the
vm,
I
mean
unless
it's
something
very
related
to
the
infrastructure.
So
so
there
are
tools
to
do
that,
which
you
can
you
can
use
it
like
what
david
just
said.
B
C
E
A
C
Specific
topic
ryan:
would
you
mind
making
a
mailing
list
post
just
about
the
unique
metadata,
and
then
I
think,
I'm
probably
going
to
follow
up
with
trying
to
understand
whether
this
can
be
solved
reasonably
with
an
external
service
or
if
this
is
something
generic
that
belongs
in
cubert.
So
since
it's
so
unique,
that's
like
the
thing
that
signaled
to
me
that
maybe
it
doesn't
belong
in
kubert,
but
I'm
trying
to
explore
it
a
little
bit
further
and
make
sure
them
right.
A
A
F
C
F
D
F
F
F
F
C
Yep,
so
it
would
be
a
workflow
something
it
might
even
have
to
be,
since
it's
it's
a
multiple
step,
workflow,
it's
increasing
both
the
pvc
size
and
then
expanding
the
image
inside
of
it,
which
can
take
different
forms.
That
seems
like
it
belongs
in
cdi.
It
would
be
some
sort
of
you
declare.
You
want
to
expand
this
volume
and
a
cdi
controller
would
would
then
act
on
that
begin.
I
I'm
spitballing,
I'm
making
that
up
as
I
go.