►
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
Anything
that
people
want
to
add
to
the
agenda
that
cover
everything
bruce.
I
think
you
had
a
question.
C
C
C
I
think
we
probably
need
to
work
out
process
in
terms
of
just
how
we
want
to
go,
and
I
know
we've
talked
about
this
in
the
past,
but
just
who
should
be
doing
reviews
and
other
issues
that
we
need
to
or
any
process.
We
need
to
apply
to
reviews.
A
I
added
that
as
an
item
all
right:
let's
go
ahead
and
jump
in
so
there's
no
updates
on
the
charter
update
and
placement.
I
haven't
had
a
chance
to
do
that.
I
was
finishing
up
the
video
stuff
which
I
just
finished
last
night,
beta
site
brian
go
ahead
and
take
it
away.
C
Okay
and
yeah,
so
we're
finally
live.
That
happened
so
you'll
notice
that
the
site
now
looks
a
bit
different
and
we
are
fully
on
to
the
mk
docs.
There's
a
couple
of
things
that
gotta
tidy
up.
I've
done
the
changes,
but
I
haven't
actually
pushed
them
to
the
site.
Yet
I
think
there's
a
couple
of
links
that
got
broken
where
things
were
pointing
to
the
old
site.
They
now
need
to
point
to
the
new
site
and
but
yeah,
I
think
we're
pretty
much
there.
C
I've
noticed
as
I
joined
bruce,
you
made
the
comments.
So
yes,
that's
one
of
the
things
I've
got
to
change.
When
I
put
the
beta
site
up,
there
wasn't
the
versions
for
okd.
C
So,
if
you
want
to
get
to
it
immediately,
that's
where
you
get
to
it,
but
hopefully
by
tomorrow
I
should
have
pushed
the
updates
and
we're
going
to
have
that
landing
page
back.
D
Yo,
I
think
that
we
we
didn't
say
that
we
want
to
get
rid
of
all
the
versions,
just
the
three-point
versions,
because.
D
D
Version
of
okd
version
4,
which
said
no,
there
was
a
there,
was
a
point
in
time.
Perhaps
briefly,
when
all
those
versions
were
available
and
at
one
point
the
latest
disappeared
and
a
different
point.
The
latest
point
to
4.8.
D
B
Not
sure
if
it
may
help,
but
from
the
experience
we
got
with
overt,
we
are
maintaining
only
the
supported
version
documentation,
so
it
depends
on
which
version
of
okd
are
still
under
support
by
the
community,
and
I.
F
Just
just
a
moment,
so
I'm
I'm
just
so
I'm
clear
and
I
think
anyone
who's
watching
this
video
is
clearing.
I
just
shared
the
screen
with
the
docs.okd.io
and
those
are
all
the
ones
that
are
available
in
the
docs
there.
So
those
are
the
ones
that
I
suspect
we
should
be
point
being
able
to
list
on
the
mk
docs
version
of
okd.I.
Or
are
you
shortening
that
list
up.
F
F
C
I
mean
it
is
a
very
interesting
question
is
what
is
a
supported
version
of
okd,
because
I
know
ocp
have
just
changed
their
long
term
support
to
be
every
version
from
4.8,
but
at
the
minute
4.6
long
term
support
is
supported,
but
on
ocp
it's
only
four,
seven,
four,
eight
and
four
nine.
Now
that
are
currently
supported.
Everything
else
is
out
of
support,
so
we're
still
listening
in
the
docs
yeah.
A
C
Versions,
as
I
said,
that's
a
point
in
time
thing
that'll
be
done
by
tomorrow.
We
will,
if
you
point,
if
you
go
to
the
left
thing
on
the
breadcrumb-
that's
the
page
I'll
land
at
which
is
the
page
that
diane
showed,
which
just
has
the
drop
down
on.
So
that's
going
to
become
the
new
landing
page
for
docs.
F
I'm
just
going
to
just
clarify
this,
because
every
time
we
say
support
someone
at
red
hat
probably
loses
their
wings
or
something
an
angel
loses
their
wings
or
an
essay
dies.
I
don't
know
what
but
probably
cries
it
there.
There
is
no
support
for
okd.
F
What
I
think
is
is
what
is
our
commitment
to
keeping
these
documents
available
for
people
to
go
back
in
time
and
and
have
access
to
them
so,
and
I
I
thought
what
I
heard
at
a
previous
docs
meeting
was
that
we
were
going
to
stick
in
tandem
with
the
ocp
docs
team,
so
whatever
they
had
in
docs.openshift.io,
we
would
stay
in
tandem
with
that,
because
we're
relying
on
the
docs
team
to
generate
those,
and
so
as
as
ocp
and
openshift
drops
documentation,
we
would
drop
them
off.
A
I
I
thought
we
had
decided,
but
I
think
maybe
there's
a
little
bit
of.
We
had
a
a
situation
where
maybe
there
was
a
miscommunication
or
something
here's.
Here's
the
issue
in
a
nutshell,
is
that
we,
within
those
pages
are
links
to
resources
and
descriptions
of
things
that
even
in
terms
of
kubernetes
may
not
be
accurate
anymore.
Right
in
terms
of
processes
may
not
be
considered
best
processes,
best
practices
right
and
do
we
want
to
keep
that
around
and
create
extra
work
for
the
red
hat
employees?
A
F
I
I
think
that
might
be
a
question
for
michael
burke,
who
is
the
the
point
person
for
the
docs.
My
my
understanding
is.
Is
that
like
say,
we
have
a
3.6
set
of
docs
sitting
out
there.
I
think
that
was
the
last
one
on
the
list.
I'm
not
positive
and
something
goes
out
of
date.
An
ansible
playbook
is
no
longer
available.
You
know
it's
removed
from
wherever
it
is
in
github
that
it
was
linked
to
that.
F
That's,
not
anything
that
we're
going
to
redirect
to
a
newer,
ansible
playbook
or
that
michael
is
going
to
that
link
will
just
be
broken,
and
so
I
and
that's
kind
of
how
it
works
with
other
things,
as
things
go
out
of
date
and
ghost
links
go.
Stale
too.
I
haven't
checked
that
if
that
happens
with
ocp,
but
I
would
defer
to
michael
burke
personally
if
they
do
that
kind
of
upkeep
on
the
older
documentation
sets
for
openshift,
I
don't
think
they
do.
F
A
F
F
A
Let's,
let's
table
this
and
have
folks
think
about
it
until
michael
shows
up
at
our
next
meeting,
there's
six
of
us
on
the
call
and
then
there's
michael
and
then
we
can
also
ask
the
larger
group
what
they
think,
because
in
a
way
in
my
mind,
I
think
it
does
also
impact
people's
perception
of
when
they
come
into
the
channels
asking
questions
and
things
associated
with
the
release
and
thing
things
that
release
are
associated
with
earth
that
are
associated
with
an
okd
community
in
terms
of
chat.
A
In
terms
of
you
know
us
providing
these
guides,
and
things
like
that,
like
we
generally,
are
only
going
to
provide
guides
and
focus
our
efforts
on
promoting
things
in
the
community
that
are
supported
that
are
versions
that
are
in
sync
with
ocp.
That's
my
sense,
but
who
knows
you
know
and
vadim
might
have
some
input
on
this
as
well
all
right.
So
let's
table
this
just
because
it's
it's
probably
a
larger
discussion,
brian.
What
was
are
there
any
other
lingering
issues.
C
I've
got
to
finish
off
the
section
on
grating
or
updating
content,
I'm
working
on
putting
a
section
for
using
sort
of
container
images
rather
than
having
to
install
stuff
locally,
and
I've
also
started
playing
around
with
the
community
and
co-ready
workspaces,
the
che
and
vha
and
creating
a
dev
file.
So
you
can
actually
edit
it
within
that
environment,
and
so
again
you
don't
have
to
install
anything
locally,
not
even
docker.
C
Now
that
we've
got
that
drop
down
back
with
multiple
versions
in
that's
it
there's
no
technical
issues
or
there's
no
challenges
that
we've
got
to
really
overcome
and
and
we're
sort
of
into
business
as
usual.
Now
so
people
want
to
tweak
the
look
and
feel
or
they've
got
suggestions
for
better
layout
or
better
wording.
A
And
then
your
next
item
is
about
basically
for
review
of
suggested
things
who,
when
and
what
and
where
and
and
whatnot.
C
Yeah,
it's
really
because,
obviously
I'm
a
committer
on
this
and
not
everybody
is
so
it's
it's
really.
When
somebody
makes
a
pull
request,
is
there
a
process
that
we
as
a
group,
want
to
do
to
evaluate
and
and
agree
and
approve
changes,
or
I
mean
I'm
sort
of
doing
it
myself
at
the
minute
and
just
reviewing
it
and
making
a
call,
but
I'm
just
thinking
as
we
are
the
documentation
group,
should
we
be
more
proactive
within
this
forum
to
actually
review
and
push
changes
forward.
F
We
say
something
like
that
in
this
docs
meeting.
We
will
review
it
each
time
we
meet
the
pull
requests
that
come
through
regarding
the
site
and
and
keep
it
as
simple.
F
As
that
I
mean
in
the
past,
I
just
willy-nilly
did
them,
as
as
I
saw
fit
or
as
people
gave
me
stuff
and
was
just
grateful,
but
I
think
if
we
use
the
same
process
jamie
that
you
use
in
the
main
meeting
of
looking
at
the
pull
request
issues
and
that
that
are
related
to
the
docs
in
this
meeting,
and
then
you
know,
do
the
you
know
merge
the
pull
request
if
it
passes
the
muster
here.
F
A
Is
that
is
that
what
the
rest
of
the
group
is
thinking.
E
A
And
all
right
next
thing
up
is
the
name
and
scope
of
the
install
and
read
me
now
that
the
site
change
has
happened,
that's
something
that
work
can
begin.
I'll
begin
on
that
and
I'll
run
it
by
the
group
as
time
goes
on
inclusive
language
update,
basically
done
and
brian
said.
You're
gonna
have
a
little
blurb
on
the
on
the
news
site
about
that.
A
Work
will
commence
now
on
the
the
build
dock
outline
that
we
can
submit
to
to
have
vadim
sort
of
fill
in
the
blanks,
or
at
least
look
over
ideas
to
have
something
for
building,
okd
and
and
people,
knowing
sort
of
where
all
of
the
pieces
lay
the
team's
obviously
kind
of
busy
right
now.
But
I
think,
if
brian
and
I
work
on
something
now
that
the
site
stuff
is
out
of
the
way,
maybe
we'll
have
more
time
code
of
conduct.
C
Oh
yes,
guys
on
that
one
jamie.
I
think
it's
worth
also
just
going
back
to
the
discussion
we
had
at
the
last
full
meeting
code
ready
containers
this
this
snow,
the
single
node
install
and
it
sounds
like
there
is
something
to
do
there.
People
are
quite
interested
in
the
single
node
install
versus
crc,
so
I
think
we
need
to
include
that
within
this
topic
as
well.
F
A
No,
we
do
we
did
not
yet
I'm.
My
sense
is
that
now
that
the
website
stuff
is
done,
the
floodgate's
going
to
open
on
all
of
the
other
things.
So
there
was
a
lot
of
emphasis
on
that
and
some
of
the
other
projects
going
on
for
me,
the
the
video
stuff.
We
will
set
up
a
time
for
that
and
once
that
group
is
solidified
and
has
met,
I
think
it's
it's
a
great
way
to
create
documentation
as
you
go
so
as
they
discuss
things
say:
okay,
this
needs
to
be
in
the
documentation.
A
This
needs
to
be
in
the
documentation,
etc
and
in
terms
of
the
code
ready
containers.
A
Charo
has
his
document
on.
His
blog
is
a
great
starting
point,
and
then
building
on
that,
I
think,
is
something
that
we
can
yeah.
F
I
just
wanted
to
see
if
we
could,
let's,
let's
try
after
this
meeting
to
touch
base
with
it,
was
daniel
and
neal
neil
gampa
and
daniel
axelrod.
I
did
reach
out
to
steve
speicher
and
a
couple
of
other
folks
on
his
team,
the
pm
for
code
ready
containers
in
there.
He
gave
me
the
name
of
two
folks
who
include
in
that
sig
too,
so,
hopefully,
that'll
move
it
forward.
A
Let's
see
code
of
conduct
that
would
be
michael
for
the
search
and
replace
he's
not
on
the
call.
So
we
will
come
back
around
to
that.
So
there
was
so
we've
sort
of
been
lobbing
back
and
forth.
This
idea
of
setting
up
our
own
twitter
or
not
if
we
set
up
our
own
twitter,
someone
has
to
man
it
right.
Someone
has
to
do
that
work.
A
E
F
F
So
I
think
maybe
what
we
could
do
to
start
is
look
and
see
what
twitter
handles
are
available
to
us.
That
are
okay,
that
we
could
use.
If
you
could
spend
a
little
a
few
cycles
on
that
and
see
if
we
can
reserve
one
of
them.
That
will
be
a
good
start,
but,
though,
and
again
where
I
think
we
last
left,
it
was
as
we
have
and
as
we
need
to.
I
can
retweet
anything
out
with
like
an
okd
hashtag
out
of
openshift
commons.
F
B
B
F
So
it
takes
a
little
bit
of
vetting,
so
maybe
d3.
If
you
want
to
do
that
and
just
set
up
a
google
chat
inside
and
you
can
include
jamie
as
well
in
that
and
then,
if,
if
there
is
something
that
you
need
me
to
retweet,
okay,
open
shift
or
openshift
commons
that
should
be.
F
You
can
just
feed
it
to
me
there,
okay,
okay,
okay,
or
do
it
to
me
in
slack
whatever,
wherever
you
want
to
do
it
but
find
me,
and
I
will
I'll
wake
up
whatever
time
it
is
theoretically
and
and
but
I
think
that
that
the
per
that
the
person
who
reserves
the
okd,
whatever
the
twitter
handle
is,
should
be
or
should
be,
with
a
red
hat
email
address.
So
I
think
that's
the
one
thing
that
legal
would
like
us
to
do
so
that
it's
owned
by.
E
B
Yeah
excellent,
I
would
recommend
to
get
open
source
program
office
involvement
because
we
have
a
bit
word
an
account
that
we
can
use
to
store
password
for
those
kinds
of
accounts.
F
F
A
Yes,
okay,
so
let's
okay,
I've
added
that
to
the
task
list
and
then
actually
you're
with
the
next
thing
survey.
Where
are
we
at.
E
I
just
came
back
from
p2
haven't
started
on
it,
but
I
do
have
a
couple
of
questions
in
that.
So
I
created
a
list
of
questions
in
the
user
survey
discussion
that
we
pasted
over
here
so
that
everyone
has
it.
E
So
I
can
see
so
this
is
the
discussion
and
I
can
see
there
are
there's
some
comments
by
sandro
and
adam.
So
do
I
finalize
do
I
include
their
questions
in
the
final
question
list
or.
A
F
Yeah
and
we
can
use
openshift
commons
would
be
good
once
you
have
the
twitter
once
you
have
it
done,
we
can
tweet
it
out.
I
would
also
post
it
on
a
couple
of
places
under
linkedin
and
on
the
mailing
lists
and
in
the
coupe
you
know
the
kubernetes
things,
but
I
think
we
can
get
a
good
round
of
feedback
on
this
very,
very
well
done.
E
But
there's
one
more
question
jamie.
Do
you
want
me
to
look
at
some
of
the
existing
questions
that
red
hat
ocp
related
openshift
previous
survey,
questions
or
yes,.
E
D
It
for
a
long
time
now
I
I
guess
in
that
I
I
it's
been
a
while,
since
I
saw
the
list
of
questions,
but
are
we
asking
what
version
you're
running
in
all
of
that.
E
No,
no,
no,
I'm
not
asking
that.
Do
you
think
that
we
should
ask
that.
D
D
Right
and
I
guess
that
should
be
a
multiple
selection
list,
because
people
could
be
running
more
than
one.
A
Okay,
I
would
say
folks
should
should
put
it
in
the
if
you
can
put
it
in
the
in
the
ticket,
then
that
way
she
doesn't
have
to
put
in
all
these
notes
right
now,
and
people
can
clearly
say
what
they
think
should
be
in
there
and
whatnot.
So
please
update
the
ticket
with
these
thoughts
that
you've
been
throwing
down,
and
then
that
creates
a
record
moving
forward
of
how
we
came
up
with
with
this.
A
All
right
and
let's
see
next
up,
is
just
reviewing
the
task
list.
Let's
see,
oh,
do
we
have
any
new
business,
any
last-minute
walk-up
items
that
folks
have
or.
C
B
I
think
it's
I.
D
Think
it's
scheduled
on
utc.
It
is
so
it
stays
the
same
in
utc
like
north
america
is
about
to
go
off
daylight
savings
or
whatever
we're
on.
So
it's
going
to
move
to
the
night.
The
clock.
C
F
I
believe
we're
sticking
with
whatever
utc
is
in
the
fedora
calendar,
and
so
I
just
adjust
based
on
whatever
the
fedora
calendar
says
to
me.
I
don't
know
if
ever
and
we
have
this
conversation
every
year,
but
I'm
pretty
sure
we
just
stick
with.
We
can
write.
A
C
D
C
D
C
F
F
A
Yep,
so
let
me
let
me
share
my
screen
really
quick
here.
A
Okay,
so
the
task
list
we
have
manipulate,
manipulate
the
charter,
which
is
me,
write
up
code
on
site,
automation,
brian,
that's
still,
a
work
in
progress
code
of
conduct,
edits
michael
gather,
legal
input
on
external
repo,
social
media
diane.
Just
so
that
we
know
where
we're
standing
with
that
stuff
connect
with
openshift
twitter
leads
to
push
out
okd
contact
diane,
get
beta
site
running
on
lab,
check,
dns,
routing
options.
Right
bruce.
You
were
going
to
do
some
experimentation.
D
Was
actually,
I
was
pleasantly
surprised
that
it
should
be
possible,
at
least
do
the
make
docs
on
git
lab
using
the
get
lab
runner,
and
so
I
haven't
actually
tried
it.
Yet
I
did
look
at
a
number
of
other
people
have
done
similar
things,
and
so
I
I
guess
my
when
I
when
I
do
get
that
up
and
attempted
to
running,
then
it'll
be
a
question
of
whether
or
not
the
add-ons
all
pull
in
right.
A
B
I
think
that
has
been
discussed
something
like
four
weeks
ago
or
something
like
that
about
moving
the
okd
website
on
github
under
an
okay
d
organization.
Is
it
something
that
we
dropped.
A
So
we're
going
to
this
is
this
is
the
first
stage
of
that
yeah.
Okay,
all
right,
I
think
we're
good
to
go
and
diane
any
events
that
we
should
be
knowledgeable
about.
Coming
up.
F
There's
always
events
like
trust
me.
There
is
on
december
2nd
if
you're
in
japan,
we're
doing
all
japanese
openshift
commons
gathering
so
stay
tuned
for
that
the
next
big
event
for
us
is
devconf
cz
in
and
just
outside
of
prague
and
bruno.
Anyone
who
has
permission
to
travel
is
in
and
wants
to.
That
would
be
a
huge
thing.
It
always
snows,
though
just
remember
it's
not
springtime
and
check
in
the
czech
republic
and
then
there's
going
to
be
a
number
of
other
things
coming
up
in
the
spring.
F
A
All
right,
so
nothing
too
much
for
folks
that
didn't
notice
there
is
a
just
before
kubecon
americas.
A
There
was
a
release
of
gidop's
principles
from
a
new
get
ops
working
group
with
the
cncf,
which
is
some
pretty
cool
stuff,
and
christian
hernandez
from
red
hat,
is
on
that
group
and
stuff
like
that
and
I'm
sort
of
tangentially
following
what
they're
doing
I
might
get
involved
with
them
as
well,
but
that's
kind
of
a
cool
thing,
because
they're
they're
talking
about
a
lot
of
automation,
stuff
with
clusters
and
get
ups
practices
and
stuff
like
that
which
is
kind
of
cool
all
right.
A
Let's
call
it
a
day
and
if
anything
comes
up
be
sure
to
communicate
with
each
other
over
the
email
list
or
in
the
in
the
chat
channels.
F
Okay,
so
d3,
I
just
pinned
you
in
g
chat,
so
you
should
see
something
an
invite
from
me
and
we'll
add
jamie
into
that
once
you
you're
there
so
anyways
thanks,
everybody
take
care,
have
a
great
day.