►
From YouTube: OKD Working Group Meeting 06-06-2023
Description
The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group includes the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group produces supporting materials and best practices for end-users and provides guidance and coordination for CNCF projects working within the SIG's scope.
https://okd.io
A
B
All
right
anything,
the
folks
see
that
they
want
to
add,
remove
around
we're
good,
all
right.
Let's
go
ahead
and
get
started,
then
so
okd
releasing
cicd
updates
with
Christian
Sheree
and
Vadim
Luigi
Alex
Etc.
C
Yes,
so
we
just
some
feedback
on
our
okd
pipelines.
We
have
the
operate
first,
servers
that
have
gone
down
and
we
on
in
transition
on
getting
the
pipelines
running
on
the
Moc,
the
Massachusetts,
open,
Cloud
platform
and
that's
game
the
they
are
basically
been
serviced
this
week,
so
we
won't
be
able
to
do
a
release
for
okd
for
the
Sprint,
so
we
were
planning
to
do
it
for
Thursday
Friday
and
doing
a
release.
C
We
are,
however,
looking
at
with
with
one
of
our
staff.
Engineers
is
looking
at
trying
to
stand
up
a
hypershift
cluster
for
us
that
we
could
use,
maybe
for
the
next.
This
Jeremy,
so
Jeremy
could
maybe
give
us
some
feedback
on
that
that
we
can.
Basically,
if
that
gets
it
sort
of
gets
commissioned,
then
we
can
run
our
release
and
it's
cost
payload
Pipelines.
C
Well,
we
were,
we
were
informed
that
the
operate
first
infrastructure
is
going
to
be
decommissioned
and
yeah,
yeah
and
I
think
it
has
to
do
with
the
whole
restructuring
of
of
what
was
happening
internally
in
red
hat
and
they
were
moving
resources
away.
But
we
were
under
the
impression
that
that
keep
the
services
running
but
have
no
admin
or
anyone
looking
at
any
problems
on
that
server.
But
it
looks
like
in
this
week,
I
think
maybe
with
the
Moc
upgrade
as
well
they've
taken
their
service
down.
C
So
we're
not
sure
if
they're
going
to
come
back
up,
we're
not
sure
of
how
that's
going
to
look.
But
it
was
a
Pity
because
we're
in
a
really
good
Cadence,
the
s-cos.
We
had
nightly
bills
working
all
of
them
working
every
night
and
then
the
cleanup
jobs
and
then
also
every
end
of
Sprint.
So
every
few
weeks
we
could
do
a
release
and
that's
been
going
quite
smooth.
So
it's
a
bit
of
a
it's
a
bit
of
a
bump
but
I'm
sure
we'll
get
over
it.
B
It's
interesting
I'm
not
seeing
anything
on
their
website
about
this.
It
would
be
good
that
they
would
let
folks
know.
Okay,
yeah.
B
The
people
know
I,
guess
right
exactly:
they
don't
have
the
resources
for
that
either.
Jeremy
is
there
anything
that
you
wanted
to
add.
E
Started
looking
at
this
like
an
hour
ago,
so,
okay,
maybe
I'll,
have
it
update
tomorrow.
Hopefully,
okay.
B
All
right,
I
have
a
question
now
in
terms
of
you
know:
Vadim
cutter
release,
Saturday
an
F
cost
release,
and
this
was
plagued
with
the
signature
issue,
and
this
is
like
the
I
think,
second
or
third
time
in
the
past,
like
two
years
or
so
that
this
has
happened,
and
then
people
have
to
do
a
force
upgrade
and
whatnot
do
folks
have
any
thoughts
about
do
we
want
to
publicize
this
and
publicize
the
fix
and
be
prepared
to
publicize
this?
B
Should
it
happen
again
because
it
burned
people
trying
to
go
from
the
earlier
version
of
413
to
the
to
the
6-4
release
of
413
and
people
kept
asking
the
same
question
and
then
the
dean
and
other
folks
had
to
chime
in
and
say
yeah.
This
is
a
known
issue.
B
Is
this
something
we
would
want
to
tweet
out
like
hey,
you
have
to
do
a
force,
it's
going
to
say
that
it's
not
a
valid
update,
but
just
use
the
force
flag
and
let
folks
know
do
we
want
to
do
a
blog
post.
Do
we
want
to
assume
that
it's
such
a
rare
thing
that
we
don't
need
to
do
it
with
some
feedback
from
the
technical
group
and
then
I'll
bring
the
same
question
to
the
community
group
next
week?.
E
Well,
if,
if
it,
if
it
publicizing
it
would
make
the
support
easier,
that
it
makes
sense,
I
mean
that's,
that's
the
route
that,
like
you
know,
the
kubernetes
community
has
adopted
for
the
same
sort
of
problem
when
they
had
signature
issues,
so
I
mean
it
doesn't
need
to
be
front
and
center.
But
you
know
in
the
normal
places
people
would
normally
look
for.
Support
is
where
I
would
put
it.
B
Yeah
for
folks
that
don't
know
what
I'm
talking
about
here's
an
example
from
the
slack
of
someone
asking
a
question,
Vadim
saying
yeah,
this
is
still
applicable
any
other
thoughts.
C
Yeah
I
I'm
I'm
up
for
getting
in
from
any
helpful
information
to
make
things
easier
for
people
and
if
they
see
I'm,
you
know
coming
up
with
this
problem.
Where
do
I
look
and
if
they
have
a
way
FAQ
or
whatever
it
is
or
known
issues,
and
they
can
do
a
quick
search,
get
the
issue
and
fix
it.
I
think
all
the
better.
B
B
It
started
a
couple
of
weeks
ago
with
the
release
a
couple
weeks
ago,
where
I
think
Vadim
signed
it
with
the
wrong
key.
Okay,
new
key
was
generated,
I'll
have
to
look
back
on
it,
but
basically
Vadim
accidentally
signed
it
with
the
wrong
key,
and
so
then
you've
got
an
issue
where
you've
got
two
different
Keys,
basically
floating
around
yeah.
F
Okay,
so
if
we,
if
we
actually
get
this
onto
the
same
process
as
say
like
the
s-cas,
where
the
signing
becomes
an
automated
part
of
a
pipeline,
this
problem
should
largely
go
away.
Okay,
because
I
I
think
the
bigger
issue
is:
how
do
we
try
and
make
sure
it
doesn't
happen
again
if
we've
been
bitten,
two
or
three
times
yeah
I'm
transitioning
to
an
automated
pipeline
suggests
it
will
fix
the
issue.
Okay,
yeah.
B
B
B
F
E
B
And
we
don't
want
folks
to
get
into
the
habit
of
using
Force
really
for
any
reason,
unless
they've
got
an
issue,
yeah
all
right
anything
else
along
the
lines
of
okd
release
and
cicd
stuff.
C
No
I
don't
know
Shireen
Alex
have
you
got
any
other.
D
Hey
folks,
all
right,
so
I
don't
really
have
much
today,
I,
don't
think
we
have
had
any
major
changes
lending
recently
we're
looking
at
the
federosity
nine
changes
in
the
federal
Aquarius
groups
looking
up
at
the
next
version
right
now,
which
is
going
to
happen
something
in
three
months
or
a
little
bit
more
than
that,
and
apart
from
that,
we
are
going
to
have
tomorrow
a
discussion
about
ipsec
support
in
of
course,
so
on
this
link
here
and
if
you
can
join
if
you're
interested
in
joining
the
working
group
discussion,
they
of
course
working
group
description,
we'll
talk
about
that.
D
I,
don't
know
the
support
exactly
ain't,
no
key
D,
but
there
should
be
ip6
support
for
put
to
Port
communication
already.
So
that's
more
about
having
ip6
support
4
clusters
for
communication
between
the
Clusters
and
say
like
another
Network.
D
And
yeah,
that's
about
it!
For
me:
oh
yeah,
sorry
I
forgot.
On
the
on
the
escort
side,
we've
been
working
on
splitting
the
openshift
specific
bits
from
the
more
system,
classic
system
bits,
and
so
this
work
is
moving
along.
We
haven't
completed
it,
but
it's
in
progress.
A
B
Timothy
is
there
a
place
where
we
could
look
to
get
more
info
about
how
this
is
how
these
are
getting
separated
and
broken
out
is.
Is
there
some
some
place
you
could
link
us
to?
That
would
help
us
sort
of
get
a
sense
of
it.
B
You
anything
else
on
s-cos
or
West
Coast.
Anyone
any
questions,
feedback.
B
All
right,
moving
on
now
to
Community
Development
updates
with
Brian.
F
Okay,
so
last
meeting
we
had
our
sort
of
walk
through
the
board
planning
board.
The
link
is
in
the
on
the
hack,
MD
and
gender
I
guess.
F
An
overall
comment
is
there's
still
quite
a
lot
of
documentation.
Work
to
do,
there's
also
a
sort
of
request
and,
if
someone's
got
time
to
go
and
try
and
work
out
how
the
openshift
documentation
process
works,
because
we
don't
have
any
tooling
for
any
community
members
to
actually
be
able
to
see
previews
and
that's
sort
of
a
quite
an
inhibitor
to
anybody
that
wants
to
actually
contribute
to
the
documentation.
F
It's
not
doesn't
feel
right
doing
a
pull
request.
If
you
don't
know
if
the
content
that
you've
changed
actually
works
or
if
you've
got
some
syntax
errors
there
or
some
formatting
issues
there.
So
from
from
community
members,
we
ideally
need
to
try
and
work
out
what
happens
under
the
covers
at
Red
Hat
to
actually
convert
the
git
repo
into
the
actual
documentation
site.
F
F
So
if
anyone
has
some
spare
time
and
wants
to
go
play
around
with
that
and
try
and
figure
it
out,
ideally
we're
looking
for
maybe
a
containerized
solution
where
someone
can
just
pull
the
container,
put
the
the
changes
through
it
and
get
a
preview
website
and
a
little
bit
like
we've
got
for
the
MK
doc
stuff
for
the
community
website
and
that
plugs
into
a
number
of
areas
where
documentation
needs
to
be
updated.
F
So
until
that
happens,
we're
still
using
the
process
where
we
raise
a
an
issue
and
then
we
have
to
work
with
Michael
Burke
to
actually
get
the
changes
made,
and
it's
just
a
little
bit
clunky,
because
he
has
to
take
screenshots
and
full
reviews.
And
so
that's
that.
F
F
F
So
the
question
was
I.
I
know
that
the
meeting
times
are
a
problem
for
some
people.
So
if
when,
if
we
can't
get
the
red
hat
people
attending,
we
would
need
to
try
and
find
a
different
time
for
the
meeting.
So
I
think
that
is
still
an
open
question.
Is
it
worth
going
ahead
with
the
meeting
next
week
and
will
we
have
sort
of
the
required
people
at
the
meeting?
F
F
So
I
think
that's
that's
for
next
week.
So
we'll
talk
about
that
after
after
this
item
just
check
that
we
can
actually
run
that
other
than
that.
F
E
B
And
one
of
the
things
that
came
out
of
this
is
we
do
have
a
volunteer
to
help
sort
of
be
our
security
issue,
traffic
director
person
to
sort
of
forward
things
to
the
appropriate
place.
If
folks
have
security
issues
that
they
come
across,
which
is
maybe
not
as
important
or
referenced
as
much
now
but
I
think
as
things
move
forward,
it
will
be
nice
to
have
someone
on
the
team
on
the
working
group
who's
knowledgeable
about
okay.
This
is
a
bug
relate.
B
This
is
a
security
issue
related
to
this
bug,
or
this
known
security
issue
on
the
red
hat
side
or
on
the
or
on
the
OSB
side,
or
on
the
side
or
whatever,
and
be
able
to
direct
folks
to
hey
here's,
some
information
about
it.
Here's
where
we
can
submit
if
it's
an
unknown
if
it's
a
new
issue,
that's
not
known
yet
by
others.
Things
like
that,
so
that
was
really
helpful
and
they've.
B
F
F
A
Okay,
okay,
so
we'll
try
to
see
if
there's
anyone
anyone
knowledgeable
about
catalogs
within
red
hat
and
who
can
tag
along.
B
That
would
be
fantastic
because
I
think
ultimately
we
need.
We
need
everyone
to
start
with
a
base
level
of
knowledge
about
how
the
catalogs
work
and
and
the
task
ahead,
and
then
we
can
once
everyone's
at
that
level.
B
F
F
So,
just
as
we
do
and
an
okd
release,
we
need
the
catalog
to
have
that
same
level
of
signature
and
again
the
pipeline
I
think
is
very
important.
We
want
this
to
be
fully
automated.
We
don't
want
any
manual
processes.
It
should
be
all
driven
from
gate
and
fully
automated
to
actually
update
the
catalog
from
from
git
source.
F
So
I
think
the
work
that
Luigi
sharing
you
did
with
the
s-cost
is
going
to
be
very
valuable
because
we
need
a
similar
type
of
pipeline
activity
within
the
operator
catalog,
but
I
as
as
I
think.
The
first
point
is
make
sure
everyone
has
a
base
knowledge
and
we
understand
what
we
what
we
can
do,
what
we
want
to
do
and
put
a
road
map
in
place.
D
C
So
it
was
the
one
we
that
that
I
did
in
the
last
shift
week,
so
it
builds
from
scratch
your
your
operator,
bundles,
do
the
index
and
then
and
then
basically
push
it
into
a
catalog
at
the
end
and
push
that
catalog
to
a
to
a
repo,
sorry,
a
registry.
C
So
it's
it's
very,
very
opinionated.
It's
it's!
It's
based
on
our
simple
operators
that
we
built.
It
needs
a
lot
of
work,
but
it
could
be
a
baseline
to
look
at
going
forward.
Yeah.
B
B
All
right
any
other
thoughts
on
operators
should
we
Shireen
can
you
let
us
know,
maybe
ahead
of
time,
so
that
we
have
like
a
day
or
two
to
decide
if
the
meeting
should
be
on
operators
or
not?
Is
that
is
that
reasonable?
Maybe
let
us
know
Monday
morning.
C
B
Whatever
works
because
it's
it's
been,
you
know
the
operator
thing
has
been
lingering
for
so
long
now
and
we
really
want
to
address
it
and,
if
I
think
we're
starting
to
build
the
momentum
right
and
once
we
have
the
knowledge,
then
we'll
have
even
more
momentum,
because
folks
will
feel
comfortable,
contributing
all
right
anything
else
on
the
community
develop.
A
survey
is
basically
done.
B
There's
three
questions
that
are
getting
added
or
two
two
more
questions
that
are
getting
added
and
then
that's
going
out
this
week
and
I
think
that's
it
for
Community
stuff.
Is
there
anything
else
that
folks
want
to
talk
about
while
we're
on
the
call
together.
B
All
right
well,
thank
you
so
much
for
your
time
and
feel
free
to
reach
out
to
us.
If
any
questions
arise
and
we'll
see
you
in
the
slack
on
The,
Matrix,
Twitter
and
all
the
great
places
where
we
get
together
all
right
see
you.