►
From YouTube: OKD Working Group Meeting 08-01-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
A
B
Yeah
sure
so
we
are
working
on
part
of
the
pipeline
to
to
actually
Implement
some
layering
for
s-cos.
B
It's
a
initiative
that
have
initiated
there
are
problems
because
of
the
layering
uses,
a
pot
that
needs
High
privileges,
and
so
we
have
capability
issues
but
we're
busy
working
on
within
okd.
Looking
at
using
the
security
context,
constraints
and
a
special
service
account
to
get
around
it,
but
other
than
that,
I
think
the
pipeline's
still
working
well
now
that
we
will
be
able
to
do
a
release
for
the
end
of
Sprint,
which
is
in
two
weeks
time
for
both
4
14
and
413.,
and
that's
it
from
my
side.
A
All
right,
let's
move
on
to
fcos
updates
and
we
don't
have
anybody
here
from
the
F
cost
team.
So
let's
skip
that
item
and
moving
now
to
s-cos
updates.
Do
we
have
anything.
A
It
doesn't
look
like
we
have
anybody
here
for
that.
That
can
really
speak
to
that
Community
Development
updates,
Brian.
C
Okay,
so
we
had
a
community
meeting
last
week.
Primarily
we
talk
about
two
things.
The
first
was
the
video
series
where
we
just
went
through
the
plans,
so
that
is
item
number
38
on
the
planning
board.
C
So
we
went
through
the
plans
we
added
layering
as
a
topic.
So
just
talk
about
the
the
core,
OS
layering
feature
that
come
in
and
we
use
that
within
okd
or
we.
So
we
just
needed
to
cover
that
and
we
also
got
asked
to
review.
So
if
you
go
and
look
at
number
38
in
the
planning
board,
there
is
a
a
machine
config
operator
video.
So
we
got
asked
to
go
and
review
that
and
comment
on
that.
C
So
if
anybody
wants
to
learn
about
the
machine
config
operator,
there
is
a
a
video
there,
our
post,
the
link
to
the
planning
board
item
in
chat
and
we'll
also
put
it
in
the
agenda.
So
anyone
catching
up
can
go
and
find
that,
but
it's
just
within
our
GitHub,
the
OCD
project,
GitHub
and
then
the
planning
board
and
you
can
find
number
38
.
so
that
that
is
really
the
video
series.
So
that
is
trying
to
help
people
understand
and
how
to
self-support
okd,
installs
and
config
and
setup.
C
C
We
didn't
really
come
up
with
a
plan
there,
but
I
think
it
is
a
to-do
item,
but
in
the
future
we
need
to
look
at
the
resources
for
people
that
want
to
want
to
use
the
cluster
for
work
rather
than
actually
installing
setup
and
debug
the
the
configuration
of
the
platform,
which
is
where
the
current
series
is
and
focusing,
and
then
the
second
thing
that
we
covered
in
the
meeting
was
the
work
going
on
on
operators.
C
So
we
we
did
look
at.
We
did
discuss
some
of
the
challenges
that
we
encounter,
primarily
because
a
lot
of
the
information
on
what
is
released
is
within
the
prow
system.
So
we
don't
have
access
to
all
the
the
exact
git
commits
for
the
actual
bundles
that
are
installed
by
The
Operators
and
The.
Operators
themselves
and
Luigi
did
did
sort
of
confirm
that
most
of
the
operators
do
have
branches
that
are
good
configurations
for
each
release.
So,
for
example,
a
413
we
should
find
within
an
operator
of
413
Brands.
C
We
will
build
the
operator
for
a
413
platform.
Similarly,
a
414
Branch
with
a
414
platform,
so
I'm,
currently
looking
at
at
some
some
test
operators
just
to
see
how
we
can
go
with
that,
so
that
work
is
slowly
progressing
and
just
trying
to
come
up
with
and
once
I
have
an
end-to-end
sort
of
path
that
I
can
do
manually.
We
can
then
start
looking
at
building
the
the
pipeline.
C
There
is
a
there
is
a
sort
of
an
embryonic
pipeline
already
created,
which
is
in
our
repo
that
we
can
actually
base
work
on,
but
it
doesn't
cover
things
like
if
we
have
to
build
the
underlying
base,
bundles
and
and
and
and
and
go
through
the
end
to
end
from
the
from
the
actual
application
into
operator
into
the
the
catalog.
C
So
that's
that
and
then
the
last
thing
that
we
talked
about
is
on
the
agenda,
which
is
us
on
a
break
so
I'll
leave
that
until
the
agenda
I
think
that's
everything
that
we
covered
in
sort
of
brief,
probably
just
worth
saying
that
if
you're,
if
you're,
not
in
those
meetings,
you're
welcome
to
join
us.
But
there
is
a
second
hack,
MD
sort
of
thread
where
we
cover
the
community
meetings.
C
So
it's
probably
worth
just
putting
that.
If
people
don't
know.
A
The
only
thing
I
would
add
to
that
is
for
any
folks
that
have
any
spare
Cycles
at
all.
It's
always
helpful
to
have
another
pair
of
eyes
and
hands
for
the
discussions
and
issues,
sections
and
okd
proj
project
okd.
So
that's
where
you
know
people
put
in
issues
which
very
often
actually
get
converted
to
discussions,
because
a
lot
of
time
they're
not
actually
issues
they're
reward.
A
You
know
discussion
items
so
they'll
get
converted
a
lot
of
times,
but
anytime
we
can
get
someone.
You
know
contributing
some.
Some
help
to
help
folks
in
the
community
get
their
okd
installations
up
and
running
is
helpful.
So
if
you
ever
have
a
few
Cycles,
please
feel
free
to
pop
in
and
and
provide
some
support.
I
go
through.
Their
Vadim
spends
a
fair
amount
of
time
in
there
and
a
couple
of
other
folks,
and
if
we
could
get
a
couple
more
folks,
contributing
and.
A
C
One
more
thing
about
there
is
I
noticed,
there's
some
quite
good
information
captured
in
some
of
those
discussions,
so
I
think
one
activity
that
we
need
to
do
is
go
and
harvest
them
as
either
blog
posts
or
documentation
updates,
because
there's
some
quite
useful
content
being
put
into
some
of
those
discussions
and
it
gets
lost
in
the
fog
of
stuff
yeah.
A
So
yeah
and
I'd
be
happy
to
start
doing
that
it
would
be.
You
know
we
could
actually
sort
of
create,
but
what
we
could
do
is
add
a
tag
to
the
item
like
documentation
because
there's
a
documentation
label
actually
so
label
it
as
that
and
I.
Don't
I
think
we
didn't
in
this
meeting
talk
about
the
blog
post,
yet
so
here's
the
blog
post.
A
This
was
we
talked
about
it
last
week,
but
so
that's
a
blog
post
that
was
written
by
Jacob
Meng.
That's
basically
an
overview
of
the
CI
CD
of
those
of
okd
and
it's
a
really
nice
reading
and
definitely
helpful
to
let
folks
know
in
a
sort
of
an
encapsulated
fashion
where
we
are
in
terms
of
CI
CD
of
building
the
actual
okd
payloads
foreign.
A
A
So
August
22nd
and
29th,
we
decided
to
take
as
break
days
to
give
folks
a
chance
to
sort
of
regroup
and
and
get
a
breather,
and
a
lot
of
folks
are
going
to
be
on
vacation
at
that
time.
So
we
won't
have
the
development
meeting
on
the
8th
or
we
will
have
the
development
meeting,
the
Community
Development
meeting
on
the
8th
and
then
we'll
have
one
more
working
group
meeting
and
then
we'll
be
off
those.
B
Yeah
I,
just
I
just
wanted
to
mention
I
think
we
did
a
while
ago.
I
mentioned
that
Alex
and
myself
we
built
a
sample
operator
I'll
paste
the
I'll
paste,
the
link
in
in
the
chat
and,
if
anyone's
interested,
it's
basically
it's
from
zero
to
building
it.
B
A
very
simple
sample
operator
that
I
think
if
I
remember
just
monitors
a
config
map
and
then
it
helps
you
to
build
from
scratch
build.
We
have
a
very
opinionated
mag
file
in
there
it'll
help
you
make
make
the
binary
build
the
bundle,
and
then
you
can
use
that.
Together
with
the
pipeline,
we
created
to
actually
Build
Your
Everything,
plus
the
bundle
to
the
catalog
and
your
artifact
that
it
there
will
be
a
catalog.
C
B
Have
a
look
at
it
play
around
clone
it
break
it
changes
whatever
you
know,
I
think
it
might
help
for
those
who
want
to
start
playing
around
with
operators
and
and
getting
especially
with
the
operator,
the
building
of
the
operators
and
all
that
type
of
thing
we
we
did
test
it
using
our
Pipeline
and
I
mean
we
haven't
tested
the
the
catalog
in
a
cluster
yet,
but
that
still
has
to
be
verified,
but
go
ahead,
look
around
and
see
if
that
of
any
help.
B
If
anyone
wants
to
play
around
with
you
more
than
welcome
and
then
just
one
other
thing,
our
director,
our
pillar,
director
of
engineering,
is
really
key
to
find
out
who
is
using
okd
I
mean
obviously
not
it
I,
wouldn't
call
it
a
production
environment,
but
maybe
a
a
sort
of
serious
environment.
Where
I
mean
we
know
soon,
the
CERN
guys
are
using
it,
but
is
there
anyone
else?
B
That's
using
it
regularly
within
the
you
know,
within
their
environments
and
I,
think
the
target
outcome
for
for
our
directors
that
she
wants
to
maybe
partner
with
the
company
and
and
work
on,
getting
and
finding
the
pain
points
of
okd
and
and
maybe
I
think
the
biggest
you
see.
The
biggest
problem
is
the
Telemetry
and
you
know
we
can't
get
telemetry
because,
obviously
you
know
it
is
a
sensitive
issue,
but
I
think
it's
more
of
finding
out.
B
How
could
we
make
and
improve
all
the
things
within
okd,
but
working
in
partnership
with
it
with
a
company
and
I?
Think
that's
what
what's
her
sort
of
main
objection
objectives
are.
So
if
there's
anyone
here
that's
interested,
then
please
reach
out
to
me.
I
think
my
emails
in
the
in
the
list
just
ping
me
and
we
could
set
up
a
meeting
and
to
get
it
without
directly
and
see.
You
know
what
next
steps
could
be
taken.
A
Excellent,
that
is
fantastic
operators.
Are
you
know
the
big
issue
that
we
want
to
tackle
and
so
having
a
tangible
example,
I
think
is
really
super
helpful.
You
know
and
Brian's
got
his
work
so
between
the
two
of
them
we
I
think
we've
got
our
Basics
covered
on
understanding
and
also
the
meeting
from
I
should
link
that
we
should
actually.
A
A
All
right,
well,
thanks,
so
much
folks.
This
was
a
quick
meeting
and,
as
Brian
mentioned
yeah
anyone
that
wants
to,
if
you're
not
already
joining
the
Community
Development
meetings
feel
free
to
show
up
at
those
those
are
more
sort
of
following
the
project
cards
and
you
know
working
on
things
to
increase
the
the
usage
of
okd
and
the
community
engagement.
So
all
right
talk
to
y'all
next
time,
thanks
guys.