►
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
A
group
meeting
for
may
3rd
of
the
year
2022
and
we
have
an
agenda
there
bruce
if
you
want
to
go
ahead
and
put
your
name
and
I'll
put
them
by
the
way
I'll
put.
A
There
we
go
all
right
and
take
a
quick
second
to
look
over
the
agenda
and
any
modifications
we
need
to
make
anything
not
quite
right.
A
Why
don't
you
go
ahead
and
do
that
and
I'll
cover
the
first
item,
because
we'd
have
that
taken
care
of
so
last
week
we
talked
our
last
meeting.
We
talked
about
archiving
the
community,
repo
diane,
put
that
in
christian
signed
off
on
it
and
actually
the
community.
The
old
community
repo
has
now
been
archived.
A
So
we
just
need
to
add
those
few
pages
into
the
current
documentation
that
we
wanted
to
to
save,
and
actually
I
think
you
did
that
is
there.
Is
there
any
page
that
hasn't
been
moved
over
yet
brian
that
we
wanted.
A
A
A
A
I
understand
it's
a
work
in
progress.
Brian
you're
still.
C
Yeah,
as
I
said
we
were
talking
before
we
started
the
meeting
official.
I
broke
my
cluster,
so
I
spent
days
sort
of
trying
to
so
work
through
things
and
probably
made
it
10
times
worse,
so
I'm
actually
going
to
just
trash
and
rebuild
the
cluster.
Then
I
can
continue
with
that
work.
So
hopefully
there'll
be
some
progress
before
the
next
meeting.
C
A
Yeah
working
group
repo
we'll
be
waiting
to
move
things
over
once
we
actually
have
our
moving
plan,
which
we'll
talk
about
towards
the
end
of
this.
I
haven't
got
a
chance
to
do
the
moving
of
the
working
group
menu
around
yet
that
will
probably
happen
tomorrow.
I'll
have
some
time
for
that.
So
some
updates
that
we
need
to
push
out
is
I
decided
to
do
this
as
a
qa.
A
Sorry
frequently
asked
question
faq,
so
we
actually
get
asked
a
lot
about
like.
Are
there
many
4.9
and
it
makes
sense,
I
think,
to
do
an
faq
and
then
wrap
it
with
some
text
that
says
by
the
way
this
applies
to
4.9.
This
idea.
C
A
Right
exactly
yeah
and
the
4.10
blocker
is
over
with
now,
and
there
is
a
new
4.10.
So
actually
we
should
change
this
that
there
okay
updates
new
4.10
that
came
out.
I
haven't
updated
to
that
one
yet,
but
I
hope
to-
and
that
was
actually
vedim
cut,
that
one
so
christian
didn't
have
access,
but
vadim
stepped
in
to
cut
a
release.
Okay,
that
was
cool,
f
testers.
A
C
Well,
I
mean
in
in
the
last:
what's
the
last
open
shift
red
and
road
map,
they
actually
did
talk
around
a
new
effort
around
crc
for
ocb,
so
I
think
that
might
have
generated
some
of
the
interest
because
I
think
they're
looking
at
a
ways
to
cut
it
down
further
to
give
that
sort
of
desktop,
because
the
sort
of
microshift
is
an
edge
that
doesn't
have
the
gui
or
doesn't
have
that
open
shift
experience
where
crc
is
meant
to
give
you
that
a
personal
open
shift
with
a
very,
very
similar
experience,
although
some
of
the
monitoring
and
the
advanced
clustering
stuff
is,
is
missing.
C
But
you
do
get
that
developer,
ui
experience
and
I
think
that's
why
there's
there's
renewed
effort
there.
It's
a
big
downside
here,
because
I'd
be
interested
to
see
how
that
team
has
got
it
getting
on
that
she's
talked
about
the.
I
think
what
they
called
it:
the
the
group
that
have
their
own
cloud
they're
going
to
look
at
that
right.
A
C
And
then
for
the
seth
testers
do
we
have
any
instructions?
Because
when
I
first
started
this
group,
one
of
the
challenges
I
had
is:
how
do
we
set
things
up?
Because
a
lot
of
this?
The
instructions
are
written
for
ocp
and
it
assumes
that
you've
got
access
to
the
registry
with
the
red
hat
operators
on
so
do
we
have
a
link
that,
if
we're
asking
for
testers
that
they
can
actually
follow
to
set
it
up
sort
of
work
with.
A
Yeah,
I
think
we
might
approach.
Maybe
we
can
get
shri
to
write
those
up.
He
was
the
one
who
actually
had
access
to
his
own
stuff.
Maybe
we
could
ask
him
to
just
write
a
quick
page
of
instructions
to
to
demonstrate
that
that
I
did
see
that
they
have
narrowed
down
the
error
a
little
bit
more.
A
Think
in
cluster
first
and
then
anything
that
we
can
do
for
out
of
cluster
is
good.
I
didn't
get
a
chance
to
read
what
the
latest
update
was,
but
apparently
they
did
narrow
down
the
issue
even
more
and
there
is
a
a
bugzilla
further
upstream
for
it.
Okay,
but
yeah
I
mean
it
would
be
good
anyway,
because
we
get
a
lot
of
questions
for
it.
So
let
me
see
if
I
can
get,
let's
see,
I
can't.
B
Yeah-
and
I
guess
a
related
thing
is
that
there
actually
is
somewhere
in
the
weeds
rooksef
operator.
Yes,
there
is
which
is
not
in.
Of
course,
our
operator
repository.
C
Well
well
for
ocp
they've
actually
done
quite
a
good
job
because
they've
rolled
it
all
up
into,
I
forgot
what
they
call
the
operator
now.
Let
me
have
a
quick
look.
C
B
Yeah,
although
it
is
fairly
straightforward,
like
I
installed
rooksef
long
time
ago,
based
on
charo's
instructions,
yeah
and
his
and
then
his
instructions
didn't
get
updated,
you
know
because
he
moved
on
to
bigger
better
things,
but
the
next
time
I
had
to
install
it.
I
started
with
the
the
manifest
files
that
were
in
the
the
rook
ceph
repository
and
just
compared
it
with
what
I've
done
before
and
there
they're
not
that
many
changes
that
you
have
to
make
to
it.
B
B
But
one
of
the
things
that
that
I
think
is
it's
almost
sort
of
an
underlying
miasma
is
that
nothing
is
easy
compared
to
like.
You
know,
compared
to
many
other
projects,
open
source
projects.
The
you
know
when
you,
when
you
do
many
things,
it's
relatively
high
risk
and
it's
easy
to
get
in
over
your
head,
because
the
actual
framework
is
quite
deep.
C
C
I
can
then
put
the
storage
foundation
on
so
I
get
object,
block
file
storage.
I
can
put
key
dot
ion,
so
I
got
local
registry.
I
can
just
put
git
ops
on,
I
can
put
pipelines
on
and
I
have
a
full
sort
of
self-contained
development
environment.
I
can
even
put
code
ready
workspaces
on
how
that
workspace
is
what
whatever
they're
calling
them
now
and
I
get
this
full
thing
and
I
don't
need
any
skills.
It's
just
point
and
press
for
the
operator.
Olm.
B
Right,
well,
I
think
I
think
that's
really
critical.
I've
been
actually
pushing
that
if
you
once
you
get
to
the
point
of
okay,
the
shiny
new
toy
is
installed.
I
want
to
actually
do
something
yeah,
then
you
need
the
various
catalog
operators.
A
They
are
working
on
the
catalog,
the
new
individual
catalog
for
okd.
Apparently,
that
project
has
been
sort
of
put
aside
slightly
because
of
some
of
these
larger
issues
that
were
looming,
but
the
okd
catalog,
we
are
told,
is
coming
right,
the
okd
specific
catalog.
So,
let's
see
what
happens
and
push
for
stuff
like
this
to
make
it
into
it
or
rally
the
community.
C
But
I
also,
I
also
think
our
technical
documentation
that
we're
doing
will
enable
people.
Because
again,
if
I
look
at
the
operator,
they
all
point
to
this
registry
thing,
but
now
that
we
know
that
just
replace
that
one
with
this
okd
410
v
opera
and
base
image,
and
then
I
can
just
use
docker
build
or
podman
build.
C
C
B
But
by
the
way
I
did
I
did
install
the
the
latest
410
without
a
hitch.
B
Very
good,
no
further
problems
there
and-
and
I
did
go
back
and
just
out
of
interest.
I
installed
the
ocp
crc
and
that
works
fine,
okay,
which
which
in
a
way-
and
it
is
410.
B
because
one
of
the
reasons
I
installed
it
was
to
see
because
charo's
instructions
were
based
on
four
eight,
and
I
wanted
to
see
what
you
know
I
mean
like.
Obviously,
if
we're
going
to
do
a
crc,
it
has
to
be
at
least
at
the
same
level
that
the
ocp
one
is
sure.
So
that's
one
of
the
reasons
why
I
was
installing
that
again
and
also
see
whether
or
not
it
took
down
my
laptop.
B
With
all
the
other
stuff
that's
on
there
and
it
it
seems
fine,
I
don't
really
have
a
casing
even
to
use
it
though,
but.
A
That's
the
thing
is:
that's
why
I
think
we
need
to
sort
of
reach
out
to
the
community
to
get
some
users
who
actually
have
a
need
to
use
this,
and-
and
really
you
know,
run
some
things
on
it
that
someone
trying
to
learn
okd
would
want
to
do
right,
because
this
is
a
learning
tool,
an
experimental
tool
or
experimenting
tool.
It's
a
it's
it's.
We
need
to
find
some
people
who
are
in
that
position
to
to
give
feedback
on
on
the
builds
that
we
do.
B
Right
I
mean
there,
are,
I
don't
know,
there's
probably
close
to
a
dozen.
B
Kubernetes,
you
know
minimized
versions
that
you
can
install.
You
know,
like
mini
cube
or
kind
type
things
yeah
for
sure.
You
know
k3
k8
I
mean
the
list
goes
on
and
on.
B
In
the
classes
I
was
doing,
and
I
had
to
go
back
and
forth
between
kind
and
mini
cube,
to
try
and
see
exactly
what
the
differences
were.
B
C
A
B
Okay,
so
I
think
I
think
where
you're
headed
is
really
the
point
in
a
way
is
that
we,
if
we
don't
know
the
purpose
for
it,
then
yeah
it's
hard
to
know
if
it's
worth
doing
or
worth
spending
time
on
versus
everything
else,
yeah.
B
We
should
have
a
discussion
of
the
pros
and
cons
of
okay,
like
what
would
it
buy
somebody,
because
we
can't
always
point
people
to
the
red
hat
ocp1
suggests
that
they
go
get
a
you
know,
developers,
you
know
free
account
and
therefore,
then
they
get
a
you
know,
pull
secret.
That
will
avoid
a
lot
of
the
grief
and
yeah.
B
And
but
some
things
I
mean
like,
like
mini
cube,
does
have
a
console,
it's
not
as
nice
for
sure
and
all
of
the
all
the
red
hat
people
that
are
doing
all
these
demos,
pushing
serverless
or
corkus
or
whatever
they
seem
to
uniformly
use
mini
cube.
B
And
and
the
guys
that
you
know
adobe,
that
was,
you
know,
teaching
operators
he
was
using
mini
cube.
B
So
I
mean
I
don't
really
have
a
dog
in
the
fight
product,
wise.
C
B
Well-
and
why
is
that,
like
part
of
that,
is
that
okay,
so,
like
the
the
the
console,
software
has
a
dependency
on
metrics,
okay,
which
include
which
pulls
in
prometheus,
which
pulls
in
all
that
stuff?
And
I
don't
know
I
don't
know
how
well
like.
Is
it
even
documented
the
dependencies
between
the
different
components.
C
C
C
B
Well,
that's
that's.
Why,
like
at
one
point,
we
sort
of
threatened
to
start
up
a
working
group
which
I
was
happy
to
be
on
to
go
through
and
slim
down
the
crc
and
try
and
figure
out
exactly
what's
required,
what's
useful,
and
how
can
we
do
that
and.
C
C
A
Let's,
let's
first
off,
we
need
to
communicate
to
people
to
get
other
crc
folks
in
the
conversation
other
than
just
ourselves.
So
that's.
B
B
But
I
think
for
our,
I
guess
limited
resources.
I
don't
see
crc
rising
that
high
compared
to
all
the
other
things
that
we
need
to
worry
about.
So
I
would
leave
the
question
mark
on
that
item.
A
Okay,
so
moving
on
to
the
twitter
issue,
so
there's
an
issue
that
the
the
twitter
was
set
up
with
a
red
hat,
employee's
email
address
and
from
what
I
can
gather
that
red
hat
employee
is
not
going
to
be
an
employee
or
is
not
an
employee
anymore,
and
so
we
have
to
connect
it
to
a
different
email
address.
I
messaged
diane
about
this.
I
have
not
heard
back
the
the
other
thing
that
this
brings
up.
Is
we
really
need
a?
A
We
need
to
start
looking
at
setting
up
an
email
address
that
is
particular
to
the
group
and
that
is
accessible
by
multiple
people
or
you
know,
or
provide
an
email
list,
email
for
setting
things
up
or
something
like
that,
like
we
set
up
a
separate
google
group
or
something
to
where
we
are
then
able
to
not
be
dependent
on
one
individual.
For
these
types
of
things,.
A
From
the
twitter
side,
I
think
it's
one
email
address
per
account.
I
could
be
wrong,
I
don't
know
I'm
not
a
I'm.
Twitter
is
not
something
that
I'm
that
I
use
a
lot
so
but
yeah.
I
believe
it's
an
it's
attached
to
a
particular
email
address.
I
don't
think
there's
any
way
to
delegate,
but
we
can
investigate
that.
But
that's
where
we
are
right
now
I
mean,
regardless
of
of
that
part,
we
do
need
to
figure
out
the
part
of
getting.
C
C
C
We
need
to
check
that
with
diane,
but
most
corporates
have
that
sort
of
policy
right
and
now
I
I
think
oh
go
ahead.
Yeah.
I
I
think
getting
a
gmail
account
or
a
something
like
that
that
we
can
then
have
multiple
people
know
the
password
of
is
probably
the
way
to
go,
or
something
like
that.
Unless
we've
got
some
money
and
we
can
set
up
our
own
and
pay
for
our
own
mail
domain.
A
If
we
so
here's
the
thing,
can
we
need
to
check
with
diane
about
this?
Can
we
convince
the
red
hat
admins
to
put
different
mx
records
in
the
domain,
because,
if
so,
I
don't
know,
I
don't
want
to
get
over
the
heads
of
anyone
here
if
you've
not
deal
dealt
with
mail
administration,
but
in
essence,
in
a
domain
record,
there
are
what
are
called
mx
records
which
point
to
mail
servers
right.
A
We
if
we
can
have
them,
set
the
mx
records
to
whatever
we
want.
We
can
set
it
to
someone's
server.
I'm
happy,
I
run
mail
servers
happy
to
volunteer
them.
We
could
use
google,
we
could
use
whatever
the
question
is
just
can
we
get
them
to
change
the
mx
records,
because
then
we
could
get
admins
at
okd.io
whatever
at
okdio
and
do
multiple
aliases
or
whatever
it's
just
a
question
of?
A
A
Yes,
yes,
100,
so
we'll
put.
A
We
can
put
it
on
the
working
group,
ema,
google
group-
and
we
can
put
it
in
the
slack
and
I
don't
no
one
is
using
the
matrix
account
no
one's
chatting
in
there
and
I
don't
know.
I
think
we
need
to
have
a
conversation
it.
It
exists.
I've
been
in
there
but
we'll
see.
A
Right
yeah,
it's
too
spread
out
as
it
is
okay
survey,
so
I
did
get
the
survey
from
treaty,
and
so
the
link
is
there.
We
should
asynchronously
go
over
this
over
the
between
now
and
the
next
meeting
and
I'll
send
a
reminder
out.
Maybe
next
week
on
the
working
group
email
list,
any
questions
that
you
think
we
should
add.
Is
it
good
enough,
whatever
let's
hammer
this
out
and
then
send
it
out
to
our
users
in
the
various
flat?
A
A
B
A
New
folks,
as
collaborators
and
and
we'll
go
from
there,
that
sound
like
a
plan,
yep
all
right
requests
for
testers
yeah,
we
need
bare
metal
testers,
we're
getting
more
and
more.
It's
amazing
how
much
bare
metal
stuff
is
going
on
that
and
crc
are
really
surprising
me
so.
C
A
At
the
main
meeting
we
can
ask
sandro
because
he
should
show
up
we'll
find
out
like
where
they
are
at
and
if
they
have
people
who
want
to
test
some
stuff
and
and
write
some
stuff
up
for
us,
they've
been
kind
of
dormant
lately,
but
maybe
we
can
find
out
if
they
can
volunteer
some
people
to
help
with
some
documentation,
or
at
least
just
circle,
the
channel
a
little
bit
and
answer
questions
when,
when
folks
have
questions
that
would
be
helpful.
Okay,
okay
and
let's
see
what
else
style
updates.
C
Styling
update
yes,
so
brandon's
did
his
pull
request
and
you
should
have
noticed
that
the
look
and
feel
has
slightly
changed
and
we've
got
a
much
brighter
main
page
on
the
light.
The
dark
mode
hasn't
changed
an
awful
lot,
but
the
light
mode
has
got
significantly
better,
more
readable
and
more
better
contrast.
C
So
I'm
not
sure
whether
he's
actually
planning
to
do
any
more.
But
that's
that's
the
work
that
he's
done
so
far
yeah
and
I
thought
it
was
important
to
get
that
release
before
we
actually
do
any
moves.
A
Can
we
acknowledge
his
efforts
somewhere
on
the
site
or,
and
I
would
say
twitter,
but
once
once
we
get
that,
but
just
be
like
thanks
for
the
efforts
to
update
our
site,
like
I
feel
like,
we
should
give
some
acknowledgement,
because
this
has
all
been
done
sort
of
in
the
background.
A
You
know-
and
that
was
a
great
thing
to
volunteer
some
time
to
do
so.
A
B
C
Until
we
get
a
twitter
or
something
it's
difficult
to
know
where
to
put
that
yeah
I
mean
what
we
can
do
is
we
I
mean.
I
know
there
is
a
blog
on
there
that
we
haven't
used
since
we
actually
moved
over
to
mk
docs.
I
don't
know
whether
we
want
to
kill
it
off
or
try
and
get
it
made
active
again,
but
I
mean
we
could
put
something
and
maybe
ask
him
to
maybe
ask
brandon
just
to
put
a
few
words
about
what
he
did
and.
A
C
Yep,
I
can
do
that
and
then
the
last
one
publishing
update.
So
when
we
publish
it
does
a
spell
check
and
a
link
check
now
the
question
is:
do
we
want
to
keep
doing
that
or
do
we
want
to,
and
the
reason
I
ask
is
because
things
like
the
minutes
jamie
he
broke
us
with
all
the
spell
check.
Oh.
C
So
the
minute,
what
I've
done
is
I've
just
gone
in
and
disabled
spell
checking
on
your
minutes
section.
So
everything
in
that
minute
and
everything
below
there
is
now
removed
from
spell
checker.
So
it's
really
do
we
find
that
automation,
useful
or
a
pain
in
the
backside
that
we
wanted
to
get
rid
of
it's.
It's
always
nice
to
have
a
site.
C
That's
correctly
spelled
and
all
the
links
are
always
working,
but
it
means
when
someone
wants
to
do
a
quick
update,
they
can
suddenly
get
stuck
with
someone's
site's,
broken
or
someone's
taking
the
page
down,
and
it's
not
something
they're
interested
in
fixing,
but
their
their
update
is
now
blocked
because
of
it
yeah
and
I
don't
have.
I
don't
yet
have
automation
to
actually
go
check
to
see
how
we've
got
any
broken
links
this
week
or
anything
like
that.
But
so
it's
really.
C
A
A
Apparently,
the
way
that
that
is
written
causes
an
error
in
in
the
link
checking
because
it
it's
thinking
that
it's
a
parenthesis
for
a
url,
and
so
we
can't
find,
for
example,
university
of
michigan
as
a
link,
but
there's
a
way
to
turn
it
off
at
the
top
of
the
page
right
like
for
the
ins
for
an
entire
page.
C
Yeah
there
are
sort
of
like
sea
spell
and
there
are
various
things
you
can
put
in.
So
I
think,
for
example,
some
of
the
pages
I've
actually
added
page
specific
spellings
that
are
accepted
because
everyone's
email
address
and
things
like
that
it
it
bought
with
spelling
on.
So
I
think
the
link
checking
and
the
spelling
off.
A
B
Well,
okay,
so
I
mean,
I
think
spell
check
is
a
useful
thing,
especially
if
it's
flexible
on
uk
versus
canadian
versus
american
spelling.
You
know
for
color,
and
you
know
honor
and
things
like.
A
B
B
C
B
Okay,
so.
C
A
B
C
Right,
so
for
them
for
the
minutes,
if
we
just
want
to
say
they
made
so
whoever
writes
them
up
is
what
gets
published,
yeah
warts
and
all
then
that's
okay,
but
I
actually
think
if
you've
got
a
main
section
of
prose-
and
it's
just
got
lots
of
spelling
mistakes
in
it
just
makes
the
thing.
No
one
cares
about
this.
No
one's
actually
cared
enough
to
write
it
properly
and
it
actually
depressed
from
the
whole
site.
Yeah
yeah.
I
do.
A
Exactly
okay,
so
I
guess
we'll
keep
it
on.
I
will
be
a
little
more
mindful
and
if
we
can
maybe
turn
it
off
for
now
for
meeting
minutes
just
because
it.
A
Okay,
good
because
when
you're
typing
stuff
in
it
can
be
very
you're
just
trying
to
get
it
in
right,
you
know
and
technically
we
we
really
should
have
someone
else
taking
the
notes,
as
opposed
to
also
leading
the
meeting,
but
we'll
get
there
when
we
get
more
people
involved.
Okay,
so
is
there
anything
else
that
we
need
to
cover
or
to
do
is
are
to
check
with
diane
by
changing
the
mmx
record.
A
That's
me
and
then
brian
you're,
going
to
get
a
blurb
on
the
web
website
style,
updates
that
we
can
share
out
to
give
some
credit
and
thank
you.
A
A
C
C
A
I
did
actually
someone
put
february
15th
what
should
be
the
purpose
and
format
of
the
guides,
and
I
think
that
was
the
folks
doing.
The
guide
stuff
like
dan,
axelrod
and
and
christian
and-
and
you
were.
C
Okay,
oh
the
other
thing
I
wanted
to
say
is:
if
you
have
a
look
at
the
issues,
I
think
we've
got
three
or
four
issues
in
the
openshift.io
repo.
Oh,
I
think
most
of
them
are
old
and
we
can
probably
close.
There
are
things
like
the
charter,
and
I
just
I
was
just
trying
to
tidy
everything
up
before
we
actually
do
the
move
make
sure
that
we
don't
lose
anything.
C
So
I
was
just
trying
to
shut
them
down
and
I
think
I
mean
we're
already
trapping
things
like
the
the
charter
outstanding
actions,
which
I
think
is
one
of
the
issues
I'm
just
thinking,
can
we
actually
close
off
issues
and
shut
down
things
and
okay.
A
A
B
C
A
I
think
we
do
need
to
have
a
conversation
about
the
matrix
situation,
update
group
charter.
I
think
we're
good.
We
can
close
that
yesing
security
contacts,
so
I
we
got
a
hold
on
that.
I
sent
an
email
to
muhammad
who
had
volunteered
to
to
do
security,
stuff
and
haven't
heard
back.
So
let
me
reach
out.
It
was
it's
like
we
we
connected
on
chat
and
then
I
said
well
I'll,
send
you
an
email
since
we're
in
different
time
zones,
and
then
I
haven't
heard
back
from
them.
A
C
But
so
I
I
don't
think
that's
something
that
we're
not
going
to
add
it
to
the
documentation
unless
there's
a
consensus
that
we're
going
to
use
it,
people
are
going
to
check
it,
support
it,
and
so
I
I
would
like
I
would
say,
let's
close
this
and
move
it
to
a
discussion
group.
That's
fine,
because
it's.
A
Well,
the
security
contact
did
we
decide
to
just
in
terms
of
the
contact?
Tell
you
what
let's
keep
that
open,
because
that
might
be
affected
by
the
mx
disc
record
discussion?
Okay,
because
if
we
can
get
like
security
at
okd.io,
that
would
be
fantastic.
C
C
A
C
A
Rebranded
because
there
are
actually
some
unique
bits,
for
example,
we
did
the
change
to
c
groups
v2
before
ocp
did
there's
also
a
couple
of
systemd
units
that
are
unique,
so
there
are
some
things
that
are
unique,
but
what
do
you.
C
A
I
think
we
need
to
do
an
analysis.
I
think
the
appropriate
path
is
to
actually
do
an
analysis
of
that
and
see
what
type
of
artifacts
are
okd
specific
and
there
are
some.
I
know
that
there
are
some
things
in
a
node
that
are
okd
specific,
that
aren't
just
branding.
So
you
know,
and
particularly
once
we
get
into
the
community
the
okd
community
operators
catalog.
If
there's
a
security
issue
with
the
catalog
configuration
things
like
that,
you
know,
but
let's.
C
Yeah,
I'm
just
going
through
all
the
repos,
I'm
just
trying
to
shut
down
anything
that
can
be
shut
down.
So
when
we
do
the
move,
everything's
clean-
and
we
don't
have
to
worry
about
taking
issues
with
this-
because
I
think
code
goes
across
quite
easily
with
a
a
sort
of
a
fork
where
we're
gonna
leave
all
the
issues
and
discussions
behind.
C
A
I
think
so
yeah,
okay
cool
well
seeing
nothing
else.
I'm
gonna
bid
everyone
ado
and
stop
the
recording
and
I'll
see
you
all
at
the
I'll
see
you
all
online
as
we
hammer
out
the
transition
plan,
asynchronously
I'll
make
sure
I
send
out.