►
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.
https://okd.io
A
A
And
don't
forget
to
put
your
name
in
the
attendance
and
it
looks
like
we
have
a
couple
folks
that
haven't
been
to
meetings
before
if
you
want
to
introduce
yourselves,
feel
free
to
do
so.
No
pressure.
But
if
you
want
to
introduce
yourself
either
in
the
chat
or
live
and
audio
and
video
go
right
ahead.
B
Yeah
sure
hi
this
is
aisha
and
I
work
with
the
with
the
cfe
team
and
with
this
flat
team
as
a
software
engineer
and
mainly
works
with
the
vmware
vsphere
and
ci
related
stuff
christian
introduced
me
for
the
okd
group
and
because
I'm
also
gonna
participate
with
him
as
a
co-speaker
in
a
def
con
2022
for
the
okd
presentation.
B
So
because
I
was
always
been
really
interested
for
okd,
and
I
really
like
I
mean
that's
the
community
thing
and
I
really
like
it
and
I'm
also
really
interested
in
okd.
That's
why
I
am
I'm
joining
this
meeting
and
I
wanted
to
say
hi
to
everyone.
B
C
A
Excellent
well,
thank
you
for
joining
us
and
anyone
else
want
to
introduce.
I
think
we
have
one
other
person.
A
No
okay,
well,
let's
move
on
then,
and
let's
take
a
look
at
the
agenda
and
we'll
start
out
with
issues
in
the
repo
brian.
Are
there
any
issues
or
pull
requests
in
the
documents?
Repo.
D
I
got
the
wrong
window
yeah.
He
he
raised
one
just
off
the
meeting
last
week
around.
D
The
community
section-
and
so
it's
issue,
number
two:
five:
five
in
the
in
the
okidi
or
io
meeting
I'll
post,
the
link
into
the
chat.
D
The
bluetooth
chat,
so
I
think
we're
probably
going
to
need
diane
to
look
at
this
one
because
it
really
looks
as
to
what
is
the
purpose
of
the
external
sort
of
the
community
site
and
should
we
consolidate
it
and-
and
I
think
the
community
site
was
more
around
the
wider
commons
community-
that
everything
was
meant
to
point
to,
but
I'm
not
sure
how
many
other
projects
there
are
that
uses
that,
and
so
I'm
not
sure
we
can
answer
that
today.
A
So
when
I
first
started
attending
the
meetings
there
was
this
community
with
the
charter
which
were
reworking
the
charter.
You
know
the
new
chairs
and
stuff
like
that
were
modified
to
that
recently
and
then
there
was
also.
A
Like
I
think,
that's
where
the
projects
tab
is,
isn't
it:
where
was
there
used
to
be
a
tab
that
had
like
the
meeting
stuff
yeah?
That's
it
so
under
projects,
there's
like
a
oh,
no,
that's
not
it
either.
So
there
used
to
be
a
a
panel,
basically
with
all
of
the
lists
of
tasks
and
whatnot,
and
I
don't
know
it's
in
one
of
the
repositories
it
might
be
might
have
been
in
this
one
in
terms
of
the
community
stuff.
A
D
However,
if
this
was
meant
to
look
at
a
wider
set
of
projects
and
then
I
think
it
just
makes
sense,
but
if
it's
purely
the
okd
community,
I
think
we
should
pull
this
into
the
okidi.io
site
or
put
it
in
the
openshift
repo.
I
don't
think
it
makes
sense
having
a
whole
repo
for
five
markdown
files.
E
E
Like
I,
I
think
that
there
is
a
general
problem
that
you
know
several
other
people
have
brought
up,
which
is
that
our
communications
is
extremely
fragmented,
with
the
number
of
places
where
people
could
go.
E
E
A
The
last
commit
was
the
changing
the
charter
or
changing
yeah.
It
was
like
changing
the
chairs
and
the
the
format
of
the
affiliations,
which
was
something
that
I
did
and
christian
approved
all
right.
Well,
straw
poll
vote
seems
to
indicate
that
well
do
any
of
our
other
guests
have
any
thoughts
on
this.
A
I
don't
want
to
just
be
the
regulars.
Anyone
else
have
any
thoughts
about.
You
know
repos
and
should
administrative
stuff
like
that's
in
this
repo,
should
it
be
separate,
can
it
be
folded
into
a
single
repo
where
we
also
have
our
website
stuff
and
other
files
I'll
give
anyone
a
chance
to
chime
in
if
they
want.
A
Okay
doesn't
seem
like
anyone
has
anything
to
add,
so
I
I
think
we
should
fold
it
in
to
the
new.
Let's
do
it
when
we
make
the
change
to
the
okd
project
github.
D
D
We
are
looking
to
create
our
own
github
organization
and
put
all
our
content
within
that
organization
and
rather
than
within
the
openshift
github
organization,
or
I
forget
what
the
customer
the
cs
customer
support,
which
is
where
the
website
is
so
at
some
point
in
the
near
future.
We're
going
to
put
everything
into
a
new
new
github
organization
for
okd.
E
Related
to
that
change,
I
was
just
thinking
about
how,
like
the
best
sort
of
github
name
was
already
taken,
and
we
tried
to
get
it
back
and
couldn't
which
is
not
untypical.
I
I
think,
with
my
experience
as
well,
so
now
we
have
sort
of
like
okd
projects
or
something
like
that.
Yeah.
E
Project
which
is
not
something
that
would
occur
to
people
to
look
for
right.
So
maybe
we
should
task
diane
to
look
into
search
engine,
optimization
to
move
that
name
up
in
the
list.
So
if
somebody
searches
for
a
you
know
like
okay,
deep
or
something
like
that-
that
that
one
appears
and
and
that
will
give
people
a
way
of
finding
it
in
sort
of
a
natural
way.
A
A
Ones
is
it
that
both
of
them
were
owned
by
someone
was
trying
to
remember
here:
yeah
it's
like
both
of
them
are
like
they
were
created
by
people
and
then
like
never
used,
okay,
so
yeah
we
can't
get
get
on
or
can't
get
okd
on
either
of
them,
which
is
too
bad.
So,
okay,
let's
talk
to
diane,
we'll
I'll.
Add
that
as
an
item
here
so
asks
I'll,
add
that
talk
to
diane
about
seo
by
the
way
she
will
not
be
in
the
next
few
meetings.
A
So,
let's
move
on
to
the
next
item:
are
there
any
pull
requests
that
we
should
be
aware
of
brian
anything
that
came
in
in
terms
of
pull
requests.
A
Okay,
great
new
business,
the
slackdown
channel,
dev
slack
channel-
you
know
going
back
to
folks-
maybe
that
didn't
pick
this
up
in
the
the
main
meeting.
There's
questions
about
the
value
of
having
the
dev
slack
channel.
It's
it's
almost
exclusively
used
by
people.
Posting
user
questions
sometimes
cross
posting
with
the
user
channel
as
well.
E
Well,
I
actually
like
the
way
it's
currently
formulated.
No,
but
I
sort
of
had
this
idea
of
the
two
channels.
Somehow
being
you
know,
one
more
for
admin
issues
and
the
other
for
actual
user
issues
like
people
running
applications
on
okd
would
be
the
users
and
people
administering
okd
would
be.
You
know,
admin,
and
so
I
I
was
originally
like
a
long
time
ago,
looking
at
the
dev
channel
as
being
more
for
people
trying
to
get
okd
itself
to
work
versus
running
loads
on
okd.
E
D
D
I
I
actually
I
actually
question
the
use
of
slack
and,
and
it
really
goes
back
to
the
I
mean
we
have
people
cross
posting,
because
one
they're
not
getting
answers
quickly
enough
because
it
doesn't
seem
to
be
there's
a
huge
community
logging
into
everywhere
to
actually
answer
the
questions,
but
also
I
mean
if
you're
a
new
user
they're
called
openshift,
dev
and
openshift
users,
so
I
I
think
there
might
be
some
hesitation
is:
are
they
actually
for
okd
or
do
I
have
to
be
in
an
openshift
paying
user?
D
I
I
think
that
there
is
some
confusion
around
that.
Certainly
when
I
first
joined
the
community,
I
I
saw
that
it's
like
well.
Do
I
have
to
be
a
paying
user
to
use
this
channel,
but
I
understand
red
hat:
don't
use
this
as
an
official
openshift
channel,
so
it
is
very
much
a
community
channel.
D
My
take
is
trying
to
push
everyone
onto
the
git
of
discussions.
Let's
have
one
place
to
go
for
for
everything.
A
I
think
I'd
be
inclined
to
as
well,
because
then
you
don't
get
repeat
questions
or
you
can
point
people,
it
says
solutions
and
and
whatnot,
as
opposed
to
it's
it's
very
hard
to
keep
linking
back
to
previous
conversation,
conversations
and
slack
and
solutions,
and
so
yeah
I'd
be
inclined
to
to
shut
them
both
down.
But
but
in
conversation
last
week
it
was
said
that
they
want
to
maintain
the
presence
on
the
on
the
kubernetes.
E
A
A
D
A
What
we
talked
about?
Okay,
so
maybe
that's
the
path
forward,
then
just
saying
yes,
okay,
so
the
next
thing
is
something
came
up
last
week
that
was
kind
of
a
surprise.
It
happened
pretty
quickly,
quickly,
sandro
organized
a
stakeholders,
okd
stakeholders
meeting
on
like
monday
afternoon,
and
it
happened
on
thursday
and
it
was
christian,
glombik,
vadim,
diane
myself.
A
Actually
I
had
to
watch
it
later
because
I
was
double
booked
and
a
handful
of
other
folks.
Charo.
Was
there
the
gist
of
it?
Is
that
sandra
wanted
to
know
for
the
virtualization
efforts?
What
is
the
path
forward?
Sandra's
here
sandra
you
want
to
talk
about
the
stakeholders
meeting
that
you
organized.
F
So,
yes,
then
I
was
trying
to
put
together
kind
of
the
situation
of
the
community
and
understanding
who
are
the
stakeholders
and
what's
the
plan
for
the
upcoming
year
or
so,
and
I
understand
that
it's
a
huge
goal-
try
to
understand
what
will
happen
in
a
year
from
now
in
the
open
shift
area
because
it
changes
every
six
weeks.
So
it's
really
hard
to
but
yeah.
F
F
This
one
of
the
things
that
just
now
in
the
rook
io
community
meeting
they
raised
is
that
they
fear
about
having
confusion
between
the
okd
version
and
the
openshift
version
of
the
operator
and
out
of
the
stakeholders
meeting
it
sorted
out
that
there
is
a
plan
for
having
a
dedicated
okd
operator
up,
and
this
will
solve
this
issue.
So
I'm
pretty
sure
that
this
will
help
getting
also
the
rook
io
operator
into
into
kd.
A
Right
and
one
of
the
things
that
diane
suggested
at
that
meeting
and
I'm
going
to
move
forward
with
that-
is
that
we
assemble
a
subgroup
for
operator
stuff,
because
this
has
been
sort
of
ongoing.
We
want
to
address
it
bruce.
I
know
you're
very
passionate
about
it,
but
it
seems
like
a
good
idea.
Maybe
it's
an
async
subgroup
doesn't
have
to
meet,
but
just
defining
tasks
and
pushing
people
to
get
that
community
operator
catalog.
A
The
okd
community
catalog
created
separate
catalog
for
okd
and
can
then
get
it
populated
with
all
of
the
operators.
We
know
and
love.
Is
there
any
opposition
to
that
idea?.
A
Sandra
can
speak
to
this
a
little
bit
more,
but
okay
and
and
other
folks
who
were
at
the
meeting
live
but
the
truth.
The
person
who
currently
is
the
point
of
contact
for
catalogs,
right,
etc.
F
I
have
no
specific
answer
for
that,
because
I
don't
really
understand
how
the
catalog
itself
works,
but
from
what
I
understood
is
a
bunch
of
configuration
files
in
a
github
repo.
So
I
believe
that
it
can
be
handled
completely
on
community
side.
D
The
issue
currently
is
it's
built
using
prow.
All
the
images
are
built
using
prow,
and
so,
for
example,
if
I
want
to
customize
it,
I
go
through
this
sort
of
chase
through
a
lot
of
repositories
to
try
and
work
out
how
I
can
replicate
the
build.
Nowhere.
Do
we
have
like
in
in
a
traditional
open
source,
repo
there's,
usually
an
instruction
says
how
to
build
this.
E
D
Where
I
think
the
red
hat
ones
talk
about
the
internal
prow,
build
process,
ci
process
and
there's
all
sorts
of
linkages
in
with
that,
and
you
look
at
a
single
repository
and
it
just
links
to
other
repositories,
and
it
just
seems
to
be
a
an
endless
chain
of
trying
to
follow
stuff
through
and
missing
information.
D
D
A
Let's
I
think
that
that's
a
that's
a
a
question
for
this
subgroup
to
to
find
out
and
do
the
research
and
meet
with
red
hat.
We
have
some
names
of
people,
there's
the
person
that
we
talked
about
at
the
last
meeting
and
then
there's
some
people
that
came
out
of
this
meeting
on
thursday
that
we
can
talk
to.
Let's
get
a
list
of
people
together
who
are
interested
in
this
topic,
and
maybe
it's
the
same
group
I
don't
know
diane
was
suggesting
a
subgroup.
A
There
might
be
people
who
are
interested
in
operator
stuff,
but
not
interested
in
documentation.
Let's
get
that
group
together,
work,
asynchronously
and
press
some
buttons
and
see
what
happens.
I
think
we
can
do
some
research
looping
in
vedim
looping
in
christian
and
looping
in
the
person
whose
name
I
forgot
already
that
we
talked
about
at
the
main
meeting
last
week
and
seeing
exactly
what
is
possible.
A
D
Yeah,
even
if
we
can't
modify
it
if
we
can
clone
the
repo
and
customize
it
for
our
own
personal
needs
right.
I
think
that
would
be
something
where,
at
the
minute,
it's
not
obvious
or
trivial.
How?
I
would
do
that
say
for
the
community
catalog
that's
currently
in
okd,
and
I
mean
that
should
all
be
public
open
source
stuff,
but
trying
to
work
out
even
how
to
rebuild
that
and
get
that
configured
into
okd
is
not
a
trivial
task
for
anybody
at
the
minute
right.
E
Yeah
now
I
I
guess
my
main
concern
would
be
that
going
from
the
current
version
to
an
okay
version.
We
then
cut
the
number
of
operators
down
by
another
factor
of
10,
and
so
we
have
an
okd
catalog
that
has
like
one
operator
in
it,
and
it
is
you
know,
maybe
the
lcd
operator
well.
A
You
can
you,
can
it's
an
array
right?
Isn't
it
isn't
the
catalog
list?
Isn't
it
a
list?
It's
a
container.
E
Though,
because
if
like,
I
was,
I
discovered-
oh,
I
know
a
short
while
ago
that
if
you
have
an
operator,
that's
in
the
catalog,
that's
you
know
that's
managed,
then
you
cannot
have
your
own
version
of
the
same
operator.
So
like
there's
a
wildfly
operator
in
the
sorry.
Well,
it's
that
that
one's
actually
not
an
operator,
so
maybe
it
doesn't
play
the
operators,
there's
a
a
a
wildfly
builder
image
and
that
gets
tracked
whenever
they
update
the
version
and
it's
generally
a
couple
of
versions
behind
okay,
fair
enough.
E
So
before
it
was
there
at
all,
I
could
install
my
own,
but
once
it's
there,
then
it
overrides
what
I
install,
and
so
there
are
some
interactions
with
things
you
know
like
these
sort
of
official
versions
of
stuff,
then
constrain
your
custom
versions
that
you
can
put
in
normally.
E
E
Without
my
having
to
prove
everything-
and
you
know
the
the
rook
stuff
operator
would
be
nice.
You
know
like
I.
I
would
mind
going
to
that.
I
would
as
long
as
it
didn't
blow
away
my
existing
setup
and
everything
that's
stored
in
there.
That
would
be
sort
of
unfortunate,
but
you
know
so.
I
guess
in
principle
good
idea
see
what
the
details
are.
D
D
F
F
F
D
E
So,
basically,
because
I've
sort
of
resisted
for
the
past
quite
a
while
using
my
you
know,
developer
pull
secret.
But
from
what
I
understand
you're
saying
sandro
is
that
with
this
new
system,
as
you
get
the
same
operators
with
no
pull
secret,
as
I
would
get
using
my
red
hat,
pull
secret.
F
E
Right
and
then
I
guess,
a
related
question
would
be
well.
Okay,
so
does
the
community
have
any
ability
to
do
it
if
the
red
hat
developers
ignore
it
for
a
particular
operator.
A
F
A
All
right,
so,
let's
look
at
the
task
list,
create
a
list
of
links
to
add
to
the
pr
against
product
documentation
to
add
an
extra
book
to
provide
links
to
the
community
documentation.
We
haven't
done
that
yet
that's
to
provide
to
michael.
We
should
get
started
on
that.
If
someone
wants
to
take
the
initiative
on
that,
one
put
your
name
next
to
it.
On
that
first
task
there
send
email
to
regroup.
Look
at
the
code
of
conduct.
A
Diane
wants
us
to
get
it
in
by
the
next
main
meeting,
so
I'll
send
a
reminder.
Email!
I
get
out
one
more
time,
but
we've
been
asked
about.
You
know:
where
is
the
code
of
conduct?
A
You
know
because
it
says
actually
even
says
on
the
website
like
in
progress
or
something
like
that
or
to
do
so.
Let's
commit
to
all
looking
at
that,
and
the
main
group
will
have
a
vote
and
sign
off
on
it
at
the
main
meeting.
The
next
main
meeting
next
week
create
template
from
general
presentation
sandra.
Did
you
get
everything
you
need
in
terms
of
template,
presentation,
template.
F
D
A
Find
out
who's
behind
okd
linkedin?
Who
was
going
to
do
that?
That
was
diane,
I
believe
yeah
and
don't
know
that
anything
has
come.
Then
I
didn't
get
a
chance
to
talk
about
vanity
links
yet
and
and
the
playlist
I
wanted
to
create
the
playlist
in
at
the
same
time
that
to
see
if
we
can
have
a
vanity
link
for
that
playlist
and
for
the
okd
group
and
see,
if
not
maybe
we
create,
I
don't
know
we'll
see,
we'll
see
what
that
is,
follow
for
youtube
content.
A
We
haven't
done
that
yet.
Does
anyone
want
to
to
write
up
a
call
out
for
youtube
content
and
want
to
take
a
stab
at
a
paragraph
or
two
of
an
email
to
send
out
to
the
community
asking
for
videos
of
installing
okd
using
okd?
A
A
So
it's
like,
there
are
people
out
there,
making
videos
that's
cool,
but
we
should
see
if
we
can
get
them
at
least
promoted
through
our
social
media
and
stuff,
like
that.
Anyone
want
to
take
a
stab
at
writing
a
paragraph
or
two
to
do
that.
A
Anyway,
all
right
we'll
leave
that
as
a
standing
item,
then
I've
got
too
much
on
my
plate
to
take
on
writing
review
code
found
it
for
next
meeting.
We've
got
that
I
did
talk
to
vadim
about
going
over
repo
materials,
and
that
meeting
will
also
have
a
conversation
about
closing
down
the
dev
slack
channel
brian
I'll
get
with
you,
because
vadim
had
some
suggested
times
that
work
well.
So,
let's
the
three
of
us
get
together.
A
D
Else
yeah.
I
just
think
we
need
to
capture
a
task
list
that
we
need
to
work
out.
What's
going
on
with
the
the
survey
and
also
the
twitter
credentials
right,
we
talked,
we
talked
about
it
on
the
main
meeting,
but
yeah,
I'm
yeah.
A
Sorry
I
have
updates
on
that.
So
diane
now
has
the
credentials
and
we
we
don't
have
an
update
on
the
survey
yet
turns
out.
Driti
was
was
out
for
a
couple
weeks
on
pto
and
just
got
back.
I
think
like
in
the
past
couple
days.
A
So
let's
check
in
with
that
asynchronously
I'll
reach
out
to
driti
directly
and
find
out
what
the
status
is
on
the
survey
and
then
let's
commit
to
getting
it
out
or
signing
off
on
it.
If
driti
can't
do
the
extra
work,
let's
just
do
it
as
it
is
because
I
think
it
was
pretty
well
close
to
being
done,
because
I
think
at
this
point
we
just
need
to
get
something
out
to
help
define
sort
of
steps
forward
and
whatnot.
E
Anything
else
I
I've
got
something
sort
of-
I
guess
new
and
wildish
in
a
way,
but
it
does
relate
to
documentation
okay,
so
you
might
have
seen
many
years
ago
there
were
a
couple
of
books
that
red
hat
was,
you
know
flogging
for
free
one?
E
One
of
them
was,
you
know,
open
shift
for
developers
covers
openshift
three
and
the
other
was
devops
for
open
for
openshift
three
or
something
like
that,
and
neither
of
them
was
ever
updated
for
openshift4
and
the
possibly
because
the
authors
are
no
longer
around
like
grant.
Shipley
was
the
the
one
of
the
authors
and
he's
long
gone,
but
I
wonder
if
it's
if
it's
worth
updating
those
like
they
were
introductory
books
and
it
might
be
worth
updating
the
okd
for,
but
you
know
sort
of,
I
guess.
E
D
Sorry
bruce,
I
actually
think
that's
incredibly
useful
because
that's
my
main
use
case
that
I'm
trying
to
achieve,
but
I
think
there
is
a
dependency
on
getting
the
operators
sorted,
because
at
the
minute
we
don't
have
an
ability
to
easily
install
any
of
the
devops
tools
that
are
in
ocp
in
okd
at
the
minute
until
we
get
those
red
hat
operators
available
to
okd.
D
But
I
actually
think
that's
a
very,
very
valuable
thing,
because
I
think
one
of
the
challenges
is
when
we
get
okd
installed.
It's
like
well
what
next
right?
Where
do
I
go
from
here
and
at
the
minute
until
we
get
things
like
the
the
the
pipelines,
the
tecton,
the
get
offs
as
an
integral
part
of
an
okd
install?
I
think
we're
missing
a
huge
part
of
the
strategic
getting
started
as
a
developer
learning
how
to
do
pipelines
with
techcons
rather
than
the
old,
build
subsystem.
E
Yeah-
and
I
mean
right-
and
I
I
agree
with
that-
and
that
would
make
the
devops
one
difficult
at
the
moment,
but
the
developer
one
openshift
for
developers,
you
know
a
guide
for
impatient
beginners
that
one
would
be
very
easy
to
update.
E
You
know
basically,
like
I
I'm
running
my
students
through
analogous
things,
so
I
wouldn't
have
a
big
difficulty.
Updating
that
I
mean
it
was
only
like
an
81-page
document
with
a
repo
behind
it,
so
that
you
could
run
the
code,
but
that
that
seems
feasible
and
it
just
sort
of
surprises
me
that
there
was
this.
E
I
guess
big
push
from
red
hat
back
in
openshift
3
and
some
of
the
things
you
know
never
carried
forward,
and
it
was
a
it
was,
I
think,
a
somehow
they
they
got
involved
with
o'reilly
o'reilly
published
it.
E
Yeah,
I'm
happy
to
get
involved
with
that.
The
question
is
where,
to.
E
Let's
ask
I
asked
diane
and
I'll
see
if
I
can,
you
know,
send
an
email
to
grant.
If
I
can
find
him
again.
A
E
A
E
Wait
one
last
comment:
okay,
it's
copyright,
2016,
red
hat.
A
A
Well,
we'll
see,
maybe
we
can,
you
know,
get
them
to
update
it
or
or
do
something
yeah
by
the
way
that
book,
what
is
it
hybrid
cloud
apps
with
openshift
and
kubernetes,
is
pretty
good
that
came
out
this
summer.
That
was
actually
really
important
this
last
summer,
I
was
actually
pretty
impressed
with
it
yeah.
Well,
that's
probably
three
or
four
authors
on
it.
Three
authors
on
it.
A
A
Then
the
main
meeting
next
week
would
be
the
best
one
to
find
out
about
involvement
in
helping
out
on
the
group
in
general
and
thanks
sandro
for
popping
in
and
updating
us
on
what
happened
thursday
and
I'll
put
more
info
on
that
and
what
came
out
of
that
meeting
into
the
meeting
notes
and
I
think
we're
good
to
go.
Thank
you
folks.