►
From YouTube: OKD Working Group Meeting 08-30-2022
Description
The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group includes the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group produces supporting materials and best practices for end-users and provides guidance and coordination for CNCF projects working within the SIG's scope.
https://okd.io
A
B
B
Let's
take
a
quick
look
at
the
agenda
for
about
30
seconds.
Let
me
know
if
there's
anything
that
you
want
to
add
it's
pretty
hi
and
let
me
know
if
there's
anything
you
want
to
add,
remove,
modify
or
anything
like
that,
so
we'll
spend
about
30
seconds
at
that.
A
I'll
add
a
couple
things
in
the
okd:
the
upcoming
event.
C
Christian
it'd
be
nice
if
you
would
say
a
few
things
about
what's
been
going
on,
because
I
see,
there's
been
quite
a
lot
of
uptakes
going
into
the
repos,
and
so
it's
an
interesting
for
an
update
on
that
I.
Don't
know
what
they'll
do
it's
partly:
okay,
updater.
D
Absolutely
I
think
I'll
just
get
started
with
the
release,
update
real
quick
so
but
in
cut
a
new
release
10
days
ago.
D
That's
really
all
I
can
say
on
that
right
now
we
have
been
working
a
lot
on
Acton
pipelines,
but
there
is
in
the
okd
project.
There
are
no
free
pipeline
repositories.
One
is
the
okd7009
rebuild
repository.
We
might
rename
that
later,
which
is
essentially
a
pipeline
for
building
your
entirely
rebuilding
your
own
payload
and
currently,
that
is
with
cepthouse9,
but
that
pipeline
should
also
be
usable
to
create
your
own
Fedora
base.
Payloads
are,
if
you're
into
any
other
RPM
based
history.
D
You
can
probably
use
those
two
would
be
interesting
to
see
Susa
built
or
something
so
that
is
essentially
what
that
repository
is,
is
used
for.
We
have
one
of
my
colleagues
from
the
multi-arch
team
working
on
getting
that
work
with
arm
so
we'll,
probably
because
our
internal
Pro
system
won't
be
ready
for
arm
releases
quite
some
time
we
might
be
able
to
to
also
get
it
to
work
kind
of,
but
we
won't
be
able
to
have
full
multi-arch
manifested
payloads
in
Pro
for
some
time.
D
So
this
is
a
stretch
goal
for
the
okd7009
rebuilt
pipeline.
I
will
be
following
well,
we'll
be
kind
of
focusing
on
that
later
this
year.
Right
now,
what
we're
working
on
is
are
mostly
working
on
is
the
okd
Cosa
pipeline,
which
is
a
pipeline
to
run
coros
assembler
in
techtone
on
any
kubernetes
cluster.
D
So
essentially,
you
can
use
a
a
small
kind
kubernetes
in
Docker
when
that
is
in
podman
local
cluster,
deploy
techcom
pipelines
on
it
and
then
run
that
Pipeline
and
that'll
run
the
chorus
assembler,
which
essentially
wraps
RPM
OS
tree
compose
we're
currently
still
working
out
the
last
few
Kings
there
with
getting
it
to
to
do
what
we
wanted
to
do.
D
So
we
currently
have
problems
mounting
in
our
getting
into
the
compose
the
the
okd
RPMs
that
is
openshift
client,
openshift
hypercube,
which
aren't
available
in
a
a
proper
young
repository,
so
we're
creating
a
local
environment.
Rpm
Western
compose
that
doesn't
seem
to
be
to
be
very
happy
with
the
local
RPM
repo
anyways,
we'll
we'll
find
a
solution
for
that.
I
think
the
best
solution
for
that
will
be
to
actually
have
a
publicly
hosted
yum
repository.
D
D
It
called
the
rel9
server
OSD
repository,
that's
still
used
in
the
S
cause
9
manifest
we've
been
able
to
replace
that
with
for
cry
and
I'm,
not
sure
what
what
exactly
is
in
in
that
repository,
whether
it's
just
the
openshift
RPMs
or
also
the
cryo
RPMs
cryo
RPM,
we
can
get
from
copper.
Now
we
have
added
build
automation,
RPM,
build
automation
for
copper
that
me
for
cryo.
That
means
each
commit
will
be
built
on
copper
and
each
release
will
be
built
on
copper.
D
Two,
the
wheel
will
be
able
to
pin
to
a
release
or
just
consume
the
very
latest
from
there
for
cryo
and
cry
tools.
That
is
uncomfortable
cry
tools
isn't
automated,
yet
it
has
to
it's
manually
built
because
we
don't
have
to
pack
it
in
that
GitHub
organization.
We
use
the
packet
as
a
service
for
for
RPM
automation.
We
do
have
it
for
cryo.
Now
so
we'll
always
get
the
latest
prior
builds
from
copper
for
now
and
then
for
the
openshift
or
okd
RPMs,
openshift
clients
and
openshift
hypercube.
D
We
are
still
looking
for
a
solution,
so
I
think
eventually
we'll
host
that
somewhere
publicly
as
well,
which
can
then
be
used
also
by
the
by
the
s-cos
composers.
If
we
have
a
a
public
young
report
for
those
so
making
great
progress
there,
we
are
hoping
to
get
the
first
s-cos
build
done
this
week
and
then
the
next
steps
will
be
for
us
to
internally
set
up
a
release
controller
in
Pro
to
build
release
payloads
for
s-cos
or
okd
on
s-cos.
D
D
But
since
we
need
the
integration
with
CI
for
for
okd
on
S
cross,
we
will
use
the
internal
release
controller
instead
for
anybody
interested
in
building
their
own
payloads,
though,
take
a
look
at
the
okd
Central's
line
rebuild
pipeline,
and
for
the
time
being,
we
will
be
using
the
okd
Cosa
pipeline
to
build
s-cos
itself.
D
The
base
operating
system
and
the
boot
images,
and
also
the
image
that
contains
the
OS
tree
in
the
new
format
that
you
can
use
it
to
to
layer
your
own
things
on
it
or
even
remove
things
from
the
base.
That
is
all
possible
with
that
new
layered
images
format
that
RPM
os3
now
support
supports
natively.
So
we
can
actually
simplify
our
bootstrapping
process
quite
a
bit
going
forward
in
both
okd
on
s-cos
and
okd
on.
D
D
D
First,
with
your
help
from
the
community
to
do
to
fill
up
our
operator,
catalog,
really
to
do
bills
of
all
kinds
of
operators
and
release
them
to
okd
through
the
operator
Hub,
but
we'll
we
have
to
build
the
the
operator
bundle
somewhere,
and
this
tactile
pipeline
really
is
the
place
a
couple
of
folks
to
the
up
and
I've
kind
of
closing
the
loop
where
we're
now
on
operate.
D
First
with
that-
and
some
of
you
folks
should
have
gotten
access
already,
you
should
have
access
to
the
okd
working
group
namespace
on
operate
first
and
feel
free
to
mess
around
there.
Deploy
your
things,
try
not
to
overwrite
anything.
Anybody
else
has
done.
But
if
you
need
another
namespace,
you
can
essentially
open
a
repository
creating
one
for
you
in
the
operate
first
apps
repo
and
then
just
put
yourself
as
the
owner
in
there
you're
already
part
of
the
organization.
If
I've
added
you
to
the
team.
C
D
And
I
will
be
adding
more
people
to
the
team
list
once
we
once
we
hand
over,
so
we're
currently
doing
our
our
okay
Cosa
work
in
a
separate
namespace
and
once
we
are
confident
that
it
works.
We
will
hand
it
over
to
the
working
group
and
host
it
in
the
working
group
namespace
there
as
well,
and
then
we'll
probably
also
enforce
some
kind
of
get
Ops
so
that
manual
changes
are
are
corrected,
are
overridden
by
the
by
the
git
State,
essentially
enforced.
That
way,
yeah.
So
a
lot
going
on.
D
We
want
to
deliver
this
in
two
weeks
at
the
latest
in
four
weeks,
so
yeah
stay
tuned.
There's
a
lot
coming.
A
Now
you
know
and
open
sourcing
the
templates
for
the
pipelines
for
people
to
do
their
own
okd
Builds
on
whatever
they
want,
and
this
is
the
first
foray
into
using
the
operate
first
platform,
and
so
as
this
as
we
work
out
the
Kinks
on
this,
it
will
really
kind
of
change
the
nature
of
what
we
do
in
the
working
group
and
what
we're
able
to
do
in
the
working
group
on
custom
okayd
builds
to
maybe
there's
going
to
be
another
core
OS
out
there
from
somebody
else
who
might
want
to
build
it
using
some
of
these
things.
A
So
there's
going
to
be
a
bit
of
education
and
that's
kind
of
where
we're
going
to
have
to
talk
about
how
we
educate
the
entire
okd
Community
about
this.
These
streams
of
work
that
they
can
do
so
it's
moving
pretty
quick
and
that
one
of
the
things
that
I'd
like
to
do
is
once
we
have
an
MVP,
give
everybody
maybe
two
weeks
and
then
have
sort
of
another
sort
of
a
deployment
and
testing
Summit
and
get
everybody's
feedback
on
that.
A
Yeah
I
want
I,
might
call
it
a
hackathon
but
just
sort
of
a
hosted
Summit
for
everybody
just
to
talk
about
what
it
was
and
what's
missing,
what
works
and
what
didn't
and
what
you
know
and
get
an
overview
from
you
on
it.
So,
but
the
more
education
we
can
do,
the
better.
C
How
do
we
actually
kick
off
a
community
sort
of
effort
to
actually
create
that
operator
catalog,
because
I
think
that
that's
one
thing
as
Dan
said,
this
is
a
new
sort
of
new
sort
of
era
for
us,
where,
potentially
we
want
community
members
and
red
haters
to
actually
come
and
work,
which
means
it's
probably
outside
of
the
traditional
red
hat
working
environment.
But
how
do
we
do
that?
C
Do
we
arrange
a
convenient
time
where
we
just
have
a
kickoff
call,
and
or
do
we
try
and
do
it
all
virtually
you
through
a
repo
I'm,
not
sure
how
we
do
this,
but
I'm
Keen
to
actually
get
that
at
least
the
basics
of
the
catalog
there.
So
we
can
then
start
allowing
people
to
build
out,
but
until
we
have
anything
and
then
obviously
the
big
question
is:
how
do
we
push
it
into
the
okb
build,
so
it
gets
there
as
part
of
the
release.
C
I
have
no
idea
how
that
bit
works,
but
any
thoughts
on
how
we
move
this
forward
as
a
community,
because,
obviously
we're
trying
to
take
work
away
from
you
not
give
you
more
work.
So.
D
The
the
operator
pipeline
is
for
optional
operators
that
go
through
operator,
Hub
and
I
think
we
will
just
be
reusing,
or
we
actually
have
this
new
okd
catalog
that
we
haven't
been
using
and
we
can
use
that
I.
Think
part
of
the
the
okd
working
group
builds
and
then
we
just
add
a
a
second
catalog
source
to
our
default
sources,
and
it
should
be
enabled
by
default.
We
we
then
just
have
to
document
the
process
and
I
think
maybe
a
video
demo,
a
recording
of
how
that
works
might
be
a
good
good
way.
D
To
start
this,
where
we
just
pick
one
operator
and
build
it
in
the
pipeline
and
the
pipeline
should
also
then
essentially
include
a
step
to
release
it
to
push
it
to
Quay
and
maybe
even
to
to
open
a
PR
on
on
the
operator,
Hub
repo
to
kind
of
update
or
add
the
operator
and
I
I
haven't
been
really
focusing
on
that.
But
I
know
that
Luigi
who's
here
today
he
has
actually
with
with
Shireen
a
colleague
of
ours.
D
He
has
contributed
the
because
the
the
operator
pipeline-
and
they
are
both
on
the
on
the
CFE
team,
which
will
once
we
get
past
this
MVP
stage.
With
the
opdion
S
cause
phase,
they
will
actually,
as
a
team,
be
taken
over
the
release
engineering
for
all
of
okd,
so
that
includes
okay
dnf
course,
okd
on
s-course
and
possibly
also
operator
releases,
so
I
I
think
they
are
just
interested
in
having
these
operators
being
built,
not
necessarily
building
them
themselves,
but
so
I
think
Luigi
and
the
team.
D
Once
we
are
kind
of
in
a
place
where
we
say
this
is
production
ready.
Hopefully,
I
can
convince
Luigi
and
the
team
to
record
a
demo
of
how
it's
done
and
what
the
process
should
be.
It
should
really
all
be
build.
It
yourself
push
it
into
a
registry
and
then
use
git
Ops
to
get
that
release
or
that
bundle
added
to
the
operator
catalog.
D
So
really
it
should
be
something
you
should
be
able
to
do
from
the
command
line
or
it
you
know
automate
to
a
great
extent
and
yeah.
Hopefully
we
will
get
a
video
recording
of
how
that
works
and
we
can
publicize
it
that
way
and
obviously
I'm
I'm
also
always
happy
to
to
have
a
kind
of
a
hackathon
or
a
kickoff
meeting
where
we
do
a
live
session.
On
this.
A
D
Another
thing
I
wanted
to
mention:
we
want
to
also
release
those
tecton
pipelines
or
their
definitions
to
the
tecton
hub,
which
is
another
I
think
very
neat
neat
platform
to
share
things
just
so
we
get
you
know
the
most
out
of
it
and
we
bring
it
to
as
many
people
as
we
can
and
obviously
yeah.
That
is
to
encourage
anybody
to
run
the
pipeline
themselves.
Tinker
with
it
change
things
up
test
things,
and
you
know
eventually
contribute
back
to
our
working
group.
D
So
yeah
I'm
really
excited
about
this
effort,
and
it's
it
really
is
a
lot
right
now
we
have
big
changes
coming
in
okd
on
F
course,
with
the
introduction
of
layered
images,
we
have
a
new
okd
on
S
course,
flavor,
dream,
I,
think
we
well
I,
yeah
I!
Think
it's
a
it's
a
release
stream
I'm,
not
sure
what
what
the
yeah,
what
the
word
will
be
eventually
but
yeah,
and
then
we
obviously
want
to
really
build
up
our
story
for
the
okd
catalogs.
D
Therefore,
the
OPD
operator
catalog
and
really
make
that
a
success
and
all
of
it
I
think
as
a
base
tool
going
forward,
will
will
very
much
focus
on
tactone
to
run
the
things
in
pipelines
and
have
just
because
we
we
get
a
lot
from
that
framework.
It's
just
really
nice
to
use
and
feels
like
yeah.
It
gives
us
all
the
possibilities
we
need
to
build
these
things.
Obviously,
there's
always
you
know
all
contributions
are
welcome
if
you
have
another
tool
running
it
yeah
and
I'm.
B
D
We
each
each
of
the
pipelines,
has
its
own
repository,
I.
Think
opening
an
issue
there
or
even
better
a
pull
request,
is
probably
the
best.
Then
we
also
have
migrated
the
okd
repository
over
to
the
OPD
project
GitHub
org
now
so
that
still
is
a
great
place
as
a
kind
of
General
issue
tracker
from
where
we
can
then
triage
and
and
go
into
the
move
it
to
the
to
the
right
place
and
yeah.
D
Also,
the
chat
still
openshift,
users
and
I
think
we
should
definitely
bridge
that
with
the
Matrix
panel
as
soon
as
possible.
I
haven't
been
able
to
to
look
into
that
yet,
but
that
is
something
I
still
have
have
on
the
list
for
later
this
year.
D
So
hopefully
things
are
a
bit
more
kind
of
coming
together,
but
not
glittering.
The
community
into
many
too
many
channels,
yeah
I,
think
the
okd
repository,
and
especially
the
in
general.
The
okd
project
on
GitHub
now
should
be
the
main.
B
Focal
point
yeah
and,
as
Brian
pointed
out
that
you
know
we
want
to
start
blogging
about
sort
of
the
status
of
releases
and
the
status
of
the
build
process,
and
things
like
that,
so
you
know
this
is
something
the
community
development
team
had
been
talking
about,
and
so
we'll
probably
be
reaching
out
to
you
either
to
vet,
something
that
we've
written
or
to
you
know,
maybe
crowdsource
a
document
of
some
kind
so
that
we
can.
A
I
did
line
up
Luigi
and
a
few
other
folks
to
do
to
start
doing
some
videos
too.
So
we'll
do
that
and
now
Michael
who
just
showed
up
to
is
Mike
McEwen
is
up
for
another
yeah,
so
I'm
gonna
start
making
more
short
videos
to
express
our
interest
in
these
new
topics.
A
You
can
associate
them
with
the
the
blogs.
B
Sorry,
you're
right:
no,
no!
No!
No,
let's
Timothy!
Sorry
Timothy
yeah!
Well,
because
I
move
things
around
and
actually
let
me
ask
the
group
this:
does
it
make
more
sense
to
have
the
community
development
after
sort
of
the
red
Hatters
and
the
folks
like
I
feel
like
it
does
make
sense
more
to
let
the
folks
who
are
more
guests
for
external
stuff
to
be
able
to
to
give
their
updates,
and
then
we
do
Community
Development
after
does
that
make
sense
moving
forward?
E
All
right,
so
we
have
just
a
couple
of
smaller
dates
on
the
F
cos
side.
We
have
done
to
change
that.
Might
impact
okg
not
impact
that
much
but
like
people
have
visible
visible
change
for
kg
and
the
first
one
is
that
we've
landed
support
for
setting
a
password
in
the
group
bootloader
right
now.
This
is
not
supported
by
the
MCO,
so
that
I
would
work
only
on
first
boot.
E
You
set
up
the
right
thing:
I'm
not,
and
it
should
be
working
with
butane,
so
you
should
be
able
to
generate
the
Manifest
and
and
do
that,
work
I'm,
not
sure
how
much
it
has
been
tested
with
okd
yet,
but
it
should
work
with
fcus.
So
if
you
get
a
new
version
enough
of
this
of
Fedora
Quest
as
part
of
a
KD,
you
will
get
that
and
so
yeah.
Just
for
the
like
the
first
installs
you,
you
cannot
do
that
for
updates,
yet
as
part
of
the
MCU.
E
The
second
item
is
about
the
print
key,
the
kernel
output
level
on
the
console.
By
default,
we
had
a
reasonably
verbose
option:
candle
candle
output
level,
and
so,
if
you
had
a
local
server
with
a
lot
of
containers,
launch
and
see
that
ad,
it
could
get
slowed
a
bit
slow
down
by
the
output
on
the
console.
You
will
get
a
lot
of
output
in
the
console
for
and
for
more
servers.
That's
not
very
useful!
So
we've
lowered
the
the
output
so
yeah.
E
If
you
see
less
output
on
consoles,
that's
okay,
because
it's
it's
a
fixer!
It
does
that
after
the
system
has
booted
to
on
like
at
the
beginning,
you
will
still
get
full
output
for
debug.
If
you
have
any
issues
and
then
once
the
system
is
booted,
the
the
output
is
switches,
and
so
that's
for
the
federal
request.
Side
of
things
I
should
maybe
base
both
of
those
with
fcus
to
make
it
clear.
I'll
do
just
that
on
the
escos
side
of
things,
so
we
we're
still
working
on
documentations
I.
E
Think
all
the
test
fix
ups
and
things
like
that.
All
these
fixes,
so
that's
still
work
progress.
Removing
progressively
we.
We
are
we've
added
more
more
supporting
cursor
to
make
things
easier
to
work
on
on
s-cos
and
hopefully
at
some
point
we
can
have
you
like
a
quick
short
and
sweet
document
to
help
folks
get
started
on
escorts,
development
and
yeah,
so
we're
still
pending.
The
of
this
is
depending
the
fact
that
we
have
all
the
packages
available.
We
are
very
close
now
we
still
have
the
cryo.
E
We
will
have
soon,
as
Christian
said,
we'll
have
quick
tools
and
opportunity,
ibq
and
OC
soon
too,
and
once
we
have
all
of
that,
we're
good
to
go,
and
we
will
like
let
you
play
with
with
Central
stream
for
us
as
you
as
you
see
fit,
and
that's
it
for
me.
D
Just
real
quick
for
me,
I
will
Timothy
I
will
reach
out
to
you
regarding
cryo.
If
you
don't
have
a
difference
and
we
we
are
definitely
planning
on
upstreaming
all
the
changes
we
do.
Downstream
in
the
open
Cosa
pipeline
repository
currently
back
into
the
OS
repo,
just
a
heads
up,
so
yeah
I'll
be
opening
PRS
as
we
as
we
go.
Unless,
obviously
you
you
need
them.
First.
E
No,
that's
good,
that's
good!
Once
we
you
have
the
changes
like
the
Repose
or
something
like
that.
We
can
start
using
them
in
our
pipeline
too,
so
that
we
we
test
again
those
right
now
we
test
against,
though,
for
for
clarity
right
now.
We
test
against
the
the
real
bills
of
those
packages,
so
the
the
one
that
are
going
into
open
shift.
So
those
are
real
internal
well
and
at
least
until
they
are
released.
So
we
kind
of
like
use
that
for
or
to
to
let
everybody
from
the
community
use
that.
E
So
we
want
to
make
sure
that
once
we
say,
okay,
you
can
use
it.
You
can
use
it
with
only
fully
public
packages.
So
that's
why
we're
waiting
on
that
and
and
once
we
will
have
that
then
essentially
folks
will
be
fully
able
to
like
see
everything
change,
the
source
everything
fix
things
wherever
they
need
to
be
fixed,
because
right
now
those
are
still
missing.
D
So
cryo
and
cry
Tools
around
Copper,
they
will
be,
they
actually
are
available
and
I'll
PR
those
shortly
and
then
for
openshift
clients
and
openshift
hypercube
we'll
have
to
find
some
solution.
They
are
also
public,
but
they
are
currently
wrapped
in
the
artifacts
container
and
in
order
to
pull
them
out
of
there.
D
We
just
and
make
them
consumable
with
RPM
OS
tree
compose
and
then
Pros
Etc.
We
will
have
to
figure
out
something
creative,
but
we
will
come
to
that
eventually.
B
B
All
right
any
other
questions
or
comments
or
feedback
on
our
updates.
There.
C
Okay,
so
so
we
had
a
meeting
last
week,
I
think
the
first
thing
to
point
out
is
that
the
okd
main
repo
has
moved.
It's
moved
from
the
open
shift
to
the
okd
project
organization,
and
currently
the
redirects
will
work.
So
if
you
try
and
go
to
openshift.pb,
you
will
be
bounced
into
the
okd
project.
C
I've
just
assigned
me
a
task
now
to
go
and
update
all
the
documents
and
all
the
links
to
the
openshift
okd
to
where
we
raise
issues
and
where
we
start
discussions
so
I'll
be
doing
that
this
week,
I
get
that
that
done,
the
other
repo
I'm
still
looking
at
Diane
and
to
try
and
pull
together
the
the
people
that
need
to
coordinate
them,
the
DNS
entries
and
to
actually
move
the
okd.io
repo,
and
that
is
the
last
thing
that
we
have
to
do
to
get
into
the
OCD
project.
A
So
it's
that
that
I
had
a
Christian
and
Vadim
had
put
in
a
request,
the
red
hat.
I
t
to
make
that
move
Christian.
Is
there
any
status
on
that.
B
Yeah,
it
would
be
great
if
we
could
tackle
that
sooner
than
later,
because
it
would
be
nice
to
get
some
okd
based
email
addresses
too
so
get
those
MX
records
changed.
We
can
use
an
external
service
like
Google.
B
Yeah
keep
us
posted
on
that
for
sure.
Okay,
all
right,
Brian
back
to.
C
You,
okay,
so
we
are
using
a
project
board
I've,
put
a
link
in
there.
It's
github.com
okd
project,
and
if
you
go
to
the
project
section,
we
have
a
project
planning
board,
that's
where
everything
we
want
to
start
doing
so
we're
removing
tasks
from
the
the
hack
MD
and
everything
should
now
be
moved
on
to
the
planning
board.
So
this
is
where
we
want
to
have
the
the
master
plan.
C
We've
got
a
number
of
things
in
progress,
there's
some
things
in
ready.
So
if
anybody
feels
like
volunteering
and
getting
their
hands
dirty
go
grab
something
assign
yourself
in
ready
and
there's
a
couple
of
things
in
the
backlog
and
then
the
okd
community
group
development
group
will
actually
look
at
the
new
items
and
and
assign
them
and
and
sort
them
each
each
time
they
meet.
C
C
So
I've
been
holding
off
doing
a
major
re-old
of
that
until
I
know
a
little
bit
more
about
what
they
want
to
produce
and
if
they
can
do
do
that,
and
we
also
have
a
volunteer.
That's
someone
identified
that
they've
written
some
documentation
around
automation
with
terraform,
which
I
think
is,
is
really
useful
that
we
want
to
sort
of
I.
Think
that
that's
that's
the
sort
of
guide
that
we
want
to
put
in
there
where
people
have
shown
how
they've
automated
it
with
the
various
platforms.
C
C
The
other
thing
that
we
did
talk
about
in
the
community
group
was
about
a
recruitment
drive,
so
anytime
anybody
speaks
at
an
event
whether
it's
coupon
or
our
Meetup,
if
you
could
in
include
an
invite
to
come,
join
our
community
as
part
of
any
okay,
the
talk
that
would
be
really
really
useful,
I
think
that's
about
it.
B
Oh,
and
one
of
the
thing
is
we're
going
to
collate
the
results
of
the
survey
and
then
like
have
a
discussion
about
it
once
we
can
like
to
use
some
data
out
of
that,
there's
a
fair
amount
of
responses
to
it.
Okay,
any
questions,
comments,
feedback
on
the
community
development
meeting
report.
B
All
right,
I'm
really
excited
about
where
that's
going
and
excited
about
the
volunteers
that
we've
had
showing
up
I've
been
swamped
with
some
internal
things,
the
past
couple
weeks,
but
that
is
resolving
itself
and
we'll
be
reaching
out
to
a
couple
of
the
folks
that
have
volunteered
and
start
starting
to
sort
of
bootstrap
them
into
the
into
the
process
and
all
right,
let's
see
Diane
did
you
want
to
reference.
You've
got
some
events
coming
up
that
you
wanted
us
to
know
about
yeah.
A
So
again,
that
Outreach
community
outreach
vein
we're
going
to
kubecon
in
October
in
Detroit
and
I've
tapped,
both
Jamie
myself
and
Mike
McEwen
who's
on
the
call
to
go
on
stage
at
the
commons
event,
which
is
the
day
day,
Zero
of
kukan
and
I've
booked
a
three-hour
room,
including
lunch
on
the
25th
for
an
okd
working
group
face-to-face
meet
and
greet
whatever
we
want
to
call
it
and
prior
just
prior
to
that,
is
going
to
be
the
operator
framework
team
he's
going
to
be
doing
a
Hands-On
workshop
and
what
we're
going
to
then
ask
is
all
the
operator
framework
people
to
come
to
the
okd
working
group
meeting
so
that
we
could
talk
about
the
future
of
operators,
and
you
know
things
get
some
of
our
questions
answered
and
do
some
cross-pollination
there.
A
So
if
you
can
get
yourselves
to
Detroit,
let
me
know
or
let
Jamie
know,
and
we
will
figure
out
how
to
incorporate
you
and
make
sure
you
can
get
there.
You
do
not
need
a
full
pass
to
kubecon
to
come
to
the
commons
Gathering.
It
is
co-locate
event,
but
it
is
at
the
Western
Book
Cadillac
on
the
25th
and
because
it
is
off-site
from
the
campus,
the
convention
center,
you
don't
need
a
coupe
compact,
so
you
don't
have
to
spend
the
15K
1500
dollars
to
get
in.
A
So
if
so,
we
can
do
some
Outreach
to
the
local
meetups
and
other
folks
too,
as
well
to
come.
The
price
point
is
a
little
high
in
pricey
for
some
folks.
A
And
then
the
only
other
thing
I
have
is
as
soon
as
Luigi
and
Christian
tell
me.
We
have
an
MVP,
probably
will
kick
off
and
pick
a
date
to
do
that.
Feedback,
test,
testing
and
deployment
Summit
hackathon
on
the
okds
costs,
I
think
so.
I'm,
just
waiting
waiting
patiently,
Luigi
and
Christian
and
we'll
start
yeah.
B
A
Afternoon,
okay,
so
I'm,
just
gonna
respond
to
my
note
in
the
chat
about
talking
with
Dennis
I
saw
that
note
earlier
and
yeah.
Whatever
time
works
for
you,
Fridays
are
best
to
start
recording
videos
I
think
we
could
just
have
a
standing
session
on
Friday
mornings,
West
Coast
time
and
Christian.
When
you
get
ready
to
do
a
video
or
Luigi
does
we
can
just
knock
them
out
of
the
ballpark
I'm
ready
and
waiting
fantastic
and
then
we
can
turn
those
into
blogs
and
keep
Brian
and
the
content.
People
happy.
B
Thanks
so
much
folks
for
showing
up
and
doing
the
work
that
makes
us
a
great
community,
so
vibrant,
and
so
many
great
things
happening
if
you
want
come
to
the
the
okd
community
development
meeting,
which
is
same
Time
same
channel
next
week
and
either
way.
We'll
see
you
in
two
weeks
for
this
meeting
thanks.