►
From YouTube: OKD Working Group Meeting 02-01-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
The
okd
working
group
meeting
for
february
1st
of
2020-
and
we
have
got
a
a
pretty
quick
agenda
here,
but
we'll
jump
right
into
it.
Don't
forget
to
put
your
name
in
the
attendees
section
of
the
heck.
Md
documents
drop
the
link
in
there
and
we
can
drop
the
link
again
and
if
you
have
any
suggestions
to
modify
the
agenda,
let
me
know
if
there's
anything
you
want
to
add
to
it.
A
All
right,
seeing
nothing,
let's
start
out
with
release
updates,
so
it
looks
like
vadim-
did
put
some
updates
in
there
in
terms
of
the
latest
for
okd,
and
it
looks
like
that
there
is
a
4.10
code.
Freeze,
4.11,
nightlys
are
being
prepared
and
4.10
is
now
fedor,
35
based
and
and
the
1.23
kubernetes
rebase
landed.
A
Expecting
one
point
two
two
point:
five
rebates
to
land
in
four
nine,
so
that
we
could
rebase
four
nine
to
f
thirty
five
and
the
any
questions
about
that
or
anything
you
want
to
talk
about
about
that
is
that
pretty
pretty
clear
the
team
threw
those
in
there
seems
pretty
straightforward.
A
No,
and
actually
you
know,
I
think
sandra
made
a
good
point.
You
know
two
meetings
ago
that
you
know
we
should
get
ahead
of
the
ball
here
and
start
figuring
out
what
is
going
to
be
in
future
releases
like
410
411,
so
that
we
can
promote
them
and,
basically,
you
know,
be
get
ahead
of
the
game
as
opposed
to
sort
of
behind
the
game,
or
you
know,
sort
of
playing
catch-up
in
terms
of
promoting
okd,
as
the
ocp
releases
come
up.
A
So,
let's
find
out
who
wants
to
take
that
out
as
a
task
to
figure
out
what
is
coming
in
410
and
411.?
Anyone
want
to
take
that.
A
B
B
A
Yeah
usually
they'll
have
that
like
hour
and
a
half
video
meeting,
and
I
haven't
seen
that
pop
up
yet
but
okay,
why
we'll
do
some
investigative
work
so
anything
else
on
okd
itself.
D
A
Okay,
excellent-
that
is
good
news.
I
just
pinged
dusty
to
see
maybe
he'll
pop
in
to
the
meeting
here
to
talk
about
any
f
cost
stuff,
see
what
happens.
Okay,
let's
move
on
from
f
cos
stuff,
docs
update
brian.
Take
it
away.
C
Okay,
we
had
our
dock
speeding
last
last
tuesday.
Again
it
was
a
pretty
quick
meeting.
Nothing
really
came
up
with
the
issues.
We
did
continue
the
conversation
around
slack
channels.
I
think
the
conversation
was
that
we
want
to
keep
presence
in
that
kubernetes
slack
channel.
C
There
was
talk
about,
should
we
merge
the
dev
and
the
user
channel,
so
we
just
have
one
slack
channel,
because
we
don't
really
have
a
devs
of
the
stream
going
on
and
there's
a
lot
of
confusion
in
the
community
about
where
to
post
and
most
people
end
up
cross
posting
just
everywhere
to
try
and
get
responses.
C
No
movement
on
the
community
survey
and
we
need
to
chase
that
up
gritty
had
been
away,
so
hopefully
we
can
move
that
next
meeting
and
then
a
conversation
that
did
come
up
was
as
we
move
to
the
new
repos.
C
Is
there
a
need
to
have
the
separate
community
repo
at
the
minute
we
have
like
a
a
community
repo
in
the
open
shift
and
org,
which
has
five
documents
in
it.
So
as
we
move
to
an
okd
organization
out
of
the
openshift
organization,
there
was
a
discussion
and
again
I
think
we
were
going
to
defer
to
diane
and
just
ask
if
there
is
any
reason
why
that
needs
to
be
kept
separate
or
any
sort
of
reasons
why
it
was
set
up
that
way.
C
If
not,
we
could
just
merge
that
into
the
okd
repo,
I
think.
In
there
there
was
like
a
membership
list,
and
then
there
was
the
code
of
conduct.
C
Within
that
one
repo,
what
else
was
did
we
talk
about.
C
Oh
yeah,
there
was
an
interesting
discussion
within
red
hat.
There
was
there'd,
been
a
meeting
around
setting
up
a
new
subgroup
for
the
operator
catalogue,
there's
obviously
some
movement
going
on
around
creating
an
okd
version
of
the
red
hat,
ocp
catalog,
and
I
think
that's
probably
a
a
reasonable
conversation
for
for
this
group
to
actually
how
do
we
want
to
handle
that
who
should
be
on
or
who
wants
to
be
on
it?
A
Yeah
and
we'll
we'll
take
the
slack
channel
thing
as
a
separate
item
new
business
in
a
second
for
context.
There
was
a
meeting
just
under
two
weeks
ago
that
sandro
organized
that
was
basically
like.
A
What's
the
roadmap,
the
the
virtual
folks
wanted
to
know
what
the
roadmap
is
for
okd
so
that
they
could
do
their
planning
accordingly,
and
in
that
meeting
there
was
lots
of
discussion
about
operators
and
operator
hub
community
catalog,
opd
catalog
and
it
seems
like
folks,
are
the
idea
of
an
okd,
specific
catalog,
but,
as
brian
said,
like
who's
going
to
be
involved.
How
do
things
get
vetted?
Do
we
have
access?
So
there's
lots
of
questions
to
that.
So
the
idea
was
that
the
folks
who
are
interested
are
going
to
get
together.
A
I've
been
engaged
with
christian
hernandez
on
some
of
the
get
ops
pipeline
questions
that
I
had
and
you
know
he
asked
well
do
you
want
this
is
your
thought
that
you'd
want
this
to
be
in
the
community
catalog?
A
And
yes,
if
not,
you
know
at
the
very
least
in
the
community
catalog,
but
ideally
in
a
new,
separate,
okd
catalog.
You
know
yeah.
C
And
I
think
one
of
the
big
comments
about
having
them
in
the
community
catalog
is
that
would
cause
confusion
for
ocp
users,
because
they
might
see
two
versions
of
each
red
hat
operator,
one
coming
from
the
ocp
behind
the
the
user,
account
sort
of
firewall
and
then
one
in
the
public
community
catalog
and
that
wouldn't
be
a
great
user
experience.
So
that's
why
there
is
talk
of
a
separate
ocp
cap,
okp
catalog,
so
we
wouldn't
get
that
duplication
of
operators
coming
from
the
community
catalog
for
ocp
users.
A
So
I'm
interested,
I
think,
brian
voiced
an
interest,
bruce
voiced
an
interest
in
sort
of
tracking
this
down
and
what
not
so
we're
going
to
create
a
shared
document
and
just
start
putting
in
any
information
we
can
gather
about
this
and
the
context
of
people
that
we're
talking
to
and
see
if
this
will
fly
as
an
idea.
So
folks
are
interested
just
put
your
name
in
this
particular
agenda
item.
A
If
you're
interested
in
sort
of
participating
in
that
sub
conversation,
I
don't
know
if
we're
going
to
do
like
a
full
on
like
sub
working
group
or
what
I
think
it
will
depend
on
what
we
find
out
after
our
initial
exploration
of
you
know,
are
we
able
to
have
a
separate
okd
catalog?
Do
we
get
to
maintain
it
in
some
way?
You
know
once
those
questions
get
answered,
I
think
it'll
determine
the
workload
for
people.
A
All
right
now,
let's
keep
moving
on
to
next
up,
is
oh
and
by
the
way
diane
does
have
now
the
credentials
to
the
twitter.
A
She
got
them
from
driti,
but
diane
is
on
vacation,
so
we
don't
have
direct
access
for
twitter
yet
and
diane,
and
I
haven't
arranged
a
handoff
so
that
more
than
just
her
and
riti
have
the
credentials,
but
then
we
can
start
utilizing
the
twitter,
so
issues
are
there
any
issues
in
the
okd
repo
that
stand
out
that
folks
want
to
talk
about,
seems
like
a
lot
of
them
are
really
old.
We
haven't
really
had
any
new
issues
pop
up.
A
It's
just
me,
but
I'm
not
really
seeing
anything
in
there.
B
A
Anything
in
terms
of
the
discussion
items
same
thing
stand
out
in
terms
of
discussion
items.
We've
got
alert
manager
stuff.
Someone
else
was
mentioning
alert
manager
stuff.
That
was
you
right
bruce.
You
had
some
alert
manager
issues
as
well.
E
Yeah,
I
know
when,
when
upgraded
to
the
the
latest
version
on
my
test,
cluster,
which
went
for
it
was
going
from
the
I
think
the
1212
version
to
the
one
that
just
came
out.
It
went
through
everything
you
know
perfectly
updated
all
the
operators
all
of
the
nodes
and
then
finally,
the
alert
manager
got
in
a
you
know,
crash
cycle
and
the
the
this
is
like
a
the
alert
manager
main
pods,
which
each
have
five
containers.
E
So
they
seem
to
be
fairly
complicated,
but
in
any
case
they
all
were
crashing
with
a
with
about
a
six
line.
Message
in
the
logs
saying
that
it
was
missing
a
port
on
my
email
address,
and
so
in
my
spare
time
I
haven't
had
a
lot
of
minutes
to
chase
it
down,
I'm
trying
to
find
the
offending
gamal
that
has
the
partial
information
that
wasn't
complete.
E
A
All
right-
and
I
see-
we've
got
that
someone
else
has
a
discussion
item
on
that.
We've
also
got
some
stuff
with
operator
stuff.
Brian,
you
put
one
in
on
an
operator
which
one
was
that.
C
Yeah,
I
noticed
that
it
looks
like,
within
the
community
operator
hub
installed
on
okd
and
4.9,
there's
now
a
dependency
to
the
red
hat
marketplace
for
the
devfile
operator,
which
obviously,
okay
doesn't
have
access
to.
So,
even
though
the
the
che.
C
C
That's
just
been
pushed
into
the
community
for
okd
into
that
catalogue,
which
I
think
then
goes
back
into
the
the
whole
catalogue
operator.
Catalog
discussion
for
okie
d.
A
A
A
So
we
should
do
that
via
twitter
as
soon
as
diane
is
back
and
also
maybe
through
the
website
and
whatnot
new
items
shut
down
the
dev
slack.
So
the
last
person
to
talk
to
about
this
was
vadim
to
be
sure
that
this
wasn't
gonna
cramp,
the
style
of
of
any
of
the
red
hat
folks
he's
on
board
christian
glenn
beck
is
on
board,
so
I
guess
we
can
shut
it
down
and
people
say
merge
it
in,
but
I
don't
there's
really
nothing
happening
there.
A
A
Yeah,
actually
I
I
note
that
mike
is
doing
been
doing
a
really
great
job
of
like
letting
people
know
that
it's
for
dev
questions
only
and
it's
slated
to
be
deprecated,
so
that's
appreciated.
A
Okay,
next
up
is
doc's
troop
to
create
a
security
posture.
That's
still
gonna
be
happening,
send
something
out
for
security.
Ladies
and
I
have
something
out,
but
without
the
twitter
we
can't
really
send
there's
no
place
to
send
it.
I
guess
I
mean
I
guess
we
could
put
it
on
the
website.
A
Charo
was
gonna
download
the
stats
charles,
not
here,
meeting
the
crc
group.
That
happened.
Actually,
that's
done
daniel.
C
C
I
don't
know
that's
a
good
question
anyways
that
seems
to
be
aimed
at
because
I
mean
one
of
the
challenges
we've
always
said
with
go
ready.
Containers
is
the
memory
footprint
and
micro
shift
seems
to
be
addressing
that
in
a
big
way,
and
would
that
be
a
better
route
for
us
to
go
down?
Is
there
a
need
for
crc
if
we
can
get
microshift?
I
know
it's
it's
an
early
project,
it's
not
yet
sort
of
released,
or
it
is
a
sort
of
a
an
incubator.
D
C
B
I'm
a
lot
more
optimistic
about
microchip
being
able
to
handle
these
cases
than
the
current
crc,
because
current
crc,
I
can't
even
run
on
any
of
my
computers
like
what
I
think
it
would
be
worth
it
if
we
could
bring
the
microchip
people
onto
the
okd
working
group,
maybe
either
to
give
a
presentation
or
a
briefing
or
like
talk
to
us
about
about
it,
because
I'm
excited
for
the
potential
that
we
could
have
a
new
mini
shift-like
experience
using
microshift,
because
what
we've
got
now
is
pretty
inaccessible
to
most
people.
A
Okay,
so
micro
shift
invite
I'm
just
going
to
add
this
to
the
to
do's,
where
the
other
item
was
and
yeah.
I
think
it's
at
least
invite
him
to
the
meeting
to
talk
about
it
and
then
from
there
like
just
find
out
ways
in
which
we
can
work
together.
So
there
we
go
all
right,
that's
added
to
it
and
there's
a
link
actually
in
the
meeting
notes
to
the
to
the
micro
shift
project
forward.
A
Thinking,
let's
see
and
brian
clean
up
the
okd
repo
of
old
guides,
we
need
to
meet
with
vadim
on
that
and
decide
like
what
needs
to
be
maintained.
I
haven't
had
a
chance
to
meet
set
up
a
meeting
with
the
three
of
us,
but
can
do
so.
A
Diane
came
to
the
conclusion
that
there's
really
not
much.
We
can
do
in
terms
of
getting
the
the
okd
repos
from
their
respective
repository
github
and
get
lab
so
we're
going
to
go
with
okd
dash
project
and
start
moving
things
over.
A
Let's
see
get
user
names
for
for
guides
right.
I
don't
think
daniel's
done
that
right
and
then
brian.
What
did
we
have
for
over?
What
was
your
task
for
overt
I'm
trying
to?
Oh
that's
right!
That
was
part
of
this
whole
thing
right.
C
A
Yeah,
so
I'm
let
me
just
cross
this
out,
and
the
question
now
is,
you
know
say
this
is.
A
There
we
go
clean
that
up
a
little
bit.
Okay,
so
we'll
find
the
proper
place
to
put
those,
and
the
request
is
in
for
matrix.
Is
there
any
update
on
that
deal.
B
Yeah,
so
it's
done,
the
room
exists.
I
I
got
it
created
last
week
and
I
worked
with
kevin
fenzie
to
figure
out
like
some
of
the
synchronization
stuff.
So
now
people
can
join
the
room
and
stuff,
I
think
now.
Where
do
we
want
to
put
docs
about
it
and
things?
Because
I
don't
know
where
we
want
to
put
it,
the
room
exists.
B
B
Yeah
so
tell
me
what
to
do
or
help
me
figure
out
where
I'm
supposed
to
do
it
and
how
and
what
we
can
we
can
get
it
added.
A
I
would
say
put
something
in
put
a
a
put
an
issue
in
the
website,
repo,
the
okd.io
and
then
brian
can
work
with
you
on
getting
that
onto
the
website.
A
Alright,
as
soon
as
diane
is
back,
then
we'll
put
it
out
over
twitter
and
link
to
we'll
probably
link
to
the
webpage,
as
opposed
to
linking
directly
to
the
room,
because
we're
going
to
want
to
like
have
a
little
bit
of
pretext
about
like
what
it
actually
is,
because
not
everyone
is
going
to
know
what
matrix
is
right.
A
B
A
C
I
guess
the
other
thing
around
there
is,
I
just
think,
as
we're
shutting
down
other
communication
channels.
I
think
we
just
want
to
be
clear
about
what
we
expect
to
happen
there
when
people,
when
users
should
go
there,
why
they
would
want
to
go
and
sort
of
install
the
apps
and
get
access
to
it
and
what
is
there
and
and
all
of
that
sort
of
stuff,
because
I
think
having
clarity
is,
is
good.
A
Let's
see
what
else
do
we
have
here-
boston,
fifth
and
sixth
and
openshift
commons
february
9th-
and
there
are
the
dev
conf
items,
which
happened
and
actually
diane
was
not
able
to
log
into
those
remotely.
So
it
was
just
christian
and
a
couple
of
new
people
that
showed
up
at
the
docs
meeting
last
week
was
really
cool.
A
We've
got
three
new
folks
that
are
interested
in
participating
in
this
group
in
one
fashion
or
another,
and
some
of
them
were
involved
with
presentations
at
devcon,
so
very
cool
stuff.
A
A
Oh
right,
so
the
idea
was
that
sandra
put
two
in
two
instances.
Within
a
24-hour
period,
people
were
suggesting
that
folks
go
to
the
working
group.
Google
group
for
user
based
stuff
or
they've
had
a
posting
in
the
working
group.
They
linked
to
a
posting
in
the
working
group.
Email
like
oh,
I
know
what
it
was
sandra
linked
to
the
deem's
email
about
the
release,
the
most
recent
release,
and
then
there
was
something
else
where
someone
suggested
that
they,
the
best
place,
was
in
the
working
group,
and
so
I'm
starting
to
think
is
there.
A
Do
we
want
to
maintain-
and
this
is
something
that
the
docs
group
can
I
guess
take
up.
Do
we
want
to
maintain
an
announcement
email
list,
something
that
actually
is
pushed
to
people
as
opposed
to
the
website
and
the
chat
areas?
I
know
everyone's
like:
oh,
not
another
communications
channel,
but
a
push
thing
people
can
sign
up
for
or
we
can
have.
You
know
we
can
add
people
or
whatever,
so
that
they
can
get
notice
of
new
releases
and
things
like
that.
A
Yeah,
what
can
we
do
then
to
get
vadim's
releases
up
on
the
website
so
that
we
don't
have
to
link
people
to
a
twitter
post
about
it?
I
don't
want
to.
In
other
words,
I
don't
like
the
idea
of
us
linking
to
the
working
group
for
users
to
see
that
like
they
should
have
something
a
little
more
presentable.
I
think
about
releases.
C
I'm
I
I
think,
they're
we
need
to
have
a
conversation
around
pipelines
and
automation,
because,
whether
it's
a
gift
of
action
somewhere
or
whether
we
have
a
pipeline
tecton
system
running-
but
I
mean
theoretically,
if
we
should
be
able
to
create
an
automatic
push
to
a
page
on
the
in
the
docs
repo,
which
adds
it
as
a
banner.
To
the
I
mean
we
can
do
something,
so
it's
adabana.
A
All
right
well,
we'll
take
it
up
in
the
docs
group
and
and
first
off
we'll
have
to
figure
out
the
technology
part
and
see
like
do
we
want
this
to
be
external.
You
know
I
can
offer
up
a
pipeline
a
tecton
pipeline,
but
if
we
can
do
it
with
the
get
pipelines
just
as
easy,
you
know.
C
A
C
So
I
don't
know
whether
that
causes
us
additional
challenges
with
doing
builds
within
the
red
hat
system
versus
outside
of
it
in
terms
of
pipeline,
but
yeah.
I
just
think
I
mean
there
is
automation
that
does
the
release
so
as
part
of
that
it'd
be
great.
If
we
could
just
have
an
automatic
push
that
updates
a
banner
somewhere
yeah,
we
shouldn't
have
to
do
manual
work
to
do
these
sort
of
things
for
sure.
A
All
right,
we
will
investigate
that
any
last
minute
things.
A
All
right:
well,
let's
end
this
meeting
because
we
are,
I
think,
we've
got
everything
dusty
did
you
have
anything
you
wanted
to
add
about
latest
fedora,
cora
west
stuff
dusty
did
end
up
logging
in.
Is
there
anything
you
wanted
to
add
about
latest
news
for
fcos
that
we
should
be.
F
I
don't
have
anything
off
the
top
of
my
head.
I
know
we're
about
to
make
a
change
related
to
iptables
flash
nf
tables,
but
we'll
send
out
an
announcement
about
that
shortly,
we're
basically
just
switching
the
default
from
iptable's
legacy
to
nf
tables.
F
Right
yeah,
so
rel
8,
I
guess,
decided
to
bite
that
bullet
early,
obviously
they're
looking
at
supporting
things
for
longer,
and
so
they
decided
to
make
that
change
early
earlier
than
fedora
did.
I
think-
and
we
didn't
automatically
pick
up-
that
change
in
fedora
core
os,
because
the
way
it
was
implemented
was
via
alternatives.
F
There's
some
technical
reasons
why
alternatives
don't
actually
get
picked
up
and
used
correctly
in
in
our
os
tree
based
systems,
so
we
missed
the
change
originally
just
because
of
that,
and
so
this
is
us
trying
to
get
back
in
line
with
what
the
rest
of
fedora
is
doing
by
doing
a
migration
for
existing
systems
over
to
nft,
but
we're
also
allowing
people
to
choose
to
stay
and
not
be
migrated.
F
So
there's
a
communication
going
out
about
that
pretty
soon
but
yeah
as
far
as
okd
is
concerned,
I
don't
know
if
okd
already
switches
like
systems
that
are
start
on
foot
or
core
os
to
use
iptables,
nft
or
not
either
way
it's
something
to
look
out
for
and
just
to
make
sure
you're
doing.
The
right
thing.
A
Awesome
thanks
dusty
all
right
folks,
I
think
that's
it
see
you
all
at
the
docs
meeting,
if
you're
interested
in
the
docs
meeting
that's
same
bat
time
same
bat
channel
next
week
and
then
I'll
see
the
rest
of
you
all
in
two
weeks
for
our
main
meeting
and
by
then
brian
vadim,
and
I
will
have
met
and
hammer
out
these,
these
last
few
items
that
we
need
to
get
to
all
right,
see
you
folks
I'll
stop
the
recording.
B
Well
before
we
before
everyone
goes
there's
a
couple
of
quick
things
I
want
to
want
to
point
out.
I
believe
so
this
weekend
is
fosdem
and
I
believe
sandro
is
going
to
be
talking
about
okd
virtualization
there.
So
that's
so!
If
you're
interested
in
checking
that
out,
you
can
go
to
fosdem.
There's.
B
Yeah,
there's
a
link
in
the
meeting
notes
for
that
you
can
check
out
the
general
fosdem
website,
there's
also
a
centos
dojo,
that's
preceding
fosdem,
and
I
don't
know
if
there's
anything
particularly
okay,
relevant
here,
probably
not
but
whatever
and
yeah.
That's
all
I
have
thank
you.
A
Yeah
and
then
there's
also,
I
put
it
in
there-
there's
the
open
shift
commons
gathering
on
git,
ops
and
I'll
be
presenting
on
the
get
ops
work
that
I'm
doing
for
icpsr
and
I
think
vadim
is
presenting
something
or
no
christian
hernandez
is
gonna,
be
presenting
something,
let's
get
the
ops
related.
So
all
right
folks,
I'm
gonna,
stop
recording
and
thanks
for
coming
to
the
meeting,
we'll
see
you
next
time.