►
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 will also include the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope.
A
Let's
get
started,
we've
got
the
slim
crew
here
today,
diane
had
to
step
away
for
an
all-day
meeting
so
and
jump
right
into
our
agenda,
and
it
looks
like
actually
I
can
take
diane's
brian
michael
bruce.
Can
you
put
your
name
in
the
in
the
document
here
clear
out?
The.
A
A
A
Oh
yes,
actually
so
diane
merged
it
14
days
ago
it
looks
like
they
did,
get
the
last
little
bit
squared
away,
and
so
the
guides
now
are
merged
into
the
okd
dot
io.
A
A
A
Link
so
now
it
is
all
just
what
is
okd
installation,
documentation,
blog
and
community,
and
why
don't
we?
Actually?
This
seems
like
a
good,
a
good
place
to
actually
move
and
put
brian's
stuff.
I'm
gonna
move
our
agenda
around
here,
because
actually
now
would
be
a
great
time
for
brian
to
give
us
an
update
on
the
beta
side.
C
Yeah
on
me
myself,
so
that
always
helps
yeah
there.
There
is
probably
easier
if
I
do
this
yeah
go
ahead
and
share
your
screen.
If
you
want.
C
C
It'll
actually
check
all
links,
so
just
a
warning
whenever
you
do
an
update
to
the
site,
you're
also
responsible
for
fixing
any
broken
links
and
so
it'll,
it
checks
all
the
links
in
the
site
and
will
tell
you
there
are
broken
links
and
then
it'll,
obviously
publish
now.
The
one
issue
I
have
is,
I
don't
have
access
to
the
settings.
C
So
we
need
that
setting
made
because
at
the
minute
the
github
pages
site
isn't
active
and
but
I
actually
don't
have
access
to
the
page.
So
if
you
look,
we
actually
are
creating
the
there's
a
lot
of
branches
in
here
we
are
actually
creating
the
git
for
pages
site.
So
this
is
the
source
of
the
beta
site,
so
it's
all
there,
it's
all
working,
but
obviously,
until
we
turn
on
get
to
pages
for
this
project,
we
don't
get
to
see
it.
So
I
don't
know
whether
you
have
access
jamie.
C
We'll
need
to
get
whoever
a
red
hat
act
has
access
to
this
to
go
and
turn
that
on
just
and
again
we
can
actually
send
them
a
screenshot
of
this
page.
If
you
want,
we
just
need
the
source
to
be
github
pages
branch
and
we
want
the
root
and
nothing
else.
We
can
enforce
https
and
that's
it
so
in
the
pages
section
on
the
settings,
just
those
two
settings
and
that
will
turn
on
the
beta
site
and
then
it'll
also
give
us
the
url.
C
So
that's
probably
just
going
to
be
the
open
shift,
dash,
cs,
github.io
and
then
it'll
be
okd
to
I
o
would
be
the
url,
so
that's
actually
getting
the
site
there.
So
every
time
we
push
code
to
the
beta
branch,
it
doesn't
touch
the
main
branch
or
the
master
branch
as
it's
defined
here.
It's
just.
This
beta
branch
will
actually
kick
off
the
github
action
to
actually
do
that.
So,
if
I
go
back
to
to
my
site
that
I
sort
of
tried
all
this
out,
we
do
have
some
decisions
to
make.
C
So
this
is
what
it
looks
like
at
the
minute
now.
I
think
we
need
to
change
this.
I
want
to
make
this
much
much
simpler.
This
also
uses
bootstrap
framework
which
causes
some
issues.
So
if
I
shrink
this,
you
notice
that
it
doesn't
necessarily
work
very
well.
The
menu
just
doesn't
work,
because
the
bootstrap
is
interfering
with
the
underlying
mk
docs
framework.
C
So
there
are
some
issues
in
terms
of
just
getting
that
reactive
sort
of
content
working.
So
we
do
need
to
work
out
what
we
want
on
the
simple
side
and
then
also
are
these
colors.
Okay,
I
mean
I
just
picked
from
the
home.
I
just
picked
these
two
colors,
but
I
don't
know
whether
this
is
what
we
want,
the
other,
the
rest
of
the
site
to
look
at.
Do
we
want
it
to
be
different,
colors,
I'm
using
red
as
the
active
highlights.
C
I've
actually
picked
up
the
the
the
font
and
the
styling
from
what
we
have
on
the
current
site,
so
I've
actually
adopted
the
same
fonts
as
the
old
site
users,
but
again
there's
a
lot
of
sort
of
style
issues
that
we
need
to
discuss
and
then
obviously
we
just
need
to
make
sure
we
move
the
content
across
because,
obviously,
what
you've
just
done,
I
mean
I
didn't
put
the
recipes
there
anyway,
but
the
guides
which
I
sort
of
suggested,
belong
here
under
the
getting
started
instead
of
a
separate
thing,
there's
all
sorts
of
things
we
need
to.
C
A
So
well,
let's
see
I'm
I'm
a
little
bit
pressed
for
time
myself
for
other
meetings
for
like
other
meetings.
In
addition
to
what
I
have
bruce.
What's
your
time
available,
you're,
okay,
yeah,
I'm,
okay,
I'm
okay!
A
Okay,
the
only
thing
that
I
know
of
that
was
important
to
diane
is
to
maintain
at
the
bottom
or
to
include
at
the
bottom
of
whatever
we
did,
the
end
user
community
part
and
the
commons
part
is
to
have
that
featured.
I
don't
know
if
it's
necessary
to
be
on
the
same
front
to
be
on
this
the
front
page
the
same
as
it
is
now,
but
it
was
important
for
diane
to
have
that
to
list
those
partners
and
list
the
community
commons,
that's
something
that
people
can
participate
in.
B
Yeah
so
well
yeah.
It
seems
that
diane
like
this
seems
to
be
from
diane's
standpoint,
a
dual
purpose
site
with
one
of
the
significant
purposes
being
marketing,
in
other
words,
a
like
some
new
potential
user
sort
of
sitting
around.
B
You
know
fat,
dumb
and
happy.
I
can
say
that,
because
I'm
fat
stumbles
across
the
site
and
they
should
be
incentivized
to
want
to
install
okd.
You
know
after
buying
a
you,
know,
bunch
of
hardware
and
so
and
then
promoting
it
to
the
world
right,
and
I
can
see.
D
B
Interest
is
more
on
what's
useful
and
you
know
because
I
think
like
from
the
standpoint
of
a
technical
person,
they
will
very
quickly
get
annoyed
by
the
marketing
bump
and
if
there's
not
useful
stuff,
then
they're
not
going
to
go
back.
A
A
Save
that
for
diane
to
see
what
she's
partial
to
in
terms
of
format
and
stuff,
but
I
would
say
the
rest
of
it
brian.
If
what
are
you
most
comfortable
since
you're
sort
of
leading
this
effort,
do
you
want
to
do
it
in
these
meetings?
Do
you
want
to
wrangle
people
for
a
separate
meeting?
Oh
and
that's
you
and
you
can
run
with
it.
C
Yeah
I
mean
I,
I
think
the
big
thing
is
just
to
get
a
consensus
on
styling
color,
the
colors
to
use
and
do
we
want
it.
I
mean
there
is
an
option
where
we
could
have
a
dark
mode
and
light
mode
with
the
toggle
switch
it'll
pick
up
your
browser's
preferences
if
we
want
that,
so
these
are
all
things
that
we
can
turn
on
and
it's
a
configuration
thing.
C
So
it's
not
anything
to
do
with
writing
the
content,
because
you
write
content
in
markdown
and
whatever
we
decide
as
a
styling
will
get
applied
to
that.
So
it's
not
as
if
the
decisions
we
make.
But
I'm
aware
this.
This
is
our
community
presence
on
the
web,
so
I'm
a
fairly
new
member.
I
I'm
happy
to
go
and
and
sort
of
start
throwing
things
up
and
letting
people
shoot
me
down
and
saying:
that's
terrible
and
go
go.
Do
better
or
yeah.
I
like
that.
C
A
Yeah
there
you
go
well,
does
it
make
sense?
So
I
mean
I
don't
know
who
else
is
going
to
be
coming
to
these
meetings?
Right
now,
folks
are
like
really
busy
in
the
past.
We've
had
like,
basically
it's
it's
plus
mike
and
then
plus
muhammad
reza,
and
then
michael
and
that's
basically
been
it
and
then
driti.
A
Does
it
make
sense,
bruce
and
brian,
for
you
folks
to
go
off
and
and
work
and
then
just
bring
something
back
to
the
larger
group,
because
there's
going
to
be
stuff
coming
up
in
these
meetings
that
we're
going
to
have
to
address
in
terms
of
some
of
the
other
documentation,
installation,
documentation
and
things
like
that,
so
maybe
in
terms
of
the
design
stuff,
if
you
folks
go
off
and
and
figure
out
what
works
best
and
bring
it
back
to
the
group
and
chances
are,
unless
are
you
in
north
american
time
zone,
brian
I'm
uk
based.
E
C
C
So
we're
eight
hours
apart,
okay,
so
yeah
I
mean
what
I
can
do
is
I
can
do
things
and
and
put
a
comment
in
the
slack
channel
or
wherever
and
say
I've
made
a
change,
go
say
a
on
a
and
we
can
take
it
from
there
and
I
can
we
can
do
it
incrementally
and
ask
people
to
the
comment
I
mean
the
problems.
Is
people
tend
not
to
comment
and
then
when
it
goes,
live
there'll
be
an
outcry
of
who
did
this?
I
don't
like
this.
B
But
I
think
I
think
that
the
your
the
optional
dark
mode
light
mode
is
good
for.
B
C
A
A
E
C
Okay,
yeah,
I
can
do
that
so
so.
The
one
question
I
have,
and
maybe
michael
can
tell
me-
I'm
assuming
I've
got
to
remove
this,
because
if
we're
going
to
be
github
pages,
driven
we're
no
longer
going
to
be
powered
by
red
hat
on
openshift
online,
I'm
guessing
that
would
have
to
be
removed
there,
any
legal
things
that
we
need
to
put
in
like
license
or
copyright
or
any
of
this
sort
of
stuff
that
we
need
to
be
aware
of,
because.
C
A
C
A
A
C
A
Change
this
yeah
that
needs
to
go
to
okd
yeah,
because
this
talks
about
like
4.6
and
above
and
okay,
oh
interesting
as
of
july
2020.
The
purpose
and
maintenance
strategy
of
the
repo
varies
by
branch.
So
apparently
origin
is
used
as
sort
of
a
dumping.
Well,
I
don't
say
dumping
ground,
but
a
jumping
off
point
so
yeah.
We
definitely
want
to
instead
drop
people
into
the
okd
one.
A
Yep
all
right,
and
so
yeah
we'll
put
that
on
the
list
just
to
find
out
about
legal
stuff.
If
michael,
doesn't
know
like
what
do
we
need
to
have
in
terms
of
any
type
of
you
know
insignia
for
copyright
or
anything
like
that.
C
And-
and
I
I
guess
just
to
go,
looking
down
further
the
the
agenda
when
we
actually
do
the
switch,
we
can
probably
handle
the
inclusive
language
update.
At
the
same
time,
that's
probably
a
good
time
to
do
that.
A
A
Okay,
so
I
have
a
next
item
in
terms
of
of
this,
which
is
priority.
What
do
we?
What
do
we
think
is
priority
to
move
to
the
beta
so
that
we
can
move
the
beta
over
sooner
than
later,
like
because
there's
a
lot
of
sort
of
sort
of
crafty
type
stuff
and
what
would
what
would
be
helpful
to
move
to
move
into
the
beta
so
that
we
get
a
good
sense
of
of
navigation,
appearance.
C
Potentially
yes,
with
a
sort
of
because
I
mean
we
sort
of
have
got
already
gone
through
the
site
and
says:
well,
we
need
to
get
rid
of
this
stuff.
So
we
looked
at
the
recipes
and
said
well
that
that's
going
that's
old,
so
I
there
isn't
a
lot
on
the
site
to
be
honest,
yeah.
I
guess
that's
true.
I
mean
we'll
move
the
blogs
across
I'll
move
the
guides
across.
C
C
A
C
C
A
C
B
Yeah
now
I
think
that
we
could
conceivably
have
content
changes
and
that
I
don't
think
we've
really
looked
at
it
to
see.
B
Okay,
like
all
the
information
that
people
want
to
access
frequently,
is
it
easily
accessible
like
I,
I
will
occasionally
find
new
stuff
popping
up
when
I
do
a
google
search
that
I
didn't
even
know
existed,
which
is
really,
and
some
of
it
is
stuff
that
vadim
did
and
put
in
markdown
this.
You
know
somewhere
in
the
you
know,
like
you
know
the
the
github
slash,
install
slash,
you
know.
If
you
go
down
a
bit,
then
you
find
a
fantastically
useful
document.
A
B
Like
somewhere
so-
and
I
noticed
like
like
whenever
I'm
on
a
different
machine,
I
need
to
find
the
the
status
page
with
the
updates.
I
have
to
poke
around
right,
and
so
so
things
like
that
would
be,
I
think,
are
generally
useful
enough.
That
it'd
be
nice
like.
If
you
go
install,
then
there's
a
link
right
to
it
with
a
meaningful
name.
C
C
C
So
even
to
the
point
of
there's
a
release,
that's
got
an
issue,
a
known
issue:
let's
put
that
up
as
as
a
known
issue
or
release
4.8
point
x
and
and
and
we
can
actually
start
making
the
site
the
go-to
place,
to
find
stuff
and
find
the
latest
information,
rather
than
I
mean
looking
back
at
the
history.
Okay,
the
io
hasn't
really
changed
a
huge
amount
for
quite
some
time,
we're
not
using
it
as
the
as
a
place
where
we
post
up-to-date
information.
B
Right
and
it'll
be
really
useful
to
have
such
a
place.
I
think,
but
I
mean
I
think,
but
again
I
wouldn't
throw
in
too
many
factors
at
once.
B
A
Yeah-
and
one
thing
I
do
have
bruce
to
your
point
about
buried
documents
is,
and
I
can
actually
I'll
modify
the
the
agenda
to
reflect.
This
is
further
down.
We
had
an
ongoing
item.
That
was
the
name
and
scope
of
install.md
and
readme.md,
because
those
are
the
ones
where
you
want
to
get
to
the
install
that
md,
because
that
has
the
link
to
releases
and
there's
all
that
navigation
stuff.
I
want
to
have
that
conversation
with
the
dean
since
vadim
created
those
two
pages.
A
Where
are
those
pages?
So
if
you
go
to
okd
dot,
io
or
sorry,
if
you
go
to
the
okd
code
repository
so
github,
okay,
so
it's
it's,
not
the
documentation.
A
E
A
Yeah
and
and
actually
there's
some
stuff
that
needs
to
get
pulled
out
of
there,
like
those
guides,
need
to
get
deleted
because
those
are
the
old
ones
there.
A
There's
the
troubleshooting
stuff,
which
talks
about
log
bundles,
there's
the
contributing
page
which
talks
about
actually
building
okd,
like
I
feel
like
contributing,
needs
to
actually
get
changed
to
like
building
okd,
because
contributing
in
terms
of
the
group
can
mean
a
lot
of
different
things
right
and
you
know
known
issues.
He
actually
has
been
updating
known
issues
with
known
issues
for
builds
and
stuff,
like
that.
A
It
it
feels
that
way
because
there's
really
nothing
here,
that's
like
scripts
or
anything
like
that.
I
think
the
the
guides
might
have
a
couple
of
scripts
or
something
like
that.
But
no
there's,
no
it's
all
content,
and
so
my
sense
is
that
yeah
I
mean
it
should
go
like
yeah
even
navigating
through
here.
I'm
not
seeing
anything
that
isn't
just
some
flat
pages.
A
So
it's
if
you
go
to,
is
it
install
indy
or
what
is
it
let's
see
hold
on?
Let
me
find
it:
it's
you
go
to
the
main
page,
oh
no,
it's
releases!
So
if
you
want
to
click
on
releases,
so
if
you
go
to
the
getting
started
part
and
then
there's
releases
that
goes
to
the
long
release
page
which,
where
is
that
in.
C
A
C
A
Right,
let's
see
the
nightly's
page.
C
C
And
it's
it's
easy
to
follow
same
with
things
like
the
faq
yeah,
and
I
think
that
should
be
a
feature
of
okadi.io
and
then
obviously
the
the
log
information
and
then
the
contribution.
As
you
say,
it
is
a
good
source
of
information
that
should
be
there.
This
should
be
part
of
our
documentation.
A
A
Right
anything
else
on
this
topic.
A
Covered
a
lot:
oh
delineation,
of
resources
for
work
group
and
okd
users,
diane
was
going
to
look
into
the
working
group
guidelines
and
conflict
resolution
post,
something
she
can't
respond
to
that.
Diane
did
want
us
to
provide
text
for
what
to
put
in
the
google
description
and
to
for
what
to
ultimately
put
in
the
chat
channel
so
that
they
don't
like
cross-reference
each
other,
because
actually
the
chat,
I
think
says
to
go
to
the
google
group
for
support
or
something
it's
I
mean.
C
I
mixed
I
mean,
I
think,
eventually,
if
we
can
get
the
community
page
on
okd.io,
then
that
would
be
a
good
place
to
send
everybody
to,
because
that
will
then
in
a
more
verbose
way,
be
able
to
say.
Are
you
an
end
user
or
do
you
want
to
contribute,
and
these
are
the
differences,
and
this
is
where
you
go
to
do
that
function.
That's
where
you
go
to
that
function,
but
until
we
get
that
page
stable,
I
mean
the
current
community
page
well
right
now.
The
link
goes
to
the
discussion
directly
to
the
discussion.
A
All
right
that
covers
all
of
that,
so
brian
in
terms
of
inclusive
language
update,
did.
Is
there
anything
on
that
ticket
from
those
three
folks
that
were
assigned
to
it?
Yet
I
haven't
been
notified
of
any
changes.
A
Let's
see,
if
there's
nothing
nope,
those
folks
are
still
assigned
to
it
28
days
ago
response,
so
I
would
say
in
how
long
do
you
want
to
wait
brian
before
we
ping
them
again,
those
red.
C
A
C
Said
if
we're
going
to
move
across
to
the
new
site,
I
can
fix
everything
as
part
of
that
and
then,
as
we
transition
from
the
current
scheme,
to
the
github
actions
they're
going
to
have
to
turn
off
whatever
automation
they
have,
and
at
that
point
we
can
just
rename
the
master
to
main,
which
is
the
primary
action
on
on
that.
So
I
think
when
we
do
that
transition,
we
close
this
ticket
down.
C
A
All
right,
that's
easy
enough.
Okay,
and
now
we're
up
to
michael's
first
draft
of
the
dots
on
submitting
an
issue
on
the
docs
michael.
Do
you
wanna
walk
us
through
a
little
bit.
D
Yesterday
I
just
started
in
google
docs,
but
unfortunately
it's
a
red
hat
only
google
doc.
Unless
I
explicitly
invite
you
all
in
right,
I
can
find
it.
D
It's
a
decidedly
simple
little
document,
because
I
assume
people
know
what
to
do.
You
know
how
to
do
these
things.
I
just
wanted
to
start
by
mentioning
that
the
okay
docs
have
built
off
the
openshift
docks,
so
any
actions
they
want
to
take
go
against
that
repo
and
not
the
okd
repo
and
folks
need
to
file
a
pr
directly
against
the
documentation.
D
D
Third,
this
is
our
template.
We
create
issues,
and
we
discussed
this.
I
think
last
meeting
what
types
of
changes
we
wanted
to
see
listed:
expressly
errors,
typos,
missing
information,
product
names,
the
operating
system,
blah
blah
blah
and
if
you
do
find
a
jira
issue
here,
the
information
to
really
hone
what
the
problem
is,
what
your
concern
is
and
and
how
to
tag
it
so
that
it
gets
our
attention
directly.
A
D
C
A
All
right,
that's
pretty
much
it
very
cool,
any
other
feedback
for
michael.
A
All
right
next
item
up.
A
Create
a
bill
doc
outline
for
vadim
bryan,
and
I
have
not
had
any
communication
about
that.
We'll
do
that
in
this
coming
week,
I've
been
just
really
overwhelmed
with
other
stuff,
but
I'm
I'm
being
able
a
little
more
time
to
break
away
from
that
and
then
so
brian
and
I
are
going
to
create
sort
of
a
set
of
questions
and
things
that
will
form
the
outline
that
we
want
vadim
to
fill
in
the
blanks
on
or
or
to
point
us
to
filling
in
the
blank
signage.
Well,.
C
A
Yeah,
I
will
do
that
in
the
agenda.
In
fact,.
A
C
I
I
guess
is
just
make
sure
that
this
crc
stuff
is
recorded,
I'm
hoping
to
apply,
but
I'm
out,
I've
got
social
plans
on
friday
evening
and
I
may
have
to
leave
that
cfc
thing
early.
If
it
goes
on
for
the
full
two
hours
and
because
I'm
guessing
again,
we
want
to
write
that
up
and
get
that
into
okd
dot,
io
right.
So
the
outcome
of
that
and
again,
if
somebody
wants
to
do
that,
if
not
I'll
I'll
do
that
after
the
effect.
C
But
if
somebody
wanted
to
document
and
write
that
up
during
the
event
and
but
I
just
think,
we
need
to
make
sure
that
we
do
have
an
action
to
convert
that
video
session
into
useful
documentation
going
forward
and
then,
as
we
do,
the
automation
post
that
event
again.
That's
then
fully
documented
and
yeah.
A
Yeah-
and
I
think
it
would
be
nice
if
we
created
a
page-
that
is
a
listing
of
all
of
these
external
events
that
we've
had,
as
opposed
to
hoping
that
someone
sees
it
in
the
all
of
the
listing
of
blog
posts.
It'd
be
nice
to
have
something.
That's
you
know
like.
I,
don't
know
what
we
would
call
it,
but
something
has
links
to
the
videos
for
all
of
these
things.
We've
been
doing,
you
know
for
the
past
year
and
a
half
or
whatever.
C
A
So
we
do
have
an
okd
playlist
on
the
openshift.
Diane
gave
me
access,
so
I
actually
have
access.
That's
all
of
the
okay
meetings
are
under
that
okd
playlist.
So
we
can
put
our
recordings
under
that.
C
C
A
C
A
A
All
right
sounds
like
we're
good.
Let
me
know
if
you
can't
make
the
next
meeting
since
we're
running
a
little
bit
thin.
I
don't.
I
don't
want
to
get
less
than
like
three
people
at
a
meeting,
and
you
know
what
I
mean.
So,
if
folks
can't
make
it,
let
me
know
ahead
of
time
because
then
maybe
we
can
reschedule
or
skip
or
something
like
that.
A
Just
so
we
don't
have
everyone
or
two
or
three
people
sitting
here
waiting.
You
know
if
we
don't
have
a
forum.
Basically
we
should
be
like.
I
guess,
four
people.
This
is
probably
the
smallest.
We
would
want
it.
B
Yeah,
I'm
okay
for
the
next
stocks.
One
I've
got
a
big
academic
kickoff
meeting
next
week,
so
I'm
gonna
have
to
see.
I
don't
know
if
I
can
come
to
the
regular
working
group
meeting,
but
it
depends
on
if
I
can
bug
out
of
the
other
one.
A
C
Yeah
I
mean
I
mean
if
it's
an
hour,
I
can
stay,
but
I
am
going
to
have
to
sort
of
after
an
hour
drop
out.
So
all
right,
yeah,
I'm
quite
looking
forward
to
that
one.
C
I
think
the
interesting
thing
is:
how
do
we
actually
I've
not
really
seen
how
we
actually
do
work
outside
of
the
meetings?
What
is
the
mechanism
of
actually
collaborating
outside
the
meetings,
because
we
actually
want
to
create
an
automation
sort
of
project
as
a
result
of
this
one?
So
I'm
quite
interested
to
see
how
that
pans
out
how
much
interest,
and
also
how
we're
actually
going
to
organize
it.
Yeah.
A
Yeah,
I
think
it'll
probably
be
I
don't
know
we'll
see,
it'll
be
interesting,
so,
but
I'm
definitely
doing
interested
in
helping
with
the
automation.
I
know
a
couple
folks
are,
I
know
you
are
so
let's
yeah
we'll
probably
tackle
that,
probably
at
the
main
meeting,
the
next
main
meeting.
So
probably
next
week's
maybe
probably
talk
about
that
with
vadim
and
soon
all
right.
Well,
thank
you.
Everyone
for
showing
up,
I'm
gonna,
go
ahead
and
stop
recording
here.