►
From YouTube: OKD Working Group Meeting 02-28-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
B
Installing
a
multi
note,
install
could
maybe
take
care
of
getting
our
you
know,
maybe
might
could
be
a
long-term
on
pathway
and
then,
if
our
goal
is
to
get
them
to
an
opinionated
kubernetes,
then
supporting
language
and
developments
of
language
towards
openshift
such
they
can
understand
basic
kubernetes
and
then
the
opinion
nation
of
of
openshift
and
so
and
there
you
see
I
have
a
little
kubernetes
cheat
sheet
to
get
so
first
I
saw
this.
B
I
was
also
I,
have
I,
have
a
Red
Hat,
a
little
ebook
that
they
had
out
and
so
I
copied
that
and
put
that
link
in
and
then
I
got
something
from
datadog
that
had
a
cheat
sheet
and
I
was
just
here
looking
at
the
okd4
documentation
to
try
to
see
so
I'm
also
talking
to
a
potential
customer.
B
That's
maybe
looking
at
look
using
openshift
and
they
keep
saying
I'm
talking
above
their
heads,
I'm
like
how
can
I
and
I'm
and
that's
a
very
frustrating
thing
so,
but
that's
probably
a
common
thing
to
get
to
grow
our
community
and
so
I'm,
trying
to
okay
what
what
gear
do
I
need
to
back
down
and
and
talk
to
them
such
that
they
can
just
be
be
more
comfortable
with
kubernetes
and
okd,
and
understand
that
we're
here
to
help
them
and
and
get
away
from
thinking
about
a
monolithic
approach
to
to
anything
and
so
and
so
there
you
can
see
list
known
processes
for
kubernetes
fundamentals.
B
This
is
where
each
newcomer
could
could
maybe
do
this
as
a
crowd
Source
activity
where
they
can
so
it.
So
this
is
a
an
experience
that
newcomers
can
gain
and
grow
and
become
articulate
and
and
then
hopefully
become
self-sufficient,
and
there
you
see
me
talking
about
them
in
the
opinionations
of
edge
microchip
hypership.
You
know
all
the
opinions
being
able
to
speak
that
language,
because
that
I
feel
is
going
to
be
a
common
thing
going
between
okd
and
openshift,
so
they
don't
get
lost
and
then
you
know
that
leads
us
to
other
things.
B
They
operated
time.
You
know
and
all
the
other
other
potential
things,
and
so
this
is,
you
know,
Brown
calling
is
a
potential
road
map
and
that
I
have
to
test
out
as
well,
because
I'm,
probably
here
and
number
two
where
of
Sno
installs
Oh
I
thought
I
had
numbers
in
there
and
so
I
want
to
be
able
to
master
that,
but
also
not
lose
any
other
newcomer.
A
Yeah
I
think
this
is
really
cool.
Dwayne
and
I'm
I'm
happy
to
hear
that
you're
kind
of
thinking
about
the
full
Journey.
You
know
how
do
we
get
from
like
a
novice
to
an
expert
one
thing
I'm
curious
about
is:
can
we
reuse
or
link
to
some
of
the
like
existing
content?
So
when,
when
you
say
like
well,
we
have
we
have
some
people
who
show
up
and
they
don't
even
know
what
open
source
is
or
whatever
it's
like.
A
A
You
know,
like
I,
think
it's
awesome
that
we
have
people
coming
who
are
like
well,
I,
don't
know
what
a
container
is,
but
I
want
to
know
more
about
this
stuff
I'm
wondering.
Could
we
use
some
of
the
the
cncf's
material
to
say,
okay,
yeah?
If
you
want
to
learn
about
containers,
you
should
really
you
know
follow
this.
You
know
tutorial
path
that,
like
this
cncf
has
put
together
or
something
so
I'm,
just
I'm,
just
kind
of
curious.
B
Yeah
I
I
do
find
myself
going
out
and
looking
at
that
stuff
to
try
to
make
things
as
as
digestible
as
possible.
So
newcomers
don't
get
confused.
Typically
like
in
the
classroom.
You
tell
a
student
to
go
read
but
and
telling
your
potential
colleagues
they
get
really
upset.
B
You
know
so
I'm
trying
to
be
more
patient,
you
know
and
and
just
well.
What
is
it
you
do
not
understand,
but
in
some
circles
people
don't
want
to
even
say
why
they
didn't
say
they
don't
understand
it
just
say:
you're
talking
over
me,
I
was
like
my
God.
You
haven't
even
asked
any
questions.
You
know
and
I
say
well.
This
is
in
the
United
States.
This
is
policy.
You
know
if
you're
going
forward,
this
is
looks
like
the
way
you're
gonna
go
for
it.
If
a
war
war,
three
breaks
out.
B
You're
gonna
have
to
know
this
so
but
I'm
I'm
trying
to
be
as
gentle
as
possible,
but
at
some
time
at
some
point
you
just
gotta
roll
as
fast
as
you
can,
but
I
don't
know
right
now,
I'm
just
trying
to
be,
as
you
know,
I
want
to
bring
a
crew
of
people
in
and
and
because
I'm
also
seeing
hundreds
of
millions
of
dollars
of
a
hundred
startup
companies
starting
Cloud,
stuff
and
I'm
like
how
are
they
doing
that
I'm
sure
they're
having
the
same
challenges,
you
know
because
things
are
moving
so
fast
and
they're.
B
Thinking
here
that
I
I
didn't
put
in
is
what
is
our
Target?
Do
we
want
to
do
kubernetes
one
two,
five,
one,
two,
four
one,
two
three:
what
is
you
know
because
it
is
a
little
bit
of
a
moving
Target
but
I'm
like
I,
haven't
even
got
there.
You
know,
and
but
but
those
are
some
questions.
B
A
A
Think
you're
running
into
a
problem
that
a
lot
of
people
run
into
when
they
talk
about
this
technology
like
I,
anecdotally
speaking,
you
know
I've
I've
heard
from
sales
associates
who
are
trying
to
sell
openshift.
You
know
who
run
into
the
same
type
of
problems
that
you're
describing
where
it's
like
you
know.
Kubernetes
is
moving
at
like
the
speed
of
light
and
a
lot
of
people
who
see
this
technology
and
hear
about
the
buzz
around
it
and
and
want
to
be
part
of
it.
A
A
I
just
want
to
make
sure
that
we're
not
like
overloading
you
with,
like
rewriting
content
that
might
have
already
be
written,
so
I
just
want
to
say,
like
hopefully
yeah
we
can
add
our
editorial
but
like,
hopefully
we're
also
linking
out
to
kind
of
well-known
places
where,
where
people
could
learn
this
stuff,
but
I
get
you
in
a
live
situation.
You
can't
you
can't
be
like
well
go,
read
this
webpage
and
then
come
back
to
me
in
15
minutes.
You
need
elevator.
C
Pitches
yeah
for
sure
yeah
all
right.
Well,
let's
so
we
know
what
the
status
of
that
is.
Let's
be
mindful
of
time
and
move
on
text
on
installation
based
on
the
new
information
I'm
reworking
a
couple
pieces
of
that
documentation,
product
documentation.
C
We
don't
have
any
news
on
product
documentation
and
I,
don't
see
that
Michael
is
here
today.
C
A
Was
kind
of
on
me
I
had
I
was
just
gonna
dig
up
the
link
to
that,
because
I
had
proposed
that
as
a
suggestion
actually
and
I
had
never
come
back
to
it.
So
we
had
talked
about
it
back
in
September,
yeah
and
I'd.
Never
come
back
to
it.
So,
like
honestly,
like
I'm,
I'm,
really
game
to
make
that
video,
we
just
need
to
I
need
to
put
together
a
script
and
kind
of
come
back
to
it.
You
know,
but.
C
B
C
Knew
how
to
dig
into
it
themselves
and
if
those
of
us
in
the
community
that
are
trying
to
support
other
users
like
I,
I've
post
through
a
must-gatherer
but
I,
don't
have
the
the
intuition
to
know.
Oh
I
should
go
to
this
area
here
in
the
in
the
must
gather
it's
a
to
really.
You
know,
based
on
what
the
person
said
find
out.
What's
going
on
knowledgeable.
A
C
C
So
here's
what
we
can
do
and
I
I
think
it's
the
most
efficient,
which
is
folks,
can
record
themselves
doing
their
presentations
just
to
make
sure
you
get
it
right.
If
you
mess
up
and
you
want
something
edited
just
make
a
note
of
the
timestamps
where
you
want
in
and
out
and
then
just
send
me,
the
the
video
and
I'll
do
the
adding
of
the
the
bumper
at
the
beginning
and
the
fade
out
at
the
end
and
all.
C
I'm
working
video
a
lot
and
happy
to
sort
of
put
the
the
front
and
the
end
the
you
know
the
start
in
the
beginning
on
it
and
if
you
have
like
a
major
mess
up
where
you
want
like
a
chunk,
you
know
taken
out.
Just
let
me
know
and
I
can
I
can
do
that.
D
That's
brilliant
Jenny.
Do
you
have
so
you've
got
software
that
stitches
a
couple
of
videos
together
as
well.
C
D
A
At
the
risk
of
signing
up
for
more
stuff
yeah
like.
C
A
B
C
Very
cool
all
right,
email
hosting,
so
we
have
confirmed
that
the
aliases
are
working.
The
question
now
is,
and
we
can
do
this
asynchronously
or
synchronously.
Where
are
all
the
places
where
we
need
to
notate
an
email
and
which
one
of
the
aliases
right
so
the
website,
maybe
info-
and
maybe
you
know-
we've
got
here-
I
can
pull
up
the
list
here,
but
what
are
some
places?
Maybe
add
them
to
the
notes
of
places
where
you
think
we
should
have
our
email
prominently
featured.
A
I
guess
like
what?
What
is
our
expectation
on
contact
from
the
community
Through?
The
email
addresses.
A
Well,
no
like,
like
so
I
know,
we
have
these
different,
like
Community
Dev,
like
obviously
like
you
know,
that's
like
a
mailing
list
that
people
should
interact
with,
but
when
we
say
like
broad
broadcasting
like
like
emails
for,
like
you,
know,
info
security
chairs
like
well,
we
we
know
we
know
like
what
what
security
is
like.
We
want
people
to
send
us
security
change.
A
C
So
cheers
is
stuff.
Tears
came
up
as
a
way
to
reach
out
to
the
chairs
for
anything
working
group
related
that
someone
may
want
to,
and
this
is
all
hypothetic
and
it's
not
happened
anytime.
That
I've
been
involved
with
the
written
group,
but,
let's
say
you're
having
an
issue
that
you
need
resolved
in
terms
of
interactions
or
you
feel
uncomfortable
in
the
community
due
to
something
or
there's
some
sort
of
communication
you
need
to
have
with
the
leadership
of
the
working
group
right.
C
So
that's
what
that
one
was
about
info
was
like
sort
of
the
catch-all
for
anything
that
doesn't
fit
into
it.
Or
you
know
someone
wants
info
about
okd
in
general,
something
like
that.
C
E
I
was
gonna
say:
would
it
be
easier,
though,
just
to
put
a
link
to
okd.io
and
have
a
contact
page
there
where
we
list
the
emails
and
their
uses?
So
it's
obvious
that
if
you
want
to
do
it
for
this
function,
this
is
how
you
contact
us
and
that
way.
A
Let's
create
that's
kind
of
what
I
was
thinking
too
Brian,
like
part
of
the
reason
for
capturing
this
is
yeah,
like
you
know,
as
I'm
thinking,
because
I've
been
looking
at
this
social
media,
Doc
Page,
and
it's
like
yeah
like
having
a
One-Stop
page
for
all
of
our
Communications,
where
it's
just
says
like
yeah,
how
to
use
the
stuff
and
then
yeah.
We
just
blast
the
link.
C
E
C
C
Personally,
just
because
it's
it's
very,
it's
like
maybe
someone's
like
well
I,
don't
need
help.
I
just
want
to
tell
you
about
something
or
something
like
that.
You
know
or
let
you
know
about
an
event
where
okd
could
participate,
or
you
know
the
OCD
Community
could
participate
or
something
like
that.
I,
don't
know
what
do
other
people
think.
E
A
I
mean
slowly
but
I
guess
like
what
maybe
what
I'll
do
is
I'll
draft
off
of
what
Brian
is
doing
here
so
as
Brian
makes
the
contact
us
page,
maybe
instead
of
trying
to
do
the
social
media,
Doc
is
like
a
whole
shot.
I
could
just
try
and
put
up
sections
as
individual
PR's,
and
then
you
know,
I
did
that
the
real
question
is
like
so
contact
us
is
about
telling
people
how
to
get
in
touch
with
us.
The
Social
Media
stuff
is
going
to
be
more
like
a
Communications
kind
of
thing.
A
A
I
mean
so
on
one,
so
the
initial
work
that
I
was
trying
to
do
was
just
capture
what
our
current
Communications
pathways
are
right.
So,
like
the
Twitter
the
website,
the
mailing
addresses
you
know
just
the
basic
stuff
and
then
my
Hope
was
my
I
guess
my
intention
for
the
future,
assuming
the
community
kind
of
like
agrees
on
it,
is
that
we
would
start
to
build
that
dock
out
as
we
started
to
create
these
guidelines.
A
So
the
notion
of
like
okay,
here's
how
you
get
in
touch
with
us
and
then
here
are
our
guidelines
for
communication.
So
when
we
say
we
have
a
Twitter
account
and
we
have
a
mastodon
account,
okay.
Well,
what
do
we
use
those
for?
Here's
like
the
guidelines,
so
that
you
know
if
we
ever
have
to
get
into
a
situation
where
maybe
we
want
someone
else
to
do
Communications
or
like
someone
else
is
going
to
run
the
Twitter
account
or
Jamie's
going
out
of
town
for
a
month
or
something
you
know
we
have
some.
A
E
Because
I
think
when
we
discussed
the
emails,
it
was
thought
that
this
was
when
you
didn't
want
communication
in
the
public
domain,
but
where
it's
like
you're
asking
for
help
and
other
people
could
benefit
from
seeing
the
open
discussion.
We'd
use
the
social
media
channels,
so
I
I
think
information
like
that.
Where
what
is
useful,
when
should
we
use
an
email
versus
a
Twitter
or
a
slack
I?
Think
that's,
because
what
we
don't
want
to
do
is
what
we
saw
with
the
the
other
channels,
where
one
person
will
get
frustrated.
E
They
didn't
get
a
response
within
10
minutes
and
they
spam
the
same
message
to
every
possible
Channel.
We
want
to
try
and
avoid
that.
So
we
want
some
clear
guidelines
if
you're
asking
for
help
other
people
could
have
the
same
problem.
So
it
goes
in
the
slack
Channel.
If
you
want
to
raise
a
concern
about
an
abusive
member
of
the
community,
that's
a
more
confidential
discussion,
so
you
do
that
in
an
email,
so
yeah.
A
C
C
Okay,
I
want
to
add
something:
I
want
to
bounce
back
before
we
move
forward.
I
forgot
to
add
it.
Someone
pointed
out
that
the
AWS,
someone
on
slack,
pointed
out
that
the
AWS
IPI
default
deployment
guide
is
actually
it
lists.
C
The
wrong
instance
types
so
for
stuff,
like
that
I,
don't
know
we
determined
that
we
don't
have
the
names
of
the
people
stored
in
here
in
any
way
that
were
the
original
authors,
do
we
like
we
didn't
even
add
any
like
metadata
tags
or
anything
that
say
who
the
authors
were
so
I,
don't
know
who
wrote
the
IPI.
A
But
the
IPI
stuff
was
all
from
me
originally
was
it
yeah,
okay
and
I
know
exactly
what
the
problem
is.
Aws
changed
some
of
their
instance
names
and
we
like
we
changed.
You
know
AWS
changed
some
of
the
default
instance
types
and
we
pushed
into
those
you
know
as
well.
So
yeah.
E
C
F
C
B
C
Asked
them
to
put
in
a
a
ticket,
I,
don't
know
if
they
did
or
not
so.
C
All
right,
all
right,
so
we
went
through
that
next
up
is
I
added
volunteer
tracking.
C
Do
we
have
any
so
we
have
an
item
to
reach
out
and
get
volunteers,
but
we
haven't
defined
a
way
to
actually
notate
who
our
volunteers
are
because
there
was
one
person
a
couple
weeks
ago
who
volunteered
that
wanted
to
do
Tech
stuff
and
then
we've
had
other
people
volunteer
for
documentation.
I,
don't
think
we've
ever
created
something
that
we
can
actually
track
our
Volunteers
in.
Have
we.
E
I
I
like
to
turn
that
into
a
different
question:
how
do
we
run
projects
within
the
community?
I
was
going
to
bring
this
up
in
the
ion
of
the
operator
catalog,
because
I
mean
it's
okay,
saying
that
someone
wants
to
volunteer.
E
Because
up
to
now
we
tend
to
to
say:
oh
I'll:
do
that
and
we
go
off
and
we
do
it
on
our
own
and
eventually,
when
time
permits
we
sort
of
it's
finished,
but
for
other
things
we
don't
seem
to
have
a
way
of
saying
who
wants
to
work
on
this,
and
how
do
we
actually
organize
these
sort
of
like
Sub,
sub
communities
or
sub
work
groups
and
I
I?
Think
that
goes
hand
in
hand
with
this.
So
when
someone
says
I
want
to
volunteer,
it's
it'd
be
much
easier.
E
If
we
could
say,
go
and
work
with
Dwayne
and
amiko
or
Luigi
and
go
and
do
the
SNL
guide,
for
example,
it's
rather
than
someone
says,
I
volunteer
and
we
just
like
fire
him
off
say:
go!
Do
that
without
sort
of
any
supporters
like
we
sort
of
hang
them
out
to
dry
a
bit.
C
Yeah
yeah,
that's
good,
that's
good
and
about
a
fedora-like
process
of
people
attaining
new
levels,
basically
of
of
within
the
working
group
like
levels
of
participation,
I,
guess,
you'd.
A
That
happens
at
a
different
time,
and
this
is
how
this
group
will
meet
here
and,
like
you
know,
because
I
I
agree
like
when
I
look
at
part
how
I
participate
in,
like
you
know
the
kubernetes
community
or
other
open
source
communities
or
even
Fedora
yeah
the
larger
communities.
This
becomes
a
problem
where
you
have
you
have
to
Define
like
what
is
a
working
group.
What
is
a
a
special
interest
group
like?
How
do
we
Define
how
that
group
gets
together
and
does
their
work
and
then
leaves
I?
E
I
mean
well,
the
example
I
was
going
to
talk
about,
is
the
catalog
project,
so
I've
been
doing
some
work
and
you
realize
it's
too
big
for
one
person,
one
person's
not
going
to
go
and
create
the
OCD
catalog.
So
how
do
we
actually
do
that
now?
I
know
things
often
happen
within
red
hat
and
you
go
off
and
you
do
your
own.
You
have
your
internal
meetings,
but
it's.
How
do
you
bring
the
community
into
that?
E
How
do
we
actually
say
who's
interested
in
doing
catalogs
and
let's
do
some
work
each
week
to
move
the
project
forward
and
how
do
we,
collaborate
and
I'm
not
saying
it
has
to
be
super
structured
and
we
have
to
go
and
create
and
create
sort
of
Articles
of
Association
and
and
whatever,
to
get
a
group
up
and
running
it's
just
foreign.
E
D
Sorry,
sorry
Jamie,
not
good
yeah,
okay
I
was
going
to
suggest.
Could
we
not
track
on
on
GitHub
just
like
like
we'll,
have
a
project-
and
we
just
say
Okay
on
this
project,
Luigi,
Dwayne
and
so
on
will
be
working
on
this
and
as
a
community
you're
welcome
just
just
to
just
to
have
it's
not
like
just
a
framework
of
a
suggestion
really
and-
and
these
are
the
contact
people
and
knock
yourselves
out.
You
know,
put
your
name
down
and
help
out
yeah.
C
And
that's
actually,
that's
that's.
Actually
what
I
was
going
to
say
is
that
so,
for
example,
the
open
git
Ops
group,
they
create
teams
within
GitHub
right,
and
so
you
create
a
GitHub
team
for
a
particular
project,
and
then
that
way
you
know
who's
in
it
and
people
can
know
who
they
need
to
communicate
with
and
whatever
so
I
think
that
might
be.
C
The
first
start
is
like
created
and
for
folks
that
aren't
familiar
here
is
here:
are
our
teams
for
this
group
and
actually
I'll
put
it
in
the
notes
as
well,
so
every
every
GitHub
org
has
teams,
and
let
me
volunteer
tracking,
also
changes
to
volunteer
participation
like
right
on
the
notes,
so
I
would
think
that
one
of
the
first
things
that
we
can
do
is
I
mean,
let's
create
a
list
of
like
maybe
five
things
and
I.
C
Think
one
of
the
first
things
in
that
list
would
be
to
create
a
a
team
for
whoever
wants
to
be
interested
in
whatever
particular
project,
because
some
projects
are
going
to
require
a
repo.
Others
are
not.
You
know
they
might
be
using
other
types
of
resources.
So
does
that
feel
right?
Does
that?
Does
that
seem
right.
D
Yeah
I
think
I
think
it
looks
good
I
mean
I,
don't
know
about
the
rest
of
the
Gods,
but
at
least
it's
something
and
something's
better
than
nothing.
Yeah.
B
A
C
Attention
now
so
sure
so,
GitHub
teams
that
would
be
like
step
number
one-
is
create
a
GitHub
team
for
an
idea
or
a
concept
that
people
wanted
to
participate
or
throw
out
as
something
you
know.
We
could.
We.
A
A
Someone
has
to
like
do
something
with
GitHub
and
I
would
want
to
I
think
like
and
not
to
be
too
much
of
an
a-hole
here
or
whatever,
but
like
I,
know
we're
small
but
like
before
we
get
to
the
point
of
doing
stuff
like
creating
infrastructure
or
doing
things
like
that
I
think
groups
should
have
to
come
with,
like
a
definition
of
like
what
they're
gonna
do.
What
are
they
trying
to
accomplish?
A
A
Six
months
later
and
like
you
know,
three
of
those
people
are
still
doing
stuff
or
so
I
just
want
to
make
sure
that,
like
we
make,
we
make
people
kind
of
buy
into
like
if
we're
going
to
make
a
GitHub
team
to
do
something,
we
should
have
a
little
bit
of
definition
around
like
what
are
we
doing?
How
will
we
know
when
it's
done?
You
know
those
kind
of
things,
so
that
would
be
my
only
pushback
on
that.
C
Synopsis
I
know
Brian,
you
said
you
don't
want
him
to
write
a
treaties,
but
it's
just
a
paragraph
of
this
is
what
we
plan
to
do,
and
these
are
the
people
who
are
involved
or
people
who
want
to
be
involved.
What
what
would
we
want
as
some
sort
of
defining
thing
from
the
people
we're
interested.
E
I
mean
I
would
say
a
ticket
on
the
planning
board.
It
would
be
a
good
place
to
start
sure.
Okay,
just
just
try
and
get
it
into
lightweight,
but
try
and
get
us
to
start
using
tools.
So
if
you
put
a
ticket
on
the
planning
board
and
then
just
guidelines
of
like
we
don't
want
to
clutter
up
the
okd
GitHub
space
with
hundreds
of
hello
world,
we
started
an
idea,
but
it
went
nowhere.
E
So
when
do
we
I
mean
because
I've
started
in
the
catalog
stuff
in
my
own
bit
repo,
my
my
personal
space
and
I'm
got
to
the
point
where
it
would
be
quite
nice
to
start
collaborating
with
people
and
it's
like
well.
How
do
we
do
this
and
do
I
put
something
in
a
slack
in
a
in
this
meeting?
Do
I
yeah?
How
do
I
actually
invite
people
in
to
collaborate?
And
it's
it's.
It's
just
things
like
that,
because
we
have
none
of
this.
E
We
have
no
sort
of
Prior
sort
of
examples
of
how
this
community
works
or
how
we
want
it
to
work.
So
it's
just
thinking
that
and
I
think
less
is
more.
In
this
case.
The
the
lighter
weights
and
get
people
to
actually
do
what
they
want
to
do
rather
than
process.
C
D
No
honestly
I
would
like
to
get
involved
and
see
how
we
can
help
I
mean
it
is
and
you're
right
it's
massive
and
we
need
lots
of
people
involved.
If
you
put
that
down.
I'll
certainly
certainly
do
my
best
to
to
get
involved
with
it.
E
Yeah
so
I
mean
I
actually
have
a
catalog
and
I
can
actually
load
operators
into
my
okd.
So
I've
got
that
far,
but
it's
then
just
working
out
and
there's
a
whole
I
mean
I'll
just
put
a
link
in
there.
If
you
go
to
the
catalog
operator
page
at
the
bottom,
there's
a
whole
lot
of
questions
and
I
am
looking
for
some
friendly
red
haters
to
answer
some
of
them,
because
it's
about
how
does
proud
work
and
because
I
mean
when
I
look
at
this,
we
shouldn't
have
to
invent
the
wheel.
Red
hat.
E
D
We
because
they're
out
of
payload
they
did
day
two
type
operators-
they're,
not
core.
So
we
can.
We
use
this
CPS
build
and
it's
there's
so
many
moving
Parts
there's
like
a
thing
called
honey,
badger
and
there's.
This
is
massively
intense
and
involved
and
the
the
flow
is
not
easy.
So
in
order
to
in
order
to
simplify
things,
we've
we've
we've
I,
don't
know
if
we
can
even
use
that
internally
and
and
maybe
even
try
and
clone
it
I,
don't
know
it's
something
I
can
find
out,
but
it
is
very,
very
involved.
D
So
if
we
could
simplify
things,
it
would
be
much
easier
and
and
get
the
community
to
also
help
and
and
and
and
be
involved
in.
That
would
be
great.
C
D
C
E
I
mean
I
think
that
this
comes
to
the
the
Crux
of
it.
We
have
no
governance
of
our
GitHub
organization
in
terms
of
who
gets
and
I
think
it
comes
to
El
Nico's
idea
of
we
have
levels
of
members,
so
somebody
walking
off
the
street
shouldn't
be
able
to
go
in
trash
up
or
GitHub
space.
But
if
you're,
a
member
that's
been
coming
to
meetings
or
working
with
the
group,
then
you
shouldn't
have
to
ask
to
do
everything.
E
You
should
be
giving
a
level
of
of
trust
and
permission
that
you
can
start
doing
things
yourself
and
but
obviously
then
to
commit
things
like
a
version
of
okd
or
the
the
pipeline
stuff
that
has
been
going.
We
want
you
to
be
a
more
trusted.
Member,
so
I
think
we
have
to
have
that
level
and
but.
F
C
Well,
I
can
I'll
tell
you
what
I'll
do
is
I'll
link
you
to
how
the
open
get
UPS
working
group.
Does
it
because
they've
got
maintainers
so
if
you're
a
maintainer
status,
you're
someone,
that's
given
rights
to
like
approve
merch
requests
on
the
website
or
of
a
majority
of
maintainers
are
a
positive
voter
required
for
a
governance
item
to
pass,
and
things
like
that.
C
So
that
might
be
a
way
that
in
which
we
can
do
this
and
it'll
solve
that
issue
of
in
the
working
group
Charter,
we
had
things
like
well
majority
votes,
so
can
someone
show
up
to
vote
and
then,
but
never
have
participated
in
like
actually
doing
stuff
for
the
project
and
and
have
a
stake
in
it
right?
You
know
so
I
think
this
answers
a
lot
of
that
stuff.
So
can
we
agree
to
maybe
collect
examples?
C
A
I
was
I
was
responding
to
something
else:
I
I,
don't
have
a
group
that
I
can
I
mean
I
probably
could,
if
I
could
think
about
it,
but
like
I
just
wanted
to
say
that
like
I,
I,
totally
agree
with
what
Brian's
putting
forth
here
in
terms
of
like
we
should
be
using
the
jira
discussion,
whatever
board
on
GitHub
like
we
should
focus
activity,
there
I
think
it's
awesome
to
have
the
people
who
are
generating
a
working
group
or
generating
a
project
like
they
should
open
a
card
there
and
then
the
the
project
maintainers
can
then,
like
you
know,
we
can
make
decisions
as
a
community
to
say.
A
Okay,
we've
got
a
card
here
that
someone
has
created
in
the
to-do
list,
and
it's
about
you
know.
Brian
Ennis
wants
to
make
a
new
operator
catalog
right
so
like
then
we
can
say
all
right.
People
should
put
their
names
on
that
card
if
they
want
to
help
out
with
Brian
and
I.
Think
we
as
a
group,
think
this
is
good,
so
we're
going
to
move
it
to
the
in
progress
category
or
something
right
or
you
know,
like
I,
think
organizing
around.
A
That
is
perfect,
because
now
we
have
like
a
way
to
kind
of
capture
all
this
in
history.
We
have
a
way
to
point,
even
though
we
don't
have
governance
for
right
now
about
how
this
stuff
should
be
done,
we're
still
gaining
it
through
the
project
like
maintainers
and
whatnot,
which
I
think
is
a
good
idea.
So
that
was
just
kind
of
my
thought.
C
Do
we
want
to
go
back
and
I
asked
this
last
year
when
we
first
got
the
project
board
up,
do
we
want
to
go
back
towards
meetings
being
going
through
project
board
stuff,
or
does
that
make
it
too
dry
and
too
sort
of
mechanical
versus
sort
of
our
more
discussion
based,
and
then
we
throw
stuff
into
the
hack
MD?
Or
is
there
something
in
between
what
are
folks
feeling.
C
E
Yeah
but
I
think
the
the
main
meeting
more
of
the
discussion.
What's
going
on
and
what's
important
to
look
at,
so
that's
more
of
a
conversational
meeting.
This
one
I
think
should
be
about
Community
projects
and
whether
it's
documentation,
we
can
all
add
a
an
item
and
and
track
them,
because
I'm
also
aware
that
there's
things
that
we
drop
and
we
maybe
shouldn't-
drop
because
there's
no
one
immediately
interesting,
but
there's
still
things
that
need
to
be
done
and
they
sort
of
slide
off
the
agenda
right.
We
come
back
to
them.
E
C
Yeah,
that's
true,
and
then
we
can.
When
people
say
I,
don't
I
want
to
volunteer,
but
I
don't
know
where.
Then
we
can
say
well,
here's
the
board,
here's
here's
things
that
are
pending
or
things
they
could
use
some
people
I
like
it
all
right
all
right.
Well,
then
expect
that
to
the
next
meeting
to
be
more
focused
on
the
board
directly
yeah.
A
I
mean
my
car,
my
caution
about
running
the
meeting
around
the
board,
because
you
know
I
have
a
few
of
those
already
that,
like
meetings
that
run
around
year,
rewards
is
like
I.
The
question
I
would
ask
is:
does
our
board
change
enough
on
a
week-to-week
basis
that,
like
having
that
conversation,
is
going
to
be
interesting
right
now,
I
think
in
in
the
future?
A
We
might
get
to
that
point
but
like
like
so,
for
example,
I'm
subscribed
to
everything
that
comes
in
the
okd
project
organization,
so,
like
I,
don't
I,
don't
necessarily
review
everything
but
I'm
just
kind
of
like
watching.
What's
going
on
there
and
like
it
seems
like
if
we
were
to
talk
about
the
activity
that's
happening
in
the
project
right
now,
we
would
probably
be
spending
most
of
our
meetings.
Talking
about
the
work
that,
like
Luigi's
group,
is
doing
around
the
pipeline.
B
F
A
E
Well,
I,
don't
I,
don't
I,
don't
think
they're
using
their
planning,
but
I
mean
if
we
look
at
the
email
activity
that
we've
just
gone
through.
None
of
that
went
in
planning,
so
that
was
purely
in
our
agenda
notes
and
maybe
that
should
have
been
on
the
board
yeah
as
a
way
of
tracking
the
progress
of
that
activity.
E
So
I
think
we
can
make
it
what
we
want
to
make
it
and
I
think
the
question
retail
is
that
we
don't
want
to
be
discussing
one
one
Bob
request
or
one
feature
request:
I
I
think
the
board
should
be
more
about
projects
than
actual
implementation
details
within
a
project.
If
that
makes
sense,
yeah.
A
Yeah
totally
totally-
and
you
know,
if
we're
gonna-
if
we
get
to
that
point
where
we
want
to
have
a
meeting
focused
around
like
a
specific
planning
board,
we
should
probably
have
a
planning
board.
That's
like
related
to
that
meeting,
then
right.
So
we
know
that,
like
when
we
get
to
the
end
of
a
meeting,
we
can
say
we
can
clear
these
cards
off
or
this
card
needs
to
stay
because
we're
going
to
talk
about
it
next
week
or
whatever
so
like.
You
know
that
would
just
be.
A
C
All
right,
we've
got
about
seven
minutes
left
and
I
want
to
make
sure
that
we
cover
everything
that
we
have
here:
prioritization
operators,
so
we
we
know
that
folks
are
all
working
on
operator.
Stuff
I'll
be
going
again,
this
Thursday
for
the
text
on
operator,
working
group
and
obviously,
we've
got
the
operators
catalog
stuff.
That
Brian
is
working
on
and
we'll
get
an
item
created
for
that
on
the
board.
Anything
else
in
terms
of
the
operator
stuff
that
we
can
do
right
now.
E
Sorry
Dwayne
go
ahead.
Oh.
B
I
was
thinking
that,
with
everything
we're
doing,
there's
a
still
a
great
opportunity
to
take
stuff
and
and
build
into
the
glossary.
So
when
The
Operators
are
going,
there's
an
opportunity
to
also
Define
prerequisites
for
people
for
the
for
a
certain
threshold
that
people
need
to
be
proficient
in
operators.
So
we
could.
B
Those
are
a
lot
of
there's
a
lot
of
operated
terms
that
would
fit
in
same
thing
for
pipelines
and
that's
the
way
we
can
maybe
build
our
newcomers
up
to
so
so
they
can
be
proficient
and,
and
but
that
may
be.
You
may
need
to
generate
a
special
list
of
maintainers
to
capture
that
long
term,
but
I'll
do
my
best
until
then
yeah
yeah.
C
Just
grab
what
resources
you
can
find
online
that
do
a
good
job
of
explaining
operators.
You
know
and
collate
them
into
a
like
a
set
of
links
or
something
like
that.
Yeah
like
like
El
Mika,
was
saying.
We
don't
want
you
to
spend
a
lot
of
time,
rewriting
stuff,
that's
already
out
there,
but
if
you
can
find
what's
out
there,
that's
that's
the
easiest.
That's
the
best.
I
was
talking
to
say
it's
the
most
well
written
to
help
people
understand
operators,
then
I
think
that
that's
that
puts
us
ahead
of
the
game
for
sure.
E
So
Jamie,
if
you're
in
your
your
tactile
meeting,
find
out
how
they
create
the
catalog
index
of
operator
bundles
for
techton,
because
that
repo
is
horrible,
yeah
same
as
like
it's
the
same
as
the
K
native
one.
It
uses
the
Google's
internal
process
of
how
they
used
to
build
things
and
it's
different
from
every
other
operator.
Cattle
yeah
yeah.
C
So,
like
I
said
they
are
reworking
stuff
over
the
next
couple
months:
they're
completely
redoing,
you
know
their
their
repos
and
stuff
like
that.
So
we
may
have
an
opportunity
to
say
Hey.
You
know
this.
Here's,
the
community
organization
that
wants
a
community
group
that
wants
to
help
and
support
you
getting
this
out
here,
are
some
suggestions
that
would
allow
us,
as
volunteers,
to
contribute
more
to
the
project
and
to
utilize
the
operator
more
in
okd
for
sure
yeah
excellent
I
will
do
that.
All
right.
We
have
five
more
minutes.
C
C
Friday
so
but
yes,
I
have
it
and
I
will
be
posting
Social,
Media
stuff
and
the
meeting
videos
and
all
that
stuff.
Today.
C
Yeah
Jack:
do
you
want
to
let
folks
here
know
and
just
so
that
they
can
share
with
people
as
well,
yeah.
F
Sure
so,
basically,
two
days
like
on
Thursday
I'll,
be
at
the
kubernetes
community
days
in
in
Amsterdam,
which
is
a
like
a
smaller
scale,
similar
to
to
kubecon.