►
From YouTube: OKD Working Group Meeting 02-15-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
Right,
let's
jump
right
into
it
with
okd
release,
updates,
vadim.
C
Perfect,
so
someone
give
the
updates,
as
for
the
releases
for
nine,
is
proceedings
honestly
we're
just
rebuilding
and
fetching
the
latest
changes
in
from
fedora
34..
C
I
think
a
few
cvs
have
been
picked
up,
which
is
poked
and
probably
one
relates
to
the
channel
pizza
definitely
should
be
in,
but
they
don't
affect
openshift
in
general,
this
very
slow,
so
we're
pretty
safe
on
this
for
10
is
approaching
release
candidate
state,
so
we
have
switched
to
fedora
35
and
we're
building
it.
Based
on
the
latest
doris
who
was
stable
in
411,
we
started
experimenting
with
a
feature
called
coreos
layering.
C
That's
an
improvement
in
our
rpm
os
3,
which
allows
us
to
use
an
existing
container
already
contained
in
the
rocker
os
layer,
our
rpms
on
top
and
proceed
with
the
release.
C
That
would
help
us
spin,
the
exact
lowercase
releases
without
building
and
distribute
all
of
our
updates
in
in
the
images.
There
is
an
enhancement
for
the
openshift
to
extend
this
so
that
folks
would
be
able
to
add
their
own
custom
configuration
on
every
upgrade
on
top
and
using
build
config.
C
This
container
will
be
rebuilt,
so
that
would
help
us
bringing
things
like
drivers
on
every
single
upgrade
more
easily
and
have
a
better
controlled
way
of
distributing
one
single
image
into
their
multiple
we're
so
far
using
this
in
411
master,
not
yet
merged,
but
once
we'll
have
it
we'll,
probably
update
for
10.
C
If
that
he
didn't
say
the
most
interesting
thing
happens.
Also
in
the
installer,
notably,
we
have
adjusted
the
existing
tech
preview
assistant
installer
to
make
it
work
without
kidding.
But,
as
I
don't
know,
system
installer
is
a
web
service
which
allows
you
to
basically
install
a
cluster
using
a
classic
wizard
style.
C
It
generates
a
so-called
discovery
iso,
so
once
you
boot
from
it,
the
machine
will
be
registered
as
a
service,
and
you
will
be
able
to
tweak
its
host
name
to
see
networks
settings
to
see
how
the
disks
are
being
laid
out
and
prepare
for
the
intelli
installation.
This
happens.
It
also
ensures
that
machine
has
valid
dns
records,
all
things
necessary
before
the
install,
so
you
are
able
to
fix
them
with
ipxe.
C
It
also
uses
bootstrap
in
place
mechanism,
so
you
don't
need
an
additional
machine.
Bootstrap
one
of
the
masters
would
be
used
as
a
bootstrap
seamlessly
and
it
also
works
with
a
single
logo.
D
Okay,
so
we
had
our
meeting
last
week.
A
number
of
things
come
out
of
it.
I
think
the
first
one
is
that
the
code
of
conduct
and
the
deadline
for
comments
is
today.
So
there
is
a
discussion
item
there.
So
if
you
haven't
gone
and
read
it
and
had
a
look
at
it
and
you
want
a
chance
to
comment,
the
clock
is
ticking.
B
I
was
just
going
to
say
one
of
the
the
outstanding
questions
on
it
that
I'm
trying
to
get
resolved
is
the
email
to
whom
the
any
questions
or
issues
are
addressed,
and
at
this
point
legal
has
not
given
I've
put
a
couple
of
requests
into
them.
B
They
have
not
given
me
feedback,
so
what
I
was
going
to
suggest
is
that
we
just
have
put
an
alias
in
the
website
and
have
it
come
to
me
and
I
will
and-
and
I
will
address
it
with
the
chair-
the
whoever
the
current
chairs
are
of
the
of
the
working
group
and
and
bring
it
to
legal.
I
I
don't
think,
there's
an
issue
with
that
at
all.
I'm
just
trying
to
get
them
to
give
me
something
in
writing.
Saying
that's
the
correct
thing
to
do
so.
B
Rather
than
setting
up
an
email
server
for
okd
dot
io,
we
just
in
the
web
link
call
it
that
so
we
can.
We
can
work
that
out
that
way,
but
they
they
didn't,
have
any
objection,
but
they
also
had
no
response
to.
So
that's
never
a
good
thing,
but
I
think
we
just
need
to
move.
If
there
are
no
objections
in
the
next,
just
in
the
next
iteration
close
it
and
and
make
it
happen,.
D
Okay
sounds
good
on
a
similar
note,
we're
doing
some
work
to
actually
tidy
up
the
existing
github
repositories
to
actually
get
ready
to
move.
We
are
setting
up
an
okd
organization
on
github,
where
everything's
going
to
be
located,
so
we're
going
to
move
out
of
the
open
shift
that
will
allow
greater
community
involvement
in
those
gate
repos,
because
there
are
some
red
restrictions
where
we
are
at
the
minute,
so
I'll
just
make
our
life
easier.
So
we
are
doing
some
cleanup.
D
So
one
of
the
items
that
we
discussed
was
the
community
repo.
There
is
a
community
repo
in
the
open
shift,
org
with
five
markdown
documents
in
it,
so
we're
going
to
roll
them
into
the
okd
dot
io,
so
they'll
come
into
the
community,
documentation,
site
and
they'll
be
surfaced.
The
content
of
the
documents
will
be
surfaced
on
that
site.
D
Also
we're
looking
at
the
content
of
the
main
open
shift
repo.
So
that's
where
we
do
all
our
discussion
and
issues
and
reporting,
but
it
currently
has
some
documentation
in
there
as
well.
So
the
idea
is
that
we're
going
to
go
through
that
we're
going
to
pull
out
what
documentation
we
want
to
preserve
and
the
decision
has
been
that
the
official
product
docs
or
on
docs.okd.io,
and
that
is
run
by
red
hat.
D
It's
a
version
of
the
official
openshift
ocp
documentation,
customized
for
okd,
and
then
we've
got
the
community
documentation
site
which
is
okidi.io
and
that's
where
all
documents
should
live.
Technical
and
non-technical,
so
that'll
be
the
single
source
that
we
send
everybody
to.
So
that
said
that
we
want
to
move
the
documentation
out
of
the
main
okay,
repo
and,
and
that
sparked
a
conversation
which
I
don't
think
we
actually
got
to
a
conclusion
is
what
technical
document
do
documentation?
Do
we
need?
How
deep
should
it
be?
What
should
it
enable
the
community
to
do
so?
D
That
is
a
conversation.
That's
ongoing
to
start
with
we're
doing
some
research
so
before
we
actually
start
bugging
some
of
the
red
hatters
and
asking
for
their
time
we're
going
to
do
some
research
and
what's
in
the
repositories,
and
what
can
we
figure
out?
Should
we
allow
somebody
to
actually
pick
up
and
be
able
to
do
a
custom,
build
of
okd
purely
on
the
technical
docs?
Should
we
allow
them
to
go
and
create
things
like
and
customize
the
operators
or
install
or
maybe
customize
the
operator
catalogs
that
are
installed?
D
So
all
these
sort
of
conversations
are
happening
and,
as
I
say,
we
haven't
yet
come
to
a
resolution.
So
if
you
want
to
chip
in
on
that
conversation,
I
would
come
to
the
docs
group
or
put
comments
in
the
discussion
in
the
okd
repo
and
we'll
be
moving
that
on.
D
We
also
look
talked
about
the
operator,
but
I
see
that
is
on
the
agenda.
So
I'm
going
to
leave
that
one
for
the
later
item
and
today
daniel
created
some
issues
to
actually
kick
off
the
initiative
to
start
the
the
guides
for
4.9.
D
So
I
think
we'll
pick
that
up
the
next
stocks
group
and
I
also
noticed,
there's
a
discussion
item
being
added
to
today's
agenda
and
I
think
we
need
a
little
bit
of
coordination.
Just
so
there's
some
commonality
across
the
guides
and
there's
a
similar
structure
and
they
don't
look
like
they've,
been
written
by
six
independent
people
with
totally
different
ideas
of
what
what
should
be
in
the
guide,
so
we'll
coordinate
that
we
now
have
access
to
the
twitter
account,
but
I
don't
think
we've
decided
what
to
do
with
it.
D
B
I
just
have
a
quick
question
since
we
have
vadim
here-
and
I
haven't
seen
his
face-
one
of
the
things
that
I
I've
done
a
couple
of
tweets
and
I
did
a
tweet
on
a
release
and
I
was
thinking
to
add
into
the
release
process
very
standard
template
to
and
if
I
give
you
privileges
to
the
twitter
account
if
you
can
just
grab
basically
what
you
put
in
the
email,
a
slight
variation
on
that
and
just
tweet
that
out
each
time
you
do
a
stable
release.
B
C
Not
true,
I
passed
the
quiz
today
and
you
have
to
have
just
two
but
yeah
using
it
for
release
notifications
is
that
would
be
useful
mostly
to
get
some
notifications
from
from
the
community,
because
the
mailing
list
is
supposed
to
be
failed.
So
I
think
twitter
would
be
a
good
idea.
B
Yeah,
so
if
I,
if
we
are
the
two
red
hatters-
and
I
also
give
it
to
jamie,
then
I
think
we
are
recovered
by
for
our
social
media
standards.
I
took
that
quiz
too,
and
but
prior
to
that
quiz
I
got
reprimanded
for
not
using
bitwarden,
so
we
will
do
that
and
it's
all
fine
and
I'm
not
sure
jamie.
I
can
give
bit
warden
to
you
so
there's
that
whole
thing
so
anyways
vadim
will
get
you
on
it.
You
will
be
my
second
and
then
and
jamie.
B
We
will
figure
out
how
to
get
you
access.
So
if
those
three
and
then
ryan
you're
kind
of
the
acting
head
of
docs
right
now.
So
if
I
can
figure
out
how
to
get
external
people
into
bit
warden,
I
may
ask
for
an
exemption
from
bit
warden,
because
this
is
an
external
thing.
I
I.
I
would
think
that
the
the
people
who
are
basically
sharing
the
different
roles
are
the
ones
and
then
the
over
the
virtualization
folks,
and
if
the
micro
shift
people
come
in,
get
them
into
the
cadence
of
that
too.
B
A
A
B
A
Is
it
too
much
to
do
blog
posts
for
it?
Do
you
think
brian?
What's
your
thought,
given
the
number
of
releases
that
we
have.
D
I
mean,
I
think
the
twitter,
for
me
would
be
the
most
useful
just
to
know
that
it's
there
I
mean.
Obviously,
if
you
are
using
okd
regularly
you're
going
to
get
the
notification
through
the
the
update
manager
that
there's
an
update
available
and
I
think,
having
a
twitter
was
a
tweet.
I
I
think,
a
blog
post.
If
there's
anything
that
needs
to
be
explained.
D
Yeah,
if
there's
any
new
features
or
if
there's
any
gotchas
or
if
there's
a
and
beware
of
this,
if
you
take
this
one,
you
may
have
to
go
and
twiddle
something
manually
because
there's
some
change.
I
think
things
like
that
warrant,
a
blog,
but
just
for
a
an
incremental
release.
A
tweet
linking
in
maybe
the
release
notes
for
that
release
is
probably
good.
We
we
should
do
a
blog
if
there's
any
sort
of
gotchas
or
any
anything.
D
We
want
to
specifically
point
out
or
new
feature
or
new
capability
that
we
want
to
add
excellent,
okay
and
there's
one
more
thing
on
the
docks,
and
that
is
that
we
now
have
a
presentation,
template
and
in
the
chat
I
actually
did
post
the
link
to
it.
So,
if
you're
ever
speaking
anywhere-
and
you
want
an
okd
template
for
a
presentation,
it
lives
in
google
docs
and
the
link
is
also
in
the
hack
md
for
the
docs
docs
meeting
the
agenda
meeting
there,
I'm
not
sure
whether
we
have
any
way.
D
I
I'll
also
add
it
into
the.
If
we
think
it's
a
good
idea,
add
it
into
the
documentation
or
is
that
something
we
want
to
keep
just
for
this
community,
or
should
we
make
it
more
generally
available
for
people
we
can?
We
can
take
that
in
the
docs
meeting
next
week
to
make
that
decision
and
that's
it.
I
don't
think
I've
forgotten
anything.
A
Second,
here:
okay,
great
any
questions
for
brian
in
regards
to
documentation,
stuff.
D
A
Yeah,
we
haven't
really
tackled
that
one.
Does.
Anyone
in
this
group
have
a
sense
of
if
docs
working
group
still
captures
what
it
is
that
that
group
does
or
should
we?
You
know
I've
weighed
in
diane's,
weighed
in
brian,
has
weighed
in
a
little
bit,
but
anyone
else
here
in
the
general
group
have
a
thought
about.
Should
that
subgroup
have
a
different
name
since
it
does
more
than
documentation
or
is
that
does
everything
it
does
fall
under
documentation,
communications,
twitter,.
B
A
A
Hey,
let's
see
next
up,
are
the
platform
guides?
Take
it
away.
H
Okay,
so
brian
brought
up
a
a
really
good
point.
When
I
filed
issues
against
people
who
who
had
interest
in
writing
guides,
I
think
we
need
to
spend
a
little
bit
of
time
figuring
out
what
these
guides
should
be,
so
that,
like
they
shouldn't,
be
a
copy
paste
of
the
standard,
install
docs
right,
there's,
there's
not
any
value
in
having
a
copy
of
those,
so
my
conception
was
as
simple
as
it's
more
of
a
story
of
here's
the
decisions
I
made
when
I
did
this
particular
install
on
this
particular
platform.
H
But
if
we
want
to
talk
about
it
more,
should
we
do
that
here?
Should
we
do
that
in
the
in
the
in
the
docs
meeting?
What
do
people
want
to
do.
D
Well,
I
think
we're
missing
two
of
the
contributors
to
in
this
meeting,
so
we
probably
need
to
arrange
a
time
when
the
contributors
have
volunteered
are
all
going
to
show
up
somewhere,
gotcha,
okay,
either
that
or
we
do
it
offline
as
a
discussion
forum
and
let
people
contribute
within
the
discussion
topic
on
the
repo.
D
A
D
H
Happens:
sorry:
go
ahead,
no
good
yeah!
I
like
the
idea
of
trying
it
async
and
seeing
what
happens.
Okay,
then
I'll
start
a
topic
in
the
in
the
discussion
group
and
and
we
can
come
to
consensus
on
what
those
guides
should
be
the
I
guess,
I'll
close
those
issues
for
now,
since
I'm
not
sure
it's
worth
having
issues
for
work
that
we
haven't
decided
what
the
shape
of
the
work
should
be.
H
The
other
question
is:
are
we
close
enough
to
4.10
that
these
we
should
be
preparing
guides
for
4.10
rather
than
4.9?
At
this
point,
the
team?
What
is
your
sense
of
timeline.
C
C
I
don't
think
charo's
nukes
can
boot
from
ip9
things,
so
we
probably
won't
be
able
to
ask
you
to
produce
them
in
any
case.
That
requires
a
totally
separate
guide.
We
won't
have
to
update
them
from
what
the
scene,
quite
a
lot
of
folks,
are
still
using
ciara's
guide,
but
wait
still
using
guide
from
okd
for
the
five
times.
If
they
are
apparently
successful.
C
They
are
stable,
I
mean
we
can
really
use
anything.
The
problem
is
upgrade
jobs,
appealing,
that's
no
vm
bug
that
would
manifest
itself
as
a
api
breakdown.
We
can
work
this
around
any
day
and
we
go
with
this
table.
D
A
I
All
right,
can
you
hear
me
correctly:
okay,
great
okay
for
federal
course.
It's
rather
calm
those
weeks
and
but
we've
started
working
and
looking
at
the
changes
for
fedora
36,
so
federal
city
state
is
coming
later.
The
beta
is
coming
something
like
in
two
three.
I
I
don't
have
the
timeline
at
hand,
but
it's
you
know.
As
always,
we
we
start
looking
before
the
release
happens.
We
before
the
beta.
We
start
looking
at
the
changes,
so
I've
added
the
links
into
the
hacking
d
for
the
trucker
we've
made
for
all
the
federation
exchanges,
and
I
don't
think
we
have
any
changes
really
impacting
okg.
I
They
will
be
some
genus
over
here
that
support
id2
system
d
reserve
d.
Hopefully
that
won't
impact
okg,
but
that
to
just
be
tested
to
make
sure.
And
yes,
apart
from
that,
there
aren't
any
big
other
changes.
Yes,
there's
there's
a
lot
of
this
is
still
one.
One
of
the
changes
that
will
be
coming
with
federal
36
is
that
the
move
from
podman
3
to
portland
4
v3
before
but
as
okg
only
uses
that
for
bootstrap.
I
I
think
that
should
be
also
mostly
fine,
as
the
other
containers
run
and
with
cryo
on
the
fedora
morphed
records
side
of
things,
so
we
finally
trying
to
move
away
from
ivy
tables
legacy
back-end
to
the
new
iniftable-based
backend,
and
that
should
happen
sometime
shortly.
I
don't
remember
if
we
I've
scheduled
it
for
the
same
time
as
the
federal
36
release,
but
that
should
be
close
all
happening
soon.
I
don't
think
that
either
will
create
any
issue
for
kg,
but.
I
Just
bring
me
that
and
yeah,
I
think,
that's
the
main
items
right
now,
the
one
for
the
for
the
ip
tables
change.
It
might
impact
third-party
operators.
So
someone
from
the
typhoon
distribution
said
that
cdm,
for
example,
needs
some
special
configuration
so
folks
that
are
running
and
things
like
that
should
take
a
look
at
the
undertale
communication
force.
We
want
to
make
sure
that
they
match
the
type
of
epitables
packet
that
we're
using
I'll,
try
and.
C
A
Excellent
any
questions
or
comments
on
the
fedora
core
os
updates.
A
Thank
you
so
much.
Let's
move
on
now
to
the
rest
of
our
current
items
list
so
shut
down
the
dev
slack,
so
we've
all
agreed
to
do
this
diane.
What
do
we
need
to
do.
B
I
just
need
to
go
in
and
kill
it.
That's
it
if
everybody's
on
board
with
that
vadim
seems
to
be
on
board
with
that.
We'll
just
go,
kill
it
today.
So
today
is
the
official
end
date
of
that
channel
and
I
will
go
in
and
retire
it.
H
B
Yeah,
so
I'm
just
gonna
retire
it.
It's
had
a
message
in
it
for
for
a
week
or
so
wow
and
yeah,
we'll
just
archive
it.
A
Pretty
cool
all
right
next
up
is
is:
should
we
create
a
google
group
for
announcements?
The
docs
team
was
sort
of
talking
about
this
and
the
general
sense
was
no.
We
can
put
announcements
in
like
twitter
or
other
places,
but
do
we
want
to
the
flip
side
of
that
is?
Do
we
want
to
encourage
people
to
look
for
announcements
in
the
working
group,
because
some
things
get
sent
to
the
working
group,
like
so
vadim
posts
updates
in
the
working
group
and
some
folks
have
said?
A
Well,
you
can
go
look
at
the
working
group
for
this
update
on
okd
and
stuff,
like
that.
I
think,
if
we're
going
to
say
that
I
think
it
might
be
helpful
if
we
just
not
discourage,
but
we
avoid
directing
non-working
group
people
to
the
working
group
list
lest
people
start
asking
user
questions
again,
no
matter
what
I
think
we
got
one
this
morning,
that
was
a
user
question
in
the
working
group.
In
other
words,
it
would
be
nice
to
keep
the
working
group
google
group
just
for
working
group
business.
C
G
I
think
it's
fine
as
a
as
a
mechanism
that
we
that
we
can
offer
user
assistance
and
whatever,
because,
aside
from
it
being
asynchronous,
it's
also
directly
linkable
and
like
one
of
the
problems
I've
had
with.
G
I
all
right
actually
say
the
biggest
problem
I
have
with
with
people
asking
for
support
in
in
the
kubernetes
slack
is
that
it's
invite
only
and
on
top
of
that,
not
indexed
anywhere.
So
the
knowledge
just
kind
of
floats
away
into
the
ether
like
the
the
the
new
okd
matrix
room.
If
people
want
real
time
chat,
all
the
messages
are
there,
we
can
always
export
it
and
turn
it
into
documentation,
whatever
the
heck
we
want.
When
it
comes
to
the
stuff,
that's
on
github
discussions.
G
B
Right
any
other
thoughts,
so
is
that
we're
going
to
move
to
matrix?
Is
that
what
sorry?
I
got
distracted
there
for
a
minute.
A
A
Okay,
so
next
up
is
security
liaison
posting.
I
don't
know
what
else
to
call
it.
This
is
the
thing
that
I've
been
working
on.
I
did
it
a
long
time
ago,
but
just
didn't
dig
it
out
until
recently,
because
now
we
have
twitter.
Basically,
we
talked
about
this
in
the
docs
group
and
in
the
main
group
a
little
bit.
A
The
idea
is
that
we
need
someone
to
like
post
about
security
stuff,
at
least
so
we
have
some
security
posture,
that's
visible,
so
that
people
know
that
we're
thinking
about
it,
as
opposed
to
just
being
like,
oh
yeah.
We
have
you
know
red
hats
talking
about
this,
so
here's
what
I
came
up
with
doc's
group
didn't
really
have
any
much
feedback
on
it.
A
A
So
if
we
can
get
someone
to
volunteer
to
do
security
stuff,
like
just
track
down,
you
know
current
bugs
and
stuff,
like
that
current
vulnerabilities,
things
that
are
security,
oriented
and
then
just
be
able
to
com
like
formulate
a
response
in
terms
of
okd,
so
that
people
know
that
we're
actually
like
we're
cognizant
of
the
fact
that
these
are
on
the
radar.
One
of
the
reasons
is
because
we
get
a
lot
of
questions
in
the
chat
in
particular
about
does
this
impact
okd?
A
Are
you
aware
of
this
et
cetera,
et
cetera,
so
it'd
be
nice
for
us
to
have
a
concise
response
to
yes,
yeah
along
the
lines
of
concise
response
along
the
lines
of
yes,
we're
aware
of
this?
It's
on
our
list
or
no,
it's
not
on
our
list.
We
will
add
it
to
our
list
or
something.
A
A
Going
once
going
twice
right,
we'll
put
it
out
we'll
see
if
we
can
get
a
volunteer.
If
there's
anyone
in
this
group
that
wants
to
volunteer
to
do
that,
just
let
us
know
I
mean
it
doesn't
involve
a
lot
of
time.
Just
combing
through
you
know,
openshift
security,
vulnerabilities
and
maybe
f
cost
security,
vulnerabilities
and
just
sort
of
putting
it
all
together
and
in
one
little
place
and
sort
of
being
up
to
date.
B
A
B
Can
I
just
ask
timothy
how
they
do
it
for
f
cos?
Do
you
do
any
any
security
vulnerability
postings
for
the
fcos
project.
I
Okay,
sorry,
yes,
we
don't
have
our
our
own,
like
posting
on
previous
notes.
Yes,
on
this
front,
so
we
essentially
rely
on
the
federal
ones,
because
there
are
already
some
federal
security
misery
or
something
I
don't
remember
the
visuals.
I
I
So
if
you
take
a
look
at
that
here
on
the
main
page
here
with
the
release
notes,
which
are
right
now,
mostly
about
package
updates,
we'll
we're
working
on
trying
to
add
short
links
to
issues
we
fixed
into
a
given
release,
but
that
won't
really
that
will
not
really
be
tool
and
complete
accurate
list
of
all
the
cpus
that
will
be
fixing
the
given
release.
I
C
C
B
I
can
see
thank
you
muhammad
for
for
volunteering.
I
can
see
you
in
the
chat
volunteering
to
take
this
on
so
we'll
we'll
we'll
see
having
a
bit
but
anytime.
We
can
automate
something
like
if
we
can
grab
a
metadata
tag
on
in
the
release
and
just
put
a
note,
I
think,
that's
probably
step
one
but
also
yeah
whatever
you
guys
come
up
with.
That
would
be
wonderful
muhammad.
So
thanks.
A
Excellent,
so
it
looks
like
we
don't
even
have
to
post
anything.
Muhammad
has
volunteered.
This
is
great
it's.
I
really
appreciate
that.
Particularly
over
the
past,
like
year,
lots
of
people
in
the
group
have
been
stepping
forward,
take
little
bits
and
pieces
of
stuff.
That's
really
propelling
us
forward
quite
a
bit
all
right,
so
moving.
I
On
to
the
next,
just
a
quick,
quick,
quick
note,
I
think
if
okd
is
publishing,
although
the
person
that
are
included
in
the
less
content
for
for
the
version
of
packages
and
like
we
do
in
ocp,
and
you
can
probably
make
a
script
which
will
like
pull
a
given
release
of
okd
list,
all
the
packages
look
at
the
federal
database
of
all
the
cvs
for
which
versions
and
then
correct
the
two
and
then
post
that
somewhere.
A
Yeah,
that's
good
excellent.
All
right,
we
will
add
that
to
the
the
pipeline
of
things
to
do
to
assemble
this
security
release.
Thank
you
moving
now
to
operators,
so
it
was
discussed
at
the
docs
meeting
that
the
place
to
have
the
continued
discussion
on
operators
is
that
same
ticket
that
christian
opened.
A
So
we
now
have
the
names
of
folks
to
bug
so
we're
gonna
start
those
conversations
and
put
our
the
results
of
those
conversations
in
that
same
ticket
in
terms
of
trying
to
first
finding
out
the
viability
of
getting
an
okd,
specific
catalog
and
then
from
that
discussion,
depending
on
how
that
goes,
the
idea
of
getting
some
of
these
community
operators,
some
of
these
things
released
as
true
community
operators
and
we've
all
reached
out
to
various
operator,
point
people,
and
so,
let's
start
putting
all
of
that
info
in
one
place,
so
that
we
can
track
it
and
see
who's
talking
to
who
and
what
the
responses
were
on
these
comments
or
questions
on
the
operator
sort
of
sub
project
and
again
this
is
to
provide
operators
that
are
okd,
specific
and
ideally
get
some
of
the
red
hat
operators.
A
That
should
be
community
operators,
we
think
available
as
true
community
operators
and
possibly
an
okd
catalog
in
and
of
itself.
So.
A
Cool,
let's
see
and
then
we're
up
to
tasks,
amy
get
410
411
update
info.
I
don't
know
if
anyone
noticed,
but
there
is,
I
think,
scheduled
for
thursday.
A
video
presentation
from
red
hat.
Unfortunately,.
A
Tomorrow,
okay,
10
eastern,
all
right,
so
this
is
the
you
know
usual
like
three
hour,
video
presentation
on
all
of
the
things
that
are
coming
and
so
I'll
be
gathering
stuff
from
that
I'll
be
gathering
stuff
from
docs
and
we'll,
like
basically
assemble
a
list
of
that.
A
A
Charo
is
not
here.
I
can
touch
base
with
him,
though
micro
shift
invite.
Has
anyone
approached
the
micro
shift,
folks
about
inviting
them
to
the
meeting.
B
I
I
will
reach
out
to
them
for
the
next
meeting
to
see
if
we
can
get
them
on
the
agenda.
If
no
one
else
was,
unless
vadim
you
have
a
close
contact,
there.
A
Right
and-
and
that's
actually
the
next
item
so
brian
and
I
talked
with
vadim
and
vadim-
is
suggesting
that
we
put
in
pr's
for
changes
to
the
current
okd
repo,
because
there's,
who
else
did
you
want
vadim
to
take
a
look
at
that
to
those
changes?
There
was
someone
else.
A
Was
it
christian?
No,
it
was
who
else
was
inviding
that
you
wanted
to
take
a
look
at
the
any
proposed
changes
to
the
okd
repo
before
we
like
clean
up
was
clayton
clayton,
that
was
it
clayton
right,
yeah
yeah,
oh.
B
B
C
I
think
we
want
clayton
or
somebody
high-ranking
just
from
an
overall
view,
to
give
us
an
impression.
First
of
all
what
we're
missing.
We
know
we're
missing
azure,
for
instance,
and
they
would
be
interested
in
that,
but
to
cover
some
use
cases
which
we
don't
have
guides
for,
and
maybe
some
guides
are
just
first
of
all
need
to
be
created.
Second,
just
insufficient
quality,
and
maybe
we
should
just
drop
down
and
ask
some
dogs
folks.
Instead,
so
we
want
clayton
somebody
high
ranking
from
a
very
very
high
level.
C
I
could.
I
could
try
finding
someone
sure.
A
Let's
see
please
github
usernames
for
guides.
Okay,
we
got
that
one,
that's
I
think
done
basically,
but
for
the
guides
cross
that
one
out.
A
F
Yeah
sorry,
my
name
is
lev,
but
they
invited
me
to
this
meeting
as
a
guest.
F
I
discussed
today
following
his
excellent
work
on
adding
the
okd
support
for
assisted
installer
and
he
proposed
to
basically
discuss
it
in
this
forum,
because
right
now,
on
the
downstream
on
openshift,
there
is
a
console.openshift.com
which
actually
allows
to
use
the
system
installer.
F
And
my
suggestion
on
you
know,
question
if
it
will
be
possible
to
actually
have
the
same
system
for
okd,
because
I
think
it
will
greatly
simplify
it
for
anyone
who
will
want
to
try
the
okd,
because
he
will
not
need
to
create
his
own
assisted,
installer
infrastructure,
basically
to
run
it
himself,
but
he
will
be
able,
for
example,
to
go
and
not
to
console.okd
dot
io
and
have
this
familiar
interface-
and
you
know
just
type
in
the
data
into
the
ui
and
get
his
system
installed.
C
No,
not
necessarily
as
in
we
can
have
different
authentication
methods,
but
if,
first
of
all
the
question
it
brings,
how
do
we
authenticate
so
we
probably
could
pick
github
or
google,
but
still
there
are
a
lot
of
questions
around
this
idea.
So
if
we
would
host
our
own
assistant
solar
service,
we
would
also
have
to
be
responsible
for
user
data
and
it's
not
just
domain
names.
We
collect
agents
ascending
quite
a
lot
of
important
information
like
network
data.
C
Why
would
we
want
to
have
this
instance
if
there
is
already
an
openshift
provided
one
and
it
has
the
same
features,
and
it
already
gives
you
the
very
same
ocp
no
locally,
but
people
posted
them
here.
What
they
want
is
a
disconnected
cluster
so
that
they
will
have
to
report
to
red
hat
or
anybody
associated
around
that
it's
a
very
interesting
problem
to
solve.
C
Really,
but
user
data
handling
and
maintenance
and
authentication
are
serious
problems
which
we
just
don't
want
to
jump
in
onto
those
we
could
find
infra
we
could
find
hosting.
C
We
could
host
it
with
door
and
things,
but
these
are
the
questions
we
need
to
have
answered
before
we
start
approaching
so
far
you
can
host
assistant
installer
on
anything
which
can
run
footman.
C
C
So
we
are
aiming
towards
slimming
down
the
requirements
instead
of
having
a
centralized
ocd
specific.
But
if
anybody
wants
to
solve
these
problems
or
at
least
start
discussing
them,
we
are
very
open.
It's
just
we're
not
yet
ready
to
start
posting
our
own
service.
D
So
so,
would
this
service
work
in
an
anonymous
way
if
we
just
want
to
use
it
as
an
installer,
where
I
fill
in
a
form
and
then
ships
me
back
the
iso
or
whatever?
I
need
and
then
forgets
everything
I
ever
told
you
would
that
model
work,
because
I'm
guessing
within
the
ocp.
You
then
link
it
into
your
central
management
console.
D
So
you
do
want
to
capture
all
that
information,
but
for
an
okd
for
an
open
source
user
as
a
mechanism
of
just
providing
an
easy
install
where
nothing
is
then
stalled
or
maintained,
it's
a
fire
and
forget
function
where
you
just
get
effective
the
install
and
then
none
of
the
data
is
actually
stored
anywhere.
It's
just
forgotten
once
that
transaction's
finished
is
with
that
model
work
in
this
case,
or
is
there
more
complexity
where
you
need
to
actually
keep
that
data
around.
A
And
I
want
to
say
actually
hold
on
one
sec.
I
do
want
to
say
that
muhammad
said
the
exact
same
thing
in
the
chat
muhammad
did
you
have
anything
you
wanted
to
add
to
that?
So
muhammad
said
what
if
it
was
a
simple
installer
ui
for
local
installation,
no
sso
or
just
a
web
ui
an
engine
for
a
kind
of
gui
installation
muhammad?
Did
you
have
anything
else?
You
wanted
to
add
what
you
typed.
K
C
Yeah,
that's
basically,
so
that's
exactly!
Basically,
the
state
of
assistance
installer.
Now,
if
you
deploy
it
locally,
it
has
no
authentication
or
nothing,
but
if
somebody
creates
a
cluster,
meanwhile,
you
will
still
be
able
to
see
all
the
details
and
before
the
host
between
the
moment
that
the
host
is
the
cluster
is
created,
the
hosts
are
being
discovered
registered.
C
Everybody
can
see
each
other
post
and
see
all
the
information
like
network
details,
disk
details,
things
like
that
because
of
the
nature
of
bootstrap
in
place,
installer
assist
installer
has
to
be
running
during
the
installation
during
the
construction,
so
you
are
for
at
least
an
hour.
Your
quite
exposed
publicly.
C
It
can
be
solved
by
authentication
and
a
system.
Installer
has
some
authentication,
but
nevertheless
storing
this
data
passing
it
around
and
having
it
a
connected
installation
are
very,
very
let's
say
they
are
as
far
as
possible
from
what
the
pd
wants
to.
Actually
we
want
to
give
people
their
own,
disconnected
environment,
they
want.
We
want
to
give
them
options,
not
to
report
to
and
have
it,
and
if
we
would
host
the
centralized
service.
That
would.
G
C
C
That
would
host
that
would
fix
quite
a
lot
of
issues
from
for
our
potential.
A
I
mean
I
could
see
like
slapping
a
an
interface
on
my
visor
upi's
work,
that
I
did
that
automates
up,
easter,
epi
and
I'd.
Imagine
other
folks
have
similar
things,
so
we
could
do
something
local
lev.
Do
you
want
to
we're
running
on
low
on
time?
Did
you
want
to
open
a
discussion
item
in
our
repo
and
then
that
way
folks
can
chime
in
on
this,
and
we
can
have
this
as
an
ongoing
discussion
and
see
what
we
can
come
up
with.
A
I'm
not
sure
how
I
do
this
on
your
environment,
I'll,
give
you
the
link
right
now
and
then
just
go
ahead
and
post
a
discussion
item
explaining
what
your
thoughts
are
and
what
you'd
like
to
see,
and
here
I'll
put
it
in
the
chat
right
now.
A
That's
the
discussion
section
for
for
the
project,
so
just
go
ahead.
There
open
up
a
discussion
item
and
then
folks
will
chime
in
with
their
ideas
and
we'll
see.
If
we
can
make
something
out
of
this,
you
know
it's
longer
term.
This
is
a
mid
to
long
term
request.
I
think,
as
opposed
to
short
term,
but
at
least
we
can
start
some
discussion
on
it.
Okay
sounds
good
thanks
awesome.
Thank
you
for
attending
the
meeting
and
thank
you
for
participating
anything
else.
A
All
right,
well,
thanks!
So
much
folks
have
yourselves
a
great
rest
of
your
week
and
dots
working
group
meeting
same
bedtime
same
bat
channel
next
week
and
then
we'll
meet
back
here.
Two
weeks
for
the
main
group
meeting
see
you
soon.