►
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 will also include the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope.
More info at https://okd.io
A
All
right
welcome
everybody.
We
will
wait
about
30
seconds
more
to
see
if
anyone
else
pops
in
and
then
we'll
get
started.
I
did
put
the
meeting
notes
in
the
chat
there
as
well.
A
All
right,
let's
get
started
here
and
we'll
do
a
quick
round
of
introductions
for
folks
that
are
going
to
be
watching
the
recording
that
maybe
aren't
familiar
and
we'll
start
out
with
diane.
B
All
right:
well,
I
am
the
director
of
community
development
here
over
at
red
hat
and
one
of
the
longtime
co-chairs
co-conspirators
on
okd
in
origin.
Prior
than
to
that,
so
I
think
I
probably
have
the
longest
running
history.
So
if
you
have
questions
about
why
we
did
things
the
way
we
do,
I'm
probably
to
blame,
so
yeah
welcome
and
maybe
d3.
Why
don't
you
go
next
because.
C
Okay,
hi
everyone.
I
am
working
for
red
heart
and
I
joined
this
meeting
to
actually
I
want
to
contribute
to
okd
and
just
looking
forward
to
understand
things
better
yeah.
That's
all.
C
Hi
I
I
have
been
with
red
hat
for
five
years
now,
but
I'm
new
to
the
steam
customer
focused
engineering
team,
and
because
of
that
you
know,
I'm
you
know
learning,
okay,
more
awesome
cool.
We.
D
E
A
So
let's
jump
right
into
the
agenda
item
of
current
projects
and
mike
isn't
here
to
talk
about
the
status
of
moving
things
over.
Let
me
take
a
quick
look
at
that
pull
request
to
see
what
the
status
of
that
is.
Let's
see.
B
It's
ready
to
merge,
we
can
merge
it,
but
I
think
he,
the
last
I
talked
to
him.
It
wasn't.
He
was
waiting
for
more
feedback
from
the
higher
the
the
uber
okay.
A
I
see
yeah,
so
it
looks
like
updated
eight
days
ago,
so
we
will
put
that
on
hold
until
the
next
meeting
to
see
if
we
have
an
update
for
that,
a
charter
updates
and
placements.
So
the
main
group
signed
off
on
putting
a
link
to
the
charter
in
off
of
the
main
website
off
of
okd.io.
A
It's
just
a
question
of
folks
notice
that
there's
a
couple
of
inaccuracies
and
some
things
that
are
outdated,
so
it'll
be
up
to
one
of
us
or
many
of
us
to
take
a
look
at
that
and
look
for
anything
that
is
outdated
or
incorrect
and
updated.
A
So
does
anyone
else
want
to
volunteer
I'm
going
to
take
a
crack
at
looking
it
over?
Someone
else
want
to
do
give
a
second
pair
of
eyes
to
help
me
out
with
that.
B
A
Should
but
if
not,
let
me
I'll
check
and
find
out
we'll
get
that
squared
away
for
sure,
yeah.
Okay,
let's
see
here
and
update
respective
calendar,
invites
so
I
updated
the
main
meeting
one.
I
haven't
updated
this
meetings
calendar
invite
yet,
but
I
will
updating
it
with
a
link
to
this
documentation
and
christian
did
give
me
right.
A
Access
over
the
calendar
invites
so
I
will
update
those,
and
I
noticed
that
actually
that
I
accidentally
did
it
as
html,
which
it's
showing
up
in
ical
funny,
if
you're,
if
you're
I'm
importing
it
via
ical.
So
I
will
fix
that.
So
you
don't
see
the
html.
That's
that.
A
And
then
that
leaves
us
actually
to
the
last
thing
in
our
agenda,
which
is
anything
more
from
brian
in
terms
of
inclusive
language
stuff.
Take
it
away
brian.
E
Okay,
so
I
did
the
review
using
the
the
tools
and
created
a
an
issue
on
github,
so
there
are
some
things
that
we've
got
to
do
and
a
lot
of
them
are
going
to
focus
around
when
we
rename
the
master
branch
to
main.
I
don't
know
how
the
site
is
built.
What
the
pipeline
is
behind
this.
B
Is
that
can
I
pause
right
is
that
the
okd
dot,
io
site.
E
B
E
The
link
to
the
pull
request-
sorry,
you
know
the
issue
into
the
chat
if
people
want
to
follow
so
yeah,
so
most
of
the
issues
are
around
the
master
branch
being
renamed
to
maine,
and
this
is
all
gonna
be
synchronized
and
done
as
one
sort
of
activity.
So
I
say
I
don't
know
what
the
pipeline
is
on,
how
the
site
gets
built.
E
There
are
a
few
references
within
the
site,
so
it
sort
of
links
back
to
the
raw
file
on
github
back
to
itself
within
the
in
the
into
the
repo
and
then
those
are
hardcoded
to
the
main.
The
master
branch
needs
to
go
and
get
changed
to
the
the
main
branch
and
there's
a
couple
of
other
things,
but
nothing
huge.
E
So
I'm
not
sure
is
that
something
within
red
hat
that
will
actually
look
at
that
in
terms
of
the
tooling
or.
B
I
just
went
in
and-
and
you
did
talk
about
this
at
the
I
didn't-
I
didn't-
watch
the
video
from
last
week-
I
missed
last
week,
so
it
did
get
talked
about.
I
assume
at
the
last
meeting
I
just
assigned
two
people
jerry
fala
and
will
gordon
they
are
red
hatters
they
are.
The
the
the
wizard
of
oz
is
behind
the
the
scripting
and
everything
that
builds
this
stuff.
B
Joseph
meyer
also
has
done
some
work
with
them,
so
I
probably
should
tag
him
as
well
to
have
a
look
at
the
issue
and
jerry
is
in
the
czech
republic,
so
he's
asleep
right
now,
but
and
not
quite
asleep,
but
probably
eating
dinner.
B
So
it
probably
won't
happen
right
away,
but
they're
pretty
responsive
depending
on
their
workloads
and
I'll,
probably
throw
a
note
in
for
for
joseph
also
to
comment
on
it
because
I
think
they're,
the
ones
that
have
to
actually
review
all
the
scripts
in
the
back
end
and
they
they
launch
the
automation
that
rebuilds
the
site
whenever
I
crash
it
or
edit
anything
so
they'll,
do
it
we'll
get
there.
E
B
Yeah,
so
let's
get
this
first
one
done
and
then
the
openshift
one
I
think
michael
burke
and
the
engineers
are
going
to
do
that.
We
don't
we
can't
make
them
do
that
they
have
to
do
it
and
they're.
E
All
right
and
yes,
anything
else,
you
need
to
help
with
happy
to
jump
in
and.
B
I
just
any
what
I
would
love
to
see
is
more
ibmers
coming
showing
up,
so
anything
you
can
do
to
you
know
cross,
promote
there
and
get
more
folks
from
ibm.
That
would
be
wonderful.
The
other
thing
that
and
we've
talked
about
this
before,
but
since
d
tree
is,
is
it
d
tree?
Is
that
how
you
say
it.
B
Okay,
I
can
do
that
pretty.
We
have
sort
of
a
a
little
bit
of
a
training
ground
for
looking
for
bugs
in
docs.okd.io
that
we're
using
right
now
and
michael
burke
and
I
have
walked
through
it
a
number
of
times.
But
one
of
the
things
we
we'd
like
to
encourage
the
customer
facing
engineers
and
any
newbies
to
do
is
to
do
an
install
of
okd
somewhere
on
whatever
hardware
red
hat
lets.
You
have
access
to,
whether
it's
aws
or
whatever,
and
then
as
you're
doing
it
walk
through
the
docs.okd.io.
B
The
latest
released
version
of
it
and
if
you
see
anything-
and
there
are
lots
of
things
especially
focus-
maybe
first-
because
we
keep
trying
to
get
this
done,
all
the
anything
that
references
rel
core
os
instead
of
fedora
core
os
or
okay,
the
wrong
thing
that
those
are
easy
lifts
and
you
can
look
in
the
issues
to
see
some
other
previous
docs
one
docs
related
one
for
how
we
structure
an
issue
for
a
docs.
We
tag
it
in
the
subject
line.
B
It
has
in
brackets
okay
d,
and
then
we
tag
it
with
docs
as
one
of
the
labels
and
then
assign
to
do
a
slash
assign
to
michael
burke
and
myself,
I'm
just
okay,
demul
or
2001's.
You
can
look
at
any
of
the
other
ones,
but
if
you
could
find
a
few
of
those
and
brian
I'd
really
like
to
just
get
you
to
have
log,
your
first
issue,
like
brian,
has
done
a
wonderful
thing
here.
B
You
know
do
for
those
and
then
with
the
new
release,
that's
coming
out
or
came
out
4.8,
I'm
sure,
there's
things
again
that
we
haven't
caught
and
then,
if
there's
stuff,
really
missing
in
our
documentation
in
in
the
generic
documentation,
there's
a
lot
of
other
documentations
like
the
charter
we
were
talking
about
earlier
and
the
guides
we
were
talking
about
earlier,
but
I
think
for
the
brand
nubians.
B
Yes,
those
folks,
I
think,
looking
with
us
fresh
eyes
on
the
docs.okd.io,
is
really
helpful
and
it
is
a
slimmed
down
version
of
the
openshift
docs.
B
With
that
michael's
team
has
overlaid
with
some,
I
I
would
call
them
patches,
but
I
don't
know
if
they,
the
pull
for
to
build
them,
is
slims
it
down
and
re-labels
and
re-edits
some
stuff.
So
we
don't
always
catch
everything
and
we
can
always
do
better.
C
E
D
A
But
yeah
these
are
named
open
shift
like
a
service
like
open
shift.
You
know
if
it's
open
shift
cluster
manager
or
openshift
whatever,
like
there's
going
to
be
things
that
will
stay
open
shift
because
the
actual
component
is
called
openshift
or
the
actual
service
is
called
openshift
something.
So
there
are
some
cases
where
it
would
stay
open
shift,
yeah,
it's
it's
kind
of
a
you
have
to
kind
of
look
at
is
like.
A
So
if
it's
an
operator
or
if
it's
a,
I
think
of
another
example,
if
it's
an
operator
or
a
service
or
anything
like
that,
that
has
open
shift
in
the
name.
It'll
generally
stay
open
shift,
but
always
best
to
file
something
that
michael
can
take
a
look
at
and
then
just
to
verify
that
that's
the
case.
A
You
know
because
it's
like
the
the
some
of
the
operators
have
open
shift
in
the
name
of
them
for
sure
in
some
of
the
some
of
the
services,
so
I
did
post
an
a
new
business
item
which
is
create
a
docs
process
document.
A
If
someone
wants
to
take
that
on,
that
would
be
awesome,
which
is
diane,
has
given
the
same
spiel
multiple
times
about
how
we
go
through
this
process,
and
it
might
be
helpful
if
there
was
actually
a
document
that
says
you
know
when
you
come
across
something
like
this
file
a
ticket
here
and
tag
it
this
way,
etc,
etc.
So,
if
someone
here
wants
to
take
a
crack
at
it,
that
would
be
great.
A
Yeah,
exactly
yeah
yep
all
right
is
there
anything
else
that
we
need
to
cover
at
this
meeting,
we're
only
18
minutes
after,
but
we
covered
our
current
agenda.
I
don't
like.
I
don't
think
we
necessarily
need
to
have
a
meeting
just
to
have
a
meeting
if
we've
gone
through
our
materials.
Brian,
it
looks
like
you
have
something.
A
30Th
of
june-
oh
yeah,
that's
right!
We
were
going
to
go
through
that
yeah.
B
E
Your
screen
brian
and
walk
us
through
it
again,
just
so
refresh
everybody.
This
might
be
a
challenge.
I've
never
done
this
on
here.
So
let
me
I
have
got
the
right
permissions
and
plug-ins
and
whatever
else
I
need
to
do
that.
A
Worst-Case
scenario
you
might
have
to
rejoin
if
you
have
to
set
security
permissions
to
allow,
but.
C
E
E
I
can't
get
rid
of
the
same
thing.
Okay,
so
I
mean
what
I
tried
to
do
is
really,
as
I
sort
of
got
in
involved
in
the
community,
so
I
mean
the
way
I
usually
do
it
as
I
look
for
a
few
weeks
just
to
try
and
work
out
as
a
community
works
and
and
then
I
I
just
sort
of
really
made
some
notes
on
some
of
the
challenges.
E
I
think
this
is
a
slightly
different
community
because
it's
based
on
alongside
a
project,
a
commercial
product,
so
one
of
the
things
that
I'm
I'm
still
struggling
with
is
as
a
community.
What
can
we
do
and
what
are
we
sort
of
be
holding
on
the
product
team
to
do?
But
one
thing
I
I
did
find
is
I
I
looked
at
the
okd.io
site
and
I
just
made
some
sort
of
comments
on
some
of
the
challenges
that
I've
seen
and
and
some
of
the
confusion
that
I
I
come
up
with.
E
So
it's
probably
this
bit
so
there's
there's
all
these
sections
on
the
actual
front
page,
but
a
lot
of
them
point
back
to
the
same
page.
So
I
is
you
wanting
to
sort
of
go
deeper
and
find
out
more.
It's
frustrating
that
all
you're
doing
is
jumping
down
the
page
to
the
next
section
where
you
were
hoping
to
maybe
go
a
little
bit
deeper
and
I
think
one
of
the
one
of
the
the
the
issues
is
it's
like.
There
was
a
lot
of
places
to
find
out
where
stuff
was
so.
E
I
mean
it
took
me
a
while
before
I
found
out
the
blog
with
the
the
live
install
session,
that
you
run
the
workshop
that
you're
on
and
there's
a
lot
of
really
really
good
information
in
there
and
but
it
actually
took
me
a
while
to
actually
get
around
to
finding
that
particular
blog
and
following
it
on
because
a
lot
of
the
technical
information
in
terms
of
how
you
get
started
and
was
in
that
set
of
videos,
I'm
seeing
quite
a
lot
of
confusion
in
terms
of
what
we
use
to
do.
E
B
Should
be
gone
now,
that's
a
remove
thing
and
the
google
group
and
the
mailing
list
are
the
same
thing,
but.
A
B
E
Sorry
go
ahead,
no
go
ahead.
Go
ahead.
I
mean
the
one
thing
that
that
I
I
became
very
aware
of.
Is
we've
actu
we're
actually
supporting
two
communities,
two
different
communities,
we're
supporting
the
users
that
need
help,
but
don't
really
want
to
come
in
and
be
part
of
the
sort
of
vienna
group
that
wants
to
help
and
contribute.
E
E
So
I
actually
think
that
it
would
be
useful
to
actually
have
a
support
on
maybe
a
commun,
a
contribution
community
or
something
separate,
the
two
out
and
and
and
have
something
so
yeah.
I
just
decided,
I
just
put
it
into
a
post
in
terms
of
where
I
sort
of
got
stuck
or
was
confused
about
things
and
and
I'm
going
to
add
another
one
to
the
list
is
the
actual
okay
that
I
o
the
technology
that
that's
using
isn't
document
friendly.
B
No,
it's
not
it's
a
yaml
based
framework
and
yeah.
It's
it's
it's
what
I
yeah,
so
I
I
have
to
say
I'm
very
buddhist
about
the
site
and
maybe
too
buddhist
about
it.
I
I
love
to
let
other
people
edit
and
and
do
it,
and
I
I
practice
non-attachment
so
to
to
this
site,
which
I
I
do
take
all
the
the
blame
for.
I
basically
created
it
out
of
nothing
so
yeah
the
framework,
that's
under
it.
I
I've
had
a
couple
of
iterations
of
it.
B
Joseph
meyer,
who
is
now
not
coming
to
the
docs
meetings,
did
an
update
to
at
least
get
it
to
the
latest
versions
of
the
things
that
were
used.
The
frameworks
and
things
which
was
a
good
help.
B
There's
been
a
little
bit
of
background
stuff
inside
of
red
hat,
to
maybe
port
it
over
to
drupal,
but
there
are
no
resources
to
help
with
that
so
and
anyways
long
story
short.
I
have
the
two
people
that
I
tagged
in
your
inclusive
language
thing
will
gordon
and
jerry
fala,
who
are
sort
of
assigned
and
resigned
to
helping
me,
keep
it
keep
it
alive.
I
am
not
adverse
to
moving
it
to
something
else.
That's
really
not
a
problem
for
me.
B
It's
just
main,
you
know
ongoing
maintenance
and
love
and
care
for
it
is
has
been.
It
has
been
the
thing
we
don't
have
a
lot
of
resources
on
it.
So.
E
Okay,
I
have
used
a
technology,
but
I
ported
another
community
within
ibm
over
to
and
I
believe
the
k
native
community
are
looking
at
as
well
who's
investigating
mk
docs.
It
means
that
once
you've
got
your
templates
and
css
set
up,
all
documentation
is
marked
on
pure
markdown,
so
to
actually
write
content.
E
Even
if
you're,
not
a
markdown
expert,
you've
got
about
five
minutes
of
learning
the
heart,
those
and
syntax
features,
and
then
you
can
write
documentation.
It's
it's
just.
When
I
looked
at
what
mike
had
done,
you
need
to
be
a
full-on
sort
of
front-end
web
developer
to
to
add
content
with
that.
So
again,
if,
if
there's
anything
that
we
can
put
up
like
a
beta
site
and
and
let
people
have
a
look
at
it,
I'm
happy
to
maybe
do
that.
B
Yeah,
no,
we
definitely
definitely
could
do
that.
What
I
would
suggest
is
like
so
some
of
these
things
that
you're
suggesting
here
you're
welcome
to
pull
make.
If
you
make
an
issue,
I
will
merge
it
or
I
think
jamie
now
has
merged
privileges.
B
If
you
make
an
issue
against
the
okd
dot,
io
repo,
which
I
think
you
can
see
and
do
I'll
definitely
accept
the
merges
and
and
do
that,
some
of
it
is
yeah.
The
framework
that
I'm
using
is
is
not
optimal
and
a
more
dock
space
one.
I
there's
always
one
porter
sh.
I
think
it's
porter
sh
is
my
go-to
example
of
what
I
think
is
brilliant.
Let
me
see
if
I
can
find
that
one
and.
E
Because
I
I
notice
the
tool,
that's
the
catalog
source
builder,
it's
a
red
hat
project.
I
noticed
they
were
using
a
different
technology.
B
I'll
just
throw
this
in
the
chat
this
is.
This
is
if
I
had
a
fantasy
land
and
I'm
not
sure
what's
under
the
here.
This
is
the
website.
The
woman
who
runs
this.
B
The
docs
for
here
is
also
in
the
cube
contributor
project
as
well,
so
she's
doing
some
other
things
and
she's
just
done
some
brilliant
stuff
that
and
that
that's
my
fantasy
life,
that
we
have
enough
resources
to
do
something
along
that
lines
hasn't
happened,
but
I'm
quite
willing
to
to
work
with
folks
to
to
move
it
to
something
there.
What
was
the
the
link
of
the
site
that
you
did
for
ibm
and
if
you
go
to
cloud
native.
E
E
This
shows
you
what
the
templates
can
do.
So
if
you
just
look
at
that,
that's
the
same
underlying
technology,
but
just
with
a
different
template
applied
to
it.
So
you
can
actually
change
it
to
what
you
want,
but
the
good
things
are
you
get
a
good
menu,
you
get
in-page
navigation
and
then
you
get
a
full
site
search
and
it's
all
a
static
website.
E
A
E
A
B
B
Yeah,
this
is
very
nice,
it
looks
it.
It
looks
less
like
a
landing
page
for
a
project
like
if
you
look
at
some
of
the
github
landing
page
people
and
more
to
me
like
documentation.
So
yeah
now.
E
If
you
look
at
what
we
did
on
the
cloud
native
toolkit,
we
created
a
custom
template
just
for
the
front
page
and
when
you
click
into
any
of
the
documentation,
you
come
into
a
more
documentation,
site,
okay,
because
they
wanted
the
front
page
to
look
more
like
the
projects
opening
page
and
then
after
that
you
go
into
the
documentation
stuff.
So
it's
it
is
customizable,
and
if
this
is
something
that
we
feel
is
a
better
direction,
I'm
happy
to
do
the
core.
B
B
Thing
is
yeah,
so
my
preference
I
mean
I
I
like
it.
I,
like
anybody,
doing
organic
reorganizing,
the
stuff
and
making
it
more
usable,
but
something
a
little
bit
more
welcoming
and
that's.
I
think
what
I
like
about
the
porter
one
is
that
it
has
the
what
is
stuff
it
has
how
to
get
on
the
landing
page
thing,
and
if
you
take
a
look
at
that
yep
it
it's
yeah,
and
I
mean
at
this
I'm
sure
the
cncf
paid
her
to
do
it
and
she
works
over
at
microsoft.
A
Actually
yeah,
I
think,
in
early
winter
or
something
yes,
can
I
pull
things
back
a
little
bit,
so
we're
sort
of
focusing
on
the
technology
right
now.
One
thing
I
think
would
be
helpful
to
talk
about.
Is
this
division
between
or
the
boundaries
between,
the
working
group,
the
community,
that's
sort
of
around
the
working
group
and
the
larger
community?
That's
the
users!
I
don't
think
that
that's
well
delineated.
A
A
I
sort
of
thought
that's
what
the
google
group
was
about,
but
we're
seeing
support
questions
getting
posted
to
the
google
group
that
to
me
seems
like
we
should
instead
have
a
google
group
that
is
or
in
addition
have
a
google
group
that
is
like
okd
support
or
okd
community,
or
something
like
that,
as
opposed
to
okd
working
group.
B
Yeah,
the
I
think,
with
google
groups,
we
could
create
another
google
forum
that
was
okd
working
group
dash
docs,
another
one
that
was
dash,
support
or
answers
or
whatever
we
wanted
to
call
it,
but
the
the
theory
behind
having
just
the
single
one
is
because
we
had
so
many
limited
resources.
People
would
be
having
to
watch
all
of
these
different
spaces
and
keeping
everybody
in
one
and
in
the
beginning,
worked
okay
and
moving
people
who
were
asking
support,
type
questions
over
to
the
kubernetes
slack
was.
B
What
we're
trying
to
do
is
that
if
people
were
asking
support
questions
to
make
them
nudge
them
over
there
and
that's
kind
of
where
I
nudge
everybody
like
I
have
to
monitor
the
facebook
openshift
stuff,
you
know
at
all,
you
know
linkedin,
you
name
it
and
trying
to
get
them
all
to
one
place.
B
It
is
easier
for
me
and
for
I
think
that,
but
I
think
I
mean
you're
right.
There's
got
to
be
some
segregation
of
threads
about
support,
so
maybe
we
could
look
at
the
google
group
and
create
a
forum
within
their
that
google
group
that
was
just
support
questions
and
then
one
that
was
docs
question.
I
think
you
can
do
that
with
google
groups.
I
haven't
tried
or
played
with
it,
but
with
the
same
google
forum
just
creates
subtopics
or
sub
forums.
A
Think
so
I
I
I'd
be
happy
to
poke
around,
for
I
don't
know
that
you
gave
me
any
access
or
not.
I
don't
know,
but
I'd
be
happy
to
poke
around
and
look.
B
Around
and
then
we
can
just,
we
could
do
one
on
one
and
create
those.
If,
if
you
don't
have
permission,
just
ping
me
and
slack
and
we
can
do
it.
A
I
just
think
that
would
be
good
because
we're
it's
things
are
getting
a
little
bit
mixed
up
and
and
it's
hard
to
wade
through
sort
of
support,
questions
and
want.
I
want
to
use
it
to
post,
like
group
like
working
group
related
stuff,
but
then
it
sort
of
gets
buried
with
the
support
questions.
I
think
that
sort
of
gets
people
sort
of
disconnected
from
it.
B
B
Well,
I
was
going
to
say-
and
these
customer
facing
engineers
like
d3
here
we
can
get
them
to
monitor
the
support
as
well
like
so
there's
about,
I
think,
there's
60
of
you
or
some
crazy
number
of
them
that
are
being
onboarded
into
the
customer
facing
engineers,
and
this
is
there's
wanting
to
use
okd
as
their
training
ground
and
to
inspire
them
to
be
more
open,
sourcy,
which
we
like
a
lot
at
red
hat.
B
So
maybe
what
we,
if
we
separate
it,
and
then
we
can
throw
some
of
the
customer
facing
engineers
to
the
wolves,
but
really
the
the
traffic
we've
been
trying
to
direct
it
to
either
openshift
dev
or
openshift
users
in
the
kubernetes
slack.
Because
then
it's
not
just
the
okd
working
group.
That's
looking
at
it!
It's
the
broader
all
the
open,
shifties,
all
the
flavors
of
them.
Those
engineers
are
there
too,
who
can
pop
in
and
answer
a
question.
A
Yeah
and
it
may
be
helpful
to
look
at
the
way
that
we
label
things
there's
you
know
the
community
link
sort
of
is
split
into
stuff,
related
to
sort
of
support
and
documentation,
and
then
also
the
working
group
like
connect
to
the
community
is
actually
working
group
stuff.
But
I
don't
know
that
the
working
group
is
the
community
so
much
right.
So
there's
the
user
community
and
then
there's
the
working
group
community.
A
So
it
might
be
better
or
helpful
to
tease
that
out,
as
we
modify
the
website
to
make
that
a
little
bit
clearer.
E
A
B
B
You
know
we,
I
I
do
own
the
openshift
common
slack,
so
if,
for
some
reason
we
we
don't
like
that,
that's
too
much
of
a
high
gate
for
people
to
to
fill
out
that
form.
Then
I
can
always
create
a
create
a
forum
and
a
slack
channel
in
the
openshift
commons
one.
But
again,
that's
yet
another
thing
for
people
to
monitor
and
get
notified
by,
so
the
fewer
honestly,
the
fewer
of
them
the
better.
B
B
E
E
Because
again,
I
think
I
looked
at
some
of
the
sort
of
first
issues
or
sort
of
a
good
first
issue,
and
one
of
them
was
about
memory,
and
it
took
me
forever
to
realize
that
the
openshift
installer
for
kd
is
actually
in
vadim's
gate
repo.
It's
not
within
the
open
source
gate
repo.
So
I
only
found
that
out
by,
I
think
it
was
in
one
of
the
videos
I
noticed
where
he
was
actually
poking
around
in
gates.
So
we
actually
don't
say
that
anywhere.
So
just
having
a
technical.
A
I
do
not
think
so,
and
I
there's
vadim
had
talked
a
couple
months
ago
about
wanting
to
provide
more
documentation
on
also
like
building
the
installer
and
people
being
able,
because,
like
joseph
in
fact,
had
wanted
to
do
his
own
install
tweaked
to
his
liking,
and
we
don't
have
documentation
on
that.
So
there's
a
little
bit
in
the
repo,
but
there's
nothing,
that's
a
a
sort
of
step-by-step
how
to
do
it
type
thing,
and
we
could
do
that
and
that
would
also
encompass.
Where
does
it
live
right?.
B
So
we
could
kill
like
three
birds
with
one
stone.
If
you
can
frame
outline,
maybe
brian
and
jamie
what
it
is.
You
want
him
to
cover
and
feed
it
to
me,
and
I
can
I
can
record
it
on
mondays.
I
do
amas
with
upstream
project
leads
as
part
of
openshift
common,
so
I
can
get
him
to
just
do
a
session
on
that
sometime
in
august
and
then
we
can
get
it
transcribed
and
then
feed
it
back
through
the
docs
group
here
to
turn
it
into.
B
B
So
if
you
can
give
me
enough
meat
about
what
you
think
he
should
cover,
we
try
and
protect
vedim
from
any
extra
workloads,
so
the
clearer
we
can
be
about
the
steps
we
want
him
to
cover
and
that
thing
that
is
in
his
own
repo,
probably
shouldn't
be
there,
and
we
should
be
able
to
pull
it
into
something.
B
E
C
B
Cool
I'm
happy
to
pay
to
get
it
transcribed
so
that
you're
not
trying
to
transcribe
it
I'll
get
that's
easy
to
do.
There's
tools,
easy
tools
with
youtube
to
do
that
now,
so
if
we
can
figure
it
out
and
then
make
the
ask-
and
he
will
be
he's
in
europe,
so
he
will
be
on
better
vacation
time
than
me
here
in
canada,
but
I
don't
know
when
he's
planning
on
taking
them,
but
I
hope
he
is
taking
them,
but
yeah
that
that's
a
brilliant
idea.
A
Sorry,
no,
no,
he
did
an
overview
for
the
what
talked
about
it
was
the
first
sort
of
big
talk
that
we
did
this
year
in
february
or.
E
E
A
All
right,
we
will
then
most
definitely
loop,
that
in
brian-
and
I
will
work
on
that
and
brian,
and
I
also
have
a
shared
desire
to
see
pipelines
in
okd
very
soon,
so
we'll
find
out.
That's
the
other
thing
that
needs
to
happen
is.
I
would
like
to
work
with
vadim
to
get
a
clearer
sense.
He
did
delineate
the
operators
a
little
bit
better
on
christian's
issue,
which
listed
all
the
operators
that
need
to
be
moved
over,
but
there's
not
a
clear
sort
of
explanation
of
okay.
A
This
one
actually
needs
some
development
work
on
it
or
we
need
to
approach.
You
know
the
the
folks
that
are
hosting
it
currently
and
have
them
do,
but
like
it's
a
little
bit
unclear
still
on
some
of
those
what
needs
to
be
done,
except
for
the
ones
that
are
in
red
hat's
hands.
A
It's
clear
that
those
are
and
actually
there's
something
vadim
said
something
about
pipelines
and
four,
eight
or
four
nine
that
something
was
going
to
change,
and
I
can't
remember
what
it
is,
but
it
might
be
that
pipelines
will
be
made
available
for
okd
directly.
I
don't
know,
but
we
can
ask
them
about
that.
A
E
Guess
the
first
thing
is,
is
how
do
we
go
and
add
a
new
catalog
source
that
gets
added
as
part
of
the
okd
installer?
That
we
can
then
start
adding
operator
bundles
into
right?
Is
that
I
think
having
that
that
that
first
bit
of
infrastructure
then
means
that
there's
a
way
of
then
adding
an
additional
operator
bundle
into
it,
and
I
mean
some
of
the
operators.
I
think
they
they
should
go
into
operator.io
they're.
Actually,
community
operators
they're
not
an
okd
operator,
they're
a
community,
but
things
like
pipelines
get
offs.
A
E
A
Yeah
there
was
one
thing
that
it
predates
you
by
a
couple
months
is
when
we
did
start
working
on
the
site
revamp.
Last
winter
there
was
a
a
there,
was
feedback
from
vadim
and
christian
about,
or
I
should
say
against
using
the
word
support
in
our
website
and
in
our
documentation,
because
it
gave
the
impression
that
people
were
entitled
to
something
by
using
okd
were
entitled
to
support
in
some
fashion,
and
so,
if
we
can
think
of
a
better
word
than
that,
that
implies
like
community
support
or
something
like
that.
Then.
B
Again,
I
would
go
back
to
sort
of
the
the
porter
dot
sh
site
and
maybe
the
helm
site
as
well
to
see
what
the
verbiage
is,
that
they
use,
because
they
are
open
source
projects
that
don't
really
have
a
supporting
thing
behind
them.
So
I
that
and
I'm
just
going
to
peek
again
at
porter
and
see
which
what
they
I
just
I
personally
yeah.
B
So
there's
install
quick,
stop
community
learning
and
docs
on
the
porter
site
and
I
think,
under
the
go
to
the
community
talks
about
engaging
with
the
community
as
opposed
to
getting
support
from
the
community.
B
Using
the
word
engaged
to
ask
questions
show
off
something:
you've
created
collaborate
with
others,
troubleshoot
something
you
should.
You
aren't
sure
is
a
bug
yet
and
just
say,
hi
to
introduce
yourself
and
then
it
says
at
the
bottom
of
it
that
bug
reports
should
still
be
github
issues
but
for
the
rest
start
here
and
get
the
conversation
going,
so
no
no
go
ahead
their
their
thing.
Is
they
really
don't
say
the
word
support
and
that's
that's
kind
of.
A
A
B
A
Oh
and
they
just
use
the
discussion
section,
so
that's
interesting,
so
porter
just
uses
the
discussion
section
of
github
of
their
github
repo.
We
could
do
that
yeah,
because
that's
sort
of
what
vadim
was
directing
folks
to
use
anyway.
So
instead
of
pointing
people
to
the
google
group
or
appointing
people
to
black,
we
could
point
them
to
the
discussions
which
would
allow
things
to
get
tagged.
It
would
allow
questions
to
be
listed
as
answered
or
not
answered,
etc,
etc.
B
A
Oh
and
see
their
community
link
for
helm
goes
to
their
discussion
section
or
actually
well,
it
goes
to
their
issues,
but
it's
still
it's
it's
yeah,
much
less
of
a
hurdle
than
joining
the
slack.
B
Yeah
yeah
and
you
know
I'm
and
then
slack
just
becomes
helm
users
and
you
know
at
home
there,
okay,
cool,
thank
you
cool,
all
right,
I'm
so
those
and
compared
to
the
cloud
native
toolkit
site,
which
I
really
like
like.
If
you
look
at
helm,
docs
or
even
docs.okd.io,
they
have
that
that
same
same
look
and
feel
as
your
site
does,
for
the
native.
So
for
the
cloud
native
toolkit.
So
there's
a
distinction
between
how
we
structure
docs
and
how
we
create
a
welcoming
landing
page.
That's
easy
to
navigate!
B
B
E
A
What
are
the
steps
that
would
be
needed
to
to
set
up
for
brian
to
set
up
an
example
and
for
us
to
get
dns
to
point
to
it?
You
know
like
beta
dot,
okd
dot,
io.
E
Yeah,
I
mean
the
way
we
did
it
for
the
cloud
native
toolkit.
Is
we
just
use
github
pages
and
then
we
just
put
a
cname
redirect
into
pizza.
So
if
you
go
to
betadot,
that's
exactly
what
you
get.
You
go
to
a
git,
github
repo
that
uses
github
pages.
We
use
github
actions
to
actually
run
the
script
that
convert
the
mark
down
to
the
static
site.
B
I'm
totally
fine
with
it.
It
needs
to
still
have
the
footer
on
it
and
some
of
the
branding
with
the
panda
and
stuff
like
that
that
we
have
on
the
okd.io
site
and
then
diane
needs
to
be
trained
on
it.
But
the
more
we
can
have
something.
That's
not
like
the
yaml
bass
and
when
you
see
the
css,
don't
yell
at
me.
E
I
mean
what
I
can
do
is
I
can
have
a
go
at
just
creating
a
gate
repo
in
my
own
personal
and
have
a
good
way
to
create
that
landing
page,
putting
the
docs
behind
it
and
happy
to
invite
other
people
in
if
they
want
to
play
around
with
it
as
well,
and
we
can
set
up
a
beta
site.
And
then,
when
we're
happy
within
the
docs
working
group,
you
can
then
sort
of
communicate
it
to
the
wider
working
group
and
get
their
feedback
and.
B
And
then
it
would
be
when
we
get
to
that
point
will
and
will
gordon
or
jury
follow,
can
do
the
redirect
for
the
dns
or
for
us
as
as
we
need
it
done.
I
don't
think
they
will
they.
They
will
not
be
disappointed
to
lose
having
to
maintain
this
site
with
me.
Yeah
the
commons,
the
openshift
commons
site
is
the
same
framework
and
so
is
project
quay,
dot
io.
B
E
B
A
What
I
can
do,
thank
you
very
much,
and
let's
can
we
formalize
your
email
so
that
we're
not
going
back
to
the
email,
like
maybe
put
it
as
an
issue
or
something
like
that
in
the
or
a
discussion
item
in
the
in
the
okd
repo
or
in
the.
A
So,
if
you
do
that,
then
that
way,
we're
not
digging
for
an
email
thread
and
we
can
actually
like
break
it
down
and
assign
people
and
things
like
that
and.
A
B
Let's
do
it
as
a
discussion
item.
I
think,
because
then,
that
that
that
does
again
puts
it
where
we
we
put
our
money
where
our
mouth
is
say
where
we
want
people
to
go
for
community
stuff,
and
then
we
can
work
through
all
of
that
and
yeah.
That's.
That
would
be
a
great
start
and
I'm
looking
forward
to
getting
off
editing,
yaml
files.
A
B
All
right
and
and
jamie
ping
me
when
you
get
a
moment
free
in
your
schedule
and
we
can
walk
through
the
google
group
thing
and
see
if
we
can
figure
it
out.
If
you
can't,
if
you
don't
have
permission
one,
I
have
to
get
you
permission
and
two.
I
will
just
do
it
on
the
fly.
I'm
sure
there
is
a
a
you.
Can
google
it
how
to
fix
that
thanks
all
right
folks,
thanks
all
right,
take
care
bye-bye
take.