►
From YouTube: OKD Working Group Meeting 06-21-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
And
don't
forget
to
put
your
name
in
the
attendees
section
just
so
we
know
that
you're
here
attending
section
of
the
meeting.
That's
the
way
we
know
you're
here
we
know
if
there's
something
you
might
have
missed
if
you
weren't
here
and
we
can
reach
out
to
you
in
case.
Maybe
let's
take
a
quick
look
at
the
agenda.
Is
there
anything
that
folks
would
like
to
add
or
change
feel
free
to
do
so?
If
you
want
to
just
plop
stuff
in
there.
A
B
A
All
right,
let's
jump
into
our
agenda
and
release
updates,
like
I
said
we
don't
have
christian
or
vadim
here.
What
I
did
want
to
do
is
bring
up
the
operator
count
question
I
asked
christian
about
this
and
he
looked
and
recently
the
operator
account
hasn't
changed
it's
at
like
150
something,
but
I
remember
it
was
much
smaller
and
bruce.
I
think
you
mentioned
that
you
remember
it
being
much
smaller
in
previous
releases.
D
Yeah
christian
brought
this
up
with
kubecon
because
I
think
something
went
off
on
his
phone
or
whatever,
and
he
noticed
and
looked,
and
there
was
like
a
much
bigger
list.
I
know
they're,
like
cecile,
machado,
who's,
a
red
hat,
employee
who's
been
doing
a
lot
with
the
olm.
I
know
she
has.
She
had
some
explanation
that
seemed
to
satiate
christian's
curiosity,
but
I
just
don't
know
enough
details
about
it
to
remember
what
it
was,
I
would
say,
maybe
reach
out
to
christian
or
next
time
we're
all
here.
You'll.
B
B
On
it,
that's
camilla,
machado,
right,
yeah,
camilla,
sorry,
sorry,
okay,
yeah!
No!
We
can.
I
can
ping
her
and
ask
for
what
was
going
on
so
that
was
yeah.
A
E
Yeah
well,
no,
I
was,
I
guess
I
was
doing
something
on
my
test
cluster
and
which
is
on
4.10
current
version,
and
I
noticed
that
there
were
a
lot
of
operators.
In
particular.
E
The
git
lab
operator
was
one
that
I
noticed,
because
I
had
been
having
difficulties
with
that
from
long
past
and
then
I
looked
around
and
there
were
several
that
were
that
had
been
deleted
going
from,
I
think,
four,
seven
to
four
eight
and
then
I
went
back
on
my
four
nine
cluster,
which
I
had
actually
made
a
note
to
myself
going
operator
by
operator
of
the
ones
that
disappeared
and
most
of
them
were
back,
and
so
it
wasn't
associated
with
an
upgrade
because
my
4.9
cluster
hasn't
been
updated
for
a
long
time.
E
Since
you
know
especially
the
stuff
thing
came
out.
So
something
happened
with
with.
I
don't
know
what
you
know
like.
Maybe
things
made
it
into
the
operator
hub
that
was
being
pulled
down
that
had
disappeared,
and
I
know
that
with
respect
to
the
get
lab
runner
one
specifically
when
it
disappeared,
and
I
asked
some
questions
vadim
and
said:
oh
well,
it
was,
it
was
wasn't.
Currently
compatible,
so
that
seemed
like
a
logical
reason
for
its
disappearance,
but
anyway,
so
that's
just
history.
E
It
doesn't
shed
a
whole
lot
of
light,
but
you
know
I
just
well.
I
mean
that
the
ones
that
I
really
care
about
so
like
all
the
ones
that
would
allow
you
to
get
ops
are
not
there,
okay
and
but,
but
still
it's
a
big.
I
mean
it
is
a
big
plus.
Yes,.
A
It
anecdotally,
all
I
know,
is:
I
did
a
there-
was
a
4-8
install
a
while
back
like
last
fall,
and
I
remember
that
there
were
only
like
40
something
or
maybe
it
was
like
in
the
early
50
operators
and
now
looking
at
a
a
four
eight
that
was
upgraded
to
four
nine
recently,
but
I
didn't
notice
it
in
the
upgrade
it
now
has
152
or
whatever
that
that
higher
number
is,
and
it's
like
aws
operators
and
all
sorts
of
stuff
that
was
not
there
before.
So
it's
pretty
snazzy,
it's
pretty
cool.
A
We
might
want
to
give
that
a
little
bit
of
promotion
if
we're
sure
that
that's
something
that's
going
to
stay
around,
we
should
reach
out
to
christian
or
the
other
red
hat
person
if
they
know
specifically
and
find
out
if
this
is
gonna,
it's
gonna
stay
like
this
for
a
while
and
then
maybe
sort
of
promote
that
sorry,
you're
muted.
I
am.
B
I
am
I'm
always
muted.
I've
got
a
cold
again
from
traveling,
not
covered,
which
is
just
a
cold.
This
time
I
will
reach
out
and
start
a
conversation
with
camilla
and
christian
and
get
to
the
bottom
of
it
and
find
out
if
it's,
if
it's
a
permanent
upgrade
or
if
it's
going
to
disappear
at
any
time
soon,
and
let
you
know
and
and
have
one
of
them
send
a
post
to
the
mailing
list.
Is
there
a
discussion
started
about
it
already.
A
B
And
if
you
tag
me
in
it,
then
then
I
you
know,
then
we
can
see,
because
if
it
is
hopefully
it
is,
there's
also
a
lot
of
work
going
on
in
the
background
around
because,
as
as
we
all
know,
vadim
has
gotten
busy
with
with
a
new
promotion,
doing
other
things.
So
there's
a
trio
of
customer
facing
engineers
who
are
taking
on
learning
and
building
out
the
ci
cd
process,
and
I
have
a
meeting
which
jamie
I
may
try
and
get
you
in
I'll
have
the
first
one
with
them.
Fabiano
franz
who's.
B
An
awesome
awesome
person
is
is
leading,
is
managing
that
initiative
with
the
customer
facing
engineers
and
he's,
I
think,
he's
down
in
brazil
somewhere
but
you'll
like
him,
we'll
all
like
him.
I'm
gonna
try
and
get
them
to
start
coming
to
the
working
group
meeting
and
they're
going
to
work
on
the
ci
cd
pipeline
for
okd
and
take
the
learnings
that
vadim
had.
B
This
is
one
of
the
many
conversations
that
are
going
on
about
how
do
we
resource
the
build
process
here
inside
of
red
hat,
and
hopefully
we
can
get
them
to
show
up
at
the
working
group
meeting
and
tell
us
what
they're
thinking
and
get
their
feedback
on
it.
I'm
hoping
for
the
next?
Not
this
not
the
docs
week,
but
in
two
weeks
time
to
have
some
of
them
on
yeah
and
get
them
to
start
coming.
A
B
D
I
I
vaguely
remember
like
I
was
talking
with
christian
and
he
looked
down
on
his
phone
and
because
someone
said
oh
there's
like
160
operators
in
the
catalog
now
he
thought
that
something
must
have
happened
that,
like
accidentally
brought
them
in
so
he
started
reaching
out
and
I
thought
he
watched
he
re.
He
spoke
with
camilla
and
it
was
like
whatever
the
result
of
that
conversation
was.
It
was
like.
Oh
it's
supposed
to
be
like
this,
so
yeah,
I'm
not
sure
what
the
detail
was,
though,.
A
Yeah
so
well
we'll
find
out
so,
but
I
I'm
not,
I
know
I'm
not
the
only
person
who
noticed
that,
after
an
okd
install
of
like
four
or
eight
or
whatever,
there
was
like
a
woeful,
woefully
small
number
of
of
operators
like
40,
some
odd
or
50
some
odds,
so
something
something
happened
somewhere
all
right,
so
bruce
is
going
to
create
a
discussion
item
and
tag
diane,
and
if
you
could
tag
me
as
well-
and
so
that's
is
there
anything
else,
okay,
release
oriented
that
folks
wanted
to
talk
about
before
we
move
on,
even
though
we
don't
have
any
of
our
redhead
engineers
here,
I
think
folks
want
to
discuss.
A
Okay
moving
on
now
to
f
cos,
updates
timothy.
F
So
I've
put
in
the
links
in
the
agenda
the
main
that'll
happen
that
are
happening
right
now
in
federal
questland,
and
that
should
impact
okg.
Oh
the
first
one
is
about
the
the
fact
that
we
are
making
the
adding
spot
in
ignition
to
remove
ignition
configs,
vmware
and
virtualbox
platform
by
default.
F
So
if
you
had
a
posted
announced
announcements
for
that,
one,
yes,
but
essentially
there
is,
if
you,
if
you
have
an
english
config
on
those
platforms,
every
unprivileged
user
even
continues
can
access
them.
So
if
you
saw
secrets
in
those
it's
not
great
because
they
can
read
them,
so
this
does
not
directly
impact
ocp
because,
as
far
as
I
know,
I
think
most
of
the
use
case
in
the
cps.
You
don't
have
directly
secrets
into
the
initial
engine
config
they
are
fetched
from
the
mceo
mcs,
so
and
pods
don't
have
containers
on
okg.
F
You
don't
have
access
to
this
server.
They
have
blocked
the
firewall
level,
so
yeah,
but
still
it's
not
that
great.
So
we're
removing
that
from
those
platforms
and
but
we're
not
removing
that
from
other
platforms.
Yet
because
we
don't
have
a
solution
for
everybody.
Yet
so
it's
just
a
start,
so
maybe
there
would
be
some
further
change
down
the
road
for
for
this
one,
but
we'll
see
how
it
goes.
F
The
second
one
is
about
the
nutanix
artifact,
so
that
only
ever
impacts
you
if
you're
using
the
new
nutanix
platform,
which
was
fairly
recently
added,
I
think,
a
couple
of
weeks
or
months
ago,
and
essentially
we
changed
the
way
we
should
be
after
federal
course,
images
for
nutanix
instead
of
shipping,
something
compressed
after
the
fact.
We
should
be
image
directly
compressed.
F
It's
just
a
change
of
format.
It
should
not
impact
anything
else
and
yeah.
Essentially,
it
should
make
your
life
easier
if
you're
using
the
nutanix
platform,
so
hopefully
that
helps
the
last
one
I
want
to
bring
up
is
this
last
issue
here
is
is
an
issue
about
the
way
we
grow
our
fire
system
by
default
for
the
node.
F
So
when
you
have
a
federal
course
image,
essentially
it
starts
really
small,
and
then
it
takes
up
all
the
space
on
the
node
that
it
has,
but
essentially
doing
that
with
excess,
but
well
with
almost
any
file
system
works.
Well,
only
if
you
use
a
rather
small
image,
so
let's
say
if
you
start
from
10
gigs
and
you
go
to
100
gigs,
that's
okay,
but
if
you
go
to
one
terabyte,
for
example,
that's
start
getting
messy,
because
the
file
system
is
that's
supposed
to
be
this
much
from
such
a
small
image.
F
I
want
to
focus
here
this,
that's
something
that
we
don't
have
a
fix
right
now
for
this,
but
essentially
the
the
right
way
to
do
things
is,
if
you
have
such
large
disks
on
your
node,
is
to
use
multiple
partitions
and
that's
what
we
recommend
and
I've
added
the
link
to
the
exact
part
of
the
ocp
documentation
or
qd
documentation
that
helps
you
set
up
machine
config
to
have
separate
partitions
to
actually
store
your
data,
which
completely
works
around
this
specific
issue
and
that's
the
recommended
way
to
do
things.
F
579,
it
should
be
in
testing
soon.
Well
it
it
will
be
an
f
course,
but
would
it
be
no
kidding
that's
another
question
so
totally
so
fedora's
35?
Yes,
it
seems
35,
so
5
17
9
right.
F
That
depends
if
we-
but
I
don't
remember
exactly
which
version
the
next
next
build
of
okay
will
be
based
on,
is
the
switchband
for
this
one
for
the
next
one.
Well,.
E
Next
in
testing
are
both
on
36
stable
is
on
35.
F
F
F
It's
in
is
it
in
the
latest
thing:
testing
devil.
So
it's
either
in
this
one
or
next
one.
It's
in
this
week's
testing
release,
okay,
yeah
yeah,
so
we'll
be.
A
66
excellent-
and
this
is
going
to
be
more
helpful
as
time
goes
on
because
as
we
try
to
do,
okd
builds
of
our
own
and
testing
and
testing
with
our
own
versions
of
fcos.
Ideally,
I
think
that
this
type
of
information
will
become
very
important
and
for
okd
word
group
members
to
be
more
aware
of
what's
happening
in
the
three
f
cost
streams
for
sure
right.
Anything
else
in
terms
of
f
cost
stuff,
all
right.
A
Let's
move
on
to
documentation,
documentation,
stuff
brian
is
not
here
today,
but
I
can
fill
you
in
on
some
of
the
stuff
that
we
have
so
when
we
met
last
week,
brian
mentioned
that
he
has
now
merged
in
okd
development.
A
It
was
sort
of
in
a
separate
clone
of
the
repo
that
he
was
working
on
with
a
couple
other
folks.
It's
now
been
merged
into
the
website.
So,
if
you
look,
the
second
to
last
link
on
the
website
is
okd
development
and
it
talks
about
basically
modifying
okd
release,
troubleshooting
things
of
that
nature.
I'm
not
not
all
of
it's
filled
in
yet,
but
basically
this
is
going
to
be
where
we
start
talking
about
building
okd
our
cell
for
modifying
okd,
getting
those
images
etc.
A
There's
a
great
conversation
that
bruce
and
who
else
it's
so
it's
it's
you
bruce
and
vadim
and
john
and
there's
a
couple
of
people
on
this
yeah
john
started.
It.
A
Right
exactly
so
so
john
fortin
started
a
discussion
thread
that
folks
should
check
out
in
the
repo
that
is
about.
If
I
wanted
to.
If
any
of
us
wanted
to
build
okd,
where
do
we
find
the
right
images
which,
which
registry
are
we
going
to,
and
is
it
the
same
for
all
of
the
components,
etc,
etc?
And
where
do
we
find
the
source
for
those
components
so
that
we
can
actually
provide
feedback
directly
to
those
components?
A
And
so
it's
a
great
thread
I'll,
put
a
link
in
the
meeting
notes
to
it
check
it
out,
because
vadim's
really
been
doing
he's
chiming
in
when
he
can-
and
it's
been
very
helpful
and
christian
has
chimed
in
as
well
with
that.
But
that
will
be
our
that
will
help
form
the
foundation
of
the
documentation
section
informing
stuff
about
actually
building
okd
in
the
community.
A
Let's
see
the
working
group
link
in
the
okd
website
has
changed.
It's
now,
okd
working
group
at
the
top
level
and
then
there's
about
charter
minutes
and
then
subgroups
and
the
subgroups
link
goes
to
the
individual
subgroups
that
we
have
going.
A
Let's
see,
I'm
working
on
something
that
explains
the
release
process
and
how
we're
not
going
to
be
releasing
4.9
any
iterations
of
4.9,
because
okd
has
been
up
to
this
point
a
once.
We
release
a
next
minor
version.
All
efforts
go
towards
that
next
minor
version
and
there's
no
maintenance
releases
for
I'm
writing
up
trying
to
find
a
good
way
to
explain
that
steph
testers
crc
we're
talking
about
that
twitter.
A
B
Yep,
apologies
for
all
the
delays,
but
I
did
find
the
problem
with
twitter.
Is
you
need
to
have
a
red,
hatter
email
address
that
is
going
to
be
not
change
jobs
and
it
needs
to
be
a
human
being.
It
can't
be
like
a
a
shared
email
address
within
red
hat,
and
I
did
find
karine
collis,
who
was
it
in
the
openshift
bu
in
marketing?
Who
will
own
it
for
us
she's?
B
Also,
the
person
responsible
for
all
social
media
for
openshift,
openshift
commons
and
owns
the
other
ones
too.
So
jia
said
yes,
we
just
now
have
to
figure
out
how
to
swap
the
emails
out
and
get
twitter
to
release
it
to
her
and
then
she'll
share,
whatever
password
username
password
with
myself
and
jamie,
and
if
someone
else
comes
up
and
wants
to
be
the
social
media
manager
that
person
too.
B
But
she
also
will
be
able
to
do
some
tweets
for
us
when
we
need
them
like
when
we
do
events
or
things
so
that
and
she's
promised
me
that
she's
going
to
stay
forever.
B
She
loves
her
job
and
she's
promised
so
the
problem
with
engineers
is
they
get
good
at
their
jobs
and
they
get
promoted
so
a
proponent
of
that.
But
we
need
people.
B
Address
stay
stable
for,
and
you
should
now
have
the
youtube
back.
They
were
doing
some
spring
cleaning
on
all
of
the
youtube
openshift
channel
admins
and
you
got
swept
out
in
the
cleanse.
B
Because
I
just
don't
want
to
be
doing
that
again
so
yeah,
that's
that's
the
social
media
update.
A
Excellent,
thank
you.
Diane
survey,
stuff
link
is
to
the
survey.
We
do
need
folks
to
provide
some
feedback
on
the
survey
and
help
us
make
it
good.
We
do
have
a
deadline
of.
We
want
to
get
it
out
june,
1st
ish,
and
we
also
we
want
to
start
the
transition
and
have
that
the
repo
transition
start
and
be
completed
by
july
1st,
so
we're
actually
starting
in
the
docs
group,
to
create
some
deadlines
to
get
things
done.
A
G
A
Look
at
the
survey
there's
a
link
in
the
in
the
meeting
notes
if
you
look
at,
if
you
think,
there's
some
questions
that
maybe
we're
missing
or
if
it.
If
a
question
isn't
clear
or
something
like
that.
Let
us
know
because
we
want
to
have
a
and
then
and
then
we're
going
to
release
the
survey
on
june
1st
to
people
in
the
community.
A
A
A
A
What
was
the
other
thing
that
was
getting
here?
Oh
so
there
was
some
discussion
about
diane.
Maybe
this
answers
somewhat
answers
the
question,
but
what
you
said
earlier
maybe
answers
this
question,
but
is
it
possible
for
the
okd
working
group
to
convince
the
dns
administrator
administrators
at
red
hat
to
put
different
mx
records?
Mx
records
are
what
point
to
a
mail
server
and
say:
oh
the
mail
server
for
this
domain
is
such
and
such.
B
If
you,
if
you
could
also
I'm
going
to
just
keep
pushing
to
this,
if
you
can
write
that
up
in
the
discussion
and
tag
me
and
then
I
will
see
what
I
can
do,
if
I
can
work
any
magic,
I
have
seen
it
done
for
other
projects,
so
it
might
be
possible
and
it
might
be
a
good
way
of
managing
some
of
our
issues.
A
A
A
Is
the
way
things
are
right
now
I
don't
have
access
to?
No
one
outside
of
diane
has
access
to
the
recordings
until
she
forwards
them
on,
so
we
can't
actually
post
them.
There's
some
technical
limitations
with
zoom
everyone
that
I've
talked
to
seems
to
be
have
more
meetings.
A
B
I,
for
one
would
love
to
get
out
of
blue
jeans
and
over
to
zoom
it's
just
a
matter
of
creating
a
you
know,
getting
an
account
that
is
available
to
us
to
use
and
yeah.
I'm
I'm
I'm
game.
If
you
all
are.
C
All
right,
I'm
gonna,
speak
now,
because
this
one
is
something
I
care
a
lot
about.
Having
fought
all
the
platforms
all
the
time
I
am
in
favor
in
order
of
usability
ease
preference,
whatever
you
want
to
go
with
zoom
jitsi,
google
me
you
can
whatever
order
you
wanna,
you
wanna!
Think
of
that
in
that's.
That's
basically
the
three
that
so
far
I
have
had
a
reasonable
experience,
dealing
with
them
on
linux
and
on
windows
and
on
mac,
os
and
and
at
work.
I
have.
I
have
zoom
conference
system.
C
A
All
right,
I
see
some
some
chat
or
folks
wanna
talk
in
over
the
air
about
what
your
thoughts
are.
D
I
was
just
saying
I
don't
I
don't
have
any.
I
think
changing
platforms
is
fine.
No,
no
objection
for
me.
I
think
it'd
be
cool
to
use
an
open
source
platform
like
jitsi.
If
we
could,
but
you
know
I
don't
know,
I
don't
have
really
strong
feelings
about
the
platform
we
choose.
B
Anyone
else
I
just
want
something
I
can
use
on
any
of
my
devices
so
and
it's
not
blue
jeans,
though.
A
Yeah,
recording
is
key,
so
neil,
I
think,
was
neil
that
yeah
neil
points
out
that
recording
agency
is
a
pain,
that's
kind
of
one
of
the
things
we
want
to
get
around
is
we
want
to
have
recording
and
posting
as
easy
as
possible
so
that
our
recordings
are
available
quickly
to
the
community
google
pay
for
recording.
Now
with
google,
I
thought
you
had
to
pay
now
for
to
get
a
paid
version
to
record,
but
I
could
be
wrong.
I
don't
know.
C
You
can
everyone
can
do
meetings,
but
only
people
who
have
paid
accounts
can
do
recordings
right
right.
That's
also
true,
with
zoom
for
what
it's
worth
you,
don't
you
can't
do
cloud
recordings
without
a
paid
account.
That
being
said,
I
am
very
aware
that
our
lovely
sponsor
has
both.
So
those
are
both
equally
valid
options
for
us.
B
So
is
there
any
objection
to
us
attempting
to
create
these
meetings
in
zoom?
B
If
I
do
the
do
some
background
work
and
see
if
I
can
get
an
account
that
the
jamie
again
like
yeah
cool,
let
me
see
it
may
not
happen
right
away
because
nothing
happens
fast.
B
But
let
me
see
if
there
is
a
red
hat
zoom
account
that
we
can
hijack
and
use
and
that
jamie
can
also,
as
an
external,
have
access
to
that's
always
been
the
issue
and-
and
I
and
I
really
want
to
have
it
something
that
an
external
person
with
a
non-red
hat
email
account,
can
boot
up
the
the
meeting.
So
it's
not
not
me.
It's
not
me
all
the
time.
A
Well,
and
with
zoom,
you
can
do
the
you
can
add
someone
as
a
secondary
right
yeah
and
you
can
start
the
meetings.
The.
C
A
C
B
Let's
put
it
on
the
agenda
for
the
docs
meeting
next
week,
give
me
until
next
tuesday
to
do
a
little
bit
of
research
and
let's
get
that
we've
got
the
youtube
the
twitter
figured
out
and
let's
get
the
zoom
thing
going
because
much
as
I
love
blue
jeans,
not
it
would
be
wonderful.
B
Next
week,
and
then
we
just
have
christian
to
change
the
fedora
calendar
involved.
I
have
access
to.
E
B
A
All
right
sounds
good,
so,
let's
now
move
on
to
plan
for
docs
update
issues,
repository
transition
survey,
rook
cef
status-
I
don't
think
there's
anything.
That's
changed
with
with
john's
bugzilla
discussion,
one
two
three
one.
I
don't
know.
E
A
E
I
just
sort
of
wanted
to
bring
up
one
thing
related
to
that
which
didn't
appear
in
the
discussion,
because
it
was
a
little
bit
longer
like
vadim
made
the
comment
that
you
could
just
try
replacing
some
of
the
base
images
with
an
open
source
one,
but
it
sort
of
seemed
like
we
did
have
an
action
item
a
long
time
ago
with
christian
to
go
through
and
look
at
that
to
me
the
issue
is
not
just:
can
you
replace
a
base
image
and
it
sort
of
seems
to
work,
because
you
haven't
quite
stumbled
into
the
area
where
it
doesn't
it'd
be
more
useful
to
know
what
spec,
what
specific
red
hat
proprietary
packages
were
in
the
proprietary
base
image
right
and
if
there
are
none,
then
you
could
presumably
safely
change
it.
A
Timothy
is
being
passionate.
What
what
can
you
say.
F
C
Think
the
more
accurate
term
it
is
because
some
of
the
content
is
subscription
encumbered
and
that
actually
might
be
the
problem.
I
don't
think
any
of
the
ocp
containers
use
any
of
that
stuff
anymore.
I
think
they've
all
moved
to
rel
ubi
quite
some
time
ago
and
just
tried
to
stop
using
base
rail
content,
but
one
of
the
things
I'm
not
entirely
certain
of
is
if
the
the
build
engine
thing
has
ensured
that
rel
content
is
disabled
during
the
build
process
to
make
sure
that
that
stuff
doesn't
leak
in.
C
If
that
hasn't
happened,
then
it's
entirely
possible
through
nobody's
fault,
that
there's
subscription
encumbered
content
inside
the
images
something
that
I've
done
at
my
workplace
was
our
rel
uvi
face.
Image
basically
inherits
from
the
main
one
and
the
first
thing
it
does,
and
really
the
only
thing
it
does
is
turn
off
subscription,
manager's
plug-in
so
that
it
cannot
actually
access
the
encumbered
stuff.
Because,
if
subscription
manager
detects
an
entitlement
on
the
in
in
the
environment,
it
will
overwrite
the
repos
and
replace
it
automatically
with
real
real
repos.
D
E
All
right
right!
Well,
I
guess
I
guess,
if
the,
if
all
of
the
the
stuff
that
we
can
access
to
build
things,
the
in
the
initial
you
know
from
image
is
a
gated
resource
that
yeah
we
can't
access
that
login
yeah.
D
D
Some
teams
have
not
created
multiple
docker
files,
so
I
have
a
feeling
we
probably
just
need
to
audit
it
and
go
through
and
figure
out
which
ones
are
still
using
the
gated
build
file
and
then
just
propose
like
well
what
our
team
maintains
is
like
a
dockerfile.rel
and
then
like
a
regular
docker
file.
The
community
would
use
like
my
personal
preference,
is
to
see
more
teams
do
this
internally,
where
we
have
a
docker
file,
that's
a
community
docker
file
and
a
docker
file.
That's
like
you
know
our
build
docker
file.
D
As
far
as
I've
seen
every
component
I've
come
across.
You
can
just
swap
the
from
line
to
the
open
builder
and
they
work
the
same.
Basically.
A
Okay,
all
right!
Well,
let's
I
think,
as
we
get
more
into
the
engineering
bits
of
trying
to
build
our
own
okd
out
in
the
community,
we'll
run
across
that
stuff
right
as
timothy
points
out,
you
can
use
option
from
with
podman.
A
Let's
now
move
on
to
crc
or
I'm
sorry,
it's
no
longer
crc.
It's
now
openshift
local
bruce!
You
noticed
this.
I
think
initially
before
I
didn't
go
ahead.
E
Yeah-
and
I
I
noticed
that
I
guess
last
week
when
I
was
looking
at
some
video
that
I
got
from-
I
don't
even
know
where.
H
B
E
But
I
think
you
had
to
go
through
the
you
know
like
the
developer
log
in
to
get
to
it,
so
it
may
not
have
been
public
at
that
time
like
a
month
ago,
but
yeah.
It's
now
made
into
a
number
of
public
places.
B
Yeah
I
saw
that
the
info
week
or
whatever
right
yeah
branding
at
red
hat,
has
never
been
our
forte.
So.
E
Right
yeah,
the
the
info
world
one
was
was
recent
and
the
there
is
a
article
on
the
red
hat
developer.
What's
new
in
openshiftlocal.2.
A
So
here's
the
question
for
the
group:
there
is
discussion
happening,
there's
that
discussion
thread
I'll
link
it
in
the
meeting
docs.
There
is
a
discussion
thread
with
charo
and
a
few
other
people
about
who's,
going
to
help
out
with
building
crc
or
okay.
Here's
the
question.
So
where
do
we
go
from
here
right?
Do
we
assume
that
it's
going
to
be
okd
local,
or
do
we
come
up
with
another
name,
because
we
will
be
building
this
ourselves?
A
B
So
this
is
the
question
I
think
the
last
we've
been
going
around
a
little
bit
in
circles
around
code
ready
containers,
regardless
about
whether
there
is
a
demand
for
it,
and
I
think
there
were
three
people
who
came
on
a
call
or
on
the
mailing
list
at
some
point
a
month
or
so
back
are
any
of
those
three
people
on
this
call
who
actually
use
code
ready.
Containers
bruce
is
that
you
were
you
one
of
them.
E
Yeah,
no,
I
don't
use
it.
I
have
built
it
once
and
I
have
downloaded
the
charo's
version
once
and
the
red
hat
version
a
couple
of
times,
but.
A
Yeah
we
get
discussion,
items
and
questions
from
people,
there's
a
couple
of
discussion
items
that
have
been
created
and
a
couple
of
people
asking
in
the
channels,
but
when
it's
supposed
to
then
that
they
help
build
it,
they
are
not
not
offering
time.
E
Yeah
I
haven't,
I
did
actually
volunteer
at
one
point,
to
be
on
a
working
group
looking
at
that,
but
that
was
mainly
with
the
interest
of
slimming
it
down
to
where
it
was
sort
of
reasonable
that
somebody
might
actually
be
able
to
use
it.
G
B
So
the
reason
I
I'm
pushing
this
envelope
is
because
we
have
a
few
things
coming
up
on
our
radar
around
the
ci
cd
community,
build
process
for
okd
itself,
and
I
think
initially
I
was
the
one
that
pushed
for
getting
a
community
build
process
for
crc
on
the
operate
first
cloud
and
at
after
some
conversations
in
kubecon
last
week
in
spain
and
as
as
mike
says,
micro
shift
is
the
new
hotness.
B
It's
new
and
small,
it's
not
really
openshift,
but
it
does
have
some
okd
in
it,
but
they're
just
using
okd
they're,
not
really
it's
not
the
full
thing.
So
it's
not
quite
the
same
thing,
but
I
don't
don't
feel
like
there's
any
real
pent-up
demand
for
us
to
do
that
and-
and
you
know,
maybe
if
we
could,
if,
if
charo,
can
get
one
more
build
out,
that's
there
and
do
a
little
publicity
about
it
to
see.
B
If
anyone
and
some
gate,
I
don't
know
how
to
gatekeep
an
open
source
project
well
enough
to
see
if
anyone's
downloading
it
or
anything.
I
I
don't
see
that
that's
honestly,
where
we
should
be
putting
any
energy
into.
We
have
a
bunch
of
other
stuff
coming
up,
so
you
know-
and
that's
so
I
would
be
okay
with
tabling
for
now
and
focusing
on
other
things,
but
saying
that
not
saying
we're
sun
setting
it
or
anything,
but
you
know
to
host
it
and
have
nobody
use.
It
is
a
lot
of
work.
A
I
think
the
one
advantage
that
I
saw
to
it
is
whether
it
was
going
to
be
the
the
place
where
you
were
suggesting
or
that
you
know
I
was
going
to
use
it
myself,
even
as
a
test
for
automation
of
building
okay
stuff.
There
is
some
advantage
to
that
as
it
being
like
a
test
case
for
things
like
that,
but
are
five
users
representative
out
of
the
okd
community,
of
a
need
to
keep
it
going.
B
Yeah
and
I
think
the
reason
I
put
the
operate
first
thing
as
the
next
topic
on
the
list-
is
that,
after
the
conversations
with
them,
I
think
we're
poised
to
rather
than
try
and
do
a
a
proof
of
concept
that
operator
first
will
work
with.
B
The
crc
is
to
actually
do
a
proof
of
concept
with
okd
and
fedora
core
os
on
the
operate
first
cloud,
and
so
I'd
rather
expend
our
energies
and
get
the
operate
first,
engineering
resources
and
brian
cook's
team
who
build
this
who's
building
out
this
new
skookum,
the
icd
process
to
to
work
see
if
we
can
get
it
to
work
on
the
what's
called
the
mass
open
cloud,
which
is
basically
boston,
university's
cloud
that
we
have
we
have
shares
in.
B
I
guess
is
the
best
way
we
can
boot
up
clusters
and
create
pipelines
for
multiple
things,
I'd,
rather
we
and
I'm
going
to
invite
them.
That's
why
I
put
it
on
the
agenda
to
the
next
full
okd
working
group
to
talk
about
how
that
might
look
and
what
what
would
need
to
happen-
and
I
and
I'm
really
glad
that
neil's
here
too,
because
we've
had
this
conversation
about
having
a
community
built,
managed
and
hosted
build
process.
B
And
I
just
think
crc
is-
is
a
red
herring
at
the
point
at
this
point
and
that
we
should
probably
try
and
focus
on
doing
something
with
operate
first
cloud,
because
I
think
I
tried
to
coerce
neil
into
giving
us
some
data
resources.
And
you
know
everybody
else
is
cloud
to
build
it
and
that's.
Why
I'm
really
pleased
that
jack's
here
too,
because
cern
has
been
building
their
own
rolling
their
own
okd
deployment
and
has
their
own
ci
cde
process
for
building
okd
with
for
running
on
openstack
turn
style.
B
B
H
B
B
I
know
I
keep
saying
l
michael
but
mike
and
a
number
of
other
folks
at
kubecon
last
week,
and
then
I
talked
to
brian
cook,
who
is
the
actually
the
engineer
at
red
hat,
managing
the
cicd
revamp
if
you
can
build
build
service
as
a
managed
service
which
we
could
host
on
this
operate.
First
cloud,
or
maybe
on
amazon,
depends
where
this
so
to
get
brian
to
come
and
talk
about
what
it
would
take.
B
B
I
would
do
anything
at
this
point,
and
so
I
I
wanted
to
see
if
we
could
use
the
next
meeting
to
talk
about
this,
because
you
know
I
wave
my
hands
a
lot
and
talk
a
lot,
but
I
would
rather
get
the
engineers
who
are
building
the
process
out
in
the
open
and
talking
to
us
and
then
there's
another
build
process,
which
is
the
current
one.
B
That's
we
use
for
building
ocp
and
everything
else
and
there's
a
group
of
those
customer
facing
engineers
who
are
doing
a
three
a
three
a
six
week,
sprint
to
build
to
take
on
what
vadim
has
been
doing
already,
so
not,
but
it's
still
behind
the
red
hat
firewall,
but
that
the
issue,
one
of
one
of
the
many
issues,
is
that
right
now,
red
hat
is
entirely
responsible
for
building
okd.
B
I
would
really
love
to
see
it.
Community
managed
and
community
hosted
somewhere
on
an
open
cloud
so
and
there
is
an
initiative
there.
So
that's
what
I'm
hoping
next
week
we
can
bring
to
the
fold
and
then
what
I'm
also
hoping
with
jack
and
cern,
and
all
that
is,
we
can
learn
from
what
you
guys
did,
and
maybe
you
can
listen
in
on
what
brian
cook
and
those
guys
are
cooking
up
for
the
new
revamped
build
processes
which
is
different
than
the
current
ones.
B
The
current
ones
have
a
lot
of
baggage,
and
maybe
we
can
learn
from
how
you've
rolled
your
own
over
at
cern
and
use
that
to
inform
what
brian
cook's
group
is
doing,
because
they
could
then
just
spin
you
up.
B
Another
pipeline
like
mike,
has
a
project
where
he
wants
a
forked
version
of
okd
for
a
certain
thing
that
he's
doing
so,
we
could
just
build
up
spin
up
more
pipelines
depending
on
what
people
wanted
to
build
in
this
open
cloud
and
learn
from
each
other
and
then
help
brian
cook
improve
what
he's
doing
so.
There's
a
lot
of
synergies
here
and
I'm
going
to
shut
up
now
and
let
you
ask
me
questions
and
then
make
jack
talk
about
what
they're
doing
at
cern.
B
We
would
really
love
to
have
you
talk
to
the
working
group
in
two
weeks
time,
if
you're
willing
to
to
talk
about
what
you're
doing
at
cern
and
how
it
is
and
maybe
give
us
a
little
hint
about
it
right
now,
and
then
we
have
another
gig
coming
up
on
the
23rd
of
june
in
dublin.
That
christian
wanted
me
to
invite
you
to
come
to
to
give
a
talk
about
what
cern's
doing
with
okd
publicly
beyond
the
working
group.
If
you're
available.
G
G
So
so,
basically,
we
are
also
just
taking
okd
as
it
is
on
on
the
github
and
then
replacing
a
few
of
the
operator
images,
mainly
the
ones
that
are
handling
the
integration
with
openstack,
so
we're
not
doing
a
full
custom
build,
but
actually
just
replacing
a
few
of
the
key
components.
And
the
reason
for
that
is
that
the
openstack
cloud
that
cern
has
is
well
rather
old,
because
cern
was
one
of
the
main,
also
contributors
to
openstack
and
developed
it
over
time.
G
G
So,
and
for
that
reason
we
we
started
out
with
having
to
to
fork
two
of
the
images,
so
that's
the
cluster
api
provider
for
openstack
and
the
machine
config
operator,
so
that
we
can
just
basically
adjust
for
those
for
those
differences
and
in
the
end,
it's
just
commenting
out
a
few
lines
of
go
code
in
there.
G
Maybe
making
some
some
different
calls
and
that's
it
so
really
nothing
fancy,
but
we're
also
really
trying
to
keep
it
at
a
minimum
so
that
we
don't
introduce
huge
deltas
to
upstream
that
then
we
need
to
port
to
each
ovd
and,
from
my
point
of
view,
that
has
been
working
fairly
well
much
better
than
I
would
have
expected
and
in
fact
we
became
pretty
comfortable
with
this
approach.
So
now
we've
actually
extended
it
also
to
the
cluster
ingers
operator,
because
that
one
is
at
least
in
my
opinion,
fairly
limited.
G
If
you're
deploying
an
open
stack
like,
for
example,
it
does
not
have
a
proper
integration
with
with
load
balancers,
it
doesn't
really
know
what
to
do
with
them
or
that
it
should
configure
the
external
load
balancer
to
speak.
The
proxy
protocol,
which
is
important
if
you
want
to
preserve
the
client
ip
address
so
some
some
kind
of
well
in
the
end
again
minor
changes
like
this,
but
that
are
just
really
huge
because
well,
we
want
to
know
from
where
clients
are
connecting
and
we
want
to
have
that
in
our
access
logs.
G
So
that's
just
an
absolute
must-have,
and
so
so
we
are
just
basically
replacing.
G
I
think
it's
in
total
at
the
moment,
like
four
images
that
that
we
are,
we
are
building
ourselves
where
we
also
coming
back
to
the
issue
that
was
discussed
before
that
some
of
the
from
images
in
the
docker
files
are
not
publicly
available,
but
instead
we
just
swapped
out
the
ones
that
are
publicly
available
and
we
never
had
an
issue
due
to
that
because
in
the
end,
most
of
the
time
you
just
need
a
working
go
compiler
and
and
that's
it
and
yeah.
G
Then
we
are,
and
basically
nowadays
we
we're
just
doing
exactly
what
is
described
on
this
new
okd
development
page
and
if
we
had
that
two
years
ago
that
it
would
have
been
a
massive
help
because
well
we
I
have
to
say
before
I
saw
this
page
now.
It
was
always
a
bit
nebulous
how
you
are
actually
supposed
to
customize
okd
and
it's
not
never
really
clear
where,
where
these
images
are
coming
from
and
how
they
are
built.
G
But
but
already
this
page,
even
though
it's
not
fully
finished
yet,
is
a
massive
help
and
basically
also
describes
exactly
what
we
are
doing
so
go
to
your
operator
that
you
want
to
replace,
make
some
changes
to
it.
Build
a
custom
image,
push
it
somewhere
and
then
do
do
a
create
a
custom
release
with
the
oc
new
release
command
again,
push
it
somewhere
and
that's
it.
And
then
I
guess
the
only
part.
G
That's
still
missing
actually
is
overriding,
the
the
version
in
the
cluster
version
operator
and
that
that's
pretty
much
it
what
we're
doing
and,
of
course,
across
several
repos
and
then
doing
some
some
integration
there,
but
yeah.
Now
that
I'm
seeing
this
page,
it
looks
so
obvious,
but
it
was
not
so
obvious
when
we
first
had
to
figure
it
out
for
sure.
A
B
A
B
A
Excellent,
I
want
to
be
mindful
of
folks
time
because
we
are
at
time
now
so
any
last
thoughts
before
we
end
the
meeting.
A
Awesome
this
was
a
great
meeting
and
appreciate
everyone's
participation
and
support
and
we'll
get
these
videos
and
meeting
no
notes
up
as
soon
as
possible.