►
From YouTube: Lightning Talk: OKD Working Group Update & Road Map Red Hat OpenShift Commons 2022 Detroit
Description
Lightning Talk: OKD Working Group Update & Road Map
Red Hat OpenShift Commons 2022 @ Kubecon/NA
Detroit, Michigan
October 25, 2022
Speakers:
OKD Working Group co-chair:
Jaime Magiera (ICPSR at University of Michigan Institute for Social Research)
with
Michael McCune (Red Hat)
https://okd.io
https://commons.openshift.org/gatherings/kubecon-22-oct-25/
A
A
B
And
so
a
little
bit
about
okd
so
for
folks
that
aren't
familiar
okd
is
the
non-subscription-based
openshift
distribution
and
it's
Community
maintained
and
supported,
meaning
the
documentation,
technical
support
and
a
lot
of
the
same
channels
as
ocp.
It's
built
from
the
same
source
as
ocp
and
Mike.
You
want
to
talk
a
little
bit
about
some
of
the
features
and
whatnot.
A
Well
yeah,
so
it
has
the
same
general
features
as
ocp,
but
as
we
mentioned
here,
it
does
not
have
all
the
same
operators
as
ocp
and
what
we
mean
by
that
are
not
the
core
cluster
operators,
but
more
the
marketplace.
Operators
that
you
might
expect.
If
you
have
an
ocp
subscription,
then
you
might
see
different
operators
than
what
you
would
see
on
ocp.
A
Do
you
want
to
talk
about
the
releases
or
should
I
keep
going,
keep
going
all
right
cool?
So
we
have
new
releases
every
few
weeks
and
we're
going
to
talk
about
a
very
exciting
feature
in
a
minute
here:
the
okd
streams
which
are
going
to
help
us
to
deliver
those
and
like
it's
very
timely,
because
we
had
a
very
exciting
release.
A
Today,
some
of
you
might
have
seen
on
Twitter,
one
of
the
other
big
differences
between
okd
and
ocp
is
that
okd
can
be
installed
on
Fedora,
core
OS
and
Centos
streams,
core
OS,
whereas
ocp
is
installed
on
railcore
OS
and
then.
Lastly,
what
we're
seeing
in
the
community
is
that
ocp
or
okd
is
being
used
in
a
variety
of
contexts
anywhere
from
home,
Labs
people
doing
experimentation
to
production
running
in
research
institutions
like
the
IC
right.
B
Yes,
I
see
it's
funny.
I
laugh
about
this,
because
we
do
this
all
the
time,
so
icpsr
CERN
and
a
lot
of
research
institutions
are
using
okd
and
tailoring
it
to
their
specific
needs.
And
so
what
have
we
been
doing
right
so
lately
in
terms
of
community
updates?
We
now
have
okd
streams,
tecton
build
Pipeline
and
we'll
be
talking
more
specifically
about
that.
B
So
we
actually
have
meetings
that
alternate
between
Technical
and
between
Community
Development,
so
that
we
have
both
aspects
taken
care
of
we've
moved
our
git
repositories
off
of
sort
of
the
the
red
hat
group
and
into
our
own
organization
in
GitHub,
so
that
we're
now
all
of
the
resources
are
Community
managed
and
we
have
access
and
control
access
controls
on
that
and
we
started
a
video
tutorial
series
and
you
can
check
them
out
on
our
blog
and
actually
Mike.
Why
don't
you
actually
talk
about
one
of
the
videos.
A
Yeah,
it
was
made
in
the
series
yeah,
so
yeah,
we
started
a
video
series
and
what
we
want
to
do
is
get
like
engagement
with
the
community
and
share
what
we
know
about
openshift
and
openshift
operational
techniques,
and
things
around
that.
So
myself
and
a
colleague
from
my
team,
his
name
is
Dennis
moisiev.
We
did
a
video
about
how
you
can
get
into
debugging
issues
around
openshift
and
okd.
A
So
what
we
showed
was
we
showed
the
okd
deployment
release
page
and
you
could
see
where,
like
failed
releases
had
come
through
and
we
showed
you
how
to
drill
through
a
failed
release,
how
to
find
the
bugs
that
were
happening
there
and
then,
where
you
would
go
to
fix
those
bugs.
So
if
you
look
on
the
blog,
you
can
see
the
video
about
that
and
what
we're
trying
to
do
is
we're
trying
to
help
educate
the
community
about
like
what
does
it
look
like
when
there's
a
failure
in
our
build
process?
A
And
then
how
do
you
debug
that?
And
how
do
you
understand
kind
of
the
infrastructure
that
we've
created?
You
know
to
run
our
tests
to
run
our
release,
Automation
and
those
kind
of
things.
So,
like
I'm
thinking
about
a
lot
more
of
these
videos,
I
know
other
people
in
the
community
are
as
well.
So
you
know
stay
tuned
because
I
imagine
we'll
have
more
content
that
will
teach
you
about
like
kind
of
the
really
the
the
details
about
running
openshift
around
getting
in
there.
How
do
you
figure
out
these
processes
and
whatnot
so.
A
So
okd
streams
this
was,
like
you
know,
very
timely.
We
just
had
an
amazing
release
today,
it's
kind
of
like
at
the
last
minute
coming
in
here
we
got
a
release
published
it's
on
Twitter,
and
you
can
see
this
link
at
the
bottom.
Here
goes
to
a
Blog
where
we're
talking
all
about
this.
But
what
are
okd
streams?
What
are
we
trying
to
do
here
so
we're
using
some
of
the
latest?
A
You
know
tecton
build
pipeline
technology
that
we're
working
on
so
that
we
can
create
automated
builds
of
the
okd
release
infrastructure,
and
this
is
kind
of
where
we're
starting
with
this
and
right
now
we
have
it
running
on
the
operate
first
cloud
and
operate.
First
is
a
really
cool
initiative.
Where
we're
you
know
kind
of
doing
this
open
operations
and
if
Karsten
Wade
is
around
here,
like
you
know,
search
him
out,
find
him
he's
got
a
lot
to
talk
about
there,
but
it
doesn't
have
to
run
only
in
the
cloud.
A
You
can
also
run
this
locally,
so
if
you
want
to
produce
an
okd
release
of
your
own,
whether
it's
just
the
standard,
Upstream
sources
or
maybe
you
want
to
modify
those
sources,
you
can
use
this
build
pipeline
locally
to
create
your
own
release,
artifacts
for
okd,
and
then
this
is
where
we're
bringing
in
the
Centos
stream
core
OS.
So
this
is
now
we're
building.
On
top
of
that,
and
like
like
many
of
the
other
openshift
deployments,
except
for
the
Rel,
you
know
the
Rel
specific
ones.
This
is
an
RPM
OS
tree
based
distribution.
A
So
it's
an
immutable.
You
know
kind
of
operating
system,
it's
very
similar
to
Fedora
core
OS
and
and
red
hat
core
OS,
but
this
is
the
Centos
version
of
it.
So
I
told
you
about
what
okd
streams
are.
Why
did
we
build
them
and
there's
some
really
big
reasons
here,
especially
as
as
okd
becomes
a
more
full-fledged
Community
project
and
we're
building
more
Community
around
it?
A
We
maintain
the
machine
API
right
now
and
how
many
show
a
hands
who's
familiar
with
machine
API
if
you're
running
openshift.
Anyone
in
here
all
right,
some
hands
coming
up
so
machine
API
is
the
layer
that
interacts
with
the
infrastructure
beneath
openshift.
There's
an
upstream
project
called
cluster
API
in
kubernetes
show
our
hands.
Anyone
here
to
Cluster
API
before
okay,
so
same
hands,
going
up
some
new
hands.
So
what?
A
If
I
as
a
developer,
want
to
replace
machine
API
and
switch
to
Cluster
API,
so
that
now
openshift
can
look
more
like
what's
going
on
in
the
community
around
cluster
API?
That
might
be
difficult
to
do
inside
red
hat,
but
in
the
okd
community.
There's
now
a
space
where
we
can
start
to
do
these
experimentations.
So
a
very
radical
change
to
openshift
could
occur
there
and
with
these
okd
stream
dreams
we
can
use
that
to
test
it
in
the
community.
So
we
have
the
ability
to
experiment
there.
A
We
also
have
Community
ownership
of
the
CI
CD
Pipeline
and
our
build
pipeline.
So
right
now,
if
anyone
in
the
okd
community
wants
to
do
something,
maybe
fix
a
failing,
CI
test
or
modify
how
our
release
build
line
happens.
They
need
to
communicate
with
red
hat
engineers
and
with
red
hat
owned
properties.
In
order
to
make
those
changes
by
moving
the
CI
into
the
community,
we
get
the
ability
to
start
creating
our
own
tests
to
modify
tests
to
bring
changes
back
to
the
Upstream
ocp
to
us,
then
we
can
say:
hey
look.
A
We
found
some
problems
in
these
tests:
here's
how
we
can
contribute
back
and
then.
Lastly,
this
is
a
very
forward-looking
build
pipeline,
so
we're
modernizing
the
process
for
building
okd
we're
using
this
new
tecton
pipeline.
It's
going
to
allow
us
to
not
only
build
these
releases
we're
talking
about,
but
it's
going
to
give
us.
This
ability,
like
I,
was
saying
to
really
vary.
How
we're
building
these
things,
and
now
we
can
use
you
know
techton
artifacts,
that
are
inside
of
of
kubernetes
to
just
build
new
releases
as
we
need
them.
A
So
it's
not
a
complicated
process
of
setting
up
new
infrastructure
and
creating
new
build
processes.
We
just
create
new
tecton
artifacts,
and
now
we
can
have
new
build
pipelines.
So
yeah,
like
I'm,
really
stoked
about
this
check
out
the
blog
post.
There
there's
going
to
be
a
lot
of
exciting
stuff
coming
there.
B
I'll
talk
a
little
bit
about
the
community
survey,
some
of
the
details
of
it
and
the
survey
was
taken.
We
posted
it
about
six
months
ago
or
so
and
have
been
gathering
information,
since
the
most
popular
version
of
okd
is
4.10
by
a
strong
majority.
This
was
really
heartening
to
see
that
so
many
people
were
adopting
the
latest
versions
available
usage
and
this
was
a
multiple
choice.
B
B
So
there's
a
handful
of
operators
in
particular,
which
are
available
on
ocp
that
are
not
available
in
okd,
and
we've
been
working
to
hash
out
those
issues
and
we're
looking
for
Community
involvement
to
hash
out
those
few
issues
that
are
keeping
those
from
running
on
okd
the
biggest
challenges
that
people
shared
with
us
were
related
to
upgrades
and
documentation,
which
of
course
go
hand
in
hand,
installation
upgrades
documentation
and
so
we're.
Taking.
B
All
of
this
feedback
and
trying
to
really
improve
the
way
in
which
the
experience
of
looking
up
documentation
and
the
videos
factor
into
that,
and
also
the
upgrade
process
and
trying
to
to
really
improve
it.
So
that
you
can.
You
can
make
those
jumps
from
minor
version
to
minor
version
without
some
of
the
pain
that
that
has
been
felt
in
the
past.
A
B
Wanna
talk
about
what's
ahead,
yeah
yeah
sure.
So
what
do
we
have
about?
Mr
chair?
We've
got
full
availability
on
the
horizon
of
okd
on
fcos
and
sentos
stream,
core
OS,
more
walkthroughs
and
video
walkthroughs
and
blog
posts
improve
technical
documentation
like
I
talked
about
and
fostering
Community
experiments
with
these
build
pipelines.
The
as
mentioned
these
build
pipelines
are
available.
These
tecton
pipelines
you
can
go
to
them.
Utilize
them
build
upon
them.
B
Experiment,
experiment
with
payloads
as
well
we're
going
to
be
posting
something
about
methods,
we're
going
to
be
getting
a
blog
post
from
a
member
of
CERN
about
how
they
modified
their
payload
for
okd
and
community-run
CI.
So
people
will
be
able
to
to
run
their
own
CI
and
participating
running
in
the
CI
and
we're
getting
our
own
email.
We're
getting
things
configured
in
such
a
way
that
you
can
email
us
for
directly
to
the
co-chairs
of
the
okd
community.
B
We're
also
going
to
have
a
security
email
address
if
security
issue
comes
up
and
folks
will
be
able
to
communicate
with
us,
if
there's
an
issue
in
the
community
that
they
want
us
to
address,
or
anything
like
that.
So
we're
actually
I
think
really
growing
into
being
a
full
open
source,
Community
Based
project
and
we're
defining
a
continuous
process
of
survey
and
feedback,
conducting
a
survey
making
changes
based
on
that
conducting
another
survey,
making
changes
based
on
that
and
our
meetings
are
on
Tuesdays
at
1700
hours.
B
Utc
and
these
alternate
we've
got
the
technical
meetings
which
are
updates
on
releases
updates
from
the
dependent
projects.
We
have
folks
from
the
fcos
community
showing
up
to
talk
about
what's
happening
there
Etc
and
we
have
discussion
of
outstanding
technical
issues.
Then
we
have
the
community
development
meeting,
which
is
updates
on
our
Communications,
the
blog
posts,
the
videos
Etc
and
discussions
on
how
we
can
take
all
of
this
information
and
facilitate
more
Community
involvement.
We.
C
B
There's
a
lot
of
paperwork
involved
with
that
and
a
lot
of
back
and
forth
to
get
fips
certified.
So,
although
we
could
say
yes,
you
can
turn
off
or
turn
on
particular
algorithms
to
in
essence,
be
fips.
Fip
certification
is
going
to
be
a
big
Community
effort,
that's
not
a
no
to
it.
It
just
means
we
need
more
people
on
board
and
we
would
need
to
define
a
regular
process
right
because,
if
you're
going
to
get
fips
certified
one
year,
three
or
four
years
down
the
road,
you
don't
want
to
lose
that
certification.
C
C
The
idea
is
we'll
be
closer
to
Rel
nine
at
core
OS
and
be
able
to
give
the
Rel
team
feedback,
as
well
as
early
warning
signal
for
the
ocp
team,
so
that
we
can
make
sure
that
when
we
do
deliver
the
new
products
on
new
releases
of
Rel
coros
we're
ready
for
it.
So
there
is
on
the
okd
project
page
and
at
okd.io
there's
a
Blog.
We
would
love
it
if
you
would
take
a
look
at
what
is
the
MVP
and
it
is
really
minimal,
viable
product
or
project.
C
Timely,
we
call
that,
just
in
time
for
a
conference
development
which
is
usually
what
happens
at
major
events,
that
we
push
something
out,
but
I
am
again
I'm
I'm,
going
to
say
totally
grateful.
There's
a
lot
of
folks
out
there
that
did
some
great
work
on
the
okd
stream
stuff
I'd
be
Shireen
and
Luigi.
Christian
glombeck
on
the
customer
facing
engineering
teams
really
went
to
bat,
the
folks
from
the
Fedora
core
OS
team
and
the
sentos
stream
team
for
core
OS,
especially
Timothy
ravier.
C
There
were
some
late
nights
put
in
over
the
weekend,
so
take
a
look,
give
them
a
little
bit
of
appreciation
and
if
you
do
get
a
chance,
take
take
it
for
a
test
run
and
give
us
some
feedback,
because
that's
really
what
we're
looking
for,
because
this
will
feedback
right
back
into
that
ocp
project
products
and
all
the
services
we're
doing
really
quickly.
So
it's
it's
really
been
my
pleasure
to
work
with
you
guys.
Thank
you
very
much
and.
A
I
want
to
say
something
to
the
question
that
came
in
from
from
online
too
about
the
fips
right.
I
hope
you
know,
Jamie
and
I
have
showed
everyone
here
and
everyone
online,
this
kind
of
window
of
where
we're
going
with
this
community,
like
we
are
trying
to
build
more
Community
power
in
here,
so
people
can
experiment.
People
can
build
things.
A
So
if
Phipps
is
something
that's
really
important
to
you,
come
help
us
build
it
or
tell
us
how
to
build
it,
or
just
you
know,
give
us
your
thoughts
so
that
we
can
know
how
to
go
to
the
next
step
right.
So
that's,
hopefully
that's
what
we're
building
here,
and
this
is
really
going
to
become
like
an
exciting
Community
just
to
do
more
of
these
kind
of
things.