►
From YouTube: OKD Working Group Meeting 08-31-2021
Description
The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group includes the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group produces supporting materials and best practices for end-users and provides guidance and coordination for CNCF projects working within the SIG's scope.
A
All
right,
let's
jump
into
our
agenda
review,
don't
forget
to
put
your
name
as
an
attendee
in
the
agenda
document
here
I'll
post,
a
link
to
it
here
in
the
chat.
A
There
we
go
so
please
put
your
name
there.
Let
us
know
that
you
were
here
and
let's
review
the
agenda,
take
a
couple
seconds
to
look
at
the
agenda,
see
if
there's
anything
that
was
missed,
anything
that
you'd
like
to
add
so
we'll
wait
about
30
seconds
and
then
we'll
solidify
the
agenda.
A
Okay-
let's
jump
into
it,
so
we
are
actually
we're
not
doing
introductions
anymore,
if
folks,
maybe
identify
themselves
the
first
time
that
they
speak.
That's
always
helpful
just
that
people
can
put
a
name
to
a
face.
A
Vadim
is
out
today
there's
a
note
here
about
vsphere
over
installs
in
four
seven
should
be
fixed
and
the
older
fedora
quarter
west
should
be
used
due
to
that
f
cost
bug
and
without
vadim
here
that
actually
takes
out
a
chunk
of
some
of
the
things
that
I
wanted
to
talk
about,
but
let's
bounce
over
instead
to
dusty
for
some
fedora
core
os
updates.
B
Hey
everybody
yeah,
I
I
don't
have
a
whole
lot,
I'm
kind
of
standing
in
for
timothy
this
week.
I
would
love
to
come
every
week.
I
just
don't
often
find
the
time,
but
what
I
would
like
to
say
is
timothy
mentioned
to
me
that
he
wanted
me
to
bring
up
the
fact
that
the
dnf
counting
support
is
now
going
to
be
defaults
in
fedora
core
os.
B
So
on
our
testing
stream.
We
just
rolled
it
out.
So
basically,
when
nodes
do
updates
it,
it
pings
our
server
and
there's
a
unique
id
and
stuff
that
that
we
can
kind
of
start
to
see
how
many
people
are
actually
using
fedora
core
os,
it's
completely
optional,
so
it
can
be
opted
out
of,
but
it's
very
similar
to
what
fedora
is
already
using
for
workstation
server
cloud,
etc
for
kind
of
getting
some
sort
of
numbers.
B
If
you've
ever
seen,
matthew
miller
give
his
state
of
fedora
talk
using
graphs
and
that's
where
all
that
information
kind
of
plugs
in
so
that's
pretty
much
it
just
an
fyi
there.
If
you,
if
you
don't
want
to
opt
in,
then
basically
you
can
opt
out
and
I'll
put
a
link
to
that
stuff
there
since
but
emit
in
here.
I'm
not
sure
exactly.
A
All
right,
thank
you,
dusty
and
moving
on
to
a
docs
update,
brian,
you
wanna,
you
wanna,
chime
in
with
the
state
of
okd.io.
C
Yeah
sure
so
I've
created
a
beat
of
sight
diane.
We
might
need
your
help
there
getting
someone
to
turn
on
the
github
pages
for
the
openshift
site.
So
I
don't
have
access
to
the
settings
tab.
So
someone
needs
to
go
in
the
settings,
go
to
the
pages
tab
and
just
enable
it
to
pages
on
the
beta
branch,
and
then
the
site
should
just
pop
up
it's
the
root
of
the
beta
branch
and
then
the
beta
site
should
just
pop
up
serve
from
github
pages.
C
So
that
is
basically
what
I
had
on
my
personal
repo.
What
I'm
currently
working
on
is
moving
the
home
page,
so
the
content
is
in
markdown
and
we
stylize
it.
It's
not
going
to
be
as
fancy
as
what's
there
with
all
the
animations
and
all
that
stuff,
but
it
means
that
the
content
will
be
updatable
in
markdown
and
you
don't
have
to
go
into
the
template
and
write
all
the
css
and
the
html
to
get
it
to
to
look
good.
C
So
I'm
doing
that
and
then
it's
really
going
to
be
a
question
of
getting
community
feedback
in
terms
of
what
color
schemes
do
we
want.
I'm
trying
to
go
with
light
and
dark,
so
we've
got
two
different
color
schemes,
one
light
and
one
dark,
and
it's
really,
then:
where
do
we
want
the
menu?
How
do
you
want
the
menu
to
be
structured?
C
Just
then
make
sure
we
have
all
the
content
moved
across
into
the
beta
site
and
when
everyone's
happy
with
that,
we
can
flip
it
over
into
production
and
for
those
who
don't
know
we're
adopting
a
technology
which
takes
pure
markdown
with
a
couple
of
extensions
to
convert
the
static
site
so
rather
than
middleman,
where
you
need
to
be
more
of
a
front-end
web
developer
to
actually
modify
content
or
moving
to
a
model
where
it's
pure
markdown
and
I'm
going
to
use
github
actions.
C
D
I'm
muted,
of
course,
I'm
talking
to
myself
so
brian.
I
will
reach
out
to
you
in
slack
and
walk
through.
All
of
that
I
may
have
privileges.
I
doubt
it
that
I
have
the
privileges
to
do
to
do
what
you've
asked
me
to
do,
but
I
I
know
people
so
I
will,
I
know
a
person
who
knows
a
guy
who
can
get
that
done
for
us
today.
Hopefully.
C
But
basically
anybody
that
goes
in
and
has
the
settings
icon
will
be
able
to
do
it.
Yeah.
D
I'm
pretty
sure
I
know
someone
who
has
that,
hopefully
he's
not
on
vacation.
Actually
one
of
them
had
just
had
a
baby,
so
he
may
be
on
pto,
so
we'll
figure
out
what
that
is.
The
other
thing
is,
I,
I
have
an
a
resource,
a
third-party
resource
that
works
for
me
on
other
projects
that,
if
we
trained
him
up,
can
help
with
color
schemes
making
things
beautiful.
D
He
has
more
skills
than
my
ms
paint
skills,
so
I'll
reach
out
to
you,
brian,
and
introduce
you
to
him
and
we'll
see
and
he's
also,
I
think,
a
good
litmus
test
for
if
we've
got
enough
documentation
for
everybody
on
how
to
how
to
successfully
update
this
stuff.
So
I'm
going
to
see
if
I
can
repurpose
him
from
doing
some
stuff
on
the
commons
website
and
get
him
to
to
help
with
this
transition.
D
And
you
know
it's
it's
a
paid
resource,
so
you
know
that's
that's,
also
helpful
and
and
get
him
involved
as
well.
So
hopefully
that
will
help
us
move
a
little
bit
more
quickly
to
to
getting
this
done,
because
trust
me,
I
would
like
to
get
off
the
current
situation
as
soon
as
possible
and
make
this
more
community
oriented.
So
let's,
let's
see
if
we
can
do
that,
and
I
can
do
that
offline
with
you
and
via
slack
and
everything
else.
A
Thank
you,
diane
and
another
thing
that
came
up
vadim
isn't
here,
so
we
can't
really
tackle
it
at
the
level
that
I
wanted
to
is
documents
group
talking
again
about
breaking
down
and
moving
the
different
components
of
the
readme
brian
has
done
that
to
some
extent
already
in
terms
of
the
menu
choices
that
he
set
up
in
the
beta,
and
so
once
that's
visible
to
everybody
and
once
folks
have
had
a
chance
to
play
around
with
it,
then
we
can
actually
turn
the
readme
in
the
okd
repo
to
just
a
basic
readme,
with
links
to
all
of
the
different
components
and
different
ideas,
as
opposed
to
trying
to
go
right
there
and
put
it
all
in
in
one
document.
A
I
do
want
vadim
to
be
a,
I
think
it's
it
would
be
beneficial
to
us
to
have
vadim
chime
in
from
an
engineering
standpoint
and
from
the
as
the
sort
of
maintainer
of
the
repo,
as
it
were,
with
his
input
on
that
and
regrettably
he
hasn't
been
this
me.
He
was
not
this
one
and
he
hasn't
been.
It
was
not
the
last
one
so
we'll
we
won't
be
moving
forward
with
that.
Completely
until
we
sort
of
get
the
dean
get
some
feedback
from
him
on
that.
A
The
other
thing
is
how
to
ask
questions.
This
is
if
you
look,
there
was
a
pinned
comment
by
vedine
in
the
openshift
users
channel.
A
Let's
see
I'm
trying
to
think
what
day
it
was,
it
was
the
27th
at
507
a.m.
Let
me
copy
this
here
and
paste
it,
but
in
short,
vadim
did
a
good
job
of
sort
of
laying
out
what
is
helpful
and
what
is
not
helpful
in
terms
of
questions,
and
let
me
post
this
here
and
I
added
a
little
tidbit
that
I
thought
was
helpful
and
he
agreed
with
that
and
it'd
be
nice
to
actually
get
this
as,
like,
maybe
a
small
document.
A
I
don't
know
of
any
resource.
That's
there's
always
the
general,
and
I
can't
remember
the
website
off
the
top
of
my
head,
the
how
to
ask
questions.
There's
like
a
website
that
actually
like
elucidates
how
to
do
this.
It
would
help
vadim
and
other
folks
who
were
doing
support
stuff
in
the
channel
and
and
the
other
places
where
people
have
been
showing
up
in
the
discussions
or
whatever,
to
be
able
to
reference
something.
That's
a
document
that
says
here's
what
we
need.
You
know
when
you're
asking
for
help.
A
You
know
we
need
your
your
log.
You
know
we
need
what
version
that
you're
running.
We
need
to
know
what
provider
that
you're
on
must
gather
is,
like
you
know,
vadim,
probably
80,
of
the
questions
that
he
goes
to
respond
to.
He
has
to
ask
for
people
to
provide
a
must
gather
and
that's
takes
a
lot
of
time
and
it
delays
our
ability
to
help
other
people
as
well.
I
think
the
docs
group
will
will
tackle
this,
probably
at
the
next
meeting.
A
If
folks
have
suggestions,
feel
free
to
shoot
an
email
over
the
working
group,
email
list
or
throw
something
in
the
chat
or,
if
you
want
say
something
right
now,
if
you'd
like
to
add
something,
but
I
think
this
would
be
really
helpful
for
supporting
people
the
best
that
we
can
as
well.
A
A
And
then
training
materials
for
doc
support
resource,
that's
something
that
basically,
the
idea
is
to
have
something
that
we
can
get
folks
to
do
doc.
Support
continuously
over
time
coming
up
with
that,
docs
group
will
be
tackling
that
if
folks
have
input
on
that
feel
free
to
shoot
something
out
over
them.
A
A
And
I
didn't
see
anything
that
stood
out
as
being
need
as
needing
discussion
other
than
I
just
noticed
that
I
don't
think
anyone
responded
in
terms
of
the
crc
questions,
so
we
can
respond
to
those
with
the
new
build
that
charo
did
last
week,
which
I
think
resolved
all
the
outstanding
issues.
D
Just
just
to
double
check:
that's
the
one
that
you'd
update
the
okd
based
crc,
build
786
that
you're
talking
about
yeah.
D
A
There
is-
and
this
is
something
that,
when
we
do,
the
automation
will
be
resolved.
So
when
we
do
come
up
with
an
automated
solution
and
modify
some
of
those
build
scripts
and
stuff,
this
will
be
resolved
and
there's
another
crc
ticket.
That
is.
A
A
A
I
did
want
to
and
vadim
isn't
here
so
I
didn't
put
it
on
here,
but
you'll
notice
in
discussion,
784
and
I'll
put
a
direct
link
to
it.
It's
a
technical
discussion,
so
I
don't
want
to
have
it
without
vadim
or
maybe
christian
or
someone
here,
but
basically
eduardo
ended
up.
Writing
a
a
very
detailed
document
that
I
don't
know
it
wasn't
put
in
this
ticket,
but
eduardo
had
a
couple
tickets
open
and
ended
up.
A
Actually
writing
a
document
about
their
evaluation
of
okd
for
the
company
that
he
works
for
and
why
they
didn't
choose
it,
and
so
my
thought
was,
I
guess
we'll
do
it
at
the
next
meeting.
If
vadim
is
able
to
show
up
for
christian,
is
to
work
through
some
key
points
of
that
document
to
determine
what
feedback
we
can
run
with
and
and
improve
the
offering
versus
something.
That's
just
the
nature
of
the
beast
versus
something
that
we'd
like
to
do,
but
we
just
don't
have
the
resources
to
do.
A
Did
anyone
else
get
a
chance
to
to
look
at
that
document
that
eduardo
posted.
C
Yeah,
I
think
I
think
wasn't
he
the
the
user
that
was
trying
to
do
things
with
changing
the
base
domain.
Yes,
that
was
one
of
the
things
yeah
yeah.
He
had
a
usage
model
that
didn't
fit
kubernetes
an
open
shift
right
in
in
the
way
that
the
the
roots
and
the
base
domain
was
doing
it.
So
I
I
think
that
might
be
part
of
it.
I
haven't
actually
just
reading
through.
C
I
I've
read
the
document,
but
trying
to
work
out.
What
are
the
bits
he's
specifically
saying
and
what
were
the
problem
and
what
didn't
fit,
but
I
I
seem
to
remember:
we
had
several
discussions
around.
C
He
was
trying
to
change
the
base
domain
and
was
having
difficulty
coming
up
with
the
model
that
he
wanted
in
terms
of
and
getting
sort
of
work
coming
in
through
a
firewall
or
something
or
through
some
external
router.
A
C
I
think
it
was
either
one
he
wanted.
Multiple
domain
names
served
by
the
same
cluster
and
it
was
things
like
the
oauth
endpoints
that
right
yeah
that
couldn't
be
changed
to
support
multiple
domains.
So,
yes,
I
think
there
was
something
with
the
model
that
didn't
quite
fit
the
way
that
if
you
do
it,
the
way
that
openshift
and
okay
wants
it
to
do.
It
works
and,
I
think,
there's
a
model
that
didn't
work.
C
A
And
that's
something
where
there's
just
a
built-in
limitation
there
and
it
used
to
be
that
you
could
change
the
console
url.
But
now
you
can't
change
it.
I
think
you
can
once
actually.
I
don't
think
you
can
work
around
that.
I
think
actually
the
console
url.
You
have
to
rely
on
using
that
long
url,
because
the
authentication
bounces
or
no
actually
there
is
a
parameter
that
you
can
set
to
where
you
get.
F
You
can
still
change
the
console
you
can.
You
can
still
change
the
web
console
url.
However,
what
you
can't
change
is,
if
you
want
to
serve
multiple,
if
you
want
to
do
a
multi-tenant
open
shift
from
a
single
openshift
cluster,
which
is
essentially,
I
think
what
his
use
case
was,
and
I
think
it's
actually
a
fairly
valid
use
case.
F
Open
shift
itself
like
the
the
oh,
the
the
add-on
components
that
make
up
openshift
and
okd.
Of
course,
don't
support
this,
so
kubernetes
does,
because
you
don't
actually
have
to
have
the
web
console
in
kubernetes
itself,
and
so
what
you
can
do
is
you
can
deploy
kubernetes
and
then
deploy
multiple
instances
of
web
consoles
and
and
have
each
web
console
deployed
with
a
different
set
of
things,
and
so
it
can
look
multi-tenant
with
a
single
cluster
manager.
F
The
route
that
red
hat
has
taken
for
this
is
they're
using
ocm
to
do
this
as
red
hat
advanced
cluster
management
through
kubernetes.
However,
that
is
currently
non-functional
on
okd,
so
without
that
working
on
okd,
there's,
basically
no
multi-tenant
path
for
for
open
for
for
okd
right
now,.
D
So
ocm
is
about
to
go
into
the
sandbox
at
cncf
and
I
know
a
person
a
bunch
of
them.
Should
I
be
bringing
the
ocm
people
here
to
the
okd
working
group,
sometimes
not
to
just
in
the
future.
Okay,
so.
F
This
is
actually
something
that
my
team,
so
at
data
we're
also
very
interested
in
this.
For
a
similar
reason,
we
want.
G
F
We
want
to
basically
on-demand
multi-tenant
for
spinning
up
tiny
dev
clusters
whenever
they
need
it
in
developer
environments.
We
also
want
to
orchestrate
prod
and
staging
from
the
same
systems,
and
we
want
them
to
be
essentially
centrally
managed
as
much
as
reasonably
possible,
and
it
looks
like
the
ocm.
Stuff
is
the
way
to
do
that,
but
there
doesn't
seem
to
be
a
way
to
use
it
with
okd,
which
is
that's
kind.
D
We
are
really
bad
at
naming
things
so
anyways
just
enough
said,
but
the
but
the
ocm.
Folks-
and
I
don't
know
if
dado,
if,
if
anyone
at
dado
has
reached
out
to
the
ocm
group,
they
have
community
meetings
as
well,
so
that
might
be
julianna.
D
Is
the
engineering
lead
and
sort
of
the
community
lead
for
that
initiative?
And
it's
basically
what
they
are
is
open
sourcing
advanced
cluster
management
because
we
open
source
everything
we
acquire
and
the
good
people
at
staff
rocks
are
right.
We
found.
F
Out
that
ocm
was
fully
open
sourced
three
days
ago,
because
I
saw
a
youtube
video
that
said
yeah
we
made
a
new
rha
cm
release.
It
is
open
source
now
and
they
pointed
us
to
a
website
and
I
went
and
looked
at
it
and
it's
like
not
complete,
like
the
the
the
deployment
is
not
complete.
F
E
E
The
whole
time
hi
daniel
axelrod,
also
from
datto
I've,
been
out
of
a
few
of
these
before
no,
we
have
not
reached
out
to
ocm
directly,
yet
that's
that's
a
good
contact
I'll
I'll
make
sure
that
that
we
have
that
conversation.
Thank
you.
D
Yeah,
no,
let's,
let's
please
do
that
because
they
are
applying
for
sandbox
status
in
the
cncf
right
now
and
so
the
more
external
voices
that
are
like
hey.
This
is
a
good
thing,
will
help
them,
so
they
will
listen
because
they
will
listen.
Anyways
julian
is
great.
So
let's
do
that
and
I
and
I
have
had
a
conversation
with
them
about
making
it
work
with
ocm
okd
and
it's
just
it's
a
bandwidth
issue.
It's
always
a
bandwidth
issue
for
folks.
B
E
B
E
Likely
attend
virtually
quite
yeah
yeah.
I
I.
G
D
I
think
I
think
it
is
it's
like,
since
most
of
all
of
us
are
remote,
but
what
I'm
always
looking
for
is
people
who
are
in
the
vicinity
of
los
angeles,
because
those
probably
be
the
only
people
who
are
allowed
in
the
country
or
in
the
state.
At
that
juncture,
who
know
who
knows
to
participate.
F
F
If
diane,
you
could
hook
us
up
with
a
contact
with
the
ocm
team
and
then
dan,
and
I
can
start
talking
with
them
about
it
provisionally,
like
I'm,
not
saying
this
with
like
any
particular
guarantees,
but
I
think
provisionally
we
could
try
to
wrangle
up
some
ability
to
test
ocm
on
okd
in
our
in
our
environment,
to
see
you
know
how
well
it
works
and
like
give
feedback
to
the
team,
if
that's
something
that
they're
looking
for,
can't
really
commit
to
anything
yet
because,
like
everything's
kind
of
like
up
in
the
air,
but
that's
certainly
it's
something
that
we
care
about
enough
that
we're
super
interested
in
that
we
would
that
you
know
we
can
try
to
make
some
openings
to
to
try
to
to
try
to
do
that.
D
Yeah,
no,
it's
definitely
wanted,
and
I
was
just
going
to
say
also
in
at
the
commons
event,
if
dado
shows
up
well
we're
doing
a
whole
series
of
lightning
talks
in
the
afternoon,
so
those
may
be
virtual.
We
have
no
idea
yet,
but
we'll
see
if
they're,
I'm
making
a
note
to
connect
you
to
juliana.
So
thank
you.
A
Excellent,
I'm
going
to
put
a
link
to
I'll
put
it
in
discussion
items,
eduardo's,
okd,
bare
metal,
install
instructions,
slash
critique
and
then
we'll
bump
that
to
the
next
meeting
to
to
delve
into
that
a
little
bit,
and
I
think
it's
just.
A
I
think
it's
good
practice
like
if
we
get
particularly
if
someone
goes
in
and
takes
the
trouble
to
write
out
something
so
detailed
of
an
analysis
of
okd
as
an
option
to
take
that
feedback
and
at
least
look
it
over
and
and
demonstrate
some
some
response
to
that
right.
So
we'll
do
that
next
time
around
code
render
code
ready,
container
status,
the
event
was
a
success.
A
It
seems
like
we
had
at
one
point:
20
some
odd
people
logged
in
for
it,
which
I
think
for
a
live
event
on
a
friday
afternoon
is,
is
a
good
thing
or
friday
morning
for
some.
What's
what
kind
of
feedback
have
you
do?
You
have
or
have
you
heard
about
the
event.
D
Did
it
get
us
anybody
else
to
help
build
crcs?
That's
that's
my
question.
You
know,
or
what
is
the
next
step
to
make
enable
someone
other
than
charo
to
make
a
to
build
and
release
a
crc
container
for
okd
that
that,
to
me
is
that
the
measure
of
success
this
has
got
people
may
be
interested.
It
sounded
like
the
next
step
was
more
documentation
right
then.
Yes,
and.
A
F
So
I
know
that,
from
our
perspective,
we're
tentatively
interested
in
being
able
to
in
doing
that.
Certainly
something
that
is
kind
of
a
concern
is
the
fact
that
this
has
not
been
automated
before.
I
think
something
that
we
could
possibly
do
is
if
there
is
interest
in
like
automating
the
the
build
and
release
of
that.
F
This
is
something
that
we
might
be
able
to
help
with,
because
it
would
be
useful
for
us
as
well,
because
what
I
think
we
would
want
to
do
you
know
just
speaking
for
myself
having
to
work
with
okd
stuff
at
datto,
something
that
we
have
for
our
own
workflow
is
that
we
actually
spin
up
simple
clusters
that
we
can
run
as
a
vm
on
our
computer
to
to
stage
and
test
the
new
version
and
test
our
our
our
workloads
and
stuff
on
it
to
make
sure
that
the
features
are
there
and
the
stuff
like
that
works
before
we
actually
deploy
into
production
because
deploying
a
production
cluster
is
such
a
pain
in
the
butt
and
such
a
lot
of
work
that
it's
much
easier
for
us
to
be
able
to
be
able
to
do
localized
testing.
F
Basically,
on
demand
to
to
do
that,
and
since
we
don't
have
and
so
crc
seems
to
be
like
the
path
to
be
able
to
do
that
for
that
with
okay
d4,
then
we
need
to.
We
would
want
to
be
able
to
to
build
that
continuously
with
newer
nightlys
or
whatever,
based
on
whatever
we're
trying
to
figure
out.
So
the
the
open
question
at
this
point
is
you
know
how
difficult
is
it
to
replicate?
You
know
what
you
know.
F
Any
missing
documentation
needs
to
be
filled
in,
depending
on
no
conversation
with
charo
and
us
or
whatever,
but
also
the
final
step
is
asking
the
question
of.
Why
was
this
never
automated,
because,
like
everything
else
about
the
openshift
deployment
process,
the
openshift
build
and
release
process
is
automated,
but
crc
somehow
isn't.
That
is
a
little
weird
to
me
in
the
first
place.
So
I
don't,
I
don't
get
what
what
happened
there
so,
having
looked.
A
At
the
documentation,
it's
not
hard
at
all,
and
I
mean
it
and
if
you
follow
what's
there,
it
appears
to
be
pretty
easily
ci
right.
My
sense
is
that
we
could
actually
do
a
process
and
that
automation
process
and
make
that
process
available
so
make
the
scripts
available
that
we
use
to
do
that
etc
and
make
the
whole
thing
open.
We
could
ask
charo.
My
sense
is
that
he
might
have
an
answer.
A
We
asked
charlo
about
why
it
was
neglected
in
terms
of
an
automated
build,
but
I
don't
know
that
I
don't
know
that.
There's
a
technical
reason
right
if.
A
Well,
I
was
suggesting
that
we
do
it
against
the
nightlys
and
if
that's
too
much
for
fedora
folks,
then
we
could
do
that.
I'm
sure
someone
would
offer
space.
I
might
even
be
able
to
offer
space
due
to
that,
but
it'd
be
great
to
do
it
against
the
nightly
so
that
we
always
have
like
a
sense
of
where
things
are
going.
But
sorry.
D
That's
that
would
be
my
question
is
what
what
what's
stopping
us
from
from
doing
that,
like
is,
is
it
just
because
that
would
be
for
me
one
one
way
to
really
showcase
the
okd
working
group
stepping
up
and
doing
that
externally
to
the
red
hat
engineering
and
maybe
being
able
to
showcase
some
of
the
work
that
you're
doing
at
dado
or
whomever
ends
up
hosting
it
too.
So
is
there
something.
F
I
don't
think
either
of
us
at
data
would
actually
have
a
problem
about
helping
set
that
up
even
within
the
auspices
of
the
door
project,
both
dan
and
I
are
actually
members
of
the
fedora
community
as
well,
and
so
we
can,
if
we
were
doing
it.
I
expect
that
even
if
data
were
like
doing
some
of
the
effort
to
make
this
happen,
we'd
probably
want
to
drive
it
so
that
it's
actually
executed
within
fedora
so
that
it
isn't
it
isn't
gated
on
us
like.
F
We
are
not
we
don't
own
it
and
it's
something
that
can
be
shared
upon
with
the
rest
of
the
community
and
sure
we'll
we'll
probably
make
it
in
a
way
that
lets
us
also
build
it
internally
for
our
own
cases
as
well,
but
we
we
certainly
want
to
make
it
so
that
it
is
a
public
resource
that
is
supported.
Well
that
way,
so
one
of.
A
Okay
working
group
maintains
those
scripts
etc.
We
get
feedback
from
data,
we
get
feedback
from
fedora,
etc,
but
ultimately
it
stays
within
the
working
group
as
a
project
that
working
group
members
can
actually
keep
alive.
So.
E
A
Think
it's
this
working
group
and
what
I
would
like
to
see
also
is
maybe
a
page
showing
how
folks
can
do
their
own
automation
for
their
provider
right,
exactly
like,
like
so
whatever,
wherever,
if
they've
got
a
jenkins
set
up
in
aws
or
in
another
okd
cluster
or
wherever
they
have
it
like
to
be
able
to
to
set
it
up
with
jenkins
or
techton.
Or
you
know,
whatever
you've
got
like
it'd
be
nice
to
have
some
examples
on
how
to
do
that
in
all
of
yeah.
A
All
right:
well,
let's
I'm
interested
in
participating
in
that
it
sounds
neil
and
daniel.
You
seem
interested
in
that
daniel.
Do
you
prefer
daniel
or
dan,
by
the
way.
C
F
A
G
Was
on
the
list
yeah?
No,
I
I
tried
it
and
it.
It
looks
like
he's
going
with
latest
latest
of
everything,
and
it
almost
worked.
It
got
it
got
up
to
where
all
the
class,
all
the
operators
came
up,
except
for
dns
and
authentication,
and
then
it
died
and
it
I
I
ran
it
on
a
a
knuck
I-10,
which
was
more.
I
already
had
sitting
there,
which
is
more
or
less
centos
stream,
which
he
was
using.
So
his
script
is
quite
clear.
G
I
didn't
have
a
chance
to
go
through
and
figure
out
why
it
didn't
go
up,
but
I'm
guessing
that,
like
there
was
a
lot
of
stuff
where
you
can't
use
the
latest
fcos
and
there
were
other
people
had
overt
problems.
So
I'm
guessing
that
that
was
one
of
the
reasons
why
the
networking
had
some
hiccup
that
didn't
cause
dns
to
come
up.
C
G
Yeah
no,
I
I
saw
that,
and
that
seems
to
be
your
recurrent
theme,
which
is
a
bit
annoying
because
it
it
means
that
a
lot
of
the
installations
and
or
upgrades
I
I've
gotten
to
the
point
where
I
don't
expect
it
to
work
out
of
the
box
and
a
year
ago,
for
a
long
time,
maybe
six
months
things
did
work
out
of
the
box.
A
But
the
question
for
vadim
might
be:
how
is
it,
how
are
these
slipping
through
their
process
to
where
these
aren't
building
successfully?
When,
theoretically,
I
mean
maybe
they're
not
using
the
stable
next
and
the
third
stream,
that
fcos
provides
to
test
all
of
these
iterations,
but
ideally
they
should,
or
we
should
right.
We
should
be
setting
up
an
automation
that
tests
against
all
these
fcos
versions
coming
down.
Yeah.
F
Right,
yeah
right
and
that's
that's
where
the
impedance
problems
are
like
if
they're
not
simultaneously
testing
every
commit
landing
into
into
openshift
on
both
our
cause
and
f
cause,
then
this
starts
falling
apart.
A
lot
right.
G
Yeah,
no,
I'm
just
gonna
say
that
with
a
lot
of
the
scripting,
it
probably
would
help
to
expose
the
the
choices
of
f
cos
as
well
as
okd
version,
so
that
you
just
don't
hard
code
pulling
the
latest
of
the
latest,
because
then,
when
you,
if
you
just
run
the
script
as
charles,
is
you
don't
a
priority,
know
what
you're
necessarily
getting
so
I
mean
that's
sort
of
a
minor,
probably
change.
As
I
say
I
haven't
had
a
chance.
G
It
takes
about
six
hours
to
run
through
the
building
the
cluster
on
a
noc
with
his
configuration
okay.
So
it's
not
something
that
you
can
from
a
time
standpoint,
easily
just
sort
of
make
a
change
clean.
It
up.
Try
another
thing
clean
it
up,
try
another
thing,
but
it's
it's
notwithstanding
all
the
things
that
you
might
think
is
negative.
It's
actually
pretty
good.
G
It
came
close.
You
know
to
to
working,
so
I
was
actually
hopeful.
A
Well,
let's,
let's
throw
a
lot
of
resources
at
it,
so
let's
actually
get
together
a
group
of
folks
I'll,
send
an
email
to
the
working
group
mailing
list
and
said
hey
if
there's
anyone
else
interested
in
joining
this
crc
sub
group,
and
then
let's
go
from
there,
let's,
just
okay,
so
neil
daniel
bruce
sounds
like
you're
interested,
let's
just
tackle
it
through
what
resources
we
have.
I've
got
a
box
that
I
can
test
it
on.
A
This
will
be
the
first
technical
project
related
to
the
okd
work,
and
I
think
that
that's
a
great
rallying
point,
because
it
gives
people
something
tangible
that
they
can
really
bite
into
in
terms
of
their
participation
and
what
not
technical
participation
and,
as
we
know,
small
single
node
clusters,
home
labs,
etc,
are
like
the
the
sweet
spot.
There's
so
many
questions
of
the
okd
in
the
okada
community
about.
Can
I
run
this
at
home?
Can
I
run
this,
can
I
do
single
note,
etc?
A
Okay:
apologies
all
right
any
any
last
thoughts
on
the
crc
stuff.
A
Alright,
so
we'll
get
a
repo
up
and
daniel
if
you
want
put
your
email
and
your
get
name
in
the
document,
neil,
I
think
we
already
have
yours
on
some
some
stuff,
but
I'll
make
sure
that
you
get
added
bruce
as
well
brian.
You
have
any
interest
in
this
or
are
you?
Are
you
tax
maxed
out
right
now.
A
A
Put
it
in
the
heck
of
d
document,
yeah
that'd
be
easiest
because
we
lose
the
chat
when
we
close
the
meeting
so
unless
we
specifically
save
it,
okay,
so
okay,
the
operator
catalogs.
I
can't
really
ask
these.
A
I
was
I
was
hoping
for
vadim
or
christian
to
chime
in
and
just
to
reiterate
this
was
I
want
to
find
out
who,
at
red
hat,
we
can
bug
about
this
internal
effort
to
get
some
of
the
operators,
like
the
logging
operator
and
pipelines
and
whatnot.
Supposedly
there's
an
effort
within
red
hat.
To
get
these
opened
up,
get
the
red
hat
versions
actually
opened
up
and
available
as
opposed
to
using
you
know,
tecton
or
using.
D
There
is,
and
the
operator
framework
is
a
cncf
project
too,
and
they
have
community
meetings
so
that
maybe
what
I
need
to
do
is
is
show
up
there
with
this
as
an
agenda
item
with
you
know
one
or
two
of
you
in
there
so
put
a
note
in
there
to
find
out
when
the
next
community
meeting
is
for
the
operator
framework
in
the
notes
and
maybe
jamie,
and
I
or
somebody
and
I
can
show
up
there
and
or
and
see
what
we
can
do
to
move
that
forward.
C
C
D
Is
right,
but
they,
but
there
is,
we
need
some
more
clarity
around
the
red
hat,
supported
ones
and
most
of
the
folks
that
are
working
in
the
operator
framework
community
are
those
engineers
so,
and
we
can
also
ask
the
questions
in
in
the
the
kubernetes
in
the.
I
think
it's
in
cncf
slack,
there's
a
slack
channel
for
operator
framework,
but
we
can
track
that
down
and
start
asking
those
questions
because
they
are
they.
D
They
just
did
a
couple
of
an
update
the
week
before
last
on
the
operator
sdk
and
I
didn't
bring
up
okd,
but
they
they
are
doing
a
lot
of
tr
thinking
about
this,
I'm
not
sure
they're
doing
the
work
around
it,
but
they're
thinking
about
it.
A
Yeah
there
is
an
operator
sdk
group
operator,
sdk
dev,
possibly
it
but
yeah.
Let's
take
a
look
at
that
and
then
it'd
be
great
to
get
some
clarity
on
that,
because
we
have
that
one
issue
that
lists
all
of
the
operators
and
they're
sort
of
broken
up
by
the
three
categories.
A
So
we
have
that
it'd
be
nice
to
get
some
clarity
on
where
that
top
category
of
like
the
ones
that
were
sort
of
waiting
to
get
addressed,
are,
and
then
the
other
thing
that
I
have
on
the
agenda
here
is:
where
can
the
community
start?
How
can
we
inspire
folks
that
are
asking
about
these
operators
on
okd
to
build
themselves
or
recruit?
People
recruit
people
to
get
these
properly
tested
on
okd
so
that
they
can
get
added
in
anyone
have
any
thoughts
on
that.
D
Well,
I'm
sure
I'm
supposed
to
have
thoughts
on
that,
but
I
don't
have
the
answers
on
that
one
and
that's
why
I
would
move
over
and
ask
on
the
okd
of
not
neokitty
the
operator
sdk
group
and
the
operator
framework
groups
there,
because
there
that's,
where
the
engineering
resources
are
right
now.
So
I
think
originally
we
had
a
few
of
them
coming
over
and
filtering
into
our
group
and
then
they
created
their
own
community
so
they're
over
there.
So
if
we
want
stuff
on
okd,
I
think
we
need
to
go
to
them.
G
Can
I
ask
a
little
related
question:
yeah
right,
okay,
the
because
I
I
was
I
I
went
through
and
was
about
to
update
an
operator
that
I
was
using
for
my
classes
and
then
it
turned
out
that
I
noticed
that
it
is
since
I
updated
to
a
recent
4.7
from
4.6.
G
My
operator
was
now
controlled
by
the
samples
operator,
and
so
of
course
it
wiped
out
my
update
because
it
was
inconsistent
with
its
status
and
I
thought
oh
okay,
that's
interesting,
and
then
it
occurred
to
me.
Well,
okay,
we
maybe
should
have
a
mechanism
for
updating
like
things
like
the
samples
operator,
separate
from
the
main
update
of
everything,
because
it's
a
bit
hazardous
to
update
your
entire
cluster
and
there
might
be
some
subcompact
components
that
were
less
risky
that
you
might
want
to
update
in
the
middle.
G
You
know
in
between
doing
a
major
update
and
I
don't
think
we
have
that
sort
of
mechanism
at
the
moment.
No,
no,
okay!
So
that's
that's
sort
of
my
question
is
throwing
out.
That
idea
is
that
it
would
be
useful
for
an
operational
standpoint.
A
I
think
that's
good.
Let's
put
that
actually
in
the
document
under
operators
bruce
go
ahead
and
type
that
do
you
get
the
document
open.
If
you
want
to
go
ahead
and.
A
G
A
It
under
the
right,
where
you
see
my
cursor
for
operator,
catalog
stuff.
I
think
that's
a
great
question.
I
think
that's
something
that
we
can
ask.
You
know
from
an
engineering
standpoint
moving
forward
like
what
types
of
options
are
there
for
that:
okay,
anything
else
on
operators
before
we
move
on
to
new
business
stuff,
we've
got
about
12
minutes
left.
So
I
want
to
keep
us
keep
us
on
time.
A
All
right,
let's
move
on
then
to
new
business
stuff,
so
migration
path
outline
that's
something
that
we're
going
to
want
to
work
on
with
between
maybe
vadim
and
the
documentation
group
is
a
document
that
shows
you
know
if
you're
at
such
and
such
version
you
can
go
to
such
and
such
version
here
are
some
issues
that
you
might
have,
etc.
A
This
is
going
to
be
on
the
agenda
for
the
next
docs
meeting
next
week.
So,
if
you
have
anything
you
want
to
chip
in
on
that
feel
free
to
send
something
to
the
to
the
mailing
group,
the
working
groups,
mailing
group,
user
group
and
we'll
be
sure
to
include
it
in
that
discussion
or
join
us
for
the
docs
meeting
same
that
time
same
bat
channel
just
next
tuesday.
A
So
the
next
thing
I
want
to
throw
out
is
what
do
people
think
about
a
user
questionnaire
getting
a
sense
of
for
the
folks
that
are
using
it?
What
are
they
using
it
for
how
do
they?
Where
do
they?
Theoretically,
we
have
lots
of.
I
don't
remember
the
number
that
vadim
gave,
but
theoretically
we
have
lots
of
folks
installing
okd.
D
If
we
came
up
with
some,
you
know
two
or
three
questions
really
basic
ones.
What
what
are
your
workloads?
What
version
of
okd?
Are
you
running?
You
know?
What's
your
I
don't
know
like
if
you
could
come
up
with
what
they
are,
we
could
host
a
link
to
this
survey
ongoing.
D
I
would
love
to
know
that
without
you
know,
people
who
you
know
invading
people's
privacy
or
gdpr
stuff,
I'm
always
curious
about
I've
done
a
few
in
the
past
that
haven't
gotten
a
lot
of
feedback,
shall
we
say
other
than
probably
the
the
group
of
you
guys
who
are
all
on
here
right
now.
Thank
you
very
much
but
like
at.
D
We
could
do
something
at
commons
and
with
the
commons
mailing
list,
I'm
trying
to
I'm
just
about
to
launch
an
end
user
page
for
that,
and
I
really
would
like
to
know
who's
got.
Okd
running
who's
got
ocp
running
rosa,
but
a
lot
of
that
is
competitive
secrets
or
whatever
folks
think
so.
Anything
we
can
do
to
find
out
and
familiarize
us
ourselves
with
that.
I
have
a
sneaking
submission
that
there's
a
lot
more
people
than
rhodium
shorts
and
market
america
using
it
in
enterprise
production.
D
Then
we
suspect-
and
I
think
that's
what
vadim's
data
shows
us
so
asking
them.
What
their
workloads
are,
would
be
really
cool
and
getting
more
of
them
to
showcase
that,
but
also,
I
think,
there's
a
huge
folks,
a
group
of
folks
using
it
in
home,
labs
and
and
doing
and
the
crc
stuff
is
going
to
be
of
of
interest
to
them
and
others
so
yeah.
D
I
I'd
be
happy
to
help
shape
that
and
if
you
guys
have
suggestions
for
questions,
maybe
we
can
create
an
issue
or
a
discussion
point
and
people
could,
in
the
comments,
help
develop
like
I'd,
say
limit
it
to
like
five
questions
we
can
max
and
then
we
can
socialize
it
as
a
poll
at
the
commons
event
at
kubecon
on
the
on
the
landing
page
and
give
it
like
a
three
month.
D
A
Create
a
discussion
item
and
then,
if
folks
have
ideas,
go
ahead
and
chip
it
into
the
discussion
and
yeah,
I
think
you're
right
diane,
just
a
handful
of
questions,
no
more
than
like
six.
That
would
be
the
absolute
max.
You
don't
want
to
overwhelm
people,
so
they
keep
putting
it
off.
A
You
want
something
that,
like
it's
in
front
of
them,
like
oh
yeah,
I
can
do
this
real,
quick
and
just
put
in
mine,
yeah
cool
all
right
and
let's
see
if
there's
oh
and
one
thing,
I
want
to
point
out,
there's
clearly
people
that
have
interest
so,
for
example,
the
okd
working
group
meeting
as
the
video
from
the
last
meeting
has
97
views
so
far
and
it
was
posted
like
just
the
other
day.
A
D
Yeah
so
yeah-
and
this
is
just
if
you're
listing
out
there
on
the
recording
and
you're
going
to
kubecon-
let
me
know
I'd
love
to
connect
with
you.
There
create
a
space
for
the
okd
folks
to
meet
there
either
on
the
12th
of
october.
We
are
going
to
try
and
do
an
okd
office
hours
during
kubecon,
and
you
know
the
cncf
is
still
mustering
through
and
saying
we're
going
to
be
there
in
person.
D
I
personally
cannot
be
go
there
because
I'm
up
in
canada
and
there's
not
there's
just
a
little
border
between
us
and
you
and
that
they're
keeping
it
pretty
stringent.
So
I'm
going
to
be
hosting
the
virtual
side
of
kukan
and
on
the
commons,
so
I'll
be
online
all
the
time,
but
we
do
have
a
space
available
on
the
12
for
a
meeting.
A
Yeah,
no,
no,
I
having
a
small
child.
He
just
turned
one
on
july:
31st
he
can't
get
vaccinated,
so
I'm
sort
of
by
default
cannot
go
to
any
large.
A
D
During
well,
I
was
going
to
wait
until
it's
seven
weeks
out
to
do
one
during
kukan
north
america
week
so
I'll
work
with
chris
short
and
josh
burkus
are
managing
the
office
hours
for
all
the
different
community
groups,
and
so
okd
is
on
their
radar.
So
hopefully
I
can
nudge
them
to
give
us
a
date
and
a
time
and
socialize
it
and
we
can
see
which
one
of
you
wonderful
people
will
be
there
and
maybe
brian
by
then
we
will
have
the
okd
site.
D
Look
migrated
over
to
a
real
world,
mk
docs
thing,
and
we
can
shout
about
it
and
invite
people
to
find
our
grammar
errors.
C
Oh
okay,
all
right,
I
I
got
something.
I
I
quite
like
to
ask
diane
you
sort
of
host
a
number
of
communities,
including
the
key,
which
I
know
you
guys
call
quay.
C
So
I
think
that'd
be
a
really
good
thing
to
have
a
a
sort
of
a
a
private
registry
and
it's
not
an
easy
process
out
of
the
box
on
okd,
but
with
the
operator
on
openshift.
It's
a
couple
of
button
clicks
and
you
get
the
whole
stack
there.
So
I'm
just
wondering:
can
we
actually
do
a
collab
with
them.
C
G
D
Yep,
so
I
have
I'm
going
to
do
the
outreach
to
the
ocm.
Folks
get
us
there
we're
going
to
do
some
outreach
to
the
operator
framework
folks
and
get
us
there
and
collab
there.
I
think
the
remainder
of
2021
and
going
into
2022
should
just
be
more
collabs.
You
know
and
figure
out
how
to
how
to
extend
awareness
of
okd
and
to
make
sure
that
okd
works
with
all
these
other
pro
and
takes
advantage
of
that
and
the
quay
folks.
D
I
actually
started
out
managing
their
community
and
they
have
moved
and
we
got
a
couple
thing
and
so
hopefully-
and
they
have
community
meetings
too,
so
there's
nothing
precluding
any
of
us
from
going
to
their
meetings.
But
maybe
we
could.
D
You
know
I'll
put
that
in
my
notes
too,
and
then
see
if
we
can't
move
that
one
forward
too,
and
just
if
brian,
if
you're
interested
what
I'll
do,
is
I'll,
try
and
find
the
date
and
forward
it
to
you
for
the
next
meeting
and
if
I
can
get
there
and
you
can
get
there,
we
can
talk
about
it
and
you
can
tell
them
what
you
need.