►
From YouTube: OKD Working Group Meeting 01-17-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
Good
catch
there
Jamie.
So
just
just
to
restate
my
question
here
since
the
recording
started,
we're
talking
about
maintaining
previous
versions
of
okd
and
kind
of
the
community's
response
to
that
and
I
just
had
a
a
question
or
I
guess
maybe
a
point
about
you
know.
Even
if
we're
able
to
have
the
knowledge
to
support
previous
versions,
our
ability
to
take
Community
input
back
to
those
versions
might
be
very
limited.
B
I
know:
ocp,
the
product
has
its
own
rules
about
like
how
back
ports
will
be
accepted
and
what
types
of
content
is
acceptable
for
backboards
and
then
more
to
the
point
you
know,
creating
a
bug
against
the
current
version
is
something
I'm,
I
think
we're
just
kind
of
getting
into
as
a
community,
so
this
kind
of
adds
an
extra
layer
to
it.
So
I
think.
B
If
we
get
into
a
discussion
about
like
how
would
we
support
previous
versions,
you
know
I
think
that
necessarily
we
we
should
talk
about
this
community's
ability
to
actually,
like
you
know,
fix
things
or
or
make
changes
in
the
Upstream
as
it
looks
right
now.
You
know
that
that
was
my
only
point.
I
guess
I.
C
Think
that's
a
good
point,
I
think
really.
The
the
the
the
community
has
spoken
in
terms
of
the
number
of
volunteers
that
we
have
at
this
time
and
and
the
infrastructure
right
so
I
think
we're
sort
of
we're
at
a
point
where
we
can't
do
anything
right
now.
Even
if
we
wanted
to
sort
sort
of
that
answers
that
question
I,
think
I
don't
know
what
do
other
folks
think.
D
Yeah
I'm
in
agreement,
we
don't
have
too
many
heads
on
Deck.
E
F
Yeah
I
think
that
for
that
to
change,
we
sort
of
need
to
get
it
to
where
the
community
can
fairly
easily
build
the
various
releases.
A
C
Well,
that's
not
to
say
that
it
isn't
a
goal
all
right
like
obviously
we
want
to.
We
want
to
continue
to
grow
the
project
and,
and
have
that
be
the
reality
moving
forward
is
that
we
can
get
enough
Community
Support
to
patch
things
in
previous
versions.
It's
just
not
there
right
now,
all
right
any
other,
any
other
thoughts
on
on
this
aspect.
So
what
are
we
saying?
C
E
C
G
I
just
didn't
want
to
do
a
big
promotion.
Everybody
try
and
give
us
your
feedback
on
something
that
we
didn't
really
want.
People
doing
that
I,
don't
think
it
should
stop
the
beliefs
I,
think
it
just
stopped
the
blog
post.
Basically,
that's
my
opinion,
but
it
it
and
I
just
wanted
a
ping,
which
is
why
I
showed
up
today.
C
Okay,
well,
let's
do
this
Luigi.
Can
you
find
the
answer
to
that
question
about
upgradability
and
then
post
it
in
the
Google
discussion
group
and
then
we'll
decide
where
to
go
from
there?
Based
on
that
and-
and
you
know,
I
think-
that's
a
pivotal
question-
you.
D
Know
at
this
point
absolutely
no,
we
will
do
so
and
then
I
think.
The
other
thing
is
if
we
go
forward
with
with
the
412
OK
d412,
stable
and
and
actually
it
wasn't,
the
413
sort
of
Dev
cut
for
because
this
is
what
the
the
openshift
team
really
wanted
was
that
that
we,
on
a
sprinting
basis,
have
a
release
of
the
the
div
every
three
weeks,
basically
we're
doing
our
sprints
and
they
were
really
Keen
to
get
feedback
from
you
guys.
D
So
I
think
the
whole
issue
is
about
signals
for
ocp
at
the
end
of
the
day.
So
it's
a
very
red
hat
selfish
thing,
but
at
the
same
time
it
will
help
help
them
and
also
help
the
community
at
large.
Really.
So,
if,
if
there's
anything
that
goes
wrong,
we'd
really
like
feedback,
and
so
what
we'll
do
as
a
team,
because
we
we've
been
sort
of
asked
to
handle
the
release
process
is
gather.
A
D
Feedback
and
feed
it
back
to
the
to
the
ocp
sorry,
the
the
larger
openshift
Community
within
Reddit,
so
it
really
helps
the
feedback
is
the
big
thing,
and
so
we
I
really
would
like
to
to
encourage
you
guys
to
give
us
feedback,
no
matter
how
bad,
even
out,
if
it's
good
that
that
feedback
would
be
really
appreciated.
So
they
just
asked
me
to
bring
it
up.
So
yes,
what.
C
Excellent
excellent:
that's
a
good
point
that
getting
that
feedback
Upstream
as
it
were,
will
help
the
community
and
help
red
and
hat
who
you
know,
Butters
our
bread,
so
to
speak
in
a
lot
of
ways
all
right.
Well,
then,
let's
get
the
research
information
and
then
we'll
move
forward
from
that.
C
We
do
not
have
well.
Actually,
let's
so
S
cost
updates
anything
specific
to
s-cos.
D
No,
we
don't
have
Timothy
here.
You
would
have
some
updates
yeah.
C
Yeah
I
will
say
this
as
I
noticed
two
people
asking
in
one
person
in
the
discussion
section
of
the
repo
and
one
person
in
slack
asking
about
using
it
separately,
just
as
it
as
a
separate
OS
to
play
around
with
so
Glenn
was
at
Macy,
and
then
someone
else
asked
on
the
get
lab
discussions
about
about
their
GitHub
discussions
about
that.
So
that
might
be
something
that
is
it
in
our
documentation
anywhere.
C
Yet
is
it
in
that
that
sort
of
write-up
that
was
done
a
couple
months
ago
by
Christian
at
all
about
this
project?
Was
there
anything
mentioned
in
there
about
it
being
Standalone
usable
as
a
standalone,
Os
or
not?
I
know
that
the
in
the
meetings
there
was
discussion
about
it
really
wouldn't
be.
There
wouldn't
be
a
focus
on
that,
but
it
might
be
good
if
we
answer
that
question
to
folks,
because
it
is
starting
to
come
from
the
community,
people
want
to
play
with
it
just
like
they
play
with
f
cost,
so
yeah.
G
I
think
we
we
talked
about
this
month
months
and
months
ago,
when
we
first
started
talking
about
svas
it
and
I.
Think
we
discussed
creating
some
in
the
FAQ
information
about
that
it
is,
you
can
use
it
Standalone
and
maybe
being
able
to
create
some.
You
know
a
link
for
people
to
download
it
separately
on
somewhere
on
okd.io,
which
I
think
would
be
very
nice
for
the
Centos
stream
Community
and
the
team
to
get
feedback
on
that
I'm,
not
sure
what
the
product
teams
all
think
about
that.
G
But
I
think
it's
a
really
good
idea
to
get
that
feedback
and
get
it
more
stable
and
strengthened
and
maybe
get
a
few
more
eyeballs
and
participants
in
the
sentos-free
cloud
Sig
as
well,
because
that's
mostly
red
Hatters
anyways,
so
I
would
be
a
strong
proponent
of
creating
even
just
a
small
landing
page
somewhere
the
FAQ
and
something
that
links.
A
H
G
That's
a
big
chunk
of
work,
but
with
the
other
thing
I
don't
know
if
Luigi
mentioned
it
in
the
last
call,
but
flat
car
is
going
for
incubation
in
the
cncf
black
car
is
another
container
of
Linux,
so
I'm
not
sure
how
I've
been
trying
to
look
for
stats
on
how
widely
adopted
it
is.
G
But
you
know:
there's
there's
other
alternatives
to
have
cost
s
costs
and
our
costs,
and
so
it
would
be
interesting
to
see
what
the
adoption
is
for
a
flat
car
versus
all
of
the
all
of
the
asterisks
causes
that
we
have
and
I've
been
looking
for.
A
way
to
get
those
numbers,
but
I
have
I
haven't
been
able
to
find
one.
G
So
if
anybody
has
any
clues
about
adoption
of
the
other
container
limits
or
saw
any
white
papers
Float
by
our
blog
posts
about
people's
adoption,
post,
I,
I'd
love
to
know
a
breakdown
of
the
the
different
container
Linux
is
out
there
and
I
haven't
seen
anybody
do
anything
that
I
would
call
credible
other
than
like
surveys
of
28
people
who
use
that
car.
That's
the
only
thing
I
could
find
the
other
day.
So
I
know
more
than
28
people
use
flat
car,
so
I
just
can't
find
any
numbers.
C
All
right
to
your
first
point,
I
will
bring
it
to
the
Community
Development
Group
meeting
next
week
for
someone
to
take
the
task
of
writing
a
landing
page
and,
at
the
very
least,
an
FAQ,
with
a
link
to
download
the
S
cause
and
then
we'll
we'll
go
from
there,
maybe
start
with
the
repo
FAQ,
the
FAQ
item,
linking
to
maybe
something
in
the
repo.
That's
just
a
single
page
with
some
info
and
whatnot
and
any
other
thoughts
on
that
on
S
cost
in
general.
D
So
so
Jamie,
let
me
also
follow
up
on
that.
If
you
could
just
keep
it
as
an
action
item
for
me,
I
will
I
will
get
to
chat
to
Timothy
and
the
gods
about
if
S
cost
can
be
used.
Standalone,
sir
okay,.
C
Let's
see
all
right,
I'll
create
an
item
for
u
in
the
working
group,
repo
I'll
create
a
or
sorry
in
the
in
the
yeah.
C
Mob
doohickey,
what
should
I
call
it
yeah
all
right,
all
right
anything
else
on
this
cost
before
we
move
on
fcos
updates,
it
doesn't
look
like
anyone
is
here
and
let
me
do
a
quick
scan
to
see.
G
What,
while
you're
doing
that
is
the
F
cost
release
currently
at
the
same
release
number
of
ocp
as
S
cost,
so
are
they
matching
right
now.
G
The
F
cross
and
s-cos
are
they
in
sync,
in
terms
of
release
numbers
in.
D
We
had
a
chat
about
this
cost
is
just
there's
a
there's,
no
versioning,
they
have
a
master,
a
master
branch
and,
and
and
that's
it
Timothy
wasn't
happy
about
having
versioning.
So
by
the
virtue
of
the
fact
that
escort
doesn't
have
versioning
I
think
might
mean
it
doesn't.
Have
the
the.
C
All
right,
Timothy
can't
join
I,
asked
him
if
there's
anything
worth
mentioning
and
for
f
costs.
Let's
go
ahead
and
that's
I
think.
Actually,
let
me
back
up
a
little
bit.
I
feel
like
that.
Lack
of
versioning
is
probably
something
that
we're
going
to
get
a
lot
of
questions
on.
So
let's
create
a
a
task
item
for
that
as
well
for
adding
that
to
the
FAQ,
because
invariably
we
will
get
asked
what
version
of
fedoras
is
based
on
what
version
goes
with
this
okd.
C
Etc,
so
let's,
let's
create
a
task
for
that
as
well.
All
right,
let's,
okay,
so
dusty
and
Timothy
do
not
have
anything
hold
on.
C
Okay,
moving
on
Community,
Development
updates,
Brian
is
out
this
meeting
and
possibly
the
next
meeting
as
well.
Community
updates.
We
do
have
the
email
situation
resolved
and,
and
we
just
need
to
send
in
the
aliases
that
we
want,
and
so
the
five
aliases
that
the
community
came
up
with.
That's
like
Communications
contact
and
there's
there's
basically
five
aliases.
C
Other
things
that
we
talked
about
are
we
spent
a
lot
of
time
talking
about
getting
Clarity
on
operators
and
getting
Clarity
on
arm
support,
both
of
which
we
will
talk
about
later
in
this
meeting
and
I'm
trying
to
think
if
there's
anything
that
I'm
missing
here,
let
me
take
a
quick
look:
I
forgot
that
Brian
was
not
going
to
be
here
today.
C
Let's
see
I'm
still
working
on
tecton
installation
document,
Charo
had
one
from
a
couple
years
ago,
so
I'm
sort
of
looking
at
what
he
has
and
comparing
with
what
I
have
social
media.
The
general
consensus
is
that
we're
going
to
try
Mastodon
and
El
Miko
is
going
to
has
created
a
document
that
is
very
helpful,
I'll
link
to
it
here,
just
so
that
folks,
have
it
I'll
put
it
in
the
in
the
chat.
C
This
was
like
super
super
helpful
and
this
sort
of
sets
the
stage
for
us
to
at
least
try
Mastodon,
so
we're
going
to
give
it
a
shot
and
just
see
how
things
go
in
terms
of
communicating
out.
C
The
phenomenon
is
that
a
lot
of
people
are
moving
from
Twitter
to
Mastodon
or
at
least
doing
both
anecdotal
evidence
that
I've
read
from
people
who
are
in
both
is
that
there's
more
engagement
on
Mastodon,
because
it's
more
sort
of
focused
communities,
and
so
some
of
the
servers
that
we
would
be
on
actually
and
we
go.
Why
don't
you
go
ahead
and
just
summarize
what
what
you
said
at
the
at
the
community
development
meeting.
B
Yeah
sure,
if
I
can
remember
it
all,
you
know
like
the
for
I
guess,
folks,
watching
at
home
and
whatnot.
You
know
the
main.
The
main
difference
between
Twitter
and
Mastodon
is
that
Twitter
is
a
centralized
service,
whereas
Mastodon
is
a
decentralized
service.
So
you
know
in
the
case
of
Mastodon
what
Jamie's
talking
about
with
the
different
servers,
which
are
you
know,
pretty
commonly
called
instances
in
the
community
each
instance
is
controlled
by
a
different
group.
B
Maybe
has
different
codes
of
contact
to
different
rules,
and
so
you
know
we
could
align
ourselves
with
kind
of
an
open
source
instance,
something
that's
kind
of
dedicated
to
sharing
news
about
technology
and
open
source
topics
and
whatnot,
and
that
might
put
us
in
kind
of
the
best
pool,
initially
at
least
for
where
our
messages
will
hit
kind
of
like
people
who'd
be
interested
in
those
topics
and
then
likewise
instances
Federate
with
each
other.
B
So
they
they'll
have
you
know
other
instances
they
share
messages
with,
and
so
what
we
see
almost
like
the
web
rings
of
old.
For
anyone
who,
who
remembers
those
days,
you
know
open
source
instances
are
usually
you
know
there
or
technology
instances
are
interested
in
Sharing
news
about
these
things
with
each
other.
So
hopefully
we
could
agree
as
a
community
on
an
instance
that
looks
suitable
to
us,
and
you
know
one
of
them
I
identified
is
where,
like
the
Fedora
project
is
and
and
Arch
Linux
and
whatnot.
G
Yeah
I'm
I'm,
totally
plus
one
to
to
doing
it
in
both
places.
Mike,
if
you
can
think
about
which
server
you'd
like
to
be
on
there's
a
couple
of
them.
Red
Hat
has
a
couple
of
other
projects
that
are
on
I,
think
Boston,
but
I
I'll
have
to
take
take
a
peek
and
we
probably
should
be
on
the
same
server
rather
than
one
of
my
more
esoterically
fun
ones
like
pachyderms
IO,
but
that
would
I
would
love
it
if
you
guys
could
set
up.
B
Yeah,
so
in
that
document
that
Jamie
shared
and
and
thank
you,
Diane
and
jack
for
adding
your
handles
here,
I'm
adding
you
to
my
follow
list
now
that
that
link
that
Jamie
shared
in
the
in
the
chat
here
and
I
guess
we
could
put
it
in
the
notes
too.
I
do
have
a
couple
recommendations
at
the
end
for
top
servers,
we
should
probably
look
at
and
fostudon
was
one
of
the
ones
that
I
agree
with
you.
Diane
I
think
it's
probably
a
good
place
for
us
to
consider.
B
Hackaderm
is
another
one
that
I
think
is
good
to
consider
as
well,
but
ultimately,
I
think
the
community
should
probably
decide,
and
we
should
agree
as
a
community
where
we
want
to
be.
C
Volunteering
to
you,
know,
help
out
and
to
sort
of
lead
the
way
technically
he
did
a
great
amount
of
foundational
work
very
much
appreciate
that,
but
obviously
he
has
a
lot
of
other
responsibilities
and
is
doing
other
stuff
for
the
community.
So
we
want
to
make
sure
that
we
share
the
love
as
it
were
in
terms
of
getting
that
done.
C
Excellent,
let's
see,
are
we
ready
to
talk
about
operators
in
arm
or
do
we
want
to
wait
still
Luigi
I.
C
Well,
basically,
what
it
is
is
if
the
discussion
came
out
of
the
community
meeting
the
community
development
meeting,
that,
like
we
sort
of
want
to
fish
or
cup
bait
on
the
operator
situation
like
if
there's
going
to
be
an
operator
catalog
supported
by
Red
Hat
great.
Let's
move
forward
with
that.
If
there
isn't,
then
the
community
might
want
to
just
tackle
that
ourselves
or
do
something
because
there's
there's
that
would
be
our
Edge
number
one
as
as
a
project
is
having
operators
and
and
maintaining
our
own
operators
and
whatnot
and
and
having
stuff.
C
That's
currently
missing,
but
is
an
ocp
right,
so
that's
sort
of
the
edge
that
we
would
have
in
in
getting
folks
over
to
okd.
The
other
aspect
of
it
is
that
we've
kind
of
been
spinning
our
gears
and
waiting
on
this
for
a
long
time
and
we're
not
getting
clear
communication
from
Red
Hat
on
like
is
this
moving
forward
or
not
in
terms
of
the
of
the
operator
catalog?
And
it's
not
to
condemn
anyone
or
or
anything
like
that,
a
lot
of
there's
a
lot
of
competing
priorities?
It's
just
at
some
point.
C
D
So
I
think
to
your
point
then
Jamie
do
it's.
D
Consensus
from
from
the
community
do
we
continue
on
a
path
where
we
maintain
our
own
Community
version
of
a
catalog
for
okd,
or
do
we
follow
what
redhead's
doing
type
of
thing
I
mean
I
I,
think
that
was
one
of
the
points
that
Brian
wanted
for
us
to
mainly
speak
about
and
sort
of
get
some
consensus.
C
Well,
there
was
a
there
was
an
internal
project
to
provide
a
okd
specific
catalog
operator
catalog,
but
it
sort
of
it
was
brought
up
by
Christian
like
last
winter.
I
think
it
was
like,
like
winter
2021
heading
into
2022,
and
then
it
just
never
picked
up
steam,
and
so
that's
why
I
was
kind
of
hoping
that
Christian
would
be
here
to
let
it
to
let
us
know,
sort
of
what
that
status
is
of
that
internal
effort.
G
C
Well,
we're
talking
about
making
sure
that
we
have
builds
of
The
Operators,
that
we
want
to
include,
and
maybe
following
a
a
fedora-esque
maintainer
system
of
okay.
These
are
the
maintainers
for
this
particular
operator,
just
so
that
it's
continuously
updated.
That's
you
know
it's
somewhat
and
then
in
having
a
package
or
or
I
should
say
a
package,
but
a
a
process
in
the
build
of
inserting
that
catalog
into
the
cluster
configuration
foreign.
C
G
Think
what
we
could
ask
Christian
to
do
to
see
to
see
what,
if
any,
work,
that
we
could
leverage
to
do
it
ourselves
like
if
there
was
somebody
who
had
an
internal
project
that
has
left
the
house
or
has
moved
on
to
something
else,
but
there's
some
code
base
or
something
that
we
could
use
as
a
starting
point.
G
But
there's
been
a
lot
of
turnover
in
the
operator
team
itself,
so
I'm,
not
sure
I.
Think
it's
a
question
like
you
say
for
Christians
if
he
could
do
a
tiny
bit
of
research
on
what
what
was
actually
done.
If
anything,
you
know,
depending
on
on
red
hat-
and
this
is
said
that
still
as
a
red
Hatter
has
not
really
proven
successful
for
us.
C
F
Because
there's
there
are
several
parts,
some
of
which
are
fairly
nominally
straightforward.
One
is
that
you
basically
need
to
Ripple
to
host
whatever
operators
you're
doing
and
without
that
you
have
nowhere
to
publish
them.
F
Given
that
you
have
a
repo
to
publish
The
Operators,
then
it
depends
on
the
operator,
and
some
of
them
probably
would
take
a
lot
of
discussion
on
the
best
way
to
proceed
so
like
with
the
tecton
operator,
which
is
one
of
the
Fairly
fundamental
ones,
there's
a
lot
of
different
ways
to
proceed,
and
if
you
want
to
mirror
what
what
ocp
is
doing
with
the
I
guess
with
the
well,
what
do
you
do
about?
F
The
Branding
is
an
issue,
but
resolving
that
detect
on
people
do
have
an
ocp
specific,
build
that
doesn't
seem
to
get
published
anywhere,
and
you
know,
but
many
of
the
essential
operators
are
quite
big.
You
know
the
you
know
like
for
the
one
for
getting
serverless
istio,
all
of
these
things
and
they're
also
quite
invasive,
and
can
really
take
your
system
down.
F
If
you
don't,
have
it
right,
having
taken
my
system
down
a
couple
of
times
so
I
I
think
that
I
think
that
overall,
to
get
to
where
ocp
is,
would
be
a
big
effort.
But
to
start
would
not
be
such
a
big
effort
like
you
can
start
with
a
tiny
operator
get
it
published,
get
it
so
that
it's
consistent
with
the
operator
manager-
and
you
know
you
can
add
it
in
as
a
testing
and
so
on,
and
so
on.
So
I
think
that's
a
good
place
to
start.
D
Yeah
and
I
think
to
that
obviously
having
having
a
common
Reaper
for
the
community,
then
we
would
need
a
set
of
Gatekeepers
because
you
could
get
some
Rogue
person
building
their
malicious
operator
that
would
destroy
or
gather
information
for
himself
or
something.
So
there
has
to
be
some
form
of
gatekeeping
and
some
form
of
protecting
that
we
can't
just
accept
any
operator
that
gets
pushed
into
the
into
the
community
operator
that
type
of
thing
and
and
then
obviously
the
standards
are
adhered
to.
D
F
Right
well,
a
lot
of
that
is
stuff.
That
Brian
was
very
cognitive,
cognizant
and
passionate
about
that
needs
to
be
discussed
sort
of
in
the
community
Forum,
but
there
are
also
technical
issues
on
how
you're
making
it
happen,
which
is
basically
what
I
was
talking
about
here.
F
So
I
I
completely
agree
with
you
Luigi
that
these
other
things
are
critical
and
we
have
a
place
to
to
try
and
discuss
that,
and
you
know
I
think
the
community
side
of
the
house
is
is
moving
along
that
direction.
A
H
Other
thoughts,
yes,
if
if
you
could
take
the
operator
situation
and
put
it
down
as
a
grant,
what
would
it
look
like
what
would
be
the
cost
of
it?
What
would
be
the
infrastructure
needed
you
know,
open
source
is
a
big
thing
to
contribute
to
the
Workforce
and
could
be
a
great
skill
to
pass
on.
H
So
so
you
know
if
I
could
see
it
in
those
terms
and
perhaps
I
could
or
or
just
find
a
funding
agency
I
think
it
may
fit
into
Workforce
Development
things
pretty
easily,
but
I
I
got
to
go
searching
for
a
grant.
That
would
you
know
that
would
mirror
the
language
that
you
would
want,
because
the
Innovation,
the
automation,
you
know,
I,
think
that's
definitely
Workforce.
C
Well,
I
think
I,
think
that's
a
great
point
and,
and
the
foundation
of
your
point
is
quantifying
the
effort
to
do
this
right
and
I.
Think
that
that's
something
that
we're
going
to
want
to
do
at
some
point
is
maybe
talk
to
folks
that
are
involved
in
building
operators
and
say:
okay,
how
long
does
it
really-
or
you
know,
look
at
release
stuff
in
repo,
but
it's
probably
best
to
actually
talk
to
people
who
are
maintaining
operators
and
be
like?
How
long
does
this
really
take
you?
What
kind
of
pitfalls
do
you
run
into?
C
How
long
do
you
does
it
really
take
for
you
to
get
this
done
and
make
sure
that
it's
in
the
catalog,
without
any
issues?
How
many
bug
reports
do
you
get
from
people
using
it
on
ocp
or
in
okd
things
like
that,
I
think
it
we
would
benefit
from
quantifying
that
it's
a
lot
of
work
I'd
be
happy
to
participate
in
that
effort.
D
Involved
in
building
three
operators
so
that
day
day,
one
operator,
so
like
external
DNS,
we
did
the
node
observability
operator
that
is
able
to
deploy
ABP
if
scripts
on
on
nodes
and
we-
and
we
did
another
one
for
I-
mentioned
that
obserability,
yes,
and
and
basically
so
so
from
scratch,
doing
those
operators
and
then
building
them,
fixing
them
and
maintaining
them,
putting
them
into
building
the
indexes
building
the
catalog,
putting
them
into
the
catalog
and
making
sure
that
they
are
in
the
red
hat
Market.
D
That
is
a
lot
of
work.
It's
I
mean
we're
talking
six
months
worth
of
work
for
one
operator
type
of
thing.
So
yeah,
it's
not
easy.
Let's
just
say
it's
not
easy,
but
if
we,
if
we
can
I
mean
if
we
get
a
that,
if,
if
like
Dwayne
is
saying,
we
get
a
grant
and
there
is
service
service
available
for
a
repo
or
whatever
and
people
helping
to
to
handle
the
catalogs,
then
I
think
we'll
be
in
good
shape.
C
And
I
think
you're
right,
I.
Think
you're
right
Diane
just
brought
up
something
interesting
in
chat
Dan.
Do
you
want
to
sort
of
just
verbalize
what
you
what
you
said
in
chat
well,.
G
First
of
all,
I
think
that
the
techton
operator
is
the
one
that
we're
all
interested
in
at
the
moment
getting
researched
and
documented
how
to
build.
That
and
I
certainly
am
so
if
we
took
one
project
one
and
narrowed
in
on
that
figured
out
what
it
would
take
to
build
that
ourselves.
G
What
the
effort
is
currently
to
build.
It
do
some
documentation
on
it
and
document
what
you
find
but
I
think
like
for
me,
I'm
I'm,
always
trying
to
how
do
we
drive
more
traffic
and
eyeballs
to
okd
dot
IO
so
get
time
still
then
bugging
Christian
to
get
the
tecton
pipelines
up
on
techcon,
HUB
or
now
artifact
Hub,
because
I
think
they're
retiring
tecton,
Hub
soon
so
I'm.
You
know
I'm
curious
if
we
could
use
that
one.
G
Maybe
Jamie
and
Benjamin
is
the
first
research
project
to
document
what
it
takes
to
do
that
and
maybe
do
that,
one
all
the
way
through
one's
being
documented
and
if
it
turns
out
to
be
hugely
onerous,
then
maybe
not
maybe
not,
but
that
would
be
where
I
would
spend
my
energy.
C
I
think
you're
right,
I've
started
in
that
path.
Actually
so
I'm
I
joined
the
techton
working
groups
and
so
I
got
20
million
calendar
invites
because
they
have
so
many
subgroups
and
so
Thursday
is
their
operator
subgroup
meeting
and
I'm
going
to
attend
that
and
see.
If
I
can
Garner
some
information
Dwayne,
if
you
want
you
and
I,
can
synchronize
offline
to
share
information
and
start
looking
at
some
of
these
operators.
El
Miko
suggested
the
windows
operator
Team
reaching
out
to
them.
Are
you
willing
to
do
that?
Buddy?
B
I
mean
I
work
pretty
closely
with
some
of
them.
I
just
know
that,
like
the
Windows,
like
the
windows
container
driver,
whatever
it's
called
whatever,
whatever
it
is,
that
allows
you
to
run
Windows
nodes
or
whatever
we
and
we
don't
install
that
as
part
of
the
core
ocp
package.
It's
actually
installed
through
the
operator
Hub,
so
I
know
like
they're
very
well
versed
in
that
you
know
how
that
packaging
goes
so
like
I
could
reach
out
to
arvind
or
one
of
the
other.
B
You
know
project
leads
there
and
see
if
maybe
they
could
just
come
to
one
of
our
community
or
not.
Community.
Come
to
this
meeting
yeah
and
just
yeah
answer
like
do
a
q,
a
for
us
just
to
kind
of
give
us
an
impression
of
what
what
the
entire
cycle
looks
like
or
something
but
yeah
I'll
reach
out
and
see
if
they
have
someone
who
can
come
join
us
all.
C
Right
and
we'll
we'll
set
up
some
tasks
in
the
in
the
board
for
all
of
these,
and
then
folks
can
report
back
to
the
respective
issues
that
get
generated.
Anything.
D
Got
about
yeah
I
just
wanted
to
say
not
to
complicate
things
too
much,
but
I
think
another
one
that
goes
hand
in
hand
with
tecton
is
the
August
CD.
So
if
we
could,
if
we
could
also
get
that
one
on
board,
I
think
yeah
I'll
go
CD
with
techton
you'd.
Have
you
have
a
lot
of
people
be
interested,
so
I
mean
maybe
there's
we
could
we
could
do
that
simultaneously,
rather
in
parallel
and
see
how
far
we
can
get
I
don't
know
as
a
suggestion.
No.
E
I
think
a
lot
of
people
would
also
be
interested
in
the
in
the
logging
operators,
since
it
used
to
be
part
of
okd,
but
then
with
I
think
four
eight
it
was
moved
out
yeah
so
that
I
think
that
would
be
a
good
candidate
that
a
lot
of
people
might
be
interested
in
and
I
can
contribute
some
resources
to
that.
C
All
right,
let's
do
that
I'll
I'll
reach
out
for
the
for
the
get
Ops
one
I'll
reach
out
for
that
and
then
I'll
attend
the
tecton
meeting
on
Thursday
El
Miko
you'll.
Do
windows
Jack
reach
out
for
to
find
out
about
logging
operator.
That
gives
us
four
right.
Let's.
C
Talks
about
it,
that's
what
I
was
going
to
talk
to
as
well
Christian,
Hernandez,
so
yeah
for
sure
all
right,
so
I
think
four
is
good.
Let's
limit
it
to
four:
let's
not
go
any
more
because
that's
we
don't
want
to
spread
ourselves
too
thin,
but
let's,
let's
synchronize
our
watches
and
meet
back
here
with
with
our
results
right
can.
G
F
G
Would
would
we
also
put
it
in
like
have
okd
built
operators
in
artifact
Hub,
or
is
that
redundant
like?
Does
it
still
come?
We
just
put
them
in
a
catalog
that
we
put
in
on
the
ojd,
repo
and
publicized
on
our
site.
G
What
what
would
the
relationship
be
to
The
Operators
that
are
in
artifact
Hub
I'm,
just
trying
to
parse
that
out
in
my
head?
That's
a
good
question
because
we
could
get
more
publicity,
and
this
is
what
Diane's
thing
right.
Mantra
right
now
is:
how
do
we
get
more
adoption
if
we
put
things
in
artifact,
Hub
and
conjoined
it
with
the
rest
of
the
universe
as
long
as
we
did
it
in
a
way
that
did
not
confuse
it
with
ocp
operators,
so
that's
really
pulling
them
down.
G
So
the
naming
convention
is
important
here,
but
we
probably
still
need
a
repo
to
put
all
this
stuff
in
so
Brian
you're,
probably
right
about
Brian
Bruce.
Sorry,
your
name
is
covered
up
and
I
know
who
you
are
for
years,
but
I
I
think
also
keep
that
in
the
back
of
my
other
thing.
I
would
keep
that
in
mind
when
you're
going
off
and
doing
this
research,
if
there's
a
way
like
the
windows
team
can
be
cajoled
into
building
it
for
us
that
use
them.
G
Like
you
know,
just
say:
we
want
to
learn
how
to
build
it
ourselves,
but
if
this
is
just
an
easy
thing
for
you
to
add,
please
do
and
put
it
here
in
the
repo
and
we'll
manage
getting
it
out
there
and
artifact
Hub
or
wherever
we
want
to
put
it,
but
I'm
curious
what
people
think
if
they
would,
if
you're
pulling
stuff
from
artifact
Hub
now
on
cncf
or
not,
and
it
doesn't
not
a
lot
of
vociferousness
here
so
I'm
thinking,
artifact
Hub
might
not
be
where
you're
getting
here.
Oh.
C
C
C
So
you
can't
really
just
go
to
artifact
Hub
to
get
those
all
right.
We
have
10
minutes
left
I
do
want
to
be
respectful
to
the
other
topic
that
I
promised
I
would
get
to
at
this
meeting,
which
is
the.
D
Was
unfortunately
held
up
in
another
meeting,
so
maybe
we
could
bring
it
up
in
the
next
meeting.
Yeah.
C
Maybe,
and
and
that's
something
that
I'll
have
to
make
sure
I
update
the
threads,
because
we
had
people
asking
in
discussion
in
the
repo
and
in
the
slack
Channel
about
status
and
I
said
that
I
would
ask
so
okay.
So
we
will
postpone
that
to
the
it
to
two
weeks.
The.
D
C
Technical
meeting,
all
right
and
next
up
Jack,
do
you
want
to
talk
about
what
what
you
added
here
to
the
agenda.
E
A
E
So
I
just
wanted
to
kind
of
ask
with
what's
what's
the
best
way
that
we
can
take
ownership
of
our
documentation
like
the
documentation,
that's
hosted
on
docs.orp
leader.io
without
just
always
blatantly
copying
from
the
from
the
openshift
docs
like
what's
what's
kind
of
the
best
process,
so
I
tried
the
process
that
I
was
told,
but
it
didn't
really
work
out
that
well
and
as
far
as
I
can
see,
we
also
just
have
one
contact
person,
who's
kind
of
responsible
for
taking
care
of
okd
and,
of
course,
like
people
are
busy
and
people
have
other
priorities.
E
B
Yeah
I've
been
I'm
looking,
you
know,
I've
been
looking
at
that
issue
that
that
Jack
linked
and
looking
at
the
pr
that
that
Michael
Burke
made
kind
of
like
responding
to
it
or
I
guess
relating
to
it,
I
think
if
we're
gonna,
if
we're,
if
we're
gonna,
stick
with
the
point
that
our
docs
start
as
ocp
product
docs
and
then,
like
Jack,
said
they
get
copied
and
we
kind
of
transformed
them
into
the
okd
docs.
B
We
probably
need
to
look
into
what
they're,
using
in
those
files
to
gate
between
the
okd
content
and
the
ocp
content,
and
then
I.
Imagine
that
we
could
propose
PRS
to
the
source
of
the
docs
as
long
as
we
respect
those
rules
about
how
we
gate
the
okd
content
that
for
now
I
imagine
that's
probably
the
path
we
would
want
to
take
if
we
actually
want
to
like
contribute
changes
and
say
no.
This
is
wrong
for
okd.
B
B
Well,
I
mean
yeah;
they
would
definitely
accept
patches
for
me,
but
I
have
a
feeling
and
I
I
would
need
to
confirm
this.
So
I
need
to
check
with
my
Doc's
contacts,
but
if
we
follow
what
they're
doing
and
we
don't
touch
the
ocp
content,
but
we
use
I
think
they
have
like,
if
else
statements
in
there
for
where
they
want
to
put
in
the
okd
community
content,
if
we're
only
adding
okd
content.
B
C
You're,
muted
I
realize
that's
a
less
than
ideal
response
to
this,
but
all
we
have
right
now
is
Michael.
Burke
Michael
has
not
been
able
to
make
it
to
any
meetings
in
like
the
past,
like
two
months,
I
think
it
is
he's
just
been
exceptionally
busy,
and
so
as
an
alternative
or
as
a
temporary
solution.
We
can
do
an
FAQ
and
just
try
to
promote
that
FAQ
for
people
that
want
to
know
about
the
secrets
issue
and
then
parallel
to
that,
we
can
work
on
getting
more
yeah.
C
But
sure,
but
that
is
sure,
but
that
is
something
that
we
probably
need
Clarity
on
right
now
still
anyway
so
and
that
can
define
a
process
like
the
the
alternate
short-term
process.
If
it
turns
out
that
we
still
have
to
follow
this
sort
of
longer
process
of
relying
on
Michael,
Burke,
etc,
etc.
So
I
think
it's
good
to
have
a
parallel
process
of
quickly
getting
FAQs
out
or
blog
posts
or
whatever
to
address
some
of
these
things.
If
we
can't
get
it
resolved
quickly
in
product
documentation,.
B
Just
one
more
thing
back
to
Jack's
kind
of
original
question:
I
think
this
is
a
question
that
the
community
probably
needs
to
take
up
and
decide,
and
that
is
that,
like
you
know,
there's
probably
going
to
come
a
point
where
it's
gonna,
it's
not
gonna,
be
maintainable
or
scalable
for
us
to
keep
contributing
to
the
product
documentation,
even
though
we
might
use
that
as
our
source
and
so
I
think.
This
is
something
we
do
in
openshift
with
respect
to
the
kubernetes
sources.
B
We
probably
want
to
consider
some
way
that
we
could
have
carry
patches
that
we
keep
for
okd
only
and
then
we
can
start
to
develop
our
own
methodology.
For
how
you
know,
someone
from
the
okd
community
could
propose
a
patch
that
needs
to
be
carried
on
top
of
the
openshift
content,
and
then,
in
that
respect
we
don't
have
to
worry
about
committing
to
the
the
open
shift
commercial
repos.
We
can
keep
our
content
in
the
okd
repos
with
some
automation
that
allows
us
to
have
carry
patches
that
ride.
B
C
And
again,
a
lot
of
this
relies
on
volunteers.
We
need
to.
We
need
more
than
the
seven
people
or
ten
people
that
always
show
up
at
meetings
right.
We've
got
to
do
some
Recruitment
and
that's
something
I
think
in
the
coming
year
that
that
needs
to
be
prioritized,
speaking
of
which
that
actually
leads
to
our
next
topic.
There's
a
list
of
prioritization.
This
is
what
the
Community
Development
Group
came
up
with
for
prioritization.
C
If
anyone
wants
to
add
or
change
this,
but
I
think
this
is
at
least
from
the
Community
Development
standpoint,
what
the
Community
Development
Group
wanted
to
prioritize
for
this
coming
year.
Does
anyone
have
anything
that
they
would
add
or
change
from
that
list?
Very
last
item
prioritization
for
q1
anyway,
of
2023.
C
B
Right,
what
about
infrastructure
like
we've
talked
a
lot
about
topics
where,
if
the
okd
community
ever
got
to
the
point
where
we
had
like
operate
first
or
our
own
infrastructure,
we
could
start
to
host
our
own
things.
You
know,
and.
C
That
brings
up
something
that
I
didn't
want
to
talk
about
at
this
meeting
without
Christian
here,
but
we
actually
did
get
sort
of
a
templated
issue
created
by
the
operate
first
folks
about
how
are
things
going
for
you?
What
not
and
so
I
think
it
was
not
very
first
yeah,
and
so
that's
something
we're
going
to
want
to
talk
about
like
how
everything's
going
and
and
well
it
could
be
q1
so
so
Amigo
is
like.
Is
this
limited
to
go
on?
Well,
it
could
be
even
beyond
that
so
yeah.
B
C
All
right:
well,
we
are
at
time
I
want
to
be
respectful
of
people's
time
any
last-minute
thoughts
before
we
end
this
meeting
all
right.
Well,
thank
you.
So
much
as
always,
folks
are
really
passionate
and
that's
very
much
appreciated.
So
Community
Development
meeting
next
week
same
bat,
Time
same
bat,
Channel,
and
then
this
meeting
happens
again
in
two
weeks.