►
From YouTube: OKD Working Group Meeting 07-20-2021
Description
The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group will also include the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope.
More info at https://okd.io
A
Thank
you,
everyone
for
joining
us
for
the
okd
working
group
meeting
for
july
20th
of
the
year
2021,
and
I
will
pop
the
agenda
into
the
chat
for
folks
that
don't
have
it
and
there
we
are.
So,
let's
do
a
quick
agenda
review
real,
quick
before
we
get
started.
Does
anyone
have
anything
that
they
want
to
add?
Is
there
anything
missing.
A
Oh
all
right
sounds
like
folks
are
good
with
what
we
have.
So,
let's
start
out
with
introductions.
I
always
like
to
do
this
because
you
know:
there's
always
going
to
be
new
people
watching
these
videos
that
are
getting
put
up
on
on
youtube.
So
we'll
start
out
I'll
just
go
across
my
screen.
Brian
go
ahead.
B
Okay,
off
mute,
hey,
I'm
brian
ennis.
I
work
for
ibm,
but
I'm
here
as
a
hobbyist,
I
run
okd
on
overt
and
got
a
home
lab
set
up.
C
Sorry,
look
in
the
middle
doing
other
things:
hey
everyone,
I'm
mike.
I
am
new
to
red
hat
as
a
junior
solutions,
architect
off
in
the
the
northeast
northeast
comm
sales
division.
Part
of
the
acquire
pod,
been
hanging
around
the
okd
working
group
for
starting
really
around.
Like
I
don't
know
like
march
last
year,
I'm
just
kind
of
been
a
more
of
a
lurker,
so
watch
what's
going
on,
but
I
would
like
to
take
part
in
some
the
container
sick
stuff
moving
down
the
line.
If
I
have
the
time
to
do
so,.
D
Hi,
I'm
philipp,
I'm
working
for
a4m
and
currently
I'm
regretting
the
okadi
stuff
from
3
11
to
4
7..
So
I
have
some
problems
but
yeah.
I
hope
this.
A
A
Thank
you
for
joining
us
and
driti.
E
Hey
everyone,
so
this
is
the
first
time
that
I
am
joining
this
ok
meeting,
I'm
from
red
hat
and
I'm
looking
to
contribute
to
katie
yeah.
That's
all.
F
Hey
y'all
name's
neil.
I
work
at
natto
as
a
senior
devops
engineer,
but
I'm
here
representing
the
fedora
community
to
help
make
sure
that
okd
and
and
the
openshift
teams
are
able
to
communicate
effectively
with
fedora
teams
and
get
the
good
stuff
in
there
basically
easily
and
quickly,
and
I'm
also
here
kind
of
as
a
hobbyist
to
to
to
like
have
okd
working
for
the
hobbyist
type
folks,
because
that
that
matters
quite
a
lot
to
me.
G
Hey
everybody
mike
mckeon,
I'm
an
engineer
at
red
hat,
where
I
mainly
work
on
openshift
cloud
platform
or
container
platform
and
cloud
infrastructure
team.
I
just
love
otd.
I
think
it's
a
great.
You
know
community
and
whatnot,
so
yeah,
just
here
open
out
excellent,
bruce.
H
Yeah
hi
there
I'm
bruce
I'm
an
instructor
at
bcit,
which
is
a
technical
school
up
north
of
the
us
border
and
a
frozen
land
called
canada,
and
you
know
so
we're
sort
of
on
on
break.
So
I've
been
distracted
with
a
whole
bunch
of
other
stuff
so
far
over
the
summer,
but
I'm
gonna
have
to
get
my
network
up
and
running
with,
hopefully
4.8
going
into
the
fall.
If
that
happens,.
A
I
Hello:
everybody,
I'm
christian
glomek,
I'm
a
software
engineer
at
red
hat.
I've
also
been
co-leading
the
okd
working
group.
Although
I've
stepped
back
a
little
bit
to
focus
on
on
more
internal
work
at
the
moment,
which
will
circle
back
to
okd,
I'm
currently
working
on
the
arm,
enablement
effort
and
yeah.
So
hello,
everybody.
A
Okay,
well
we'll
move
on,
and
until
if
you
decide
you
want
to
say,
hi
timothy.
J
J
K
K
I
am
actually
a
newbie
in
the
cloud
community.
It's
about
a
month
or
two.
I
work
I'm
coming
to
these
meetings
and
this
week
I
am
a
bachelor
of
bachelor
of
science
in
electrical
engineering.
I
finally
finished
my
bachelor
and
happy
to
be
here.
M
Hi
everybody
I'm
sri,
I
work
with
neil
at
datto
and
you
know
we
we
use,
you
know
kubernetes
and
red
hat
at
work,
but
and
openshift
and
everything,
but
I'm
here
I
think,
along
with
several
people,
as
as
as
part
of
the
sort
of
hobbyist
sort
of
home
lab
community
trying
to
get
okd
more
traction
in
that
space.
F
Hey
there,
I'm
also
an
engineer
at
red
hat
working
on
the
operator,
sdk
team,
and
so
I
like
to
kind
of
watch
these
meetings
from
that
perspective
and
then
I'm
also
a
hobbyist
in
the
homeland
space
still
running
openshift
3
in
my
home
cluster,
but
definitely
excited
to
upgrade
to
openshift4.
So
following
these
discussions
for
that
purpose,
as
well.
A
Excellent
and
brian
did
you
go
yet?
I
don't
think
you
did.
A
It
all
the
way
around
yeah
all
right,
excellent,
oh
and
I'm
jamie
mcgarrett,
with
the
university
of
michigan
co-chair
of
the
working
group
and
at
university
of
michigan
we're
using
okd
for
in
a
variety
of
places
within
the
university.
The
one
that
I'm
particularly
involved
in
at
the
moment
is
with
a
consortium
called
icpsr
of
many
different
universities
and
organizations,
doing
social
science,
research.
So
a
lot
of
data
and
number
and
survey
crunching
and
whatnot.
A
Let's
jump
now
to
the
next
item
on
our
agenda,
and
that
is
the
release
updates
with
christian.
What
do
you
have
for
us.
I
So
there's
two
things
I
think
that
are
noteworthy.
We
have
been.
Our
vadim
has
been
looking
at
preparing
okd,
4.8
and
4.9
nightlys,
so
that
is
probably
a
soon
to
land
if,
if
it
hasn't
already
and
then
very
very
importantly,
I
think
we
have
finally
merged
the
the
f
cos
and
master
branches
of
the
installer.
So
the
installer
for
okd
can
now
be
built
off
of
mainline,
which
I
think
yeah.
This
has
been
a
long
time
in
the
making,
and
this
is
a
great
milestone
for
us.
I
Unfortunately,
the
mco,
which
we
had
merged
at
some
point
now,
is
still
forked
again,
but
that's
only,
I
think,
five
comments
and
we
we're
definitely
working
on
getting
that
merged
back
in
again
as
well,
but
yeah
getting
closer
and
closer
so
that
I
think
yeah.
That's
a
really
big
important
milestone
for
us
internally
as
well
for
just
making
okd
one
important
part
of
the
main
branch,
so
that
is
in
the
installer
that
has
happened
now.
I
Finally-
and
I
think
you
have
a
team-
had
sent
me
some
things:
yeah,
okay,
the
population
problem-
I
like
this
corporation-
no,
I
don't
think
there's
anything
anything
else.
Right
now,.
A
Okay,
thank
you
for
that
updates
and
thank
you,
christian
and
vadim,
and
all
of
the
people
that
have
been
doing
the
work
to
to
get
the
installer
in
the
position
that
it's
in
and
to
get
okd
in
the
position
that
it's
in
right
now
very
much
appreciate.
All
of
that
and
by
the
way
christian
pointed
out
and
actually
was
vadim.
I
think
that
pointed
out
that
it
was
just
a
year
ago
that
okd
v4
was
released.
A
I
Actually,
let
me
let
me
jump
right
here
and
jump
in
here
and
one
more
thing
that
I
think
is
kind
of:
it's
not
strictly
related
to
okd
yet,
but
it's
definitely
release
related.
So
for
openshift
we
have
just
released
a
developer
preview
for
arm
64,
like
for
the
arm
64
architecture
which
you
can
download.
I
think
you'll
need
the
the
developer
subscription
for
that,
but
there's
a
blog
post
about
that
I've
linked
it
here,
I'll
put
it
in
the
in
the
notes
as
well.
I
So
if
you
want
to
try
out
openshift
on
arm,
you
can
do
that
right
now.
We
will
hopefully
soon
also
get
okd
on
arm
that
timothy
might
be
having
some
updates
there
with
regards
to
to
the
fedora
core
os
ami.
That
is
still
missing
to
to
run
the
ar-64
image
on
aws
but
yeah.
That
is
definitely
on
the
horizon
for
us
as
well.
So
we're
working
on
that
and
you
can't
wait,
then
you
can
already
install
open
as
a
dev
preview.
There.
A
Excellent,
very,
very
cool
all
right.
Let's
move
now
to
the
fcos
updates,
so
go
ahead
and
take
it
away.
Timothy.
J
Sure,
thanks
right
so
as
I've
been
mentioned,
I'll
talk
about
on
64
support
first
and
the
work
is
still
in
progress.
I
think
dusty
posted
an
one
ami
that
you
can
use
for
testing,
but
it's
probably
available
only
on
one
region.
If
I
remember
correctly,
so
it's
definitely
a
test
ami
that
will
go
away
at
some
point.
So
don't
rely
on
that
for
anything
serious.
J
J
Then,
after
that
I
don't
have
anything
specific
new
just
want
to
point
again
two
things
from
last
meeting
and
the
first
one
we're
still
looking
at
federal
certified
changes
they
come
along.
So
this
is
like
a
continuing,
continuous
process,
make
sure
we
don't
miss
anything
we're
still
having
discussions
around
how
we
should
and
wouldn't
manage,
also
on
federal
race.
J
So
this
does
not
exactly
directly
impacts
okd
because
you
ship
with
your
defaults
pre-built
in
so
but
well,
maybe
some
inputs,
if
you
have
any
inputs
on
that,
it's
still
welcome
off.
On
the
federal
course
side
and
finally,
we
had
last
and
last
meeting,
we
had
platform
support
discussion,
so
we
run
out
of
time.
So
if
we
still
have
any
questions
around
platform,
support
for
then
feel
free
to
read
them
today,
so
that
we
could
discuss
that.
J
The
summary
is
still
in
the
in
the
I
can
d
for
which
platform
was
supported
for
federal
records.
But
if
anything,
if
any
other
questions
are
raised,
feel
free
to
ask.
M
I
So
right
now
I
think
the
biggest
challenge
there
is
is
the
the
memory
that's
available
on
those
devices.
We
can't
install
okd
or
run
okd
with
eight
gigabytes,
and
even
16
is
probably
not
enough.
So
until
there
are
devices
with
32
gigabytes
available,
we
it
won't
be
easy
to
do
that
to
say
the
least
might
not
even
be
possible
at
all.
I
So,
but
once
we
have
those
32
gigabytes
of
ram
available
that
should
really
be
it
should
be
doable
then
yeah,
and
if
you
can,
I
don't
know
solder
your
own
memory
onto
a
raspberry,
pi
4.
Then
you
might
be
able
to
do
it
earlier,
but
yeah.
That
would
be
a
really
cool
post.
A
Can
we
back
up
for
a
second,
let
me
for
people
that
might
be
watching
this
that
aren't
familiar
with
the
excitement
around
arm
and
why
the
excitement,
let's
actually
provide
a
little
a
little
bit
of
context
in
terms
of
why
arm
as
an
architecture,
is
so
exciting
to
run
clusters
or
run
anything
on
so
in
short,
right,
better
efficiency
fraction
of
the
power
utilized
for
the
power
that
for
processing
power
that
you
get
out
of
it.
If
someone
wants
to
be
more
specific,
go
ahead
and
jump
in
there.
I
Right
so
obviously
openshift
will
or
okd,
but
then
also
will
only
run
on
sbsa
certified
hardware
or
computable
hardware,
which
is
the
the
arm
server
ready,
certification,
which
means
in
order
to
to
install
fedora
on
it,
fedora
core
os
and
for
openshift
railcar
os.
You
will
have.
I
You
will
have
to
have
that
compatibility,
which
essentially
means
that
the
devices
are
uefi
capable
or
acpi
capable
of
booting
in
a
uefi
image
without
having
to
go
through
the
device
tree
boot
process
with
ubud,
so
yeah
and-
and
that
is
actually
that
is
actually
available
for
raspberry
pi
force.
There
is
the
uefa
firmware
for
our
pies,
which
is
r54
minus
uefi.dev,
I'll
put
it
in
the
chat
here
as
well.
With
that
firmware,
you
can
essentially
install
or
run
the
the
okd
installer
and
use
it
that
way.
M
G
You
know
this
is
like
on
the
back
of
the
work
that,
like
apple,
is
doing
and
whatnot,
where
they're
showing
marked
performance
increases
with
the
silicon
they're
building.
So,
like
I
don't
know
how
true
that
is.
But
if,
if
that's
true
in
the
next
year
or
two
years,
we
could
start
seeing
a
huge
presence
for
armed
devices
in
the
cloud
as
well.
So.
I
Absolutely
I
I
think
that
is
really
the
case
right
now,
there's
only
two
or
three
devices
that
actually
have
this
spsa
certification
and
we're
really
only
at
the
big
at
the
very
beginning
of
this,
and
you
know
the
more
powerful
those
devices
become
the
cheaper
they
become,
so
maybe
with
the
raspberry
pi
five
when
it
comes
out
next
year
or
if
it
comes
out
next
year.
Maybe
that'll
that'll
already
do
the
trick,
and
you
know
so
really.
I
I
think
there
will
definitely
be
much
much
more
many
many
more
hardware
parts
will
be
available
and
right
now
those
are
still
really
expensive.
Those
servers-
because
you
know
these
ampere,
whatever
they
are
really
expensive
devices
at
the
moment,
but
once
this
really
gets
into
the
the
consumer
market
and
is
produced
in
in
mass
prices
will
go
down
and
this
will
become
available
for
the
hobbyists
among
us
to
run
their
own
open,
show
or
okd
cluster.
Definitely
that's
what
I
I
strongly.
C
Believe
yeah,
I'm
not
super
tuned
into
the
the
arm
ecosystem
from
what
I've
the
stuff
that
I've
done.
But
does
anybody?
Has
anybody
run
any
kind
of
like
hpc
type
workloads,
whether
it's
machine
learning
or
ai
stuff
on
either
like
graviton
or
ampere
stuff,
either
on
aws
or
have
they
got
stuff
done
locally
at
the
university
or
something
like
that?
Does
anyone
even
have
a
chance
to
use
them
there.
F
Are
a
couple
of
japanese
facilities,
the
university
that
have
switched
over
to
ampere-based
armed
super
computers
for
high
performance
computing,
both
of
them,
I
believe
ron
rel
on
them,
but
it
is
the
the
catch
22
for
arm
is
that
there
isn't
good
equipment
for
people
to
develop
on
there's
only
good
equipment
for
people
to
to
run
stuff
in
production
on,
but
all
of
that
is
too
expensive
for
most
people
to
use,
even
with
the
with
the
max
right,
like
the
the
problem
with
the
arm
max
is
because
you
can't
run
linux
natively
on
them,
and
you
can't
do
anything
meaningful
with
that.
F
F
Unless
there
are
companies
or
people
like
actively
pushing
for
arm-based
equipment
to
exist
at
affordable
price
points
that
are
actually
powerful,
you're,
just
not
going
to
see
our
move
past
where
it
is
now,
so
you
know,
maybe
you
know
if
if
companies
like
ibm
red
hat
zuza
are
all
like
really
wanting
to
have
this
arm
thing
take
off,
maybe
they
should
be
talking
to
the
people
that
make
these
sbcs
and
stuff
to
you
know
maybe
tilt
the
road
map
a
little
bit
more
in
in
favor
of
making.
C
F
Right,
like
there's
a
couple
of
attempts
to
do
something
more
affordable,
but
nobody
is
released
to
manufacturing
anything
other
than
talos
and
like
when
your
lowest
price
to
your
product
in
terms
of
pricing
is
two
grand
for
one
machine
like
that's
out
of
the
realm
of
possibility
for
almost
everyone,
like
you
know,
I
very
much
personally
believe
that
it
has
been
a
huge
mistake
that
that
for
arm
development
for
professional
use
cases
that
everybody's
been
ignoring
the
fact
that
we
don't
have
access
to
good
arm-based
equipment
on
an
individual
level,
and
this
is
something
that
I
know-
I've
harped
on
a
little
bit
in
previous
okay
meetings
when
we've
talked
about
okd
on
arm,
but
like.
F
G
Without
you
know,
obviously,
without
breaking
any
of
my
contractual
obligations
to
red
hat,
I
can
just
say
that,
like
neil
the
kind
of
things
you're
you're
talking
about,
I
have
like
seen
those
conversations
happening
inside
that
I
can't
say
anything.
We
really
like
deeper
about
it,
but
I
know
that
there
are
people
who
are
more
senior
than
me
who
are
like
concerned
about
these
things.
So.
F
Yeah
I
mean
it's,
it's
even
something
as
simple
for
me
like
with
this
last
fedora,
you
know
I'm
gonna
break
a
little
bit
out
of
the
openshift
bubble,
a
little
bit
just
just
for
a
brief
moment.
You
know
this
last
release
cycle
for
fedora
for
fedora
linux
34.
F
I
launched
fedora
kde
on
arc64,
but
it
was
such
a
pain
in
the
butt
to
dev
and
test
that
I
had
to
do
most
of
it
blind
and
kind
of
hope.
Somebody
would
tell
me
whether
something
was
wrong
because
good,
reliable
arnold
64
hardware,
just
flat
out,
doesn't
exist,
and
that
is
a
serious
problem
that
you
know
no
amount
of
like
promoting
on
the
server
end
is
going
to
fix.
You've
got
to
do
something
else.
On
the
developer
end.
G
J
Yeah
we're
not
the
arch,
64
development
working
group,
so
yeah.
All
of
that
we
know
we
cannot
do
anything
about
it.
We
work
on
on
the
support
of
the
platform
that
actually
exists
and
for
federal
rest,
it
will
still
be
s
s
vsa
and
whatever
and
ufi
so
sure
lobby,
other
lobby,
vendors
or
whatever,
but
yeah.
We
cannot
do
anything
about
it.
I
Yeah
yeah,
I
I
can
essentially
second
that
we
can't
really
we
don't
control.
The
hardware
is
we're
here,
making
the
software,
and
I
mean
looking
at
the
the
development
over
time.
I
I
do
think
there
is
a
trend
towards
making
that
more
accessible.
I
You
can
now
get
these
nvidia
jetson
devices
for
like
four
hundred
dollars,
which
you
know
they
have
32
gigs
of
ram.
Maybe
you
can
even
run
openshift
on
them.
I
don't
think
they
have
the
uefi
firmware
yet,
but
you
know
it
is
going
in
in
that
direction.
Our
devices
are
getting
more
powerful
and
at
the
same
time
the
prices
are
going
down
and
then
the
proliferation
is
taking
place
all
always
slowly,
but
I
do
think
in
the
future.
Obviously
it's
not
going
to
be
tomorrow.
I
It's
probably
going
to
be
next
year
or
in
two
years
or
even
three
years,
but
by
then
I
think
we
will
have
the
ability
to
really
run
an
openshift
cluster
on
hardware
that
doesn't
cost
much
more
or
even
less
than
a
thousand
dollars.
Let's
say.
A
All
right,
I
do
want
to
move
on
to
the
next
topic.
This
was
a
great
exploration,
though
I
think
it's
really
helpful
in
a
variety
of
ways
to
to
give
viewers
a
sense,
also
of
what's
happening,
and
people
in
the
meeting
here
as
well
of
what's
happening
in
that
space.
So
moving
on
our
next
item
is
a
look
at
the
issues.
A
What
are
the
issues
so
looking
at
issues
that
are
in
the
okd
repo?
Is
there
anything
that
stands
out
here
that
folks
want
to
bring
to
our
attention?
There's
actually
only
been
one
added
just
in
the
past
like
two
weeks,
and
it
was
one
about
creating
a
new
cluster
4.7
and
looks
like
there
was
some
conversation
about
it.
A
A
A
Yeah,
nothing
really
to
add
so.
Okay,
nothing
in
particular,
initiatives
have
popped
up.
That's
good!
Now.
Moving
on
to
discussion
items
is
there
anything
in
the
discussion
items
section,
that's
worthy
of
our
attention.
The
only
thing
added
in
the
past
couple
weeks
actually
is
just
mirroring
in
the
repository.
I
Yeah,
I
think
I
commented
on
on
that.
I
I
do
think
it's
a
user
error
that
is
really
tested
and
supported.
A
Yeah,
okay,
moving
on
now
to
updates
from
the
documentation
group
mike.
Why
don't
you
go
ahead
and
cover
the
stuff
that
that's
sort
of
in
your
court
right
now
or
our
court.
G
Yeah
sure
I
mean
I
can
talk
about
these,
these
other
things
on
the
on
the
list
yeah.
I
can
just
repeat
what
happened
in
the
meeting
so
linking
to
the
charter
from
the
main
website
page.
I
think
we
discussed
that
I
thought
diane
was
going
to
look
into
doing
that,
but
you
know
well.
A
We
wanted
to
get
the
the
whole
group's
agreement
on
that
was
the
the
gist
so
bringing
it
to
the
whole
group.
Does
anyone
have
any
opposition
to
putting
a
link
to
the
charter
on
the
front
page
of
the
okd.io
website?
G
G
Let's
see
yeah,
I
thought
we
were
gonna,
do
it
but
yeah.
I.
A
Charter
update,
okay,
I
don't
see
the
link
to
it
actually
I'll
find
the
link
and
put
it
in
there.
But
yes,
there
is
a
charter.
Christian
can
provide
a
little
more
context
on
that,
but
and
maybe
neil,
I
think
you
were
there
at
the
beginning.
A
Basically,
it's
like
a
page
of
explaining
what
the
working
group
is
about
and
people
voicing
interest
and
whatnot,
so
it
doesn't
sound
like
anyone.
Okay,
neil
posted
the
the
link
to
it,
so
it
doesn't
sound
like
anyone
has
any
downsides,
so
we
can
say
to
the
documentation
group
go
forth
and
diane,
thereby
go
forth.
H
I
All
right
just
wanted
to
be.
One
thing
I
maybe
would
like
to
do
is
update
the
date.
That's
at
the
top
of
it
because
it
has
actually
been
updated,
like
it
was
updated
three
weeks
ago,
but
the
date
wasn't
changed,
maybe
make
that
a
v
1.2
and
update
the
date
before
we
link
it.
So
everybody
sees
this
is
still
current
and
not
some
some
document
from
2019.
A
Okay,
great,
let
me
put
that
in
the
notes
there
to
do.
Is
there
anything
else
that
stands
out
with
folks
that
that
we
should
do
to
the
document
before
making
it.
A
L
A
All
right,
sorry
to
interrupt
you,
there
go
ahead
and
take
it
away
finish
up:
yeah,
no
documentation,
yeah,
no
worries.
G
So
the
inclusive
language
update
you
know
like
the
the
okd,
the
docs.okd.io
that
is
all
generated
from
the
ocp
upstream,
so
like
we
had,
we
had
pretty
positive
feedback
from
the
red
hat.
Docs
lead
who's
kind
of
doing
that
work.
That
they've
run
the
inclusive
language
stuff
on
that.
But
then
we
also
want
to
run
it
again
like
some
of
the
linting
tools
we
have
on
the
produced
documentation
and
also
on
okd.io,
so
like
okd.io
itself
has
not
had
any
sort
of
treatment.
G
It
didn't
look
like
it
was
in
that
bad
of
shape,
but
this
is
kind
of
something
that
you
know
I
think
is
probably
going
to
be
coming
so
that,
but
that's
going
on
in
the
background
you
know,
I
think,
it's
being
handled
by
the
docs
team,
pretty
much.
A
A
B
Okay,
so
I
actually
did
run
the
tool
on
okdie.I
o
and
I
summarize
the
results
in
this
issue.
I
think
that
the
primary
issue
is
the
primary
branch.
Obviously,
all
new
github
repos
now
get
main
as
a
primary
branch.
B
B
Actually,
let
sort
of
clones
work
for
a
while,
but
again
for
completeness
you,
everyone
who
has
a
clone
should
run
the
the
commands
in
the
issue
and
just
to
update
their
that
they
get
config
and
a
couple
of
other
things
that
come
out
of
it.
There
is
a
couple
of
other
words
like
white
list.
That's
in
there
that
we
obviously
need
to
change
they're
they're,
just
in
comments,
but
again
we
should
go
in
and
change
those
other
than
that.
B
It's
it's
pretty
clean,
so
I
I
did
put
an
issue
in
because
obviously
there's
quite
a
lot
of
coordination.
Gonna
have
to
happen
to
actually
move
that
over
and
so
I'm
not
sure
how
that's
going
to
do.
But
I
I
guess,
are
there
any
other
repos
that
the
okd
community
owns
that
on
sort
of
managed
by
a
product
team,
I'm
actually
thinking
of
probably
the
main
okd.
B
I
know
there
is
some
some
content
in
that
one.
That
probably
also
needs
to
be
done
and
the
tool
is
very,
very
simple
to
run
and
you
can
run
it
natively
or
I
actually
just
use
the
docker
there's
a
docker
docker
file
in
there.
You
just
run
the
docker
file
and
it
pretty
much
works
out
the
box
so
yeah.
That's
we
just
need
to
then
coordinate,
get
these
issues
actioned.
I
We
also
own
the
the
community
repository
in
the
openshift
arc,
which
I
don't
think
any
automation
touches,
which
is
also
the
one
that
contains
the
charter,
so
we
might
want
to
rename
the
master
branch
to
main
there
too.
I
don't
think
we
can
do
that
in
all
the
openshift
component
repositories
yet
because
of
the
extensive
automation
and
ci
that
that
requires
that
name
where
the
master
name
is
hard
coded
in
various
places,
but
in
in
that
in
those
two
in
the
community
repository
in
the
okd
repository,
I
think
possible.
G
A
Yeah,
I
think
what
we'll
end
up
doing
at
the
next
docs
meeting
next
tuesday
is
basically
developing
a
plan
of
getting
all
of
the
changes
in
in
the
repos
that
we
know
and
have
control
over,
as
prs
send
out
a
message
to
the
community
in
our
various
social
media
channels,
letting
them
know
about
this
change
and
then
approving
the
prs
after
maybe
a
week
or
something
like
that
and
sort
of
the
our
intent
has
seeped
out
into
the
community
and
and
that's
probably
what
the
docs
team
is
gonna.
A
Do
that's
what
I
think
we'll
we'll
talk
more
about
it
at
the
next
stocks
meeting.
Is
there
anyone
here
who's
not
attending
the
docs
meeting?
That
has
any
input
or
anything
they'd
like
to
add
to
this,
that
we
can
bring
back
to
the
docs
group
or
is
there
anyone
who
would
like
to
join
the
docs
group
that
hasn't
been
participating.
A
A
Go
do
the
thing
yeah
el
miko,
anything
else
you
wanted
to
say
from
docs.
G
Yeah,
the
only
last
thing
was
like
I
sent
out
an
email
earlier
in
the
week
about
this
guides.
Pr
that
I
have
up,
I
think
you
know
the
last
week
at
the
docs
meeting.
You
know.
Diane
was
like
let's
merge
this
now
like,
so
I
think
we're
probably
going
to
merge
it
next
week.
If
people
have
comments,
please
go
check
out
that
review.
I
got
a
few
changes
to
make,
but
you
know
definitely
comments.
Welcome
I'll
put
it
in
the
notes
for
today,
too.
A
A
From
what
I
know
of
it,
I
totally
understand
that
happening.
Okay,
let's
move
on
now
to
new
business
and
the
new
business
that
we
have
is
to
promote
the
recording
of
the
open
office
hours.
A
A
lot
of
people
attended
it
and
forwarded
it
on
social
media,
the
link
to
it
when
it
happened
or
before
it
happened.
Now
we
need
to
promote
the
recording
of
it.
So
there's
a
link
in
the
meeting
notes
to
that
youtube
recording.
A
So
if
you
could
share
that
widely
in
your
networks,
that
would
be
awesome,
and
the
next
step
in
this
operation
is
deciding
on
a
date
for
the
next
one.
So
diane
isn't
here,
but
basically
she's
offered
up
the
the
the
friday
or
I
think
that
they
also
have
a
wednesday
when
they
do
the
common
stuff
for
us
to
commandeer
those
and
for
context.
A
The
last
one
was
the
second
friday
of
the
month,
so
it
was
july
9th
at
noon,
and
my
thought
would
be
that
we
do
the
second
friday
in
august,
which
would
be
friday
the
13th
at
noon.
A
B
I
A
A
Very
cool
okay,
so
even
if
diane
can't
be
there,
I
can
be
there
and
can
anyone
else
be
there.
Anyone
else
from
the
group.
A
G
There
you
go
yeah,
just
fair,
fair
warning
jamie.
I
was
just
looking
at
the
calendar
friday.
That
august
the
13th
is
is
actually,
I
think,
a
holiday
for
most
redhead
employees.
G
G
A
Friday,
the
13th
okay
yeah
right,
who
wants
to
give
a
demo
on
friday,
the
13th
of
something
let's
see.
Well,
let's
I
guess
we'll
oh
go
ahead.
No,
no!
I
didn't
want
to
interrupt
you
go
ahead.
A
I
was
gonna
say:
do
we
want
to
punt
and
just
keep
that
date
and
hope
that
someone
can
join
me
or
should
we
change
it.
H
A
A
wednesday
date
as
well,
there
was
a
slot
yeah.
There
is
it's
the
two
days
that
openshift
commons
has
slots
are,
I
think
it's
wednesday
at
noon
as
well.
Does
anyone
else
know.
L
But
keep
in
mind
that,
on
that
friday,
chris
and
bobby
will
be
on
recharge
day
as
well,
so
they
won't
be
able
to
produce.
But
let
me
check
our
calendar
because
that's.
L
A
A
I
If
we
want
to
do
that
on
on
fedora
core
os
instead
of
rel,
then
september
might
be
better,
because
I
don't
think
we
can.
B
B
H
G
I
think
4.9
is,
I
think,
that's
when
it's
going
to
be
coming.
I
don't
know,
but
single,
like
a
single
note.
Open
shift
is
something
that's
coming
as
like
an
edge
case.
It's
a
little
bit
different
than
I
think
what
we're
talking
about,
but
that
I
don't
think
that
profile
has
been
tested
at
all
with
okd
and
I'm
just
not
sure.
C
C
Something
I've
thought
about
in
the
past
is
okay,
even
though
it's
more
of
like
a
sibling
thing
with
openshift.
Obviously,
the
okiti
stuff
kind
of
puts
feels
like
it's
sometimes
like
a
version
ahead
like
what's
going
on.
You
know
like
four,
both
like
four
eights
kind
of
come
out
around
the
same
time,
but
like
four
nine
is
like
available
in
the
ci
stuff,
even
though
there
are
night
leagues
from
ocp.
C
Would
the
working
group
like
want
to
try
and
show
like
hey
we're
going
to
demo
like
four
or
nine
features
people,
so
they
can
see
what's
coming
in
openshift,
but
also
like
you
can
use
this
now
kind
of
thing
like
for
future
releases
at
all,
or
do
they
not
want
like?
Do
we
want
to
back
off
that
and
let
red
hat
have
their
their
promo
for
those
kind
of
things.
G
I
mean
that's
a
great
question
I
was
I
was
thinking
something
similar
because
there's
a
feature
that
I'm
working
on
for
ocp
right
now
that
hasn't
been
tested
with
okd
yet
but
like
it,
I
was
gonna
recommend
I
was
gonna
say
like
maybe
we
should.
This
could
be
a
possible
demo
idea
as
well.
So,
like
I
think,
it's
totally
like
all
these.
Many
of
the
features
we're
working
on
are
being
developed
in
open
source.
So
I
don't
see,
there's
any
reason
not
to
like
do
that.
G
I
mean
they'll
get
released,
they'll,
get
release
announcements
when
you
know
ocp
comes
out,
but,
like
my
understanding
at
least
from
a
red
hat
perspective,
is
that
okd
is
supposed
to
be
kind
of
running
out
in
front
a
little
bit.
You
know
so,
like
I
think,
it'd
be
perfectly
okay
to
you
know
to
talk
about
these
things
like,
for
example,
what
I
was
going
to
propose.
G
G
We
have
it
working
on
ocp
right
now,
but
we
could
probably
try
it
out
with
okd
and
then
demo
like
how
people
could
do
a
migration
from
entry
to
out
a
tree
and
also
how
they
could
install
a
cluster
using
out
a
tree
cloud
providers
so
that
you
know
that's
a
feature.
We're
working
on
that
we're
going
to
you
know
it's
going
to
be
a
big
thing
for
ocp,
but
it
could
also
be
a
big
thing
for
okd
as
well.
We
could
certainly
demo
it
and
you
know,
talk
about
it
if
people
are
interested.
C
Something
I've
thought
about
in
the
past:
there's
a
like
in
the
the
cloud
space
in
the
container
space.
Specifically,
I've
always
wanted
to
investigate
because
I
never
got
the
chance
to
use
them
is
build
packs.
I
know
for
eight.
I
think
they
gave
that
feature.
I
don't
think
I've
ever
seen
like
any
like
written
tutorial
or
video
on
using
build
packs
within
the
openshift
space,
because
it's
always
like
s2i
use
s2i
for
everything.
But
now
you
have
this
feature
from
cncf.
A
A
Okay,
let's
do
that
and
then
we'll
make
a
final
decision
about
what
we're
going
to
do
is.
If
we
can
get
someone
lined
up.
I
think
it
would
be
good
to
have
a
regular
cadence
and
not
skip
just
because
it.
It
builds
that
momentum
and
people
know
that
you're
always
gonna,
be
there
same
that
time
same
bat
channel.
But
if
we
can't
do
it,
you
know,
then
then
we
won't
do
it.
H
B
It
might
actually
be
worth
setting
up.
I
don't
know
where
we
put
it,
but
just
I
mean
we
captured
quite
a
few
ideas
of
what
what
what
we
can
do.
Just
actually,
let's
get
a
list
together
of
what
people
think
we
should
cover
on
those
days
and
then
we
can
actually
start
asking
for
volunteers
on
who
can
look
at
this
topic
for
maybe
next
month
or
the
month
after
and
start
sort
of
building
out
a
schedule
of
topics
that
you
want
to
cover.
A
Well,
I've
got
the
in
the
meeting
notes.
You
know,
there's
an
item
for
why?
Don't
folks
just
put
the
name
or
the
the
idea
that
you
have
and
then
well,
it
looks
like
some
people
have
already
started,
actually
adding
it.
So
if
you
have
a
suggestion
for
who
might
be
the
person
to
to
demo
those
ideas,
if
you
put
it
as
a
sub
item
of
your
entry
there,
just
who
we
might
contact
for
that,
then
that
keeps
everything
nice
and
organized.
A
All
right,
we
have
five
more
minutes
left
we've
covered
everything
in
our
agenda.
Are
there
any
last
minute
topics
or
questions
or
concerns
that
you
want
to
bring
to
the
table
before
we
call
it.
C
I
feel
bad
asking
for
this,
I'm
asking
just
because
I've
been
out
of
the
loop
for
months
now,
a
lot
of
work
stuff
happening.
On
my
end.
Last
time
I
was
in
the
working
group.
There
was
discussions
around
operator
hub
and
like
the
red
hat
registry
versus
the
community
registry
and
the
cross
pollination
there.
I
don't
really
know
what
that
status
is
routine.
Okay
and
ocp.
Right
now
is
has
that
changed
at
all
or
improved?
Since
I
don't
know,
I
feel
like
this
is
like
november,
or
at
least
christian
go
ahead.
I
Yeah,
I
don't
think
there's
been
a
lot
of
development
on
on
that
front,
so
we
do
still
plan
on
having
separate
okd
catalogues,
and
I
think
vadim
has
talked
to
some
people
internally
to
to
make
that
happen
and
yeah,
but
I
haven't
heard
anything
for
at
least
three
three
months
three
weeks
now
so,
probably
not
since
the
last
meeting
that
there
is
an
update
on
on
it
yeah.
I
I
will
ask
him
about
that
again
and
hopefully,
by
by
the
next
meeting,
we'll
have
some
more
news.
Definitely
it's
in
the
making,
but
I
don't
think
it
has
a
high
priority
at
the
moment
internally.
We
should
probably
push
on
that
a
little
more
from
from
our
side.
I.
A
Think
that's
a
good
selling
point
is
what
we
have
you
know
in
terms
of
operators.
Now
I
will
say
that
the
the
document
that
christian
created
the
the
issue
was
reorganized
a
little
bit
with
a
little
bit
more
context
as
to
what,
like
the
three
different
categories,
basically
of
of
hubs,
and
so
you
might
revisit
that
christian
might
have
the
link
to
it.
A
If
not,
I
can
post
it,
but
basically
there's
a
little
more
context
in
the
in
the
issue
that
christian
created
that
lays
out
all
of
the
operators
that
folks
are
interested
in
seeing
and
where
they're
coming
from
what
ones
are
internal
to
red
hat?
What
ones
need,
basically,
a
community
developer,
what
ones
you
know
etc.
So
we
can
start
with
that.
A
My
sense
is
that
probably
in
august,
we'll
take
a
more
targeted
approach
and
we
had
talked
in
the
last
working
group
meeting
about
starting
to
reach
out
to
folks
at
particular
companies
in
terms
of
having
okd
tested
in
their
environments
on
their
platforms.
A
I
I'm
thinking
we're
gonna
probably
do
the
same
thing
with
operators
is
just
like
start
reaching
out
to
folks
and
saying
hey.
We
would
like
this,
you
know
we
would
like
to
get
some
resources
we'd
like
to
contribute
some
resources
to
getting
this
operator
working
on
okd
and
in
the
proper
place,
so
to
take
a
very
targeted
approach
to
it.
That's
what
I'd
like
to
do
anyway,
so
all
right
anything
else.
A
All
right,
thank
you
very
much.
Folks
and
again.
The
docs
meeting
is
next
tuesday
same
that
time.
Same
bat,
channel,
fedora,
coreos
meeting
is
tomorrow
at
12,
30,
eastern
and
just
we'll
put
links
to
that
for
the
federal
core
os
meeting.
If
folks
are
interested
in
attending
that-
and
I
think
we're
good
to
go
thanks,
everyone
thanks
jimmy
hey.