►
From YouTube: OKD Community Development Meeting 02-07-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
Folks,
welcome
to
the
okd
Community
Development
meeting
for
February
7th
of
the
Year
2023,
and
we
have
the
agenda
before
us
here.
Take
a
look
see
if
there's
anything
you
want
to
modify.
Please
add
your
name
to
the
attendees
section
so
that
we
know
that
you
were
here
or,
if
they're,
if
you're,
not
if
you
weren't
here
during
a
particular
meeting,
then
we
would
know
to
reach
out
if
there's
something
relevant,
to
work
that
you're
doing
so.
B
Please
put
your
name
in
the
attendees
section
of
the
of
the
agenda
and
and
Brian
dropped
a
link
or
someone
dropped.
A
link
Brian
did
to
the
agenda
in
the
chat
there.
So
let's
take
a
quick
look
anything
that
folks
want
to
change.
Move
around
add
to
the
agenda.
B
All
right
anything
else,
folks
want
to
change,
move
around
all
right,
let's
jump
into
it,
Sno
installation
is
that
meant
to
be
a
sub
item.
A
Yeah
I
guess
you
can
say
a
sub
item.
Okay,
there
we
go
yeah,
so
pretty
much
I
said
I'm
gonna,
try
to
you
know,
take
all
the
pieces.
I
have
put
it
together
and
I
guess
have
a
video
for
you
since
we'll
be
presenting
to
you
so
try
to
have
a
video
of
Everything
stitched
together
and
then
you
know,
because
I
have
an
actual
presentation,
maybe
two
or
three
weeks
later
so
I'm
gonna,
pretend
I'm
presenting
in
front
of
y'all
and
so
y'all
can
critique
me.
A
So
I
can
be
a
little
bit
more
brushed
and
Polished.
You
know
for
the
audience,
and
these
are
nine
users
and
basically
maybe
trying
to
talk
your
faculty
into
using
it.
You
know
and
give
them
the
reasons
why
to
use
it
and
that'd
be
the
policy
stuff
I
got,
but
you
know
give
them
that
Hands-On
expectations
and-
and
sometimes
you
know
if
they,
if
they're
Ground,
Zero
and
kubernetes-
that
you
have
to
start
there
as
I
have
to
you
know.
Oh
yeah.
C
Are
you
working
on
this
content
in
GitHub
anyway,
because
if
you
are,
if
you
share
the
link,
then
we
can
jump
on
and
maybe
review
it
before
you
get
to
do
that?
Maybe
give
you
some
feedback,
we
can
try
it
ourselves
see
where
we
get
stuck.
Yes,.
A
All
right
so
I'll
I'll
put
everything
in
GitHub,
so
I
can
have
feedback,
and
yes,
I'll
I'll.
Do
that?
Yes,
excellent.
B
That's
good
and
tecton
installation
working
on
that
and,
as
you'll
hear
later,
I'm
working
to
get
more
information
attend
the
operator
meeting
to
get
a
little
more
information
so
that
we
can
make
the
installation
on
par
with
ocp
product
documentation.
So
I've
reached
out
to
Michael
a
couple
times
now
and
just
sent
an
email
actually
a
couple
hours
ago,
hoping
to
hear
from
him.
B
I
asked
him
if
he's
still
participating
in
the
okd
working
group
and
if
not,
if
there's
someone
else
that
we
should
be
connecting
with
and
then
also
would
it
be
helpful.
If
maybe
we
just
came
up
with
a
list
of
things
pulled
from
the
meetings
to
to
discuss
with
him
and
we
just
shot
him
an
email
with
those
things.
Would
that
help
this
process?
B
Just
because
you
know
we
we
do
want
to
get
the
product
documentation
situation,
sort
of
squared
away
and
figure
out
how
we
can
have
a
little
more
involvement
or
or
control
over
the
process,
I
guess
or
integration,
as
we
discussed
so
as
soon
as
I
hear
something
back.
I
will
share
that
with
the
group
email
hosting,
so
the
aliases
were
sent
to
osbo
like.
B
Half
ago
or
so,
and
then
they
we
got
an
email
back,
that
the
changes
were
committed
and
that
they
were
going
to
send
a
test,
email
and
I'll
check
one
more
time,
but
as
of
last
night,
we
we
hadn't
received
any
test
email
to
any
of
the
to
the
aliases
that
we
set
up.
B
I'll
check
one
more
time
since
I
happen
to
be
here.
No
so
I'll
actually
send
an
email
at
the
end
of
this
meeting
to
one
of
the
aliases
and
track
where
it
goes
and
see
sort
of
where
we're
at
with
that.
But
we're
we're.
So
close.
B
It's
only
been
a
couple
months,
but
but
we'll
get
there
for
sure
the
email
hosting
social
media
next
episode
Mastodon,
while
umiko
isn't
here
so
we'll
put
that
one
on
on
hold.
We
need
more
likes
and
retweeting
of
the
okb
tweets.
B
So
it's
just
like
me
and
like
randomly
one
or
two
other
people
can
folks
in
this
meeting.
If
you
have
a
Twitter
account
make
an
effort
to
to
forward
towards
you
know,
retweet
the
okd
tweets
or
copy
the
content
into
your
own
social
media
somehow
or
do
something
to
help
us
build
our
our
participation
in
the
social
media
grid,
because
it's
it's
pretty
light
right
now
and
we're
not
getting
a
lot
of
activity
and
the
more
visibility
we
get.
I
think
the
the
better
it'll
be
song.
Just
just
a
heads.
B
B
Nope,
okay
and
all
right
moving
right
along
here
operators,
so,
like
I,
said
I
reached
out
on
techtown,
reached
out
on
git
Ops
El
Miko
isn't
here
to
talk
about
Windows.
B
C
A
Hello,
oh
sorry,
talking
to
myself
so
I,
you
know:
I
was
up
late
last
night.
The
operators
meeting
was
like
it
10
o'clock
here
yesterday
and
I
go
so
I
said
I'm
up
I
just
went
on,
but
they
were
cool.
They
they
talked
about
their
process
and
they
gave
me
some
some
points.
So
let
me
just
go
over
that
real
quick.
A
They
gave
me
this
this
this
book
up
here
on
kubernetes
operator
framework,
they
said,
would
be
good
and
I
operated,
IO
docs
and
they
rep
are
recommended
that
I
learned,
go,
laying
and
and
and
knowledge
of
the
kubernetes
certification
would
be
great
and
when
you're
writing
you
want
to
have
the
understanding
of
one
level
down
in
the
abstraction
they
were
saying
and
and
and
he
said,
we
need
to
understand
what
we
need.
A
What
happens
when
the
upgrade
happens,
because
the
operator
is
unreachable
or
something
like
that,
and
we
need
to
think
about
the
full
life
cycle
and
then
he
he
suggested
hey
use,
operator
SDK,
it
was
laughing
and
then
they
said
they.
You
know
they
look
at
the
cute
cute.
Con
I
think
that's
supposed
to
be
kubecon.
Yeah
I
think
cubecon
Europe
is
going
on
and
so
maybe
some
stuff
up
there
and
then
they
said
something
about
a
cookbook,
Cube,
Builder
and
then
at.
A
Lastly,
he
was
he
joked
and
said:
well,
you
know
I
tried
to
chat
GPT
and
it
wasn't
too
bad.
They
wrote
my
operator.
I
was
like
oh
pretty
interesting
so
and
so
I'm
trying
to
take
this
stuff
and
put
some
of
this
in
the
glossary.
So,
oh
and
then
on
the
glossary.
I
was
thinking.
You
know
four
priorities,
priorities
for
newbies,
some
for
openshift
language,
because
that's
always
important
and
then
operators
in
the
kubernetes.
A
B
You
need
to
unmute
myself
there
kubecon
EU
is
happening
in
Amsterdam,
the
17th
through
the
21st
I,
think
it
is
of
April,
so
yeah,
and
actually
one
of
the
other
groups
I'm
affiliated
with
a
group
of
people
that
submitted
just
found
out
last
night
that
we
got
our
talk
accepted
for
how
git
Ops
changed
my
life,
so
that'll
be
kind
of
interesting
I
gotta
find
my
way
to
Amsterdam,
which
will
be
fun
so
in
terms
of
operator
stuff.
Yeah
go
ahead.
Sorry.
C
I
think
one
other
thing
that's
important
to
put
on
this,
for
our
initiative
is
actually
the
catalog
stuff
on
the
olm.
So
the
operator
lifecycle
manager
is
how
the
operators
are
surface
in
the
operator,
Hub
and
open
shift
or
okd.
So
the
olm
or
the
operator
life
cycle
manager,
lifecycle
manager,
yeah
and
that's
another
piece
of
the
operator
SDK.
C
C
So
the
olm
is
important
piece
about
wanting
to
create
an
okd
catalog,
because
what
you
have
to
do
is
you
have
to
package
your
operator
in
a
slightly
different
way,
which
includes
update
graphs
in
terms
of
one
version
goes
to
another
version.
It
includes
things
like
channels.
So
if
you
want
to
cover
channel
for
for
11
a
channel
for
412
a
channel
413,
it's
all
of
that
sort
of
stuff
and
I
I
actually
think
at
some
point.
We
actually
need
to
make
some
decisions
in
terms
of.
C
Are
we
going
to
follow
the
red
hat
catalog
of
ocp
and
make
the
okd
catalog
the
same,
follow
the
same
conventions
because
that's
a
whole
other
issue
or
a
whole
nother
level?
Once
we
look
at
the
individual
operators
like
the
techton
or
the
githubs
or
the
whatever
the
operator,
the
windows
are
and
storage
or
so
yeah
I,
I
I
think
there
does
have
to
be
some
some
work
in
there
and
I.
Don't
know
how
we
do
that
with
this
group
we
don't
really
have
a
way
of
actually
collaborating
as
a
community.
C
C
So
as
a
community,
we
haven't
really
got
an
engagement
process
and
in
terms
of
how
we,
how
we're
going
to
collaborate,
should
we
set
up
a
workshop,
a
brainstorming
session,
should
we
do
it
via
remote
access
to
a
git
repo
and
people
just
put
their
ideas
in
there,
and
we
have
a
discussion
about
it
at
this
meeting
or
so
yeah.
D
Yeah,
so
how
I
I
wanted
to
be
worthwhile
to
have
a
proof
of
concept,
hello,
world,
olm,
compliant
operator,
with
two
versions
that
you
can
try
and
install
and
update
just
to
get
all
the
pieces
like
I
I
know
that
the
last
time
I
dipped
into
this
seriously,
which
was
now
has
gotten
to
be
a
couple
of
years
ago.
D
D
C
The
world
has
moved
on
and
just
to
just
to
add
extra
confusion.
They
have
recent
released
a
new
technology
where,
instead
of
having
a
binary
format,
there's
now
a
text-based
format,
so
it's
actually
easier
to
do.
But
if
you
look
at
the
existing
operators
are
probably
still
on
the
older
technology.
So
it's
a
it's
one
of
these
Technologies,
that's
continually
involved
evolving
and
unless
you're
staying
in
touch
you
get
up
to
date
very
quickly.
C
D
Yeah
but
I
guess
there
are
two
separate
threads
in
a
way.
One
is
if
you're
writing
your
own
operator
from
scratch,
and
the
other
is,
if
you
are,
you
know,
porting
one
of
the
existing
operators,
which
I
think
is
more
Our
concern.
You.
D
They,
you
know,
like
I,
I,
think
I've
lost
track
of
the
number
of
people
that
have
independently
said
that
we
need
to
get
a
lot
of
these
Red
Hat
branded
operators
that
are
perceived
and
marketed
as
part
of
ocp,
so
that
we
can
deploy
them
on
okd.
C
Yeah
I
mean
I
I,
certainly
believe.
That's
the
way
that
we
should
go
I,
don't
think.
We've
got
enough
people
in
our
community
to
actually
go
in
great
operators
and
maintain
them,
and
red
hat
is
already
doing
that
in
open
source
in
public
get
repose.
So
where
possible,
I
mean
one
of
the
challenges
is
finding
them.
They
seem
to
be
spread
over
all
sorts
of
multiple
get
her
bogs,
they're,
not
all
in
one
org,
but
I
I.
C
Think
what
we
want
to
do
is
you
want
to
create
a
series
of
either
pipelines
or
we
could
use
get
Ops,
but
we
want
a
series
of
automation
which
just
takes
their
repos,
builds
the
operator
bundle
and
then
that
kicks
off
another
pipeline
which
goes
and
packages
them
in
a
catalog
and
that
we
can
then
test
and
eventually
release
into
the
keto
IO
in
the
okd
account
yeah
and.
B
That
would
be
awesome.
I
I
would
think
that
the
tech
time
pipelines
one
is
going
to
be
our
easiest,
because
really
it's
the
operator
plus
an
add-on,
conf
custom
and
then
the
tasks
which
are
in
another
repo
and
just
pulling
those
in
now.
B
That's
a
my
perspective,
after
not
really
talking
to
folks
yet
on
the
tech
time
side
of
things.
But
to
me
that
seems
like
one
of
our
easiest
candidates
right
is
to
create
a
pipeline
that
literally
just
pulls
the
operator
repo,
pulls
the
configuration
and
pulls
the
the
other
scripts
tasks
cluster
tests
and
then
has
that
ready
to
go,
and
so
that
might
be
our
first
test
case
of
like
maintaining
something
ourselves
right
and
but
I
do
like
Bruce
I.
B
Do
like
your
idea
of
like
a
hello,
hello,
world,
the
reason
and
and
Dwayne
also
for
the
idea
of
adding
this
documentation
that
you
link
to
is
we
sort
of
have
to
understand
operators
to
be
able
to
support
them
or
even
suggest
to
community
members?
B
And
we
talked
about
this
before
like
last
week
last
meeting
right
is:
we
have
to
be
sort
of
informed
about
them
to
be
able
to
even
make
suggestions
to
the
maintainers
about
stuff
that
we
want
and
that
we
need
so
does
it
make
sense
to
set
up
a
meeting
with
Vadim,
since
Vadim
has
voiced
an
interest
in
on
his
own
read
invigorating
the
initiative
for
a
for
an
okd
specific
catalog
should
I
try
to
set
up
a
meeting
with
him
that
for
us,
like,
maybe
an
off
off
meeting
time,
because
he
has
meetings
right
now
during
this
time,
but
maybe
at
some
other
time,
and
then
we
can
all
get
together
and
sort
of
hash
this
out
and
try
to
move
forward
on
it
because
we're
we're.
B
D
Jamie,
if
you
want
anybody
to
help
work
with
you
on
the
Techno
thing,
I'm
happy
okay,
to
do
that,
I'm
sort
of
the
closest
time
zone,
I!
Think
of
the
of
all
of
us,
I.
B
Is
there
anything
else
about
operators,
I'll
set
up
a
meeting
or
I'll
I'll
ping
Vadim
about
setting
up
a
meeting
and
then
I'll
send
out
a
calendar,
invite
on
the
the
Google
Groups
list
for
folks
to
sign
on,
and
we
can
try
to
get
as
many
people
as
possible
and
we'll
record
it
as
well.
Does
that
sound
good
awesome?
B
One
other
thing
that
I
did
Ping
Vadim
about
just
recently
and
I'm
waiting
to
hear
back
is
for
Community
to
do
more
support
of
okd
in
the
discussion
and
issues,
and
so
I've
asked
Vadim
if
he'd
be
willing
to
do
us,
a
a
log
bundle
dissection.
B
You
know
session
where
he
just
says:
okay,
this
is
where
I
start
you
know
to.
If,
when
someone
describes
an
issue,
that's
networking
this
is
where
I
start.
When
someone
describes
an
issue
with
you
know,
llm
or
with
or
config
manager,
you
know
whatever
it
is
machine
config
manager
like.
Where
does
he
start
and
how
does
what
is
his
thinking
a
little
bit
because
clearly
he's
one
of
the
only
people
contributing
to
problem
solving
at
a
technical
level
in
the
issues
and
the
discussions?
B
We
need
to
not
have
that
single
point
of
failure
and
if
we
can
distribute
that
knowledge
enough
of
really
understanding
how
to
dissect
and
understand
the
log
bundles,
we
can
give
other
people
an
in
to
start
participating
in
the
community
because
we
can
be
like
Well
here.
Here's
how
you
can
start
helping
help
triage
some
of
these
things
and
actually
learn
about
okd
in
the
process.
B
C
B
C
B
B
They
messaged
me
on
slack
privately
about
they
wanted
to
get
involved
in
okd,
but
they
didn't
really
know
how
and
where,
because
things
are
so
sort
of
isolated
in
the
Red,
Hat,
World
and
so
I
think
we
need
to
update
the
how
to
contribute
page
and
link
to
the
the
the
stuff
for
Centos
stream
that
Initiative
for
building,
because
people
can
actually
look
at
the
repos
and
and
see
that
happening.
So
that's
something
that
people
could
actually
contribute
or
at
least
see
the
you
know
how
the
vegan
sausage
gets
made.
So,
okay.
C
B
Right
exactly
and
actually
I
use
that
blog
post
in
a
in
the
slack
Channel.
Recently
someone
asked
a
question:
they
didn't
quite
understand
the
the
juxtaposition
between
the
different
flavors
and
stuff
and
I
linked
them
to
the
blog
post,
and
they
were
very
appreciative.
So
that's
that
was
a
good
thing.
C
I
guess
the
only
other
thing
that's
just
come
to
mind
and
I
know
Anika's.
Not
here
is:
do
we
want
to
start
looking
or
does
anybody
have
any
ideas
about
automation
because
we
talked
we
started
talking
about
automating.
So
when
we
get
to
news,
we
can
put
it
on
the
website.
It
can
go
to
Twitter,
it
can
go
to
Mastodon.
It
can
go
into
this,
the
slack
Channel
or
the
Google
group,
so
we're
not
helping
to
to
post
five
different,
separate
things
right.
C
So
I
don't
know
whether
anyone
has
any
views
on
how
that
would
work
or
any
technology
that
they
they
use
or
they
played
with.
That
makes
that
a
lot
easier,
I
know
a
lot
of
like
gaming.
Streamers.
Have
this
all
set
up,
so
they've
got
sort
of
multiple
streams
coming
in
and
it
all
gets.
Aggregated
I'd
never
do
anything
like
that,
but
that
is
something
that
we're
going
to
need
fairly
quickly.
If
we
get
this
Mastodon
stop
working
yeah.
B
A
I
don't
know,
maybe
I
can
look
into
ansible
and
see
why
I
asked
who
could
do?
Maybe
maybe
something
simple.
B
B
All
right,
well,
I,
think
we're
good,
then
for
now
Let's
go
forth.
I
will
try
to
get
those
two.
Some
dates
set
up
so
well.
Do
folks
have
a
particular
calendaring
survey
solution
that
they
like
for
like
finding
dates.
Agreeing
upon
dates.
Is
there
anyone
partial
to
there's
like
20
million
different
ones,.
D
C
I,
don't
I
guess
my
only
comment
would
be.
It
would
be
good.
It
was
morning
us
which
is
about
midday
Europe
and
evening
as
you
get
into
sort
of
Middle,
East
Asia,
sorry
Australia,
New
Zealand,
but
we
don't
have
a
and
I
think
the
most
of
our
community
attendees
are
between
America
and
and
the
Middle
East
yeah.