►
From YouTube: OKD Working Group Meeting 03-14-2023
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
B
Group
meeting
for
March
14th
of
the
Year
2023
and
we've
got
an
agenda
laid
out
and
let's
go
ahead
and
get
started
with
Shireen
and
Luigi
for
okd
released
and
cicd
updates.
C
Yeah
sure,
so
to
be
honest
from
the
release
perspective,
we
are
still
waiting
for
Christian
to
he's
busy
working
on
working
with
the
Center
C
group
to
get
a
couple
of
RPMs
built
on
the
Sig,
the
center
centers
group,
and
then
we
can
go
ahead
and
and
continue
the
releases.
C
The
the
the
the
the
the
thinking
here
is
that
we'll
have
three
Loop
releases
now:
four
fourteen
Dev
413
and
412
Stables.
So
so,
hopefully,
at
the
end
of
we
tried
to
do
a
sprinkly
release.
So
we
in
our
second
week
of
the
Sprints
and
next
week
or
maybe
the
week
after
we'll
have
a
hopefully
have
a
Sprint
for
all
three
I
mean
a
release,
four
or
three.
So
if
you
want
to
add
anything
to
that.
B
All
right
does
anyone
have
any
questions
or
comments
or
any
type
of
feedback
on
that.
B
D
Yeah
all
right
good,
so
the
main
news
for
us
is
that,
with
with
the
federal
38
beta
released,
we
know
moving
our
federal
38
next
stream
to
Federal
next
stream
to
the
federal
38
release.
D
So
this
isn't
impacting
okd.
Yet
it
will
likely
be
for
the
next
release
and
it's
likely
I
think
that
the
413
release
we'll
see
on
February
37
for
now
but
yeah.
So
we're
working,
we're
moving
to
this
one
for
Ferra
chorus
and
that's
the
main
thing
I
have
for
today,
because
it's
a
big
change
for
us,
otherwise
I
think
we
have
anything
specific
that
landed
that
would
impact
or
KD.
Yet.
D
B
All
right
thanks
any
feedback
or
thoughts
on
what
Timothy
related
to
us.
B
All
right
moving
on
now
to
the
s-cos
updates.
Is
there
anyone
here
that
can
speak
to
those
I,
don't
know.
B
Yeah
I
don't
think
we
have
anyone
to
really
speak
on
it.
Yeah
yeah
yeah,
all
right,
moving
up
to
Brian
with
Community
Development
updates.
E
Okay,
so
we
had
our
call
last
Tuesday,
there
is
no
video
of
it.
Jeremy
had
a
conflict
and
we
didn't
have
tons
to
sort
out
hosting
permissions,
so
the
hack
MD
is
the
master
record
of
that
meeting.
E
A
couple
of
things
we
talked
about
so
Dwayne
talked
about
just
getting
the
glossary
he's
been
doing
some
work
to
actually
look
at
and
communities
getting
some
grant
funding,
and
what
he's
coming
across
is
is
an
argument
or
a
discussion
that
we've
had
here
a
number
of
times
around
what
is
open
source?
What
is
OPD
what's
the
relationship
between
ocp,
which
is
also
open
source
and
he's
coming
across
some
confusion
there.
E
So
we've
had
this
discussion
several
times
in
this
community,
but
I,
don't
think
we've
ever
got
around
to
actually
putting
it
to
bed
and
writing
it.
So
we
do
need
to
put
something
in
the
documentation
to
try
and
be
a
little
bit
more
clear
about
what
is
the
relationship
between
okay,
the
ocp
and
Dwayne
will
actually
update
the
glossary
and
and
and
bring
that
in
line.
E
The
pull
request
is
still
the
method
that
we
use
to
update
the
documentation
and
we
did
chat
around.
One
of
the
problems
with
pull
requests
is
that
we
can't
really
build
the
documentation
and
test
it
out,
and
so
before
you
do
a
pull
request
service.
You
want
to
make
sure
it
formats,
so
it
is
going
to
have
to
be
a
bit
of
a
collaboration
between
someone
that
wants
to
create
some
documentation
and
Michael
to
actually
get
the
formatting
right
test.
E
It
works
before
it's
actually
pushed
into
the
documentation,
not
ideal,
and
it's
something
that
we
do
need
to
look
at.
Is
there
a
way
that
we
can
actually
build
at
the
end
of
the
day,
it
is
open,
source
tooling,
but
there's
quite
a
sort
of
a
process
to
actually
go
build.
It
and
the
scripts
aren't
in
the
report
the
minute.
So
so
we
need
to
look
at
that.
E
E
So
we
need
to
find
a
new
owner
for
that
and
get
an
SNL
set
of
instructions
around
the
assisted,
installer
I
know
Luigi's
doing
the
the
the
nuts
and
bolts
version
from
sort
of
ground
up,
but
we
probably
do
need
the
assisted
installer,
the
easy
way
of
doing
it
documented
within
the
product,
documentation,
so
docs.orgd,
dot,
IO
and
then
the
last
part
of
the
meeting.
We
already
talked
about
how
the
community
can
engage
and
we're
going
to
try
for
the
second
time
to
focus
on
the
project
board.
E
So
the
idea
is
the
community
meetings
will
move
to
be
driven
by
the
project
board.
So
if
there's
something
you
want
to
do
or
there's
something
you're
doing,
it
should
be
on
the
project
board.
So
we're
going
to
try
and
for
next
meeting
to
get
that
project
board
updated.
We
last
sort
of
looked
at
this
sort
of
September
October
last
year
and
I
sort
of
fell
out
of
out
of
use
So.
The
plan
is
for
next
week
to
try
and
get
all
the
outstanding
actions
updated
to
work
out.
Is
it
active
work?
E
Has
it
been
sitting
there
with
nothing
done?
There
are
some
that
have
the
work's
been
done,
but
they've
not
been
closed,
so
we
want
to
bring
that
up
to
line
for
next
week,
I'm
a
little
bit
sort
of
strapped
at
the
minute.
My
I
I
smashed,
my
laptop
screen,
I
cracked,
the
screen
and
it
stopped
working.
So
my
personal
laptop
I
don't
have
access
to
so
I'm
on
iPad
today,
so
I
need
to
actually
write
some
documentation.
E
I
volunteer
to
actually
write
some
documentation
to
to
try
and
get
the
project
board
some
processes
written
around
some
simple
instructions,
so
we're
all
going
to
use
it
in
the
same
way
and
then
so
I
think
that
was
more
or
less
it.
As
I
said,
hack
MD
is
the
the
source
of
Truth
for
last
week's
meeting
and
there
is
no
going
to
be
no
video.
B
Any
questions
any
thoughts
on
that
and
I
apologize.
It
was
a
last
minute
thing
that
I
was
not
able
to
attend
the
last
meeting,
but
we'll
work
it
out
so
that
Brian
can
manage
and
steer
the
ship
at
a
technical
level.
B
F
Yeah,
hey
just
basically
two
quick
things.
The
first
is
I
mean
I
can't
promise
anything,
but
it
seems
like
we
may
get
some
time.
F
A
F
Architectural
implications
on
everything
but
I
think
we've
all
agreed
for
a
while
that.
F
Right
and
actually
we
want
to
get
to
the
point
where
we
build
an
OS
base,
image
that
is
just
Centos
content
and
then
openshift,
branches
or
okd
branches
are
layer.
On
top
of
that,
there's
a
lot
going
on
in
here
and
you
know,
I
know.
Christian
was
sort
of
interested
in
this.
A
lot
of
details
on
how
that
works,
but
I
think
we've
all
agreed
well
again.
F
I
can't
promise
anything,
but
it
seems
likely
we'll
do
it
and
like
we
have
the
big
problem
today
that
the
way
the
okd
pipeline
works
is
totally
different
from
how
the
production
pipeline
works.
This
would
impact
both
of
them.
I,
don't
understand
the
okd
pipeline
I
feel
like
maybe
I
just
need
to
I,
don't
know
get
a
brain
dump
from
someone.
Maybe
we
could
even
try
and
do
that
in
this
in
okd.
First,
a
lot
involved
in
that
yeah
did
did
I
sell
this
well
enough.
C
Yeah
cool
Colin,
I
think.
If,
if
you
have
some
time,
we
could
arrange
and
we
could
go
through,
you
know
what
we've
done
on
that,
that
it's
basically
I'm
sure
you
know
it's
based
on
Tech
times,
so
it's
fairly
straightforward,
making
use
of
coza
and
because
of
building
it
and
all
those
commands,
and
it
just
run
you
through
it
and
then
just
sort
of
give
you
a
quick
introduction
and
then
you
can
then
tell
us.
What's
the
best
way
to
go,
then.
F
A
F
Time
to
work
on
this
because
we
can't
break
everything
but
yeah
we
usually
benefit
I
think
this
does
lead,
though,
to
like
the
next
topic.
At
the
same
time,
I
feel
like
this,
how
thinking
of
the
OS
as
a
container
image
and
and
driving
from
that
you
know-
we've
been
like
slowly
reoranting
ourselves
towards
that,
but
my
my
whole
should
be
on.
This
is
basically
the
OS
has
a
bootable
container.
F
It's
not
an
openshift
feature,
it
should
be
a
Linux
feature
and
the
the
Centos
Bootsy
stake
is
very
much
taking
like
many
steps
forward.
It's
like
what,
if
we
have
a
much
smaller
image
than
Rel
core
OS
today,
that
is
actually
produced
in
version
from
the
OS.
So
like
I'd
love
to
see
the
bootable
OS
image
comes
from
Centos
like
what
Centos
produces
is
not
composes
and
yum
repos,
but
a
bootable
container
image,
that's
CI
tested,
and
we
take
that
very
seriously
and
and
it's
integrated
into
CI
processes
and
Centos.
F
F
Focus,
which
would
probably
not
be
tecton
but
I,
don't
know
we
yeah
there's.
D
B
F
Short
term
and
there's
a
bunch
of
stuff
like
if,
if
Bootsy
succeeds
and
rpmo
Street
would
basically
be
deprecated
because
we'd
stop
doing
package
installs
per
node.
All
that
stuff.
F
On
there,
but
in
order
to
get
the
booty
Sig
off
the
ground,
other
people
need
to
agree
to
join
like
so.
F
In
that,
like
couple
steps
ahead,
how
do
we
do
this
in
a
Centos
context,
decoupled
from
openshift,
so
it
can
be
used
on
iot?
It
can
be
used
for
desktops
all
that
type
of
stuff.
Please
feel
free
to
join
the
thread.
I'm.
B
Can
you
drop
a
link
in
the
meeting
notes
so
that
people
can
find
out
more
info.
B
All
right
cool
any
other
questions
or
comments
in
regards
to
what
Colin
was
laying
down
there.
E
I
I
guess
the
question
to
Timothy
is:
is
there
any
implications
that
are
on
the
Fedora
because,
obviously
with
okd
we've
got
the
Dual
base
now
with
Fedora
and
Centos,
and
so
I
was
just
wondering
if
there's
any
any
ceramic
ramifications
for
the
fedoracas
and
where
we
also
have
two
different
build
processes
for
the
two
different
versions
at
the
minute.
So.
A
D
The
part
of
this
is
like
already
done
right
now
in
the
escos
pipeline,
so
the
escos
pipeline,
as
is
the
setup
for
KD,
is
building
one
single
image
and
is
then
layering
using
chorus
layering
to
clear
the
packages
just
for
okg
to
ship,
any
in
all
the
variants.
So
there's
only
just
like
one
core
image
of
s-cos
saturation
course,
which
is
kind
of
independent
over
KD,
and
then
it's
made
to
be
what's
used
by
okd
for
its
string,
each
each
version.
Okay.
D
So
it's
part
of
doing
that
for
at
another
level
in
essence,
doing
that,
but
pushing
that
to
like
being
the
true
part
of
central
stream
to
partner
like
being
a
core
image
based
OS,
that
we
have
in
central
stream
that
could
be
used
for
everybody,
which
is
just
not
something
used
just
for
KD
but
being
there
for
everybody
to
use
and
and
and
then
yeah
okg
would
consume.
That
and
do
it
like.
It
does,
does
right
now
at
the
packages
that
it
need
Etc
or
anything
like
that.
So.
E
That's
nice,
yes
right,
sorry,
but
but
for
the
Fedora
release.
Would
that
play
better
with
the
Fedora
Community,
because
obviously,
we've
got
the
Dual.
We've
got
the
Dual
Parts
at
the
minute
for
Fedora
and
Santos
stream,
core
OS,
so
I
know
that
for
the
Fedora
Community
already
creates
a
core
OS
image:
that's
not
a
an
okd
image.
E
So
does
this
mean
that
this
is
going
to
be
easier
to
actually
then
retrofit
the
same
process
onto
the
Pandora
released
image,
or
will
there
be
some
alignment
needed
between
the
the
current,
the
center
stream
and
the
fedora
released
images?
So
we
can
then
use
it
in
okay.
The
does
that
make
sense.
D
For
federal
growth
right
now,
the
Yorkie
Burns
is
as
well
something
built
on
top
of
federal
cores.
So
it's
already
a
container
built
now
a
earlier
build,
so
I
guess
whether
or
not
where
exactly
this
bit
happens
in
federates.
It's
unclear
right
now,
because
in
federal
we
have
like
more
a
lot
more
variants
like
we
have
desktop
Brands.
We
have
iot
Etc,
and
so
how
exactly?
This
is
going
to
be
laid
out.
D
We
don't
really
know
yet,
but
the
thing
is
that
we
probably
don't
want
to
change
how
federacurus
like
looks
like
right
now,
because
we
want
to
keep
things
working
for
users
right
now.
So,
even
if
we
change
things
that
below
it's
likely
that
the
interface
will
stay
the
same
and
that
okay
D
could
consume
that,
it
could
also
be
that
okay
D
could
consume
something
like
below
Federal
cross
directly
and
like
not
gate,
continuity
or
something
like
that
in
the
image,
for
example,
that
would
slim
down
the
image.
D
You
would
only
get
podman
cryo
and
something
like
that,
and
we
would
stop
having
containerd
in
okd
where
it's
basically
unused
and
something
like
that.
So
there's
pros
and
cons
every
time
we
do
things
like
that,
because
we
yeah
you
would
like
benefit
less
from
the
testing.
That
is
unfair
request,
but
at
the
same
time
you
would
be
life
cycle
movies
with
raw
which
matches
what's
needed
for
Kitty
right
now.
So
it's
it's
also
interesting.
F
A
D
So
the
build
is
done
differently
for
Federal,
corrects
and
Central
history.
D
Is
built
in
the
tecton
pipelines?
Of
course,
fcus
is
still
built
in
Pro
as
far
as
I,
remember
and
I
think
that
this
repo
here
has
some
Docker
files
or
some
friendship
that
has
layered
builds,
but
maybe
I've
forgot
something
I
don't
work
on
this
one
all
the
time
and
for
sure
Christian
would
have
more
info.
B
All
right
and
just
a
heads
up
that
at
our
next
meeting
we
will
have
a
next
working
group
meeting
in
two
weeks
on
the
28th
we're
gonna
have
Ali.
Is
it
mobrum?
Is
that
or
mobrim?
Is
that
how
you
say
it
El
Miko,
do
you
know.
B
Yeah
right
so
m-o-b-r-e-m
products
manager
for
openshift,
a
product
manager
is
going
to
come
and
talk
to
us
and
talk
a
little
bit
about
trying
to
get
more
Community
involvement.
B
B
G
He
is
I,
think
he's
specifically.
He
is
like
a
ux
UI
project
manager,
so
he
wanted
to
talk
about
some
of
the
things
kind
of
around
that
that
aspect.
Excellent,
so
like
customizing,
consoles
and
stuff,
like
that,
I
think.
G
B
B
For
sure,
so
is
there
anything
else
that
folks
want
to
talk
about
before
we
in
the
meeting?
Is
there
anything
else
that
we've
missed
I.
G
Had
a
couple
items
I
added
to
the
agenda
there,
oh
yeah
go
right
ahead
under
the
Community
Development
updates,
so
I
did
make
an
initial
Communications
page
to
contribute
to
the
site
and
I
opened
a
PR
for
it,
I
also
to
draft,
along
with
what
Brian
was
saying
earlier.
G
I
created
a
card
on
the
planning
project
for
it
as
well,
and
I
moved
it
up
to
like
in
review
status,
because
I
basically
did
all
the
other
work.
So
I
went
through
and
tried
to
Monkey
around
with
like
how
we
would
Plumb
and
issue
all
the
way
through
to
the
planning
board
and
everything
and
I
I
worked
through
a
few
of
the
I
guess,
a
few
of
the
speed
bumps
on
the
way.
So
some
of
you
might
have
seen
emails
come
into
your
box
about
like
cards
being
created
and
deleted
and
stuff.
G
That
was
just
that
was
me
trying
to
figure
out
the
proper
way
to
link
these
things
together.
But
after
I
did.
That
I
also
made
a
comment
on
Brian's
card,
because
Brian
had
made
a
card
about
like
wanting
to
do
some
planning
around
like
how
we
use
that
project
board.
So
I
made
a
bunch
of
notes
about
my
experiences
to
hopefully
help
contribute
to
the
conversation
that's
happening
there.
G
The
okd
io
website
I
also
found
there's
a
CI
problem.
Currently
so
we're
not
processing.
You
know.
New
PRS
like
the
workflow,
doesn't
work
so
I
put
up
a
fix
for
that
as
well.
So
you
know
just
whenever,
whenever
we
get
back
around
to
it,
like
the
21,
PR
I
think
is
needed
first
and
then
the
20pr
could
go
after
it,
but
really
I'd
like
people
to
take
a
look
at
that
number
20
PR
just
to
see.
G
B
All
right
well
we'll
go
ahead
and
end
the
meeting
here
and
feel
free
to
reach
out
and
slack
or
the
working
group
Google
group
email
list,
if
you
have
anything
pop
up
and
if
folks
folks,
in
the
meeting
here
that
are
involved
with
the
Community
Development
meeting,
take
a
look
at
the
board
so
that
we
can
hit
the
ground
running
next
week
to
start
tackling
some
of
those
things
or
at
least
organizing
them
and
and
having
status,
updates.
Clear
status
updates
on
them
all.