►
From YouTube: OKD Working Group 2020 07 21 Full Meeting Recording
Description
OKD Working Group 2020 07 21 Full Meeting Recording
https://okd.io
B
B
For
the
august,
17th
live
demoing
of
each
of
the
different
platforms,
okd4
running
on
that
and
set
it
up
so
I'll,
send
an
invitation
and
then
a
note
to
the
mailing
list
to
get
people
to
sign
up
and
volunteer
for
demos
demo
sessions.
Does
anyone
have
an
idea
about
how
long
each
of
those
sessions
should
be?
Should
they
be
a
half
an
hour
or
one
hour?
Does
it
take
a
full
hour
to
deploy
okd,
say
on
gke
or
and
talk
about
it.
D
One
hour
is
generally
the
case.
I
mean
it
takes
twelve
and
a
half
minutes
just
to
deploy
a
three,
not
twelve
and
a
half
twelve
now
for
one
node,
a
single
node,
but
about
32
minutes
for
it
for
the
three
node
reduced
setup,
okay,
yeah
I'll
I'll,
actually
test
a
a
bare
metal
mirrored
install
I'll
time
it.
B
So
that
that's
my
goal
and
I'm
sticking
to
it
for
now
and
then
I'll
create
a
landing
page
for
that
sort
of
a
la
the
openshift
commons
gatherings
and
we
can
and
I'll
but
I'll
do
it
off
of
okd.io
as
opposed
to
off
of
commons
gap.
The
common
site
and
people
can
come
as
they
wish.
So
each
hour
would
have
to
have
like
the
first
five
minutes
might
have
to
be
what
is
okd
by
each
of
the
the
persons
just
a
little.
B
You
know
a
couple
of
minutes
about
what
it
is
and
then
go
into
the
demo
and
we'll
then
we'll
have
the
end
of
the
day,
and
this
is
what
diane
being
sneaky
we'll
have
you
know
six
or
seven
videos
of
each
of
these
topics
to
add
for
people
to
use
from
the
website.
So
I
am
my
my
motto:
is
renew
reuse,
recycle
content
everywhere
and
that's
really
what
I'm
going
for
so
vadim.
You
should
be
back
in
now.
Vadim-
and
I
see
christian
is
here
so
how
about?
A
A
A
E
Add
I
don't
think
so.
Honestly,
I've
been
head
down
in
the
code
for
the
past
couple
of
days
ever
since
we
got
ga
out
and
yeah,
not
much
more
to
say
from
my
side,
I'm
I'm
definitely
interested
in
feedback
from
from
folks
that
have
installed
it
and
yeah.
Maybe
one
thing
we're
I'm
we're
in
the
middle
of
migrating,
the
ocp
installer
to
ignition
spec
3.
E
So
very
soon,
we'll
have
redchat
core
os
with
ignition
v2
that
supports
spec
3
and
then
the
installer
will
be
the
ocp
and
okd
installer
will
will
already
be
much
more
aligned
than
they
are
right.
Now
the
mco
we
have
successfully
merged
together
so
from
4.6
on
there
will
be
just
one
branch
avadim
and
I
are
currently
working
on
figuring
out
how
to
test
both
ocp
and
okd
from
the
same
branch
there,
but
yeah.
E
We
will
figure
that
out
and
right
now,
obviously
we're
in
okd
4.5
at
ga
and
just
wanted
to
say
I'm
very
happy
about
that.
Yeah
thanks
everybody
who,
thanks
for
team
thanks
diane
from
my
side,
great
work
and
especially
diane
for
for
keeping
us
on
edge
with
this
and
vadim
yeah.
For
for
just
doing
lots
and
lots
of
work,
there.
D
A
This
graph
counts
active
life
clusters.
Ci
is
doing
the
very
same
thing
like
creating
crazy
amount
of
clusters.
Meanwhile,
so
we
can
see
some
jitter.
I
think
we
would
come
up
with
a
better
graph
showing
if
a
cluster
has
lived
at
least
a
day,
we'll
keep
it
in
the
stats.
But
that's
something
we
that's
something
we
should
invest
in
on
ocp
side
as
well.
D
B
All
right,
I
flashed
it
up
on
the
screen
for
a
minute,
but
I
just
was
going
to
share
as
well
the
and
I'll
try
sharing
again
now
I
apologize.
I
need
to
show
everybody
that
right
off
the
bat.
The
survey
that
I
went
I
sent
out
about
you
know.
Adoption
really
was
meant
to
just
sort
of
get
us
a
baseline
right
now,
and
so
I
can
redo
it
in
six
months
or
three
months
or
whatever
in
a
cadence.
B
So
we
can
sort
of
watch
this
going
up
and
I'll
share
the
the
results
with
it
here
I
haven't
done
any
really
deep
things,
but
some
of
it's
pretty
obvious
and
I
think
a
lot
of
thank
you.
A
lot
of
the
responses
came
from
people
in
the
working
group,
so
which
is
natural,
but
there
are
a
few
outside
folks
as
well,
and
that's
pretty
pretty
a
lot
of
it
is
we're
just
it's
very
early
to
stuff,
and
what
I
was
really
interested
in
is
what
people
were
looking
for
in
terms
of.
B
You
know
what
we
can
do
as
a
working
group
to
help
them
and
maybe
developer
workshops,
operational
workshops
and,
as
always,
better
documentation
on
the
ocp.
On
the
openshift
side.
We
are
also
seeing
a
lot
of
asks
for
help
for
migrating
from
three
to
four.
So
that
didn't
surprise
me
at
all-
and
you
know
there
was,
you
know
some
basic
stuff.
B
The
lack
of
a
dual
stack
support
was
a
couple
of
issues
yeah,
but
it's
really
still
pretty
pretty
early
days
and
if
you
guys
saw
my
tweet
with
the
survey
in
it,
if
you
could
retweet
that
on
your
twitter
thing,
so
we
can
get
more
people
in
in
the
door.
But
it
is,
you
know,
I'm
not
surprised
other
than
the
fact
that
the
colors
don't
coordinate
with
the
words
here
with
the
graphics,
but
I
can
fix
that
too.
B
B
It's
very
interesting
to
try
and
figure
out
who
is
actually
using
it
out
there
in
the
universe,
so
the
surveys
will
just
keep
repeating
and
if
there's
other
questions
that
I
should
be
asking
please
let
me
know
I
base
this
on
one
that
we
sent
out
to
some
openshift
folks,
so
I
could
compare
openshift
folks
to
okd
folks
so
that
that's
my
bit
for
the
day,
but
there's
nothing
here.
Nothing
here,
hugely
shocking.
From
my
my
point
of
view.
B
The
thing
that
I
I
know
I
heard
from
joseph
post.
That
was
some
conversations
about
the
operators
that
were
available
only
for
ocp
opera
operators
and
I'm
wondering
yes,
if
we
wanna,
if
joseph
you
wanna
express
what
you
need
here,
and
maybe
we
can
figure
out
if
that
is
this
working
group
or
another
set
of
resources
that
we
need
to
attach
to
that
project.
C
I
was
talking
with
vadim
about
the
service
mesh
operator.
There
is
a
substitute
called
maestra,
but
I
I
don't
know
how.
How
often
does
it
it
is
updated.
I
I
it's
a
little
bit
behind.
In
its
version
behind
of
c
service
mesh
operator
from
red
hat,
the
serverless
operator
is
not
available
in
a
community
version
and
I
think
it
would
add
lots
of
value
to
okd
if
they
were
available
yeah
because
they
are
based
on
open
source
projects.
D
So
one
thing
that
kind
of
threw
me
for
a
loop.
I
you
know
I
looked
at
what
the
operator
hub
presented
to
me.
It
was
there's
a
it's
kind
of
empty
there's,
not
a
lot
available
to
you
and
that's
actually
more
depressing
and
disheartening
than
you
than
I
than
I
imagined
it
would
be
because,
like
during
the
betas
and
the
nightlys,
and
I've
played
with
a
few
of
them
here
and
there
like
it,
looks
incredibly
full
and
incredibly
functional
like
you
could
do
so
much
and
now
you
can
basically
do
nothing.
E
E
E
Definitely
so
I
think
the
the
duke
verge
operator
just
merged
the
pr
last
week
to
make
it
work
on
on
okd,
so
I'm
not
sure
whether
they'll
be
promoting
that
to
operator
hub
right
away
or
whether
it
may
already
be
there,
but
yeah
that
should
technically
technically
work
now
and
we'll
follow
up
to
make
the
keyboard
operate.
Anti-Serverless
maestra
operator,
well,
serverless
and
istio
operators
are
also
available
there
yeah
definitely.
I
agree.
That
is
a
very
good
use
case
and
we
should
deliver
on
that.
C
E
A
D
A
This
discrepancy
is
also
different
from
ocp,
where
we
package
and
we
can
prepare
a
custom
version.
So
in
the
end
we
had
a
chat
with
people
from
operator
hub
and
they
said
that
it's
mostly
a
problem
of
time
of
the
team.
They
are
unable
to
manage
three
different,
potentially
different
streams
of
their
operator,
and
we
are
working
with
them
how
to
introduce
community
who
would
support
kubernetes
versions,
who
would
support
okidi
and
so
on.
It's
a
very
tricky
problem
and
we're
just
trying
our
first
steps
with
cube,
weird
and
image
streams
on
fedora.
A
B
Yeah,
I'm
not
quite
sure
which
which
person
you
were
talking
to
and
I'm
glad
you
were
you've
already
talked
yeah
and
I
really
want
to
make
that
distinction
operator
hub.io
is,
is
kubernetes
generic
and
so,
and
a
lot
of
them
haven't
been
tested
and
so
and
there
there
are
thousands
more
out
there.
I
just
haven't
done
a
lot
of
outreach
to
populate
it
yet
because
some
of
the
there
isn't
a
lot
of
automation
behind
operatorhub.io.
B
To
be
quite
honest,
there
are
humans
and
and
testing
them,
and
you
know
there.
There
is
no
certification
process
there
at
all
and
really
what
operator
hub.io
is
is
basically
just
a
catalog
that
you
know
you
could
stand
up.
Anyone
could
stand
up
their
own
catalog
and
put
a
ui
around
it.
So
it's
a
pretty
simple
website.
D
B
E
So
that
would
be
helpful
for
us
to
prioritize
because
we
want
to
get
there
eventually,
so
we'll
just
have
to
keep
bugging
the
teams
and
maybe
put
some
of
our
own
work
hours
into
this,
but
there's
many
operators.
So
if
you
could,
please
add
all
the
operators
you
want
to
see
which
are
you
know
the
most
urgent
for
you
into
that
list.
We
that
that
would
be
helpful.
B
D
D
Okay
that'll
help
yeah
because
I'm
I'm
now
starting
to
look
at
what
it's
gonna
take
to
do
the
thing
to
like
replace
her:
oh
openshift,
origin,
three
cluster
with
okd4,
and
so
it's
gonna.
It's
gonna
be
interesting,
so
the
preliminary
preliminary
exploration
has
begun
for
doing
it
for
reals,
so
that'll
be
helpful
because
this
time
we
want
to
do
it
kind
of
right
rather
than
what
we
did
now,
and
I
don't
I'm
not
proud
of
what
we
have
right
now.
C
And
serverless
yes,
but
serverless,
I
understand
at
least
the
service
mesh
is
available
in
a
community
version.
It's
not
not
not
up
to
date,
I
think,
but
at
least
yeah
as
there
were
efforts
to
to
publish
it
to
the
community
catalogue
which,
which
is
great
but
yeah,
but
I
don't
know
how
often
it
it
be
updated
or
how
good
is
it
tested,
and
the
same
is
for
every
operator
in
the
operator
hub
for
sure.
But
this
would
be.
This
was
would
make
okd
similar
as
feature
rich
as
ocp.
C
D
So
you
know
defeat
from
the
jaws
of
victory,
and
all
that
yeah
is
the
is
the
developer
content
that
sits
behind
the
samples
operator
in
kind
of
the
same
boat?
No,
it's
it's
worse
off.
The
samples
operator
is
nobody.
Nobody
has
any
samples
to
provide
to
begin
with.
The
the
samples
operator
for
ocp
is
populated,
with
a
mixture
of
ubi
and
non-uvi
content
and
separating
all
that
stuff,
like
I've.
D
Looked
at
it
personally,
like
look
separating
all
that
stuff
is
complicated,
it's
probably
a
lot
easier
to
go
back
and
start
and
build
up
content
based
on
fedora
based
fedora
base
image
and
centos
based
image
and
start
putting
together
a
mixture
ourselves,
because
the
the
stuff
that
they
use
for
ocp
is
like
not
reusable
at
all,
like
that.
That's
really
the
samples
operator
framework
is
great.
D
A
B
B
A
D
And
if
uefi
is
activated,
they
won't,
they
won't
load.
That's
not!
Okay!
This
problem!
No,
but
it's
your
problem
with
the
gpu
operator
like
they.
They
don't
load.
So
it's
not
going
to
work.
It's
it
works
in
rel
because
there's
an
ugly,
very
hacky,
terrible
thing
that
they've
done
to
make
it
so
that
it
works
with
even
uefi
mode,
but
it
will
not
work
in
fedora
right
now.
B
Beyond
the
list
that
we
have
here
now,
are
there
other
ones?
I
mean
someone
was
just
asking
for
what
what
did
we
filter
out
and
maybe
that
he
not
write
this
instant,
but
if
you
can
grab
a
list
of
what
got
filtered
out.
That
might
also
be
a
a
thing,
a
thing
to
add
in
here,
not
as
a
wish
list,
but
just
for
reference.
A
I
didn't
see
a
reason
why
those
should
be
filtered
out.
All
of
them
are
optional.
Some
of
them
might
not
work
in
your
setup,
but
that's
a
different
story,
but
for
us
this
list
is
helpful
because
we
can
start
contacting
teams
and
ask
them
to
implement.
You
know
to
revive
their
okay
support.
Basically,
if
we
get
some
of
them,
that's
great,
we
don't
commit
getting
them
all
of
them
by
I
don't
know
next
week
and
so
on.
That's
just
not
gonna
work,
that's
outside
of
our
reach.
B
B
B
Excuse
me
that
that
we
that
I
could
ask
to
see
if
they
will
put
theirs
in
first
of
all
an
operator
hub.io
and
I
haven't,
and
I
should
and
then
to
see
if
they'll
get
it
and
tested
on
okd.
So
that's
that's.
A
another
possibility
is,
and
we
all
have
been
probably
watching
the
istio
k
native
google
conversation,
so
it
might
not
be
a
bad
backup
plan
to
have
those
available
as
well.
B
So
one
of
the
things
just
yesterday,
I
did
a
an
ask
me
anything
session
with
the
open
data
hub
folks
and
I'm
trying
to
get
them
to
and
I'm
pretty
sure
they
already
have
tried
and
done
it
successfully.
We
just
haven't
demoed
it
running
open
data
hub
on
okd,
so
that
there's
a
pure
openstack
open
source
stack
for
open
data
hub
it,
which
is
just
a
reference
architect
here,
it's
not
for
ml
and
ai,
it's
not
a
product.
B
Yeah
so
maybe
offline
christian,
we
could
figure
out
what
those
demos
are
and
just
get
them
staged
and
and
broadcast
them
out
to
the
universe
I'd
like
to
to
be
on
in
on
on
whatever
those
reference
architectures
the
more
we
can
get
that
more
content
that
that's
great,
but
I'm
thinking
the
open
data
hub.
One
will
drive
the
gpu
piece
if
they,
if
they
build
open
day
because
they
rely
so
heavily
on
gpu,
so
that
might
be
a
way
to
a
way
to
nudge
the
nvidia
people
to
to
do.
B
A
D
D
It
it's
in
the
it's
in
the
documentation
for
my
lab.
I
did
drop
the
links
in
there.
Actually
I'll
go
ahead
and
bring
this
up.
I've
started
preparing
a
pull
request
to
see
if
you
guys
like
this
idea
for
our
okd
site,
to
add
a
section
for
recipes
just
little
short
snippets
of
how
do
I
install
eclipse
chay
in
my
okd
cluster
or
what
one
of
them
I've
written
up
is
is
deploying
seth
or
you
know,
adding
persistent
storage
to
the
image
registry.
B
Yeah,
so
I
would
love
to
do
an
okd
cookbook
just
saying
I
did.
I
did
a
whole
bunch
of
them
when
I
was
at
active
state
for
python
and
other
languages
with
people.
I
think
that's
a
really
effective
way
to
get
get
recipes
out
there
and
get
people
get
examples.
So
that's
we
could
do
a
okay
d,
slash
cookbook
and
then
have
a
whole
bunch
of
recipes
out
there,
and
I
think
that's
a
known
thing
in
in
the
tech
world
to
do.
Cookbooks
like
that.
B
B
Anyone
gives
me
and
pray.
Merge
and
pray
is
what
I
do
so.
I'm
happy
charlotte
to
do
that
and
then
I
actually
think
that
would
be
a
good
e-book
to
share
like
a
little
to
if
everybody
brought
their
recipes
together.
That
would
be
a
really
great
way
to
do
that,
so
a
plus
for
that,
but
I'm
pretty
sure
there
was
someone
on
the
code
ready
team
that
was
looking
at
building
an
okd
code,
ready
thing
and
I'll
I'll
dig
up
the
name
from
an
email.
B
C
We
are
preparing
okd
for
some
of
our
production
clusters
and
we
found
out
that
we
had
problems
in
integrating
the
monitoring
in
our
environment,
because
we
have
a
central
monitoring
which
monitors
several
openshift
clusters,
and
I
was
talking
with
vadim
also
in
the
slack
channel.
But
I
would
like
to
talk
here
also
about
that
and
we
had
to
turn
off
the
monitoring
operator
for
that.
So
we
had
to
bring
our
own
monitoring
stack
on
okd,
because
the
operating
monitor
monitoring
operator
is
overwriting,
our
our
promises,
rules
and
dashboards
and
yeah.
C
I'm
just
asking
if
it's
possible
to
to
turn
off
modules
some
models,
you
don't
want
to
have
for
some
reason
during
the
installation
and
without
any
hacks,
because
in
other
distributions
colleagues
of
me
always
show
me.
Hey
here
is
a
button
suck
switch
off
and
you
don't
have
to
mess
around
with
anything
you
you
don't
like,
and
I
think
it
would
be
a
great
advantage
if
you
are
possible
to
do
so
on
your
own
risk
sure,
because
yeah,
you
are
responsible
for
everything,
but
it's
it's
possible
to
also
feed
the
ui
with
metrics.
C
A
This
is
a
very
tough
topic
and
when,
when
joseph
says,
adjust
simeo,
it
means
rip
it
out
entirely.
That's
the
biggest
problem
here,
because
okd
has
to
have
all
the
features
so
cp
has
one
of
the
features
of
ocp
is
constant
monitoring
and
it's
embedded
very
heavily
in
every
single
part
of
the
product.
You
would
other
other
operators
might
render
degraded
if
they
say
my
metrics.
A
A
A
So
more
brutal
options
available
right
now
is
ripping
out
senior
out
of
manifests
in
the
release
image.
You
can
replace
it
with
dummy
rail.
I
don't
know
real
ubi
images
they
would
just
be.
There
have
no
manifests
to
be
always
say
I
did
my
best.
I
have
played
everything
we
had
and
would
move
on
again.
You
would
have
to
maintain
your
own
fork
for
that
which
is
not
really
complex,
but
that's
not
okay,
anymore.
A
Another
brutal
thing
is,
you
can
ignore
this
in
cvo
and
scale
down
the
monitoring
operator
to
zero.
You
won't
be
able
to
upgrade
because
you
have
overrides
in
studio,
so
nice
options
are
pretty
much
very
limited
right
now,
mostly
because
demio
is
very,
almost
every
core
operator
is
actually
core
and
very
critical.
We
cannot
disable
them.
They
were
carefully
picked
up,
but
we
definitely
will
work
on
minimizing
its
impact.
C
A
A
A
E
Yeah,
the
broader
the
broader
issue
here
is
really
that
that's
the
thing
we
don't
support
in
any,
not
an
ocp
and
therefore
also
not
in
okd
right.
So
what
I
would
suggest,
because
it's
definitely
out
of
out
of
what
we
can
do
right
now
and
in
the
very
short
term.
What
I
would
suggest
is
to
to
in
order
to
raise
this
awareness
with
the
team.
That
actually
does
that.
D
D
We
are
running
two
prometheus
instances.
Now
this
is
pre-operator
right.
We've
got
prometheus
that
came
with
the
cluster
and
is
monitoring
all
of
the
cluster
infrastructure,
and
we
followed
the
rules
on
it
and
didn't
muck
around
with
that
one.
But
we
did
deploy
our
own
set
of
prometheus
infrastructure
in
the
cluster.
That
is
monitoring
all
of
the
apps.
So
so
it's
it.
We've
got
it
watching
the
name
spaces
that
we
deploy
our
apps
in
and
it
it's
working
fine
side
by
side
with
the
with
with
what
came
deployed
with
the
cluster.
A
A
It
sends
a
part
of
metrics
back
to
different
prometheus
server,
leaving
cmo
fully
intact.
This
is
how
we
get
those
fancy
graphs.
Basically,
your
clusters
are
sending
a
part
of
critical
control,
plane
data
back
to
our
servers
using
remote
rights.
So,
instead
of
fully
removing
simio
and
replacing
it
with
your
solution,
you
could
send
the
very
same
metrics
to
a
different
prometheus
and
maintain
a
monitoring
system
based
on.
A
A
B
B
I'm
pretty
sure
kubecon
is
running
on
eu
time,
so
it'll
be
early
for
me
on
the
west
coast,
but
please
just
do
fill
it
in
and
we'll
try
and
do
that.
And
if
multiple
people
talk
about
the
same
platform
like
five
people
want
to
do
it
on.
You
know:
aws,
we'll
we'll
get
you
all
together
and
you
can
chat
about
it
and
be
in
one
one
hour
and
one
person
could
be
the
driver,
so
we'll
figure
that
out
too
there
you
go
so
we're
almost
to
the
top
of
the
hour.
D
A
D
C
If
you
are
talking
about
a
price,
we
are
shortly
before
getting
our
okay
d4
cluster,
in
production,
for
internal
usage,
for
different
teams,
and
that's
why
I'm
asking
about
this
gpu
thing,
because
I
think
it
will
come
in
the
midterm
and
but
yeah
we
are.
We
are
planning
to
getting
ga
in
the
next
next
very
few
weeks.
D
And
as
for
as
for
datto,
like
we're
we're
working
on
figuring
out
when
we're
going
to
do
our
deployment,
there's
some
underlying
unfortunate
architectural
things
that
we
need
to
fix
first,
but
we
are
starting
to.
We
are
starting
to
scope
and
plan
our
okd4
deployment
to
replace
our
open
shift
origin
deployment
so
that
that's
that's
a
common
at
some
point,
hopefully
soon
rather
than
later,
because
nobody
more
than
me
wants
us
to
switch
to
locating
four
already.
D
D
B
So,
charles,
so
I
think
that
one
of
the
takeaways
is
I'd
like
to
have
a
conversation
on
the
side
with
you
about
designing
the
cookbook
recipe
pages
for
okd.io
and
give
you
proofs
to
do
to
do
so
and
and
start
thinking
about
that,
because
I
think
that's
a
really
great
thing
and
then
please
fill
out
the
form
that's
in
there
communist.
If
I'm
on
my
reading
here,
fedora
head
communication,
yeah,
that's
what
we
need
the
anarchist
version
of
okd,
the
anarchist
guide
to
okd.
B
That's
next
all
right!
Well,
I
don't
know!
Maybe
jamie
deliver
the
child
first,
okay,
I
don't
know
make
sure
the
child
is
ga
yeah.
I
know
yeah
before
before
anything
else.
Otherwise,
there'll
be
some
other
problems
in
your
life.
So
let's,
let's
see
what
we
can
do
and
yeah.
So
if
you
can,
everybody
fill
out
the
form.
B
I
will
try
and
create
a
landing
page
for
the
august
17th
thing
that
we
can
all
use
and
schedule
people
on
and
you
can
see
what
your
time
slots
are
and
we
can
promote
it.
It's
a
bit
of
gorilla
marketing
during
kubecon,
so
we'll
have
to
use
our
stealthy
social
channels
and
everything
else
to
get
the
word
out
about
it.
B
But
and
there's
probably
70
other
things
that
are
happening
on
day
zero
at
kubecon
as
well.
But
we
can
rise
up
above
the
noise,
hopefully
and
at
least
capture
all
that
content
in
a
day-long
thing
and
where
you
probably
wear
your
t-shirts.
If
we
can
get
them
printed
and
shipped
in
time
and
maybe
set
up
a
store
and
sell
t-shirts
or
something
at
kucon
and
pop
t-shirts
and
popcorn.
C
I
have
a
question:
do
I
was
thinking
about
that
in
the
last
days?
I
would
very
appreciate
it
if
we
could
do
some
kind
of
hackathons
for
for
different
tasks,
which
it
will
improve.
Okd
such
like
yeah.
This
is
a
gpu
thing
to
get
that
working
here
and
propose
a
poc
or
a
blueprint.
How
to
do
that?
I
would
love
to
do
so,
because
I
think
we
have
some
knowledge
in
in
this
working
group
to
pick
out
several
things
which
are
too
hard
to
solve
some
alone
yeah.
E
B
Yeah,
that's
definitely
the
way
forward,
I
think
for
us,
and
I
think
it
might
be
something
that
we
can
cross-pollinate
with
the
operator
framework
group,
and
you
know
co-host
that
once
if
we
can
get
our
list
and
the
point
people
for
each
of
those
things
that
are
on
our
wish
list
identified,
that
might
be
the
good
basis
for
a
cncf.
Now
that
operator
framework
is
in
cncf
and
okd,
co-sponsored,
hackathon
and
I'd
be
happy
to
to
do
that.
B
So,
let's
get
that
list
prioritized
figure
out
who
who's,
who
there
I'll
go
on
to
and
reach
out
to
the
folks
on
that
the
operator
framework
side
and
once
the
list
is
there
and
see.
If
I
can
figure
out,
you
know
how
we
could
do
that.
So
that's
that's!
Not
a
bad
thing
at
all.
So
I'll
add
that
into
the
list
of
possibilities
beyond
ga,
but
still
adoption
is
really
where
it's
at
right
now
and
more
feedback
and
adoption
when
we
have
the
operators
will
be
easier.
B
I
think
they
can
do
more
things
more
workloads
easier.
So
that's
a
key
piece
of
it
and
you
know
again
creating
content
and
updating,
doing
the
recipes
and
continuing
what
you
guys
have
been
doing
wonderfully
home
labs
content
on
live
streams,
openshift.com
medium.
All
that
stuff
is
really
it's
huge
and
we'll
just
keep
doing
the
outreach
and
getting
more
bodies
here
and
to
talk
on
this
call.