►
From YouTube: OKD Community Development Meeting 04-04-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
B
Planning
board
cards
and
and
go
ahead
and
get
started.
Let's
look
at
what's
in
progress
here
so
in
progress.
We
have
create
documentation
for
single
node
installation,
non-assisted,
installer
Luigi.
That's
you
yeah
yeah,.
C
Absolutely
so
I
mean
I,
I
have
I
mean
I've,
I've
actually
had
someone
else,
look
at
it
and
they
they
didn't
install
and
they
there
were
some
lots.
C
Because
it
actually
is
feel
involved,
but
they
managed
to
get
something
going
so
I
mean
I've
I.
Think
in
this
point
in
time,
it's
ready
ready
for
review
and
maybe
having
some
eyes
on
it
and
people
trying
it
out,
testing
it
and
commenting
on
on
the
documents.
So
would
it
be
okay
to
move
it
into
in
review
or
and
then
yeah
just
have
the
links
shared
with
everyone
yeah.
C
C
E
Would
be
the
best
I
mean
there
are
two
places
it
could
go.
It
could
either
go
into
the
official
documentation
because
we
don't
have
anything
in
the
documentation
for
single
node
installed
for
okd.
We
remove
this
section
because
the
ocp
docs
send
you
to
the
assisted
installer
website.
The
red
hat.com
hosted
assistant
installer.
Well,
the
other
thing
is
we
could
put
it
in
okd.io.
E
So
my
second
comment
was:
it
does
mix
ocp
and
okd
within
the
dock.
Yes,.
C
Yes,
it
does
I
can
I
can
take
all
that
out
and
add
in
and
remove
all
the
the
ocp
specifics.
Yeah.
E
A
E
And
you're
not
familiar
as
familiar
with
okd,
it
might
be
a
little
bit
more
confusing,
so
they
were.
They
were
my
two
thoughts
on
it.
Yeah.
C
Yeah
now
the
only
reason
why
I
did
it
was
it
was
initially.
It
was
my
internal
guide
so
that
I
could
I
could
do
okd
or
ocp
builds
locally
on
a
single
node
at
any
time.
So
that's
why
I
included
both,
but
I
will
take
out
all
the
specifics
for
ocp,
make
it
okd
and
then
so.
Okay.
So
let's
leave
it
in
in
progress
because
I'll
I'll
move
it
over
to
maybe.
B
C
Because
just
so
that
I
can
put
it
into
a
into
a
format
for
for
the
for
the
either
okd
blog
or
as
Brian
mentioned
in
the
documentation
or
yeah
I.
Don't
know
Brian
I
mean
you
tell
me
the
only
reason.
C
E
B
B
A
C
B
E
E
C
I
think,
do
you
have
a
sort
of
maybe
a
quick
intro,
a
little
guide
on
how
to
get
it
up
and
running
in.
E
B
B
B
B
E
Yeah
I've
not
I've,
not
heard
anything
from
Michael.
B
All
right,
let's
I'll,
put
it
as
an
to
do
for
myself
to
reach
out
to
him.
Let
me
put
it
in
the
I'm:
gonna
do
a
card
for
it.
I'll
do
just
a
separate
foreign.
B
B
B
B
B
We
got
else
here
defined
a
getting
started
page
for
okd
openshift
beginners.
So
this.
B
E
There
was
also
some
comments.
Did
we
actually
need
that?
Because
Michael?
If
you
look
in
the
comments,
Michael
pointed
us
to
some
introduction
stuff,
there's
some
introduction
of
stuff
in
on
the
kubernetes
site,
so.
E
That
said,
there
was
a
conversation
around
and
Dwayne
I
think
this
come
back
to
some
things
that
that
you
encountered
that
people
don't
immediately
get
okd
in
terms
of
that,
it's
free,
it's
it
truly
is
free.
It's
it
is
open.
There
is
no
subscription
needed,
so
I
think
there
is
some
positioning
information.
We
need
I,
think
for
the
technical
stuff.
We
can
point
to
existing
content
yeah,
but.
B
So
does
it
make
sense
to
have
a
getting
started
page?
That's
a
stub
as
with
links
to
the
rest
of
these,
because
I
do
agree
that
the
kubernetes
getting
started
stuff
is
good
and
then
the
open
shift
kubernetes
overview
is
good,
but
does
it
make
sense
for
us
to
have
a
stub
just
so
that
we're
we're
at
least
organizing
it
in
a
way
that
might
be
helpful
in
terms
of
order
and
adding
any
new
things
that
come
up
and
and
whatnot?
It
is
another
page
to
curate,
but
it's
still.
It's.
D
A
E
E
What
I
would
do
is
I
would
I
would
close
this,
pointing
it
up
that
other
one,
but
put
a
synopsis
of
this
one
in
the
other
one
to
say
that
we
wanna
we
wanna
link
into
so
reference.
The
closed
issue
right.
Does
that
make
sense
yeah
just
so
we
can
buy.
We
combine
the
two
threads.
We
need
to
redo
the
home
page,
but
it
has
to
contain
this
discussion
as
well.
A
B
B
D
B
B
B
B
And
we
want
help
wanted
on
redesign
right
because
we
because
we
don't
actually
have
a
designer,
so
we
should
tag
that
yeah
as
help
wanted
all
right.
Let
me
add
that
to
that
one
help
wanted
all
right:
I'm,
good,
okay,
all
right
so
we'll
deal
with
those
review
guides
section.
We
still
need
to
review
the
guides
sometime
in
the
near
future
so
that
we
can
just
prune
all
that
stuff
out
well,.
E
B
B
E
B
B
B
I
did
create
a
volunteers
group,
so
we
now
do
have
a
a
group
that
is
a
user
group
that
is
just
for
volunteers
and
added
some
people
to
that
who
are
just
volunteers
and
then
maybe
we
could
have
like
volunteers,
something
something
and
then
maintainers
that
might
be
a
way
to
start
that.
E
Yeah
I
mean
I'm
just
trying
to
find
out
where
it
is,
but
I'll
meet
code
put
some
notes
together
because
he
looked
at
the
process
of
going
through
a
a
get
change
and
he
wrote
some
notes
on
that
and
he
did
send
a
link
to
them.
But
I
can't
I
can't
find
them
because
we
should
link
them
into
that.
One.
E
B
B
B
B
B
Yeah
exactly
yeah
review
license
and
copyright
requirements
for
community
repos
and
that
one's
on
you,
Brian
and
I
know
you've
got
a
lot
on
your
plate,
so.
E
Yeah
I
mean
I,
I
was
just
what
I
need
to
do
is
just
find
some
time
to
go
and
look
at
just
look
at.
What's
there
and
I
think
also
need
just
some
need
some
feedback
Luigi
on.
E
E
C
B
But
leave
that
okay
should
I,
swap
that
out
then,
and
instead
Luigi
put
you
on
this
card
planning.
I'm
sorry
review
license
and
copyright
requirements.
Okay,
let's.
C
C
Yeah
the
LM
yeah
I,
shouldn't
I,
should
never
have
actually
I
should
have
gone
in
with
my
the
red
hat
one
and
left
the
other
one.
C
B
Now
we're
defining
a
diary
calendar
process
to
update
roadmaps
guides
and
glossaries,
and
that
was
like
to
basically
for
us
to
define
a
cycle
for
updating
everything
to
keep
revisiting
it,
and
we
Mr
branch
and
I
started
that
and
we
we
didn't
really
get
a
chance
to
finish
it.
Yet
so,
let's
get
together
in
the
coming
weeks,
buddy
and
and
see
if
we
can
just
hash
that
out.
B
So
basically
the
idea
is,
we
want
to
say
like
okay
annually,
let's
review
such
and
such
Docs,
you
know
quarterly,
let's
review
such
and
such
and
have
like
a
schedule
so
that
we
can.
You
know,
make
sure
that
we're
always
following
a
process
of
updating,
collect,
use
cases
for
feature
toggle.
We
didn't
ever
really
get
a
chance
to
to
do
this.
B
I
think
the
best
bet
would
be
I'll
assign
that
to
myself
we
asked
people,
we
created
a
discussion
item
and
some
people
chimed
in,
but
I
think
that
this
might
be
good
as
something
for
the
next
iteration
of
the
survey.
So
I'll
add
myself
to
this
and
add
this
to
the
next
iteration
of
the
survey
that
I'm
working
on,
because.
B
Way
to
engage
people
to
be
like
hey:
where
do
you
see
if
a
feature
toggle?
What
would
be?
What
would
be
good
for
that
reach
out
to
volunteers?
I
have
continued
I,
don't
know
how
to
gauge
this
as
like
a
it's
not
like
a
thing.
That's
done,
because
I've
been
sort
of
continuously
doing
it,
sort
of
promoting
Us
in
various
areas,
but.
D
I'll
yeah
go
ahead,
yeah
I
may
have
some
volunteers
or
some
new
users
coming
soon
I'm
talking
to
a
professor
and
hopefully
soon
we'll
we
may
I'll
join
in
on
some
Sno
things
to
get
them
into
the
okd
community.
I
think
their
class
is
actually
cyber
security,
so
I'm
trying
to
they
may
want
to
pull
in
from
that
angle,
but
we
will
see
soon.
A
Okay,
I'm
also
a
new
community
here,
so
I
would
like
to
volunteer.
So
you
can
also
count
me.
B
Okay,
all
right:
let's,
okay!
So
can
you
put
your
GitHub
username
in
the
chat
or
in
the
meeting
notes,
and
then
that
way
we
can
add
you
to
the
GitHub
group
that
we
have
We'll.
Add
you
to
our
volunteers,
section.
B
B
Okay,
let's
move
that
one
over
boom
that
one's
done
all
right
so
now
we're
ready
to
look
at
our
our
backlog.
Of
course,
I'm
working
on
the
the
tecton
one
and
Mr
Link
I
haven't
seen
it
the
past.
You
see
it.
Last
week's
Tech
beat.
A
B
A
C
A
C
B
Makes
sense
I'll
tell
you
what
I'll,
let's
just
let's,
let's
assume
that
Diane
wants
to
enjoy
her
retirement,
so
I
will
swap
myself
out
on
this
card.
I
I
do
a
fair
amount
of
video
work,
so
I'll
just
put
myself
as
as
the
person
on
this
one
well
I'll
add
myself.
There
we
go
and
if
she
happens
to
pop
up,
then
she
happens
to
pop
up
okay
reviews
survey
responses
that
Brian,
you
and
I
need
to
get
together
on
I.
B
E
C
Oh
yes,
so
what
I'll
do
is
I'll
I'll,
take
the
the
link
that
Jamie
provided
in
updated
the
ticket
and
I'll
start
working
on
on
getting
it
and
pushing
up
a
PR,
and
then
we
can
eventually
add
that
in
is
that
okay,
bro,
yeah
yeah,
okay,
cool
cool
cool,
great.
B
Yeah
we
were
going
to
have
an
event
to
sort
of
talk
about
the
the
operator
catalog
and
whatnot,
but
we
Luigi
is
also
planning
on
making
a
video
about
the
operator
pipeline.
B
This
is
kind
of
multiple
of
multiple
things,
sort
of
stuck
under
the
Community
virtual
event.
We
don't
really
have
an
update
in
terms
of
the
operator
catalog
stuff
to
be
able
to
have
an
event
yeah
yeah.
So
let's
keep
this
in
backlog.
I
think
because
I
think
the
the
catalog
I
think
that
having
a
virtual
event
is
a
good
idea,
but
we're
kind
of
heading
into
a
weird
spot,
because
we've
got
conferences
coming
up
the
next
couple
weeks,
so
I
think
scheduling
anything
in
May
or
June
is
probably
going
to
be
problematic.
E
Well,
what
I
was
thinking
is
maybe
just
a
range,
a
time
where
we
actually
have
a
meeting
just
to
discuss
the
direction,
get
those
interested
rather
than
actually
a
full-blown
event
like.
We
did
last
time
where
it
was
like
a
full
day
of
activities.
Let's
just
say
what
time
is
the
best
time
to
have
a
say
an
hour:
okay,
where
we
can
just
pull
those
that
are
interested
in
the
catalog
just
to
come
together
in
sort
of
just
talk
through
what
it
should
be,
how
we
move
it
forward.
E
To
meeting
okay,
yeah
yeah
I
I
think
event
was
was
a
lot
bigger
than
what
I
was
thinking.
I
was
just
a
way
of
trying
to
it's
it's.
How
do
we
actually
get
because
just
reviewing
it
sort
of
bi-weekly
we're
not
really
getting
any
any
sort
of
movement
on
this
I
think
it
just
got.
I
mean
internally
red
heart
when
they're
due
to
them,
they'll
just
get
people
together
and
put
a
probably
a
meeting
in
the
calendar
and
just
discuss
it
and
then
move
it
forward.
E
B
C
And
then,
and
then
yeah
yeah
Christian,
is
he
he
last
week
or
the
week
before
it
was
moving,
so
he's
been
quite
snowed
under
also
with
his
day-to-day
job,
so
but
I'm
sure
he
did
mention
in
a
meeting
we
had
a
while
ago
that
it'd
be
quite
interested
in
getting
involved
with
this
catalog
thing
and
I
agree.
C
E
Well,
let's,
let's
actually
think
week,
beginning
with
17,
because
this
week
is
coming
up
to
Easter
weekend
so
I
know
in
Europe
all
the
children
are
on
holiday
from
school.
So
a
lot
of
people
out
this
weekend
next
week,
so
the
week
between
the
17th
I,
don't
know
Tuesday
Wednesday
Thursday.
Is
there
a
preferred
day,
let's
find
when
people
are
most.
C
B
C
Yeah
so
Brian
you're
right
for
for
that
week,
April
the
17th
on
the
17th
yeah.
E
A
C
E
This
is
to
create
a
an
okd
catalog
of
operators
like
we
have
on
open
shift
and
like
we
have
the
community
operators
and
okd
is
missing
some
of
the
key
operators.
Things
like
pipelines
like
the
get
Ops
Argos
CD,
so
it's
to
create
an
okd,
specific
catalog
that
will
replace
the
open
shift.
Red
Hat
catalog
I'll
provide
some
of
those
operators
into
okd.
So
that's
what
we're
talking
about
in
terms
of
the
operator
catalog.
So
again,
if
anybody
wants
to
I
guess
the
best
thing
is
to
do
it
is.
E
If
you
look
on
the
project
board,
issue
number
19
put
your
name
on
there
and
we'll
make
sure
that
you're
include
you
get
notified.
B
B
Okay,
investigate
CRC
on
okd
option
from
the
red
hat
team
they
now
I
I
haven't
had
a
chance
to
talk
to
them
about
the
the
CRC
team
about
what
they
did
now
that
they're
doing
okd
builds
in
a
more
streamlined
fashion,
using
some
sort
of
tagging
or
something
has
anyone
talked
to
them
at
all
about
this,
because
they
they
did
some
work
a
couple
months
ago
and
I
just
haven't
had
a
chance
to
reach
out
to
them.
Yet.
C
B
B
All
right,
let
me
let
me
currently,
it
has
Diane
Brian
and
Michael
on
it.
I'm
gonna,
add
myself
to
it
and
I'll
reach
out
to
the
CRC
folks
to
find
out
a
little
bit
more
about
what
they
did,
because
now,
there's
theoretically
and
I'll
put
this
in
ready,
because
it's
I
can
go
and
talk
to
them.
B
Theoretically,
there
is
they've
streamlined
the
process
of
doing
the
okd
CRC,
so
there
was
a
thread
about
the
work
that
they
were
doing:
geez
I'm,
gonna,
guess
like
December,
maybe
November
and
I
just
never
followed
up
with
it
blog
post
for
a
road
map.
So
this
is
going
to
involve
it's
a
good
first
issue
and
it's
going
to
involve
conversations
with
Luigi
Christian
from
the
technical
side
at
the
very
least,
and
then
also
probably
Brian
myself,
and
so
this
is.
B
This
is
Diane
and
you
Mr
branch,
do
you
should
I
add
myself
to
this
and
then
we'll
just
schedule?
Maybe
a
meeting
and
Hammer
out
what
the
roadmap
might
look
like.
B
Okay,
all
right
I'm,
gonna,
I'm
gonna,
add
to
this
ticket
all
of
the
people,
so
Brian
myself
and
then
Luigi
and
Christian.
B
B
B
B
We
do
if
you
want
to
go
ahead
and
do
that.
You
know
sometime
between
now
and
the
next
meeting.
That
would
be
good.
We.
B
Want
to
merge
it
with
those
other
ones:
yeah
yeah,
okay,
update
the
installing
openshift
on
a
single
node
instructions
in
the
end
user
Docs.
This
was
Mr
Burke
from
last
month.
E
C
E
E
So
we
need
to
write
it
about
the
self-hosting,
hosted,
assisted
installer
and
there's
been
about
four
tickets
got
in
in
the
last
month
on
the
the
issues
on
okd
about
that.
So
people
are
obviously
interested
in
it.
So,
but
that
is
a
duplicate
of
number
two.
B
So
let's
I'll
put
that
in
ready
and
then
I'll
put
those
together
merge.
Those
together
write
up
project
board
guidelines.
No
one
ever
actually
took
this.
One
I
think
we're
kind
of
defining
it
as
we
go
along
yeah,
so
I
I'll
put
it
in
backlog,
but
I
feel
like
eventually
we
will
get
to
it
because
we're
learning
now
how
to
work
with
this
and
we're
starting
to
get
the
flow,
and
it
does
help
visualize
things
I'm
glad.
B
We
went
back
to
this
missing
security
contacts
on
okd.io,
so
we
do
have
now
I
think
security
at
okd
dot
IO.
Do
we
just
wanna?
B
D
The
website
somewhere
well
I,
I,
think
kind
of
like
when
we
get
into
the
meeting
about
where's
the
direction
going,
I
think
in
the
U.S
there's
a
lot
getting
that's
going
to
hit
security
pretty
hard,
and
that
could
you
know,
put
us
in
multiple
directions,
so
I
I
think
I
think
it
kind
of
merges
a
little
bit
with
that
that
a
little
bit
you
know,
because
that
will
affect
the
you
know
the
direction
you.
B
Know
with
security
yeah
right
now
of
the
six
email
Alias
aliases,
we
do
have
security
I,
think
it's
security
at
okd,
dot,
IO.
Currently,
that
goes
to
like
the
same
group
of
people
that
receive
all
of
the
other
aliases
and
we
don't
have
like
a
defined
security
team.
So
my
sense
is
that
we
should
just
keep
that
alias
pointing
to
EV
to
that
genetic
to
the
generic
Gmail
account
and
then
try
to
build
up
a
security
Presence
by
getting
a
volunteer.
B
We
had
someone
who
was
going
to
and
then
they
sort
of
dropped
off
the
map
a
little
bit.
E
Yeah
I
mean
I
was
just
looking
at
the
comments.
It
does
say
that
we're
waiting
on
the
email
issue
to
be
solved
yeah
and
the
other
I
think.
The
other
comment
is
this-
that
the
most
likely
action
of
any
email
that
comes
in
there
is
just
pointing
it
back
at
the
appropriate
project,
because
we
actually
don't
own
the
code
for
most
of
the
stuff
I.
E
Think
it's
really
only
the
the
what
the
machine
config
operator
that's
different
for
okd,
more
or
less
everything
else
is
the
Upstream
projects
either
Fedora
core
OS
and
Center
stream,
core
Os
or
core
open
shift.
So
I
think
our
security
action
is
most
likely
to
be
Just
Bounce
it
on
to
the
Upstream
project.
B
E
So
I
think
the
action
here
is
just
out
of
this
to
the
okd.io
site.
B
E
A
B
A
B
You
know
I'll
I'll,
find
it,
but
I'm
pretty
sure
security
was
one
of
the
ones
that
we
added
it's
back
in
the
meeting
notes
too
we'll
be
able
to
find
it.
B
It's
there
were
six
aliases
that
we
had
and
then
we
can
just
add
that
one.
B
B
At
okd
all
right-
and
we
are
at
time
so
I
want
to
be
respectful
of
people's
time.
We
did
get
a
lot
of
going
through
stuff
today,
any
last
minute
comments
before
we
end
the
meeting.
B
All
right
and
I'll
reach
out
to
our
volunteer.
Thank
you
for
volunteering.
Our
new
volunteer
got
your
name
and,
let's
see
anything
else,
I
think
that's
about
it
all
right.
Folks,
I'll
make
sure
all
the
calendars
are
updated
and
whatnot
and
I'm
a
little
bit
behind
on
the
videos
of
the
meetings,
but
those
will
go
up
as
well.
I've
got
a
little
a
little
more
free
time
in
the
next
couple
of
weeks.
Coming
up
so
see
you
all
next
time.