►
From YouTube: OKD Community Update Vadim Rutkovsky & Christian Glombek Red Hat OKD Working Group OSCG 2022 Spain
Description
OKD Community Update
Speakers: Vadim Rutkovsky & Christian Glombek Red Hat OKD Working Group
OpenShift Commons Gathering Kubecon EU
May 17, 2022 Live from Kubecon EU in Valencia, Spain
Full Agenda here: https://commons.openshift.org/gatherings/OpenShift_Commons_Gathering_at_Kubecon_Europe_2022.html
Learn more at: https://commons.openshift.org
A
Hi,
I'm
christian
glombeck,
I'm
a
senior
software
engineer
at
red
hat.
I
work
in
the
openshift
arc
been
on
a
couple
of
teams
there
currently
on
the
specialist
platform
team
that
works
on
integrating
new
platforms
or
adding
support
for
new
platforms
and
providers,
and
previously
I
was
on
the
machine,
config
operator
team
and
the
core
team
and
I've
also
been
co-leading.
The
the
okd
working
group
for
some
time.
B
And
my
name
is
vadim
rutkowski.
I
work
for
edge
for
red
hat
in
the
edge
group,
and
today
we
joined
forces
to
speak
about
our
community
distribution,
which
is
called
ocd,
we'll
start
with
doing
an
overview
on
what
okd4
is
then
we'll
move
on
to
more
detailed
features
in
its
current
state
of
the
union.
B
As
you
can
see,
the
openshift
okay
is
effectively
openshift,
with
a
slight
difference
of
branding
other
than
that.
The
goal
is
to
provide
all
the
features
that
oocp
has
with
an
option
for
the
community
to
participate
and
make
decisions
where
the
distribution
is
going
more
into
details
of
the
current
state,
we're
mostly
focusing
on
rolling
release
model
where
we
have
one
single
stream
for
consumers
to
use
it.
We're
currently
at
release
4.10.
B
B
Okay,
also
sits
in
between
operator
hub
upstream
and
fedora
communities.
So
since
we
use
fedora
os,
we
also
get
all
the
new
features
coming
in
fedora
and
you
can
also
make
use
of
all
the
features
coming
in
operator
hub
and
participating
in
those
communities
using
opt
as
a
starting
platform.
B
Another
goal
of
the
ocd
is
to
get
new
technologies
enabled,
preferably
by
default.
For
instance,
okd
was
the
first
distribution
to
use
ignition
version
three.
First
and
now
we
are
defaulting
to
c
groups,
v2
enabled
by
default
before
ocp.
Does
that-
and
there
are
smaller
examples
similar
to
that
and
with
that
I'll
pass
it
to
christian.
A
We
we
collaborate
with
quite
a
few
communities
and
have
a
few
users
that
make
use
of
okd
one
prime
example
you
heard
of
today
already
is
microshift,
which
right
now,
as
it's
not
a
product,
yet
uses
okd
pieces
to
to
get
built
and
that's
an
interesting
project
and
yeah
one
of
the
things
we've
kind
of
started
up
where
started
within
okd
and
are
now
going
to
be
productized
and
obviously
that's
very
exciting,
to
get
to
the
edge
and
enable
small
scale
deployments,
and
maybe,
in
the
future,
things
like
a
b
availability,
highly
available,
a
b
deployments.
A
A
It
would
be
rel
core
os,
and
with
this
you
can
actually
use
a
docker
file
to
to
install
more
things
into
your
image
and
create
the
image
beforehand
and
then
use
it
later
on
as
the
machine
os
content
image
that
is
used
as
the
that
the
machine
config
operator
uses
writes
to
disk
as
as
the
operating
system,
so
that
there's
going
to
be
a
lot
of
interesting
things
going
to
happen
happening
with
with
coreos
layering,
because
that'll
just
enable
us
to
to
have
a
much
easier
development
flow
in
comparison
to
what
we
have
today
with
the
current
machine,
os
encapsulation,
where
the
machine
os
image.
A
Is
you
probably
know
this?
You
might
not.
We
ship
the
the
os
as
a
container
image
as
a
oci
container
image,
and
then
we
have
the
machine
config
operator
that
extracts
that
os
tree
the
directory
structure
and
writes
it
to
disks,
and
we
reboot
into
the
new
version.
A
With
this
it's
going
to
be
very
similar,
but
the
container
that
ships
the
operating
system
is
actually
usable
as
it
just
like
any
other
container
right
now
we
have
a
special
encapsulation,
where
you
can't
just
use
the
the
machine
os
container
as
a
normal
like
a
normal
container
with
coreos
layering.
You
can
actually
use
that
os
tree
image,
just
as
you
would
would
use
any
other
container.
A
So
you
can
you
can
either
boot
it
or
you
can
run
it
as
a
container
which
is
pretty
cool,
and
then
you
also
just
heard
about
the
operate
first
cloud,
so
we're
going
to
collaborate
with
them.
We're
going
to
try
to
spin
up
a
few
okd
clusters,
so
you
can
also
use
them.
I
just
want
to
really
plug
this
operate
first.
If
you
want
to
gain
experience
or
get
to
know
openshift
in
general
or
okd,
please
do
try
it
it's
great
yeah
and
then
we
have
actually
two
sub
working
groups
in
okd.
A
One
is
mentioned
here:
it's
the
docs
working
group,
which
has
been
very
active
and
has
been
doing
great
work
on
on
our
docs
website.
We
actually
built
the
docs
from
the
same
sources
as
the
the
ocp,
the
openshift
product
docs,
but
obviously
there's
a
few
slight
changes.
We
need
to
make
to
to
refer
to
fedora
and
and
the
okd
pieces
instead
of
the
rel
pieces.
A
We
have
a
second
sub
working
group,
which
is
the
virtualization
subgroup,
which
kind
of
came
from
the
overt
community,
and
we
want
to
provide
essentially
a
way
with
that.
What
the
that
sub
working
group
wants
to
provide
a
way
to
migrate
over
workloads
into
into
openshift
into
okd,
and
that
is
built
on
cube
vert.
A
A
A
I
also
want
to
plug
the
fedora
core
os
working
group.
If
you're
interested
more
in
kind
of
core
operating
system
work,
we
have
a
liaison
from
from
the
coreos
group
in
the
ocd
working
group,
just
as
we
have
a
liaison
from
the
machine
config
operator
in
the
okd
working
group
and
fedora,
or
the
fedora
coreos
working
group
has
their
own
meetings
weekly
on
irc
there's
also
the
fedora
coreos
tracker.
A
So
if
you
hit
any
issues
with
your
base
operating
system
or
afterburn
any
of
the
tools
that
are
part
of
the
base
operating
system,
then
that's
the
right
tracker
to
file
things
or
just
to
track
development
of
of
fedora
core
os
yeah.
There's
a
discussion
forum
on
the
fedora
forums,
there's
the
mailing
list
as
well
and
again
the
calendar
for
for
the
meetings
and
with
that
we're
already
through.
If
we
do
have
some
time
for
questions,
we
will
take
questions
if
there
are
any
other
ways.
Thank
you
very
much
for
listening
to
us.
C
A
Those
we're
going
to
be
bridging
that,
because
yeah,
the
fedora
community
is
mostly
active
on
on
the
matrix,
which
is
bridged
with
irc
the
liberal.chat
irc.
And
so
we
want
to
really
bring
together
both
the
fedora
and
the
openshift
communities.
And
so
we
will
set
up
a
bridge
for
the
matrix
and
the
slack
channel
as
soon
as
we
figure
out
how
to
do
that.
Cool.