►
From YouTube: OKD Working Group Meeting 01-31-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
Welcome
to
the
okd
working
group
meeting
for
January
31st
of
2023,
and
we
have
the
agenda
before
us.
If
folks
could
take
a
quick
look
at
it,
and
let
me
know
if
there's
anything
that
you
want
to
change
or
modify
before
we
get
started
and
then
for
the
meeting
at
various
times
of
the
meeting,
we'll
put
the
agenda
up
as
well,
so
that
folks
can
see
it.
B
And
then,
if
we
are
having
a
conversation
like
with
our
guests,
then
we'll
hide
the
agenda
and
focus
on
the
guest
and
I
see
Christian
is
here
so
all
right.
Any
changes
to
the
agenda
as
it's
written
anything
you
want
to
add,
remove,
move
around.
B
All
right
we're
good
to
go.
So,
let's
start
out
with
our
guest,
could
you
go
ahead
and
introduce
yourself
and
tell
tell
us
a
little
bit
about
yourself
and
then
we'll
go
from
there.
C
Well,
I'm
excited
that
I
know
half
of
you.
So
that's
nice!
C
Oh
it's
good
to
see
you
all
Karina,
Angel
I
think
probably
no
Christian
the
longest
okay,
so
I
have
been
at
Red
Hat
since
2019
and
I
kind
of
have
been
involved
in
almost
everything
it
feels
like
so
I've
been
on
the
openshift
PM
team.
For
about
three
and
a
half
years
now,
I
have
covered
Cloud
packs,
which
broadly
means
that
I
touch
kind
of
all
across
the
different
areas
of
red
hat.
C
But
I
am
here
because
I
am
taking
over
openshift
comments
from
Diane
and
we're
all
so
so
sad
that
Diane
is
I,
know
and
there's
no
way.
I
can
ever
fill
Diane's
shoes,
so
you
know
it'll
be
different,
but
at
least
expectations
I,
don't
know,
tell
me
what
you
want
and
I
can
help,
but
unfortunately
I'm
not
Diane
and
every
open
shift
Commons.
We
will
have
space
for
an
okd
talk.
C
I
want
to
continue.
The
you
know
have
space
for
working
groups.
You
know,
there's
always
support
for
you.
There
so
I
guess
that's
kind
of
a
very
brief
overview.
B
C
Thanks
Jamie
you're,
a
great
moderator,
all
right,
so
openshift
Commons,
it's
I,
think
of
it
as
a
gathering
place
where
you
know
customers
end
users
doesn't
have
to
be
a
customer
but
end
users,
Partners
Upstream.
We
all
come
together
and
talk
about
different
topics
through
different
channels
and
one
of
the
big
channels,
everybody
kind
of
knows
about,
or
we
have
the
open
shift,
Gatherings
that
are
usually
tied
to
a
kubecon
or
red
hat
Summit.
We
are
doing
Summit
this
year
or
other
events.
C
We
also
have
virtual
Gatherings
and
then
also
exploring
different,
just
different
ways
that
we
can
also
Drive
value
to
the
whole
community,
and
this
year
I
would
like
to
highlight
that
Jack
is
speaking
at
Amsterdam.
C
B
D
Right,
just
a
very
quick
note
in,
in
addition
to
the
openshift
comments,
we'll
probably
also
be
more
active
at
the
Centos
connect
events
going
forward,
which
is
it
used
to
be
called
Centos,
dojos
and
I'm,
not
sure
how
much
yukarina
are
involved
in
planning
those.
But
since
we
have
kind
of
joined
the
Centos
Cloud
special
interest
group
with
the
Centaur
stream
koros
effort,
they
very
much
like
to
include
us
there,
because
the
the
Centos
Cloud
sync
was
our
activity.
D
There
was
was
decreasing
over
time
because
it
was
essentially
the
open
stack
Community,
which
is
now
slowly
yeah,
just
getting
less
and
less
traction
there
and
kind
of
as
a
replacement.
They
have
invited
us
to
join
the
Centos
Cloud
sick,
so
we
will
be
actually
at
the
centers
connect
event.
This
Friday
in
Brussels
before
first
Dem
and
then
on
Fall
stem
at
first
time,
I'll
be
at
the
centaurs
Booth
representing
okd.
There.
B
Fantastic,
hey,
Christian,
make
sure
you,
you
send
a
little
blurb
to
me
that
we
can
put
on
the
social
media
promoting
that
absolutely
yeah.
So
green,
could
you
maybe
let
us
know
some
of
the
best
ways
that
you
or
the
ways
in
which
you
envision
us
communicating
on.
B
You
know
collab
our
collaborative
projects
like
Commons
events
and
things
like
that.
What's
the
best
way
to
work
with
you
to
to
reach
our
shared
goals,.
C
Well,
I
think
we
may
need
to
Define
what
our
shared
goals
are,
then
sure
so
I
mean
you've
worked
with
Diane
long
enough,
so
my
goal
would
be
to
Foster
more
collaboration,
which
you're
already
doing
saying,
driving
more
capturing
more
stories
of
innovation
as
well,
which
you
know
Diane,
would
also
help
with
and
so
Jack
speaking
at
kubecon.
The
Commons
at
kubecon
is
one
of
those.
So
I
would
like
to
understand
how
I
can
capture
more
of
those
stories.
C
What
are
more
things
you're
doing
in
okd
to
innovate,
the
more
I
know
about
what
you're
all
doing
and
different
directions
or
areas
that
you're
looking
at
you
know,
innovating.
C
The
better
I
can
help
evangelize
that
or
find
ways
to
anyway
new
channels
that
we
can
use
openshift
Commons.
That
doesn't
quite
answer
your
question,
though,
because
I.
B
Don't
know
it
it
does,
though
it
sets
the
stage
for
it
right,
and
so
one
of
the
things
that
we
need
that
comes
out
of
that
is
that
we
need
to
and
I'll
bring
this
up
at
the
at
the
community
development
meeting
next
week
is
reach
out
to
gather
user
stories.
We
haven't
actually
done
that
we
haven't
actually
reached
out
via
our
social
media
channels
or
anything
or
the
slack
and
said
hey.
Do
you
have
a
good?
What
are
you
doing
with
okd?
B
Do
you
have
a
good
story
about
how
you're,
using
it
I
think
that
if
we
do
something
like
that,
then
we
can
get
something
to
you
right
yeah.
So,
given
that
and
given
what
it
is,
you
want
to
do
and
that's
sort
of
our
goals
as
well.
I
think
does
anyone
else
have
anything
they
want
to
add.
I,
don't
want
to
I'm
just
sort
of
riffing
here.
Does
anyone
else
want
to
add
what
we
feel
okd
wants
to
get
out
of
this
relationship.
E
Yeah
I
think
we
want
to
do
everything
we
can
to
grow
the
okd
working
group
in
the
community,
such
that
we
can
maybe
move
to
hosting
large
Events,
maybe
get
to
maybe
a
year
from
now
and
okay,
D
hackathon
or
something
you
know
or
you
know
something
where
okd
is
a
cool
thing
and
everybody
just
wants
to
be:
okay,
D
so
trying
to
change
the
world
like
that
foreign.
D
Since
you
Since
you're
speaking
right
now,
I
heard
from
Luigi
that
you
were
planning
on
on
doing
a
workshop,
possibly
on
I,
think
probably
focused
on
the
on
the
build
pipelines
that
we
have
created
with
a
tecton
and
I
I.
Think
that
would
be
one
one
thing.
One
example
of
things
we
we
love
to
do
more
I
think
is
just
like
workshops
and
really
showing
people
how
to
use
our
Tech
and
what
to
do
with
it
and
kind
of
exploring
possibilities.
D
In
a
workshop,
it's
just
even
more
I
think
it's
even
better
to
to
have
this
in-person
experience
in
a
workshop
than
just
reading
through
some
documentation
pages,
so
I
very
much
I
like
that
idea,
I
I
did
I
I,
think
Luigi
mentioned
it
I'm,
not
entirely
sure,
but
I
think
it
was
you
who
was
planning
that
Workshop
yeah.
E
I
just
got
I
just
got
it
from
family
accepted
and
so
I'll
be
sharing
those
details
with
you,
because
I
gotta
prep,
it's
all
right,
I'm
gonna
need
y'all
to
get
me
ready
because
I'm,
you
know
I'm
I'm
trying
to
work
on
a
glossary
so
that
I
have
some
definitions
to
roll
through
and-
and
just
you
know,
try
to
you
know
represent
okd
to
to
my
fullest
ability.
E
The
organizations
are
working
are
working
with
they
like
to
do
climate
change,
so
the
okd
Sno
would
be
a
great
solution
to
bring
some
data
in
into
the
network.
So
right
now
we're
trying
to
first
I
gotta.
Even
today,
I
was
talking
with
the
NSF
and
we
had
a
little
slight
little
discussion
about
kubernetes
and
I
was
like
because
we
was
he
was
talking.
He
was
saying.
Well,
this
grant
is
about
the
architecture
of
building
a
geospatial
platform.
E
I
was
like
well,
you
know
the
cyber
security
policy
states,
kubernetes
and
then
I
said:
okay,
D
is
old,
so
and
I
and
I
noticed
that
sometimes
I
gotta
slow
down
when
I'm
and
then
in
this
group
I
got
to
speed
up
and
I'm.
Like
oh
yeah,
it's
a
great
Paradox
and
I'm
like
it's
just
different
audiences
and
you
you
have
to
build
a
dual
skill
set,
sometimes
and
and
I'm
learning
to
to
learning
this
open
source.
Journey
Jack
go
ahead.
F
Okay,
the
users
are
kind
of
testing
the
boundaries
of
what
they
can
do
with
with
well
the
openshift
sources,
the
the
in
in
terms
of
the
source
code
and
maybe
also
using
some
features
for
which
it
was
not
originally
developed,
or
that
that
have
not
been
ironed
out
yet
and
are
encountering
some
things.
And
then
the
question
is
okay.
How
do
we
contribute
something
back
like
maybe
a
simple
bug
fix?
F
Maybe
documentation
updates,
maybe
even
a
small
feature,
and
because,
if
I'm
just
gonna
go
to
one
of
the
openshift
repositories
and
open
a
pull
request
there
with
with
changes
that
I
think
the
in
most
of
the
cases,
the
chances
are
really
low
that
that's
gonna
even
get
reviewed,
much
less
so
actually
get
merged.
At
some
point
and
I
mean
that's
understandable.
Of
course,
the
the
open
source
Community
is
not
the
the
the
the
product
line.
F
Those
are
not
the
end,
end
users
from
from
the
red
hat
perspective,
but
still
it
would
be
nice
if
we
can
kind
of
get
this
channel
so
that
we
are
not
just
using
the
software,
but
we
can
also
contribute
something
back
because
I
think
now,
then
we
actually
come
across
some
things
that
could
need
some
ironing
out
or
documentation,
updates
and
yeah
in
in
that
direction.
I
would
like
to
see
some
Community
Development.
B
Okay,
so
so
tying
this
back
to
Karina's
efforts,
it
sounds
like
really.
We
want
opportunities
to
be
able
to
do
workshops
at
events
and
opportunities
to
give
talks
and
to
let
members
of
the
okd
community
present.
You
know
Innovative
things
that
they're
doing
and
to
present
examples
of
people
who
have
done
interesting
stuff
with
okd
and
have
contributed
back,
highlight
that
they've
contributed
back
so
any
opportunities
that
we
have
within
events
and
within
the
the
commons
Community
to
highlight
that
type
of
stuff
it
sounds
like
would
be
what
we're
looking
for.
G
Yeah
thanks
I
I
would
like
to
sort
of
second
the
idea
of
hackathons
and
in
particular,
a
branch
of
them
that
would
be
suitable
for
students.
G
No,
because
you
know
I
I've
got
about
the
you
know:
25
students
coming
out
every
year
that
have
used
okd
to
deploy
their
labs
and
assignments,
and
things
like
that.
G
On
the
other
hand,
we
also
have,
in
our
sort
of
you,
know,
software
development
side-
another,
oh,
maybe
120,
students
that
have
gone
through
other
streams
and
haven't
actually
used
it.
But
you
know
some
of
them
are
in
Ai
and
a
variety
of
things
that
are
actually
quite
suitable
for
deployment
on
kubernetes
and
the
the
students
do
often
like
to
participate
in
hackathons.
G
Some
of
the
better
ones
and
it'd
be
I,
guess
not
only
figuring
out
what
your
problem
set
was,
but
also
adverts,
and
you
know
seeing
how
you
would
connect
with
sort
of
a
student
population.
D
Yeah
I
I
agree
to
all
of
what
was
just
said:
I
think
the
more
educational
things
we
can
do,
the
better,
and
there
might
be
that
just
came
to
my
mind.
D
We
have
we
have
this
effort
with
the
Massachusetts
open,
Cloud
going
on,
and
the
plan
there
is
essentially
for
for
us
internally
to
have
builds
that
we
can
immediately
test
by
spinning
up
a
cluster
on
the
Moc
on
the
Massachusetts
open
Cloud,
but
that
platform
is
obviously
an
educational
platform
and
we
are
then
making
going
to
make
that
open
to
the
public
so
that
anybody
will
be
able
to
spin
up
a
cluster
at
first.
D
This
is
going
to
be
ephemeral
clusters,
but
I
think
because
they
got
2000
service
donated
to
them.
I
will
definitely
get
a
a
cluster
just
for
for
the
working
group
to
to
manage
ourselves
and
so
moving
that
kind
of
off
of
the
operate.
D
First
Cloud,
where
we've
been
building
the
s-cos,
which
is
also
hosted
on
Moc
by
the
way,
but
we'll
just
get
our
own
cluster
and
we'll
be
tasked
to
to
maintain
and
manage
that
ourselves
and
I
think
we'll
be
able
to
use
that
as
a
tool
for
for
learning
learning
and
teaching
SRE,
as
well
as
from
there
spinning
up
more
clusters
on
that
free
Hardware
that
we
essentially
given
for
free
and
will
be
able
to
use
without
any
costs,
and
that
is
bound
to
educational
purposes.
D
So,
I
think,
once
we
have
that
story
with
the
Moc
right
now,
they're
still
working
on
on
the
API,
that
that
is
bare
metal
deployments
using
essentially
an
openstack
API.
So
once
that
is
all
set
up,
we'll
we'll
make
that
open,
obviously
to
not
only
the
working
group.
But
anybody
really
who
wants
to
test
clusters
or
do
anything
really
so
leveraging.
The
Moc
I
think
will
be
a
good
opportunity
if
we
wanted
to
do
workshops
and
and
even
hackathons
testing
out
changes
right
away.
D
Deploying
a
new
cluster
with
the
change
that'll
be
possible
on
Moc
and
it'll,
be
free
of
cost
to
us.
So
I.
Just
wanted
to
reiterate
that
we
should
and
I
love
to
focus
on
education
and
experimentation
here
so
yeah.
That's
definitely
one
thing
to
keep
in
mind
that
we
have,
or
we
will
have
those
resources
in
the
in
the
short
term
available
to
us.
E
D
I
I
think
we'll
we'll
probably
kind
of
have
to
talk
to
the
Moc
folks
directly
for
for
things
outside
of
of
our
very
specific
use
case
of
spinning
up
ephemeral
clusters
to
run
conformance
tests.
If
you,
for
example,
want
a
persistent
cluster
for
longer,
you'll
you'll
probably
have
to
talk
to
them,
but
since
they
have
these
2000
servers,
okd
will
only
be
one
tenant
of
in
in
the
of
in
on
those
in
on
that
infrastructure.
D
So
there
will
be
the
opportunity
to
to
get
some
to
get
a
piece
of
those
resources,
even
outside
of
of
the
working
group
or
or
inside
the
working
group
in
another
kind
of
effort
than
than
our
bare
metal
testing
there.
D
So
definitely
I'm
I'm
I
think
we
should
probably
invite
the
Massachusetts
open
Cloud
folks,
which
is
also
it's
a
multiple
Unis
I,
think
MIT
yeah
I
have
it
maybe
there's
a
couple
of
of
Unis
that
that
are
kind
of
yeah
in
in
that
group
and
I'd
love
to
invite
them
here
once
we
have
that
kind
of
setup
for
them
to
to
get
to
know
us
and
for
us
to
get
to
know
them
and
how
to
reach
them
with
requests
like
this.
B
Excellent,
so
one
thing
I
want
to
do
is
make
sure
that
we
have
a
a
process
down
for
the
working
group
being
aware
of
all
of
the
opportunities
that
we
have
to
participate
in
outside
of
events
and
in
particular
with
Karina.
Here,
events
related
to
The
Commons
right.
So
you
know,
once
Karina
is
back
on
screen.
We
can
ask
about
that.
B
I
think
that
it
would
be
good
to
Define
sort
of
what
our
Communications
protocol
is
going
to
be
for
finding
out
about
about
events,
then
communicating
back
our
our
ability
to
participate
and,
and
what
not
just
to
have
a
clear
path
of
communication
and
sort
of
knowing
what's
happening,
and
what
our
opportunities
are.
B
One
thing
I
would
say
in
the
short
term
is:
if
you
you're,
participating
in
an
event.
Jack
sounds
like
you're
participating
event.
Christian
you've
got
an
event.
We
need
to
be
able
to
get
copy
out
over
our
social
media.
B
So
if
you
could
to
the
working
group
send
to
the
Google
group
or
message
myself
and
Brian
directly
like
blurbs,
that
you
would
like
posted
in
the
various
places,
that
would
be
good
because
we
want
to
get
these
things
attended
right
and
we
want
also
to
sort
of
highlight
that
we
are
participating
in
these
events.
You
know,
regardless
of
of
attendance
and
and
whatnot
so
Karina.
What
is
the
best
way
to
for
you
to?
B
Let
us
know
about
events
and
for
us
to
then
respond
to
you
about
that,
so
that
it's
a
group
process
we've
had
and
there's
not
a
criticism
in
any
way,
but
Diane
would
sort
of
go
off
and
do
her
own
thing
and
work
with
people
directly
and
then
sometimes
that
would
get
to
the
group
after
the
fact
I'd
like
to
sort
of
change
that
Dynamic
a
little
bit
so
that
opportunities
are
presented
to
the
group.
B
You
know
from
you,
you
know
from
you
to
the
the
co-chairs
and
then
co-chairs
to
the
group,
and
then
we
work
to
get
a
response
back
to
you.
So
I'd
like
that
to
be
like
an
inclusive
process.
So,
what's
the
best
way
to
do
that
with
you.
C
Minute
is
when
the
dogs
barking
to
be
let
back
in
but
go
right
ahead.
C
Well,
first,
because
I
can
still
hear
you
when
I
let
him
in,
but
so
I'm
going
to
ask
you:
how
do
you
all
communicate?
What's
your
mailing
list
do
I?
Would
it
be
better
if
I'm
on
your
mailing
list
to
send
out
hey
this
event's
coming
up?
Think
about
it,
Etc
is.
Is
that
instead
of
me
creating
a
new
channel
of
communication,
should
we
just
be
using
yours.
B
Absolutely
so
we
have
a
Google
group
that
I
will
paste
the
details
of
which
into
the
channel,
and
that
is
the
a
Communication
channel
that
is,
for
the
most
part,
all
see
there.
We
go
so
yeah
and
there's
that's
the
slack
as
well.
B
Although
the
thing
about
the
slack
is
that
it
it's
mixed
with
ocp
stuff
and
everything
like
that,
but
the
Google
group
would
be
a
way
to
communicate
directly
with
people
participating
in
the
Google
group,
and
let
me
see
if
the,
if
I
have
the
link
directly
to
the
Google
to
the
sign
up
for
the
Google
group
here.
C
So
I
I
do
want
to
mention
a
couple
things
because
we're
talking
it
and
by
the
way,
I
actually
really
like
the
details
that
Christian
is
going
into
because
it
helps
me
think
about
different
ways
to
use
the
working
group.
C
So
we
on
the
openshift
commons
site
I'm,
just
thinking
tactically
through
some
things,
on
how
to
build
more
awareness
for
okd
and
I
was
looking
at
the
blog,
and
it's
awesome
on
the
okd
site,
saying
what's
going
on
I'm
wondering
if
I
can
pull
in
some
of
your
content
over
to
the
common
site
as
I
start
pulling
in
other
groups
into
that
blog
and
that
one's
also
anybody?
Well,
you
can
contribute
to
that
one
as
well,
so
I'm
thinking
some
integration
points
in
addition
to
the
events
it
doesn't
have
to
be.
C
You
know,
just
you
know,
talking
at
a
gathering
or
Etc
if
you're
thinking
through
once
you're
getting
use
cases
and
I
mean
just
things
that
come
to
mind.
I'd
love
to
see
a
a
blog
post
on
this
is,
and
you
probably
already
have
one
out
there
somewhere.
This
is
what
okd
is.
This
is
the
value
that
it
brings
to
people.
Are
you
know,
companies
that
you
know
aren't
ready
to
use
openshift?
This
is
from
you
know,
like
a
conversation
that
I
was
having
with
Jack
because
really
interesting,
diving
into
okay.
C
Well,
it
doesn't
do
x,
y
and
z,
but
maybe
in
the
future
openshift
will,
but
for
now
we're
gonna
stay
here.
So
stories
like
that
are
excellent,
I'm
thinking
through
some
of
those
things,
this
yokd
how
it
fits
into
the
overall
ecosystem.
You
know
why
you
know
thinking
through
what
a
good
blog
post
would
be,
but
that's
just
one
and
then
capturing
the
stories
do
any
of
you.
Anybody
else
ideas.
D
D
Obviously
the
Fedora
Community
then
now
with
Centaur
stream
chorus,
the
Centos
Community
there's
operate
first
dot
Cloud,
which
is
which
also
runs
on
the
Massachusetts
open
Cloud,
which
is
a
project
for
an
educational
project,
hosted
by
or
run
by
red
hat,
which
essentially
informs
a
best
practices
in
in
SRE
so
and
that
is
run
by
the
by
the
office
of
the
CTO
of
redhead,
and
that's
where
we
are
we're
currently
building
our
Central
stream,
core
OS
base
operating
system.
D
So
that
is
another
project,
and
this
new
Massachusetts
open,
Cloud
Moc
is
another
part
of
that
world
and
there
are
probably
a
couple
of
a
couple
of
more
projects
that
are
related
to
okd
in
some
way
and
that
we
could
kind
of
connect
with
even
more
and
more
kind
of
formalize
that
relationship
a
bit
more
because
it's
all
it's
all
very
loose
right
now
and
yeah.
It's
not
really
formalized
and
I'm.
Trying
to
find
that
overview
that
I
think
Michelle
creche
had
created
a
very
good
slide.
D
It
might
be-
or
maybe
it
might
just
be
good
to
to
recreate
that
slide,
I'm,
not
sure
whether
I
can
just
screenshot
it,
but
I'll
try
to
find
it
if.
D
I'll
just
type
down
the
list
of
projects
I
just
mentioned
excellent
El.
B
A
Yeah,
so
this
is
kind
of
going
back
to
a
topic
that
was
brought
up
before
and
I
think
you
know,
I
think.
A
lot
of
the
suggestions
that
are
coming
up
here
are
awesome
like
this
is
good
content,
but
I
think
something
that
we
and
you
know
Karina
and
Christian.
This
is
falling
more
on
our
shoulders.
A
Something
I
think
we
should
be
looking
at
too,
is
how
we
can
generate
blogs
and
content
that
go
into
the
okd
community
that
help
instruct
the
type
of
interactions
that
kind
of
Jack
was
talking
about
before,
where
it's
like.
How
would
a
user
of
okd
interface
with
you
know
creating
a
bug
for
openshift?
How
would
they
find
where
to
suggest
a
new
feature?
How
could
they
you
know?
A
How
could
they
work
with
openshift
engineering
to
propose
a
patch,
even
and
so
I
think
there's
been
a
lot
of
discussion
about
this
internally
and
openshift
Engineering,
especially
with
regard
to
like
partners
and
how
we
get
them
involved
in
looking
at
jira
and
whatnot,
but
I
think
there's
a
bigger
story
here,
which
is
like
for
the
okd
community.
How
do
we
start
to
instruct
them
about
like
hey
if
you
find
a
bug?
A
Here's
where
you
should
go
to
open
it
up
if
you
want
to
fix
something,
here's
how
to
get
into
jira
here's
how
to
like
take
ownership
of
a
card?
Here's
how
to
communicate
with
the
people
who
are
generating
these
cards.
You
know
I,
think
generating
some
of
that
content
would
be
really
instructional
for
the
okd
community.
E
Well,
I've
also
been
hanging
out
with
the
Enterprise
neuro
system
and
and
and
I've
been
talking
up,
okd
with
them
and
and
and
and
they
I'm
trying
to
get
them
to
be
our
customer
and
they
are
an
AI
climate
change
type
of
organization,
and
so
that
may
be
developing
pretty
soon.
They
and
I'm
Jamie
I'm
trying
to
send
you
this
link
but
I'm
it's
on
another
computer,
but
I'm
in
the
work
group
we'll
try
to
get
you
the
information
as
soon
as
possible.
E
With
that
I'll
send
it
to
your
slack
or
something:
okay,
fantastic.
B
All
right
I
want
to
make
sure
that
we
have
enough
time
for
the
rest
of
the
things
on
our
agenda.
Are
there
any
other
things
that
we
want
to
bring
to
Karina's
attention?
For
this
brief
little
meeting
here
before
we
move
on
to
our
next
topics,.
B
All
right:
well
thanks
so
much
for
showing
up
here
and
making
your
presence
known
to
the
group
and
looking
forward
to
working
with
you
and
now
that
you're
on
the
working
group
Google
group
mailing
list,
we
can
have
lots
of
communication
there
and
stuff
like
that.
Async
is
probably
the
best
for
you,
because
I
I
understand
you
have
a
conflict
with
this
meeting
regularly
is
that
is
that
right,
so.
B
C
B
D
So
I
have
I.
I
have
been
out
for
quite
a
bit
and
I
just
kind
of
came
back
last
week
after
yeah
since
beginning
of
December.
So
I
don't
have
a
an
update
on
on
Fedora
corewest
based
okd,
since
I
haven't
been
following
that
I
think
though,
but
he
has
created
a
new
release
recently
I
think
that
was
the
first
4.12
release
I'm.
Just
it.
D
Awesome
so
I'm
just
going
to
put
it
in
the
chat
again,
that's
that
release
I
have
yeah.
I
haven't
been
following
up
on
on
any
potential
issues
with
that
release.
I
do
think,
though,
that
one
issue
with
memory
leak
leakage
was
fixed.
G
D
If
I
remember
correctly
but
again,
not
entirely
sure
and
then
I
have
a
very
quick
update
on
okd
on
s-course,
which
is
hopefully
going
to
be
released
on
Thursday,
so
we
are
working
on
that
right
now.
B
All
right,
I,
pinged,
Dusty
and
Timothy.
Neither
him
nor
Timothy,
have
anything
in
terms
of
f
cost
updates.
B
Community
Development
updates
Brian
was
out
for
the
last
meeting
just
to
fill
folks
in
the
the
Mastodon
we've
decided
to
move
forward
with
and
omico
is
going
to
give
us
a
little
bit
of
guidance,
but
we're
going
to
Shadow
him
so
that
he
doesn't
do
all
the
work
on
just
getting
us
on
one
of
the
servers
and
we'll
try
it
out,
we'll
see
how
it
works
and
the
other
thing
is.
B
The
email
aliases
have
been
submitted
so
that
they
are
all
going
to
point
to
the
Google
email
address.
B
That's
been
used
to
set
up
the
Twitter
and
everything
like
that,
and
then
eventually
we
will
like
have
different
email
accounts
and
and
sort
of
you
know,
direct
specific
aliases
to
specific
email
accounts.
Yeah.
Let
me
go.
A
Oh
I'm,
just
going
to
follow
up
I,
do
still
have
on
my
whiteboard
to
make
the
kind
of
Baseline
social
media
docs.
So
I
guess.
The
idea
would
be
like
we'll
capture
our
state
as
it
is
today
and
then,
as
we
push
forward
into
the
Mastodon
era,
hopefully
we'll
add
kind
of
like
our
guidelines
about
social
media
and,
like
you
know,
we'll
kind
of
develop
that
as
we
as
we
push
into
this
new
space.
So
that's
what
I'm
thinking
about
right
now,
I!
B
Absolutely
your
your
efforts
so
far
have
been
awesome
and
it's
very
much
appreciated
some
new
business
stuff.
B
On
Community
Development,
we'll
we'll
our
meeting
Brian
will
be
with
us
for
our
next
meeting.
Presumably
so,
we'll
have
a
lot
more
to
talk
about
then
new
business,
so
operators.
This
was
mentioned
at
the
community
development
meeting.
I'll
mention
it
here.
B
I
talked
with
Vadim
a
little
bit
about
the
catalog
and
apparently
management
within
Red
Hat
sort
of
shifted,
Focus
away
from
the
catalog
on
other
things.
But
Vadim
wants
to
start
up
that
effort.
Again,
we
did
decide
that
there
will
be
that
several
working
group
members
are
going
to
reach
out
to
different
operator
project
maintainers,
to
gather
information
about
the
best
way
to
approach
things.
What
are
some
of
the
pitfalls?
B
They've
come
across
Etc
I'm
attending
the
tecton
one
they've
canceled
the
past
two
operator
meetings,
though,
now
that
the
new
version
came
out,
the
new
version
of
pipelines
came
out.
They
don't
really
have
much
to
talk
about,
but
I'll
be
attending
this
Thursday
and
then
omico's
reaching
out
to
the
windows
operator.
Folks
and
someone
else.
We
had
the
third
project.
What
was
the?
What
was
the
third
project?
Oh
get
Ops
reaching
out
some
for
the
get
Ops
one
and
Christian.
Do
you
have
any
any
input
on
that?
B
D
I
have
only
seen
the
the
updates
on
the
jira
cards
that
that
made
him
posted
I
haven't
had
the
time
to
dive
into
that
I
I'd
love
to
help.
So
if
there's
anything,
you
think
I
can
be
helpful,
with
I'm,
definitely
open
to
doing
that,
but
I
haven't
yeah
I
haven't
had
the
time
to
to
actually
look
at
at
it.
I
do
think
that
yeah,
especially
the
git
Ops
operator,
is
one
that
I'm
I'm
very
much
looking
forward
to
having
having
an
okd
version
of
and
kind
of
tangentially.
D
We
are
also
investigating
now
whether
we
can
actually
replace
the
the
tecton
build
pipeline
that
we've
just
built
for
s-cos
within
Argo
workflow,
because
that
is
even
more
powerful,
apparently
than
technolon
pipeline,
so
just
just
to
spike
just
an
investigation
thing,
but
yeah
we're
looking
at
at
that,
and
obviously
now
that
we
are
building
escorts
with
tecton.
We
need
the
the
pipelines
operator
for
okd,
so
we
can
really
kind
of
build
okd
on
top
of
okd
using
okd
without
relying
on
any
openshift
product
parts.
D
So
that
is
definitely
very
much
still
on
on
our
agenda
and
if
we
can
help
I
think
all
of
us
also
I'm
sure,
Mike
and
then
Luigi
Shireen
Alessandro,
who,
who
have
showed
up
here
from
time
to
time,
are
also
very
much
interested
in
getting
that
done.
B
D
B
B
Okay
and
now
here's
one,
the
Christian.
We
hope
you
can
answer
what
is
the
status
of
arm.
D
So
it
is,
it
is
getting
closer.
Let
me
put
it
that
way:
Alessandro
who
is
our
arm?
Qe
lead
for
openshift
he's
been
a
regular
I.
Think
on
on
this
meeting
too,
so
he's
been
working
on
it
and
we
essentially
just
need
to
get
a
compute
on
arm
to
be
able
to
build
on
arm
and
then
so.
D
He
has
has
a
pipeline
that
actually
creates,
creates
a
fully
multi-arch
manifest
listed
payloads,
and
he
has
built
it
once
and
it
works,
and
we
just
essentially
right
now
need
to
find
resources
to
deploy
that
on
and
build
it
regularly.
So
it
is,
it
is
very
close
and
yeah,
hopefully
in
the
in
the
first
quarter
this
year
still.
H
Yeah
I've
just
got
a
question:
do
we
have
a
a
general
approach
that
we
want
to
take
with
the
operators?
Because
I
I
listened
to
this
meeting
two
weeks
ago
and
it
sounded
like
we
wanted
to
get
in
to
creating
operators
rather
than
I
thought.
H
We
were
looking
to
take
the
red
hat
open
source
for
what's
in
the
red
hat
catalog
and
just
build
it
and
put
it
in
okd,
catalog
and
I
was
a
little
bit
confused,
because
some
of
the
conversation
seemed
to
be
going
down
the
route
of
let's
see
if
we
can
go
and
create
an
operator
rather
than
just
build.
What's
in
the
git
repo
somewhere.
B
B
We
can't
really
have
informed
discussions
about
changes
that
we
need
in
operators
for
them
to
be
able
to
be
deployed
without
really
understanding,
operators
and
understanding
the
process
and
for
maybe
members
of
this
group
to
go
and
contribute
to
those
projects
to
help
them
be
okd
friendly
right,
so
that
that
was
my
perspective
for
going
down
the
road
for,
including
in
the
discussion,
understanding
operator,
maintenance
and
whatever
right.
But
that's
just
me,
that's.
That
was
my
thought
of.
Why
we're
going
there
Christian.
D
So
we
we
have
this
one
repository
the
okd
operator
Pipeline,
and
that
is
something
that
Luigi
and
Shireen
have
been
working
on.
They
they
haven't
had
the
time
to
really
finalize
it
and
and
make
it
yeah
make
it
well
tested
and
all.
D
But
this
is
a
essentially
a
template
pipeline
that
you
can
use
to
build
some
of
the
operators
that
we
currently
ship
in
the
red
hat
catalog
to
rebuild
that
and
I
think
we
should
kind
of
agree
on
using
tecton,
or
at
least
our
tecton
or
Argo,
to
build
this
to
build
all
of
the
operators.
So
this
pipeline
can
be
used
to
build
a
couple
of
them.
D
There
are
a
couple
of
other
operators
that
are
too
complex
to
build
with
that
pipeline,
namely
I
think
the
the
important
ones
for
us,
the
pipelines
and
the
git
Ops
operators.
D
D
So
we
might
have
to
create
a
repo
for
for
all
of
these
tasks
or
we
just
merge
the
tasks
for
building
the
pipelines
operator
into
the
okd
operator
pipeline
repo
here
and
I
would
yeah
essentially
my
tip
would
be
you
try
to
use
tecton
to
build
the
operator.
It's
really.
It
really
comes
down
to
just
building
a
couple
of
container
images
and
putting
them
in
this
and
creating
this
bundle.
D
Image
which
yeah,
essentially
bundles
them
all
together
and
has
has
a
format
that
is
recognized
by
the
operator
Hub,
and
so
really
it's
just
building
containers
and
if
we
can
share
the
recipes
for
building
those
containers,
I
think
we
are
already
a
huge
step.
Yeah
we've
already
taken
a
huge
step
and
then
obviously
first
would
be
to
upload
that
to
a
personal
account
for
testing
and
then
once
we've
kind
of
vetted
it.
As
a
working
group,
we
can
move
that
into
the
official
Quay
okd
organization.
G
Yeah
I
think
that
that
sort
of
is
in
the
direction
of
answering
what
my
question
was,
which
is
that
you
know
we
don't
seem
to
have
any
place
to
put
the
bundles
into
a
catalog
if
we
build
them.
G
Okay
to
like
you
know,
techton
actually
builds
their
stuff
using
a
tecton
pipeline
and
I
had
to
look
at.
You
know,
building
all
that
and
one
of
the
the
initial
showstoppers
is.
You
know:
where
does
the
output
go
into
a
place
where
I
could
then
pull
it
in
into
okd?
You
know
and
that's
something
that
we've
been
talking
about
for
the
last
two
or
three
years
and
I
I.
Don't
know
we
have
an
answer
to
that.
G
But
what
Christian
is
saying
we
sort
of
need
a
couple
of
things.
Okay,
like
we
need
development,
ripples
for
testing
that
don't
go
anywhere
public,
but
once
it
goes
through
all
those
processes,
then
we
do
need
a
public
catalog
and
if
it
was
just
operator
hub
I,
don't
know
we
need
some
sort
of
labeling
so
that
you
know
we
could
set
up
a
you
know
samples
equivalent
of
knowing
what
to
pull
down
since
a
lot
of
the
stuff.
G
That's
there
won't
work,
so
I
think
there's
a
few,
maybe
we're
almost
there.
But
it's
not
clear
to
me
that
those
sort
of
showstoppers
are
out
of
the
way
on
how
to
proceed.
D
Yeah,
the
one
missing
part
is
definitely
that
catalog
repository,
we
I,
think
we'll
we'll
have
to
create
one
in
the
okd
project
organization
on
GitHub
and
then
I
I
haven't
looked
at
at
that
in
depth.
D
Yet,
but
then
we
can
take
a
look
at
the
community
operators,
repository
for
example,
kind
of
to
see
how
how
such
an
index
repo
works
and
then
kind
of
use
that,
as
a
template
for
the
index,
we
are
building
for
okd,
specific
operators
and
in
in
that
Repository
we'd
essentially
have
all
the
yeah
the
commits
specified.
What
what
what's
built
for
a
specific
operator
version
and
essentially
yeah
see
showing
what
goes
into
the
operator
and
what
comes
out
as
a
bundle.
D
That
is
definitely
something
we
yeah
we'll
need
that
that
catalog
repos,
actually
our
index
repo,
whatever
you
want
to
call
it
all.
B
Right,
it
might
be
useful,
I
think
in
the
near
future
to
create
a
document
of
steps
of
like
a
plan
like
these
are
the
things
we
need
to
do
and
in
what
order
to
get
there.
So
maybe
this
is
something
that
we
can
start
a
document
share
with
Vadim,
so
that
we're
all
working
together
and
sort
of
outline.
The
steps
that
we
want
to
take
to
to
get
there.
D
I
and
just
very
quickly,
Jamie
I
think
the
operator
Hub
community
has
already
documented
some
of
these
things.
I'm
just
going
going
into.
H
Yeah
I
mean
there
is
good
documentation
on
how
to
build
all
this.
It's
actually
got
considerably
easier
because
it
can
now
be
a
text-based.
You
can
build
a
catalog
from
textbooks
file.
You
don't
need
to
use
the
tooling
to
actually
build
the
format,
so
yeah
I
mean
basically
we
need
to
build
the
operator
bundles
for
each
of
the
individual
operators
and
then
the
catalog
is
created
effectively.
We
need
update
paths
generated
so
version.
1.2
then
goes
to
1.3.
It
goes
to
103..
H
We
need
to
Define
channels
and
I
think
the
way
that
ocp
does
it
has
a
channel
for
each
each
minor
release.
So
411
has
a
channel
for
12.
Has
a
channel
for
13
has
a
channel,
so
we
need
to
do
this.
Then
we
have
to
work
out.
When
do
we
actually
build
an
operator?
How
do
we
tie
it
into?
What
does
openshift
pipelines
version
x
mean?
Is
there
a
commit
that
we
can
identify
that
we
could
then
build
off?
H
B
To
clarify
what
I'm
talking
about
are
the
steps
of
administrative
things
that
we
need
to
do
as
a
group
just
to
clarify
that
those
are
the
those
are
the
things
that
I
think
we
should
write
out
like.
We
need
to
create
a
repo
here.
We
need
to
decide
XYZ
and
we
need
a
maintenance
plan,
a
cyclical
maintenance
plan
where
we
are
evaluating
if
something
needs
to
drop
off
or
not
or
if
we
need
to
search
for
contributors.
We
talked
about
this
before
about
maybe
the
Fedora
model
of
making
sure
that
there
are
people
assigned.
B
So
let's
actually
start
a
document
with
that
and
fill
it
in
with
the
steps
administrative
steps
to
getting
us
where
we
want
to
go
and
then
we'll
bring
it
to
vadim's
attention
and
go
from
there
and
then
just
start
checking
them
off
right
and
do
this
and
and
set
aside
some
time,
maybe
in
each
agenda.
15
minutes
for
the
next,
like
you
know,
next
five
working
group
meetings
to
talk
about
process
operator
maintenance
process
and
make
sure
that
we're
all
on
the
same
page.
B
Does
that
sound
like
a
tactical
plan,
to
get
us
where
we
want
to
go
I'm,
seeing
lots
of
nodding
heads
okay,
yeah
I,
think
so
all
right
all
right!
So,
let's
see
what
else
do
we
have
here
on
the
agenda.
B
So
prioritization
stuff
I
want
to
keep
revisiting
this
at
the
end
of
the
ever.
At
the
end
of
every
meeting,
we've
got
about
seven
months
left,
and
so
this
was
the
list
from
last
time.
Prioritization
we
talked
about
operators,
standardization
and
automation
for
community
activities.
I
think
that's
kind
of
represented
in
some
ways
in
terms
of
the
build
process,
but
then
I
asked
this
before.
B
D
That
one
thing
that
comes
to
mind
for
me
is
having
something
again
like
like
Fedora,
where
you
have
essentially
levels
of
would
trust
a
member
is
given.
So
you
have
the
admin
you
have
proven
packages
and
you
have
packages
proven
packages
can
make
changes
to
other
packages
as
well.
Packages
have
their
own
packages
assigned
to
them
and
I
think
scoping
that
down.
That
way
makes
a
lot
of
sense.
D
So
imagine
we're
talking
about
operators
now
and
there
might
be
a
person
or
multiple
persons
that
that
are
able
to
package
all
the
operators
or
do
changes
to
any
of
them.
While
others
just
have
access
to
their
own
to
to
the
operator,
to
that
one
operator
that
they're
maintaining
that
might
make
sense
so
essentially
kind
of
our
back
style
yeah
permissions
to
to
do
things
I'm,
not
sure
how
we
want
to
implement
that.
D
Whether
we
want
to
just
do
that
manually
or
you
know,
you
use
a
an
account
system-
maybe
we
can
get
the
Fedora
like
reuse,
the
Fedora
I
think
it's
called
Triple,
A
now
or
yeah
the
Fedora
rbac
system.
We
already
have
the
Fedora
group
The,
the
okd
group
in
the
Fedora
system,
I
believe
so
we
might
be
able
to
reuse
that
and
kind
of
just
use
our
Fedora
accounts.
D
Another
option
might
be
to
to
ask
sentos,
since
we've
now
kind
of
introduced
ourselves
there
or
yeah
setting
up
another
system,
although
that
obviously
needs
maintenance
as
well
so
having
reusing
one
of
the
existing
existing
systems
like
Fedora
or
Centos,
might
make
sense
here.
Okay,.
B
Excellent
one
of
the
things
that
came
up
as
well
as
more
install
docs
and
that
led
to
a
conversation
about
Dwayne
working
on
a
glossary.
Can
you
Duane?
Are
you
still
working
on
that
is
I
know
you
got
a
lot
on
your
plate?
Yes,.
B
E
Yes,
so
I'm
gonna
get
back
on
the
glossary
and
and
I'm
almost
doing
two
things
at
one
time
continue
to
work
on
on
the
okay
DS,
and
no
because
you
know,
if
we
have
someone
who
comes
in
and
and
they're
new,
then
you
have
to
break
down
things
to
them
so
that
that
you
know
part
of
the
glossary
is
done,
but
then
to
to
Give
Them
Enough
scope
of
why
it's
important
and
why
it's
a
a
potentially
great
career
skill
set
so
that
they
understand
the.
Why
they're
doing
this
and
for
students?
E
That's
always
important.
They
you
know
when
you
know
they
so
that
they
can
understand
how
to
prepare
themselves
for
the
Workforce
concern,
so
I'm
trying
to
do
it
at
that
level
and
I
think
I'm
I
think
in
my
mind,
I'm
targeting
maybe
16
and
above
you
know
you
know
so
that
you
know
up
to
young
adults
if
y'all
think
that's
the
most
appropriate
such
that
they
can
begin
to
to
have
the
vocabulary
and
to
understand.
E
You
know
how
to
find
these
things
and,
as
these
things
begin
to
shift
over
time
and
so
I'll
try
to
have
a
I,
have
a
draft
ready
but
I'll
try
to
work
on
the
mkd
docset
to
try
to
get
that
up
in
a
standard
format.
So
we
can
all
start
commenting
on
it
as
soon
as
possible.
B
Excellent
all
right
and
then
Jack,
your
your
item
is
still
on
there,
because
I
was
hoping
that
Michael
would
show
up
our
docs
person
that
he
didn't
show
up.
So
we're
still
sort
of
we
need
to
reach
out
and
see
if
we
can
get
him
to
come
to
the
meeting.
So
we
can
talk
a
little
bit
more
about
documentation,
challenges
and
and
their
system
and
whatnot,
so
I'm
going
to
hold
that
topic
until
the
next
meeting.
B
Ideally
when
we
can
have
our
our
red
hat
official
red
hat
docs
person
here,
I
think
the
last
thing
is
just
Edge,
so
a
lot
of
folks
are
talking
about
Edge.
Is
there
anything
Christian
that
you
can?
Let
us
know
about
something:
have
you
heard
anything
about
people
wanting
to
use
okd
on
the
edge?
What
are
our
options?
D
I
haven't
heard
anything
since
yeah
since
last
time
on
on
edge
I
do
know
that
people
are
still
interested
in
it
and
even
even
using
it,
but
yeah
I
haven't
heard
any
news
on
that
side.
I'd
rather
hand
it
over
to
jack.
For,
for
the
last
minute,.
F
I
was
actually
mainly
just
agreeing
on
the
on
the
other
point
from
before.
So
the
the
issue
of
the
doc.
Like
the
specific
thing
about
c
groups,
B2
was
results,
but
I
was
actually
more
asking
about
the
whole
process
like
how
we
can
change
some
of
the
dogs
and
not
get
ignored
when
we
don't
have
a
at
redhead.com
email
address.
B
Yeah,
this
was
discussed
at
the
community
development
meeting
and
the
previous
working
group
meeting
Christians,
so
we're
we're
kind
of
waiting
to
get
Michael
back
into
the
fold
here.
He's
been
kind
of
M.I.A
for
the
past,
like
I,
don't
know
a
month
and
a
half
or
so
just
because
we
need
to
sort
of
understand
better
how
we
can
leverage
the
red
hat,
docks
the
product
docs
and
then
what
we
need
to
just
do
on
our
own.
You
know
I.
H
Think
part
of
this
is
is
a
question
of
trust.
I
says
because
there
are
some
of
us
that
can
get
changes
done
quite
quickly
because
we've
been
working
with
the
Michael
for
over
a
year
and
he
trusts
us
and
and
I
think
that's
part
of
the
community.
It's
it's
I
think
it
goes
back
to
what
Christian
said.
Getting
people
that
have
that
high
level
of
trust
and
and
using
the
community
to
actually
build
that
trust
with
the
red
hat
organization,
so
that
we
can
get
things.
H
Names
are
recognized
and
we
can
get
things
accelerated
rather
than
just
it
could
be
anybody
off
the
street.
That's
put
a
pull
request
in
and
there's
no
recognition
or
trust
there.
So
I
think
this
part
of
this
process
is,
as
people
get
more
involved
and
become
known.
I
think
you
get
elevated
trust
and
you
sort
of
Fast
Track,
but
I,
don't
know
how
we
formalize
that
that
mechanism
and
getting
that
to
be
more
efficient.
B
D
Yeah
we've
asked
internally
and
it's
that
that's
not
gonna
happen
so.
F
Yeah
I
mean
I
mean
that's
the
finance,
that's
also
understandable,
but
maybe
then
this
week,
if
we
as
a
community,
can
can
set
up
some
mechanism
that,
like
some
other
member
of
the
community,
backs
up
your
merch
or
your
full
requests
or
like
two
or
three
people
say
hey.
This
is
actually
what
we
want,
because
of
course,
if
just
a
random
person
comes
along,
then
I
can
totally
understand
that
they
won't
easily
take
that.
But
maybe
we
can
reference
it
to
a
to
a
discussion
that
we
had
on
our
GitHub
or
so
and
say:
hey.
A
So
I
had
I
had
said
this
when
the
discussion
came
up
before,
but
one
we
need
to
create
some
docs
for
ourselves
on
how
we're
supposed
to
make
changes
to
the
Upstream
docs.
You
know
what
what
like
markup.
D
Something
we
could
even
do
is
Fork
the
okd
docs
repo
into
okd
into
the
okd
project
and
then
merge
our
working
group
changes
into
the
farc
first
and
then
open
a
PR
from
the
fork
to
the
main
repo.
That
would
you
know
that
would
already
show
people
that
there
has
been
some
betting
done
by
the
working
group.
D
It
has
first
merged
into
the
fork
that
is
maintained
by
by
us,
so
we
have
looked
at
it
and
when
that
origin
of
okd
project
might
that
might
then
have
a
higher
degree
of
of
trustworthiness.
H
Just
a
comment
about
do
we
is
the
tooling
open
and
available
to
actually
convert
the
repo
into
a
website,
because
I
know
that
on
a
red
hub,
just
changed
the
tools
underneath
the
docs,
because
if
we
do
that,
we'd
want
to
ensure
that
it
builds,
and
it
renders
correctly
and
I'm
not
sure
what
the
tool
chain
is
behind
docs
at
openshift
and
docks
at
okd.
B
D
B
Top
the
tagging,
though
I
don't
know
like,
is
it
just
like
okay,
D
or
what
you
know
I,
don't
know
all
right,
we're
five
minutes
after
I
do
want
to
be
mindful
of
people's
time.
Let's
put
an
end
to
this
meeting
and
we'll
put
a
a
note
to
add
this
to
the
agenda.
B
The
next
working
group
meeting
I
will
send
an
email
to
Michael
and
see
if
we
can't
sync
up
somehow
it
might
be
that
the
time
change
made
it
a
Time
conflict
form
or
something
like
that,
but
I'll
reach
out
to
him
directly
and
see
if
we
can
get
some
conversation
going
for
the
next
meeting.
All
right
thanks
folks
appreciate
you
spending
so
much
time
and
effort
on
the
okd
project
and
we'll
see
you
next
time.