►
From YouTube: OKD Working Group Meeting 01-18-2022
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
All
right
well,
let's
get
started,
welcome
folks
to
the
first
meeting
of
the
okd
working
group
general
group.
This
is
our
meeting
for
january
18th
of
2022
and
we
have
an
attendees
section.
So,
if
you're
an
attendee,
please
in
the
meeting
notes,
put
your
name
and
if
you
so
choose
your
affiliation
and
we'll
put
that
in
the
chat
again
in
case
anyone
has
joined
since
that
was
posted.
A
A
All
right
great:
well,
let's
jump
into
the
first
items,
as
I
mentioned,
vadim
is
not
here,
but
he
did
put
some
notes
in
there.
The
new
4.9
stable
release
is
out
with
no
significant
changes.
The
123
and
122.5
rebases
are
landing
soon,
which
would
unblock
the
fedora
35
rebase
and
christian
landed
the
final
okd
specific
bits
in
the
machine
config
operator
master
on
410
and
there
we
are
about
to
be
100
upstream
soon.
A
That
is
awesome
and
there's
some
progress
on
the
okd,
assisted
installer
working
on
the
installer,
slash
ai
changes,
and
are
there
any
questions
on
that?
I
don't
think
christian
is
here
as
well,
so
we
don't
really
have
anyone
from
that
side
of
the
house
here.
They
can
answer
questions,
but
if
you
want,
we
can
put
them
in
the
notes.
Any
questions
you'd
like
to
put
in
the
notes
for
the
next
meeting
to
be
answered
on
these
things.
Vadim
provided.
A
Okay,
not
seeing
anything,
let's
move
on
next
up
is
timothy
with
fedora
core
os
updates.
B
Yes,
hi
everyone
and
happy
new
year,
so
on
the
federal
court
side
of
the
house,
we
working
on
chorus
layering
work,
so
I
think
there
are
two,
this
documentation,
experimental
documentation
and
the
tracker
for
for
the
work
there,
which
is
like
the
big
thing
happening
right
now
in
federal
crest,
which
will
hopefully
enable
fully
layering
based
images
for
kd.
So
everything
we
do
in
sync
and
much
easier
to,
I
think,
with
with
theracross
changes
involving
less
rebuilds
and
faster
turnaround.
B
A
All
right
seems
pretty
straightforward
up
next
brian:
do
you
want
to
discuss
updates
from
the
dots
or
something
group.
C
Yep-
and
we
might
as
well
start
with
that,
so
we
had
our
first
meeting
of
the
last
week
for
what's
the
documentation,
work
group
and
one
of
the
things
that
came
up
is:
should
we
rename
the
work
group,
because
the
scope
has
expanded,
we're
no
longer
just
looking
at
documentation
we're
looking
at
things
like
the
social
media
platform,
we've
looked
at
the
community
interaction
model,
how
we
can
actually
do
that
we're
talking
about
the
new
gate
organization,
so
there's
been
a
couple
of
thoughts.
C
Should
we
be
the
comms
work
group,
or
should
we
be
community
liaison
of
community
outreach
work
group
because
we
are
sort
of
doing
that
role,
so
any
feedback
on
that
would
be.
We
have
a
discussion,
a
couple
of
other
points
that
we
talked
about
while
I'm
on.
C
We
are
still
looking
at
moving
into
a
new
git
organization
for
okd,
so
out
of
the
open
shift,
so
community
members
have
more
access
to
the
community,
and
with
that
in
mind
we
have,
we
did
have
a
discussion
around.
Do
we
have
too
many
contact
points,
because
there
have
been
some
comments
that
we've
got
too
many
touch
points.
C
We've
got
the
google
mailing
list,
we've
got
the
two
slack
channels
and
we
have
tried
to
move
everyone
to
the
discussions
group
within
the
okd
dot,
git
repo,
and
then
there
are
various
social
media
and
from
us
who
are
in
the
community.
C
The
comment
is
there's
too
many
places
to
to
to
track
and
to
follow
what's
going
on,
and
it
must
also
be
confusing
to
new
members
and
as
to
where
they
ask
questions
and
are
the
people
looking
at
the
channel
that
they've
chosen
to
ask
the
question
and
are
they
getting
a
response
in
a
timely
manner?
So
I
think
that's
a
second
issue
and
it'll
be
a
good
opportunity
to
sort
that
out.
C
So
as
we
move
to
the
new
git
org,
we
can
put
everything
in
place,
so
we
don't
actually
cause
confusion
and
there
were
no
new
issues
and
there
were
no
real
changes
and
I
did
tweak
the
colors.
So
we
now
pass
the
accessibility
checks
from
the
google
developer
tooling,
and
we
had
a
couple
of
contrast
issues.
So
that's
all
been
insulted
now.
C
So
really
those
two
discussion
items.
I
don't
know
whether
you
want
to
have
a
discussion
in
this
group
or
whether
people
just
want
to
ping
and
add
to
discussions
around
the
naming
and
also
community
outreach
channels.
D
The
only
thing
that
I
would
say
is
that
documentation
and
getting
good
documentation
for
okd
is
still
a
really
high
priority
and
so
having
visibility
of
a
working
group
working
on
documentation
is
pretty
key
and
that
that
communication-
I
know
it's
a
priority,
but
it
from
from
my
perspective,
it's
the
getting
the
documentation
up
to
snuff
is
still
something
we
really
need
to
focus
on,
as
you
know,
as
an
entire
community,
not
just
the
working
group
folks,
but
I
I
wouldn't
want
to
lose
visibility
of
that,
because
I
think,
from
my
perspective,
the
thing
that
I
get
the
most
feedback
on
personally.
D
Is
you
know
the
documentation
is
still
needs
improvement.
So
I
think
I
I
shared
with
jamie.
I
didn't
share
it
with
a
group,
but
one
of
my
ex
red
hat
colleagues
from
vmware.
I
don't
know
if
you
shared
it
with
the
docs
meeting
jamie
john
holly's
review
of
trying
to
install
on
vmware
something
yeah.
So
I
was
gonna
you
know.
For
me,
my
concern
is:
is
getting
getting
out
of
the
business
of
focusing
on
documentation.
D
A
What
about
anyone
else
in
terms
of
the
naming
part
of
it.
A
All
right:
well,
the
docs
group
is
going
to
be
talking
about
it
next
week
and
we'll
take
this
feedback
or
take
the
feedback
that
we
got
and
work
on
that
and
see
where
we
land
and
we'll
definitely
let
folks
know
any
thoughts
on
the
narrowing
down
the
scope
of
our
communications
right
and
actually
so
timothy
points
out
that
we
do
have
reserved
okd
project
on
github
and
get
lab
diane.
A
Has
there
been
any
movement
on
trying
to
get
okd
just
okd
project
wrestled
from
the
hands
of
the
random
person?
No,
no.
D
The
random
person
and
the
random
people
in
at
github
that
approve
that
stuff
haven't
responded
at
all.
So
I
think
we
probably
just
move
with
the
okdproject.org
and
be
happy
with
that.
A
Okay,
I
think
we
waited
long
enough
sure
so
we'll
take
that
to
the
docs
group.
Another
thing
to
come
out
of
the
docs
group
is
that
brian
and
I
are
setting
up
a
meeting
with
vadim.
A
Actually
I
just
got
done
talking
to
vadim
a
little
bit
ago
about
this
brian
and
I
are
going
to
meet
with
him
and
talk
about
the
current
main
okd
repo
and
like
what
needs
to
stay
and
what
needs
to
go
and
like
reworking
that,
because
it's
sort
of
like
a
long
screed
right
now
of
differing
ideas,
so
we'll
meet
with
vadim
and
see
from
an
engineering
perspective
what
he
thinks
needs
to
stay
sort
of
at
the
top
level.
Read
me
in
the
repo
versus
other
places.
A
The
other
thing
was
there
anything
else.
No,
I
think
that's
about
it.
Brian!
Is
there
anything
else?
Where
are
we
good.
A
Actually
have
those
twitter
credentials,
yet
I.
D
Reached
out
to
her
again
last
night
or
her
last
night,
my
last
my
last
night
her
morning,
she's
in
india,
I
believe-
and
so
I
haven't
heard
back
from
her.
I
will
ping
her
again
today
and
see
if
I
can
get
those
back
here,
I'm
sure
it
is
she's,
a
red
hat
employee,
so
she'll
respond
eventually.
A
Yeah
excellent,
let's
see
so
next
up
is.
A
Issues
there's
there
were
no
new
issues
submitted
to
the
repo
the
main
repo
in
january.
Yet
discussions
note
that
the
discussion
section
is
meant
to
be
like
covering
the
discussions
items
in
there
and
if
you
have
like
new
items,
that's
where
you
would
put
like
new
items
so
like
sandra
that
would
your
item
would
actually
go
under
new
items,
since
it's
a
new
topic,
as
opposed
to
something
that
was
submitted
to
the
discussions
section,
which
is
actually
sort
of
a
self-referential
thing
so
well
sandra.
A
Why,
since
we're
sort
of
skating
into
that,
there's
no
discussions
in
the
repo
of
note
so
sandra?
Why
don't
you
go
ahead
and-
and
you
had
some
thoughts.
E
I
kind
of
maybe
it's
just
my
personal
opinion,
but
I
I
kind
of
find
difficult
to
find
a
single
place
where
a
point
user
to
ask
questions
and
get
answers
from.
I
come
from
the
overt
experience
and
there
we
have
a
mailing
list
and
several
social
media.
But
whenever
a
question
arrives,
we
everyone
direct
to
the
user
mailing
list.
So
we
have
all
the
questions
and
answers
in
a
single
place.
E
So
I
wonder
if
it
makes
sense
to
have
us
a
main
contact
point
where
we
can
direct
people
asking
questions
and
looking
for
answers
before
asking
instead
of
having
to
to
search
multiple
channels.
If
there
is
already
someone
who
asked
the
question
or
if
someone
already
provided
the
needed
answer
there.
A
A
Thing
it
can
be
tagged
with
work
group.
We
did
verify
that
we
can
add
tags
and
labels
and
whatnot
to
those
discussion
items
as
it
currently
is
in
the
in
the
okd
dot
io
repo,
so
that
the
thought
was
that
we
would
be
heading
in
that
direction.
Brian,
you
want
to
speak
a
little
bit
more
to
that.
C
Yeah,
so
just
a
very
quick
recap,
so
we've
got
the
google
mailing
list,
which
was
initially
meant
to
be
for
the
contributors
that
wanted
to
discuss
sort
of
technical
issues
that
started
getting
taken
over
by
users
asking
for
help.
We've
got
the
two
slack
channels:
one
is
a
developer
and
one
is
a
user
again.
The
working
group
were
meant
to
look
at
the
developer
and
the
end
users
that
want
support
that
want
help
with
things
like
install.
They
were
meant
to
use
the
user
channel.
C
And
recently
we
started
using
the
new
discussion
feature
of
github
and
what
we've
done
is:
we've
changed
the
header
in
the
slack
channels,
and
we
put
messages
in
the
mailing
list
to
say
that
if
you're
looking
for
help
or
connecting
with
users
using
opd
the
place
to
start
is
the
discussion,
if
you're
having
problems
and
you're,
not
sure
whether
it's
actually
a
bug
start
with
a
discussion.
If
you
have
identified
a
bug
that
is
repeatable
raise
an
issue,
so
we
try
to
give
that
advice
and
that
is
actually
in
the
the
community
documentation.
C
A
And
one
of
the
things
was
okay:
do
we
start
shifting
to
the
discussion
section
on
okd.io
as
opposed
to
the
okd
repo,
and
the
idea
was
well
if
we're
going
to
be
using
the
new
repo
sometime
in
the
next
couple
weeks,
it
doesn't
make
sense
to
to
spread
things
out
across
that,
so
we
would
ideally,
when
the
new
repo
is
populated,
start
managing
conversations
and
directing
people
to
the
discussions
there.
A
One
thing
I
don't
know
if
folks
noticed
this
or
not,
but
vadim
actually
left
the
dev
channel
the
other
day
in
frustration,
because
people
have
been
asking
user
questions
there
and
there's
not
really
any
dev
discussion.
So
one
thing
we
might
ask
ourselves-
and
this
will
be
discussed
at
the
at
the
documentation
subgroup
is:
are
we
actually
utilizing
the
dev
slack
channel?
A
Does
it
confuse
things?
Does
it?
Is
it
helpful,
as
we
start
doing
more
developments,
ideally
as
things
align
with
upstream
downstream
and
there's
more
community
contributions
like?
Will
we
use
that
or
do
we
anticipate
that
that's
just
going
to
be
an
empty
channel
from
from
now
on?
Do
folks
have
anything
they
want
to
chime
in
on
it?
That
we
can
take
back
to
the
documents
group.
H
H
B
I
If
we
were
going
to
have
a
thing
that,
where
developer
ish
type
stuff
were
happening,
probably
it
would
wind
up
being
I,
I
would
probably
put
forth
that
we'd
do
a
matrix
room
and
then,
if
we
wanted
to
have
it
like
also
accessible
as
a
touch
point
in
the
kubernetes
slack
being
able
to
bridge
it
there,
but
like
the
vast
majority
of
the
people
that
in
here
that
are
doing
stuff
like
myself,
timothy
and
others
like
we
just
don't
use
slack
for
that
at
all.
I
Like
I,
mostly
I
mostly
look
in
matrix,
and
I
barely
look
at
the
kubernetes
slack
to
begin
with,
or
the
openshift
common
slack,
even
less
so
like
I
mostly
am
living
in
matrix
talking
to
the
other
developers
in
matrix
rooms
over
there,
and
it's
just
the
gravitation
for
the
developers
is
just
not
in
slack.
D
Yeah,
neither
do
I
so
sorry.
It's
basically.
A
Yeah
and
it's
bridged
actually
fedora
actually
has
a
bridge,
but
there
were
some
issues
a
couple
of
weeks
ago
with
slowness
in
the
bridging.
I
don't
know
if
that's
been
resolved
or
not
seems.
A
I
The
the
servers
are
maintained
by
element
matrix
services
and
we
have
a
support
agreement
with
them
and
they're.
They
basically
prioritize
whenever
we
say
something
is
wrong,
they
go
and
they
go
whack
it
with
a
hammer
and
go
fix.
It
diane
do.
D
D
Yeah
that
that
I
hear
you
and
openshift
user
is
where
the
team
would
like
us
to
have
point
people
to
if
we're
gonna
at
the
moment.
If,
unless
we
set
up
something
else,
so
that
okd
users
and
openshift
users
go
there
and
ask
questions,
I'm
just
trying
to
figure
out
what
vadim's
preference
is.
Was
it
just
get
everybody
in
users,
because
what
what
is
vadim's
expectation
that
openshift
dev
would
be
is
kind
of.
My
question
is:
what
should
that
thought.
K
D
A
The
issue
is
so
I
can
him,
and
I
actually
had
a
conversation
about
this
when
he
left,
because
I
mes
I
was
like
what
are
you
leaving
for
like
what's
going
on
and
basically
he
was
like.
It's
useless
people
keep
repeating
questions
from
the
user
channel,
which
is
true
and
he's
thinking
that
we
should
just
use
users
dash
users
instead
and
then
like
for
short-lived
personal
chats.
A
You
know
for
particular
problems
or
something
like
that.
He
thinks.
Slack
is
only
good
when
it
comes
to
community
options
really
right.
So.
D
In
my
humble
opinion,
to
maintain
a
presence
in
the
kubernetes
slack
just
for
visibility
of
okd
as
one
of
the
many
just
you
know,
distributions
of
of
of
kubernetes
from
a
optics
perspective,
I'm
totally
cool
with
combining
the
two
of
them
into
one.
You
know
just
call
or
maybe
just
call
openshift
just
have
one
called
open
shift
period
rather
than
users
and
dev
and
and
and
we
can
make
that
request
of
the
kubernetes
folks.
D
I
know
commons
isn't
used
very
much,
but
if,
if
at
some
point,
there's
no
real
reason
to
make
something
up
in
openshift
commons,
like
an
okd
channel,
there's
some
okd
rooms
there
and
chats
that
happen
every
once
in
a
while
and
I
get
pinged
and
I
send
them
over
to
openshift
user
in
the
kubernetes
slack.
If
it's
technical
and
beyond
me,
so
I
think
the
very
first
step
that
we
probably
should
be
doing
is
is
rectifying
the
the
duplication
issue.
D
That
vadim
is
frustrated
with,
I
don't
know
matrix,
I
know
discord
and
not
that
people
want
another
thing
to
log
into.
I
certainly
don't,
but
if
we
wanted
to
set
up
some
sort
of
whatever
this
matrix
thing
is
matrix,
four
is
terrible:
don't
go!
Watch
it!
It's
just
stream
at
home
and
watch
it
with
popcorn
that
you
don't
have
to
pay
10
bucks
for,
but
if
this
matrix
thing
is
is
better
than
matrix
4,
then
you
know
and
it's
what
the
community
wants.
D
We
could
probably
set
up
a
matrix
server
for
ourselves
to
use
yeah,
so
you
know-
and
I'm
happy
to
do
you
know
something
like
that,
especially
if
it
bridges
to
everything.
I
think
that
that
might
be
a
solution
for
us,
but
I
do
think
we
need
that
public
space
in
kubernetes
and
even
if
in
the
header
for
the
openshift
combined
kubernetes
slack,
we
have
a
pointer
to
the
matrix.
D
That's
going
to
blow
my
mind
here,
I
think
keep
saying
that
to
or
to
discord
that
would
that
would
be.
I
think,
the
solution
for
that
to
for
me
for
watching
it.
You
know
this
duplication
is
is
terrible
for
me,
I'm
I'm
in
like
20
different
slack
things.
So
I'm
you
know
if
you
wonder
why
I
can't
find
g
d3's
thread
on
the
username
password.
That's
because
I
can't
find
which
one
she
gave
it
to
me
in.
So
I
would
say.
The
first
thing
is
to
go
ahead.
F
I
I
I
would
agree
with
that
entirely.
I
I
don't
think
we
want
to
lose
the
kubernetes
slack
altogether,
because
just
there's
an
audience
there
and
people
might
find
it,
and
even
though
it's
not
very
active
and
I'm
certainly
not
looking
there
every
day.
I
think
it's
good
to
have
that
presence.
F
Matrix
is
somewhat
of
an
spiritual
successor
to
irc.
Maybe
it's
a
federated
thing.
Fedora
has
an
instance.
We
now
have
an
internal
red
hat
instance
in
on
the
vpn
as
well,
and
that
is
certainly
used
a
lot
by
the
fedora
community.
F
So
I'm
already
on
there-
and
I
know
other
people
like
neil
and
timothy
are
as
well.
So
I
think
that
might
also
make
sense.
Obviously
it's
it's
another
another
channel
on
top
of
what
we
already
have
and
if
we
want
to
reduce
things,
but
I
do
think
that
makes
sense
as
a
presence,
because
that's
only
going
to
grow
in
the
future,
the
usage
of
matrix
so
yeah
and
having
just
one
channel
it's
all.
F
It's
mostly
gonna,
be
user
usage,
related
questions,
anyways,
and
if
we
need
space
to
discuss
some
development
in
the
future,
then
it's
definitely
easier
to
just
create
a
a
matrix
channel.
For
that
we
could
ask
fedora
to
host
us
there.
I
think
I
think
that's
a
good
idea
and
you
can
actually
join
the
fedora
hosted
matrix
channel
with
with
the
matrix.
F
Have
anywhere
so.
A
I
A
D
D
But
the
the
only
thing
that
I
think
it
might
be.
I
agree
with
totally
with
that
statement,
but
I
also
think
there
are
a
lot
of
customers
who
go
to
that
from
looking,
and
so
it
might
be
that
we
just
need
to
get
the
redirect
statement
or
whatever
it
is
at
the
top
of
the
box
description
to
point
to
like
if
you're
looking
for
okd
conversations
go
to
the
matrix
god.
D
I'm
gonna
love,
saying
that
and
if
you're
looking
for
open
shift
go
to
the
red
hat,
open
shift,
support
line
because
I
think
there's
there
is
occasionally.
There
are
open
shift,
people,
engineers
and
folks
who
go
there
and
peek
and
look,
and
especially
during
conferences
and
events.
People
tend
to
to
hang
out
there
more
so
yeah.
But
I
I
like
having
okd
visible
so.
A
Yeah-
and
one
thing
we
might
want
to
do
is
talk
to
chris
short,
so
chris
short
has
been
someone.
Who's
been
contributing
a
lot
in
the
dash
users
on
the
kubernetes
slack
and
see
if
we
can
get
him
to
join
the
new
matrix
because
he's
an
incredibly
helpful
person
and
and
he's.
A
Oh
sorry,
I
said
chris
short,
what
I
meant
was
my
brain
is
not
chris
short.
Andrew.
Sorry
andrew
is
someone
who's
really
helpful.
Andrew
andrew
block,
no.
A
What's
his
last
name
mike,
I
forget
there
are
a
lot
of
andrew.
A
Sullivan,
it
would
be
good
to
let
him
know,
he's
really
helpful
and,
and
actually
chris
short
did
leave.
I
saw
the
openshift
channels
on
kubernetes,
as
he
was
transitioning.
D
We're
sad
but
he's
still
around
and
if
you
go
to
kubernetes
contributor,
sig
stuff
he's
in
that
all
those
channels
very
active
instead.
So
he
said.
A
And
I
work
with
him
in
the
open,
get-ups
stuff,
actually
he's
a
participant.
D
So
so
the
one
ask
I
have
of
neil,
I
put
it
in
the
chat,
is
if
you
get
that
room
at
fedoras,
if
you
could
do
a
little
write-up
blurb
for
us
sure
how
to
you
know
how
to
get
a
matrix
account
from
fedora
and
what
the
general
name
is
and
maybe
give
it
to
the
docs
group.
So
we
can
put
it
someplace
front
and
center
absolutely.
A
Okay.
The
next
item
is
operators,
community
operators
and
whatnot
brian.
C
Yeah
so
yeah
I
mean
we,
we
had
this
conversation
a
little
bit
in
the
documentation
group,
but
I
think
it
belongs
here.
It's
really
is
there
anything
that
we
can
do.
I
know
that
jamie
you're
going
to
talk
to
the
the
red
hat.
Is
it
offering
managers
or
product
managers
to
see
if
they
can
actually
create
community
supported
versions
and
put
them
somewhere,
that's
accessible,
but
I'm
just
thinking
is
there
anything
that
we
can
do
or
anybody
would
be
interested
in
saying?
C
Can
we
get
these
operators
running
because
I
know
there's
quite
a
few
of
us
that
are
looking
for
some
of
the
red
hat
operators
to
actually
make
okay
the
development
platform,
things
like
serverless,
githubs
pipelines
and
taking
the
upstream
isn't
trivial
and
we
we
run
into
security
context
things
they're,
not
in
the
operator
hub.
They
don't
behave
the
same
way
as
they
do
on
openshift.
C
So
getting
that
nice
usability.
Even
if
it's
documentation.
How
do
I
build
my
own
operator
hub
catalog
with
the
pipeline
name,
or
is
this
something
we
can
actually
release
as
a
community?
I
mean
we
say
we
don't
do
any
development
in
this
group.
Maybe
we
could,
even
if
it's
temporary,
so
just
open
up
the
discussion,
because
this
has
been
around
for
ever
since
I
joined
the
community
and
it
don't
seem
to
have
gotten
anywhere
so
so
we
did
get
a
little.
A
Play
I
I
did
have
a
conversation
with
christian
hernandez,
so
christian
hernandez
is
the
the
product
manager,
for
I
forget
what
it
is,
but
he's
basically
for
the
get
ops
operator.
A
Apparently
it
falls
under
simek
said
you
see
that
right
right,
so
that
would
be
the
person
to
get
the
get
ops
operator
into
the
community.
It
does
christian
says
it
does.
Install
christian
hernandez
says
it
does
install
on
okd,
but
he's
like.
Are
you
looking
to
get
it
into
the
community
catalog
and
it's
like
yeah?
That's
really.
Ultimately,
what
we're
looking
for
is
not
just
getting
it
so
that
it
installs,
but
getting
it
listed
in
the
community
catalog.
So
there's
someone
that
we
can
approach.
A
I
mean,
don't
go
mob
this
person,
but
you
know
it's
someone
that
we
can.
We
can
send
someone
forward
to
go
and
initiate
a
conversation
on
at
least
a
good
ops
operator.
D
We
could
and
see
cmak
at
the
moment
is
he's
he
he
migrated
to
toronto
and
then
during
covet
migrated
back
to
sweden
just
because
he
they
had
a
baby
in
anyways
long
story,
but
he's
definitely
open
to
having
that
conversation,
and
so
we
could
have
a
side,
conversation,
jamie
and
maybe
brian
and
christian
lumbeck
or
whoever
is
the
appropriate
person
on
the
tech
side
about
that
issue.
Again,
if,
if
he's
and
I'd
be
open
to
brokering
that
call
easily,
it
would
be
nice
to
have
some
movement
on
that.
A
D
Operators
and
austin
mcdonald
is
the
community
lead
for
the
operator
framework,
which
is
now
a
cncf
project
and
he's
a
red
hatter
and
he's
keen
to
do
whatever
we,
you
know
whatever
he
can
to
raise
visibility
so
and
get
more
usage
and
feedback,
so
he's
another
person
that
we
could
do
so
if
we
wanted
to
kick
off
a
discussion
thread
on
that,
and
I
we
could
maybe
just
tag
a
few
of
them
and
pull
them
into
a
special
meeting
of
the
working
group
on
operators
that
might
be
a
way
to
move.
G
Yeah,
could
I
comment
too
the
okay?
So
so
I
guess
I've
been,
you
know,
running
a
version
of
okd
with
you
know,
students
as
guinea
pigs,
for
you
know,
since
the
I
guess,
the
the
late
pre-release
versions
so
like
4.4,
I
think,
and
I'm
currently
running
4.9
and
the
biggest
benefit
in
that
shift
is
that
in
the
apology
view,
the
positioning
of
the
little
bubbles
is
sticky.
G
Okay-
and
I
I
guess
in
the
counterbalancing
that
is
that
you
can
no
longer
delete
pods
from
the
console.
You
have
to
do
it
from
the
command
line.
So
the.
G
I
don't
see
operationally
a
whole
lot
of
benefit
from
what
we're
spending
all
of
our
time
on
and
the
things
that
are
being
mainly
flogged
in
the
sales
channels,
which
is
you
know
all
these
operators.
That
brian
mentioned
we've
been
talking
about
it
for
20
months
and
there's
been
zero
movement
so
like
I
think
that
actually
getting
treating
those
some
of
the
main
operators
as
part
of
okd.
G
So
in
a
way
I'm
just
sort
of
piling
on
brian's
comment,
but
it's
been
a
long
time
and
there's
been
zero
movement.
D
G
Of
those
operators
don't
use
the
operator
framework
group.
Like
last,
I
looked
at
the
tecton
pipelines
thing.
It
was
using
an
older
version
and
I
haven't
looked
recently
okay,
so
they
might
have
changed,
but
it
wasn't
using
the
latest
version,
and
so
when
I
tried
to
build
it
with
the
latest
version,
it
was
going
to
be
a
lot
of
work,
so
it
seemed
you
know.
I
mean,
like
the
operator
framework
group
is
sort
of
independently
moving,
and
so
existing
operators
aren't
necessarily
going
to
convert.
G
M
One
one
issue
is
like
the
work
that
needs
to
be
done
to
release
want
something:
that's
currently
only
on
the
red
hat
olm
and
put
it
into
like
operatorhub.io,
so
that
everyone-
that's
one
part
of
it,
but
then
the
second
part
of
it,
too,
is
like
the
continued
maintenance
of
keeping
the
operator
hub.io
thing
up
to
date,
and
I
think
this
is
probably
where
things
you
know
where
we
get
into
friction
with
red
hat
internal
teams
is
that
you
know
someone
unless
there's
an
engineer
inside
red
hat,
who
is
excited
and
motivated
to
keep
those
things
up
to
date
for
the
so-called
community
versions,
because
we
deal
with
this
in
the
components
I
work
with
a
lot
too,
unless
someone
is
really
watching
out
for
that,
it's
very
easy
for
those
pieces
to
like
slip
away
under
the
mountain
of,
like
you
know,
jira
cards
and
bugzillas.
M
We
have
and
I'm
kind
of
curious
if
there's
a
way
that
you
know
like,
I
would
love.
What
I
think
would
be
awesome
to
see
would
be
like
people
from
the
okd
community
being
able
to
propose
a
patch
that
says:
okay,
we
want
this
operator
in
operatorhub.io
and
we're
willing
to
maintain
whatever
artifact.
We
need
to
put
in
your
repo
to
keep
that
up
to
date,
because
I
think
that's
ultimately
the
best
way
to
solve
this,
and
I
have
a
feeling
that
it's
just
a
matter
of
getting
in
touch
with.
M
Let's
just
take
the
get
ops
operator,
for
example
like
getting
in
touch
with
that,
get
ops
team
figuring
out
what
they
want
to
see
proposed
to
their
repo
to
make
it
be
able
to
be
pulled
into
operatorhub.io,
and
if
someone
from
the
community
shows
up
and
does
that-
that's
probably
like
our
best
pathway
to
getting
these
things
also
in
operator
hub.
So
I
mean
that's
just
my
two
cents.
G
Well,
I
just
wanted
to
comment.
One
short,
one
jamix
that
in
going
to
from
4749
55
operators
disappeared.
D
I
think
in
general
operator,
hub
io
needs
more
love
so,
and
I
put
the
pm
who
owns
it,
because
that
focus
has
been
on
the
the
customers
and
the
marketplaces
and
certified
operators,
and
all
of
that
things
that
people
pay
money
for
an
operator
hub
dot.
Io
doesn't
get
a
lot
of
love.
D
So
you
know
maybe
using
the
get
ops
operator
to
start
up
a
conversation,
but
also
to
to
pull
in
daniel
messier,
who
owns
operator
hub
under
his
his
domain
of
things
that
he
pms,
amongst
other
things,
might
be
the
the
way
to
go
with
daniel
and
and
pull
cmak
in
as
well.
To
get
that
and
just
have
one
meeting,
and
so
I
I
threw
his
email
and
address
in
there
and
maybe
jamie,
and
we
can
kick
something
off
a
thread
there
about.
How
do
we
get
this
moving.
A
Yeah,
I
will,
since
I
already
started,
also
the
conversation
on
the
other
side
with
with
the
get
ops
one,
so
we'll
sort
of
collect
them
all
together.
Or
do
you
want
to
divvy
these
up?
It's
up
to
you?
Well,
let's
talk
offline,
we'll
figure
it
out
yeah
yeah
and
figure
out
who's
going
to
do
one.
Okay,
let's
keep
moving,
because
I
do
want
to
go
through
the
we
go
you're
up
next.
M
M
Our
team
has
been
for
a
long
time,
had
requests
and
been
thinking
about
how
to
add
machines
of
the
control
plane
into
some
sort
of
machine
set
of
their
own,
and
this
would
be
like
a
big
kind
of
topology
change
for
openshift,
but
what
we've
come
up
with,
because
there
are
a
lot
of
special
needs
for
those
control
plane
machines.
What
we've
come
up
with
is
a
proposal
to
create
a
new
type
of
custom
resource
called
the
control
plane
set.
M
That
is
in
some
ways
akin
to
a
stateful
set,
but
for
the
machines
of
a
control
plane-
and
you
know,
we've
created
an
enhancement
to
describe
what
we're
doing
and
during
our
team
discussions
today
you
know
we
thought
it
would
be
cool
to
reach
out
to
the
okd
community
as
another
source
of
kind
of
expertise
in
this
area.
Just
to
see,
if
maybe
people
would
review
the
enhancement.
You
know
if
anybody
had
comments.
M
That'd
be
awesome
to
see
as
well,
and
you
know
just
to
try
to
help
build
this
bridge
between
the
development
of
ocean
shift,
that's
happening
and
the
community
that
we
have
growing
as
well.
So
really,
I
just
wanted
to
kind
of
bring
it
here
for
to
share
the
link,
and
if
anybody
has
questions
or
wants
to
discuss
stuff,
I'm
you
know
happy
to
answer.
A
All
right
seems
like
folks,
are
sort
of
quiet
about
that.
So,
if
you
have
any
further
comments
or
questions,
please
feel
free
to
reach
out
to
him
and
for
more
info
and
we'll
track.
You
know
the
progress
of
things
as
time
goes
on
and
have
conversations
about
this
moving
forward.
These
types
of
changes
all
right
next
up
task
list
going
through
the
the
tax
task
list,
doc's
group,
to
create
a
surgery.
I
do
have
a
security
posting
ready
to
go
now
that
the
holidays
are
over.
A
I
can
post
it.
Basically,
we
want
to
find
someone
that
can
sort
of
keep
an
eye
on
secure
security,
stuff
and
sort
of
be
a
liaison
for
okd,
so
keeping
track
of
those
things.
So
I've
got
a
little
posting
that
I'll
put
out
as
a
discussion
and
also
in
the
working
group
for
the
people
that
happen
to
be
in
the
working
group.
Currently
that
are
interested
might
be
interested
charo.
You
had
something
for
download
stats.
Any
update
on
that.
A
Daniel
is
daniel
in
the
chat
or
in
the
meeting
at
all,
seen
him
since
I
think
the
holidays
so
we'll
reach
out
to
him.
I
think
he
got
everything
he
needed.
Brian,
clean
up
of
okay,
revo's
and
old
guides.
C
And
that's
something
I
gotta
do
I'll
have
to
do
a
pull
request.
I
don't
have
right
permissions
within
repo,
so
someone
will
also
have
to
accept
the
pull
request
to
actually
do
that,
but
also
that
feeds
into
a
conversation
that
we're
going
to
do
with
with
vadim
in
terms
of
what
content
needs
to
be
moved
out
of
that
into
elsewhere,
or
vice
versa.
C
A
Yeah
so
diane
research
transfer
of
github,
okd
repo
to
the
working
group,
and
you
said
that
that's
sort
of
been
a
dead
end.
Should
we
take
that
off
the
task
list
or
yeah.
D
We
should
just
change
the
tax
to
move
the
repo
from
once
you've
had
the
conversation
with
vadim
move
the
the
salient
things
into
the
okd
projects,
repo
or
reboot-
that
so
you
can.
You
can
say
we
we
tried.
We
did
our
best
effort
to
get
people
to
respond
to
us,
but
didn't
happen
so,
but
I
think
the
new
task
is
review
with,
as
you
are
doing,
with
vadim
what
should
be
in
there
and
then
use
the
one
that
we
reserved
and
move
it
forward.
D
A
A
Brian,
there
was
some
overt
stuff.
What
was
that
related
to.
N
A
Neil
did
his
task
already,
which
is
fantastic
upcoming
events.
Let's
see
here
sandra
you're
still
here
sandra.
Do
you
want
to
comment
a
little
bit
on
fostem.
E
Yeah
we
got
accepted,
presenting
the
okd
virtualization
initiative
and
showing
how
to
install
and
use
okd
virtualization.
There
recording
have
been
done
and
submitted.
So
we
are
ready
to
go.
D
D
I
added
a
couple
of
things
in
there
as
well.
We
just
paused
them
there.
Jamie
is
very
nicely
going
to
be
speaking
at
an
openshift
commons
gathering
on
git
ops
on
february
9th,
and
then
we
have
two
things
coming
up
sooner
than
later
next
week
at
devconf
movie
and
there's
a
third
one
that
I
just
noticed
when
I
searched
there
on
courier
cni
in
octavia,
I
think
that's
one
of
your
cohorts,
sandra
sandro,
rohit,
sorry,
is
that
somebody
that
that
you
know
aware
of.
D
I
thought
he
was
no,
maybe
he's
an
openstack
person.
Let
me
just
see,
but
I
had
an
courier
and
octavia
to
manage.
Okd
services
is
the
thing
it's
a
plug-in
that
uses
it's
an
open
stacking
thing,
but
they're
using
okd
clusters
to
do
it.
Just
an
interesting
thing.
M
A
Yep
all
right
any
last
minute
things
before
we
end
the
meeting.
A
All
right
folks,
well,
let's
hope,
for
a
successful
and
safe
and
happy
2022.