►
From YouTube: OKD Community Development Meeting 05-02-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
Welcome
to
the
okd
Community
Development
meeting
for
the
second
day
of
May
of
2023,
and
we
have
the
task
board
in
front
of
us
and
essentially
were
a
little
light
on
participants
today,
because
we've
got
a
lot
of
folks
out.
So,
let's
just
take
a
look
at
the
board,
really
quick
and
talk
about
some
of
the
things
that
happened
in
terms
of
new
stuff.
There's
no
motion
on
refreshing,
the
home
page
review
and
refreshing
the
home
landing
page.
B
C
Okay,
so
I've
created
number
32.,
which
is
investigate
a
Blog
plugin.
So
at
the
minute,
it's
a
bit
clunky
to
add
a
Blog,
because
we've
got
to
go,
create
the
blog
entry
then
manually,
to
update
the
indexing
where
there
are
a
couple
of
plugins
available
to
MK
docs,
which
do
that
for
you
automatically
so
before
I
went
and
moved
all
the
guides.
I'm
gonna
activate
one
of
the
plugins
I'm
just
investigating
it
now
and
check
testing
it
out.
C
But
the
idea
is
you
put
a
little
bit
of
metadata
and
then
it
gives
you
a
summary
page
with,
like
the
first
sentence
of
each
blog
and
standard
blog
layer,
types
things
and
that's
automatic
Automatic
by
adding
something
to
a
subdirectory
of
the
blogs
folder
within
docs.
So
I'm
going
to
add
that
in
and
then
once
I've
added.
That
in
I
can
then
move
all
the
the
guides
across
rather
than
having
to
do
on
the
manual
index.
Page
updates.
B
B
No
progress
on
the
techton
docs
I
was
working
on
the
other
stuff
and
they
are
still
making
sort
of
changes
in
their
process.
Right
now,
they're
actually
mid
change.
A
Yeah
on
the
techton
stuff,
the
like
I
had
to
uninstall
Catan
from
the
411
on
the
way
to
412,
because
it
was
using
apis
that
were
removed
from
the
latest
version
of
kubernetes.
Do.
A
That
well,
it
was,
it
was
well,
let's
see
which
one
was
it.
C
But
I'd
imagine
that
would
be
getting
fixed
fairly
quickly
because
tucked
on
the
tecton
project
really
has
to
work
on
the
latest
kubernetes,
and
these
are
kubernetes
rather
than
openshift
apis,
so
I'm,
imagining
that
will
get
fixed
pretty
quickly
within
the
kubernetes
project.
B
Excellent
video
content,
no
one's
approached
me
with
any
more
video
content
that
they
wanted
to
write
or
produce.
I
should
say,
but
yeah
we've
got
that
open
in
the
backlog,
because
we
can
do
more
video
content.
We
just
need
ideas
and
I'm
happy
to
provide
the
video
editing
services
for
it
and
recording
I
can
meet
up
with
folks
online
and
record
them,
and
then
you
know,
do
the
file
write
a
project
board
guidelines.
B
We
haven't
really
had
anyone
take
that
yet
and
update
the
installing
openshift
on
single
node
instructions
in
end
of
in
the
end
user,
Docs
right
and.
B
B
C
The
idea
is
that
we're
going
to
create
the
single
node
instructions,
get
them
validated
and
then
once
we've
got
the
instructions
working,
we
then
need
to
update
the
actual
official
docs
right.
B
B
C
So
so
I
mean
I
think
the
other
thing
we
want
to
do
is
work
out
where
we
want
to
put
Luigi's
stuff
within
the
docs,
because
Luigi
did
a
hand
cranked
single
note,
install
from
sort
of
bear
sort
of
config
and
how
to
build
it
up
yourself,
manually,
yeah,
so
I
think
that
will
be
useful.
I
mean
it
is
almost
like
a
UPI
installed
for.
B
B
I
everyone
sort
of
nav
gravitated
towards
the
insist,
the
assisted,
installer
and
we've
been
getting
lots
of
questions
about
it.
But
my
I'm
still
thinking
back
to
when
I
first
started
with
openshift
and
okd
I
was
doing
hand
cranked
stuff,
I
I
think
it'd
be
useful
as
a
blog
post
and
then,
if
it,
if
it
seems
like
it's
getting
some
traction
and
if
it's
something
that
can
be
duplicated
over
time,
then
moving
into
something.
That's
a
that's
a.
B
Then
moving
over
to
the
ready
section
review,
licensing,
copyright,
that's
you
and
Luigi
and
Luigi
is
going
to
talk
to
Red
Hat
internally,
haven't
heard
anything
back
on
that
next
time
we
see
him
we'll
we'll
ping
him
on
some
of
these
review
survey
responses.
I
did
I
shared
those
out
with
you
right.
B
The
link
is
also
the
link
is
also
in
that
other
ticket
for
synthesize.
The
survey
results
into
something
visually
appealing,
so
the
link
is
is
in
that
so
34
as
well
yep.
So
go
ahead
and
start
looking
at
that
and
that'll
inform
and
you'll
see.
This
actually
I
did
start
constructing
2023.
That's
in
progress,
number
33
and.
B
Basically,
I
think
we
can
look
at
the
responses
and
go
okay.
This
question
didn't
quite
get
us
what
we
were
getting
at,
or
maybe
we
need
to
word
this
differently.
You
know
based
on
responses.
We
can
sort
of
improve,
I,
think
the
2023
survey
and
it
looks
like
if
you
and
I
work
together
over
the
next
couple
weeks.
C
B
B
Like
it
excellent
collect,
use
cases
for
feature
toggle,
we
never
really
that
never
got
any
traction
and
I
I
actually
didn't
hear
anything
from
Red
Hat
anymore
about
it
being
used.
No.
C
B
A
A
B
B
Yeah
I
mean
it
sounds
good,
but
we
just
don't
have
enough
people
I
think
that
we're
tracking
or
communicating
with
who
do
are
doing
experimental
stuff.
We
know
there's
people
doing
experimental
stuff,
but
we
don't
know
who
and
we're
not
in
any
we're,
not
communicating
with
them,
and
we
don't
really
have
any
features
unique
to
okd
right
now.
Yeah
yeah.
A
C
A
C
B
Well,
it's
you
know,
I
mean
I've
I've
been
leaning
towards
the
get
up
stuff
lately
and
and
I.
Think
if
you,
if
you
have
your
manifests,
you
can
do
it
and
now,
with
ACM
Advanced
cluster
manager
and-
and
you
know
the
non-commercial
offering
like
you-
can
spin
up
clusters
pretty
quick,
but
there's
always
a
bunch
of
nuances
of
things.
Maybe
you
didn't
capture
and
you
know
different
resource
names
in
AWS
and
things
like
that's
if
you're
doing,
AWS
or
whatever
so
there's
it's
not
a
perfect
rebuild
every
time.
Yet
I
don't
think.
A
A
If
you,
if
you're,
going
to
actually
do
what
you're
wanting
not
only
you'd,
have
to
get
kubernetes
itself
to
be
working
under
get
Ops,
but
every
single
thing
that
was
run
on
it
yeah,
which
means
that
I
guess,
if
somebody
did
an
ad
hoc,
you
know
like
build
a
container
push
it
some
repository
and
then
do
a
pull
into
kubernetes
or
into
okay
d.
A
Then
there's
a
lot
of
manual
processes
in
that
and
they
would
just
go
away
when
you
rebuilt
the
cluster
yeah
and
so
you're
you're,
asking
for
a
certain
amount
of
discipline
from
all
of
the
users
as
well,
which
I
think
is
a
heavy
ask.
Yeah.
B
All
right,
reach
out
to
volunteers,
that's
an
ongoing
process.
We
did
get
two
new
people,
volunteering
in
the
past
couple
months,
which
is
good
like
we
were
showing
up
to
meetings
for
the
most
part
regularly.
C
Yeah
I
mean
I
just
had
a
thought
that
I
wanted
to,
because
I
know
that
red
hat.
Do
you
advocacy,
sort
of
local
advocacy
I'm
just
wondering
if
we
can
do
anything
to
try
and
get
people
to
go
and
speak
Acts,
local,
meetups
and
local
events
to
try
and
promote
okd
and
the
community.
B
I
think
so
yeah,
let's,
let's
put
a
note
in
there.
Actually,
why
don't
you
go
ahead
and
update
that
and
put
that
in?
As
a
note,
the
other
thing
that
I
was
thinking
of
is
I
need
to
update
that
item
with
I
did
add
a
volunteers
subgroup
in
GitHub
so
that
we
can
add
people
as
volunteers
now
and
sort
of
treat
them
as
a
group.
B
So
I'll
need
to
add
a
note
for
that
as
well.
B
And
okay
missing
security
contacts
looks
like
we
just
need
someone
to
update
the
website
with
that
yeah.
C
B
I'll
I'll
add
myself
to
it:
I'll
go
ahead
and
get
to
that.
Let
me
add
myself:
you
got
a
lot
of
other
stuff
going
on
as
well
so
and
I'm
starting
to
crank
through
my
stuff.
B
That's
weird!
It
must
remember
if
you've
like,
where
you
left
off,
because
I
just
loaded
that
page
and
I
know
I
didn't
scroll
through
them.
Let's
see
investigate
tutorials
for
setting
up
okay
determine
if
you
have
good
options
to
refer
people
to
okd.io.
B
This
was
a
Diane
thing
and
then
Michael
asked
about
if
we
could
repurpose
the
openshift
container
platform
item
Diane's
been
kind
of
hidden,
Hit
or
Miss
showing
up
but
I,
don't
think
we
want
to
assign
things
to
her
anymore.
C
A
C
Think
this
is
all
about
what
is
the
first
encounter
for
somebody
discovering
us
as
I
say,
we
just
migrated
the
old
cycle,
which
is
the
new
MK
doc
stuff,
and
it's
a
lot
of
fluff
and
not
a
lot
of
useful
information.
If
I
can
say
that
without
being
too
derogatory
and.
C
Lot
of
there's
a
lot
of
buzzwords
on
the
page,
but
not
a
lot
of
information,
so
I
I
think
we
need
to
really
try
and
look
at
the
home,
the
whole
home
page.
What
the
messaging
is
and
because
again,
we
had
a
lot
of
we've
had
a
few
discussions
around
people,
don't
quite
understand
that
what
okd
is
and
what
they
can
do
with
it
and,
more
importantly,
what
resources
they
need
for
it.
They
they.
They
hear
their
thing.
It's
a
community
version
and
they
don't
really
know
what
the
relationship
to
Red
Hat
is.
C
What
relationship
to
openshift
is
the
fact
that
it
is
truly
free
to
use
no
license,
even
though
it
uses
most
of
this,
the
open
shift,
container
platform
source
code,
so
I
I
think
we
just
have
to
look
at
that
and
again
I'm
getting
the
point
of.
Maybe
we
just
need
to
set
up
a
a
monthly
working
session
somewhere,
a
time
that
like-minded
people
can
get
together
to
work
on
something
rather
than
having
a
meeting
well.
B
C
Mean
the
other
thing
is:
we
could
use
the
first
month,
the
first
Tuesday
of
the
month
to
do
the
Board
review,
the
second
one
as
a
working.
That
might
be
another
one,
because
I
I
think
something
like
this.
It
needs
the
community
to
contribute
as
a
whole,
so
having
a
brainstorming
in
our
brainstorming
session
to
actually
Define
what
we
want
the
messaging
on
the
homepage
to
be,
then
someone
can
go
and
create
it,
but
I
think
it's
a
group
discussion
rather
than
one
person
who'll,
do
all
the
work.
B
Do
you
want
to
run
let's,
let's
run
with
that,
then
starting?
Do
you
want
to
start
in
two
weeks
and
and
just
have
that
be
the
first
meeting
of
going
through
the
site
and
and
listing
the
things.
B
And
if
folks
and
I'll
send
something
out
over
the
working
group
email
and
if
we
get
enough
people,
then
yeah,
let's
run
with
it
for
sure
you
know:
okay,
okay,
the
operator
discussion,
I,
see,
there's
been
some
some
movement
on
that.
The
for
the
meeting.
C
B
That
the
community
virtual
meeting
to
help
create
catalog
of
operators
for
operator
Hub,
I.
C
B
B
B
There's
a
lot
of
us
on
that
and
I
think
that
I
was
kind
of
waiting
for
them
to
get
a
little
more
clarity
in
terms
of
the
builds
and
stuff
like
that,
and
their
cycle
I
feel
like
now
that
they're
starting
to
hit
a
stride
with
that
so
I
think
now
we
can
actually
tackle
this
and
have
a
sense
of
where
things
are
going
and
I
had
also
had
heard
some
murmurings
of
internal
things
that
were
that
I'm
curious
if
those
are
becoming
extra,
honest
outside
of
red
hat,
okay,
so
yeah.
B
B
C
Think
it
goes
back
to
well
there's
a
question:
do
we
want
the
s-cos
to
be
part
of
that
initiative,
or
just
the
epcot's
version
yeah.
A
C
C
C
C
B
Well,
let
me
I'll
reach
out
and
find
out
exactly
specifically
what's
needed,
because
that's
the
thing
is
when
they
say
Well
we'd,
like
the
community,
to
take
it
over
well.
Okay,
does
the
community
actually
have
access
to
change
that
manifest,
which
is
it
which
relates
to
the
certificate
right?
So
then
the
question
is,
like
you
know,
we're
gonna
we're
gonna
have
to
have
someone
regularly
do
that.
B
B
And
I'll
just
reach
I
forget
the
person's
name,
but
I'll
reach
out
to
the
person
that
actually
said
a
couple
weeks
ago.
You
know
we
want
the
community
we'd
like
the
community
to
get
this
over
okay
and
then
we've
got
the
homepage
stuff,
which
basically,
we
know
yep.
C
B
C
B
All
right
review
license
and
copyright
requirements.
B
And
okay,
moving
over
to
in
progress,
create
document,
so
Mark
311
as
end
of
life.
That's
in
progress
and.
B
Yeah,
yes,
okay,
create
documentation
for
sugar
node.
We
know
where
that's
at.
B
C
It's
a
shame
that
none
of
the
red
haters
are
there
because
I
want
somebody
unless
Jenny
or
Bruce
you've
got
time
to
go
and
look
at
that,
there's
a
link
to
their
where
the
where
the
document
is
on
the
issues
are
with
it,
be
interesting
to
see.
If
you
get
the
same
issues.
B
A
A
Yeah
I
might
I
mean
I've
vaguely
been
interested
I'm
sort
of
up
to
my
years
in
Project
supervision
at
the
moment,
but
I
might
be
able
to
give
it
a
shot
in
the
next
two
weeks.
C
Yeah
well
I'd
say
you
follow
that
link
that
I
put
in
the
draft
guide
can
be
found
here
three
weeks
ago.
It's
on
my
it's
it's
in
my
GitHub.
C
That's
a
step
by
step,
so
that
should
be
easy
to
follow.
Require
should
require
no
figuring
out
a
thought
other
than
when
it
doesn't.
Work
is
to
work
out.
A
C
But
the
the
the
the
the
core
OS
is
still
a
bit
of
a
mystery
for
me,
how
it
all,
how
it
all
happens
and.
A
Right
my
issue
with
all
those
things
is,
is
always
when
I
start
before
the
you
know
the
pivot,
which
version
of
S-Class
F
costs,
do
I
need
to
use,
but.
C
Yeah
so
I
I'm
actually
using
the
same
version,
but
the
the
S
cost
pivot.
It
fails
before
the
pivot.
The
F
cross
gets
through
the
pivot,
but
then
the
cluster
doesn't
come
up
cleanly,
so
I
I
think
there
might
be
something
to
do
with
the
assisted
installer
config
issue
there,
but
it
means
start
debugging
stuff
that
I'll
just
have
my
time
to
get
around
to
it.
Yet.
B
All
right,
well,
let's
play
around
and
see
if
we
can
duplicate
that
I
can
definitely
try
to
give
it
a
shot
and
take
a
look.
Updating
cluster
section
needs
to
be
updated.
That's
a
Mr,
Burke
I'll
reach
out
again
see
if
I
can
get
him
investigate
the
plug-in.
We
talked
about
that
Brian
you're
doing
the.
A
B
Collecting
a
plug-in
for
updating
the
making
the
blog
post
process
easier,
remove
some
support
section
from
the
okd
docs.
B
B
B
Construct
survey:
we
talked
about
that
so
I'm
working
on
the
survey
for
2023
link.
Is
there
so
I
can
get
feedback
over
the
next
like
two
weeks
or
so
that
would
be
awesome
and
then
we'll
put
it
out
and
then
synthesizing.
The
survey
results
working
on
that
making
some
graphs
and
that
will
help
inform
how
I
manipulate
the
data
from
the
2023
survey.
Now
the
question
is:
have
the
survey.
B
Like
there's
a
point
where
we
should
just
sort
of
take
a
snapshot
and
then
say:
okay,
let's
put
up
a
new
survey
next
year
or
whatever.
C
C
And
I
actually
have
an
annual
cycle
there.
It
goes
live
in
May
you
go
up
to
August
September,
you
publish
the
results.
Okay,
the
other
thing
is,
ideally,
it
should
tie
in
with
our
road
map.
So
exactly
we
want
to
publish
the
roadmap
in
September,
then
that
would
be
a
good
thing.
If
we're
looking
to
do
a
road
map
May
June
time,
then
the
results
need
to
come
out
right
before
that
road
map
and.
B
I
would
say
that
that
you
probably
need
a
month
or
two
between
when
the
survey
closes
to
actually
factor
that
stuff
into
the
road
man
yeah,
okay,
all
right!
Well,
let's,
let's
get
feedback
then
on
the
road
map
construction
process
at
next
week's
meeting
and
then
I
think
that'll
help
inform
survey,
time
frame,
update
dependency
versions
for
okd
DOT
IO.
That's
in
review
and
looks
like
you
got
to
commit
from
three
weeks
ago.
For
that.
C
C
Yeah,
it's
just
making
sure
that
we're
not
using
old
images
or
our
libraries
that
may
have
CDs
or
anything
like
that.
Okay,
so
I
mean
I'm,
no
one
shouted
and
said:
I've
broken
anything
so
I'm
I
think
I'm.
B
C
C
And
there
was
a
couple
of
changes
that
really
made
from
my
comments,
but
I
don't
know
whether
we
want
to
formalize
this
piece
and
actually
have
two
or
three
people
look
and
comment
or
whether
it's
just
like.
We
leave
it
there
for
a
couple
of
weeks
and.
B
So
one
of
the
things
that
that
other
groups
do
is
they
have
sort
of
a
like.
You
need
like
two
maintainers
or
three
main.
You
need
a
number
of
reviewers
right
to
do
that.
Do
we
want
to
do
that
for
stuff
for
the
website?
That's
you
know.
Is
that
going
to
be
too
tedious
if
we
make
it
that,
like
at
least
two
of
us
need
to
sign
off
on
it.
C
I
think
there's
two
answers
there.
When
there's
like
maximum
like
four
or
five
people,
making
changes,
I
think
yeah,
it's
not
an
issue
but
I'm
hoping
we
get
to
the
point
where
there
are
tens
and
twenties
of
people
making
changes
right,
some
of
which
are
going
to
be
first
time,
changes
newbies
and
that's
when
you're
going
to
want
a
little
bit
more
scrutiny.
C
But
yeah
I
mean
so
this
really
comes
back
into
the
document,
the
document,
the
process,
it's
like.
What
do
we
want
in
terms
of
who
can
sign
off
emerge
and
then
what
is
the
if
we,
if
they've
done
a
sign
off
correctly,
do
we
need
a
post,
merge
review
or
how
do
we
want
to
apply
it
and
I
don't
have
an
answer.
C
A
Right,
well,
maybe
what
we
could
do
is
go
ad
hoc,
Until,
It,
Breaks,
and
then
you
know
put
in
the
structure.
Then.
Okay,
in
other
words,
you
know.
As
long
as
you
know
the
informal
you
know
it
it,
you
know,
hasn't
broken
anything
yet
so
we
might
as
well
approve
it
as
long
as
that
works,
we
stay
with
that
and
we're
ready
for
her
growth
yeah.
We
don't
get
too
encumbered
by
process,
albeit
good
process.
I
mean
I,
agree
with
you
on
that
before
we
get
the
growth.
B
Should
we
start
putting
documents
that
we
want
to
collaboratively
work
on
in
the
planning
section
like
I'm
thinking
about
okay,
this
document
to
outline
processes
and
what
are
all
of
the
tasks
that
we
need
to
do
cyclically
I'm
feeling
like
we
should
just
start
adding
documents
within
that
repo
within
the
planning,
repo
and.
C
B
C
A
C
B
B
C
B
B
C
In
a
branch
yeah,
but
the
web
page
that
will
become
and
then
what
it
means
is
that
you
can
then
run
the
MK,
docs
or
npm,
build
right
command
and
have
a
local
version.
So
you
can
actually
then
check
that
you've
got
the
formatting
correct,
whereas
MK
dot
or
if
you
use
hack,
MD
you've
then
got
to
transpose
it
across
and
add
the
formatting
in
and
right
I
mean
I'm
I'm
I
I'll
go
either
way,
but
I'm
just
thinking.
C
Well,
if
the
end
result
is
going
to
be
a
web
page,
we
can
just
create
a
branch
for
the
issue
and
then
collaboratively
work
on
that
Branch
without
it
impacting
the
main
live
version,
and
then
people
can
just
use
their
local
sort
of
workflow
to
actually
check
the
formatting,
see
what
it
looks
like
within
the
and
then
we
can
just
crush
the
branch.
If
we,
if
it
all,
goes
wrong
and
we
abandon
it
and
it's
it's
causing.
A
C
Cool
men
just
just
name
the
branch
in
the
just
just
create
an
issue
that
when
we
get
so
like
in
that
calendar
one
we
can
say
moving
to
branch,
whatever
yeah,
and
then
we
can
actually
just
say:
yeah.
Okay,.
B
C
I'm
just
I'm,
just
just
in
the
minutes,
we
probably
want
to
I'm
just
looking
here
yeah.
We
probably
just
want
to
document
that
we're
thinking
of
alternate
meetings.
B
B
All
right
and
then
I'll
get
that
form
out.
Regrettably,
my
plan
to
hopefully
connect
with
more
people
here
to
let
them
know
that
the
Forum
was
coming
to
for
meeting
time
didn't
quite
work
out.
It
is
the
inverse
of
what
I
intended
so,
but
I'll
go
ahead
and
send
that
out
with
three
options,
basically
follow
GMT,
keep
it
at
what
would
be
for
me
noon.
Eastern
so
switch
the
GMT
time
or
provide
a
different
suggestion.
Those
will
be
the
three
options.
A
B
Right
I
think
we're
good.
Then
thanks
Bruce,
for
showing
up
give
your
puppy
some
love
for
us.
What's
your
puppy's
name.
A
I
think
that's
classified
I'd
have
to
ask
my
wife.
If
I
can
divulge
that
information.