►
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
All
right
and
welcome
to
the
okd
working
group,
documentation,
subgroup
meeting
for
june
28th
of
the
year
2022
and
the
agenda
has
been
shared
in
the
chat
and
now
we
can
look
at
the
agenda
and
see
if
there's
anything
folks
want
to
change
your
ad
real,
quick
I'll.
Give
you
30
seconds
to
do
that,
scan
it
over
and
see.
If
there's.
A
All
right
looks
good
all
right,
then,
let's
get
started
with
technical
documentation.
A
Just
for
my
part,
I
did
reach
out
to
jack,
sent
an
email
and
waiting
to
hear
back
on
cern,
seeing
if
they'll,
if
jack
will
write
like
a
little
write-up
for
us,
either
blog
post
or
something
we
can
put
somewhere,
and
I
also
in
chat
reached
out
to
glenn
marcy
who's,
an
okd
user
who's,
doing
single
node
and
so.
A
C
So
I'm
working
through
a
number
of
threads.
I
actually
had
quite
a
good
discussion
with
christian
in
dublin
about
how
to
improve
the
documentation.
I
mean
one
of
the
biggest
challenges
we've
got
is
the
prowl
and
the
work
that
it
does
sort
of
under
the
covers
when
it
does
build,
and
for
me
one
of
the
biggest
challenges
is
the
image
replacing.
C
And
one
thing
I'd
be
interested
in
is:
can
we
get
this
source,
the
dockerfile
of
the
container
file
that
makes
up
the
time
but
also,
more
importantly,
the
build
image
that
is
substituted
in
prowl?
It
must
be
in
a
repo
somewhere.
C
I
don't
know
whether
it's
in
public
domain
or
whether
it's
sort
of
within
the
red
hat
firewall,
but
I
had
to
chat
with
christian
and
want
to
try
and
see
if
we
can
do
that,
because
if
we
have
the
source
of
truth
for
the
images,
then
it
helps
people
understand
what's
going
on
because
at
the
minute
that's
a
bit
of
a
sort
of
a
closed
box
area.
So
that's
one
area,
I'm
looking
at.
C
C
C
Once
we
understand
what
the
build
and
the
runtime
containers
need
to
look
like,
there's
no
reason
why
we
can't
go
and
create
an
okay.
The
community
catalog
build.
A
C
From
and
that
that
means,
I
think
that
unlocks
then
okd
as
a
useful
tool
in
a
lot
of
other
scenarios,
because
at
the
minute
you
can't
follow
the
same
steps
for
ocp
to
set
okd
up,
because
there's
so
much
missing
from
that
catalog.
C
Everyone
everything
says
I'll,
go
and
put
the
storage
operator
on
go
put
the
githubs
or
the
pipelines
operator
on
and
they're
just
not
there
for
us,
so
I
think
having
that
catalog
would
bring
us
much
closer
to
parity,
so
anybody
who
sees
ocp
instructions
should
be
able
to
follow
them
on
okd
and
to
try
and
get
around
so
I've
also
been
looking
at.
What
does
that
involve
and
how
complex
would
it
be?
So
again,
I
think
a
good
idea
would
be
if
we
can
create
a
a
workshop
day.
C
B
We
could
also
reach
out
to
the
operator
framework
community
and
ask
them
but
to
participate
in
that
hackathon
day,
because
they're
they're
trying
to
do
more
outreach
as
well
they're,
now
tncf
incubated
project,
but
most
of
them
are
red.
Hatters
austin
mcdonald.
Is
the
community
lead
for
that
sort
of
the
christian
lombeck
of
their
side?
B
Well,
he
might
be
someone
if
we,
if
you
really
want
to
do
this,
and
I
and
I
think
it's
time
we
we've
been
waiting
a
very
long
time
for
red
engineers
to
free
up
some
resources
and
it
just
doesn't
feel
like
it's.
It's
moving
so
yeah,
it's
not
a
bad
sub
project
to
take
on.
So
we
had
also
talked
about
doing
a
hackathon
on
the
centos
stream
project
as
well.
So
you
know
we
can.
We
can
do
a
series
of
them,
I'm
happy
to
host
them
and.
C
C
I
I
think,
it'd
be
quite
a
good
idea,
because
I
mean
I
it'll
also
help
us
build
up
the
community,
because
I
think
some
people
are
are
a
bit
wary
on
taking
on
a
role
a
responsibility
by
themselves,
but
would
be
quite
happy
to
join
a
community
effort
yeah.
I
think
so.
I
I
think,
having
a
quarterly
hack
day
or
something
like
that
would
be
a
good
way
just
to
move
the
computer,
the
community
forward
or
something
just
something
to.
B
I
think
that
will
do
that
jamie.
What
do
you
think
I
mean
you're
nodding,
but
that's.
A
D
C
Well,
it's
it's
actually
not
what
it
pulls
in
it's
it's
during
the
build
of
the
catalogue,
because
okd
only
has
a
single
catalog
installed,
which
is
the
community
catalog
at
the
minute.
We
we
actually
don't
they're
disabled,
so
we'd
need
to
actually
go
and
build
a
new
and
install
a
new
catalog,
which
I
suggest
you
call
the
okd
community
catalog,
which
would
then
contain
what's
in
the
red
hat
catalog.
C
But
I
also
know
that
when
red
hat
builds,
the
community
catalog
it's
built
for
ocp,
it's
not
built
for
okd
and
some
of
the
links
go
back
to
red
hat
marketplace.
Some
of
the
links
go
into
the
red
hat
catalog
and
I
think
that's
what
I
think.
That's
what
you're
talking
about
why
some
things
suddenly
disappear
from
that
catalog,
and
so
I
haven't.
B
D
Okay,
but
it
seems
it
seems
to
it's
not
related
to
an
update.
You
know
if
you
keep
your
system
stable,
the
catalog
will
change
from
time
to
time.
So
it
looks
like
everything
is
periodically
updated.
Yeah.
C
D
Right
yeah,
because
and
sometimes
even
if
it's
an
operator
that
you
recognize
it's
a
very
old
version
of
it,.
C
So
I
don't
think,
there's
anything
magical
about
why
the
operator
hub
would
hide
the
catalog.
That's
an
operator,
that's
in
the
catalog,
but
again
I'm
I'm.
I'm
learning
this
and
trying
to
pick
up
all
the
sort
of
subtleties.
I
know
the
basics,
but
I'm
trying
to
work
out
but
I've
yet
to
find
out
which
repo
builds
the
community
catalog
and
fully
understand
that.
But
so
I
I
think
it's
probably
something
we
want
to
take
to
the
main
meeting.
C
A
Okay,
so
it
sounds
like
what
we're
saying
is
then,
let's
schedule,
let's
pick
a
date,
we
can
do
that
async,
we'll
pick
a
date
one
well,
what
we'll
probably
have
to
do
is
first
off
decide
a
guest
list
right
who
do
we
want
to
invite
from
the
respective
teams
then
do
a
poll
to
find
out
the
date
that
will
work
best
to
get
those
people
in
the
room,
because
we
want
to
make
sure
that
we
don't
have
an
event
where
a
lot
of
members
of
the
public
show
up,
but
we
don't
actually
have
the
people
who
are
knowledgeable
at
that
event.
C
C
We
can
do
a
a
quick
tutorial
explaining
how
olm
works
and
and
demonstrate
it
with
a
couple
of
examples
to
actually
kick
off,
because
I'm
not
sure
if
we
say
it's
a
three-hour
workshop,
I'm
not
sure
how
much
will
get
done,
but
I'm
hoping
that
would
be
an
event
where
someone
will
say.
Oh
I'm
going
to
go
and
try
do
the
dev
work,
work,
space
or
the
I
want
to
go
and
try
and
do
the
text
on
operator.
C
I
want
to
go
and
try
and
do
the
argo
operator
so
we'll
get
people
that
we
kick
them
off
with
the
activity
and
then
we're
going
to
see
an
onwards
momentum
and
maybe
create
a
slap
channel
or
some
way
of
actually
continuing
the
work
and
the
discussion
after
the
event,
because
I
say
with
a
three
hour:
if
you've
never
done
any
operator
stuff
within
three
hours,
you're
you're
not
really
going
to
get
much
done.
So
I'm
hoping
these
are
going
to
be
sort
of
seeding
activities
where
we
sort
of
educate
spend
the
first
hour.
C
Educating
people
give
them
a
few
examples
in
a
repo
that
we
can
walk
through
and
explain,
and
then
maybe
we
can
do
a
partial
one
on
the
day
I'll,
maybe
get
two
or
three
people
to
to
host
a
a
one
on
a
on
a
specific
operator
and
then
continue.
C
So
I'm
almost
think
we've
got
a
seed,
as
you
say,
seed
event
with
two
or
three
people
that
can
that
have
actually
done.
It
worked
out
how
it
all
works
and
then
help
anybody
else.
It
turns
up
if
we
can
get
the
red
hat
people
that
are
doing
this
on
ocp
to
be
part
of
the
hack
even
better,
because
that
means
they
may
be
able
to
take
their
operator
and
do
it
on
the
day
in
three
hours
and
we
get
stuff
for
free.
C
But
if
it's
just
a
public
event,
I
think
we
have
to
make
sure
that
there's
one
or
two
of
us
that
have
actually
gone
through
the
pain
of
working
out.
How
olm
works,
how
you
create
a
catalog,
how
you
create
the
operator
bundles
to
populate
the
catalog
and
then
how
you
can
actually
test
it
all
works
out.
A
C
C
So
I
don't
think
it
say
we
have
a
three
hour
event
if
someone's
not
familiar
with
operators
and
operate
the
hub,
an
olm,
I
don't
think
they're
going
to
be
very
productive
in
three
hours,
so
I'm
hoping
that
we
can
use
the
event
almost
like
as
an
education
session
to
get
them
started
to
see
some
work
going
on.
C
And
then
we
need
to
maybe
look
at
a
social
media
channel
where
we
can
actually
try
and
encourage
the
group
to
keep
working
after
the
event
and
use
it
as
like
a
seating
event
to
get
some
work
done.
B
C
B
The
the
operator
framework
people
just
came
to
me
austin,
I
talked
to
him
every
friday
and
they're
trying
they
were
thinking
about
doing
an
operator
con
at
kubecon,
north
america.
In
detroit
they
haven't
yeah,
but
they
are
looking
to
do
more
much
more
outreach.
B
So
we
may
be
able
to
get
someone
to
do
a
short
talk
on
olm
and-
and
so
that's
why
I'm
was
thinking
throwing
austin
asking
maybe
austin
to
come
to
the
next
docs
meeting
and
and
once
you've
done
your
exploration
hook
you
up
with
him
and
we
can
figure
out
how
to
make
it
an
operator
framework,
slash,
okd,
joint
hackathon
thing,
yeah
yeah
bring
the
two
communities
together
and
work
on
something
so
yeah.
There's.
C
So
I
don't
know
if
there's
anyone
there
that
particularly
knows
like
newbar,
because
I
think
I
think
that
needs
object
store
as
a
dependency
to
get
that
working.
Okay.
So
again,
if
there's
anybody
that
that
knows
nubar-
and
I
don't-
I
think
you
can
do
nubo
without
rook
and
seth.
B
A
new
but
nobody,
that's
the
yeah,
that's
nuba,
n-o-o-v-a
yeah.
C
Yeah
but
that's
the
object,
store
piece
that
gives
you
like:
s3
object:
storage
on
on
a
cluster
yeah,
so
I'm
I'm
just
thinking
if
we
can,
if
we
can
actually
target
because
I
mean
I
think
that
the
people
we
want,
we
want
I'm
being
selfish.
I
want
a
development
environment,
so
I
want
gt,
I
want
object
store.
I
want
git
ops,
I
want
pipelines
and
I
want
to
registry,
which
is
key.
B
Yeah
so
figure
out
by
the
next
docs
team
meeting
or
whatever
you
want
and
which
ones
you
can
be.
You
can
curate,
which
ones
we
work
on.
If
you're
going
to
move
this
forward
move
the
needle
forward,
you
curate
the
ones
that
we
hack
on
and
I
will
try
and
find
the
owners
of
those
guys
for
you
to
work
with
and
maybe
deal
if
we
do
something
a
little
bit
longer
like
we
introduce
it
with
yeah.
A
B
C
A
Okay,
great:
let's
move
on
to
our
next
topic,
which
is
repository,
move
and
timeline
and
brian,
do
you
have
any
updates
on
that.
C
C
B
Yeah,
so
will
gordon
is
the
person
and
I'm
going
to
send
an
email
and
cc.
Well,
I'm
going
to
him
and
brian
and
jamie
ryan,
innis
and
I'll.
Do
that
right
now
and
give
them
the
link,
and
if
it's
not
will
gordon
there
will
be
somebody
else
he
he'll,
he
will
know
who
can
do
it
so
well
I'll,
keep
talking
everybody
and
I'll
just
send
an
email,
diane.
A
C
C
And
obviously,
all
of
the
any
documentation
I
can.
I
can
do
the
the
main
doc
site
and
and
push
all
the
changes
to
there,
but
it
again
we
probably
need
to
be
in
the
google
groups,
the
slack
and
then
maybe
the
twitter.
We
need
to
arrange
that.
A
Probably
do
a
heads
up
like
not
just
mention
it
when
we
do
it,
but
actually
mention
it
ahead
of
time.
Hey,
we
are
going
to
be
doing.
C
C
I
I
mean
again
it'd
be
worth
just
checking
with
christian.
Is
that
going
to
break?
I
don't
think
that's
used
for
anything
in
terms
of
the
install
releases
or
anything
like
that.
That's
all!
That's
all
elsewhere.
So
I
think
it's
just
going
to
be
the
the
two
gate
repos
and
the
okay
lego.
I
o
site.
That's
all
it'll
really
impact,
but
as
soon
as
we
got
the
red
hat
is
lined
up.
I
think
we're
ready
to
go
just
just.
A
All
right,
so
I
would
say
brian
put
a
note
in
that
thread,
saying
that
diana's
is
reaching
out
to
will
gordon.
B
Bill,
gordon
and
the
other
gentleman
is
jerry,
jerry
fala
and
I'm
just
sending
out
jerry's
in
the
czech
republic.
So
okay
and
I'm
sending
him
the
link
so.
A
All
right
moving
on
to
the
next
item,
because
this
one's
pretty
straightforward
is
depersonalizing
the
home
lab
documentation
I
reached
out
to
vadim
and
he
he
is
totally
on
board
and
actually
sri
just
responded
to
me
a
few
minutes
ago
and
he
is
on
board.
A
So
we
can
move
both
of
these
to
blog
posts
and
maybe
put
a
tag
like
you
know,
home
lab
examples
or
just
home
labs
or
something,
and
this
will
give
people
an
opportunity
to
share
their
home
lab
setups
and
not
get
it
confused
with
a
guide
which
is
an
actual
step-by-step.
A
And
then
we
can
promote
these
items
as
home,
layup
examples
or
something
on
the
twitter
in
the
chat
and
stuff.
Like
just
say,
hey,
look,
there's
some
hotline
examples.
Okay,.
C
A
A
As
my
oct
guide,
you
know
doing
vsphere
upi
someone
put
a
merge
request
actually
or
an
issue
on
the
repo
the
other
day,
so
someone
people
are
actually
using
my
repo,
I
don't
know
if
they're
following
the
instructions
or
not
that
would
if
I
can
clean
that
up
a
little
bit
and
test
it
again,
then
I
would
say
that
would
be
one
guide
so
installing
upi
on
vsphere,
I
thought
we
had
more.
A
C
Again,
I
think
we
need
to
work
out
what
we,
what
we
mean
by
a
guide
and
actually
have
some
form
of
standardization,
of
what
a
guide
is,
because
there
are
some
which
are
like,
I
would
actually
call
it
as
step-by-step
instructions,
but
there's
like
general.
You
have
to
think
about
this,
then
think
about
that.
Then
think
about
that.
C
A
Okay,
so
I'm
writing
a
a
to
do
for
myself
to
create
a
discussion
item
on
guide
guidelines.
A
A
D
Yeah,
you
might
want
to
separate
the
stuff
that
doesn't
change
that
often
from
the
stuff.
That's
version
specific,
because
I
mean
I
think
one
of
the
problems
with
the
guides
that
we
have
is
that
they're
all
tagged
to
some
version,
and
so,
if
you're
going
to
use
them,
you
need
to
change
certain
things
from
4.6
to
4.10.
A
D
Open
shift
part
presumes
that
you
already
have
you
know
dns
set
up
and
things
like
and
that
your
nodes
have
a
way
of
getting
a
name,
and
once
you
have
that
set
up,
then
that
will
work
for
many
versions
of
okd
and
you
don't
have
to
change
that
sort
of
services.
Part.
D
And,
on
the
other
hand,
every
version
of
okie
d
may
have
certain
perks,
but
for
the
most
part
it
is
a
generic.
You
know,
run
the
cluster
install
command
and
then
hustle
to
get
your
thing
up
within
a
day
before
all
the
certs
expire.
D
That
will
allow
the
pivot
to
succeed,
because
there
have
been
versions
where,
if
you
picked
the
wrong
f
costs,
then
it
would
all
break,
even
though
that
shouldn't
really
matter
that
much
because
the
version
of
f
costs
that
you
boot
your
bootstrap
node
up
in
is
not
the
one.
That's
gonna
wind
up
using.
A
Exactly
yeah
yep,
my
vote
would
be
for
using
techdown
pipelines
to
do
it.
So
that's
why
next.
D
A
I'll
create
it
yeah
I'll,
create
a
ticket
on
guides
and
we'll
start
out
with
defining
our
template
and
basically
just
like
five
to
ten
sections
that
it
needs
to
have
and
then
we'll
go
from
there
and
then
what
we'll
do
is
second
step
after
we
define
the
template,
we
can
apply
that
template
or
compare
against
the
current
guides,
see
if
they
adhere
to
that
and
if
not
then
ask
the
authors
to
update
sound
like
a
plan.
A
All
right,
let's
see
next
up,
is
at
that,
so
the
centaur
stream
core
os
initiative.
A
I
don't
know
how
many
folks
caught
the
last
meeting,
but
it
was
it's.
It's
taken
a
discussion,
the
last
two
main
meetings.
A
So
do
we
want
to
do
we
want
to
communicate
this
question
to
the
larger
community
and
get
their
thoughts
or
do
we
want
to
just
leave
this
to
the
main
group
to
say,
yay
or
nay?
We
want
this
thing
that
that
they're
offering
diane.
B
So
I
think,
where
we
kind
of
left
it
at
the
last
meeting
and
I'll
listen
to
the
recording
again
is
they're
going
to
build
it,
whether
we
want
it
or
not
right,
so
that's
so
that
and
what
we
offered
or
what
I
offered
to
facilitate
was
once
they
have
it
built
to
reach
out
to
the
our
community
and
other
communities
to
test
it
and
to
do
a
deployment
hackathon
and
see
if
it
sticks.
B
If
it's
anything,
that's
sticky
and
it
will
be
members
of
the
working
groups,
you
know
whether
they
participate
in
testing
it
or
not,
will
kind
of
be
the
litmus
test.
I
think
for
whether
it
gets
any
traction
whether
we
do
whether
we,
the
okd
working
group,
take
it
on
as
a
sub
project,
I
think,
is
still
out
there
in
the
ether
as
a
conversation,
you
know
whether
people
will
actually
use
it
or
not,
but
it's
coming.
Basically
it's
getting
built.
B
So
I
I'm
I
personally
because
I'm
a
red
hatter
and
they
employ
me-
I'm
going
to
have
to
do
the
work
around
publicizing
it,
but
the
working
group
does
not
have
to
take
it
up
as
a
piston
resistance
or
whatever
cause
whatever.
The
word
is
well.
A
So
here's
here's
my
understanding
of
the
situation,
though,
is
that
so
it
is
given
that
it's
going
to
be
used
internally.
It's
not
a
given
that
it's
going
to
be
provide
that
a
release
of
okd
will
be
provided.
That's
what
they're
asking
the
working
group
or
the
community
to
to
decide
is
if
there
will
be
an
okd
release,
yeah
an
actual
release
with.
B
B
There
will
be
a
release,
it
will
be
the
mvp
release
of
this
thing
called
okd
for
s
cost,
so
there
will
be
a
whether
they
do
it
repeatedly
and
keep
pushing
it
out
in
a
in
a
in
a
landing
page
of
our
choice
somewhere
that
we
publicize
as
okay
working
group
is
another
is
the
question
of.
A
Okay,
so
maybe
we
misstepped
by
putting
as
much
time
in
the
discussion
as
we
did,
because
now
I
feel
like
maybe
we
need
to
do
a
little
bit
of
messaging,
at
least
to
to
to
say
what
you
just
said,
and
what
I
think
we're
sort
of
agreeing
on
is
that
this
is
going
to
happen
anyway.
Internally,
there
will
be
a
version,
a
release
for
the
community
to
try.
A
C
Jamie,
I
I
was
a
little
taken
aback
by
last
meeting
and
some
people
I
thought,
would
support
the
idea
were
vermont
against
it
and
I
I
think
we
need
to.
We
need
to
understand
what
that
is.
C
I
don't
know
whether
some
of
this
is
coming
from
the
centos
withdrawal,
whether
there's
still
some
acrimony
around
that
I'd
sense
that
that
might
be
it.
But
I
also
part
of
me
thinks
it's
because
the
community
doesn't
feel
empowered
at
the
minute.
So
if
red
hat
decides
that
s
cos
is
the
thing
that
they're
interested
in
they
can
just
pull
fcos
and
we're
going
to
be
left
hanging.
So
I
think
part
of
the
solution
of
this
is
really
potentially
to
do
with.
C
A
And
yeah,
so
let
me,
let
me
just
add
one
thing
and
then
diane.
So
one
of
the
things
that
I
did
pick
up
on
in
conversations
with
at
least
one
person
was
that,
if
f
cos
gets
pulled,
there's
a
sense
that
the
centos
upstream
it
doesn't
have
that
same
sort
of
oh.
I
know
where
to
file
this
bug
in
fedora
to
get
this
addressed.
A
I
know
you
know
that
this
is
a
fedora
issue,
or
this
is
a
fedora
core
os
issue
and
it's
clear
clearer
where
you
would
file
a
bug
and,
and
some
of
the
people
have
been
very
who
are
concerned,
I've
been
very
active
in
sort
of
being
point
people
with.
Oh,
this
is
a
fedora
or
westbug.
This
is
a
fedora
bug,
etc.
A
B
You
nailed
it
thank
you
for
for
describing
it
as
that.
I
think
that
that
that
one
of
the
primary
issues,
for
me
is
is,
is
the
centos
stream
or
s-cos,
as
people
are
calling
it
centos
stream
core
os?
Is
it
an
open
project?
Is
it
something
that's
going
to
be
that
we
can
have
give
feedback
to
engineering
and
what
are
those
processes
and
timothy
was
timothy
ravier?
B
Who
is
on
the
call
is
working
through
that
and
and
is
going
to
just
you
know,
figure
out
what
those
processes
are
for
us
because
he's
basically
the
person
doing
the
the
work
on
s-cos
and-
and
there
are
mechanisms
for
doing
that.
But
to
me
what
my
big
my
bigger
concern
about,
that
is
that
it's
not
being
run
like
an
open
source
project.
It
is
an
internal
thing
that
you
know
we
may
not
like.
B
Just
like
brian,
we
described
you
trying
to
hack
through
trying
to
figure
out
these
internal
bits
and
pieces
for
the
operator
stuff.
We'll
have
the
same
issue
with
the
centos
stream
one
and
as
an
open
source
community,
which
is
what
okd
is
will
be
still.
You
know
handcuffed
to
not
really
having
a
great
feedback
mechanism
for
the
testing
and
deployment
results.
B
Even
you
know
if
it
turns
out
and
and
people
have
over
the
past
two
or
three
years,
gotten
really
comfortable
engaging
with
the
fedora
core
os
community
and
they
have
a
lovely
set
of
processes
and
guidelines
and
release
things
that
are
very
public
and
very
transparent.
So
that
to
me
is
a
bit
of
a
red
flag.
I
have
to
say,
which
is
why
I'm
not
putting
a
lot
of
I
don't
not
putting
a
lot
of
blog
posty
stuff
out
there
and
like
promoting
the
centos
stream
core
os
okd
yeah.
B
I
just
want
to
get
them
to
release
the
mvp
so
that
we
can
test
it
and
then
try
giving
feedback
through
whatever
timothy
sets
up
for
us
and
if
it's
sufficient
and
we
feel
like
we
can
do
it
and
at
the
same
time
keep
raising
these
issues
about
it,
not
being
a
true
open
source
distro
of
coreos,
I'm
just
gonna
say
it.
I
don't
care
if
they
fire
me.
B
It's
like
it
bugs
me
that
it's
not
gonna
have
its
own
landing
page
and
that
maybe
will
there
was
a
little
in
innuendo
that
maybe
we
would
put
up
a
landing
page
under
okd.
B
For
this
thing,
there
was
even
a
suggestion
that
we
call
it
okd
os,
not
centos
stream,
core
os,
which
I
really
will
object
to.
You
know
vehemently
as
much
as
I
like
okd,
I
don't
think,
there's
any
yeah,
there's
no
reason
for
that,
but
they
so
there's
this.
This
thing
that
took
me
off
guard
last
week
too
around
the
lack
of
a
true
open
source
project
around
or
processes
around
centos
stream,
and
I
could
be
wrong.
I
could
have
had
you
know,
got
ears
and
not
been
listening
to
it.
B
In
timothy
we
could
have
had
english
as
a
second
language
issues
too.
So
I'm
giving
people
the
benefit
of
the
doubt
that
with
this
mvp
there
will
be
some
processes
and
we
would
we
can
improve
them,
and
I
had
a
conversation
as
well
with
neil
from
dado
right
after
the
call-
and
the
interesting
thing
to
me
is
and
he's
got,
he
has
a
long
standing
relationship
with
the
center
west
community
as
many
okd
working
people
working
group.
People
do
as
well.
B
So
he
knows
all
the
history
and
even
in
spite
of
all
that
what
he
said
to
me
the
use
case
for
dato
was,
they
probably
would
deploy
this
in
production
because
he
can't
pre.
B
He
cannot
get
his
I.t
team
to
allow
him
to
deploy
okd
using
fedora
coreos
because
they
are
required
by
compliance
to
run
some
security
package
that
they
pay
for
and
it
doesn't
run
on
fedora
coreos,
and
I
think
there
is
a
use
case
out
there
for
okd
on
s-cos
for
people
like
that,
and
I
don't
call
them
and-
and
I
I
think
I
had
this
conversation
with
you
jamie.
So
I'm
we're
recording
this
I'm
just
I.
They
are
not
the
the
same
kind
of
people
that
are
currently
in
the
okd
working
group.
B
Right
now,
in
the
okd
working
group
we
have
people
are
willing
to
hack
on
fedora
core
os
hack
on
okd
hack
through
prowl
logs.
Do
all
that
I
think,
there's
another
group
of
end
users.
Let's
call
them
who
will
just
use
it?
You
know,
and
so
we
will
get
this
adoption
and
there
will
be
some
feedback
and
on
both
ocp
and
on
realm.
You
know
whatever.
B
So
the
feedback
mechanism
is
a
good
thing,
but
I
don't
think
there
other
than
workload
and
use
cases,
and
maybe
issues
with
deployments
we're
going
to
get
them
to
be
as
active
as
you
guys
in
the
working
group,
because
they're
going
to
be
the
like
the
godaddy
hosting
kind
of
folks
they're
going
to
people
just
use
it,
and
but
there
are
lots
of
people
who
do
that
with
open
source
projects.
B
We
haven't
been
attracting
those
people,
because
it's
too
bloody
complicated
right
now
and
we
need
people
we
need
to
retain
both
of
those
communities
or
and
gain
back.
I
think
we
lost
those
end
user-ish
people
who
just
wanted
to
run
it.
So
I
think
this
is
an
opportunity
for
the
working
group
to
grow.
I
don't
think
it's
going
to
grow
technical
resources
in
the
community.
I
think
it's
gonna
and
we
have
to
be
aware
of
that
because
it's
gonna
be
a
resource
hog.
B
This
is
people
will
ask
questions
and
want
tech
support
for
this,
and
if
there
is
no
feedback
mechanism
to
timothy
that
is
effective
or
to
the
team,
that's
doing
the
releases.
That's
effective,
they're
going
to
come
to
us
and
we're
going
to
waste
copious
amounts
of
goodwill
and
time
from
this
team
on
those
efforts.
B
So
I'm
very
cognizant
of
this
is
an
mvp
we're
going
to
see
if
people
are
interested
in
it
and
which
kinds
of
people
are
and
what
the
feedback
mechanisms
are-
and
that's
my
feel-
and
I
I
think,
everybody's
in
semi
violent
agreement
with
me,
but
bruce.
D
D
So
that's
compelling,
but
the
the
the
way
it's
been
presented
so
far
is
just
a
shiny
new
toy
here
you
know
play
with
it,
isn't
it
fun
and
it
did
sort
of
threaten
the
f
cos
people
I
would
say,
because
it
told
them
hey
you're.
You
know
you
may
not
have
a
job
in
a
few
months,
and
so
there
was
a
little
bit
of
reaction
to
that.
A
I
don't
know
that
that's
I
don't
know
that.
That's
true,
because
f
cos
is
a
what
one
thing
and
I
I
tried
to
highlight
this
in
the
in
the
last
main
meeting-
is
the
f
costs.
Folks
are
trying
to
orient
fcos
as
being
a
sort
of
neutral
container
operating
system.
You
can
run
it
on
its
own.
You
can
run
it
in
other
cluster
technologies,
etc.
So
I
don't
it
doesn't.
I
don't
because
that's
a
volunteer
effort
as
well.
I
think
I
don't
think
it
threatens
their
job
so
much.
A
I
think
the
the
the
security
thing
it
probably
would
be
fips
right
so
fix.
You
can't
do
fips
on
f
costs.
Centos
you
can
do
fips.
So
if,
if
that
means
that
sun
toss
stream
core
os
means
that
okd
can
finally
do
fips,
that's
pretty
big,
because
even
I
haven't
been
able
to
use
okd
in
all
the
situations
I'd
like
to
because
of
its
inability
to
support
those.
D
Yeah
I
agree,
but
but
my
my
concern,
though,
is
that
the
or
one
of
my
concerns
about
the
whole
centos
thing
is
that
it
seems
to
have
fallen
flat
on
the
upgradeable
issue.
D
Okay,
like
when
I
started
with
linux.
Every
time
there
was
an
update,
you
had
to
completely
reinstall
from
scratch,
with
slackware
and
red
hat
introduced.
You
know
rpm
updates.
D
And
since
then,
the
you
know
it's
sort
of
changed
its
labeling
several
times,
but
it's
always
had
pretty
good
update
history
and
I
recently
updated
the
you
know:
fedora
desktop
system
from
34
to
36
no
problems.
D
Now
going
from
centos
to
stream,
that
is
just
seemed
to
be
no
longer
the
case.
D
Okay,
you
could
update
from
centos
7
to
cinder
s8
and
for
a
while
you
could
update
from
centos
8
to
stream,
but
at
the
moment
it
seems
that
if
you're,
if
you
have
a
centos
eight
system,
you
can
not
update
it
or
convert
it
to
stream.
You
have
to
reinstall
from
scratch.
C
D
Yesterday,
yes,
but
I
mean
the,
but
I
guess
it's
based
on
the
centos
stream,
which
is.
A
C
Upstream
version
of
rel
cos,
so
it
has
the
same
use
cases
that
rel
core
os
has
which
is
ocp
only
today,
but
obviously
s
cost
will
be
okd
only.
So
that's
what
my
understanding
and
christian
actually
did
this
on
the
dublin.
He
actually
talked
about
this
on
the
dublin
gathering
and
he
the
way
he
put
it
is
fcos
is
where
we
get
all
the
latest.
Linux
features
it.
C
C
If
you
want
a
more
stable
version,
then
s-cos
will
be
that
more
stable,
where
it's
had
time
to
be
hardened
and
it
is
going
to
be
the
upstream
of
rel
core
os.
So
if
you
want
a
a
more
stable
platform,
okd
on
s
cos
will
give
you
that
most
more
stable,
where
new
features
have
had
time
to
be
embedded,
be
checked
out
before
they
get
released
into
that.
That's
what
christian
said
on
on
on
at
the
gathering
so.
B
I'll
grab
that
video
as
soon
as
it's
available
and
share
it
with
everybody,
but
I
I
want
to
go
back
to
something
that
bruce
said,
because
I
I
just
want
to
have
some
clarity
on
it
that
one
of
the
issues-
I
I
think,
if
I
heard
you
right,
is
the
upgrade
process.
So
say
you
install
okd
on
s
cos
and
it's
using
you
know
a
rel,
nine
or
what
whatever
the
latest
version
is,
and
you
wanted
in
well
nine
point
two
came
out:
you
wanted
to
upgrade.
B
D
Well,
okay,
the
okay,
so
I
I
agree
with
the
comments
that
the
okd
usage
of
it
and
the
machine
operator,
and
so
on,
changes
things
considerably,
because
you
are
essentially
with
a
machine
config
operator.
You
are
installing
a
new
version
rather
than
upgrading
an
old
one.
Okay.
So
so
I
guess
that
that
my
synthos
experience
is
mainly
running
it
as
an
operating
system.
Yeah
right,
you
have
to
upgrade
the
operating
system
right
and.
A
In
yeah,
it's
yeah,
it's
not
because
if
we're,
if
we're
talking
about
a
core
os,
a
core
os
has
a
different
version.
Multiple
versions
of
the
operating
system
essentially
lined
up
that
you
can
select
from
to
boot
into
and
essentially
you're
you're,
not
updating
the
os
you're
booting
into
a
new
right
yeah.
B
D
And
so
my
concern
actually
is
more
fundamental,
which
is
the
lack
of
these
upgrade
facilities
on
the
centos
side
leads
me
to
have
a
feeling
which,
of
course,
feelings
can
be
totally
incorrect.
I
agree
with
that
that
centos
is
a
step
backwards
in
maturity
from
everything
that
we've
had
so
far
and
if
it's,
if
it's
an
immature
operating
system
framework,
then
it
would
give
me
concern
to
base
a
production
system
on
it.
D
Because
everybody's
busy
and
priorities
change-
and
it
does
take
a
while
to
get
a
community
up
to
speed
so
like
I
can
believe
the
story.
The
fedora
community
now
is
relatively
mature.
B
Yeah,
I
think
what
I
would
say
is
it's
a
trust
issue
right.
What
we
have
here
is
a
classic
open
source
trust
issue
and-
and
that's
kind
of
why
having
to
me
having
the
mvp
available,
trying
to
do
the
testing
and
deployment
with
it,
building
some
trust
that
there
are
feedback
mechanisms
and
processes
finding
out
whether
it
is
fixed
compliant.
B
B
If
we're
going
to
spend
our
time
and
energy
doing,
testing
of
the
mvp
first
and
foremost-
and
I
think
timothy
and
the
team
and
steven
are
totally
okay
with
that
and
and
we'll
do
that,
and
if
nobody
shows
up
at
this
hackathon
and
nobody
tests
it,
then
I
don't
believe
you
know,
I
think
they
will
have
an
internal
release
of
okd
and
s-cos
going
on,
but
they
are
not
going
to
like.
B
If
we
don't
do
a
little
bit,
come
the
other
20
steps
towards
you
know
it's
like
square
dancing
or
something
we.
You
know
if
we
don't
come
a
little
way
in
and
do
some
of
this
on
the
mvp
they're
gonna
just
go
okay,
there
is
an
interest
in
the
community,
so
I
think
there
is
some
interest
in
the
community
I'll
ask
the
question
jamie
or
maybe
you
can
ask
it
of
christian
as
well
about
the
fips
compliant.
B
I
think
that's
a
good,
solid
use
case
if
this
gets
us
to
compliance,
that's
kind
of
huge
and
so
that
yeah,
but
it
this
is
a
classic
trust
and
we
have
built
up
a
great
relationship
with
the
fedora
community
around
fedora
core
os,
and
we
trust
them
to
hear
us
to
do.
What's
you
know
what
we
need
and
they
trust
us
to
test
their
stuff
and
give
them
good
feedback
and
collaborates.
B
We
need
the
same
thing,
but
there
is
no
real
community
there
in
the
center
west
stream
community
there
are
no
bodies
other
than
engineering
resources
from
red
hat.
So,
and
if
and
this
is
my
concern
and
I'll
keep
saying
it-
we
get
two
minutes
left
as
if
that's
not
going
to
be
run
as
an
open
source
community.
There
will
never
be
a
bunch
of
people,
you
know
managing
the
infrastructure
and
the
release
process
for
it
like
the
fedora
core
os,
and
I
think
so,
and
nobody
from
fedora
coreos
is
going
to
lose
their
job.
B
Trust
me
on
that,
because
most
of
them
are
red
hatters
that
are
doing
this
work
and
they're
both
doing
both
like
timothy.
So
that's
that's
not.
I
don't
think
they're
because
I
think
it's
I
I
just.
I
just
think
we're
in
a
in
this
flux
moment
where
we
don't
have
the
trust,
and
we
have
the
past
experience
with
centos
that
you
know.
B
As
it
wasn't
great,
I
will
burn
a
lot
of
people
burned,
a
lot
of
people.
You
know,
and
so
you
know
we're
asking
to
take
this
steps
towards
each
other
and
start
this
dance
again
and
everybody's
been
burned
once
so.
You
know,
I
think,
that's
it.
The
other
thing
jamie
that
I
wanted
to
say,
brian
cook,
is
the
agenda
item
for
next
week
for
the
main
meeting
I
just
wanted
to
mention
it
here.
B
Brian
cook
is
in
my
business
unit
and
he
is
running
in
building
tectonic-based
build
pipelines
as
a
service
for
red
hat
products
and
projects
he's
got
an
initiative
inside
and
he
I
think,
he's
got
a
few
things
that
he's
working
on
as
pilot
projects
for
this
and
he's
hoping
to
come
next
week
and
talk
about
it,
and
he
has
been
talking
about
the
next
thing
that
they
might
build
as
a
service.
B
Using
these
based
tectonic,
more
modern,
shall
we
say
pipelines
could
be
okd
and
that's
that's
separate
from
the
operate
first
cloud,
because
that
would
be
on
something
else.
So
I
wanted
to
have
him
come
next
week
and
describe
what
he's
doing
to
see
if
there's
interest
in
us
being.
You
know
the
guinea
pigs
for
that,
and
that
would
probably
be
okay
d
with
f
cos,
but
I
don't
have
clarity
on
that.
So
there's
another
way
to
get
okd
with
fcos
built
that
we
could
also
participate
in.
C
I
was
going
to
say:
I
think
the
importance
is
that
at
some
point
we
get
to
the
point
where
a
community
member
can
build
okd
and
produce
a
binary
equivalent
to
what
red
hat
releases,
because
at
the
minute
we
can't
there's
no
way
that
we
know
what
happens
in
prow,
to
the
extent
that
we
can
go
and
repeat
that
within
the
community
outside
red
hat
firewall.
I
think
to
me
that's
important
thing.
We
end
up
with
a
process.
C
So
if,
for
some
reason,
red
hat
decides
that
resource
constraints,
they
can't
put
the
same
amount
of
resource
into
it,
something
that
we
rely
on
we're
not
killed.
I
think
that
that's
the
danger
that
that's
what
we
feel
that
we
are
so
beholden
to
red
hat,
giving
engineers
time
to
work
with
us
and
produce
things
for
us
that
if
that
stops,
we
die,
and
I
think
that's
that's
the.
I
think
that's
some
of
the
frustration
that
also
bowled
over.
A
A
We've
got
our
to-do's
there,
let's
go
forth
with
our
to-do's
and
then
we'll
bring
these
other
things
to
the
greater
meeting
that
I
think
probably
should
be
fleshed
out
in
the
greater
meeting
all
right.
So
thanks
folks
appreciate
your
participation
and
continued
efforts
and
talk
to
you
next
time
take
care.