►
From YouTube: OKD Working Group Meeting 03-29-2022
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
A
Let's
see
if
we
have
any
new
folks,
any
new
folks
want
to
introduce
themselves.
I
see
one
or
two
names
that
I
don't
recognize
no
pressure,
but
if
you
want
to
introduce
yourself
feel
free.
A
All
right:
well
then,
let's
move
on
to
our
first
agenda
item,
which
is
the
okd
release
updates
christian
is
not
here
today,
vadim
is
taking
a
hiatus
from
okd,
and
so
basically
christian
sent
me
some
info
that
basically
there's
a
blocker
and
I
have
a
link
to
it
up
there,
and
this
is
for
the
410
release
and
as
soon
as
they
can
get
past
that,
then
we
will
have
a
solution
to
that,
and
it
looks
like
this
issue
here
might
be
related
to
it,
so
that.
A
Within
that,
like
yeah,
okay,
so
that
is
the
link
actually
that
first
link.
So
basically,
if
you
go
in
there,
you'll
find
some
stuff
related
to
the
ongoing
issue
for
okd
410
and
we'll
be
talking
more
about
that
at
the
next
meeting.
The
docs
group
is
just
sort
of
getting
things
settled
where
we'll
have
multiple
people
with
access
to
the
twitter
and
be
able
to
tweet
out
things
like
new
releases
and
and
whatnot.
A
It's
just
a
question
of
everyone
having
the
same
bitten
word
set
up
to
share
the
credentials
for
twitter,
but
we'll
talk
about
that
in
the
docs
updates.
Is
anyone
from
the
f
cos
any
red
hat
folks
from
fcos?
Here?
Doesn't
look
like
it
so.
B
I
wasn't
at
the
last
doctor
meeting
I
was
ill,
so
I'm
not
sure
if
there's
anything
happened
there.
What
I
can
say
is
I've
moved
the
charter
into
the
okay,
the
iodox
and
I
put
a
new
items
list
in
the
repo.
So
we'll
talk
about
how
we
want
to
sunset
the
rest
of
that
content.
B
There
is
a
roadmap
in
there
and
there
is
a
membership
and
there
are
membership
lists
in
that
repo,
and
I
don't
know
whether
we
still
want
to
do
those
or
keep
them
up
to
date
or
just
drop
them.
So
we'll
talk
about
that
there,
but
in
terms
of
the
the
charter,
the
charter
as
it
now
stands
is
in
the
okay.
B
I
o
docs
in
the
community
section,
and
I
am
still
working
with
brandon
to
get
some
styling
updates
added
he's
done
some
tweaks
on
basically
the
css
style
sheet,
just
to
update
some
colors
and
to
make
the
site
a
little
bit
easier
to
read
and
improve
accessibility.
B
So
I'm
not
sure
whether
he's
going
to
do
a
pull
request
on
those
or
he's
going
to
wait
until
he's
done
any
further
styling
but
I'll
catch
up
them.
This
week
yeah
there
was
some
people
have
commented
there.
B
There
has
been
a
discussion
group
about
site
stability,
and
this
is
down
to
github,
because
okd
io
is
now
hosted
by
github,
it's
on
the
github
pages,
and
we
just
redirect
the
okidi.io
url
to
the
github
pages
site
and
github
have
been
having
a
number
of
issues,
apparently
they're
having
they're
having
some
database
issues
which
caused
the
outage,
and
I
put
a
link
in
the
mk
into
the
hackmd
minutes,
where
there
is
a
blog
from
github
discussing
the
issues
they've
been
having
over
the
last
few
weeks.
B
B
No,
no,
it
was
nothing
to
do
with
us.
It
was
purely
the
githubs
pages.
Environment
was
down,
so
every
site
hosted
by
github
was
down
for
a
while,
and
I
know
that
there
was
some
repo
at
about
the
same
time.
I
had
some
repo
issues
where
you
couldn't
access
repo,
so
it
was
purely
a
github
issue.
Okay,.
A
I
think
that's
it
for
docs
dusty
did
pop
in
to
talk
about
fcos
stuff.
Real
quick
he's
only
got
a
few
minutes.
So
let's
pass
the
the
talking
stick
over
to
dusty,
real
quick
to
talk
about
f,
cos
stuff
and
then
we'll
switch
back
to
maybe
docs
after
that,
so
dusty.
Take
it
away.
C
Gotcha
yeah,
I
didn't
know
if
we
had
any
specific
questions,
a
couple
things
to
call
out
just
happenings
in
the
community.
C
Our
next
stream
in
fedora
core
os,
is
now
on
fedora
36,
so
the
beta
for
fedora
36
came
out
today
and
we've
been
testing
on
next
devel
for
a
few
weeks
running
that
through
ci.
So
hopefully
you
know
people
don't
find
issues,
but
if
they
do
at
least
they
may
you
know
we
found
them
before
they
reached
our
other
streams.
C
So
I
don't
know
what
the
demon
christian
have
set
up
now,
for
you
know,
testing
future
streams,
but
that
might
be
something
to
look
at
and
then
one
other
thing
jamie.
I
know
I
think
you
run
some
vmware,
don't
you?
We
are
updating
our
vmware
images
to
use
uefi
and
secure
boot
by
default,
and
that
is
happening
on
our
next
in
testing
streams.
This
go
around
and
then
it'll
happen
in
stable
in
two
weeks.
C
We
also
have
some
documentation
that
we're
working
on.
I
don't
know
if
it's
published
yet
that
will
show
you
how
to
essentially
go
back
in
and
edit
the
image
if
you
for
some
reason
need
to
stay
on
bios
boot.
That's
it
for
me.
As
far
as
updates.
I
don't
know
if
we
had
any
specific
questions.
D
I
thought
that
the
the
f
cause
image
production
process
actually
produces
hybrid
boot
images
that
they
do
both
uefi
and
bios.
C
D
Reason
right
the
reason
I
asked
that
clarification
is
that
at
work
I
deal
with
some
vmware
or
some
things
that
I
pretend
to
hope.
I
don't
have
to
care
about
very
much,
but
it's
a
thing
and
some
versions
of
vmware
esxi
straight
up,
ignore
the
value
that's
set
in
the
ova
metadata
and
we'll
just
always
do
one
more
or
the
other,
depending
on
what
bug
is
affecting
the
the
the
esxi
or
v
sphere
software
at
this
point
in
time.
C
Yeah,
I'm
I'm
pretty
sure
that
it
supports
both
because
for
the
most
part,
our
images
on
different
platforms
are
mostly
just
the
same
bits,
just
repackaged
in
a
different
way,
because
different
for
different
platforms
take
different
inputs,
like
I
think,
gcp
takes
the
tarball
and
you
know
some
take
a
cucao
and
some
take
a
vhd
and
some
take
an
ova
but
nine
times
out
of
ten
like
there's
nothing.
C
You
know,
as
far
as
when
you
boot
the
machine,
there's
no
changes
between
the
different
platforms
other
than
a
platform
id
that
gets
embedded
so
neil
it
should
you
know,
because,
obviously
we
can
boot
on
either
or
for
other
platforms.
It
should
work
as
well
on
vmware,
if
you,
if
you
tried
to
go
in
and
override
that
to
go
back
to
bios.
D
Okay,
cool!
That's
all
I
really
care
about
is
just
not
that
I
want
people
using
bios,
but
I'm
already
aware
of
vsphere
and
esxi
versions
where
this
there
are
bugs
in
vmware,
where
it
doesn't
read
the
metadata
value
properly
and
will
do
one
thing
or
the
other,
regardless
of
what
you
tell
it,
and
so
I
would
just
rather
that
actually
work
regardless.
C
Cool
yeah,
if
you
have
access
to
one
of
those
environments,
go
grab
our
testing
or
next
vmware
image
you
can.
You
should
be
able
to
grab
those
on
the
web
page
today
and
and
see
if
they
work.
C
A
A
Just
on
spur
of
the
moment.
C
Yeah
no
worries
yeah.
I
I
was
planning
to
cover
today,
but
I
got
busy
with
some
other
things.
So
sorry,
no
problem
at
all
I'll
see
you
all
later.
A
So
one
of
the
things
that
came
out
of
the
the
docs
meeting
is
the
need
for
a
contributor's
guide
and
a
guide
on
the
infrastructure,
like
the
actual
infrastructure
behind
the
builds.
A
The
reason
for
this
is
something
that
I
alluded
to
earlier
in
the
that
vadim
has
decided
to
take
a
hiatus
from
working
on
okd,
so
right
now,
there's
christian
contributing
when
he
can,
but
that's
it.
A
We
can
put
in
bug,
fixes
and
code
changes
and
whatnot
and
get
them
approved
by
a
christian
and
a
handful
of
other
folks.
So
we
can
contribute
still,
but
there's
really
there's
no
guide
for
sort
of
how
things
work.
In
the
background-
and
you
know
brian-
has
rift
on
this
quite
a
bit.
A
A
You
know
you,
you
get
a
badge
basically
after
so
many
of
certain
types
of
contributions
that
allow
you
to
step
up
to
make
more
sort
of
fundamental
contributions.
A
That's
something
that
the
docs
group
will
talk
about
is.
Does
anyone
have
any
feedback
on
those
ideas?
Any
thoughts
on
this?
You
know
this
was
also.
A
The
morning
of
the
dots
meeting
he
sort
of
left
the
channel
and
said
he's
going
on
hiatus,
so
it
was
kind
of
sudden.
B
Okay,
jamie
yeah-
I
have
been
quite
vocal
on
this.
I
think
one
of
the
one
of
the
challenges
is
before
anybody
can
start
contributing.
B
So
just
trying
to
find
out
which
repos
I
actually
need
to
care
about
to
actually
work
out.
How
to
do
a
build.
I've
tried
to
go
down
the
sort
of
the
the
the
sort
of
m
maze
before
and
you
just
end
up
going
round
and
round
circles
and
getting
totally
lost
I'd
love
to
be
able
to
do
an
okd
build,
but
even
things
like
are
we
still
in
vadim's
repo
for
the
special
okd
sort
of
process.
B
Vladim
had
that
in
his
personal
repo
for
a
while,
there
was
talk
about
it
moving
into
the
open
ship
repo
again,
so
I
don't
think
anybody
outside
red
hat
really
understands
or
has
the
ability
to
understand
how
to
do
a
build
if
it's
possible
to
do
a
build
outside
of
the
red
hat
infrastructure
and
if
so,
what
is
the
end
to
end
process
flow?
So
I
I
think
it'd
be
really
good
to
actually
try
and
get
that
at
least
documented.
I'm
quite
happy
to
write
things
up,
but
I
need
some
guidance.
E
I
think
it
depends
on
what
you
mean
by
a
build.
You
know
I
built.
I
build
my
own
images
for
the
last
year.
You
know
for
testing.
You
have
to
realize
that
okd,
you
know
in
openshift
are
built
with
a
wide
variety
of
modules
and
each
of
those
modules
kind
of
has
its
own
build
process,
they're
kind
of
similar,
but
99
of
time.
You
don't
need
to
rebuild
those,
you
just
go
out
there
and
you
access
ones
that
are
currently
out
there
and
currently
built.
E
So
it's
more
of
how
do
you
build
a
particular
module
say
you
know
okd
machine
os,
and
how
do
you
integrate
that
into
your
own
image
to
test
with
it's
not
a
hard
process
for
that
particular
one?
It's
it's
honestly,
it's
not
even
convoluted,
but
what
you
probably
do
need
is
your
own
repository
out
on
not
github
or
doctor
hub.
I
just
went
right
out
of
my
head
where
all
the
images
are
currently
stored.
Key.
E
Yes,
so
you
know
you
need
to
have
your
own
repository
there,
that
you
can
push
out
these
images
and
then
you
build
a
complete
image
and
you
push
it
out
and
then
you
can
actually
do
an
install
from
that
secondary
image.
You
know,
is
it
going
to
look
exactly
like
what
you,
what
we're
currently
doing
with
all
the
dates
and
everything?
E
No
and
you
know,
there's
probably
details
that
we
can
get
from
vadim
on
that
you
know
to
help
with
the
process,
but
for
debugging
and
building
it's
really,
not
that
not
that
difficult.
It's
just
not
well
documented.
F
The
open
shift,
release
repo
set
up
your
own
prow
system
and
then
allow
because
that's
how
we
build
the
release
images
now
is
we
use
all
that
proud
automation
to
build
the
individual
images
we
put
them
through
testing,
and
then
we
promote
them
into
release
images.
This
is
kind
of
where
you
know,
vadim
is
isn't
taking
the
inspiration
for
cutting
the
okd
images
off
so
like,
and
this
is
yeah
go
ahead.
Jimmy.
A
Well,
just
let
me
add
a
little
bit
more
context.
One
of
the
things
that
came
up
in
the
docs
meeting
was
diane
is
actually
going
to
check
into
what
is
what
are
the
ramifications
of
making
okd
a
truly
external
open
source
project?
So
if
this
is
necessarily
in
terms
of
users
building
it
but
the
community,
the.
F
Right
right,
and
so
I'm
trying
to
get
to
the
point
of
like
what
you
originally
said
about
like
making
changes,
and
then
you
know
brian
was
talking
about.
Well,
you
probably
want
to
test
your
changes
before
you
do
anything
so
like
it.
What
I
my
point
here
is
that,
like
yeah,
I
think
if
the
okd
community
wants
to
grow
to
the
point
where
they're
doing
they've
got
like
their
own
prow
system,
that's
building
everything
like
that's.
F
You
know,
that's
awesome
and
whatnot
right,
like
all
that
code
is
still
going
to
go
back
to
the
ocp
stuff,
unless
okd
becomes
a
full
fork
right
and
then
there's
like
no
sub
there's,
no
linkage
between
the
okd
code
repositories
and
the
upstream
or
downstream.
I
guess
is
the
way
we
look
at
it.
Ocp
repositories
right
so
like
we're
working
with
partners
to
help
them
do
these
kind
of
things
now
from
the
red
hat
side
and
the
way
we
do
it
is
exactly
like
john
was
just
talking
about
now.
F
So,
like
the
entry
way
to
get
into
testing,
your
things
is
learning
how
to
build
an
image
for
the
component,
you're
working
on
a
container
image
right
and
then
using
the
oc
adm
tooling,
to
build
a
release
image
from
a
known,
good,
okd
image
that
has
your
component
image
inserted
into
it
and
so
like
to
me.
That's
the
level
one
process
you
want
to
get
to
once
you
once
you
know
how
to
create
like
a
component
image
that
you're
working
on,
let's
say:
you're
working
on
machine
config
operator
right,
so
I've
got
my
repo.
F
I
know
how
to
build
an
image.
I
know
how
to
put
it
into
key
or
quad,
depending
on
which
side
of
the
pond
you're
from,
and
then
I
know
how
to
build
a
release
image
that
points
to
my
image
in
the
registry
right
and
so
now.
I've
got
that
all
bundled
up,
and
I've
made
sure
that
the
internals
look
good,
so
it'll
it'll
match
the
image
when
I
deploy
it.
Just
getting
to
that
step
alone
is
a
really
big
accomplishment,
but
once
you
get
there,
you
can
do
what
john's
talking
about
where
you
can
build.
F
Learning
how
to
do
that
for
each
component
and
building
a
full
release
image,
but
I
think
for
a
contributor
just
get
like
if
we
had
guidance
of
how
they
could
take
a
currently
released.
Okd
image
use
the
oc
tooling,
to
replace
one
of
the
components
that
would
probably
get
people
started,
at
least
on
this
process
of
contributing.
E
And
honestly,
that's
how
I
do
my
testing.
You
know
we
identify
a
bug.
You
know
whether
it
was
mco.
You
know
back
a
year
ago
or
okay,
machine
os
or
whatever
that's
how
I
do
it.
Then
I
build
it
on
my
local
environment
and
test,
because,
honestly,
it's
faster
than
going
through
ci
it's.
So
it's
so
much
easier
to
go
through
and
iterate.
You
know
you
know
over
an
hour
than
it
is
over
four
hours
waiting
for
ci
to
do
a
test.
E
You
know,
then,
once
you
have
some
confidence
in
it.
Yes,
I'm
only
testing
vmware.
You
know
a
lot
of
changes
have
to
go
through
and
you
know
go
on
openstack
and
you
know
all
the
other
things,
but
at
least
you
have
some
confidence
that
at
least
you
know
in
one
environment
it
runs
and
built
and
then
ci
can
test
it.
Hopefully,
wherever
else
it
has
to
do
part
of
the
issue
we
have
right
now,
especially
with
okd
machine
os.
E
Is
that
right
now
it
can
only
you
can't
build
it
from
a
poll
from
another
user
account.
So
if
I
create
something,
I
have
a
fork
build
and
then
I
want
to
do
a
pull.
It
won't
work
because
of
how
much
oh
kitty
machine
os
is
currently
built
with
vadim's
magic.
E
He
has
some
magic
that
happens
in
there,
so
that
you
can
build
is
if
you
have
actual
access
to
the
direct
repository
outside
of
a
build.
You
can
still
do
a
poll,
but
you
have
to
have
real
access
to
it,
not
not
from
a
fork.
So
that's
that's.
One
of
the
issues
that
we
have
is
that
somebody
has
to
be
able
to
control
it
right
now.
I
think
it's
only
vadim
and
christian,
although
I
could
be
wrong.
E
I
haven't
looked
at
the
the
owner's
side
very
much,
but
that's
a
it's
not
really
a
flaw,
but
that's
a
disadvantage
of
how
we're
currently
building,
because
that's
how
you
know
we're
building
the
images
for
f
cos
and
adding
all
the
other
magic
that
happens
that
differentiates
us
from
using
rh
cost.
So
there's
some
discussion
that
has
to
happen
in
there.
If
you
don't
have
build
authority
in
that
repo
yeah.
A
Okd
is
now
theoretically
a
true
upstream
of
open
shift,
so
that
might
change
the
dynamics
a
little
bit
in
terms
of
what
red
hat's
thought
might
be
about
our
spinning
off
and
and
how
those
any
fixes
we
would
make
would
end
up
back
in
ocp
right
like
they
might
be
reluctant
to
relinquish
it
now,
because
we
are
a
true
upstream
or
they
might
be
really
happy
to
do
that,
because
there'll
be
innovation.
If
there's
a
lot
of
developers
working
on
it.
E
D
Or
if
we
flip
it,
the
other,
we
flip
it
on
its
head
right.
The
the
other
way
to
think
about
this
is
the
existing
process
shifts
to
being
more
in
the
public
view,
the
one
that
actually
runs
right
now,
that
builds
the
ocp
slash
okd
whatevers,
and
if,
if
we're
saying,
okay
we're
we're
tracing
all
this
we're
already.
Okay
with
the
contents
that
the
the
little
the
literal
binary
blobs
that
make
up
the
different
container
images
that
are
the
unbranded
bits
are
identical.
D
So
that's
mcd
web
console
container
and
I
think,
like
two
others
out
of
like
the
360,
odd
containers
that
actually
make
up
openshift
those
get
splintered,
one
you
get
that
is
ocp
built
internally
and
one
you
get
okd
built
publicly
and
then
the
rest
of
them
just
happened
publicly
in
one
built
process
because
doing
that
flipping
that,
because
right
now,
we're
sister
builds
we're
not
like
the
truth
is
we're
sister
builds
and
the
way
red
hat
does
it
is
that
they
promote
at
their
own
pace
rather
than
following
the
train
that
we
do
now.
D
If
we
keep
that
model,
which
I
think
is
actually
a
really
good
model,
then
we
can
minimize
what
kind
of
splitting
we
actually
have
to
do
architecturally
for
motivate
making
this
more
of
a
community
platform
right.
So
if
we
shift
what
we're
already
doing
from
inside
the
red
hat
farm
to
outside
the
red
hat
farm,
and
then
we
take
the
bits
that
actually
have
to
be
different
and
split
their
processes.
So
there
is
one
inside
the
red
hat
side
and
one
outside
the
red
hat
side.
Then
we
don't
wind
up
boiling
the
ocean.
D
I
think,
like
two
or
three
times
for
no
particularly
great
reason
and
it
maximizes
the
value
to
the
ocp
team
and
minimizes,
the
the.
How
would
I
say
this
responsibility,
or
or
or
pressure
onus
on
the
okd
side
and
and
that
I
think,
is
probably
what
we
want
to
move
towards,
because
I
think
we
basically
want
to
emulate
without
the
bad
parts.
D
The
way
that
rh
osp
is
handled
right
now,
which
is
you've,
got
the
rdo
stuff,
that's
all
being
built
essentially
once
and
then
red
hat
promotes
internally
at
their
own
pace,
because
otherwise
it
just
turns
into
madness,
because
it's
like
hundreds
of
components
that
need
to
be
recycled
through
and
it's
just
like
nobody
want.
Nobody
on
this
planet
wants
to
boil
the
oceans
faster.
F
F
E
F
Yes,
it's
a
very
big
deal
and
so
there's
no
way
that
these
architectural
decisions
could
be
moved
outside
of
the
red
hat
fence
at
the
moment,
right,
not
well.
Things
are
in
flight
like
this
so
like.
I
would
expect
that,
like
at
some
level,
oh,
the
okd
community
coming
together
to
start
building
a
mirror
of
the
build
process.
That's
happening
internally.
That
might
be
the
natural
course
here
and
then
at
some
point
there
could
be
a
discussion
about
like
okay.
F
Is
there
a
way
that
we
move
the
fader
over
more
towards
the
community
side,
where
we
have
confidence
that
there
is
a
proud
configuration
happening,
the
same
way
that
we
do
internally
and
now
can
we
start
to
model
what
it
would
look
like
to
have
the
community
doing
this,
but
like
as
far
as
where
I'm
sitting,
I
haven't
heard
any
of
these
discussions
internally
about
like
moving
to
like
a
community
model
or
okd
being
upstream.
You
know,
maybe
that's
happening
around.
E
D
E
Yeah
that
I'm
aware
of
you
know
that
would
allow
us
to
go
through
and
do
something
like
that.
You
know
we're
not
kubernetes,
you
know
we
don't
have
you
know
that
support.
So
I
I
you
know-
and
you
know
the
jaded
part
of
me
is
saying:
hey
y'all
are
owned
by
ibm.
Now
you
guys
are
a
profit
center
they're
not
going
to
give
that
away.
B
I
was
going
to
say
I
mean
I,
I
think
let's
do
what
what's
achievable
so
we
know
there
are
bits
of
okd
that
are
different.
We've
talked
about
getting
an
okd
catalog
for
what
are
currently
the
licensed
operators.
So
that's
different.
We
do
have
some
differences
in
branding,
so
there
are
some
differences
where
we
do
have
a
different
we're
based
on
fedora.
B
There
is
no
governance
outside
of
red
app,
so
I
I
think
there
are
some
discussions
to
be
had
primarily
within
red
hat
initially
and
then,
wherever
those
discussions
lead
we're
sort
of
beholding
to
them,
and
we
can't
really
do
anything
until
those
discussions
have
been
taken
at
senior
level
within
red
hat,
but
there
are
bits
we
can
certainly
do.
I'm
very
keen
to
try
and
get
this
operator
thing
up
and
running
it.
B
Both
our
community
catalog
is
broken
currently
because
the
community
catalog
that
gets
shipped
with
okd
has
dependencies
on
the
registry
at
red
hat
operators
that
are
missing.
So,
for
example,
I
can't
put
the
the
community
che
operator
on
okd,
because
it's
looking
for
the
terminal
operator,
that's
part
of
the
licensed
red
hat
registry.
So
without
a
pulse
secret
and
pulling
that
operator,
I
can't
even
put
put
the
community
che
version
on
so
there
are
things
like
that.
I
think
that
we
can
own
our
destiny
and
we
can
actually
make
progress
on.
B
G
So
I'd
just
like
to
propose
to
the
red
hatters
one
of
the
ways
this
could
go
is
the
same
way.
Centos
stream
went
where
it's
red
hat
controlled,
but
it's
out
in
the
open
enough
that
the
community
has
some
level
of
participation
and
just
like
red
hat
is
I
mean
red
hat
linux
is
is
obviously
a
huge
money
maker,
but
centos
stream
still
makes
sense
as
a
collaboration
model.
G
G
If
the
result
was
that
we
in
red
hat,
were
aligned
in
moving
in
the
same
general
direction,
I'm
I'm
curious
to
hear
other
people's
perspectives
on
that,
but
I
just
wanted
to
point
that
out
for
other
for
for
red
hatters,
who
were
talking
about
this
internally.
D
Let's
ignore
our
cause
and
f
cos,
because
those
those
two
bits
are
already
technically
independent:
build
infrastructures,
all
the
other
stuff,
that's
layered.
On
top
of
that,
most
of
it
is
bit
for
bit
identical.
We
produce
the
same
containers
and
they
get
consumed
by
both
sides.
Then
you
have
the
very
small
proportion
of
things
right
now.
D
I
think
it's
mcd
web,
the
the
openshift
web
console
the
api
server
and
like
two
other
things
that
are
actually
fundamentally
different
because
they
need
to
be
tweaked
specifically
to
be
red,
hat
openshift
container
platform
versus
okd
on
f
cause
like
if
you,
if
you
consider
what
actually
makes
the
differences
between
the
two
platforms,
then
the
bigger
win
initially
is
to
try
to
move
the
thing.
That
already
does
the
stuff
into
the
public
view,
so
that
people
can
see
what's
happening
and
then
we
can
talk
about
access
controls.
D
We
can
talk
about
contribution
levels
and
we
can
talk
about
where
splits
need
to
be
done
for
stuff.
That
happened
that
it
has
to
happen
internally
versus
externally.
We
could
do.
We
could
talk
about.
How
do
you
deal
with
like
because
then
you
can?
The
focus
point
then,
is
dealing
with
things
like
okay,
you
have
sensitive,
ocp
rod.
You
have
cv
things
you
have
non-disclosures
and
and
weird
things
that
vendors
do,
that
those
need
to
be
done.
D
I
don't
think
it
is
productive
for
us
to
consider
going
down
that
path
for
the
working
group
or
anyone
as
a
whole
beyond
the
fact
of
how
can
we
do
a
subset
of
this
for
the
okd
specific
parts,
because
the
rest
of
it
is
identical
and
also
it's
enormous
and
frankly,
I
don't
think
anyone
wants
to
build
all
of
it
more
than
once.
B
B
I'm
aware
that
those
guys
have
a
lot
of
internal
knowledge
that
we
in
the
community-
probably
don't
have-
maybe
john,
I
think,
is
probably
one
of
the
more
technically
advanced
in
the
community,
but
I
just
think
as
a
community,
we
need
to
make
sure
that
we're
not
beholden
to
a
single
person,
because
if
that
person
has
to
step
back
for
either
personal
up
or
job
related
issues,
we
don't
want
this
project
to
stall.
A
Yeah
and
I've
voiced
this
before
is
that
I
mean
vadim
is
basically
the
linchpin
in
all
of
this
right
and
if
the
team
gets
abducted
by
aliens,
you
know,
then
we're
kind
of
screwed
right.
It's
it's.
We
can
assume
that
red
hat
would
put
someone
else
in
there,
but
you
know
we
don't
know.
We
do
know
that
red
hat
has
put
some
effort
into
this
new
operator's
catalog,
that's
okay,
d,
specific,
that's
a
step
towards
acknowledging
that
it's
okd
is
still
viable.
A
I
think
in
the
eyes
of
red
hat,
because
they're
putting
some
engineering,
but
we
don't
really
have
any
guarantees
and
no
promises
and
lots
of
people
there
as
diane
phrased
it
to
me
the
other
day
there
have
been
many
vadims.
A
There
have
been
many
people
in
the
in
the
life
cycle
of
okd
who
have
stepped
into
that
role
and
then
stepped
out
because
they
get
promoted,
it's
basically
a
stepping
stone
to
getting
promoted
it.
So
it's
gonna
happen,
and
it's
just
a
question
of
how
you
know,
as
you
said,
brian
like
how?
How
do
we
fill
that
and
can
it
be
filled
by
an
external
person?
Or
can
we
show
the
value
so
much
that
that
red
hat
very
easily
puts
someone
else
in
who's?
A
Gonna
do
a
good
job
of
leading
this
project
right
from
a
technical
standpoint,
it's
been
said,
and
I
it's
probably
accurate.
I'm
not
gonna
mince
words
about
it,
but
it's
likely
that
red
hat
views
okd
as
a
stepping
stone
to
ocp
to
people
purchasing
ocp
licenses.
It's
like
hey
here's.
This
thing:
it's
nice
by
the
way
it's
even
nicer
and
stable
and
supported.
A
E
E
E
I
specifically
asked
when
that
happened.
What's
going
to
happen
to
okd,
you
know,
because
again
you
know
you
could
look
at
okd
as
being
a
competitor.
Do
ocp,
you
know
it's
free.
You
know
people
can
manage
it
themselves.
You
know
you
look
at
a
lot
of
the
problem
tickets.
Whatever
you
see
online,
you
can
manage
a
lot
of
your
issues
yourself.
If
you
have
the
technical
teams
to
do
it.
E
It's
okay,
but
we
know
you
know
that
any
okd
issues
themselves
are
probably
the
same
issues
that
ocp
has
in
terms
of
the
actual
product
outside
of
networking
and
some
of
the
other
things.
So
we
have
a
high
level
confidence
that
okd
itself
is
probably
fine
if
we
go
to
an
upstream
version
or
like
until
streams,
or
you
know
something
similar
to
that.
My
concern
is
that
we
will
go
to
a
different
model
of
how
quickly
we
do
things
and
now
we're
going
to
have
so
many
changes.
E
You
know
kind
of
like
we're
doing
in
fedora
between
you
know:
32
33,
34,
35
36,
where
it's
going
to
make
it
hard
for
it
to
be
used
in
a
production
type
of
environment
like
I'm,
using
it
versus
a
lab
or
a
college,
or
something
else
where
people
are
learning
about
openshift.
You
know
technology,
so
there's
my
concern
in
terms
of
you
know
going
to
a
centos
streams
type
of
model.
I
understand
why
red
hat
did
it.
At
least.
E
I
think
I
understand
why
red
hat
did
it,
but
it
really
made
the
community
the
centos
community
unhappy
and
now
that's
why
you've
got
rocky
linux.
F
E
No,
I
understand,
and
like
I
said
you
know,
I
was
a
centos
user
for
a
long
long
long
time.
You
know,
and
that
kind
of
you
know
hit
me
hard
and
still
it
still
bothers
me,
but
I
just
the
reason
I
say
that
is
because
I
mentioned
that
a
year
ago
or,
however,
long
ago
that
this
happened
that
my
worry
was.
This
was
going
to
happen
with
okd.
E
This
is
the
first
time
that
I'm
not
saying
it's
officially
been
said,
but
the
idea
has
been
brought
forward.
You
know
to
model
okd,
you
know
like,
like
you
know,
the
centos
streams
and
daniel.
B
E
G
F
But
there
are
continual
discussions
inside
redhead
about,
like
you,
know
the
best
ways
to
improve
openshift
and
kind
of
the
future
and
whatnot.
So,
like
you
know,
I
well,
I
get
what
you're
saying
and
I
think
in
to
me
in
an
ideal
world
what
we
would
want
out
of
a
situation
like
that
is
kind
of
like
the
best
of
what's
coming
out
of
the
centos
streams.
You
know
thing,
which
is
that
streams
is
like
this
kind
of
bleeding
edge.
Next
rel
that's
coming
and
the
community
can
put
things
in
there.
F
D
So
a
couple
of
things
I
want
to
quibble
since
we're
now
at
quibbling
points.
First
of
all
send
us
stream
not
really
bleeding
edge
and
not
even
like
fedora
leading
edge
or
any
of
that
sort
of
thing
right.
That's
it
it's
no
particularly
worse
than
what
happens
that
you
get
that
real
minor
release
three
months
four
months,
six
months
from
now
right,
that's
how
that
works.
The
second
point
of
of
order
really
is.
D
We
have
always
been
this
way,
even
if
we
haven't
tacitly
acknowledged.
We
haven't
really
explicitly
acknowledged
this.
The
the
centos
stream
model,
as
it
were,
is
essentially
how
okd
operates.
Now
we
basically
take
what
red
hat.
D
Does
we
spiff
it
up
with
a
alternate
logo,
push
it
out
with
a
f
cause
underneath
it
instead
of
an
r
cause,
and
we
kind
of
call
it
a
day
that
that's
pretty
much
what's
happening
now,
and
the
main
point
of
difference
between
okd
and
ocp
is
that
where
the
version
numbers
track
so
like
okd
right
now
is,
I
think,
going
to
be
tracking
to
411
and
ocp
is
just
about
to
track
on
to
so
we're
already
in
that,
like
okd,
is
the
next
minor
version
of
ocp
thing,
the
the
continual
integration
of
container
technologies
and
such
and
especially
trying
to
get
more
kubernetes
zee's
stuff.
D
You
know
bettered
has
necessitated
using
f
cause
as
the
base,
rather
than
building
a
cent
cause
or
whatever
you
want
to
pervert
words
into
making
a
centos
version
of
choreos,
like,
though
that
is
already
today
formalizing.
That
structure
makes
it
easier
to
make
the
engagement
more
positive
between
red
hat
engineering,
red
hat
product
management,
technical
marketing
and
the
community,
because,
right
now
the
situation
is
we
all
just
don't
talk
to
each
other
and
we
pretend
we
don't
exist
and
that's
pretty
bad
like
being
involved
in
centos
stream.
D
Now,
like
I
I'm
a
member,
I'm
not
in
red
hat,
I
don't
know
people,
I
don't
know.
What's
going
on
in
the
internal
discussions
the
minutiae
of
what
goes
on
inside
of
red
hat,
I
know
some
people
claim
to
think
I
work
for
red
hat
or
do
whatever,
but
I
promise
you
I
never
have.
I
don't
even
know
if
it
ever
will
happen,
but
I
can
say
this
much
that
centos
stream.
D
I
was
one
of
those
people
that
pushed
very
hard
on
the
centaur
stream
concept
even
before
it
existed
like
when
red
hat
acquired
the
census
project,
to
revive
it
from
its
like
half-broken
state
that
it
was
before
it
was
something
that
I
talked
to
a
lot
of
red
hat
enterprise
linux
product
managers.
D
About
like,
I
want
a
way
for
this
to
be
a
thing,
because
y'all
pushed
out
two
point
releases
that
broke
all
of
my
servers,
because
you
didn't
test
amd
stuff
enough
to
make
sure
that
you
didn't
break
them
and
I
had
to
like
hold
back
real
minor
releases
and
the
the
faces
that
they
made.
When
I
said,
I
had
to
hold
back
rel
minor
releases
because
they
because
of
you,
know
actual
faults
in
the
software.
D
I
think
drove
the
point
home
that
something
like
this
needed
to
exist
and
when
rel
9.0
gas
in
a
month
and
a
half,
I
think
people
are
going
to
be
surprised
at
how
up
to
snuff.
It
is
immediately
out
of
the
door
with
the
collection
of
apple
with
all
the
software,
with
all
the
hardware
testing
and
all
the
usage
that
has
happened
from
having
six
six
months
to
a
year
of
existing
as
centos
stream.
D
Nine
ahead
of
time
right,
like
that,
that's
a
huge
win
that
I
want
to
replicate
for
openshift,
and
I-
and
that
is,
I
think,
where
we
should
move
our
north
star
towards
and
I
think,
for
red
hatters,
like
el
mico.
Bro
and
and
others
I
think,
that's
a
productive
point
to
go
towards
when
you're
talking
about
how
in
the
world
we
want
to
make
okd,
viable,
successful
and
interesting
to
red
hat
and
the
community.
F
A
Well,
this
has
been
a
great
conversation.
I
think
we
covered
a
lot
of
ground.
It
sounds
like
first
and
foremost,
we
want
a
contributor's
guide
that
includes,
as
its
first
chapter
sort
of
an
overview
of
the
infrastructure
and
how
it
works.
The
build
process
overall
and
then
chapter
two
is
our
first
goal,
which
it
seems
like
we
sort
of
agreed
upon,
is
building
components,
successfully,
building
components
and
integrating
them
as
being
a
first
step
to
really
being
contributors
to
it,
and
so
does
that
sound,
like
a
game
plan.
A
Moving
forward
that
the
docs
working
group
can
start
on
that
next
week
is
basically
create
a
template
and
start
asking
questions
to
fill
out
that
template,
so
that
we
have
a
the
first
two
chapters
of
a
contributor's
guide.
B
A
That's
what
I
mean,
that's
what
I
mean
actually
that
that
would
be,
but
but
chapter
one
would
be
like
what
is
everything
like?
How
is
it
all
connected,
like
just
sort
of
an
overview
of
the
of
the
build
process,
to
even
know
that
there
is
this
thing
out
there
that
you're
taking
the
whole
of
and
then
inserting
a
component
into.
F
I
mean
it
does
make
sense.
I
just
dropped
a
link
in
chat
here,
because
this
is
a
documentation
site
that
we
just
launched
that
I've
been
kind
of
leading
the
effort
for
internally,
and
this
is
like
the
documentation
that
we've
been
creating
over
the
last.
You
know,
six
months
to
a
year
when
we've
been
onboarding,
ibm
and
and
alibaba
and
whatnot-
and
this
is
the
documentation
that
we're
gonna,
that
we're
starting
to
show
to
like
nutanix
and
others
for
how
they
would
integrate
like
core
components
into
openshift
like
integrating
new
infrastructure
layer
components.
F
I
don't
think
it's
necessarily
specifically
related
to
like
the
whole
notion
of
the
contributor
guide,
but
I
think
it's
another
window
into
the
type
of
activity
that
someone
contributing
might
want
to
do,
and
it's
got
a
lot
of
links
to
like
prs
from
ibm
and
alibaba
and
how
they
integrated
their
components.
I
think
it's
extra
information
that
would
help
someone
who's
really
trying
to
dive
deep
to
understand
this.
So
I
just
wanted
to
share
it
as
like
one
more
point
to
think
about
as
we're
maybe
assembling
a
contributor
guide.
F
You
know
this
is
more
resource
and
we
plan
to
continue
to
update
those
docs
with
more
information
about
how
to
you
know
how
to
put
these
components
in
so
yeah
just
forget.
I
share
that
all
right.
E
So
jamie
I'll
put
something
together
I
mean
it
sounds
like
I
mean,
except
for
christian,
I
probably
and
obviously
vadim.
You
know.
I've
been
through
this
process
a
couple
of
times
I'll
try
to
get
something,
maybe
in
the
next
week,
depending
on
my
on
my
time
at
least
how
to
do.
It
may
end
up
being
videos
because
a
lot
of
times
videos
are
just
easier
to
do,
but
if
I
can
I'll
try
to
drop
in
on
the
docs
meeting
next
week,
right.
A
Or
touch
base
with
me
and
brian
brian,
and
I
and
just
let
us
know
what
you
have
and
we
can
shape
it
into
something
that
we
can
bring
the
dots
through.
And
I
I
do
have
a.
B
B
E
Yeah,
I
mean
it'll,
probably
be
a
combination
of
I
mean,
like
I
said:
I've
gone
through
this
quite
a
few
times.
What
what
I'll
probably
want
to
do
is
take
two
like
okd
machine
os
and
then
our
our
good
old
friend
mco
and
build
those
two.
Those
are
the
the
two
most
interesting
for
us,
but
the
process
is
the
same
for
console
or
for
auth
or
anything
else.
You
know,
there's
usually
a
build
file
or
a
make
file
or
something
that
you
run.
E
F
Cool
all
right,
I'd
like
to
share
two
more
links
here.
If
you
don't
mind,
yes,
share,
share
away
buddy,
chair
away.
F
F
The
cloud
controller
managers
and
the
second
one
is
for
the
machine
api,
but
the
first
one
has
our
instructions
about
like
replacing
a
component
inside
of
the
inside
of
a
release
image.
So
I
know
john's
gonna,
like
demo
that
and
everything,
but
there's
a
little
pre-canned
text
for
you.
F
If
you
want
something
to
reference
to
go
along
with
what
john's
doing
and
then
the
machine
api
operator,
one
is
all
about
like
hacking
on
the
machine
api
that
might
give
you
a
little
insight
into
how
we
talk
about
contributor
guides
and
kind
of
what
we
talk
about
to
other
people.
You
know
predominantly
red
hatters
who
are
contributing
these
things,
but
I
figured
those
might
be
helpful,
like
as
inspiration
for
what
you
guys
are
doing
yeah.
I
appreciate
you
sharing
fantastic
well.
C
F
A
Thing
that
we've
talked
about
that
we
haven't
done
yet,
and
I
brought
up
even
early
on
in
my
involvement
with
okd
is
we
need
a
list
of
who
has
what
resources
for
testing
and
building
and
whatnot?
So
I
think
the
docs
group
I'll
add
that
to
the
agenda
for
the
docs
group
for
the
next
meeting.
Just
so,
we
get
a
sense
of
the
membership
of
the
okd
working
group
and
surrounding
community.
What
can
people
contribute
in
terms
of
infrastructure,
for
testing
building
etc?
A
Like
I've
got,
you
know,
vsphere
access,
someone
might
have
you
know
alibaba,
someone
might
have.
You
know
whatever,
like
the
more
that
we
can
test
across
the
platforms
and
and
do
builds
on
different
infrastructure.
I
think
the
stronger
will
be
to
contribute
right
and
right.
E
Aws,
that
would
be
aws
resources,
I'd
be
happy
to
test
aws,
but
I
can't
pay
for
it.
On
my
own
hook.
A
Right
and
and
well
so
I
here's
the
thing
I
did
aws
a
basic
okd
in
aws.
It
ran
about
340.
G
A
Worker
nodes
and
your
your
you
know
so
it's
it's
it's.
It's
can
be
kind
of
expensive.
We
might
be
able
to
come
up
with
some
way
of
a
couple
of
companies
contribute
every
month
or
weed
develops.
I'm
actually
involved
in
a
lot
of
community
groups
that
take
contributions
to
do
various
types
of
work
in
my
other
apps,
but.
E
F
Exactly
you
know
like
it
doesn't
always
have
to
be
testing
on
those
specific
clouds
like
if
it's
an
aws
problem,
yeah
you're
not
going
to
be
able
to
solve
it
without
testing
on
aws
yeah.
But
when
I
think
about
what's
going
on
with
the
operate
first
community,
that's
coming
out
of
like
the
cloud
native
computing
foundation
and
red
hat
has
a
bunch
of
inroads
in
with
it.
F
You
know
ci
infrastructure
that
deploys
openshift
using
the
openstack
provider
for
one,
but
then
you
could
also
do
vsphere
installations
on
top
of
openstack.
You
know,
assuming
you
could
you
could
handle
the
nested
virtualization
or
whatever,
but
you
can
see
what
I'm
getting
at
here
like
it
doesn't
always
have
to
be
aws,
gcp
alibaba,
whatever,
like
as
a
community,
we
might
decide
to
choose
to
use
openstack,
because
it's
also
a
community
project
that
we
have
good.
You
know
coverage
on
and
we
have
people
who
can
operate
it.
F
You
know,
I
think
that
really
gets
to
kind
of
the
the
crunchy
granola
side
of
the
open
source
which
is
like
you
know,
we're
collaborating
with
others
and
using
shared
infrastructure
to
do
these
things
and
like
for
me,
that
would
be
like
an
ultimate
kind
of
milestone
to
reach.
It
would
be
tough
to
do,
but
you
know
very
cool.
A
Yeah
yeah,
we
might
be
able
to
do
aws,
I
mean
I'd,
have
to
map
it
out
with,
like
you
know
anyway,
it's
it's
it's
possible
right
and
it's
possible.
I
think
if,
if
we
got
the
community,
everyone
chips
in,
you
know
five
dollars
a
month
or
something
like
that.
Like
you
never
know,
there's
no.
I
mean
I'm
serious,
like
there's,
there's
there's
a
myriad
of
ways
in
which
we
could
like
fun
or
get
donated
stuff
like
let's
not
limit
ourselves
in
any
way
right
right.
F
But
like
if
they
would
support
it,
but
like,
for
example,
if
let's
say
john
is
like
working
for
a
company,
that's
using
okd
or
john
owns
a
company
that
uses
okd
and-
and
they
happen
to
be
using
aws
and
they're,
hitting
this
issue.
Then
it's
like
okay,
if
you
fix
the
issue
on
your
own
deployment
and
then
take
it
back
to
propose
the
code
change
upstream
and
we're
using
at
that
point,
the
community
infrastructure
or
red
hat's
infrastructure
then
like.
I
would
expect
as
long
as
the
test
pass
on
the
ci.
F
A
Yeah,
yeah
and
actually
the
organization
I
work
for
does
have
okd
and
aws
and
okd
and
vsphere,
but
we
need
to
document
who
has
what
and
who
has
access
to
what
to
be
able
to
know
what
we
have.
So
I
think
that's
the
first
step
all
right.
I
want
to
be
mindful
of
people's
time.
It's
three
minutes
after
the
hour.
Thank
you
so
much
for
this
awesome
discussion,
we'll
pick
it
up
at
the
next
meeting.
There'll
be
a
lot
of
stuff
happening
in
between.
A
So
please
check
the
mailing
list
and
the
oh
matrix
I
was
able
to
get
into
matrix.
Other
folks
have
as
well,
so
they
fixed
an
issue
where
the
room
wasn't
visible.
A
Now
it's
visible,
if
you
just
if
you're
in
the
matrix
server,
you
can
now
find
the
room,
so
anyone
that
hasn't
gotten
into
it
just
shoot
a
message
to
me
and
I'll
help
you
get
into
it
because
it
seems
like
we
might
be
having
some
conversation
any
last-minute
thoughts.
Before
I
end
the
meeting.