►
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.
A
A
And
once
twice
all
right,
let's
move
forward
then
with
our
first
item.
So
first
item
is
the
charter
update
and
placement?
Nothing
from
me
on
that.
I
was
working
on
some
of
the
other
texts
actually,
but
that
will
be
coming
soon
actually
and.
B
Okay,
there's
I've
not
actually
done
any
changes
since
last
week,
I'm
not
pushing
any
changes.
I'm
gonna
be
a
bit
busy
this
week,
but
I'm
hoping
to
get
the
site
to
a
point
where,
at
the
next
full
meeting
we
can
having
a
vote
on
to
put
it
live
or
not.
B
Because
there's
been
a
an
issue
raised
on
the
okay,
I
o
gate
and
it
looks
like
the
virtualization
sub
group
have
already
created
their
own
web
presence.
A
Yeah,
I
was
a
little
bit.
I
we
had
talked
at
the
last
main
meeting
about
creating
a
sub
working
group
and
they
just
sort
of
went
and
ran
with
it
on
their
own
and
then
created
a
presence.
A
B
And
and
that's
what
I
was
going
to
say,
because
I
think
we
need
to
be
consistent,
so
we've
obviously
got
the
new
virtualization.
We've
got
this
document,
so
where
do
we?
Where
do
we
want
to
put
our
our
content
and
the
active
topics
that
we're
doing
and
then
I'm
guessing
that
we
may
eventually
create
one
about
the
operators
or
going
forward?
I
mean
to
me
having
fewer
places
is
easier
to
manage
sending
people
off
across
the
web.
I
I
think
just
gets
over
complex
and
then
you
just
don't
know
how
to
update
it.
B
C
I
think
it's
a
git,
wiki
yeah,
I
think
at
the
next
meeting
we
invite
the
vert
people
to
come
to
the
docs
meeting
and
ask
them
to
migrate
into
the
mk
docs.
A
B
A
Right
they
did
say
something
in
the
text
of.
If
you
want
to
join
us,
come
join
us,
but
it
wasn't
very
yeah
I'll
reach
out
to
them
probably
later
today
and
I'll,
basically
outlay.
You
know
hey,
we
want
this
to
be
participatory.
A
Could
you
please
use
our
web
interface?
We've
just
moved
over
to
this.
It's
consistent
as
opposed
to
bouncing
people
around
and
then
I'll
also
give
them
the
list
of
folks
that
had
voiced
interest
at
the
last
meeting
and
I'll
send
something
out
to
the
group
that
will
ping
people
again
diane
go
ahead.
C
Yeah
and
the
other
thing
is,
we
want
to
make
sure
that
they
record
their
meetings
and
upload
them
to
youtube
so
because
that's
our
way
of
capturing
and
being
open
and
transparent
without
having
to
do
huge
amounts
of
meeting
notes
and
things
so
yeah.
If
you
want,
please
do
send
it
out
and
if,
because
I
bet,
they're
a
bunch
of
them
are
red
hat
or
so.
If
you
see
me
on
that,
and
they
give
you
any
guff,
I
think
they
just
want
to
get
it
done.
Then
they
want
to
yeah.
C
The
easiest
thing
in
the
world
is
to
create
a
web
presence.
You
know
and-
and
that's
like
the
first
step,
everybody
tries
to
do
before
anything
else
and
and
that's
just
and
we
haven't
gone
really
public
with
using
mk
docs
and
the
data
set
a
lot,
so
that
probably
was
confusing
in
any
ways
so
yeah
the
sooner
we
get
to
the
mk
docs
and
get
out
of
beta
brian,
that
the
happier
everyone
will
be
as
for
where,
in
the
in
the
hierarchy
of
the
mp
docs
and
the
pages
this
group
lands.
B
What
I
was
going
to
do
is
I
was
going
to
put
it
at
the
bottom
of
the
sort
of
menu
working
groups,
and
then
each
working
group
will
get
their
own
section
and
what
I'm
also
doing
is
thinking
of
putting
a
new
section
on
the
front
page,
which
says
current
working
groups
with
sort
of
fast
links
to
their
their
landing
page.
So
yeah.
A
And
we're
going
to
have
three
basically
because
we'll
have
virtualization
the
operator
subgroup
and
actually
four
crc
subgroup
and
also
the
documentation
subgroup,
so
we've
actually
got
four
subgroups
now
that
are
coming
together.
So
it's
great.
D
C
Hey
there,
of
course,.
C
I
think
that
that
the
real
work
of
the
operators
and
the
operator
framework
and
the
olm
and
all
that
is
happening
in
us,
a
set
in
the
cncf.
Now
I
mean
it's
and.
A
D
Would
it
be
reasonable
that
these
are
all
subgroups
to
the
working
group?
Yes,.
A
D
A
Okay,
anything
else:
brian,
on
okay,
okay,
great
delineation,
of
resources
for
working
group
and
okay
to
users.
That's
my
suggested
text
for
google.
C
I
checked
with
google.
We
have
to
trim
a
few
words
off.
We
can
do
that
so
I'll.
Take
some
of
the
also's
wills
and
things
like
that
out
and
see.
If
I
can
get
it
into
the
I
it
doesn't
give
me
a
number
of
character
account
right.
You
just
gotta,
keep
on
keep
trying,
so
I'm
gonna
clean
it
up
and
I'll
do
that
as
we
speak,
and
then
we
can
look
at
it
and
see
if
it
it
fits.
C
A
A
A
C
A
A
I
just
sort
of
did
it
okay
and
then
yeah
then
for
the
google
group,
diane
you're
gonna
trim
that
down
name
and
scope
of
the
install
that
md
and
readme.md
discussed
at
the
main
meeting
all
were
in
favor
and
again
for
folks
that
were
at
the
main
meeting.
Vadim
just
said
you
know
yeah.
I
think
this
is
a
great
idea.
Just
make
sure
you
link
to
the
the
proper
sections
in
the
main
site
so
that
people
can
get
all
of
this
information.
A
So
basically,
I
think
we're
good
brian
to
start
like
moving
things
over
to
that,
like
you
know,
just
start
separating
things
out
from
install
md
and
readme.md,
and
we
can
point
if
you
want
maybe
a
future
docs
meeting
the
next
stocks
meeting
if
we
can
just
walk
through
through
people
through
where
it
got
put,
so
that
everyone
can
sort
of
know
and
point
folks
to
if
it
isn't
obvious,
does
that
seem
reasonable.
B
Yeah,
so
I
mean
what
I
was
going
to
do
is
I
was
going
to
do
it
create
a
new
readme
for
the
okd
repo
I'll
I'll,
not
do
a
pull
request,
and
so
I'll
probably
show
it
at
the
next
meeting.
Okay,
people
are
happy
I'll,
put
a
link
to
my
my
get
reaper.
Well,
where
it'll
be
so,
people
want
to
actually
go
and
review
it.
They
can
go
review.
B
I
will
have
updated
the
readme
in
the
okd
dot
of
the
ok
main
repo
referencing,
the
beta
site
organization,
and
then
we
can
also
close
the
next
one
just
to
save
time,
because
that
ticket
will
no
longer
be
valid
and
we
can
actually
I'll
make
sure
that
the
new
site
is
fully
inclusive
and
passes
all
the
scans
etc.
B
Apart
from
as
we
go,
live
we've
got
this
complex
set
of
actions
to
do
in
terms
of
disconnecting
the
red
hat
hooks
to
the
current
build
system,
renaming
the
master
to
main
and
then
moving,
obviously
promoting
the
beta
to
the
main
branch
and
then
getting
the
c
name
register
and
the
whoever
our
provider
is
getting
them
to
update
the
the
pointers
to
the
yeah.
A
B
A
Okay,
so
let's
do
here,
tasks.
B
Unhooking,
the
web
hooks
the
point
that
link
into
the
current
red
hat,
build
process
for
okd.io,
there's
a
couple
of
workbooks
in
there
and
I'm
guessing
there's
some
back
end
stuff
to
clean
up
as
well.
We've
then
got
a
rename
master
to
maine
for
the
inclusion,
inclusive
language.
A
Something
broke
here.
That's
me,
I'm
sorry
about
that.
I'm
just
that's
right!
I
can.
I
can
read
through
it.
Okay,
there
we
go
perfect,
inclusive
language,
okay,
so
I
don't
know
if
other
folks
have
had
a
chance
to
look
at
michael's
document.
I
was
looking
at
it
the
other
day
and
to
me
it
has
everything
we
need.
A
A
F
F
A
A
E
A
Okay,
what
do
we
have
so
create
a
build
doc
outline
we're
going
to
hold
off
on
that?
Still
vadim
is
out
for
two
to
three
weeks.
A
He
will
be
back
theoretically
in
october,
at
which
time
the
site
will
have
moved
over
and
so
we'll
be
able
to
to
go
with
this
build
dock
outline
and
so
we're
sort
of
on
hold.
Now
still
with
that
upgrade
path.
Notifications
bruce.
Do
you
want
to
talk
a
little
bit
about
the
conversation
you
had
at
the
main
meeting
with
vadim
about
this
and
what
your
takeaway
was.
D
Well,
no,
I'm
just
going
off
the
the
meeting
minutes
there.
So
so,
basically,
I
had
a
question
for
vadim
on
what
the,
if
the
upgrade
path
did
not
have
success,
but
it
had
s's
and
f's
what
that
was-
and
my
guess
was
totally
wrong.
It
turned
out
that
those
are
just
specific
tests
that
had
succeeded
or
failed,
which
I'd
already
discovered
that
you
could
find
by
clicking
on
them.
You
know
and
go
through
the
pages
upon
pages
of
what
they
were.
D
I
don't
know
it
might
not
hurt
to
document
that,
but
I
I
think
that
that
actually
uncovered
a
bigger
issue,
which
is
that
I
I'm
not
sure
that
we
really
know
who
our
audience.
D
D
One
is
sort
of
hobby
people
and
they
have
different
needs.
Basically,
so
if
you're
wanting
to
use
it
in
production,
then
you
are
concerned
about
stable
streams
that
are
actually
stable
right
and
we've
seen
that
even
the
f-class,
stable
stream
can
wreak
havoc
on
occasion.
D
D
I
I
wouldn't
say
surprised,
but
what
was
you
know?
I
guess
pleasantly
observed
that
it
worked.
D
So
I
I've
gone
to
where
my
underlying
assumption
is
that
it's
not
going
to
work,
and
so,
if
it's
something
that
I
don't
want
to
take
the
time
to
try
and
debug,
then
I
will
skip
the
updates
so
so
and
then
related
to
that.
The
somebody
asked
okay
well
they're,
requesting
the
documentation
and
then
vadim
said
oh
well.
Our
documentation
is
for
4.8
because
that's
the
latest,
which
is
something
that
we
haven't
released.
A
Yeah
and
I
so
I
actually
have
this
actually
dovetails
into
the
new
business
section.
All
right
and
I've
got
a
link
to
that
github
issue.
This
is
issue
882
and
basically
it
started
out
with
redeem.
Vadim
said:
oh
yeah,
so
it's
in
the
latest
release
and
someone
said
well,
I
don't
see
a
4.8
release
and
I
said
well,
he
means
nightlys
and
they
and
then
they
said
well.
Okay,
then
you
should
make
that
clear.
A
I
agree
this.
This
all
sort
of
dovetails
into
the
same
thing
is.
We
need
to
be
more
clear
about.
What's
a
nightly
release,
what
can
it
be
used
for
what's
a
real
release
and
that
one
release
page
with
the
tabs
and
whatnot
that's
available
on
that?
Ci
server
is
nice,
but
if,
if
you're,
a
user
of
okd
or
hoping
to
be
a
user
of
a
okd
navigating
through
all
of
that,
I
think
is
probably
not
the
best
right.
D
Right,
well,
you
notice
that
our
documentation
goes
sort
of
like
one
point
something
and
then
up
through
two
point:
something
and
then
finally,
we
jump
to
kubernetes
and
it
goes
three
point
something
yeah
up
to
like
3.11
and
then
it's
latest.
D
Like
we
have
gone
through
documentation
for
all
those
things,
but
we
sort
of
never
separated
the
documentation
by
version
right
and
again,
I
think
that's
the
underlying
assumption
of
production
versus
latest
and
greatest
versus
development,
and
maybe
it
all
tracks
back
to
resources.
Okay,
but
I
think
we're
just
it's
just
sort
of
all
into
one
big
mush
without
clearly
delineating
the
different
stakeholders.
C
C
Ask
a
question
of
michael
burke:
I
think
a
few
meetings
back.
We
asked
if
you
could
generate
the
interim
four-point
releases
so
that
we
didn't
have
the
latest.
What
was
the
status
on
on
that?
Getting
that
done.
A
So
let's
take
this
back
to
the
main
group
meeting,
but
my
senses
were
probably
going
to
want
to
go
4.6
and
up
right
and
and
latest
can't
be
4.8
because
it
isn't
actually
our
latest.
So
I'm
I'm
hoping
that
there's
a
way
to
tweak
that
pull
down
to
make
it
clearer.
That
latest
is
4.7,
and
maybe
we
follow
sort
of
an
f
cost
model
that
4.8,
which
we
can't
release
yet
is
considered
next
stream
like
an
f
cos
or
something
like
that
or
or
we
give
it
a
name
that
indicates
it's
on
its
way
right.
C
A
B
A
That's
the
thing
is
so
what
so,
because
there's
one
channel,
basically
for
all
of
the
the
minor
releases,
it's
always
been
that
we
sort
of
have
our
own
release
schedule,
and
this
is
confusing,
because
actually,
someone
asked
a
question
the
other
day
about
that
new
security
bolton
that
came
out
the
other
day
and
they
wanted
to
know
what
ocp
is
addressing.
This
is
fcos
or
is
okd
addressing
this,
and
we
we
actually
don't
have
any
information
about
our
addressing
of
security
concerns
on
anywhere
on
our
website.
A
So
anyone
that
wanted
to
use
okd
for
production,
they
wouldn't
know
like
okay.
This
is
we
are
incorporating
updates
that
fix
this
and
whatnot,
and
this
incorporates
such
and
such
bug
fixes
and
whatever
we
aren't
beholden
to
them,
because
we
are
built
off
of
f
costs
and
because
there's
that
that
underlying
issue,
that's
preventing
us
from
doing
or
eight,
we
won't
be
doing
four,
eight
at
least
for
like
another
month
or
something
like
that.
At
least
so
I
mean
like.
B
An
official
release
I
mean,
I
think
the
question
comes:
are
we
going
to
skip
photo?
I
can
go
straight
for
9
or
but,
and
I
I
also
think
from
a
documentation
point
of
view,
not
just
okie
d
releases,
but
also
the
documentation
releases.
Are
we
tied
in
with
openshift
ocp
on
the
dock
site,
or
could
we
actually
have
different
versions
under
okd
than
ocp
has
yeah.
A
D
Right
like
we
do
use
that
same
numbering,
and
even
if
you,
even
if
you're
getting
a
beta
version,
it's
some
number.
You
know
four,
eight
four
nine
vadim
started
talking
about
410,
so
it
seems
like
it
would
be
handy
to
have
documentation
that
is
tracking
whatever
you
know,
ocp
is
doing,
which
is
the
basis
for
hours.
A
C
A
A
C
C
So
I'm
not
sure
what
the
group
is
landing
on
here.
It
sounds
like
we
ought
to
have
some.
I
wanna
I
hate
to
keep
creating
readme.md
pages
and
things
like
that,
but
like
some
notation
about
how
this
scenario
plays
out
like
a
short
write-up
on
that
and
where
to
go
to
get
more
information
because
we
are
reliant
on
the
ocp
patches,
there
is
a
what's
new
section
in
the.
A
Semantically,
I
think
what
is
so,
what
is
under
the
what's
new
section
now
in
the
beta
site?
A
Let
me
go
to
that
link
again.
I
always
have
to
look
for
the
link
because
for
some
reason
it
I
don't
have
it
memorized
yet
so.
A
It's
in
the
chat:
okay,
can
you
put
it
in
the
meeting
docs
so
that
it
always
gets
copied
when
I
copy
over
the
meeting
docs?
For
some
reason,
the
news
site?
Okay,
so
okay,
so
this
is
the
old
right.
So
this
is
the
new
features.
A
This
is
basically
version
diversion
stuff
right,
so
this
is
basically
like,
what's
different
between
in
here.
Let's
share,
let
me
share
my
screens
see
this.
This
is
basically
stuff
like
what's
new
from
version
four
five
to
four
six
and
stuff
like
that,
I
think,
or
is
this
like
four
versus
three
four
versus
three
yeah.
A
Maybe
you
don't
know
the
history
but
sort
of
how
we
ended
up
moving
away
from
like
okd
individual
sort
of
you
know,
4.6,
4.7,
etc,
etc,
so
that
it
just
like,
because
one
of
the
things
that
someone
asked,
I
guess
I
should
rephrase
this
one
of
the
things
that
someone
asked
is
that
you
know
there
is
no
4.6
4.7
individual
documentation,
and
if
we
go
here
to
documentation,
it's
not
in
the
pull
down,
and
you
said
you
can
add
it
and
generate
it.
F
A
C
C
Yeah,
michael,
I
don't,
I
think
it's
probably
more
on
me
not
insisting
on
it
and
not
realizing
the
implications
back
back
way
back
when
and
for
that
and
just
being
grateful
to
get
any
documentation
auto
generated
at
that
moment
in
time.
B
C
I'm
sure
it
wasn't
laziness
or
not
wanting
to.
I
think
it
was
just
me
not
knowing
exactly
what
to
request,
and
then
you
know
until
now
nobody's
really
asking
about
it.
D
It
it
was
about
a
year
before
between
the
time
that
ocp
came
out
and
we
actually
got
a
release
version
of
okd
yeah
and
what
was
our?
Was
it
4.5
or
point?
Four
I'd?
You
know,
I
don't.
A
Okay,
because
one
thing
that's
always
kind
of
annoyed
me
is,
if
I
do
a
a
web
search
for
a
particular
topic,
I'll
get
the
link
for
like
4.3
of
ocp,
you
know
or
4.1,
and
then
you
get
that
big
red
text
that
says
you
know
this
is
not
the
most
current
documentation
for
some
reason.
That
annoys
me:
well,
I
think
only
because
it
ends
up
being
rising
to
the
top
in
terms
of
web
searches.
So
that's
that's.
B
C
F
C
C
Yeah,
I
think
it's
a
redirect
so,
but
it's
still
going
to
be
generated
and
going
to
be
publicly
available.
It's
not
going
to
be
behind
a
firewall.
So
as
long
as
ours
keeps
going
to
doc
from
the
same
batch,
the
output
goes
to
docs.okd.io.
I
don't
think
that
does
anything
to
us.
A
F
A
And
so
what
is
this?
Can
you
find
out
what
the
impact
will
be
on
this
auto
generation
between
whatever
the
new
system
will
be
and
okd
we're
going
to
want
to
find
that.
F
C
A
B
B
A
A
Theory,
michael:
what
are
your
thoughts
on
that
as
the
documentation
expert
that
seem,
legit
have
three
three
x
and
four
x
but
drop
the
two
and
the
one.
B
C
A
So
there's
that
we
talked
about
that
and
noting
release
version
in
the
docs
we'll
also
want
to
figure
out
a
page
that
better
describes
nightly.
A
So
this
is
something
that
we're
gonna
have
to
write
ourselves
or
have
vadim
right
or
something
like
that
and
incorporate
it
into
the
website,
and
so
that
should
explain
the
nightly's
process
and
that
you
know
nightlys
are,
you
know,
pruned
after
72
hours
and
basically
better
explain
nightly
so
that
people
understand
what
they
are
really
you
know,
and
so,
if
someone
wants
to
take
on
that
task,
that
would
be
helpful.
A
I
I
think
we
need
to
recruit
a
couple
more
docs
group
people,
maybe
we'll
send
something
out
and
say
something
at
the
main
meeting
and
I'll
send
something
out
over
the
email
list.
If
we
could
have
one
more
person
to
volunteer
time
for
docs,
so
particularly
docs
that
we
need
written
new
docs,
that
would
be
helpful.
B
A
Right,
that's
right
because
there
were
supposed
to
be.
There
was
this
horde
of
new
red
hat
employees
that
were
like
they
were
supposed
to,
like.
You
know,
basically
start
out
here
to
to
get
their
way.
I'd
be
tempered
right
either
they
ran
off,
or
they
did
so
well
that
they've
moved
on
to
the
ocp
stuff.
A
I
don't
know
okay,
so
let's
put
that
as
a
task
item
I'll,
take
care
of
that
I'll
reach
out
to
the
people
that
used
to
be
here
and
then
we'll
also
send
I'll
send
something
out
over
the
mailing
list.
The
google
group
to
try
to
round
up
more
people
for
the
docs
stuff.
We
could
have
one
more
person
who
actually
writes
new
docs.
That
would
be
fantastic,
so
this
one
came
up.
A
That's
interesting
is
that
change
logs
are
missing,
and
so,
if
you
were
to
go
to,
I
need
to
share
my
screen
again.
A
Okay,
so
change
logs
are
missing.
So
if
we
were
to
go
here-
and
you
know,
these
are
the
index
of
releases,
if
you
go
to
four
seven
stable,
even
the
one
from
the
other
day,
you
get
this
error
and
says
could
not
load,
and
this
is
vadim's
repo
right
and
the
funny
thing
is:
if
you
go
to
vadim's
repo.
A
There's
like
no
commits
here
beyond,
like
february
17th,
so
I'm
I'm
confused
as
to
what's
happening
and
vadim
is
off
for
a
couple
weeks.
A
Yeah,
it's
kind
of
hard
to
tell
which
one
it
would
be.
Is
it
for
four
seven,
our
back
v1
devel?
A
Okay,
well
so
yeah
I
mean
I
was
not
able
to
find
it
when
I
searched
for
it.
So
this
is
an
issue
for
all
builds.
We
won't
be
able
to
do
anything
about
it
until
vadim
gets
back,
but
if
you
hear
anyone
mention
this,
it
does
stop
at.
I
think
it's
3
25
yeah
is
the
first
one
where
it
fails
february.
14Th
works
so
everything
after
february
14th
fails
I'm
assuming
it's
not
the
branch
related,
because
these
are
all
the
same
branches.
Basically,
it's
all
off
the
same
branch.
A
I
think
that
gets
sent
to
ci
so
we'll
have
to
find
that
out
sort
of
what
the
deal
is
with
that
the
other
one
that
came
up
is
related
to,
and
I
hadn't
visited
this
in
years.
A
The
red
hat
virtualization
and
those
failed
there
is
a
ticket
that
was
opened
for
openshift
docs,
michael
at
three,
six,
six,
one,
seven
that
someone
opened
up,
and
so
we
will
want
to
fix
this.
Apparently,
the
issue
is
that
the
its
particular
release
versions
are
accessible,
but
not
just
like
release
four
or
version
four
or
anything
like
that
like
here,
it's
released
for
and
apparently
that
will
fail
now
it
might
have
in
the
past,
and
it
actually
needs
to
reference
the
minor
version.
A
A
I
think
that
this
is
problematic
for
a
couple
reasons:
let's
have
this
discussion
at
the
main
meeting.
Let's
put
let's
earmark
this
for
the
main
meeting,
because
ultimately
this
is
also
a
technical
discussion,
particularly
as
we
start
talking
about
cuvvert
and
stuff
like
that,
and-
and
actually
I
notice
actually
that
sandro
chimed
in
on
this
conversation.
A
So
let's
bookmark
this
for
the
main
meeting
I'll
put
that
as
an
agenda
item,
I
think
that's
a
great
question
brian
and
something
that
we
we
definitely
should
resolve.
Particularly
if
we're
talking
about
this.
This
shift-
and
I
thought
I
am.
A
All
right,
so,
yes,
we
will
earmark
that
for
the
next
main
meeting,
I
think
that'll
be
a
great
conversation
and
we
can
get.
You
know
sandro
and
other
folks
involved
in
that
as
well
and
I'll
mention
that
this
is
the
other
one
that
we
had
here.
There
was
one
more
oh
yeah,
so
diane
did
get
us
another
office
hours
during
coupon,
north
america.
This
is
gonna,
be
another
live
stream,
so
10
13,
2
2,
30
pst,
which
is
you
know,
5
to
5,
30,
eastern
and
well.
A
I
don't
think
we've
picked
a
topic
yet
or
if
we'll
just
riff,
on
questions
that
we
get.
Does
anyone
in
this
group
have
any
suggestions
for
like
a
an
area
of
focus
or
anything
like
that?
There
was
mention
that
the
arm
version
may
be
available
by
that
time,
but
there's
no
guarantees.
So
that
might
be
something
that
we
put
a
riff
on,
but
but
invasion
of
walks.
A
So
the
armed
version
of
open
shift
and
by
proxy
okay
d.
Is
that
because
I'm
guessing.
A
He
will
now
how
fast
he
does
that
I
don't
know-
and
this
is
so
this
is
going
to
be
brought
up
at
the
maybe
I'll-
bring
it
up
here,
because
it
should
come
up
at
the
main
meeting,
I'm
going
to
propose
at
the
next
main
meeting
that
we
get
multiple
working
group
people
ci
access
to
do
builds
so
that
vadim
is
not
the
only
point
person
for
okd.
A
I
realize
it's
his
baby
and-
and
maybe
the
the
larger
group
will
disagree
with
madness,
but
I'm
going
to
propose
that
we
at
least
have
one
other
person
or
ideally
two
other
people
that
are
point.
People
for
building
okd
so
like,
for
example,
he's
gone,
but
he
said
he
would
still
do
the
builds
the
next
two
weeks
or
three
weeks
since
it's
automated
and
nominally.
Does
it
that's
cool
but
like
what
if
vadim
wins
the
lotta
lottery,
or
you
know
you
know
I
and
it's
just.
A
B
A
At
the
minute,
if
there
is
some
red
hat
resources,
which
is
the
ci,
is
a
red
hat
ci
that
uses
centos.
B
A
B
D
Yeah,
I
agree
with
you
jimmy
one
of
the
things
that
keeps
coming
up
is
being
able
to
build
okd
from
scratch
outside
of
the
red
hat
environment,
and
the
sticking
point
often
seems
to
be
the
machine
config
operator
according
to
vadim.
D
So
that's
that's
been
long-standing,
I
guess
ask
and
that
sort
of
relates
to
what
you're
doing,
even
if
like,
if
people
could
build
it
themselves,
then
you'd
have
sort
of
more
survivability.
A
Right
right-
and
I
did
play
with
the
idea
of
setting
up
a
ci-
for
I
probably
will
in
the
next
week
or
so,
because
we've
been
getting
a
lot
of
questions
on
single
node
okd,
and
it
seems
to
me
that
single
node,
a
ci
that
tests
single
node,
would
be
a
really
great
idea,
because
we
kind
of
got
caught
with
our
pants
down.
A
B
I
just
actually
think
we
need
to
actually
review
the
whole
point
of
automation
and
testing,
because
obviously,
we've
got
the
crc
group
as
well,
and
we
we
need
to
automate
that
and,
and
then
several
times
vadim
is
sort
of
alluded
to.
A
lot
of
the
instability
is
because
we
don't
have
sufficient
test
capability
within
the
current
process.
D
B
A
But
the
installer
version
does
it
didn't
work
for
someone
the
other
day
and
but
I
was
able
to
get
it
to
work.
So
I
don't.
I
don't
know
that
might
have
been
a
configuration
issue
on
there
and
this
was
in
aws
ipi
right.
B
I
think
we
need
brian
and
then
bruce
yeah.
As
you
can
see,
we
need
to
put
this
on
the
the
agenda
for
the
next
full
meeting,
because
obviously
there's
documentation
to
be
done,
then
there's
the
whole
ci
infrastructure
question
and
getting
more
people
support,
but
also
extending
it
with
the
new
use
cases
and
then
potentially,
we
need
to
get
vadim's
gate
repo
into
somewhere
a
bit
more
official.
A
Agreed
so
I
will
add
that
to
the
agenda
for
the
next
meeting,
I
think
that's
very
important
in
terms
of
survivability
of
of
the
project
and
also
you
know,
being
able
to
publicize
the
the
project
and
and
being
able
to
have
confidence
that
when
we
say
to
people
that
something
works,
a
relative
level,
a
relatively
high
level
of
confidence
that
something
does
work
like
single
note,
installs
or
you
know,
or
whatever
right
so,
okay,
that
will
go
on
the
next
agenda
for
sure
we
mentioned
the
okd
office
hour,
here's
the
sig
stuff.
A
So,
as
we
talked
about,
I
will
email
them
and
ask
them
to
move
their
stuff
into
the
web.
So
brian
I'll
cc
you
and
I'll
also
cc
diane.
On
that,
just
to
say,
hey,
you
know
we
have
this
new
web
system.
We'd
prefer
that
it
stayed
within
this,
and
also
here
are
the
working
group
members
and
hopefully
that
that
will
just
go
smoothly
and
then
brian
you
can
show
them
next
step.
Yes,.
B
A
A
You
know
a
year
and
a
half
ago
or
whatever
it
was
or
a
year
ago
we
needed
twitter
because
so
much
so
much
promotion
is
done
on
twitter
and
when
we
get
a
new
release,
no
one
really
knows
about
it
because
we're
not
like
oh
okay
d,
you
know,
4.7,
you
know,
september
21st
version
came
out
check
it
out
new
features,
bug
fixes.
We
don't
do
anything
like
that.
A
We
don't
promote
ourselves
and
I
feel
like
that's
something
that
would
be
really
beneficial
to
people
to
us,
increasing
adoption
and
also
getting
people
using
it
so
that
it
gets
tested
and
it
gets
improved
as
well.
So
anyone
have
any.
A
Yeah,
which
never
includes
any
okd
stuff,
never
has
never.
I
predict
never
will
right,
because
they
have
that
sort
of
interest
in
heavy
openshift.
So
we'll
have
to
ask
diane,
but
I'm
sure
there's
some
sort
of
branding
type
thing
you
know,
but
if
we
could
just
do
like
okd
kubernetes
or
something
like
that,
like
you
know,
and
just
get
a
one
of
the
newbies
or
something
or
a
couple
newbies
or
some
of
us
just
to
staff
it
right
and
to
send
stuff
out.
I
think
that
would
be
really
really
awesome.
D
Yeah,
I
think
that's
a
good
idea
if
you
could,
if
you
could
also
get
which
I
know
diane,
I
think
has
been
working
on
if
you
could
also
get
some
of
the.
D
All
the
the
the
people
are
doing
openshift
demos,
if,
if
maybe
a
tenth
of
them,
would
be
on
okd.
That
would
probably
be
helpful
too
right.
Yeah
yeah,
like
have
edison,
do
an
okd
demo.
A
Okay,
I
think
that's
the
agenda.
We
have
like
30
seconds
left,
so
let's
go
ahead
and
call
it
see
you
all
everyone
here,
except
for
michael,
is
at
the
main
meeting.
B
A
I
think
yes,
anyone
have
a
disagreement
with
that.
Anyone
think
it
would
be
a
bad
idea
to
have
an
okd
facebook.
A
Right,
that's
that's
absolutely
and
that's
where
the
the
the
newbies
come
in
and
and
us
seasoned
professionals
who
have
some
social
media
experience
and
we
can
also
automate
some
stuff
right.
So
if
there's
a
a
post
that
goes
to,
if
there's
a
commit,
you
can
do
things
where,
like
a
commit
made
to
a
repo,
then
calls
the
twitter
api
to
make
a
twitter
post.
A
That
you
know
has
that
information.
So
we
could
look
at
doing
that
as
well
to
a
spam
feed
because
of
that
they're
going
to
leave
sure
absolutely
yeah
yeah
all
right!
Well,
let's
go
ahead
and
stop
it
there
and
thank
you
diane
for
offering
us
this
this
great
conversational
opportunity
to
make
okd
better.
C
All
right
perfect,
I
will
stop
the
recording
jamie.
If
you
have
a
few
more
minutes,
I
just
want
to
catch
up
and
then
we'll
go
on
from
there.