►
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
Updates
so
welcome
to
the
okd
documentation
and
communications
subgroup
meeting
for
december
14th
of
2021,
and
this
will
be
our
last
meeting
for
the
year
and
actually
the
last
okd
meeting
for
the
year
overall
and
so,
let's
start
out
looking
at
current
projects.
The
charter
updates
nothing
yet
for
me
on
that.
Nothing.
Yet,
on
the
the
basically
install
and
read
me
stuff,
I
think
we've
almost
got
everything
moved
over.
A
And
create
a
dock
for
the
build-out
line.
Haven't
done
that
yet
vadim
hasn't
been
available
for
a
regular
meeting
time
brian.
Maybe
we
should
set
up
a
time
to
meet
with
vadim
and
just
talk
to
him
about
this
like
separate
in
the
new
year,
since
it's
been
kind
of
hard
to
catch
him
at
meetings.
A
A
Okay,
excellent
code
of
conduct,
search
and
replace
michael,
have
you
had
a
chance
to
do
a
search
and
replace
on
the
code
of
contact
document?
I.
C
Okay.
The
team
has
given
his
looks
good
to
me.
So
if
the
rest
of
the
team
here
can
take
a
look
at
it,.
A
A
D
A
Hash
things
up
all
right
so
I'll,
send
some
I'll
add
that
as
a
task
I'll
send
out
something
to
the
working
group,
send
email
to
working
group
to
look
at
code
of
conduct.
A
Hey
survey,
I
don't
know
what
the
status
of
that
is.
I
think
we'll
have
to
reach
out
to
dritis
separately
yeah
outside.
E
E
E
A
E
That
yeah
there's
I'll
keep
pinging
her
too
and
and
ccu
on
in
slack.
So
eventually,
because
I
would
like
to
get
the
username
password
shared
with
between
you
and
I
as
well
for
the
twitter
so
in
as
well
as
figure
out
what
to
do
next
for
the
survey.
So.
A
Yes,
yes,
daniel
is
not
here
to
talk
about
the
guides
updates
for
folks
who
weren't
at
the
full
meeting.
He
was
in
the
full
meeting
and
gave
an
update
and
we
decided
to
do
it
as
a
discussion
thread.
A
So
he's
going
to
be
doing
that,
probably
in
the
new
year
to
round
out
the
guides,
update
and
then
that'll
clear
everything
out
of
the
repo
that
is
sort
of
content
related
and
he'll
work
with
brian,
on
making
sure
that
that's
all
nice
and
pretty
on
the
website.
E
In
early
january
or
late
january,
we
have
the
dev
conf
cz,
which
is
now
virtual.
What
I'd
like
to
do
is
add
a
task
and
I'll
take
this
on
too,
with
some
with
christian
is
to
update
the
presentation
slides
that
we've
been
using
whenever
we
do
an
office
hours
or
when
we
do.
These
meet
up
hallway
meet
up
things
at
there,
so
that
we
have
a
an
updated
set
of
slides.
E
We've
been
using
the
same
slides
for
a
while,
and
I
think
they're,
due
for
a
bit
of
revision
as
well,
especially
with
the
new
release
and
4.9
information,
make.
A
Sure
you
make
sure
you
grab
the
version
that
we
had
if
in
what
was
the
event.
E
Just
throw
it
in
here
or
share
it
with
me
and
I'll
I'll
do
it.
I
just
want
to
make
sure
we
have
some
of
the
latest
stuff
in
there
and
and
and
also
because
bruce
you
had
been
asking
those
questions
about
c
groups,
v
v2,
that
and-
and
that
is
something
that's
in
fedora
core
os
or
is
coming
in
fedora
core
os,
but
it's
not
in
real
nine.
E
So
a
little,
I
wanted
to
add
a
slide
in
just
sort
of
the
early
warning
system
for
that
coming
and
when
it's
coming
in
in
ocp
and-
and
you
know,
what's
that
so
a
cup
this
I'm
sure
other
people
have
things
that
they
want
to
add
in
or
update
as
well.
So
I
think
that's.
I
think
we
should
just
keep
a
refresh
every
once
in
a
while.
So
it
looks
slightly
different,
at
least.
D
Yeah
and
I
think
that's
as
much
of
a
documentation
issue
as
anything
so
that
people
know
what
they're
getting
and
how
to
change
it.
If
it's
not
what
they
need.
A
Great
there's
there
are
no
new
issues
in
the
repo
that
I
saw
that
aren't
things
that
we've
already
talked
about.
Of
course,
the
low
contrast
for
the
for
the.
A
E
At
brian
innis
you're
on
the
call,
I
think
I
had
brandon
johnson
send
an
email
out
to
you
and
I
and
I
haven't
reviewed
it
yet
with
some
suggestions
for
the.
B
E
Thought
he
sent
it
to
your
gmail
account
so
because,
but
if
he
did,
if
you
didn't
get
it,
he
did
send
something,
and
I
will
dig
it
up.
I
had
him
review
it
and
make
some
suggestions
on
what
we
could
do
to
make
it
more:
a
better,
better
readability
and
more
for
people
with
disabilities
being
able
to
more
accessible
site
as
well.
E
So
he
had
some
good
suggestions,
but
I
I
haven't
dug
it
up
and
I'll
dig
it
up
and
resend
it
if
you
didn't
get
it
because
he
just
had
to
send
it
to
you
and
with
me
cc'd,
and
so
let
me
see
what.
E
First
name
is
brandon
johnson
and
it
might
have
been
from
his
gmail
account.
He
is
a
red
hat
contractor
he
might,
it
could
be
brandon.
I
don't
see
anything.
Let
me
just
go
into
my
inbox
and
see
what
I
have.
B
Forward
me
that
I
just
couldn't
paste
it
into
slack,
we
can
look
at
that.
There
was
one
two
or
three
the
modifications
for
inclusive
language.
E
B
E
A
G
G
And
you
won't
get
spammed.
I've
already
said
it.
E
A
I
got
that
so
in
terms
of
issues
so
you're
dealing
with
the
accessibility
ones,
so
we
can
let
that
go.
The
other
one
was
the
group
charter
legal
input.
So
we
basically
have
the
legal
input
in
terms
of
external
repo
and
social
media
and
that
one
be
closed
out.
E
A
Okay,
I'll
close
that
one
out
well
I'll,
come
back
to
it
and
close
it
out
now.
Actually
I
don't
just
get
rid
of
it
and
close
information
gathered.
A
Okay,
close
with
comment
there
we
go.
Let's
see
here,
missing
security
contacts.
I
got
that
when
I'm
writing
up
my
ask
for
someone
in
the
community
to
do
that
and
code
of
conduct,
that's
in
process.
So
no
other
issues.
B
Okay,
so
I
actually
have
merged
it,
but
I
was
hoping
to
get
some
reviews
on
that.
We
sort
of
had
a
conversation
last
meeting
that
it'd
be
good
if
we
as
a
collective
as
a
group
did
pull
requests
rather
than
me
just
doing
it,
and
so
this
meeting
should
own
the
the
the
content,
and
I
just
felt
that
if
I
was
just
doing
everything
myself,
then
it
it
doesn't
reflect
this
group.
B
So
I
I
left
that
one
hoping
that
somebody
would
comment,
and
nobody
did
so
I
just
closed.
I
just
accepted
it
and
nudged.
It.
B
B
A
Perfect
and-
and
we
should
be
better
about
that
I'll-
make
sure
I
send
reminders
for
folks
to
look
at
these
things-
we'll
add
it
to
the
task
list
and
that
actually
brings
us
to
the
task
list
all
right.
So
what
we
have
is
create
a
list
of
links
to
add
to
the
pr
against
product
documentation
to
add
the
extra
book.
A
E
With
the
latest
release
note
whatever,
then
we
also
have
that
for
2022.
A
For
sure
what
I
would
be
inclined
to
do
is
make
it
part
of
this
group's
process
to
maybe
quarterly
go
through
it
as
a
group,
if
even
asynchronously,
just
to
make
sure
it
has
the
latest
and
greatest,
and
that
way
it
doesn't
have
to
happen
in
in
the
lead
up
to
an
event.
E
E
A
E
Would
be
awesome,
we
are
very
all
of
red
hat
is
as
well
very
event-driven
as
you
see
product
releases
going
out
in
terms
of
when
red
hat
summit
happens
or
kubecon
releases,
so
it
would
be
nice
to
have
it
on
a
quarterly
cadence.
E
Do
you
have
any
thoughts
about
where
that
should
live
in
in
the
in
the
whatever
the
github
repo
is
that
we
create
thegithub.com,
okd,
project
or
okd?
And
on
that
note
I
will
say
I
reached
out
to
the
one
fellow
who
was
following
that
repo,
the
okd
one
turns
out.
He
follows
350
other
repos
as
well,
so
he
just
is
a
follower,
and
nobody
has
responded
to
me
from
that.
E
So
there
is
a
process
at
github
where
I
can
ask
to
take
over
a
site,
and
I
will
I
will
put
that
in
but
yeah.
So
maybe
in
the
new
year,
if
nothing
happens
from
github,
if
they
don't
respond
or
whatever
we'll
just
go
with
the
okd
dash
project
site
and
be
done
with
it,.
A
E
I
think
most,
if
not
most,
of
the
red
hat
sponsored
open
source
projects
are
in
github
and
culturally.
I
think
our
communities
lean
towards
github,
so
not
that
I
have
I
like
both
of
them,
so
it
doesn't
really
matter
to
me,
but
I
think
I'd
rather
stay
in
github,
where
we
have
people
already
connected
to
us
as
opposed
to
disconnect
and
reconnect
and
making
that
ask
of
people.
D
E
Yeah,
I'm
gonna,
I'm
gonna
write
to
github
and
it's
I
I
was
trying
there
was
a
guy
kevin
hook
who
was
he's
hooked
to
300.
As
I
said,
350
github
projects,
I
thought
he
was
the
owner
of
it.
I
was
mistaken,
but
he
did
respond
to
me
so
kudos
out.
There.
A
Speaking
of
which
we'll
close
out
with
one
thing
did
we
want
to
say
anything
about
log
4j
like
it
doesn't
really
impact
us
directly,
because
the
only
thing
in
openshift
that
was
impacted
was
the
logging
operator,
which
we
don't
have
so
that
I
know
of
there's
nothing
that
directly
affects
that.
It
directly
affects
okd
the
vulnerability,
but
does
anyone
have
any
a
different
sense
that
that's
that
there
is
something
we
should
be
looking
at
and
should
we
say
something
like
we
are
not
aware
of?
A
E
I
I'd
rather
not
since
it
doesn't
impact
us
and
we
are
not
supporting
the
logging
operator
personally.
If,
because,
if
we
do,
then
it's
gonna
distract,
I
think
from
the
openshift
messaging
around
that
or
the
red
hat
messaging
and
I
haven't
even
looked
to
see
what's
what's
out
there
yeah,
but
it
might
distract
people.
Okay,
that's
all
I
mean.
D
Yeah
as
well
as
you,
if
you
say
like
I
looked
at
that
one
and
and
it
would
say
okay
noted,
but
if
you
say
that
it
doesn't
affect
us,
then
you're
really.
F
A
Yeah
all
right:
well
then,
that
brings
us
down
to
the
end
of
the
meeting
any
last
comments
or
questions
before
we
sign
off.
E
I'm
just
looking
forward
to
2022
guys
and
getting
you
know
working
more
with
michael
and
getting
the
the
extra
book
in
there
with
the
guides
updated,
and
it's
going.
I
think,
we're
going
to
rock
it
next
year.
A
Work,
that's
right:
yep,
we're
gonna!
We're
gonna,
wait
that
extra
week
to
give
folks
a
chance
to
settle
in
and
whatnot
so.