►
From YouTube: OKD Working Group Meeting 11-23-2021
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
Get
started
with
our
november
23rd
meeting
first
folks,
if
you
could
put
your
name
in
the
attendees
section,
I'll
put
a
link
in
the
chat.
If
you
don't
have
the
document
handy
there
you
go
and
also,
if
you
could
take
a
quick
look
at
the
agenda
and
see
if
there's
anything
that
I've
missed
any
sections
there
and
we'll
wait
for
about
a
minute
or
so
for
folks
to
get
that
squared
away
and
then
we'll
jump
into
our
our
items.
A
Let's
see,
we
have
one
more
meeting
after
this
and
then
we're
breaking
for
the
holiday
season,
we'll
have
our
next
meeting
on
the
seventh
and
then
we'll
be
done
until
the
new
year
and
starting
back
up
on
the
fourth.
I
believe.
A
All
right
and
if
we're
good
with
the
agenda,
let's
go
ahead
and
get
rolling
on
this
release.
Updates
vadim
is
not
here,
but
I
can
share
with
you
what
he
shared
with
us,
although
christian
you're
on
the
call,
why
don't
you
go
ahead?
You
read
the
same
thing
that
I
did
so.
A
Sure
I
have
oh
okay.
Well
I
I
was
thinking
of
that.
He
chatted
some
stuff
but
updates
yeah.
So
in
short,
there's
an
issue
with
going
from
four
eight
to
four
nine.
The
upgrade
tests
are
failing
and
there's
a
pull
request
here.
I
can
link
to
it
that.
A
Is
an
attempt
to
work
through
these
issues
and
it's
basically
causing
a
reboot
of
an
odd
thing,
but
he
is
working
at
that,
and
so
his
efforts
are
very
much
appreciated
christian.
Do
you
have
anything
that
you
want
to
add
to
that
yeah.
C
C
B
A
hunch,
though,
and
vadim
is
following
through
with
that,
so
hopefully
that's
gonna
be
fixed.
If
it's
not,
if
it
can't
be
fixed,
we
will
just
not
conform
here
to
the
kubernetes
conformance
test
and
just
make
it
reboot
twice.
It's
not
like
anything
else
would
be
broken.
It's
just.
We
obviously
lose
the
availability
twice
and
it
should
prepare
the
confirmation
test
only
happened
once,
but
after
those
two
reboots
everything
still
works.
So
it's
not
like
there's
any
serious
issues.
It's
just
we.
We
don't
want
the
second
reboot.
B
Obviously,
so,
if
there's
no
solution
to
it,
we
will
still
go
ahead
and
release
4.9.
That
is,
although
obviously.
A
Does
anyone
have
any
comments
or
questions
about
that
or
anything
else
in
terms
of
the
4.8
to
4.9
transition.
A
All
right,
let's
see
moving
on
now
to
fcos
updates
with
timothy
go
ahead.
D
B
There
is
a
pr
open
for
that
as
well
and
yeah.
That's
awesome,
so
we
will
definitely
switch
over
to
the
35
soon,
apparently,
we're
still
obviously
rebuilding
okd
the
fedora
core
os
into
the
okd
base
os.
I
eventually
and
I've
been
kind
of
talking
with
jonathan
livon
from
the
core
team.
Eventually,
we
don't
want
to
do
the
rebuild
anymore
and
just
kind
of
layer
on
top
of
fedora
core
os
we'll
need
some
additional
tooling
for
this.
B
That
is,
however,
on
its
way,
there's
some
interesting
enhancements
going
on
on
the
coreos
side
that
I've
just
been
following
from
afar,
but
yeah.
That's
awesome.
Awesome
work
on
the
coreos
side,
so
thank
you
very
much,
timothy
and
yeah.
Looking
forward
to
all
those
changes
that
are
coming
soon.
D
Yep,
hopefully,
that
should
at
least
the
federal
certified
rebates
should
help
with
network
manager
and
everything
so
yeah,
and
apart
from
that,
we've
got.
D
We've
got
something
that's
about
merging
the
mco,
but
related
to
all
the
interaction
in
interaction
with
ssh
key
long-standing
issues,
which
is
no.
It
should
not
be
fixed
and
hopefully,
we'll
be
fixed
or
okay.
If
I
find
the
pr
again.
B
Right,
yeah
that
pr
merged
yesterday
and
we
we
do
have
some
similar
functionality
in
our
machine
config
operator,
fork
that
we're
still
carrying
right
now
for
okd
but
yeah.
Eventually,
that
is
one
of
the
last
few
remaining
comets
that
had
to
go
in,
and
I
think,
there's
only
really
two
minor
things
that
still
have
to
be
fixed
in
in
the
mainline
code.
B
Until
we
can
move
back
to
using
that
mainland
and
not
requiring
the
fork
so
yeah,
I
do
hope
we
will,
and
that's
kind
of
the
agreement
with
the
machine
config
operator
team
that
we
get
all
that
in
into
mainline
in
the
4.10
release
cycle,
which
is
the
current
cycle,
we're
working
in
so
yeah,
hopefully
with
4.10.
We
won't
be
needing
that
fork
anymore
and
that's
on
its
way.
I
think
there's
only
a
few
minor
issues
now
remaining,
so
I
think
we're
pretty
good.
There.
D
Remember
if
anything,
big,
impacting
federal
rest
right
now,
so.
A
Excellent,
okay
and
now
we're
going
to
move
on
to
the
docs
update
with
brian
and
he's
on
the
call
or
not.
No
so
brian
go
ahead
and
take
it
away
from
update
from
the
docs
meeting.
E
Okay,
so
the
docs
is
sort
of
live
into
normal
running
now
from
the
mk
docs
update,
so
everything's
done,
we've
got
a
code
of
conduct
coming
and
michael
is
sort
of
worth
sniping
that
at
the
moment
and
one
area
of
discussion
that
came
up
in
the
doc's
work
group
that
we
sort
of
defer
to
this
group
is
what
is
the
use
of
the
okd
repo
going
to
be
moving
forward,
because
at
the
minute
we've
got
documentation,
split
between
the
repo
and
the
opd
community
documentation,
as
well
as
the
product
documentation.
E
So
it's
just
thought
it's,
it's
probably
worth
having
a
conversation
as
to
should
we
move
the
documentation
out
of
the
opd
repo
and
use
that
for
as
an
issue
tracking
mechanism
and
have
the
document
the
community
documentation
in
a
single
place
or
do
we
think
there
is
a
useful
documentation
within
that
gate,
repo,
and
so
that's
a
conversation
really
for
this
group
to
make
it
make
a
decision
on
and
get
people's
views.
So
what
do
people
think.
F
Where
did
the
and
sorry
that
I
don't
know
this
off
the
top
of
my
head?
Where
do
the
open
shift
docs
reside?
Are
they
in
the
open
shift
repo
on
github
christian?
F
E
Well,
it
was
really
that
if
you
look
at
the
okd
main
repo,
the
open
ship,
slash
okd
repo
we've
got
some
documentation
in
there.
There's
some
old
guides
in
there
and
there's
some
how-to
information
in
there.
And
it's
really
should
we
move
that
out
of
the
repo
and
focus
it
on
the
the
ukd.io
website
and
make
that
the
single
place
for
community
documentation.
A
Yeah
and
one
of
the
things
that
that
this
points
to
is
that
again,
I
saw
updates
actually
to
the
guides
the
old
guides
in
the
okd
repo
a
couple
days
ago.
I
need
to
mention
something
to
vadim,
because
I
think
vadim
approved
it.
We
don't
want
any
changes
to
those
anymore.
We
need
to
actually
delete
those,
because
those
all
got
moved
mike,
I
think,
has
all
of
those
now
when
he
moved
those
over
to
the
okd.io
site.
A
So
I
think
what
we
need
to
do
is
decide
like
just
to
make
sure
we
have
everything
updated.
I'm
not
sure
how
we're
going
to
do
that,
like
because
people
added
updates
to
those
recently
make
sure
that
everything
is
updated
on
the
website
and
then
delete
all
of
that
stuff
and
then
ask
vadim
if
he's
comfortable
with
that
okd
repo
just
being
for
issues
on
the
software
and
discussion
on
the
software
and
everything
else
being
the
okd
that
I
o
repo,
which
I
think
we
agreed
is
going
to
move
eventually
to
get
lab.
A
If
we
can
get
everything
working
correctly
right
and
take
it
out
completely
from
openshift,
because
the
problem
is,
is
that
we
have
no,
we
have
a
little
bit
of
control,
but
not
a
lot
right,
and
if
we
move
it,
then
we
can
exercise
more
control
and
be
a
little
more
creative
with
how
we
do
access.
A
That
was
my
thought,
so
I
think
putting
it
under
the
open
shift
would
actually
take
us
in
the
other
direction.
Right
from
where
we
were
that's.
F
A
C
I
have
a
question
here
so
like
we,
you
know
we
have
like
docs.okd.org,
which
is
like
generated
from
the
actual
ocp
like
fork
of
the
product,
docs
or
whatever,
and
then
we're
talking
about
the
open
shift,
kind
of
more
community
oriented
docs
here,
and
my
question
is
like:
if
we
intend
that
community-oriented,
you
know
repo
to
be
a
place
where
the
community
can
actually
come
and
contribute
guides
and
stuff
like
that,
then
you
know,
if
that's
kind
of
the
ultimate
intention,
then
we
definitely
need
to
have
that
in
a
place
where
everybody,
you
know,
the
governance
can
be
more
community
oriented
and
everyone
can
feel
comfortable
kind
of
coming
and
contributing
stuff
there
so,
like.
A
Yeah
and
diane,
actually
I
did
open
a
an
issue
and
assigned
you
to
it
to
investigate
the
legal
ramifications
of
that.
A
Basically,
we
want
to
know
is:
is
this?
Is
this
going
to
cause
any
problems
with
redhead
or
are
they
okay?
If
we
move
the
document
now?
The
one
thing
we
have
to
ask,
though,
is
moving
this
out
it
is,
it
will
mean
going
even
further
or
an
even
greater
separation
between
the
generated
okd
docks
that
michael
is
in
charge
of,
and
the
reaper
that
we'll
have
in
presumably
git
lab
bruce
was
doing
some
testing
to
see.
A
If
we
can
get
the
mk
docs
and
what
not
working
get
lab,
then
we
we
will
be
going
like
even
across
repositories,
repository
servers
as
the
case,
which
is
something
to
keep
in
mind.
E
F
Yeah
yeah
docs
are
pretty
separate
from
the
code
base,
so
I
just
I
and
the
there's
a
little
chat
going
on
here
too,
that
the
sl,
the
github
slash,
okd
repo,
has
been
taken
by
somebody's
who's.
You
know
sitting
on
the
real
estate,
but
I
think
it
it
looks
like
some
I
could
reach
out
and
ask,
and
sometimes
legal
can
reach
out
and
ask
and
and
get
that
back
for
us.
F
G
H
F
Yeah
so
I'll
see
what
I
can
do
about
that.
But
we'll
add
that
in
yeah
reserve
timothy,
if
you
could
the
okd
dash
project
at
just
in
case
and
github
and
and
I'll
see
I'll
work
on
that,
because
it's
nice
and
quiet
this
week,
while
everyone
in
the
states
eats
turkey.
E
Just
picking
up
from
the
mike's
post
in
the
chat
are
we
going
github
or
gitlab.
I
G
C
A
Was
a
gitlab
or
github
that
changed
their
policy
on
project
names
that
conflicted
with
other
people's
projects?
One
of
them
recently
changed
their
policy
like
the
in
the
past
year
about
that.
I
don't
remember
which
one
but
something
to
consider.
But
if
you
reach
out
to
the
individual,
it
doesn't
look
like
they're
doing
any
commits
on
the
get
lab
ones,
so
they
might
treat.
B
Yeah,
I
I
would
prefer
if
we
could
keep
all
of
the
collaboration,
mostly
on
github,
just
because
all
of
the
code.
I
Once
we're
in
a
separate
organization,
most
of
the
benefits
of
being
on
github
versus
get
lab
fall
away,
because
you
can't
do
things
like
migrate
issues
across
orgs.
You
can't
you
can't
actually
make
pull
requests
stuff
like
that.
The
only
main
value
of
doing
it
on
github
versus
gitlab
is,
if
you
wanted
to
have
like
a
code
fork
in
okd's
project
versus
on
the
openshift
door.
I'm
not
sure,
that's
something
we
actually
want
to
do,
but
if
that
is
an
option
that
people
are
actually
comfortable
with
us
ever
actually
exploring
then
sure
otherwise,.
A
B
I
think
that's
just
personal
yeah
for
me,
that's
just
personal
preference,
because
I
spent
most
of
my
time
on
github.
I
don't
want
to
block
any
words
like
yeah.
G
F
F
Give
me
until
the
december
7th
meeting
that
do
a
little
research
and
background
on
that
that
topic
and
grabbing
back
the
okd
one
and
I'll
see.
If
I
can,
if
there's
anything
the
ospo
team
or
governance
team
has
to
say
about
that
either.
I
I
don't
know
I
I
don't
have
an
opinion.
I
just
have
a
github
account,
not
a
gitlab
account.
A
So
one
of
the
things
that
we
can
do
is
issues
so
their
thing
of
discussions,
I
think,
is
pretty
much
similar,
but
the
other
thing
we
talked
about
before
was
tags
for
issues
being
for
website
or
code
or
whatever
and
breaking
things
down
by
the
tags
for
issues
or
whatever.
So
that
would
cover
things
that
are
like
issues
on
the
site
and
whatnot
and
then,
in
terms
of
general
discussion,
I
I
don't
know
how
we
would
do
that.
K
Yeah
but
but
I
thought
we
were
using
the
github
account,
for
you
know,
bug
reports
and
discussions,
and
you
know
like
basically,
all
the
stuff
that
is
currently
on
the
github
account
we're
still
going
to
keep
there
that
we
were
just
moving
all
the
docs
over,
but
well
I
mean
that
was.
I
thought
that
was
a
discussion.
F
Yeah
did
yeah,
so
I
obviously
I
missed
something
while
I
was
away
in
in
the
get
lab
conversation,
so
I'm
gonna
go
back
and
watch
the
recordings,
and
so
I
I
I
don't
have
a
preference
either
way.
I
just
think
there
might
be
a
cultural
thing
out
in
the
kubernetes
world
where
people
are
using
github
more
frequently
and
that
I'm
concerned
a
little
bit
about
what
the
other
300
or
so
people
who'd
never
come
to.
E
Yeah
I'll
just
say
so,
it
sounds
like
folks
for
sort
of
phase
one
or
step
one.
We
can
look
at
shutting
down
the
documentation,
content
on
openshift,
okd,
github,
repo
and
then
a
stage
two
is
where
it's
all
gonna
live
eventually,
so
yeah
I'll
I'll
take
a
task
on
trying
to
get
rid
of
the
guides
and
that
put
a
pull
ruckus
in
to
delete
all
that
sort
of
stuff.
We
probably
need
vadim
to
look
at
some
of
his
contribution
because
he's
got
things
like
some
stuff.
E
Partial
instructions
like
to
build
a
release
within
the
repo,
so
we
need
to
work
out
where
that
should
go
and
if
that
is
actually
worth,
porting
needs
updating,
valid
or
so
I'll
I'll
reach
out
about
him.
On
that,
and
just
to
finish
off
the
docs
greedy
has
created
a
a
draft
survey.
I
don't
have
a
link
to
it
and
I've
just
been.
We
didn't
put
one
in
the
in
the
agenda
and
then
the
meeting
notes
from
the
last
docs
meeting,
so
I
think
we're
getting
ready
to
release
that
it's
sort
of
getting
finalized.
A
A
Hasn't
done
the
survey
she
hasn't
done
it.
She
was
doing
google
forms,
but
she
hasn't
completed
all
of
the
things
that
we
talked
about
at
the
last
meeting.
So
okay,
here
I'll
put
it
in
the
meeting
notes
as
well.
Here:
okay,.
F
So
she
also
I'm
sure
you
guys
talked
about
this.
While
I
was
way
too,
she
also
created
the
okd
twitter
handle,
and
so
what
I'm
hoping
to
do
with
that
is
push
out
this
survey
as
well
as
each
time
we
put
a
new
release
out,
put
a
notice
in
that
okd,
one
that
that's
going
on
and
then
whenever
we
do
a
talk,
or
maybe
even
the
meeting
reminder
to
add
that
in
so
it
just
starts
getting
some
a
little
bit
of
content
going
there.
F
That's
very
specific
to
these
meetings
and
talks
and
events
not
sort
of
fluff.
Unless
someone
writes
a
wonderful
okd
swimming
upstream
blog
post,
those
kinds
of
things
and
retweet
them
there
so
yeah,
so
that
that's
where
I
would
push
out
that,
as
well
as
the
the
mailing
lists
for
the
survey
and
maybe
even
linkedin
posts
there.
So
we
can
do
some
socializing
and
get
some
real
feedback
there.
K
Just
throw
in
one
more
thing
on
the
on
the
docs
thing
like:
if
you
look
at
the
way,
most
get
repositories
are
organized
the
the
documentation
for
that
specific
code.
That's
in
the
repository
is
documented
in
that
repository
right.
You
know
so
like
there'll,
be
a
readme
and
maybe
an
install
and
all
that
stuff.
K
In
our
case,
it's
a
bit
different
because
we're
basically
a
delta
to
the
official
site,
and
that
makes
it
hard
to
find
you
know
if
you
were
going
to
try
and
build
the
code,
it's
hard
to
find
everything
as
we've
talked
about
many
times.
K
That's
sort
of
any
way,
that's
a
vedim
question
right
or
maybe
a
christian
question.
What
makes
like
we
sort
of
talk
to
them
off
and
on
about
pulling
stuff
over.
I
don't
know
that
we've
ever
asked
them
what
makes
sense
to
stay
there
in
terms
of
the
readme
you
know
document
and
so
on.
Well,.
B
Well,
yeah,
I
I
think,
since
we're
since
the
the
main
docs
is
generated
from
essentially
a
shared
documentation
that
is
also
used
by
ocp.
I
don't.
I
think
we
don't
want
to
lose
that,
because
otherwise
we'd
have
to
replicate
everything
somewhere
else,
and
I
think
it
might
be
easier
to
kind
of
add
the.
What
I
would
prefer
is
still
to
have
a
single
source
of
truth
here,
and
maybe
we
can
convince
the
the
red
hat
docs
team
to
allow
for
those
guides
that
we
have
these
community
guides.
B
We
also
pulled
into
the
main
main
repository,
but
then
only
be
generated
for
the
okd
docs.
I
think
you
can
just
exclude
stuff
there
for
the
ocp
product
line
and
have
essentially
files
that
will
only
be
included
in
the
in
the
okd
docs.
Maybe
we
could
add
those
community
guides
to
the
main
documentation
as
something
that
then
only
shows
up
in
the
ok
detox.
That
would
be
my
preferred
way
of
doing
things
just
to
have
all
of
those
things
centralized
somewhere.
I
think
the
the
fewer
repositories,
the
better.
E
I
think
the
issue
with
that,
though,
is
it
then
can't
be
community
contributed.
I
think
the
whole
idea
of
what
we're
trying
to
do
is
facilitate
the
community
being
able
to
contribute,
and
if
we're
moving
everything
back
into
the
official
red
hat
repos,
we're
then
limiting
it
to
red
hat
only
contribution.
E
All
red
hat
is
having
to
do
the
transformation
and
the
work,
and
so
what
would
I
think,
what
we're
trying
to
do
is
go
exactly
the
opposite
direction.
Keep
the
official
stuff
that's
built,
as
it
is
now
on
docs.ok
io,
but
have
a
community
site
where,
eventually
we
don't
have
the
red
hat
barrier
to
contribution,
because
it's
within
that
organization,
so
I
think
that's.
The
whole
idea
between
okidi.io
is
is
having
that
community
capability
and
in
terms
of
adding
technical
documentation.
That's
what
we're
really
missing
from
the
project.
E
It's
the
low
level
stuff
and
the
stuff
that's
in
vadim's,
installer
repo.
I
think
that
is
the
primary
source
for
craving
a
build
image,
but
then
that
does
then
link
into
the
upstream
ocp
repos
and
pull
a
lot
of
stuff
in
it's
the
magic
that
goes
on
there.
As
we
get
into,
I
mean
I'd
like
to
pick
up
the
whole
thing
about
the
missing
operators,
things
like
pipelines,
githubs
and
so
again,
how
do
we
build
those
from
a
community
point
of
view?
I
think
all
that
documentation
should
be
okdie.I
o
one
of
the
challenges.
E
I
think
that
I
certainly
have
when
when
going
across,
this
project
is
just
where
do
I
go?
Look
I
mean
I've
tried
to
look
at
building
the
pipelines
and
I
think
I'm
on
to
about
six
repos
of
stuff
and
having
it
all
in
the
central
place
describing
the
relationships
I
think
is
going
to
be
a
lot
easier
than
trying
to
pick
out
the
the
reposito
specific
documentation
and
then
me
having
to
try
and
link
them
all
together.
B
Yeah,
that's
essentially
the
same
reasoning
as
I
had
in
moving
stuff
into
the
main
openshift
blocks,
but
I
I
do
see
the
point
I
mean
everybody
can
create
a
pull
request
and
even
for
those
openshift
docs,
the
official
ones,
but
yeah
you're
right.
It
still
needs
a
peer
review
by
some
red
hat
employee.
B
For
that
to
be
able
to
merge
in
there
so
yeah.
It
might
be
better
to
then
split
that
out.
Indeed,
we
we
don't
want
to
lose
the
main
openshift
generated.
Docs,
though,
because
that
is
still
very
much
bespoke
and-
and
you
know,
our
technical
writers
do
do
that,
and
we
kind
of
get
that
for
free
with
okd.
And
for
me
it's
just
a
little
bit
difficult.
I
mean
if
we
can
find
a
way
to
kind
of
get
both
into
onto
one
website.
B
That
would
be
ideal,
so
you,
as
a
user
you'd,
have
you
just
have
one
the
site
to
to
see
to
find
the
guides,
the
community
dogs
and
the
the
official
generated
dogs,
and
then
that
would
be
generated
from
two
separate
repositories,
one
that
the
community
owns
with
all
the
guides
and
the
all
that
stuff.
That's
currently
in
the
okd
repository
and
also
the
official
repository,
but
as
as
a
user
I
wouldn't
want
to,
would
have
to
deal
with
those
differences.
Where
does
the
stuff
come
from
so
yeah?
B
If,
if
we
could
just
have
one
second
repository
for
all
those
guides
and
kind
of
plug
that
into
the
into
the
docs
website,
make
it
show
up
on
the
docs
website
as
well?
In
addition
to
the
generated
stuff
from
the
openshift
docks,
that
would
be
ideal,
but
yeah
I
have.
I
don't,
have
I'm
not
very
familiar
with
with
how
that
is
actually
generated.
A
Yeah,
well,
you
know
what
we
need
is
an
okd
cluster
that
we
can
run
a
task,
a
pipeline
on
that
pulls
down
from
one
repo
and
then
commits
to
the
other
on
a
regular
basis
and
then
you'd
be
able
to
incorporate
the
docs
into
you,
know
the
the
external
repo
you
know
just
by
cloning
it
down
and
then
putting
it
into
into
the
docs
repository
the
into
the
community
docs
repository.
A
So
are
we
good
on
this?
I
feel
like
we
still
need
to
talk
to
vadim
because
he
doesn't
really
know
he's,
incidentally,
he's
sort
of
missed
every
meeting
where
we've
had
detailed
discussions
about
this
just
through
chance,
and
so
I
feel
like.
We
should
definitely
include
him
in
this.
F
Well,
it's
maybe
what
what
I
can
do
is
in
the
interim
between,
because
we're
only
going
to
have
one
more
meeting
between
now
and
december.
7Th
is,
if
I
can
get
not
taro
jamie
myself,
vadim
and
christian
on
a
quick
call
in
between,
and
we
can
maybe
suss
out
what
the
implications
are
and
pull
in
michael
burke
as
well.
I
think
we
have.
We
have
one
docs
meeting
there
too
between
now
and
the
seventh.
F
So,
let's
see
if
we
can
do
a
little
quick
sprint
and
figure
out
what
the
logistics
are.
I
just
don't
want
to
lose
the
docs
teams
as
resources
for
generating
the
okd
dot
io
stuff
do
something
that
would
would
would
lose
lose
those
resources
they're
very
key
for
us,
and
I
think
my
gut
says
that
there
is
a
way
when
they
generate
those
docs,
okd.docs.io
or
docs.okd.io.
F
They
can
add
a
sub
group
of
links
out
in
the
menu
on
the
side
to
the
guides
in
some
way,
and
so
that
would
pull
from
the
stuff
that
brian
innis
has
been
working
on
with
the
make
docs
and
make
links
there
in
one
canonical
docs.okd.io
and
the
community.
Could
still
be
working
on
the
the
guides
and
all
of
that
and
then
put
pull
requests
in
on
docs.io.
F
That's
after
listening
to
everything
today,
that's
kind
of
where
I
think
we're
gonna
head,
but
I'd
like
to
talk
to
vadim
as
well
to
make
sure
it
doesn't
screw
up
anything
he's
thinking
about
so.
L
Hi
everyone
just
a
quick
update
on
the
virtualization
side.
We
are
now
implementing
automated
tests
for
running
okd
virtualization
with
rook
io,
so
it's
currently
still
under
development,
but
we
already
reproduced
it
manually
and
it
seems
to
work
fine.
L
But
that's
a
good
news
for
us
and
on
the
communication
side
we
are
redirecting
the
existing
website
for
okay
diverterization
to
the
subgroup
within
the
okdio.
A
All
right,
then,
let's
move
on
to
any
issues.
Are
there
any
issues
in
the
repo
that
folks
want
to
bring
to
our
attention
that
that
point
to
anything
that
maybe
the
the
group
can
take,
take
some
action
on
or
improve
documentation
or
anything
of
that
nature?
Is
there
anything
that.
B
I've
just
leaked
one
issue
in
the
chat
here:
issue:
nine,
six
three
and
I
I've-
I
didn't-
have
a
lot
of
time
to
look
into
it,
but
I
will
continue
to
do
so.
I
just
wanted
to
know
if
anybody
else
has
hit
this
issue,
and
this
is
essentially
the
machine
config
operator
is
degraded
after
installation
and
doesn't
come
up
properly.
The
logs
show
that
it
can't
find
the
rendered
machine
config
that
is
set
as
initial
node
config.
It
apparently
sets
sets
that
field
to
a
conflict
that
does
not
exist.
B
It's
at
least
not
the
one
that
is
rendered
by
the
machine,
config
controller.
B
A
I
can
do
a
upi
on
vs
here
and
see
if
I
can
duplicate
it
is
post
something
to
the
email
list
and
something
in
the
chat
asking
if
anyone
else
has
had
that
so
I'll.
Take
that
as
an
action
item
just
to
see
randomly
if
there's
anyone
else
out
there,
that
can
do
that.
We
need
to,
I
think,
leverage
that
a
little
bit
a
little
bit
more.
A
A
B
Start
there's
oh
yeah,
I
just
I
saw
that
sandro
opened
an
issue,
and
that
is
issue
898
I
was
wondering.
Have
you
have
you
hit
that
issue
again?
Is
that
still?
Is
that
still
an
issue
you're
hitting?
B
Because
really
these
ncati
service
should
be
disabled,
and
you
are
referring
to
a
tamil
file
here
that
we
used
to
have
in
in
okd
to
disable
it,
but
we've
since
removed
that
file
and
disabled
zincati
a
different
way.
So
I
yeah,
I
was
just
wondering
if
that's
still
an
issue.
I
haven't
heard
back.
L
There
I
saw
it
when
installing
on
4.7
and
I
didn't
redeploy
from
scratch
for
rotate.
So
I'm
not
sure
if
the
issue
is
still
there.
I
just
upgraded
from
four
seven
to
four
eight,
so
I
didn't
notice
any
special
case
for
this,
but
I
I
can
try
to
reproduce
installing
from
scratch
for
it,
and
I
can
report.
B
B
It
seemed
strange
to
me
that
this
was
that
this
would
pop
up,
but
if
it
doesn't
happen
on
for
eight
and
nobody
sees
it
on
for
eight,
I
would
like
to
close
all
those
old.
B
Obviously
I
think
back
then
4.7
was
the
latest
release,
but
that
seems
to
be
a
recurring
thing
here
that
people
try
old
versions
and
come
up
with
problems,
and
then
I
I
I
don't
really
want
to
spend
time
on
that.
If
we've
already
moved
on
from
that,
I.
L
Totally
agree:
I
opened
it
in
4.7
because
at
that
time,
for
the
tail
wasn't
yet
related.
So
oh.
B
Yeah,
absolutely,
and
and
and
that
that's
why
it
would
be
great
if
you
could
double
check,
it
still
happens
with
4.8
if
it's
not
fixed
there.
Obviously,
that's
that
would
be
an
issue
and
there
is
a
whole
bunch
of
other
issues,
though,
how
would
people
install
older
versions.
I
Can
even
connect
it's
worth.
We
might
want
to
consider
something
along
the
lines
of
what
happens
with
fedora
in
red
hat
bugzilla,
where,
when
a
new
release
goes
out,
you
know
throw
a
warning
tag
it
as
like
decade
or
whatever
and
like
if
nobody
confirms
that
it
is
actually
for
valid
for
the
new
release,
close
it
after,
like
a
couple
of
weeks.
F
Yeah
some
sort
of
general
surgeon's
warning
message,
politely
saying
you
know
this
is
that
we
can
put
into
the
comment
and
then
say
you
know
if
they
don't
respond
back
with.
You
know
they
are
stuck
on.
You
know
using
4.7
or
something
like
that
close
it
there's
some
there's
some
etiquette
around
this.
B
I
think
that
would
be.
That
would
be
immensely
helpful
just
to
keep
to
keep
us
focused
on
the
things
that
are
actually
that
actually
still
are
an
issue,
and
it's
it's
kind
of
similar.
With
more
discussions,
I've
been
seeing
people
following
some
guide
from
some
third
party
site.
B
You
know
we
should,
and
I
I
am
very
appreciative
of
the
dog's
effort
just
for
that
alone,
that
we
should
have
all
those
guides
in
okd
proper
and
not
have
people
follow
guys
from
some
blog
they
read
somewhere,
which
might
be
version
4.5
or
something,
and
it
just
you
know
if
they
install
the
the
current
version
with
that
blog.
B
Obviously,
things
might
go
wrong
that
nobody's
thought
of,
and
it's
not
really
productive
too,
to
spend
a
lot
of
time
on
them
yeah
if
we
could
kind
of
have
official
installation
guides-
and
I
think
this
is
essentially
what
brian
and
all
of
your
dogs
subgroup
is
working
on
and
if
we
make
could
make
it
easier
to
link
that
out.
I
think
that
would
happen
less
and
less,
but
I
I
I
also
don't
don't
want
to
just
shut
those
discussions
down.
You
installed
it.
B
The
wrong
way-
and
nobody
does
it
like
that-
that's
also
not
fair,
but
just
yeah
and
just
as
an
additional
comment
here,
yeah
the
less.
F
F
You're
hitting
my
one
of
my
mantras
of
I
hate
bla
documentation
by
blogging.
I
just,
I
think,
we're
doing
the
work
around
having
the
twitter
handle
starting
to
raise
the
visibility
of
okd.io
and
the
okd
twitter
handle
and
just
trying
to
pump
up
people
and
direct
them
to
the
right
places
is
really.
A
A
No,
that's,
that's
fine
always
feel
free
to
go
ahead.
I
we
did
see
one
come
in
recently.
It
was
like
an
issue
I
think,
or
a
discussion
item
where
someone
like
had
four
different
links
to
like
external
guides,
and
they
were
asking
for
our
help
and
it
was
like
all
of
these
random
places
that
they
got
the
info
from
and
it's
like.
Well,
where
do
we?
A
Where
do
we
start
with
that
we'd
like
to
help,
but
it's
kind
of
hard
if
we
can't
point
them
directly
to
one
of
our
yeah
for
sure
anything
else
on
that
before
we
move
on
all
right,
so
now
we're
into
discussions
sandro,
you
want
to
go
ahead.
You
have
a
question
here.
L
A
Yeah
the
documentation
group
talked
about
this
a
little
bit,
but
we
we
don't
really
have
anyone.
That's
that's
volunteered
to
start
putting
that
all
together.
Yet
I
don't
think
I
don't
think
anyone
volunteered
at
the
at
the
last
meeting,
but
yeah.
That's
definitely
something
that
we
want
to
do,
and
I
think
basically,
what
we
talked
about
was-
and
we
talked
about
a
little
bit
in
this
meeting
as
well-
is
create
a
document
and
start
putting
together
like
bullet
points
of
what
are
some
of
the
so
409
is
coming.
A
What
are
some
of
the
benefits
like
we
can
riff
on
the
openshift
official
documentation
and
release
stuff,
and
then
you
know
create
our
own.
That's
you
know
makes
the
case
for
upgrading
to
409.
Basically,
you
know
your.
F
Yeah,
I
just
add
on
that:
I'm
on
the
openshift
4.9
marketing
thread,
so
they're
building
a
blog
post.
You
know,
and
each
of
the
releases
there's
a
thread
and
a
group
meeting
about
what
we're
going
to
publicize
in
4.9.
So
I
kind
of
have
an
early
warning
system
for
what
is
going
to
be
the
official
openshift
stuff,
so
sharing
that
and
then
shape
shifting
that
with
the
docs
team
into
some
sort
of
a
missive
blog
post
or
what,
however,
we
didn't
want
to
do
or
just
yeah.
We
can
do
that
easily.
F
If
I,
if
I
remember
and
then,
if
I'm
not
the
person,
I
can
find
someone
anes
kim
from
red
hat
drives
that
effort.
So
we
can
ask
her
also
to
give
us
a
the
draft
release
before
it
gets
published
and
then
do
a
version
of
it
add
any
fedora
coroses,
yes,
that
we
should.
A
And
we'll
add
that
as
a
task
item
for
the
next
docs
meeting
is
to
actually
start
that
official
effort
for
4.9
releases.
E
Okay,
then,
just
to
add
answer
that
and
based
on
the
previous
conversations
do
we
need
to
go
and
update
the
guides
for
4.9,
so
they
don't
find
out
that
they
out
of
their
information
yeah.
So
I
I
think,
that's
big.
That's
going
to
be
bigger
than
just
the
docs
group,
so
I
think
we
need
to
reach
out
and
ask
for
volunteers
across
all
the
various
platforms,
but
I
think
we
probably
do
need
a
plan
and
do
we
have
christian?
Do
we
have
a
sort
of
an
eta?
E
B
A
F
Yeah
not
thanksgiving
for
you
guys,
yeah.
Let's,
let's
talk
about
it
at
the
docs
meeting
next
tuesday
too
and
see
you
know
who
are
the
original
authors
of
some
of
those
guides
and
reach
out
to
them
as
opposed
to
you
taking
it
all
on.
Maybe
it's
a
simple
thing
to
collaborate
with
them
and
I
will
dig.
E
Up
go
ahead.
Sorry
then,
I
just.
I
also
think
we
need
the
the
variety
of
platforms,
because
not
everybody
has
access
to
all
of
the
underlying
platforms.
I
can
certainly
do
the
overt
and
play
around
with
that
one,
but
I
don't
have
vsphere
access.
I've.
A
Got
vsphere,
so
I
can
do
that
and
there
was
there's
someone
else
who
has
and
we
can
actually
reach
out
to
people
who
we
know
are
using
these,
but
maybe
haven't
written
docs
before
and
we
could
say:
hey
we've
got
this
doc.
That
needs
updating.
The
original
author
is
mia
or
doesn't
have
the
time
you
know.
Would
you
be
interested
in
taking
a
look
at
this
and
see
I'm
thinking,
particularly
of
kai,
for
example?
So
if
I
didn't
have
time
for
upi
vsphere,
the
guy
is
on
it
in
terms
of
upi
vsphere
okd.
A
So
that
would
be
someone
we
could
reach
out
to.
B
If
anybody
has
access
to
bare
metal
machines,
we
have
now
included
all
the
bare
metal
parts
in
the
payload
we
haven't
been.
We
haven't
found
the
time
to
set
up
end-to-end
tests
from
our
side,
but
theoretically
this
should
work
now.
I
don't
think
anybody
has
tested
it
yet,
but
if,
if
anybody
has
access
to
at
least
I
think
you
need
at
least
four
machines,
three
masters
and
a
bootstrap
node,
that
would
be
super
awesome.
If
somebody
could
test
this,
unfortunately,
I
don't
have
access
to
those
machines
either.
B
A
Yeah
we
talked
about
doing
this
before,
but
the
we
just
didn't
have
anyone
to
back.
I
mean
we
talked
about
this
like
months
ago
of
like
basically
generating
a
list
of
who
has
access
to
what
platforms
that
we
just
didn't
have
enough
people
to
to
support
that,
and
if
someone
wants
to
take
that
on,
like
you
good
sir,
that
would
be
fantastic.
M
We
have,
we
have
me
on
openstack,
who
else
just
just
gave
their
names
all
I'll
write
down
right
now,.
B
I
I
don't
want
to
volunteer
myself
right
now,
but
I
did
want
to
put
a
link
down
somewhere.
Maybe
this
is
the
the
right
place
here.
We
do
have
a
pr
open
to
add,
enter
and
test
for
openstack,
and
that's
this
pr
has
been
open
for
a
long
time.
Just
never.
It
just
never
worked,
unfortunately,
so
far.
B
So
if
any,
if,
if
you
get
openstack
to
work-
and
you
could
also
have
a
look
at
this
pr-
maybe
you
see
what's
wrong
with
the
pr
currently
vadim
has
been
doing
an
awesome
job
rebasing
that
from
time
to
time,
I
think
the
last
three
races
a
month
ago
now
already
again,
though
so
yeah
just
if
you
see
anything
if
it
works
for
you
and
you
could
also
have
a
look
at
the
pr
that
would
be
super
awesome.
B
I
mean
it
is
our
release
repository
job
config
stuff,
that's
in
in
the
pr,
so
it
might
not
be
super
clear,
but
did
I
make
the
right
one
so
yeah
just
just
in
case?
If,
if
you
have
the
time
that
might
make
sense,
I
can
it
it's
not
super
clear
because
it
doesn't.
It
just
adds
another
job,
config
and
links
out
to
an
existing
workflow,
so
you
you'll
actually
have
to
look
at
the
workflow.
It's
not
not
at
the
code
that
is
added
in
the
vr.
B
A
Well,
thanks
christian
diane
said
something
here.
I
wanted
to
touch
on
real
quick
diandy
said
we
could
create
an
issue
and
tag
them
with
a
note
to
ask
if
they
need
help.
One
of
the
things
is
mike.
I
don't
think
we
had
an
account
for
every
single
guy
did
like
like.
Basically,
the
guides
got
copied
over,
but
it's
not
like
the
users.
Are
there
in
the
system
to
be
able
to
tag
them
on
there.
C
I
mean
it
looks
like
the
metadata
got
room.
There
was
some
metadata,
some
header
information
we
had
in
the
old
format
that
was
preserving
kind
of
like
who
wrote
it
and
when
the
last
time
it
was
updated,
but
it
looks
like
some
of
that
stuff
probably
got
removed,
probably
because
it
doesn't
fit.
You
know
the
frameworks
we
went
through.
F
Yeah,
I
I
just
think
if
we
can,
you
know,
give
credit
where
credit
is
due
first
of
all,
and
then
we
can
add
them
in
and
some
of
them
may
have
disappeared
off
the
planet.
You
know
and
doing
other
things,
so
that
happens
all
the
time.
But
as
long
as
we
we
have
that
information
in
the
make
docs
version
or
the
the
right
places,
we
could
create
an
issue
tag
them
with
it.
F
With
a
note,
you
know
if
they
that
4.9
is
coming,
do
you
need
help
updating
your
guide,
blah
blah,
blah
and
yeah?
Finding
the
time
is
always
going
to
be
the
hard
thing
and
then,
if
they
say
yes,
they
need
help
or
they
don't
respond
at
all.
Then
we
can
go
in
and
tag
a
few
other
volunteers
from
maybe
from
daniel's
list
yeah.
F
C
I
mean
yeah
that
was
kind
of
the
idea
of
being
able
to
use
like
a
metadata
block
at
the
beginning
of
these
documents
is,
we
could
say,
like
you
know,
who's
worked
on
this.
When
was
the
last
time
it
was
updated.
What
is
the
known
version
that
it
works,
for
you
know
just
to
help
it
bake
a
little
provenance
into
these
documents.
J
E
Can
actually
put,
we
can
actually
put
metadata
blocks
in
comments,
mk.comments
or
markdown
comments.
Sorry,
if
you
want
to
put
that
stuff
back
in
and
that
doesn't
get
rendered,
then.
F
Yeah
that
would
be
great
or
even
render
it
and
then
that
people
get
credit
where
credit
is
due.
We
could
talk
about
that
next
week
in
the
docs
meeting
after
you
all
eat
turkey,
but
I
think
that
might
be
an
excellent
way
of
doing
it,
and
then
any
additional
volunteers
can
pile
on
to
the
issue
that's
created
for
the
next
release
and
that
can
be
part
of
the
release
tasks.
Each
time
a
new
release
comes
out
for.
A
J
A
B
Something
broke
in
that
calendar.
When
I
don't
know,
I
think
jamie.
When
I
added
you
and
I
I
don't,
I
used
to
import
that
calendar
into
google
and
it
doesn't
work
for
me
anymore.
I
don't
know
if
anybody
else's
has
that
problem,
it's
just
that
it
doesn't.
I
L
A
F
Devconf
cz
is
coming
up.
We
have
a
working
group
meeting
and
a
talk
that
were
accepted.
I
know
christian's
going
so
I'm
not
I'm
not
going
to
be
able
to
go
because
of
covet
and
travel
restrictions,
but
so,
if
anyone's
going
and
listening
to
this
video
and
you're
going
to
devconf
and
bruno,
let
us
know
so
that
we
can.
You
know
coalesce
and
figure
out
the
speaking
gig
and
attendee
stuff
and
do
promos
for
that.
F
The
other
thing
that
I
wanted
to
mention
today
is
the
kubecon
call
for
papers
closes
on
december
17th.
I
was
out
and
I'll
nudge,
you
separately
christian
around
the
arm
stuff
and
other
things.
If
anyone
has
something
that
they
want
to
submit,
get
it
in
now.
If
you
need
help,
let
me
know
I'm
happy,
I'm
not
I'm
in
canada
now,
so
I'm
not
eating
turkey
this
week.
F
I
can
help
you
with
that,
but
I
would
love
I'd
love
to
have
some
okd
being,
even
if
it's
not
talking
about
okd,
but
you
do
using
okd
as
the
kubernetes
distro
that
you're
demoing
on
that
would
be
bloody
awesome.
So
some
of
the
ends
and
we
can
figure
out
how
to
get
it,
tweak
it
so
that
it
gets
there.
I'm
also
going
to
be
hosting
an
okd,
no
no
kd
an
openshift
commons,
this
one,
this
hat
gathering
at
kubecon
eu.
F
So
I
am
once
again
looking
for
a
an
okd
end
user
story.
So
if
anybody
knows
of
one
and
one
of
the
things
that
I'm
going
to
try
and
do
on
my
thanksgiving
and
holiday
break
is
is
create
a
list
of
everybody.
I
know
who
has
okd
in
production
and
so
that
we
have
sort
of
a
real
end
users
working
group
for
that.
So
that's
that's
my
quick
and
dirty
on
that.
So
anyone
needs
help
shape-shifting
for
that.
F
Anyone
going
to
bruno
and
anyone
using
okd
in
production
has
a
customer
or
end
user
story
with
a
cool
workload.
Let
me
know,
because
I'm
looking
again.
A
All
righty
any
last-minute
thoughts
we're
right
at
time.
Christian
did
you
find
out
what
field
that
is?
That's
faulty
on
the
calendar.
B
Yeah
I
found
it
out.
I
I'm
just
looking
at
the
source
file
here
and
it
was
the
recurring
I
I
have
to
find
the
name
like
there's
a
field
that
actually
says
that
it's
a
recurring
thing
and
that
is
that
doesn't
work
the
r
rule
frequent.
Maybe
that
is
different.
Now,
though,
I
think.