►
Description
OKD4 Release Update & Road Map with Christian Glombek (Red Hat)
https://okd.io
The OpenShift Commons Gathering was held on Jan 29th, 2020 in London, UK, and featured guest speakers from local customers and users. The OpenShift Commons Gatherings brought together 300+ experts from all over the world to discuss container technologies, best practices for cloud native application developers and the open source software projects that underpin the OpenShift/Kubernetes ecosystem.
https://commons.openshift.org/gatherings/London_2020.html
A
A
It
will
be
the
first
point
then
I'll
quickly
talk
about
F
cause,
Fedora
core
OS
will
have
a
very
short
preview
demo
and
then
I'll
pitch
to
you
that
you
should
try
out
okay
D
for
then
we'll
have
a
quick
look
at
the
road
ahead,
the
road
map
and
also
what
what's
next,
in
okay,
D
and
then
I'll
pitch
the
ok
D
working
group,
which
I'm
sharing
together
with
Diane
and
Danny,
come
Nia.
Who
is
our
community
chair
from
outside
of
Red
Hat,
who
isn't
here,
I?
Think
yeah.
Alright,
let's
get
started.
A
It's
not
an
acronym,
that's
very
important.
It
just
means
that
it's
the
OpenShift
code
base
plus
Fedora
core
OS,
so
we
build
essentially
off
of
the
master
branches,
so
we
run
okay.
What
okay
DeForest
right
now
is
what
OpenShift
4.4
will
be
in
some
at
some
stage.
Essentially
we
build
off
of
the
Masters
yeah
and
plus
Fedora
core
OS
and
there's
a
little
star
there.
It
could
be
any
operating
system
that
is
built
with
the
RPM
OS
tree
and
ignition
technologies
I'll
dive
into
that
in
a
bit
a
little
bit
more
as
well.
A
So
if
you
want
to
check
out
okay
deep
for
go
to
ok,
Dao
and
you'll
land
on
this
page,
yeah
all
right,
so
this
is
a
slide.
I
think
we
had
a
similar
one
in
an
earlier
already.
So
this
is
OCP
the
product
and,
as
you
can
see,
if
I
go
to
the
next
slide,
there's
a
little
difference
there.
We
switch
out
the
operating
system
which,
in
the
product
OCP,
is
this
redhead
core
OS
or
rel
core
OS,
and
here
it
is
Fedora
core
OS.
So
that's
the
main
difference.
A
We
use
the
same
OpenShift
codebase,
but
the
operating
system
is
different.
What's
very
cool
in
in
Cooper
net
in
an
open
shift
is
that
we
update
the
operating
system
through
the
cluster
and
we
just
bind
the
lifecycle
together.
So
the
operating
system
becomes
an
implementation
detail,
so
here
we
switch
out
DRL
core
OS
with
Fedora
core
OS,
so
what's
Fedora
core
OS,
then
the
mission
statement
of
Fedora
core
as
I'll
just
quickly
read
out.
A
A
So
maybe
I'll
just
dive
into
what
what
ignition
rpm
OS
tree
is
a
little
bit
more.
It's
a
you
know,
I'm
technical.
So
if
you
get
part
with
this,
I'll
skip
this
quickly
I'll
to
keep
it
short.
So
ignition
is
our
declarative.
First
boot
configuration
system,
so
we
have
a
declarative,
config,
the
ignition
configs
specification
and
on
first
on
the
very
first
boot
after
provisioning
it'll
set
up
the
system
as
needed
like
in
what
cloud
am
I
running?
A
Rpm
OS
tree,
on
the
other
hand,
is
the
base
for
our
immutability,
the
some
of
it.
We
compose
images
out
of
RPM
packages
and
have
an
immutable
semi
immutable
system,
where
only
only
you
can
only
write
on
parts
of
of
the
file
system
or
the
rest
is
totally
mutable
and
then
an
update
will
happen
by
downloading
a
new
OS
tree
commit
laying
that
onto
disk
and
booting
into
that
commit
and
on
traditional
Fedora
or
well
on
Fedora
core
OS.
You
can
actually
roll
back.
We
don't
support
that
in
the
cluster
use
case.
A
The
rollback
would
would
be
an
update
to
the
older
version
sort
of
updating
to
the
older
comment
again.
So
there's
only
yeah,
there's
no
going
back
in
that
graph,
so
yeah
right
at
what's
the
difference
with
right
at
core
OS
again
red
head
core
OS
is
a
component
and
implementation
detail
of
open
shift.
It
updates
alongside
openshift,
there's
only
one
life
cycle.
You
don't
really
notice
anything
about
the
update,
that's
out
to
the
operating
system
and
as
opposed
to
Fedora,
chorus,
erratic
or
OS
is
based
on
the
relative
set.
A
So,
let's
quickly
switch
to
the
preview
demo,
so
we're
in
preview
stage
right
now,
it's
like
an
alpha.
Maybe
almost
beta
and
I,
have
a
cluster
spun
up
here.
So,
as
you
can
see,
we
have
different
branding
it's
okay,
D,
instead
of
instead
of
the
openshift
one.
So
the
main
difference
is.
Let
me
quickly
dive
into
the
node
details
just
to
show
you
we're
running
on
the
OS
image,
Fedora
core
OS,
which
just
got
add.
So
it's
a
little
bit
small
wavy.
A
A
One
important
difference
is
that
you'll
notice,
as
a
customer
trying
this
out
I
on
the
operator
hub
you'll,
have
access
to
the
community
operators.
You
don't
have
access
to
the
to
the
Red
Hat
operators,
but
most
all
of
them
have
their
upstream
operators,
which
you
can
which
you
can
install
through
the
operator
hub.
So
on
the
operator
hub,
you
will
find
all
the
all
the
community
operators.
A
Now
it
is
possible
so
go
to
ok
di
o,
go
to
the
download
section
and
download
it.
We
have
a
release
page
where
you
can
find
all
the
CI
builds
of
ok
D
and
try
any
of
them
out,
preferably
a
green
one.
Otherwise
you
might
not
be
able
to
to
test
anything
and
then
give
feedback.
We
have
two
repositories
actually
one
for
the
technical
feedback,
which
is
this
one
github.com
slash,
OpenShift,
slash,
ok
d.
So
if
you
find
anything
any
bug
on
open
ship
on
ok
d,
we
will
file
it
there.
A
The
yeah
let's
get
to
the
road
ahead,
so
we
created
a
an
oak
ID
for
road
map
together
with
the
community
with
you,
ok,
d,
working
group
that
formed
about
half
a
year
ago,
and
we
had
some
general
guidelines
in
there.
That
is,
we
will
use
ignition
v3
right
now.
Ocp
still
runs
with
ignition
spec
v2
will
use
ignition
spec
v3
because
just
to
get
will
get
with
the
with
the
product
soon.
But
we
want
to
get
that
early
testing
again
and
then
we'll
have
someone
one
OS.
A
So
there's
a
few
general
guidelines
and
then
we
had
the
phase
zero,
which
was
get
the
first
alpha
out
and
we've
done
that
so
we're
in
phase
one
right
now,
which
is
sort
of
more
of
a
stabilizing
face.
It's
still
pretty
much
internal.
You
can't
really
participate
and
contribute
a
lot,
but
once
we
go,
GA
it'll
will
be
in
phase
2
and
then
we'll
also
revisit
this
roadmap
and
in
phase
2.
A
We
want
to
really
focus
on
community
collaboration
and
technology
incubation,
meaning
that
if
you
have
any
ideas
for
features
or
you
find
bugs
early
on
in
the
in
okd,
we
want
to
be
the
interface
to
ratchet
externals
to
make
make
collaboration
actually
possible.
That
was
very
hard
with
okay
t3
point
X,
and
there
was
lots
of
room
for
improvement
there.
So,
with
with
your
new
okd
working
group,
we
really
want
to
make
that
possible.
A
And
that's
this
is
leading
over
to
to
this
part,
the
okay
D
working
group.
We
have
two
repositories:
the
community
repository
which
is
sort
of
for
planning
the
meetings
and
and
everything
organizational,
and
then
we
have
the
okd
repository,
which
is
the
technical
one.
So
this
is
where
you
would
file
bugs
and
we
would
begin
triage
them
and
send
them
off
to
the
right
people
to
fix.
You
can
find
us
on
slack.
There
is
the
open
shift,
deaf
channel
on
the
kubernetes
slack
and
there's
also
where
else
in
the
open
ship
users
channel.
A
So
if
you
have
a
user
oriented
question,
go
to
the
user's
question:
oh,
if
it's
really
a
deaf
question,
we're
in
the
Deaf
Channel
and
then
also
the
openshift
comments
slack,
you
might
be
familiar
with
that
we're
essentially
in
any
channel
there.
I
think.
There's
we're
on
the
general
channel
definitely
understand
okay,
D
for
channel
on
the
open
ship
comments
slack
as
well.
We
also
have
a
mailing
list
in
the
form
of
a
Google
Group.
It's
another
annoying
URL!
You
can
copy
down
now.
A
I,
just
get
the
slides
later
now
join,
join
that
group
and
you'll
be
informed
of
everything.
That's
happening
of
our
meeting
agendas
and
meeting
times
and
you'll
get
the
links
to
the
recordings
of
those
working
group
meetings
as
well,
so
come
by
and
say
hello,
we're
always
open
to
new
interested
members
that
want
to
contribute
and
share
anything
more
yeah.
So
we
have
two
projects:
Kanban
projects
on
github
as
well,
one
in
the
community
repository
which
is
again
for
planning
out
the
meetings
setting
the
agenda.
Diane
manages
that
usually
so.
A
This
is
where
we
plan
out
the
meetings
and
you'll.
You
can
see
the
agendas
up
front
and
you
can
even
well
add
ideas
for
the
agenda
and
then
the
other
one,
which
is
the
the
okd
for
project.
It's.
If
you
go
to
the
open
shift
organization,
it's
the
only
organization
wide
project
there,
and
that
again
is
for
following
the
the
current
status
of
development
of
the
engineering
work
we
do
on
OK
d4
and
with
that
I'm
already
through
I,
think
I
haven't.