►
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
B
There's,
I
think
what
might
be
useful
is
just
putting
like
we
do.
The
main
meeting
review
the
issues
and
pull
requests,
because
I
think
we're
now
saying
that
that's
part
of
this
meeting.
A
Full
request
and
then
new
business,
okay,
so
and
don't
forget
to
put
your
name
in
the
attendance
part
of
the
document.
That
way,
we
know
who
was
hearing
you
have
to
talk
to
someone
if
they
missed
something
and
put
your
affiliation.
That
always
helps
okay.
A
Let's
see
charter
update
and
placement
there's
no
update
on
that.
I
do
actually.
I
did
open
an
issue
but
no
update
on
that
beta
site,
brian,
any
updates
in
general.
B
Other
than
it's
no
longer
beta,
it's
running
as
normal
from
last
doc's
meeting
I've
added
the
section
on
how
to
actually
create
new
content.
We've
got
three
sections
there.
We
got
one
if
you
want
to
install
the
stuff
locally
one
if
you
want
to
use
podman
or
docker
and
then
the
other
one.
B
If
you
wanted
to
use
in
cluster
with
che
I've
added
a
dev
file
to
the
repo,
and
so
any
feedback
on
that
will
be
greatly
appreciated,
and
I
also
noticed
that
in
the
working
group
session,
I've
missed
the
main
working
group.
I
put
all
the
sub
working
groups,
but
I
actually
hadn't
put
anything
about
the
main
working
group,
so
I
changed
that
and
obviously
the
two
links
in
the
bottom,
the.
B
Github
now
goes
to
the
okd
open
shift,
okd
main
repo,
instead
of
the
the
comments
and
with
the
new
twitter
handle.
That's
now
in
the
bottom
comment
as
well,
but
the
facebook
sold
it
goes
to
the
openshift
facebook,
so
they're
the
changes
since
the
last
stocks
meeting.
But,
as
I
say
it's
now,
business
as
usual,
I
think
moving
forward
which
is
no
longer
beta.
We're
live
we're.
B
No
one
screamed
that
it's
terrible
and
we
should
revert
it
back
or
anything
like
that.
So
I'm
calling
it
done.
This
is
closed.
It's
it's
now.
Production.
A
All
right:
well
then,
let's
move
on
to
name
and
scope
of
install
and
readme
haven't
done
anything
on
that
brian
broke
up
a
lot
of
that
and
put
that
in,
but
now
we
just
need
to
to
rework
those
actual
files
in
the
in
the
the
code
repo
or
the
the
okd
repo.
B
B
B
If
you
want
to
extend
and
add
new
capability,
and
I'm
just
thinking
how
do
we
want
to
do
that,
because
I
think
some
of
the
information
in
there
will
fall
into
that
sub
sub
grouping
or
sub
categorization
of
information,
so
it
might
be
worth
just
thinking
about
how
we
want
to
organize
documentation
generally
for
the
I
want
to
do
more
than
use
okd.
I
want
to
be
able
to
get
into
the
covers
and
do
stuff.
A
A
Is
that
the
read
me
on
the
okd
repo
should
just
be?
This
is
how
to
file
an
issue.
This
is
what
you
should
do
if
you
have
an
issue.
This
is
what
you
should
do.
If
you
want
to
talk
about
something
like
breaking
down
the
the
issues
and
discussions
section
of
that
repo
for
actual
code
related
stuff,
I
think
modifications
should
go
on
the
website.
B
B
A
Yeah
I.
A
Yeah-
and
I
mean
so,
if
we
look
at
this
here-
let's
let
me
bring
it
up
actually
real,
quick.
D
A
What
are
you
seeing
right
now?
I.
A
All
right
so
yeah
I
mean
at
this
point
the
repo
is
becoming
you
know.
So
let's
look
at
the
the
read
me.
So
if
you
look
at
the
read
me
there's
this
explanation
of
what
it
is
right.
A
Right
exactly
and
and
we
can,
I
feel
like
getting
started,
having
a
getting
started
in
the
repo
file.
The
repo
readme
makes
sense,
because
there
are
some
folks
who
go
directly
to
repos
for
open
source
projects.
What.
B
B
E
A
Right,
yeah!
Well,
so
I
I
feel
like
the
this
info
about
the
installer
and
stuff
like
that.
It
starts
out
in
one
place
and
then
this
whole
thing
and
then
it
sort
of
ends
up
in
another.
It
kind
of
meanders,
yeah
and.
B
E
E
You
know
sort
of
evolving
from
that,
okay
and
in
a
way,
whatever
we're
going
to
do
now,
it
might
be
an
interim
step
because
it
would
sort
of
be
useful
to
do
what
we
were
talking
about
in
the
other
meeting,
which
is
get
to
a
sort
of
an
oc
cluster
up
type
capability
yeah,
which
basically
means
you
know
stripping
out.
You
know
metrics,
and
you
know
you
know
basically
stripping
out
all
the
stuff
that
makes
okie
d
useful
in
production.
B
E
B
A
B
A
B
Because
I
mean
the
problem
is:
if
they're
there
and
you're
in
the
documentation,
you're
not
gonna,
find
them
if
you're.
So
we
need
the
information
in
one
place
yeah,
and
maybe
we
take
it
to
the
other
meeting,
that
we
shut
down
all
content
in
here
and
move
it
onto
the
website.
If
it's
gonna
sort
of
persist.
A
Yeah
well
because
this
has
all
been
rewritten
this
one
I
wrote
and
that
one's
that's
old,
old,
vsphere,
terraform
yeah.
Actually
these
shouldn't
have
been
updated.
What
we
should
have
done
is
pulled
them
a
while
back,
because
that's
part
of
the
stuff
that
was
rewritten
and
moved
over
the
work
that
mike
did.
B
A
Right
so
let's
do
that,
then,
let's
bring
this
to
the
greater
group
that
we
limit
guides
and
we
limit
this
repo
to
just
discussions
and
pull
requests
and
issues
related
to
the
code
base
itself
or
the
the
release
itself.
And
then
we
modify
the
readme
to
go
to
the
dogs,
the
docs.
Now
what
about
known
issues,
because
vadim
is
probably
going
to
ask
about
that?
Do
we
keep
known
issues
and
faq
here
or
do
we
do
them?
Well,
I
think
he
was
on
the
website
now
right.
B
B
A
markdown
file
it's
trivial,
to
update,
so
I
I
would
say
that
that
is
the
single
source
of
information,
and
this
is
purely
for
discussing
changes,
raising
issues
as
we've
highlighted
in
our
sort
of
community
guidelines.
This
is
a
place
where
you
talk
about
changes
and
potential
bugs
and
that's
the
purpose
of
this
repo.
Now
information
is
on
the
website
and
this
is
a
sort
of
a
way
of
managing
issues
and
and
bugs.
A
A
A
B
I
think
we
just
put
them
to
website,
because
that's
all
in
the
website,
then,
if
we
want
to
reorganize
a
website,
this
doesn't
get
left
behind
and
I
think
there.
E
Is
not
yeah
brian,
it
should
be.
Aren't
you
really
saying
that
there
is
no
use
for
this
repo?
Well
like
it
is
it
all?
We
should
really
close
this
one
down.
B
A
Well,
let
me
ask
you
this,
though,
is
there
a
reason
why
we
wouldn't,
in
the
s
the
okd.io
repo,
have
a
a
tags
for
issues
to
separate
out
website
versus
code.
B
We've
got
nowhere
because
most
of
the
upstream
most
of
the
content
comes
from
upstream
repo.
So
if
you
want
to
raise
a
bug
on
okd
other
than
redeems
installer
repo,
there's
no
way
to
put
that
bug
or
if
you
want
to
have
a
discussion
around
say
the
work
that
we're
doing
on
on,
say
getting
operators
updated
and
things
like
that.
There's
no
way
we
can
have
that
discussion
and
this
repo
is
that
purpose.
So
I
I
think,
having
this
as
not
for
content,
but
to
do
the
manage
the
discussions,
the
bug
requests
for
okd.
B
I
think
that's
a
good
use!
Okay,
if
we
were
a
bit
more
formal
we'd,
use
those
issues
and
put
a
zen
hub
or
something
on
the
front
of
it,
and
this
would
then
be
our
task
tracking
as
well.
But
as
we're
not
that
that's
a
reformal
here,
then
we
just
need
the
discussions
and
the
the
issues.
A
A
A
There
is
yeah
now
I
and
I
actually
have-
I
actually
created
a
ticket
with
diane's
name
on
it,
to
look
at
the
legal
and
security
to
check
with
legal
and
security
at
right
now
to
see
if
that's,
okay,.
B
So,
ideally
we
we
want
to
shut
this
one
down.
We
want
to
shut
the
ok
dot
io
down
and
move
them
both
to
the
new
git
hook,
the
okd
org,
wherever
that's
going
to
end
up
living,
that's
the
way,
I
would
see
it
going
and
then
community
members
can
then
be
admin.
A
All
right,
yeah,
that's
that
makes
sense.
So
let's
run
this
by
the
main
group
then
and
see
where
we
go
from
there
see
if
anyone
has
any
concerns
about
doing
that.
Okay,
so.
E
Just
to
summarize
jamie,
then
our
proposal
is
to
move
the
content
to
okd.io
and
leave
the
discussions
and
issues
here:
yeah,
okay,
all
subject
to
everything,
moving
right,
yeah!
Thank
you.
Yeah.
A
Let
me
find
this
here
create
build
a
code
of
conduct,
michael,
isn't
here,
to
respond
on
the
status
of
the
code
of
conduct
treaty
survey.
C
Okay,
hi
jim
I'll,
just
give
me
a
second.
Let
me
fix
my
earphone.
C
Okay,
I'm
gonna
share
my
screen.
C
Can
you
see
my
screen?
Yes,
we
can.
So
this
is
the
user
survey
that
I
have
created.
I'm
gonna
share
it
with
you
and
everyone
else
so
that
you
know
for
feedback.
But
how
does
this
look
I
have
compiled,
or
this
was
the
question.
This
is
about
eight
eight
questions
over
here.
C
This
was
suggested
by
somebody
in
the
last
meeting.
What
version
of
okd
are
you
using,
although
it's
not
in
in
this
this
discussion,
but
it
was
suggested
last
time,
so
I
added
it
over
here.
So
the
questions
are:
what
version
of
focus
are
you
using?
C
A
Let
me
let
me
ask
you
something
about
the
before
you
move
on.
Let
me
ask
you
about
that,
one.
Maybe
should
we
maybe
ex
you
know,
and
I
can
I
can
comment
on
this
as
well,
but
yeah
should
we
maybe
what
do
we
mean
by
using
it
like
developing
on
it
administering
it
like?
We
might
want
to
clarify
like
like
what
we
mean
by
using
it
or
write
the
sentence
in
such
a
way
that
that
it's,
you
know.
B
And-
and
I
think
the
other
thing
is
sorry-
I
missed
the
first
couple
of
questions.
Yeah.
Are
you
asking?
Are
you
using
it
in
a
business
or
personal
content?
That's
a
good
question,
yeah
yeah,
because,
obviously
that
that
question
doesn't
make
sense
and
what
we
don't
want
to
do
is
we
we
don't
want
people
to
think.
Oh,
you
only
want
business
users
here.
E
Okay,
yeah
and
you
should
also
think
about
multiple
versions,
because
people
can
be
easily
using.
You
know
like
at
the
moment
four
seven,
four,
eight.
E
C
Moving
on
the
other
questions
are
which
optional
operators
are
you
using
now
this
was
suggested
by
vadim,
which
operators
are
you
lacking
those
two
questions,
so
I
reframed
it
like
which
operators
are
currently
missing
and
are
needed.
Maybe
I
need
to
reframe
it
in
a
better
way.
This
particular
again
how
helpful
is
yeah.
A
A
Question
do
we
anticipate?
This
is
more,
I
guess
for
the
larger
group.
Do
we
ever
anticipate
adding
content
like
operators
that
are
not
default
in
ocp?
B
A
E
E
A
Okay,
by
the
way
there's-
I
don't
know,
if
folks
saw
the
discussion
I'll
just
mention
here,
a
matter
of
fact.
I
need
to
log
into
the
issue
and
comment
because
I
mentioned
that
I
would-
and
I
just
haven't,
had
a
chance
yet,
but
last
week
someone
pointed
out
that
they
found
the
error
as
to
why
it's
a
fluent
d
and
journaling
issue
as
to
why
the
logging
operator
isn't
available
yet
and
the
response
from
the
person
at
red
hat
will
was
well
eventually.
A
The
versions
will
sync
up
and
you
know
then
we'll
be
able
to
release
the
logging
operator
for
okd.
Obviously,
that's
a
less
than
desirable
response,
yeah
once
the
journal
yeah.
So
basically
it's
the
way
the
journal
journaling
is
being
done.
There's
an
older
version
on
our
costs
and
because
fcos
is
a
newer
version
of
fedora
and
there's
the
newer
journaling
that
that's
an
error.
That's
holding
it
up.
So
I'm
going
to
respond
to
that
thread
as
well
and
if
other
folks
want
to
mine.
A
That
would
be
helpful
because
if
we
could
get
openshift
logging
in
there,
that
would
be
very
helpful
anyway,
a
little
bit
of
a
diversion.
But
I
want
to
make
sure
folks
were
aware
that.
C
Okay,
so,
coming
back
to
this
after
this
there's
a
question
for
okada
documentation,
how
helpful
is
official,
okay,
documentation
for
achieving
your
goals?
Can
we
add
any
other
question,
or
should
we
reframe
this
question.
A
C
A
Well,
could
we
add
a
question
where
that's
open-ended
about
their
response,
so
in
other
words
a
question
after
that
that
would
be
like.
Can
you
elaborate
on
your
response
to
the
question
above
or
you
know
something
like
that,
so
that
we.
A
That
it's
two,
you
know:
why
is
it
a
two?
What
is
it
that's
lacking
in
the
documentation,
yep.
B
A
A
Have
you
are
you
interested
in
using
code
running,
have
you
or
will
you
be
using
code,
ready
containers
or
something
like
that?
I
don't
know
brian.
What
do
you
think
bruce.
E
Yeah,
I
guess
that
is
sort
of
two
separate
things.
Isn't
it
one
question
is:
do
we
want
to
know
if
people
have
been
using
it
and
that's
sort
of
interesting,
but
it
doesn't
really
affect
what
we
do
in
the
future,
which
is
what
you're
interested
in.
B
A
E
Exactly
so,
for
the
c
from
the
crc
side,
what
would
be
most
useful
is
well,
okay,
one
are
you
using
it
and
two?
If
not,
how
would
you
want
it
change
so
that
it
would
be
useful
to
you
or
something
like
that.
B
E
B
B
Yeah,
it's
like
if
you
could
run
a
a
personal
copy
on
your
laptop.
Would
that
would
you
find
that
useful
or
a
cut
down
version
on
your
laptop?
Would
you
would
you
use
that
or
something
something
along
those
lines?
Just
so
we
can
have
an
information
and
then
just
ask:
what's
the
memory
footprint
of
your
laptop
8,
16,
32,
64,
gig
and
just
see
what
people
wanting
to
take,
because
that
would.
E
C
But
I've
seen
it
in
some
other
google
forms.
So
let
me
find
that
out.
C
B
A
E
B
A
D
A
C
And,
and
and
after
that,
one
question
for
the
community:
do
you
think
we
should
add
this
over
here?
What
could
we
do
to
make
the
community
more
welcoming,
or
do
we
need
this
yeah?
I
think
so
should
I
add
some
add
one
more
lik,
any
additional
comments.
A
question
like
that.
A
C
A
C
Okay,
thank
you.
So
we
we
have
a
twitter
account
and
I
hope
you
know
that
we
I
cray
so
I
talked
to
diane
and
she
suggested
this
channel.
Okd
underscore
I
o-
and
this
is
the
this-
is
the
profile
I'll
share.
It.
C
We
send
our
first
tweet
and
the
your
question
was
about
how
to
you
know
giving
the
twitter
access
to
others.
So
I
think
I'm
gonna,
I
don't
know
I'm.
I
shared
all
the
password
and
everything
with
diane
already,
but
I
saw
something
like
this,
so
maybe
you
know
we
could
share
this
this
through
tweet
deck.
C
C
So
let
me
start
with
diane
and
then
we
can
I'll
share
it
with
diane,
and
then
we
can
take
it
from
there
who
else
to
add.
C
A
A
Maybe
start
following
back
people,
not
just
anyone
who
follows,
but
you
know
right
exactly
like
the
sig,
maybe
follow.
Some
of
us
follow.
Other
kubernetes
based
twitter
handles
other
git
ups.
Twitter
handles
things
like
that.
B
A
A
Yes,
issues,
sorry,
I'm
I'm
not
used
to
it
yet.
Obviously,
so
let's
go
to
issue.
A
Right
and
update
the
group
charter
is
in
there
gather
legal
input.
I
put
these
in
like
just
a
bit
ago,
yeah
so.
A
B
That's
probably
one
that
we
need
to
talk
about
whether
this
meeting
or
the
next
one
and
the
one
I
actually
want
to
close
off
is
the
last
one
on
the
list,
the
modification
required
for
inclusive
language.
I
put
a
comment
in
there
and
we've
got
66
instances
of
the
word
master,
which
gets
flagged
by
the
inclusive
tool
and
they're
all
down
to
links
to
other
repos,
and
I've
listed
the
one
two
three
four
five
repos
we
have
links
to
that
have
their
primary
branch
called
master
and
then
the
main
use
is
obviously
okd
and
openshift.
B
E
I
noticed
it's
it's
in
the
console
as
well.
There's
several
places
that
talks
about
you
know
masternodes.
B
Yeah,
so
there's
nothing
in
there
that
is
inflammatory
or
people
could
take
offense
to
in
terms
of
our
content,
but
there's
the
66
cases
that
are
flagged
by
the
tool
and
they're
all
legitimate
uses.
So
I
think
we
can
close
this
issue
off.
I
did
look
at.
Could
we
make
this
part
of
the
publishing
pipeline,
but
the
issue
comes?
Then
it's
it's
a
subjective,
this
decision
there
is
not
a
sort
of
yes
or
no
case
because,
like
with
these
66,
you
have
to
look
at
it
and
say:
is
this
offensive?
B
So
I'm
proposing
that
we
close
this
issue
with
no
further
action
needed.
E
Well,
I
guess:
okay,
I'm
totally
happy
with
that.
My
question
is:
do
we
need
diane's
blessing
coming
from
the
red
hat
side
of
things.
D
A
Yeah,
I
would
just
assign
her
to
the
ticket
and
then
put
a
your
adder
to
the
ticket
and
then
for
a
last
comment.
But
you
know
diane.
Will
you
right.
A
So
the
thing
about
that
one
is
that
the
main
group
decided
that
we'd
want
to
get
a
community,
a
security
liaison
or
someone
to
sort
of
to
speak
about
that,
and
we
did
talk
about
this
group
publishing
some
security
information.
I
think
that's
a
little
bit.
A
I
think
we
should
wait
until
after
the
holidays
to
take
that
one
on
in
essence,
what
we're
going
to
want
to
do
is
we
have
those
links
that
we're
in
the
main
meeting
folks
through
in
links,
we're
going
to
want
to
define
some
sort
of
process
and
get
a
volunteer
to
be
sort
of
the
person
to
scan
those
and
make
sure
that
you
know
we
haven't
missed
anything
or
add
anything
or
you
know
whatever
I'm
kind
of
maxed
out
in
terms
of
time.
A
E
A
Let's,
let's
take
this
up
in
december
and
we'll
we'll
circle
around
and-
and
you
know,
basically,
we
need
a
web
page
that
puts
all
those
links
in
a
nice
coherent
way
with
some
explanation
and
then
provides
like
a
contact
or
actually
a
description
of.
If
you
think
you
have
a
security
issue,
you
know
reach
out
to
x,
email
which
we
don't
really
have
a
dedicated
email
right
now
for
this
stuff.
B
A
All
right
is
there
anything
else
that
we
want
to
talk
about
not
right.
Well,
I
am
going
to
stop
recording
here
and
I
appreciate
everyone
coming
for
the
meeting.
A
lot
of
great
work
has
been
coming
out
of
these
meetings.