►
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
With
the
documents
meeting,
I
put
a
link
to
the
agenda
in
the
chat
and
go
ahead
and
put
your
name
in
the
attendance
there,
and
this
is
our
meeting
for
september
7th
2021
and
take
a
look
at
the
agenda.
Real,
quick
and
since
diane
is
here,
there's
a
couple
of
items
that
were
sort
of
hinged
on
diane
from
the
last
time
that
are
there
yeah.
So
take
a
look
at
real,
quick.
If
there's
anything
you
want
to
add
to
the
agenda
or
remove
from
the
agenda.
C
I
was
going
to
add
in
a
note
I
have-
and
I
think
I
told
brian
a
number
I
bruce
about
it.
I
said:
is
it
bruce
it's
brian
in
this
sorry,
there's
too
many
bees
here
today.
Sorry
about
that
guys,
I
have
a
a
resource
that
we
can
apply
to
cleaning
up
the
github
pages,
making
them
look
a
little
more
beautiful
from
that
I
use
for
the
common
site,
so
we'll
add
that
into
the
mix
today
too,
and
then
I
was
going
to
invite
him
to
come
to
these
meetings.
A
Excellent
all
right!
Well,
let's
jump
into
what
we
have
here
the
and
this
actually
I
had
skipped
from
last
time
we
can
take
skip
out.
We
can
be
here
since
diane.
I
was
here
so
charter
update
and
questions.
A
I
I
was
not
around
for
the
charter
creation
process
today,
and
these
are
more
questions
for
you.
When
we
look
at
the
charter
there's
some
hold
on.
Let
me
see
if
I
can
pull
it.
C
A
A
In
okay
great,
so
if
we
look
at
the
charter,
this
was
done
last
done
in
2019
and
there's
references
here
to
stuff
and
there's
also.
So.
My
first
question,
I
guess,
is
in
regards
to
the
cncf
stuff.
It
seems
like
this
could
be
rewritten
in
a
better
way.
A
So
do
we
want
to
actually
take
a
stab
in
the
coming
weeks
at
sort
of
rewriting
this
a
little
bit
because
it
looks
like
there
were
some
ideas
that
were
tacked
on
like
this
sentence
here
seems
like
it
was
sort
of
tacked
on
at
the
end
as
an
afterthought.
C
Well,
just
originally
it
went
through
so
so,
let's
go
back
to
the
origins
of
okd
just
for
a
second,
so
you
know
there's
a
couple
couple
of
things
is
one
is
we
did
not
push
openshift
into
this
as
a
cncf
project,
because
in
the
early
days,
because
origin
was
something
separate
and
then
it
morphed
into
a
kubernetes
thing,
which
was
a
cncf
project,
which
is
why
the
reference
here
is
to
that
so
some
cncf
reference
should
be
in
here,
because
we
are
related
to
a
cncf
project,
aka
kubernetes
and
a
bazillion
other
things
that
the
cncf
has
under
its
umbrella.
C
Now
I
think
what
provide
guidance
and
coordination
for
cncf
pride.
C
C
Just
the
word
sub
dash
projects
within
the
working
groups,
scope,
because
I
think
we
started
out
as
a
sig
and
it
never
got
updated.
So
I'm
perfectly
okay
with
if
you
want
to
make
today,
like
just
work
to
change
that
first
first
paragraph
and
make
a
create
an
issue
for
it
and
bring
it
to
next
week's
meeting
to
make
that
correction
and
take
out
the
cncf
reference
in
that
first
one.
I
think
that's
totally
fair
game.
C
I
think
the
one
the
second
line
is
is
there
be
just
because
there
are
so
many
engineers
working
in
cncf
projects
and
fedora
projects
and
red
hat
projects
to
clarify
that.
So
I
would
leave
that
in
there
that
that
to
me
actually
resonates
or
what
we're
trying
to
clarify
here.
So
people
don't
come
here
and
mistakenly,
think
okd
is
sig
or
sub
distribution
or
something's
related
to
the
cncf.
C
So
for
me
it
clarifies
something
that
you
know
for
wandering
fools
who
come
in
and
land
on
this
page
and
might
think
we
are
part
of
this
cncf
because
we
have
things
like
k3
and
you
know
other
sub
projects.
So
that's
kind
of
important.
I
think
one
thing.
A
One
thing
I
think
we
might
want
to
do
is
to
and
I'll
give
it
a
stab
sometime
in
the
next
couple
days:
rework
that
paragraph
so
that
it
reads
something
along
the
lines.
Although
the
okd
working
group
is
independent
of
both
fedor
and
the
cloud
native
computing
foundation,
dot,
dot,
dot
and
then
sort
of
it
then
incl
phase
into
that
second
paragraph
stuff,
so
in
other
words,
sort
of
flip
it
so
that
it's
sort
of,
although
we
are
independent,
we
provide
this
and
blah
blah
blah
blah.
Does
that
make
sense.
C
Yeah
it
make
the
proposal
make
log
an
issue,
just
just
do
it
and
we
can
hash
it
out.
I
you
know,
I
think,
if
we
change
it
to
change,
we
definitely
need
to
change
the
word
sig
to
working
group
and
we
definitely
need
to
take
cncf
projects
and
change
it
to
sub
to
projects.
A
B
Yeah
we're
sort
of
trying
to
work
towards
getting
to
upstream
someday,
maybe,
but
I
noticed
that
4.8
is
actually
out.
A
Yeah,
we
were,
I
remember,
vadim
and
christian,
mentioning
that
it
was
going
to
be
soon
and
that
it
would
be
4.8
would
be
the
turning
point,
but
I
think
actually
that
didn't
happen.
C
A
C
Unless
they
contradict
me,
I
don't
think
that's
that's
happening.
We
originally
were
the
upstream
for
ocp
back
in
the
day
and
then,
when
we
switched
over
to
kubernetes,
kubernetes
became
the
upstream
and
we
became
a
sibling
and
I
think
sibling
stream
is
the
best
way
to
describe
it.
You
know
other
yeah,
a
sibling
stream.
A
B
D
C
Yeah,
that's
what
I
was
going
to
bring
up
right
now.
Openshift
is
no
longer
yeah,
no
longer
one
thing
right
and
even
as
a
product,
even
ocp,
then
there's
okay
and
there's
a
bazillion
different
met.
You
know,
managed
service
things
and
yeah.
So,
oh,
what's
open
source
about
origin
which
is
what's
in
the
origin.
Repo
is
what
we
are
the
the
siblings
dream
of.
So
I
you
know.
C
C
C
Taken
me
eight
years
to
get
it
out
that
way,
but
it
is
really
it
is
it.
I
think
the
more
interesting
thing
about
this
distribution
is
its
relationship
to
fedora
core
os
and
that's
what
makes
a
true
open
source
distribution
of
you
know,
because
otherwise
you're
constrained
to
rel
and
if
someday
they
came
up,
come
out
with
a
rel,
that's
licensed
in
a
way
that
could
be
open
source,
then
that
then,
what
bruce?
What
you
were
describing?
C
A
Okay,
so
that's
that
was
a
can
of
worms
question,
but
I
think
it
provided
at
least
a
little
bit
of
clarity
on
what
we
should
put
into
this
right
now.
B
C
Absolutely
yeah,
those
and
and
what
we
use
internally
to
describe
this,
and
there
are
other
projects
that
are
similar
to
this,
that
that
are
that
that
have
a
sibling
stream
approach
as
well,
and
I
think
you're
going
to
see
acm
and
ocm
advanced
cluster
management
and
open
cluster
management
have
some
semblance
of
a
similar
thing
going
on.
But
we'll
we'll
see
how
that
all
plays
out
too.
A
The
little
statement
that
says
things
that
are
out
of
scope
would
be
initiation
of
new
open
source
projects.
Do
you
have
any
sense
of
what
what
the
history
of
that
item
is.
C
There
you
go
yeah,
so
I
think
we
would
not
be,
for
example,
kicking
off
as
an
okd
working
group,
our
own
version
of
say,
a
monitoring
project
like
prometheus,
or
that
that
what
we're
trying
to
do
in
this
working
group
is
work
on
okd
and
the
okd
bits
and
parts.
C
That's
you
know
that
was,
and
I
think
that
comes
also
from
some
guidance.
We
got
from
the
cncf
reviewing
what
the
cncf
was
doing
and
what
some
of
the
other
projects
were.
Doing
too
is
that
we
really
wanted
this
group
to
focus
on
that
on
just
okd.
C
Well,
operators
is
a
nice
new
can
of
worms
and
it
has
its
own
community
and
I
think
what
we
talked
about
at
the
last
working
group
meeting
and
I
tried
to
get
austin
mcdonald
who's
coming,
should
be
back
for
our
next
working
group
meeting
to
come
and
talk
about
how
to
get
it,
how
to
build
a
better
relationship
with
the
operator
framework
community,
which
is
a
cncf
project,
which
is
where,
if
we
were
going
to
do
something
operator-ish,
we
should
work
with
them
or
be
a
sub-project
of
that
community,
and
so
that
actually
would
be
out
of
scope.
C
I
mean
we
might
be
able
to
kick
off
a
discussion
group
or
a
working
group
around
it,
but
if
we
were
going
to
kick
off,
you
know
okd
operator
framework,
or
you
know
that
sort
of
thing
like
that
changed
the
technology
that
is
in
the
operator
framework
or
expanded
upon
it.
Then
we
would
go
we
we.
This
is
my
opinion
and
I
have
lots
of
them.
We
all
have
them
that
that
we
should
go
and
work
in
the
operator
framework
to
do
that.
C
Work,
like
you
know,
sometimes
you'll
see
rancher
and
the
k3s
folks
go
and
work
in
the
kubernetes
place
to
get
an
extension
to
make
something
work
with
rancher
those
those
kinds
of
things
that
that
would
be
my
clarification
for
and
so
for
me,
and
that
this
is
for
me,
because
I
think
I
was
around
definitely
when
this
was
being
written
and
copied
and
pasted
from
other
places
that
line
still
rings
true
and
and
because
we
are
so
closely
tied
at
the
hip
to
ocp
as
a
sibling
stream.
C
It's
this
difficult
dynamic,
where
we
even
inside
of
red
hat,
push
our
people
to
contribute
further
upstream
if
they
need
something
to
get
into
openshift
like
go
put
it
in,
put
make
it
available
to
everybody,
every
kubernetes
or
every
operator
framework
person,
rather
than
put
it
just
an
open
shift,
and
because
just
an
open
shift
means
so
much
more
than
just
putting
in
creating
an
open
source
project.
B
Hey
yeah,
but
but
I
think
there
it's
again
complicated.
I
think,
because
there's
a
whole
pile
of
operators
that
we
have
on
a
on
an
issue
in
okd
that
we've
been
talking
about
for
a
long
time
and.
B
It's
many
of
these
operators
on
the
ocp
side
seem
to
be
part
of
openshift
like
serverless,
for
instance,
is
one
that
you
know
keeps
coming
up
and
came
up
through
my
email
this
morning,
and
it
looks
like
it's
sort
of
at
this
point
practically
trivial
to
get
it
on
to
quay.
B
E
Yep
so,
but
I
think,
there's
another
issue
here,
so
there's
the
individual
operators
and
where
possible,
they
should
be
in
the
community
pub
rather
than
any
special
one.
But
there
are
certain
number
of
operators
which,
as
bruce
said,
are
quite
tied
to
the
ocp
product
pipelines
githubs
the
things
that
are
in
the
registry.red
hats,
sort
of
repo
and
then
to
make
them
appear.
E
We
need
another,
build
olm
catalog,
which
would
be
an
okd
project
that
we
possibly
wouldn't
want
to
give
to
the
operator
framework
team.
It's
going
to
be
the
okd
that
replaces
the
red
hat
catalog
in
ocp.
C
So
I
think
that
if
there's
a
distinction
here
that
that
I
that
I
have
in
my
head
between
an
artifact
like
a
container
or
a
catalog
specific
to
our
community
or
our
ecosystem
versus
a
full-on
project.
C
Okay,
so
that's
that's!
That's!
I
think
what,
when
initiation
of
a
new
open
source
thing?
So
if
we
have
to
create
an
artifact
such
as
a
catalog
or
a
container
or
an
image
or
and
we
have
to
work
with
other
people
and
coerce
them
into
building
it
for
us
and
maintaining
it?
That's
a
different
ball
of
wax
than
initiating
a
new
open
source
project.
E
C
And
there's
a
reason
they
call
it
artifact
hub
and
the
cncf,
because
they're
getting
and
at
first
I
was
completely
resistant
to
that.
I
wanted
it
to
be
operator
hub.
You
know
because
everything
should
be,
but
then
once
they
kind
of
explained
it
to
me
a
little
bit
like
the
thick
skull.
I
have
the
idea
of
artifacts
versus
simply
operators,
operators
are
artifacts
and
there's
helm,
charts
are
artifacts
and
those
things
are
artifacts,
but
this
line
that
he's
got
highlighted
here.
C
Initiation
of
a
new
open
source
project
is
different
to
me,
so
yeah,
so
that
that's
just
around
that
one
line,
but
I
I
and
what
it
means
to
me
is
that
there
is
this,
a
log
jam
around
collaboration
and
build
processes
of
those
artifacts,
which
is
what
I'm
trying
to
get.
E
So
I
I
guess
what
I'm
taking
from
this
is
the
content
of
this
current
document.
If
we
don't
understand
it
and
we've
been
part
of
the
community
for
a
while,
but
it
suggests
it
does
need
wordsmithing
to
add
clarity
around
the
finer
points
that
we've
just
discussed
here.
So
we
do
need
to
sort
of
make
sure
that
it's
from
somebody
new,
it
actually
reads
and
they
can
understand
the
final
nuances
of
what
the
document
means.
A
A
There's
an
increasing
interest
in
making
okd
more
stable
and
better
documented,
and,
as
that
happens,
the
charter
and
the
processes
are
going
to
become
more
and
more
official
and
real,
as
opposed
to
things,
were
kind
of
wavy
in
the
beginning
and
whatnot.
So
I
think
it
would
be
good
to
revisit
this.
It
sounds
like
folks
have
interest,
so
we
can
work
at
updating
this
and
then
seeing
if
that
aligns
with
process
and
see
if
process
needs
to
change
with
the
larger
group.
So
an
example
of
that
is
this.
A
This
says
here
about
membership,
that
membership
is
actually
determined
by
putting
in
a
a
issue
and
saying
that
you're
a
member
and
then
that
gets
recorded
in
the
members
dot
md
file-
we've
not
done
that
for
as
long
as
I've
been
part
of
the
group,
no
one's
actually
done
that.
Now
it
hasn't
been
modified
for
two
years
right
exactly
so.
I
think
the
question
we'll
have
to
come
to
the
group
with
some
larger
questions
on
this.
A
Even
before
we
modify
the
document
is,
do
we
want
to
still
follow
this
process
and
if
so,
then
we
need
to
vote
or
we
need
to
start
doing
that
process
or
the
larger
group
needs
to
vote
to
say
no.
Actually,
we
want
to
change
the
charter,
because
this
process
is
too
onerous
or
there's
a
better
way
or
something
like
that.
C
And
that
that
I
think
that's
it,
the
first
stuff
editing
out
the
cncf
and
the
sig
words
that
I
think
we
can
do
in
a
quick
issue
and
get
that
through
whether
or
not
we
want
to
go
to
this
membership.members.md
format
and
start
using
this,
because
we
don't
really
currently
vote
on
anything.
C
We
haven't
and
I
think
you're
right
we've
hit
a
maturity
level
and
an
adoption
level
of
okd
out
there
in
the
world
where
we
may
want
to
do
this,
we
may
you
know
we
may
decide,
you
know,
there's
something
we
need
to
do
that.
That
requires
a
vote
beyond
you
know,
consensus
in
the
the
meeting
we
had
we
we
are
close
to
that.
I
think
I
think
we're
we're
close
to
that.
So
it's
not
a
bad
time
to
revisit
it
and
if
so,
then
get
everybody
to
do
this.
A
All
right
well,
then
I'll
add
it
to
the
agenda
of
the
main
meeting
for
next
week,
just
a
little
bit
of
time
to
introduce
this
issue
and
see
what
the
main
group
thinks
and
anyone
else.
That's
that's
on
this
call
I'll
take
a
stab
at
some
of
the
stuff
up
towards
the
top
here.
If
anyone
else
wants
to
as
well.
C
C
Would
ask
you
to
keep
it
as
simple
as
change
as
possible.
You
know
because
this
did
go
through
a
legal
review
and
I'm
hesitant
to
ask
red
hat
legal
to
do
much
more
than
look
at
it
again
quickly,
because
that
takes
time.
A
That's
an
interesting
point
because
we've
got
the
community,
which
is
the
the
working
group
stuff
and
actually
the
meeting
notes.
Maybe
it
makes
sense
for
the
meeting
because
we
talked
about.
Oh,
the
meeting
notes
are
in
the
hackmd,
but
they
could
be
in
the
okd.io
or
they
could
be
in
the
community,
one
it
is
kind
of
distributed,
and
so.
C
C
The
hesitation
I
have
about
moving
this
out
from
the
openshift
repo
itself
is
that
the
okd
one,
the
okd
dot,
io
repo,
where
we're
going
to
go
on
to
the
next
topic
here
that
we've
now
got,
that
is
in
a
weird
wonky
repo
directory
too.
It's
openshift-cs
which
actually
stands
for
customer
success,
was
the
team
that
the
website,
the
team
that
worked
on
it
with
me
and
created
it
ages
and
ages
ago,
used
to
be
called
the
customer
success.
Team
and
now
they're
been
changed
their
names
ten
times
since
then.
E
C
C
I
think
that
would
be
my
druthers,
but
that
then
becomes
the
other
problem
of
permissions
to
do
anything
because
then
the
openshift
repo,
basically
is
I
99.9
percent
red
hat
engineers
will
have
permission
to
do
anything.
I
there
might
be
a
few
non-red
hatters
who
are
associated
like
with
fedora
and
linux.
That
might
have
permission-
I
don't
even
know,
but
I
would
say
so.
That's
the
other
thing.
So
it's
freedom
versus
respect,
maybe
how's
that.
A
That
brings
up
an
interesting
point,
though,
so,
if,
if
we
wanted
to
do
the
agenda
items
and
have
the
chairs
be
able
to
modify
the
members
file,
wouldn't
the
chairs
all
have
to
have
yeah?
Well,
I
guess
you
could
they
could
submit
full
request
to
the
community
repo.
But
for
me
working
on
the
agenda,
I
wouldn't
want
to
submit
a
pull
request
and
work
on
the
so
that
so
either
I
would
need
access
or
not
me
being
representative
of
anyone
who's
not.
A
C
So
I
think
the
bigger
car
I'd
like
to
have
a
conversation
about
that
with
vadim
in
there,
because
he
is
sort
of
our
liaison
to
the
engineers
who
have
the
privileges
to
do
all
of
that.
And
that
could
be
the
next
working
group
meeting
and
add
that
into
the
agenda
about.
How
can
we
this
rag-tag
bunch
of
repos?
How
can
we
make
them
into
a
more
respectable
and
still
have
the
ability
to
edit
and
do
what
we
need
to
create
a
site
underneath
this.
E
Yeah.
Because,
because
because
I
guess
we
want
to
consolidate
where
we
can,
I
mean,
but
also
like
bring
vadim's
installer
from
his
personal
github,
into
an
open
shift,
an
okay
d,
repo,
so
yeah.
It
sounds
like
we
do,
need
a
discussion
around
our
use
of
github,
which
will
come
into
all
the
permissions
and
ease
of
use.
And
but
I
think
it's
worth
just
trying
to
remove.
E
C
A
So
I
don't
we're
we're
at
halfway
through
the
meeting
I
do
want
to
get
to
the
other
thing,
so
I've
added
repo
discussion
added
to
the
main
meeting
agenda
beta
site
brian.
Do
you
want
to
give
us
an
update?
I
think
you
were
waiting
for
diane
to
publish
some
buttons.
Oh
okay,.
C
And
let's
take
a
look-
and
this
is
the
repo
that
that
brandon,
I'm
hoping
will
be
able
to
help
us
make
pretty.
E
Right
so
the
first
thing
you've
noticed:
I
have
totally
removed
all
of
the
middleman.
I've
totally
removed
bootstrap.
This
is
a
pure
markdown
site,
so
everything
about
okd
banner
is
now
comes
from
markdown,
so
we
can
go
and
change
the
home
page.
We
can
change
all
the
document.
It's
all
just
marked
down
now
in
a
git
repo
and
if
you
go
to
the
very
little
top
to
the
left
of
the
search.
E
E
So
if
you
just
move
the
browser
to
these
just
shrink,
it
leftwards
it
is
fully
responsive,
so
it
it
can
be
used
on
a
mobile
if
you
just
keep
going
just
keep
going
smaller
and
smaller.
Just
imagine
it's
like
a
a
mobile
phone
size
thing
you'll
find
that
the
the
sidebars
vanish
and
then
we
get
a
hamburger
menu
and
it
just
sort
of
it's
all
responsive.
E
E
E
B
C
Mean
I'm
okay
with
it
going
to
that
other
site,
because
it
means
that
michael
burke
keeps
maintaining
it.
The
guy
who's
not
on
video
right
now,
mostly
because
and
because
it's
something
that's
generated.
D
E
C
Again,
just
jumping
from
the
menu
yeah
go
for
it
yeah.
That
would
probably
be
good,
so
yeah
yeah.
I
think
I
think
you're
right
about
that.
Yes,
I'd
agree
with
that
and
the
other
question
I
have
is
these
things
that
say:
temp
content
community
adequate
is
there
stuff
to
grab
and
put
in
there
or
do
we
need
to
create
that?
A
Were
gonna,
you
were
gonna,
look
up,
diane
the
rights
and
responsibilities
type
stuff
from
other
communities.
I
believe.
A
Yes,
yeah.
That
was
because
I
I
think
the
gist
was
that
we
wanted
to
get
something
that
is,
you
know
like
the
cncf
has,
has
a
nice
guidelines,
basically
in
code
of
conduct
and
and
whatnot,
and
I
think
that
you
know
having
something
there
would
be
good,
but
I
mean
we
can
search
out
stuff,
but
you
had
volunteered
if
you're
strapped.
C
E
C
C
D
C
No,
I
think,
you're,
okay,
the
way
it
is.
I
actually
like
the
way
it
looks
so
the
missing
pieces
that
you
need
me
to
do
is
how
to
ask
for
help
community
etiquette,
let's
walk
through
it
from
the
top.
What's
what
do
you
need
to
pull
over
still
brian.
E
Yeah
I
mean
there's
a
lot
of
stuff,
I
mean
I
was
really
focusing
on
the
styling
and
getting
the
css
right.
So
I've
not
really
been
looking
at
the
content.
I've
just
started
moving
the
guides
across.
I
haven't
actually
pushed
it
yet
so
I've
just
started
moving
the
guides,
which
is
under
the
getting
started.
We've
talked
about
moving
the
content
from
okd
main
repo,
there's
that
big
readme
there,
which
has
a
lot
of
stuff
in
it.
E
So
some
of
that
stuff
will
come
into
the
installation
and
I
believe
we
want
to
talk
to
vadim
in
terms
of
what
he
thinks
should
be
in
this
section
and
because
he
created
that
initial
thing
blogs,
so
more
or
less
I've
moved
across
with
their.
Then
it's
the
community
stuff
and
it's
the
community
contribution
stuff
which
a
lot
of
it
I
think
we're
gonna,
have
to
create
from
fresh.
E
C
For
next
week,
I
would
focus
on
that
so
that
everybody
gets
to
see
it,
but
I
think
if
we
run
this
by,
it
looks
great.
Thank
you
for
it.
First,
first
and
foremost,
is
there
anything,
then
if
we
get
any
styling
or
css
issues
that
you
can't
handle,
or
you
don't
have
time
to
handle,
that's
what
I
think
the
third
party
contractor
I
have
and
I'm.
C
You
know
what
I
think:
you've
done
a
very
good
job
to
be
quite
honest.
Let's
what
I
would.
What
I
would
say
is:
let's
show
it
to
the
larger
group
next
week
get
their
feedback.
If
they
say
oh,
that's
ugly
or
that
doesn't
work
or
that's
not.
You
know
working
for
them
on
their
browser
or
something.
Let's
let
the
third
brandon
work
on
those
issues.
For
us.
We
can
even
tag
him.
He's
got
a
luminous,
coder
you'll,
see
him
in
the
okd,
repo
and
or
maybe
other
repos
every
once
in
a
while.
C
So
he
could.
He
could
do
those
things,
but
I
think
the
stuff
where
we
have
to
create
the
content.
He
doesn't
know
enough
about
who
we
are
and
what
we're
doing
to
do
that
other
than
maybe
a
grammar
check.
Checker.
A
And
I
think
one
thing
we
can
do
is
vadim
hasn't
been
able
to
show
up
to
the
last
two
main
meetings
at
the
next
main
meeting.
If
he's
there,
we
can
talk
to
him
about
splitting
that
stuff
off
of
the
okd
repo
read
me
and
some
of
which
will
go
into
installation,
some
of
which
will
go
into
you,
know,
nightlys,
whatever
we
want
to
call
the
you
know
the
stuff
related
to
the
nightlys
for
48
and
whatever
so
yeah.
A
I
think
the
larger
group,
and
also
seeing
if
we
can
pin
down
vadim,
to
really
give
us
his
perspective
on
sort
of
breaking
up
the
the
installation,
instructions
and
stuff.
That's
in
that.
Okay,
but.
E
But
I
mean
I
said:
once
we've
got
the
once:
I've
got
the
instructions
there.
The
idea
is,
then,
that
this
should
become
a
very
dynamic
site.
Everyone
should
just
be
able
to
add
content
quickly
and
even
if
you
just
want
to
put
us
something
on
the
heading
that
don't
install
4.81,
because
it's
busts
this
week
and
then
next
week,
when
we
fix
it,
we
can
take
the
thing
off
the
home
page.
We
can
do
things
like
that
very
very
dynamically.
It's
it's!
It's
not
difficult
to
do
so.
A
To
get
to
so
there
really
is:
are
we
so
we're
saying,
there's
really
nothing
in
terms
of
like
copyright
or
anything
like
that?
That
needs
to
be
added
to
it.
If
so,
then
we
can
just
strike
that
and
not
worry
about
it:
yeah,
okay,
so
delineation
of
resources
for
the
working
group
and
okd
users,
we
need
to
change
that
text
at
the
top
and
give
that
to
diane,
so
we've
been
kind
of
putting
that
off
as
we
worked
on
other
things,
but
I
will
work
diligently
on
that.
A
If
anyone
else
wants
to
chip
in,
I
will
do
it
as
a
as
a
document,
maybe
in
the
okd.io
repo
or
something
like
that,
and
then
this
will
be
the
text
we
put
at
the
top
of
the
google
chat
group.
That
makes
it
clear
that
that's
more
for
working
group
business
and
then
also
change
the
text
in
the
slack
channels
to
point
to
hey,
create
a
discussion
item-
and
you
know
we
mentioned
this
last
time.
A
Vadim
has
really
been
doing
a
great
job
of
transitioning
stuff
to
the
discussion
items
that
really
aren't
bugs
they're,
not
issues
they're
discussion
items
because
it's
someone
needs
to
know
how
to
do
something
or
something
like
that,
and
I
I
I
think,
we're
narrowing
in
on
a
very
efficient
process.
So.
A
And
yeah,
this
is
that
item
diane
for
look
into
the
working
group
guidelines
and
conflict
resolution.
C
Yeah
now
that
you
have,
if
you
get
brian,
if
you
get
the
mk
docs
documentation
in,
I
will
grab
those
things,
and
I
will
try
by
next
tuesday
to
get
that
in
so
that
people
can
see
it,
and
we
can
look
at
it
as
a
group
as
well
see
if
that
works.
For
folks
and.
B
Yeah-
and
I
was
just
thinking
that
something
that
I
didn't
see
in
our
process,
that
might
be
useful,
is
with
respect
to
docs,
okay,
which
is
that
whenever,
in
theory,
whenever
there
is
some
confused
user
that
had
to
put
in
a
discussion
to
get
themselves
out,
then
the
docs
should
be
adjusted
so
that
they
wouldn't
have
been
confused.
B
And
that's
sort
of
analogous
to
the
the
philosophy
that
whenever
you
find
a
bug
manually,
you
put
in
an
automated
test
so
that
you
don't
get
a
regression.
A
A
I'm
gonna
bring
up
the
topic
of
single
node
clusters
and
also
bare
metal,
because
we're
getting
a
lot
of
requests
in
terms
of
documentation
and
in
terms
of
issues
in
regards
to
both
of
those,
and
I
think
we
need
to
flush
those
out,
because
a
significant
number
of
okd
users
are
looking
for
home,
lab
single
node
cluster,
you
know
and
and
and
sort
of
the
minimal,
installs
and
bare
metal,
right
and
stuff
like
that.
D
A
Single
node
stuff
should
be
easier
with
4.8.
It
is,
but
I
don't
know
if
you
caught
that
discussion
the
past
couple
days
vadim
was
under
the
so
in
our
faq.
A
F
B
Actually,
I
thought
it
was
clear
because,
like
certainly
in
in
all
of
charles
single
note
installs
that
he's
been
doing
for
the
last
year,
you
have
to
hack
a
bunch
of
things
right.
A
A
It
does
not
work
on
four
six
or
four
seven.
It
does
work
on
four
eight.
So
we'll
need
to
update
the
docs
on
that
and
up
and
up
our
game
in
terms
of
testing
to
catch
those
cases.
B
A
It
wasn't
a
feature,
and
that
was
actually
something
for
ocp
that
was
touted
as
a
feature
was
single
node
clusters
right,
but
yeah
back
to
your
original
point.
B
A
Oh
yeah-
and
I
appreciate
that
about
you
bruce.
I
you've
brought
some
things
to
people's
attention
over
the
you
know,
past
year
or
two
that's
been
like
well,
this
is
supposed
to
work
and
it's
not
or
you
know
it
says
here
in
the
documents-
yeah
and
that's
been
really
helpful.
Okay,
so
we're
punching
again
on
name
and
scope
of
the
installation
doc,
because
vadim
wasn't
at
the
last
meeting
I'll
put
it
on
the
agenda
again
for
the
next
meeting,
so
inclusive
language
update
brian
you're
sort
of
hinging
on
the
folks
that.
C
C
E
C
Yep,
I
think
that
thank
you
for
summing
up
and
the
other
thing
is,
I
know
that
will
yuri's
in
on
european
time.
Will
gordon
just
went
on
pto,
but
yuri
is
waiting
for
us
just
to
say
when
we
want
to
repoint
the
site
over
to
that.
So
it's
just
a
dns
name
change.
C
So
as
soon
as
we
get
our
content
in
there
and
group
approval,
we
can
make
that
happen,
and
it
you
know
whatever
it
takes
48
hours
once
the
the
foldover
goes
and
the
sooner
the
better,
in
my
humble
opinion,
so
and
that's
why
getting
if,
if
we
need
brandon
to
give
you
a
hand,
brian
just
ping
me
and
chat
and
we'll
make
this
okd
middleman
thing
go
away
very
far
away.
A
You
know,
and
in
fact
this
came
up-
I
think
in
what
we
put
at
the
top
of
the
google
discussion
group
and
at
the
top
of
the
slack,
may
want
to
reference
the
code
of
conduct,
slash
community
guidelines
stuff
and
have
a
reference
in
there
to
the
inclusive
language,
because
I
am
noticing
in
the
chat
there's
a
lot
of
hi,
guys
hi,
guys
hi
guys,
and
although
there's
the
the
cncf
has
that
bot.
A
You
know
it
would
be
better
to
actually
have
something
ahead
of
time,
not
after
the
fact
yeah
yeah.
So
so
I
don't
want
anyone
to
get
the
impression
that
we're
just
gonna
be
done
with
it.
After
this,
it's
some
it's
an
ongoing
process
right
to
continuously
make
sure
docs
are
up
to
that
standard
creep,
build
dock
outline
for
vadim.
A
This
is
gonna,
be
brian,
and
I
we're
gonna
hold
off
until
the
beta
site
is
ready
until
vadim
can
attend
a
meeting
and
we
can
and
and
and
vadim
has
time
he's
in
incredibly
pressed
for
time
right
now,
and
so
we
have
to,
I
think
brian
and
I
will
do
most
of
the
work
and
then
just
run
it
by
the.
D
A
So
the
idea
was
that
we
would
actually
flesh
out
upgrade
pads,
because
there
was,
you
did
find
some
documentation,
all
right
right
on
upgrade
pads
and
and
could
we
turn
that
into
a
like
a
table
or
something.
And
can
we
better
understand
what
red
hat
meant
and
right.
B
Well,
it
was
partially
just
defining
what
the
notations
meant,
but
there
are
some
related
things
like
some
things
that
have
come
up
recently
is
that
in
okay,
there's,
there's,
there's
basically
three
places
where
a
version
of
fcos
comes
into
play,
and
at
least
if,
like
the
way,
I
build
things
on
vsphere.
B
I
start
off
with
a
version
of
f
cos.
That's
in
a
where
the
iso
is
mounted
to
to
initially
boot
the
hosts
with,
and
then
that
one
pulls
down
a
version.
B
That's
referenced
in
in
the
the
initial
ignition
sequence
and
then
that,
assuming
that
boot
and
everything
bootstrap
and
everything
makes
it
up,
then
it
pivots
to
a
current
version.
A
Right,
but
actually,
interestingly
enough,
vadim
last
week
in
a
conversation,
was
said
to
someone
well
we're
not
really
using
a
version
anymore
because
it
gets
modified
and
it's
a
rebuild
basically
of
the
mod.
So
it's
interesting
for
folks
that
don't
know
the
way
the
ins,
the
okay
installer
works.
It
actually
downloads
a
version
of
it.
A
The
documentation
needs
to
be
clearer
about
what
you're,
starting
with
and
what
you're
going
to
end
up
with,
because
the
question
that
sparked
vadim
to
respond
was
that
someone
asked
like
well.
If,
when
I
do
the
os
rpm
tree
command
to
look
at
the
version
it
doesn't
jive
with
what
is
it?
Is
it
version?
That's
out
there
like
available
for
downloading.
B
Right
and
then
it's
a
referencing,
some
machine
config,
something
or
other,
but
along
the
ways,
depending
on
which
versions
you
get
some
of
them,
don't
work
right
and
and
there's
various
things
that
can
happen
like
when
you,
when
you
go
from
one
major
release,
know
like
32
to
33
to
34
to
35
whatever.
A
B
Love
the
yeah,
so
there's
so
in
instances
where
now
I
I
think
I
think
that
those
things
are
made
into
the
frequently
asked
questions
of
hey.
This
version
of
fcos
doesn't
work
for
these
versions
of
okd
right
so
slowly
slowly
we
seem
to
be
improving
those
sorts
of
things.
It
might
not
that
sort
of
stuff
that
would
be
useful
in
the
installation,
information
or
a
given
release
is
what
things
you
have
to
use
when
it
matters.
B
E
A
D
A
Four,
eight
or
you
know,
can
there
be
different?
You
know
minor
version
document
loads.
E
C
Generate
that
that
would
be
pretty
bloody
awesome,
and
that
would
but.
D
G
C
C
C
In
the
wild,
that's
the
problem
right,
yeah.
C
We
could
take
some
of
them
out
what
is
on
the
list,
michael
for
open
shift.
How
far
back
do
they
go
for
open
shift,
good.
G
Question
maybe
a
moment
it
goes
back
to
3.0.
C
Saying:
okay,
we're
going
to
grandfather
the
documentation
prior
to
3.0,
we're
going
to
and
stay
in
line
with,
whatever
openshift
has
for
documentation,
otherwise
use
the
wayback
machine
and
and
then
clean
it
up
just
do
a
notice
and
that
from
the
okd
working
group,
docs
and
socialize
it
at
the
next
these
ideas
at
the
next
working
group
meeting
next
week.
Jamie
will
do
and
say
that
this
is
our.
Our
intention
is
to
do
this,
and
if
anyone
has
any
objections,
let
us
know
and.
A
Michael
just
just
to
sorry
diane
I
didn't
mean
to
cut
you
off,
go
ahead,
michael
just
to
get
a
sense.
Do
we
have
the
so
right
now
the
way
things
work
is
you're,
generating
with
a
script,
the
okd
docs
off
of
the
ocp
docs
and
just
changing
the
names
out
we
put
in
a
ticket
for
like
a
minor
tweak
here
or
there
can
we
actually
put
in
a
ticket
for
like
a
new
page
to
be
created
or
anything
like
that?
Or
is
it
or
are
we
just
being
limited
to
tweaks
of
what
gets
generated?
A
A
B
I
don't
know
it
could
be
okd
books,
yes,
that
are
sort
of
you
know
like
free
for
download
red
hat,
pdfs
yeah
or
buy
it
from
o'reilly
or
whatever
those.
I
don't
think.
G
I'm
sorry
by
books
I
mean,
if
you
look
at
the
docs.okd.io
site,
everything
in
that
table
of
contents
on
the
left
side.
What's
new
architecture
installing
we
call
those.
A
Documentation
selected
version
yeah
look
at
that.
These
are
all
books
right,
because
these.
C
If
anybody
wants
to
write
an
okd
o'reilly
book,
let
me
know-
and
if
you
have
that
much
time
on
your
hands,
don't.
A
I
want
to
close
out:
we've
got
one
minute
left.
Just
so
folks
know
we
were
approached
by
the
red
hat
team,
that's
basically
building
off
of
kubrt
for
the
virtualization
stuff
in
ocp,
and
they
want
it
to
work
better
on
okd.
A
So
we
will
be
talking
at
the
main
meeting
about
this
next
week,
but
if
this
is
going
to
come
into
play
in
terms
of
documentation,
making
sure
that
we
promote
and
encourage
and
test
documentation
relating
to
using
cooper
for
virtualization
on
okd,
so
just
want
to
throw
that
out
there
real
quick
does
anyone
else
have
any
last
minute
things
before
we
sign
off.
We
have
one
minute
left.
G
C
Thank
you.
What
I
would
say
about
that
is
michael
burke.
If
you
can,
let
us
know
that
it
is
possible
officially
that
it
is
possible
to
add
the
four
point
x
versions.
I
will.
G
A
I
will
convent
all
right.
We
are
at
time.
Thank
you
so
much
folks
and
appreciate
all
of
your
hard
work.
See
you
next
time
all
right
thanks
brian.