►
From YouTube: KubeVirt Community Meeting 2023-01-04
Description
Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/
B
C
B
For
this
I
work
for
this
company,
let's
say
that
works
on
backup
entry
store
of
street
food
applications
that
are
deployed
on
kubernetes.
We
have
been.
C
B
Not
queue
but
directly,
let's
say,
but
we
have
customers
that
are
using
Cube
word
and
obviously
we
are
trying
to
protect
those
workloads.
So
that
is
how
we
we
work
with
keywords
on
day-to-day
basis.
I
would
say:
yeah
I
have
been
talking
to
Mike
back
and
forth
and
yeah
I'm
glad
to
be
here.
Let's
see
if
I
can
provide
some
valuable
inputs.
A
A
A
I,
don't
have
a
note
on
who
dropped
this
year.
If
someone
wants
to
go
ahead
and
speak
to
it,.
D
This
this
was
also
an
email
on
the
mailing
list
from
Shelly
Ryka
I.
Don't
think
Shirley's
here,
okay
and
then
honestly
works
with
Shirley
on
the
call.
A
Right
it
looks
like
a
valuable
design
document.
We
should
definitely
follow
up
on
that.
A
C
E
E
or
there's
another
way.
We
could
edit
the
SC
Linux
that
Jed
suggested
in
the
discussion
on
the
pr
at
the
moment.
I
think
we're
looking
at
going
with
the
two
different
providers
so
that
we
can
initially
start
testing
126
and
introduce
us
with
Center
stream
8
and
then
move
on
to
Center
streamline
once
that
becomes
table.
C
A
Andrew
I'm
gonna
tap
you
on
the
shoulder.
Should
we
bump
both
of
these
two
next
week
to
bring
up
again
as
people
are
getting
back
from
BTO
and
such.
D
Yeah,
it
sounds
good
I
mean
people
can
follow
up
here
and
make
whatever
comments.
They
can,
but
hopefully
Shirley
and
Daniel
can
join
us
next
week.
A
All
right,
it
looks
like
we
have
a
few
p.
A
couple
PR's
picked
out.
D
A
D
Just
adding
test
IDs
but
I
don't
be
coming
soon,
so
I
was
dump
them
here.
Okay,
is
it
normal
for,
like
there's
no
issue
description
or
PR
description
of
these?
Is
that
normal,
when
adding
something
very
small
for
a
like
a
test,
ID.
A
All
right
and
Andrew
I
know
it's
holidays,
so
are
there
any
bugs
or
mailing
lists
stuff
that
I
should
go
chase
down,
or
did
you
already
go
through
that.
A
All
righty
then
last
call
then,
if
anyone
wants
to
speak
to
anything
else,
for
agenda
or
open
the
floor.
G
G
G
What
is
when
these
golang
client
go?
Gonna
be
depreciated,
not
any
more
support
who
who
is
taking
care
of
that.
F
So
I
think
this
discussion
was
about
splitting
up.
Originally,
the
client
go
basically,
the
cubert
client
go
repo
contained
the
API
resources
and
the
generated
kind
of
client
Library,
but
that
caused
a
lot
of
problems
for
people
that
just
wanted.
The
API
definitions
like,
for
example,
if
you're
using
the
controller
runtime
library
with
kubernetes,
like
you,
don't
care
about
the
generated
clients,
there's
a
client
that
works
with
anything,
and
you
just
want
the
API.
F
So
we
just
split
the
API
from
the
generated
clients
which
would
allow
people
to
you
know
either
just
import
the
API
and
use
the
controller,
runtime
library,
for
example,
or
import
the
API
and
generate
their
own
clients,
based
on
whatever
version
of
the
kubernetes
library,
they're
using
and
but
the
client.
But
the
Qbert
client
go
library
is
not
going
away,
but
we
use
it
internally,
for
you
know
in
the
keyword
convert
project
but
generally
I.
F
Think
most
people,
unless
you
want
to
you,
know,
be
tied
to
the
same
dependencies
that
we
have
in
Cube
vert.
You
should
probably
use
the
API
the
keyword,
API
repo
and
generate
your
own
client
or
use.
You
know
the
clanco
library
I.
G
I
today,
I'm
using
the
golang
and
I
plan
to
move
back
to
the
the
with
your
recommendation:
okay,
okay,
the
goal
line
gonna
be
depreciated,
they
did
they're
gonna,
be
stop
it
to
be
supported.
F
No,
it's
not
now
the
client
go.
Repo
is
not
going
to
go
anywhere.
F
Okay,
yeah
yeah;
no,
it's
still,
it's
still
gonna
exist
and
still
gonna
be
used.
You
know,
as
far
as
I
know,
for
the
foreseeable
future,
in
Cube
vert,
it's
just
yeah
and
yeah.
You
can
still
use
it,
it's
not
going
anywhere,
but
it
would
probably
be
best
to
not
tie
yourself
to
our
dependencies
and
just
use
the
API
repo
directly.
D
In
which
case,
if,
if
no
one
else
has
anything
to
add
we'll
call
it
there
I
don't
see,
anything
else
has
been
added.
So
yeah
I'll
give
the
customer
a
countdown
of
a
three
two
and
one.
Thank
you.
Everyone
for
joining
and
we'll
see
you
next
week.