►
From YouTube: OKD Working Group Meeting 08-17-2021
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: https://okd.io
A
All
right,
let's
get
started
so
quick
agenda
review.
Does
anyone
have
anything
that
they
want
to
change?
Modify
add
to
the
agenda
removed
from
the
agenda
happy
with
the
agenda.
A
Three
times
all
right
looks
like
we're
good,
so
I've
decided
to
instead
of
doing
full
introductions
now,
just
if
folks,
the
first
time
you
talk
during
the
meeting,
introduce
you
just
say
your
name
and
then
folks
can
then
go
to
the
meeting
notes
and
see
like
who
you're
affiliated
with
that
gives
us
just
a
little
bit
more
time,
because
we're
always
sort
of
coming
up
the
edge
like
that.
A
But
at
least
that
way
people
know
who
is
talking.
I
always
laugh
because
I
look
at
the
cnc
f
videos
and
they
don't
have
any
descriptions,
no
links
to
the
particular
working
group.
That's
that's
having
the
meeting
no
link
to
their
meeting
notes
and
no
description
of
who
the
people
are,
so
you
always
have
to
like
dig
around
and
do
a
search
for
everything
all
right
so
jumping
into
it.
Let
me
share
my
screen.
A
All
right
so
folks
should
see
the
meeting
notes
and
again,
don't
forget
to
put
your
name
in
the
attendees
there.
So
vadim
couldn't
make
it
today.
So
he's
got
a
couple
of
notes
here
that
he
wanted
to
make
us
aware
of
4.7
stable,
was
released
last
week,
he's
focusing
on
48
nightly's.
Now
the
stability
on
fixing
the
four
seven
to
four
eight
upgrade
issues
to
promote
four
eight
to
stable
and
mustafa
is
tackling
that
right.
A
A
Yeah,
it
looks
like
so
sc
linux.
A
Looks
like
this
is
a
conversation
on
different
perceptions
of
how
this
should
be
implemented
for
months
check
this
out.
If
folks
want
to
have
a
convert,
larger
conversation
about
that,
we
can
do
so,
but
vadim
didn't
want
to
bring
it
to
our
attention
and
mustafa.
Is
that
one.
B
B
C
A
And
a
little
bit
about
doc's
stuff,
so,
let's
see
take
a
quick
look
and
see
who's
on
here
is
brian
on
he
is
oh
yeah
brian.
You
want
to
go
ahead
and
talk
a
little
bit
about
the
path
forward
that
we've
decided
to
take
in
terms
of
the
new
site.
D
Yeah
sure
so,
we've
been
having
a
number
of
discussions
in
the
docs
working
group
about
the
okidi.io
site.
D
What
it's
for,
what
it
should
be
for
and
one
of
the
challenges
is
it's
not
easy
to
update
the
technology
and
that's
being
used
means
you
need
to
be
really
a
full
web
front-end
developer,
to
be
able
to
add
content
and
as
our
community
front
door,
we
thought
that
that's
not
really
where
we
want
to
be
so
we're
exploring
a
technology
called
mk
docs
which
allows
you
to
write
pure
markdown,
and
it
does
allow
extension.
D
So
you
can
add
sort
of
richer
features,
things
like
tabs
and
things
like
tables
that
look
like
the
proper
tables,
not
with
sort
of
minus
an
equal
sign
in
it
in
an
ascii
format,
and
we
can
create
sort
of
banners
with
warnings
or
information
type
things.
So
there
are
a
few
extensions
that
we
use
to
mark
down,
but
the
idea
is
that
anybody
should
be
able
to
pick
up
the
technology
within
a
few
minutes.
D
Markdown
is
a
technology
that
drives
git,
so
hopefully
everybody
should
be
able
to
get
on
board
with
that.
We've
also
been
looking
at
using
maybe
github
automation
to
actually
do
the
put
do
the
publishing
and
that's
what
I
do
and
there
are
other
communities
I
work
with
and
that's
the
way
we've
gone
so
just
pushing
to
the
main
branch.
D
We'll
actually
publish
the
update
onto
github
pages,
which
we
can
then
use
a
cname
to
link
to
okd
io.
So
it
becomes
a
sort
of
maintenance,
free
front
door,
and
then
we
can
then
open
it
up
to
the
community
to
really
make
that
our
own
our
front
page,
where
we
can
actually
start
putting
a
lot
more
information
on
there.
And
the
idea
is
that
you
want
to
consolidate.
D
D
But
the
idea
is
that
we're
now
going
to
create
a
beta
branch
within
the
okd
repo
and
that
will
then
become
a
beta
and
there's
a
lot
of
things
that
we
need
to
work
out
in
terms
of
the
styling,
the
colors,
how
we
want
this
the
site
to
look
and
feel.
I
think
we
want
it
to
be
a
little
bit
simpler,
there's
a
lot
of
bootstrap
animation
in
there,
which
just
adds
complexity
to
the
actual
structure
of
the
site.
So
we
want
to
just
make
it
a
little
bit
simpler.
B
And
I'll
just
brian
I'll,
let
you
know
that
I
did
talk
to
the
the
folks
who
own
own
or
control
the
c
name
and
as
soon
as
we're
ready,
they
are
quite
happy
to
move
the
cname
dns
over.
So
we
just
have
to
pull
the
trigger
when
we're
ready,
they're,
actually
thrilled
that
we're
doing
this.
So
one
one
less
website
for
them
to
worry
about
yeah.
There.
A
And
while
brian's
doing
that,
here's
a
quick
link
to
or
quick
update
on
some
other
things
that
were
added,
so
I
push
some
changes
and
some
other
folks
push.
Some
changes.
Community
now
goes
to
the
discussion.
A
Functionality
of
the
get
repo
for
okd
recipes
is
still
there.
We
talked
about
sort
of
merging
that
into
some
of
the
other
documentation.
I
thought
we
had
decided
to
get
rid
of
recipes
completely.
I
I
well
there
is,
there
are
two
there,
and
so
my
thought
was
taking
so
for
you,
click
on
this
there's
taking
these
two
and
then
moving
them
into
the
the
guideline
like.
E
E
Yeah,
that's
exactly
what
that
is
yeah.
We
we!
I
either
need
to
rally
some
community
folks
around
reading
more
of
those
or.
B
C
A
B
B
And
and
take
it
off
there
and
just
keep
it
simple
and
there
you
go.
D
Sorry
just
to
follow
up
on
that
I
mean
I'm
really
interested
in
getting
the
rook
seth
working
on
okd.
So
it's.
Where
do
we
see
that
going?
I
know
ideally,
we'd
want
a
community
operator,
that's
in
the
okd
community
operator
hub
eventually,
but
I
I
think
there
are
little
things
like
that.
That
will
save
people
a
lot
of
time
when
they're
trying
to
set
up
an
environment
so.
B
What
I
might
do
charo
is
e,
introduce
you
and
your
link
here
to
annette
kluet
and
travis
nelson,
the
two
folks
behind
rook
and
that
and
see
if
we
can
get
someone
from
that
community
to
work
with
us.
I'm
getting
you
know,
updating
it
saying
hey.
This
is,
you
know,
obviously
out
of
date
and
a
little
stale
is
there
anyone
that
you
know
there.
B
If
I
did
that
email
intro
tarot,
can
you
walk
them
through
what
you've
done
and
then
maybe
we
can
get
them
to
convert
it
into
one
of
the
guides,
rather
than
they
probably
have
they've
they've
done
a
ton
of
demos
for
me
on
ocp
in
the
commons,
and
you
know
in
combination,
so
I
think
that
might
be
the
route,
and
that
would
help
and
brian.
I
can
ccu
on
that
too.
A
So
one
thing
we
may
want
to
be
mindful
of
is
so
this
right
now
and
in
the
new
site
is
installation,
and
so
these
are
deployment
guides
for
actually
deploying
okd.
So
we
may
want
to
somehow
modify
this
connect
connection
of
ideas
because
once
you
start
getting
into
deploying
particular
apps
or
particular
technologies
on
the
cluster,
that's
not
the
same
thing
as
installing
the
cluster.
So
we
want
to
tease
that
out
all
right,
so
we'll
be
dropping.
This
community
was
changed.
Blog
documentation
goes
here
now.
A
D
F
F
No,
this,
the
ingress
controller
stuff,
doesn't
exist
in
the
okt4
document
right.
If
someone
wants
to
change
that,
what
should
they
read?
Where
should
they
read
them?.
E
Yeah,
that's
true,
I
think
the
official
red
hat
open
shift
documentation
has
instructions
for
using
kubernetes
ingress
if
you
choose
to,
but
the
the
preferred
method
is
through
the
ingress
operator,
with
with
routes.
A
So
it
I
mean-
maybe
one
thing
we
could
do
is
create
a
document
and
this
again
could
be
tackled
at
the
documents
meeting,
but
a
document
that
outlines
some
of
these
changes
for
folks
to
help
them
get
over
to
for
and
understand
for
just
a
quick
document
where
we
can
throw
ideas
into
it.
But.
D
A
E
D
A
A
You
know
guide
for
folks
coming
from
three
to
four
about
things
like
you
know,
ingress
controller
versus
operator
and
routes
and
stuff,
like
that,
just
little
tidbits
that
might
be
helpful
to
help
folks
make
that
transition,
and
they
can
go
back
here
if
they,
if
they
wanna
they're,
still
needing
to
work
with
three
for
some
reason,
all
right.
So
this
is
yeah.
Let
me
go
back
here,
so
this
is
brian's
example
that
he
provided.
A
Got
these
on
the
side,
it's
got
search
and
stuff.
If
you
want,
the
video
will
be
posted
in
the
next
couple
days.
Folks
can
watch
the
video
of
the
meeting,
because
brian
does
like
a
whole
walk
through.
A
So,
oh,
and
so
this
is,
I
was
gonna-
ask
this
to
the
larger
group
because
it
came
up
at
the
docs
meeting
and
we
sort
of
made
an
assumption,
but
now
I'm
wondering
if
maybe
maybe
it
wasn't
the
best
assumption.
So
the
idea
was
okay.
We
can
put
the
meeting
notes
and
other
working
group
docs
into
the
okd
dot
io
repo.
D
I
guess
the
question
is:
are
we
still
going
to
maintain?
I
mean
I
don't
know
what
red
hat
policy
is,
but
do
we
still
have
to
maintain
the
sort
of
pull
request
model
where
a
red
hatter
has
to
or
do
we
want
and
an
an
approver
to
have
to
approve
any
changes?
I
think
that's
probably
a
safe
option.
Yeah.
H
A
What
well
you
and
I
have
access
to
do
approvals
right.
D
A
Yeah
so
I
mean
maybe
we
have
three
people
diane
and
then
like
two
others,
you
know
so
the
co-chairs
and
then
like
third
person
like
brian
and
then
three
people
can
do
approvals
on
those
then
yeah,
then
that
would
avoid
any
any
issues.
I
think
with
someone
accidentally
clobbering
stuff.
A
A
Okay,
so
here's
a
couple
of
crc
ones.
Suddenly
there
was
a
several
crc
related
issues
which
relate
to
build.
We
got
those
brians.
A
In
discussions
we
talked
about
this
in
the
in
the
docs
meeting
is
in
discussions
have
like
templates
pop-ups
when
you
select
a
like
a
q,
a
have
a
template
pop
up,
so
we'll
have
to
do
some
investigation
on
how
to
get
that
set
up,
because
people
really
need
to
include
log
bundles,
a
lot
or
at
least
provide
some
basic.
A
I
So
yeah
good
job-
I
I've
got
a
question
about
why
this
to
me
would
seem
to
be
an
issue
you
know,
so
I
thought
it
would
have
been
open
in
issues
and
in
some
discussions
I
guess
I'm
kind
of
confused
as
how
how
vadim
is
because
I've
seen
that
he's
moved
a
lot
of
stuff.
That
seemed
to
be
issues
to
me
that
should
be
in
the
issues
portion
into
the
discussion
side.
So
we
kind
of
lose
that
issue,
template
type
of
thing.
So
do
we
have
a
do?
A
I
think,
and
don't
quote
me
on
this
I'd
hate
to
speak
for
him,
but
my
sense
was
he
was
getting
a
lot
of
stuff
that
was
or
that
in
general,
the
stuff
coming
into
the
issues.
A
Queue
was
stuff
that
maybe
wasn't
an
actual
issue
or
people
asking
questions
that
could
be
triaged
in
a
way
that
did
not
involve
modifying
code
or
bug,
fixes
or
anything.
A
I
Because
I
I've
seen
that
a
lot
of
the
issues
have
been
moved
to
discussions,
but
it
almost
seemed
to
be
the
default,
and
I'm
just
wondering
if
that's
how
we
really
want
to
do
it.
Because
to
me,
discussions
are
a
higher
level
thing
when
we're
talking
about.
I
You
know
install
processes
or
or
there's
something
that's
affecting
a
lot
of
people.
You
know
that
you
know
we
have
a
lot
of
discussion
on
to
me
that
would
this
one
would
be
an
issue
at
least
start
off
as
an
issue,
but
I
was
just
curious
because
I
I
noticed
that
over
the
last
few
weeks
that
that
had
happened,
so
I
just
wasn't
sure
if
there
was
a
decision
made
or
something
that
had
said
we're
gonna
we're
gonna
put
a
lot
of
this
stuff
into
the
discussion.
So
I'm
just
curious.
A
I
think
that
was
something
that
he
did.
He
can
speak
to
it.
More
do
folks
have
thoughts
on
it.
In
terms
of
I
mean
because
so
one
of
the
things
we
want
to
do
that
any
board
or
committee
needs
to
do
is
sort
of
separate
the
needs
of
the
group
from
like
okay,
this
one
individual
who
needs
to
be
in
this
position.
H
Yeah
jimmy
yeah
yeah,
I
I
guess
one
question
is
are:
is
issues
intended
to
be
bug
reports.
H
Yeah
so,
and
in
many
cases
when
something
happens
to
you,
you
don't
know
if
it's
your
fault
or
a
bug,
report
yeah.
So
it's
reasonable
to
have
a
discussion
first
before
you
open
an
issue.
If
issues
are
intended
to
be
bug
reports
and
in
the
past,
that's
often
been
slack
where
something
like
that
and
after
some
discussion,
vadim
says:
okay
open
an
issue
and
then
you
go
ahead
and
open
an
issue.
H
That's
not
going
to
be
immediately
closed
but-
and
I
think
that
we've
sort
of
been
moving
that
more
to
this
discussions
group,
so
I
think
that's
sort
of
what's
going
on
there.
H
Like
either
way,
no
matter
where
it
gets
opened,
it
appears
in
the
in
you
know:
if
you've
subscribed,
then
it
appears
in
your
inbox.
D
D
This
is
the
forum
where
community
end
user
community
members
meet
to
sort
of
communicate
with
each
other
and
then
once
we've
identified
that
there
is
a
potential
bug,
then
we
will
move
it
to
the,
and
I
think
we
were.
We
copied
that
from
one
of
the
other
open
source
communities
where
we
saw
that
they
did
exactly
the
same.
They
put
the
community
link
directly
to
their
discussion.
So
I
think
that's
where
the
idea
came
from.
I
Okay,
like
I
said
I
was
just
curious.
I
noticed
that
over
the
last
few
weeks
that
what
I,
what
we
were
seeing
as
issues
before
are
now,
are
now
going
to
discussions,
and
if
that's
where
we're
going,
I
mean
that
makes
sense,
but
maybe
that's
something
that
needs
to
be
described
or
pinned
somewhere.
That
says
before
you
open
an
issue
open
a
discussion
first
or
something.
A
G
A
So
we
would
want
different
nomenclature
because
there's
a
strong,
I
would
say,
push
from
red
hat
folks
and
the
sponsors
of
okd
to
not
use
the
word
support,
because
then
it
implies
that
that
they
are
entitled
to
support
with
with
it.
If
we
come
up
with
a
different
word,.
B
F
A
All
right
well
we'll
throw
that
around
a
little
bit
more
and
see
where
it
goes.
Is
anyone
opposed
to
the
idea
of
stuff
going
to
discussion
and
then
issues
getting
filed
afterward
as
fitz
determined
to
be
an
actual
code
issue?
Anyone
have
any
anyone
not
think
it's
a
good
idea.
A
All
right,
well
not
hearing
anything.
So,
let's,
let's
and
we'll,
have
vadim
at
the
next
meeting,
maybe
flesh
out
his
thinking.
Morbid,
pretty
sure
that's
where
he
was
going
is
trying
to
keep
that
as
issues
as
just
actual
bugs.
A
Oh
okay,.
B
A
It
looks
like
it
with
study
yeah.
I
know.
Okay,
all
right
well,
we'll
I'll,
take
a
look
and,
and
other
folks
should
take
a
look
at
as
well
vadim's
been
like
really
strapped
for
time,
and
if
we
can
get
more
community
members
tackling
these.
That
would
be
awesome,
I
mean,
and
if
you
don't
have
time
to
dig
through
someone's
log,
that's
understandable
too.
I
Yeah
jamie
there
may
need
to
be
a
a
gentle
reminder
in
the
slack
channels
about
calling
people
out
directly.
There's
been
a
few
over
the
last
few
days
directly
to
vadim
again.
A
Yeah
and
vadim
is
sort
of
sometimes
he'll
respond
and
just
go
with
the
flow.
I
think
it's
if
he
knows
the
person,
maybe
but
other
times
he'll
be
like
you
know
it's
rude
to
attack
me.
I
will
post
something
again
and
we
should
maybe
can
put
something
in
the
description
about
that.
A
A
Five
and
four
six
anymore,
we
haven't
really
had
that
discussion.
Actually
I
had
that
on
here
before
I
knew
that
vadim
was
gonna
be
coming,
was
a
migration
path
outline
and
support
outline,
and
since
he's
not
here,
I
don't
know
that
we'd
be
able
to
have
a
technically
informed
discussion
about
it,
but
I
do
think
that
that's
a
good
idea.
E
G
4.4
or
4.3
was
the
first
ga
4.4.
Maybe
it
was
4-4,
but
even
then
like
there's,
no
concept
like
of
like
separate
release
channels
or
anything
like
that
for
whether
it's
with
ocp,
you
just
get
a
release
on
the
train.
Whenever
the
dean
puts
it
out,
you
upgrade
to
it
so
yeah,
I'm
kind
of
a
charo
on
this.
I
don't
think
we
should.
We
should
encourage
people
to
think
that
oh
they're,
separate
parallel
supported
release
branches.
A
I
I
do
think
it
would
be
helpful
to
have
a
migration
path,
because
there
are
some
people
who
are
on
like
very
urgent
early
earlier
earlier
versions
of
okd4
that
want
to
be
able
to
go
to
four
seven,
and
there
are
certain
versions
of
four
six
that
do
not
go
to
four
seven
etc.
And
so
I
think,
having
that
matrix
laid
out
would
be
helpful
for
folks
that
do
want
to
get
to
the
latest.
C
So
generally,
what
happens
here
speaking
from
the
federal
court?
Sign
generally,
what
happens
on
ocp
is
that
you
update
from
one
visual
to
the
next
measure.
You
don't
skip
major
releases,
that's
unless
I'm
completely
missing
something
that
also
applies
to
a
kg.
So
I
would
recommend
users
move
from
4.5
to
4.6
and
then
for
4.6
to
4.7,
then
fall
seven
to
four
update
when
that
gets
released.
C
The
general
idea
that
when
you
move
from
one
release
to
the
other,
you
have
some
you
move
essentially
from
one
community
three
days
to
the
next
one
and
which
means
that
some
apis
get
deprecated.
Some
gets
updated,
sometimes
removed.
So
you
have
to
make
sure
that
everything
works,
and
you
do
that
and
and
the
hcd
version
changes
things
like
that,
so
the
configuration
may
change.
C
H
C
Anywhere,
we
don't
test
that
moving
from
one
or
cpu
release
directly
to
another
one
like
skipping
releases,
so
I
would
not
recommend
users
do
that
and
on
the
other
side
of
support
events,
that
we
don't
it's
not
support.
Anything
below
4.6
is
completely
even
unsupported
on
the
red
outside.
So
we're
talking
about
any
supporting
anything
below
4.6
in
okd
is
I'll,
say
completely
not
happening
most
probably.
H
Also,
by
the
way,
yeah
now,
just
just
that
this
is
a
4.5
install
fail,
not
an
upgrade
fail,
so
I
think
you
could
reasonably.
You
know
like
if
the
person
is
going
off
some
blog
post,
that
it's
installing
4.5
a
reasonable
rejoinder
would
be
to
say,
don't
install
that
one.
You
know
you
have
to
install
at
least
you
know
xyz
and
the
current
one
is
4.7.
A
A
I
don't
know
that.
That's
true,
I'm
pretty
sure
that
more
recent
versions.
I
I
was
able
to
upgrade
yeah.
I
think
there
might
have
been
issues
with
certificates
and
stuff
that
broke
at
a
certain
point
yeah,
but
that
was
remember
exactly
when
that
was,
and
you
had
to
do
a
force.
I
know
that's
what
I've
had
to
do.
I
haven't
had
to
do
in
a
while,
but
I
know
there
were
a
couple
of
versions
where,
because
of
of
tagging
or
church.
A
A
Let
me
look
into
that
and
then
I'll
chat
with
vadim
as
well
and
see
if
we
can't
come
up
with
a
clear
answer
on
that
and
I'll
look
back
on
some
of
the
notes
just
so
that
we
can
respond
to
this
question.
That's
in
the
chat
and
I'll
seem
to
recall.
I
seem
to
recall.
I
Working
with
people
like
in
may,
you
know
that
had
issues
with
with
doing
certificates,
you
know
because
they
weren't
they
weren't
tagged
right
or
whatever,
but
maybe
it
was
before
that
time
kind
of
compresses
a
little
bit.
A
Yeah,
I
think
it
was
the
the
upgrade
issue
with
that
was
earlier
than
that
yeah
all
right,
very
cool,
moving
on
now
to
code
ready,
container
status
so
just
to
lay
the
foundation
for
this
discussion.
We
got
two
tickets
in
on
code.
Writing
containers,
there's
some
things
that
need
updating.
A
At
the
docs
meeting
there
was
a
discussion
actually
the
last.
I
think
full
group
meeting
discussion
about
getting
code,
rated
containers
up
to
snuff
and
having
multiple
people
who
can
help
with
it
to
make
sure
that
there's
always
a
updated
release
and
that
there's
good
documentation,
whatever
charo
has
been
awesome
and
just
like
beyond
belief
in
his
support
of
crc
stuff.
But
his
time
is
getting
taken
by
other
great
things,
and
so
it
seems
like
something
the
community
to
handle.
A
I
sent
out
an
email
well
reach
out
to
charo
charo
responded
to
me:
hey
get
round
up
any
people
who
are
interested,
and
you
know
we
can
do
a
show
and
tell
type
thing
I
sent
something
out.
We
got
an
initial
like
eight
people
that
are
folks
that
are
sort
of
in
and
out
of
the
working
group
like
in
terms
of
participation,
and
then
we
just
in
the
past
two
days
got
eight
responses
from
people
that
haven't
really
participated
in
the
working
group
in
any
because
this
was
posted.
A
I
posted
my
email
on
the
google
group
and
so
there's
eight
people
who
aren't
really
affiliated
with
the
working
group
and
in
terms
of
contributing
to
it
or
maintaining
anything.
So
the
thought
is.
A
Maybe
this
could
be
their
entry
point,
but
I
think
what
we'll
do
is
maybe
take
the
first
because
that's
like
16
people
take
the
first
eight,
which
includes
like
myself,
mike
mccune,
a
bunch
of
sort
of
the
regulars
that
are
here
at
this
meeting
and
whatnot,
we'll
work
with
charo
and
then
from
there
educate
outward
and
and
come
up
with
something
so
that
this
doesn't
become
something
that
charo
is
burdened
with
and
that's
the
foundation
charo
go
ahead
and
take
it
away
from
there
talking
about
what
you
want
to
do.
E
Excellent
okay,
so
I
I'm
preparing
documentation
how
I
build
code,
ready
containers
or
okd.
It's
actually
in
the
one
of
the
links
that
I
just
posted,
there's
very
little
documentation
there.
It's
at
at
this
point,
just
a
a
bash
barf
of
what
I
run
through
to
build
it.
E
E
I
just
don't
have
a
place
to
automate
it,
except
in
my
home
lab,
and
it
is
still
in
that,
when
the
downstream
the
side
stream
project
for
red
hat
code,
ready
containers
makes
code
changes,
it
often
breaks
the
okd
build
and
so
like.
For
instance,
I
have
a
new
release
to
push
out
this
afternoon
after
I
test
the
executables
make
sure
they
work,
but
I
had
to
make
code
changes
to
both
the
snc
project
and
the
crc
project.
E
E
B
But
do
you
want
to
do
this,
so
I
I
mean
there's
there's
a
lot
of
ways.
We
can
do
this
one
it
might
what,
but
what
helps
for
the
the
documentation
process
the
best,
so
that,
like
that
core
group
that
jamie
was
talking
about,
we
can
host
this
as
by
bye,
john,
I
have
one
quick
question
for
john
before
you
go.
If
you
have
a
second
or
is
he
gone,
he
might
be
gone.
B
Well
get
him
later.
So
what
I
was
hoping
was
a
just
to
facilitate
this
like
we
can
do
this
as
an
open
shift,
commons
briefing
and
you
can
walk
through
what
you've
done.
The
other
question
I
have
is
when,
where
you
get
the
code
from
the
red
hatters,
how
public
is
the
code
to
do
these
builds
like?
Are
you
being
gifted.
E
No,
it's
totally
it's
totally
open
source
hero,
I'll
post
it.
Actually,
I
think
if
you
scroll
scroll
down
just
a
little
bit,
let's
see
no
scroll
up.
I'm
sorry
find
the
get
clones
right
there.
B
E
How
could
you
get
clones
yeah
that
that's
where
that's
where
the
code
is
so
snc
builds
the
single
node
cluster
that
you
then
tear
down
and
build
a
qcal
a
disk
image
out
of,
and
then
you
and
then
you
compile
crc
crc
is
written
in,
go
you
compile
crc
and
embed
the
cucow
image
in
crc.
E
B
Yeah,
so
so
to
do-
and
this
is
for
jamie
too,
so
if
we
were
gonna,
we
could
do
an
ama
on
this.
Where-
and
I
don't
know
when
you'd
be
ready
for
it,
but
any
friday
like
we
would
do
for
a
community
office
hour.
B
We
could
do
this
any
friday
at
9
00
a.m,
and
we
could
also
live
streaming
on
twitch
and
invite
everybody
to
it,
but
I
could
host
it
sort
of,
as
rather
than
blue
jeans
like
this
there's
another
blue
jeans
level
of
blue
jeans,
blue
jeans,
events,
where
you
know
you
have
a
bunch
of
you
guys,
are
and
gals
whomever
we
can
coerce
being
the
presenters
and
then
there's
a
q,
a
q,
so
that
they
can
ask
questions
and
you
can
answer
them
as
you
go
and
that's,
I
think,
that's
a
better
facility
for
this.
B
It's
actually
better
than
the
zoom,
because
it
actually
lets
you
queue
up
the
questions
and
ask
them
and
records
the
questions
and
answers.
If-
and
I
I
mean
even
this
friday-
I
could
do
it
at
9am.
If
you
were
ready
to
do
it,
we
could
invite
everybody
who
came
and
then
maybe
what
we
do
is
make
the
core
group
of
people
that
jamie
was
referring
to
as
co-presenters,
so
that
they
their
faces
could
be
on
stream
and
everybody
else
who
asked
about
it.
B
E
E
Yeah,
so
I'm
I'm
actually
planning
to
the
reason
I
went
ahead
and
posted
this
in
my
new
blog
site
was
to
go
ahead
and
get
it
out
there
for
a
few
people
that
have
been
asking
me
directly
about
it,
and
my
plan
over
the
weekend
is
to
finish
documenting
it,
so
that
it's
it's
a
little
more
polished,
I'm
actually
going
to
drop
it
as
a
blog
post
as
well
so
next
friday,
then
we.
B
Why
don't
we
try
for
the
the
following
friday
and
I
can
put
it
on
the
calendar
as
an
openshift
commons
briefing,
okd
working
group,
whatever
thing
so
it'll
get
some
other
eyeballs
as
well,
and
then
the
group
of
people
jamie?
If
you
can
send
me
that
list,
I
will
make
them
co-presenters
or
you
and
mike
and
everybody
else
in
in
the
event
so
that
you
can
be
on
screen
and
you
can
add
your
two
cents.
B
No,
it's
that
would
be
noon.
Eastern,
oh!
No!
I
live
in
pacific
standard
time
me
and
bruce
over
here.
Where
are
the.
E
Yeah,
I
was
one
when
you
said
nine.
I
was
thinking
you're,
not.
A
B
Yeah,
it
would
be
good
if
we
could
try
and
do
it
in
an
hour.
But
that's
that's
fine
with
me
and
I'll
book
it
and
and
do
that
so
that's
cool.
B
E
E
I've
also
got
actually
another
internal
red
hat.
E
Brett
toefl
t-o-f-e-l
he's
he's
one
of
the
senior
software
engineers
that's
actually
working
on
olm
stuff,
so
I
also
talked
to
him
about
running
around
and
beating
gently
beating
some
of
our
community
operator
developers
over
the
head,
get
them
to
start
building
the
operators
with
the
container
images
as
manifests
instead
of
tags.
A
Eventually,
okay-
and
this
is
definitely
looking
this
over-
this
is
definitely
very
easily
automatable
and
I
think
if
we
just
find
a
server
or
even
a
cluster,
this
could
be
done
on
a
cluster.
That's
willing
to
host
it,
and
I
may
be
able
to
do
that.
Then
we
could
just
have
this
automatically
doing.
A
You
know
continuous
builds
and
when
it
fails,
we
go
oh
something
upstream
broke
this
and
then
we
can
go
upstream
and
say:
hey.
You
know
this
is
going
to
break
okd,
crc,
yeah,
yeah,.
E
It's
actually
it's
a
it's
a
three-step
process.
The
one
piece
that
I
haven't
added
to
it
yet
is
kind
of
a
sanity
check
in
between
the
two
steps
to
ensure
that
the
cluster
is
healthy
and
actually,
if
we,
if
we
get
this
running
somewhere
with
a
with
a
cicd
process,
hey
pause
for
just
a
minute,
because
if
you
at
the
very
top
of
this
code,
block
that
you're
on
see
that
curl
command
that's
actually
grabbing
as
and
setting
as
an
environment
variable
because
passing
is
an
argument,
the
current
release
of
okd.
E
So
this
this
thing
running
would
actually
be
be
running.
Continuous,
build
tests
of
okd,
it's
it's
using
a
libert
ipi
build!
So
you
know
it's
not
testing,
aws
or
gcp
or
that,
but
it
still
would
be
a
good
sanity
check
of
a
current
or
an
upcoming
okd
release
to
ensure
that
it
can
build
all
the
way
up
to
a
running
single
node
cluster.
A
B
One
more
thing
on
the
agenda,
I'm
just
because
I
I'm
just
curious
if
anybody
who's
on
the
call
or
anybody
who's
watching
this
afterwards
is
going
to
planning
on
attending
kubecon
and
would
be
willing
or
interested
in
giving
an
end
user
case
study
talk
at
commons
on
the
day
before
kukan
at
the
same
location.
It's
co-located
there,
please
ping
me
I'm
looking
for
more
folks
to
chat
and
to
share
their
stories.
B
So
if
you
have
one
and
you're
planning
on
going,
it
is
planned
to
be
a
hybrid
event,
so
just
in
case
they
they
close
us
down
and
we
can't
be
in
person
in
la
I'm.
I
am
going
to
host
it
on
hop
in
so
if
you
have
a
story
that
you
want
to
share,
let
me
know
reach
out
to
me
my
emails.
There
I'd
be
happy
to
have
a
an
okd
another
okd
story
on
the
menu
at
that
event,
trying
to
close
the
agenda
by
the
end
of
this
month.
B
So
let
me
know
soon
so
jamie
if
you've
got
one
or
bruce
or
brian,
or
I
know
you
guys-
are
home
lobby
kind
of
folks
for
a
large
part,
but
and
that's
what
I
was
going
to
hit
john
forten
about
see
if
we
can
get
market
america
on
stage
so
somebody
we
got
rhodium
schwartz
last
time,
but
then
he
disappeared
from
the
working
group
afterwards
because
he
got
too
busy.
So
I'm
not
sure
that's
the
right
thing
to
do,
but
anyways.
That
was
my
ask.
B
So
if
you
have-
or
you
know
of
somebody
who
might
be
willing
in
your
travels
charo,
that's
we're
up
and
we're
on
the
hunt
again
and
it's
it's
it's
looking
like
it
will
happen
in
person
kubecon
so
get
your
seat
belts,
ready
and
your
travel
packs
and
we'll
see
if
canada
lets
me
out
of
the
country.
A
Excellent
all
right,
the
other
thing
that
we've
sort
of
skipped
over
is
city
operator.
Catalogs
vadim
isn't
here,
but
what
I
wanted
to
find
out
is
what
the
status
was
of
the
internal
effort
to
there's
like
a
handful
of
operators,
actually
that
there's
an
internal
effort
to
put
into
a
community
version
such
as
serverless
and
pipelines
and
whatnot.
I
don't
know
what
the
status
of
that
is.
I
was
going
to
ask
dean,
but
it'd
be
good
to
find
out
and
then
also
where
the
community
can
start.
A
So
the
idea
is
that
if
we
go
to
the
tagged
issue
up
here,
the
wish
list-
you
know
these
are
the
ones
that
are
currently
unavailable
and
when
I
asked
vadim
about
he
mentioned
that
there's
an
internal
effort
on
these
it'd
be
nice
to
know
where
that's
at
and
and
who
we
might
need
to
bug
to
to
get
that
moving
forward.
Because
there's
a
lot
of
requests
for
these.
D
I
also
think
that's
the
key
inhibitor
to
people
adopting
okd,
because
with
ocp,
if
I
can
go
instead
of
my
full
cloud
native
environment
in
a
less
than
an
hour,
I've
not
yet
managed
that
on
okd,
because
every
operator
I
hit
it's
it's
a
little
bit
of
a
challenge
and
I'm
gradually
trying
to
work
through
things,
and
but
it's
if
it
was
as
easy.
It
was
on
ocp.
I
think
we
get
a
lot
more
usage
of
okay.
A
Yeah,
so
here's
a
good
example
right
like
if
you've
got
a
production,
cluster
or
even
a
a
true.
You
know
dev
cluster,
where
you
really
want
to
monitor
stuff
or
qa
or
anything
you're
going
to
want
persistent
logging
through
the
operators.
A
Well,
you
need
these
two
to
get
open
shift
logging
going
right,
you
need
the
elastic
elasticsearch
and
the
cluster
logging
operator
together
installed
and
again
you
can
do
it
manually,
but
it's
a
big
difference
being
able
to
go
through
the
hub
and
the
catalog
and
be
able
to
get
those
in
serverless
same
thing,
the
gitlab
operator
as
well.
A
So
all
right,
let's
put
that
on
the
agenda
for
next
meeting
and
we'll
get
an
update
on
that
and
see
who
we
can
talk
to
about
parking
a
little
fire
to
get
those
done.
The
other
thing
that
I
wanted
to
get
a
sense
of
from
vadim
or
whomever
a
christian
isn't
here
either.
But
what
can
we
do
to
start
these
ones
that
need
to
get
need
to
be
made
available
like
pipelines
and
stuff
like
that?
A
Like
do
we
just
select
a
handful
of
people
to
tackle
it,
and-
and
this
group
I
think,
needs
to
think
about
what
we
can
do
to
start
a
process
of
roping
people
in
or
getting
people
to
be
volunteer,
getting
people
to
volunteer
to
get
these
operators
built
and
into
catalogs.
A
D
I
think
one
of
the
challenges
that
the
diamond
countering
is
the
build
process
seems
to
be
this
sort
of
mythical
thing
within
red
hat:
it's
not
easy
to
find
out
from
an
outside
in
point
of
view
of
how
they
build
them,
and
often
there
are
secondary
sort
of
containers
that
are
in
the
entitled
registry.
So
I'm
looking
at
the
getty
that
someone's
actually
gone
and
done
a
great
gt
operator
and
it
works
on
ocp,
but
it
uses
the
our
back
proxy
from
registry.redhat.com.
D
So
I
can't
put
it
on
a
kd,
because
it's
got
that
entitled
registry
container
and
it's
then
I've
now
got
to
go
and
work
out
how
to
recompile
that
and
and
do
it.
So
I
I
think,
there's
a
lot
of
cases
like
that
where
there
is
some
internal
dependency
within
red
hat,
I
don't
know
whether
it's
intentional,
but
we
sort
of
hit
that
sort
of
external.
E
The
challenge
that
I'm
seeing
as
I've
worked
with
a
few
of
the
operator
communities
is
that
I
think
it's
less,
that
there's
an
internal
process
and
more
that
there
isn't,
each
of
because
each
of
the
operators
start.
You
know,
start
their
lives
as
an
upstream
project
and
the
way
they're
built
doesn't
follow
a
dimension,
much
less
a
standard.
E
And
so,
if
you
know,
if
the
person
that
started
working
on
like,
for
example,
to
get
t
operator,
if,
if
they
were
in
a
entitlement
basis,
they're
pulling
from
registry,
they
just
didn't
realize
they
were
hard,
locking
it
and
it
required
us
that
of
using
the
the
quay
dot.
Io
version
of
the
exact
same
container.
A
I
think
the
tectonic
operator
would
be
one
that
we'd
really
want
to
get.
You
know,
pipelines
actually
working,
because
that's
something
that's
sort
of
fundamental
right
is
getting
that
pipeline.
Working
and.
D
E
Okay,
I'll
I'll
post
in
straight
it,
it's
actually
really
easy
to
build
the
tecton
operator
for
open
shift
and
install
it.
You
can
do
it
in
just
a
few
commands
with
a
with
a
few
dependencies.
If
you
have
a
go
development
environment
set
up
on
your
linux
or
macbook,
I
haven't
read
it
from
windows
because
I
don't
have
any
windows,
so
I
can
at
least
for
people
that
are
waiting
for
tecton.
I
can
close
that
gap
pretty
quickly,
because
that
I've
been
renting
it
for
a
while
and.
E
E
It
it
is,
there's
there's
a
couple
of
undocumented
steps
that
you
need
to
do
to
set
some
permit
variables,
but
it
will
actually
build
and
then
push
it
it'll
push
the
images
to
whatever
registry
you
want
it
to
push
them
to,
and
then
it
will
apply
the
the
crds
and
manifest
to
your
openshift
cluster.
A
Okay,
I
want
to
be
mindful
of
folks
time
because
we're
at
the
hour
so
let's
call
it
and
then
we've
we've
got
our
homework
set
out
for
us
up
until
the
next
meeting
and
charo.
Thank
you
so
much
for
helping
with
crc
and
helping
with
operators
and
and
doing
that
leg
work
for
us.
I'm
very
much
appreciated.
D
D
A
A
B
Back
out
give
me
something
to
cut
and
paste,
and
I
will
cut
and
paste
and
we'll
just
do
that.
That's
cool
all
right!
I
have
a
couple
of
things
I
have
to
do
for
you
guys
right
away.
So
look
for
those
the
blue
jeans
thing
to
come
out.
Charo
with
you
and
jamie
and
I'll
include
fred
toefl
in
there
too,
just
to
scare
him.
B
All
right,
I
like
scaring
our
red
hatters
thanks
again
jamie
for
doing
this,
and
it's
always
a
pleasure.