►
From YouTube: OCB: OKD Community Office Hours
Description
OKD Community Led Open Forum led by Jaime Magiera (UMICH) co-chair OKD-Working Group
Guest Speakers:
Charro Gruver (Red Hat) - Code Ready Container for OKD 4.7
Diane Mueller (Red Hat) - How to hack the docs.okd.io
A
A
A
A
A
A
A
Well,
hello,
everybody
and
welcome
to
this
community
okay
working
group
office
hour,
we're
going
to
use
the
hour
that
we
normally
use
for
openshift
commons
and
we're
going
to
bring
together
some
of
the
members
of
the
openshift
of
the
okd
working
group
and
we're
going
to
give
you
a
really
short
intro
and
then
some
demos
of
the
crc
and
answer
all
of
your
questions.
And
to
do
this.
I'd
like
to
introduce
from
the
university
of
michigan
amy
magria.
A
A
All
right
and
I'm
also
going
to
hit
the
start
recording
button,
so
I
forgot
to
hit
that
so
here
we
go,
recording
has
started
and
don't
worry
because
we
keep
a
raw
file
of
it
too.
So
no
worries
well
hello,
everybody
and
I'm
the
director
of
community
development
at
red
hat
and
a
long
co-chair
of
the
okd
working
group
and
been
working
on
openshift
and
origin
since
the
early
days
like
seven
years
ago,
so
we're
eight
years
ago
now
so
yeah
happy
to
be
here.
C
Greetings:
everyone
charo
groover,
formerly
an
openshift
origin
user
and
an
ocp
customer
now
red
hat
employee
almost
a
year
now
still
trying
to
stay
as
active
as
I
can,
with
the
okd
working
group,
but
hashtag
day.
Job
takes
away
from
that,
but
I,
whenever
I
can,
I
contribute
with
a
lot
of
things
I
do
in
my
home
lab.
C
D
Hey
y'all
name's
neil
gampa,
I'm
from
datto,
and
I'm
here
primarily
working
kind
of
to
help
bridge
the
gap
between
the
fedora
community
and
and
the
openshift
okd
community,
as
well,
as
you
know,
trying
to
help
make
okd
and
openshift
the
best
that
it
can
be
as
a
kubernetes
platform.
So
I
use
okd
actually
personally
and
professionally
at
my
workplace.
D
B
B
So
let's
get
started
with
an
overview
of
okd4
for
I'll
walk
you
through
a
little
bit
of
this.
So
okd
is
a
community
distribution
of
kubernetes
and
basically
it.
This
means
that
it's
a
community
developed
and
supported
distribution,
and
so
when
you
ask
a
question,
you're
asking
a
question
of
the
community
for
support.
There's
people
contributing
various
components
to
it
and
even
doing
their
own
builds
of
okd
to
add
functionality
that
they'd
like
and
it
has
the
open
shifts.
B
B
So
it's
an
automated
installation
patching
and
updating
from
the
operating
system
up
so
from
fedora
core
os,
all
the
way
up
to
the
applications
and
services,
and
so
you've
got
a
red
hat
and
community
operators
will
be
talking
about
operators
in
a
little
bit.
You've
got
the
platform
of
kubernetes
itself
and
the
cluster
management.
B
You
can
get
it
to
work
in
a
lot
of
environments,
so
you
know
the
the
usual
suspects
right,
so
overt
openstack,
vmware,
vsphere,
aws
azure,
google
cloud
platform,
basically
across
the
spectrum
from
you,
know,
cloud
all
the
way
to
bare
metal
there's
options
for
you
to
use
this
in
in
a
variety
of
ways.
Actually,
so
what
is
the
state
of
okd?
For
and
right
now,
we
are
currently
at
a
stable
release
in
4.7
and
there
are
new
maintenance
releases
on
a
regular
basis.
B
We
actually
have
a
quicker
pace
than
ocp
and
there's
community
contributions
getting
added
all
the
time
and
we
have
a
link
actually
to
the
repo
and
also
documentation
for
getting
the
latest
set
releases
and
also
the
nightly.
So
you
can
get
access
to
the
nightlys
to
test
things
moving
forward
and
there's
collaboration
with
operator
hub
and
the
fedora
communities.
We'll
be
talking
more
about
that
in
a
little
bit
and
there
are
operators
for
okd,
specifically
and
stuff
coming
from
these
other
sources
that
make
for
a
really
nice
environment.
B
If
we
have
time
I'll
I'll,
actually
show
you
that
there's
a
hundred
and
last
I
checked,
it
was
146
operators
that
are
available
for
install
in
okd
just
by
default,
and
it
enables
early
adoption
of
some
upcoming
technologies
and
we'll
touch
on
that
a
little
bit.
So
that's
today
and
tomorrow,
what's
happening
with
okd
and
there's
4.8
is
up
there
for
testing
as
well.
B
So
if
you're
looking
to
get
a
sense
of
what's
happening
with
4.8,
that's
also
available
as
well
there's
a
channel
with
the
releases
for
that
to
test,
and
I
want
to
talk
a
little
bit
about
operators
and
operator
hub.
So
for
folks
that
don't
know
operators
are
a
method
of
packaging
deploying
and
managing
kubernetes
applications
in
the
open,
openshift
okd
world.
B
You
can
even
write
them
in
bash
script
and
they
simplify
the
process
of
deploying
applications
and
maintaining
all
of
the
associated
resources
and
there's
an
operator
sdk,
that's
available
that
allows
you
to
on
various
os's,
create
operators
of
your
own
and
there's
documentation,
examples
for
ansible
for
go
and
they
allow
you
to
get
up
quickly,
creating
your
own
operators
they're
quite
easy
to
deploy
also
too
in
okd
cluster
and
so
the
cluster
version
operator.
Well,
let
me
back
up
a
little
bit
so
in
essence,
when
ocp
and
okd
or
x.
B
So
when
we
started
down
that
path,
essentially
everything
from
the
the
top
applications
down
to
the
cluster
management
became
operators.
So
you've
got
the
cluster
version
operator,
which
actually
is
maintaining
the
version
of
okd
that
is
installed
and
also
the
various
components.
Right
then,
you've
got
the
cubase
api
server
controller
manager,
scheduler
ncd.
These
are
all
operators
underneath
as
well
and
for
networking.
Well,
you've
also
got
network
operators
ensuring
that
your
plugins
are
installed.
B
Your
cni
plugins
are
installed
your
sdn
is
properly
configured
and
it
it
switching
to
operators
really
just
radically
changed
the
the
ecosystem
that
is
openshift
and
okd,
and
there's
an
image
registry
operator
that
keeps
your
local
image
registry.
There's
a
built-in
image
registry
in
okd
keeps
that
functioning
correctly
and
sets
it
up
with
a
few
little
button,
presses
and
and
some
application
of
some
yaml.
If
you
so
choose
and
there's
also
monitoring
for
your
metrics
and
ingress.
B
Your
ingress
router
ensures
that
your
ingress
operator
ensures
that
your
routes
are
are
properly
set
up
and
functioning
and,
of
course,
storage
ensures
that
your
plugins
are
installed
and
that
the
storage
classes
exist
and
there's
you
know
if
you
do
an
install
on
aws,
you're,
automatically
connected
to
registry
and
storage
in
ebs,
and
likewise,
if
you're
doing
vsphere,
you
can
connect
to
that
storage
as
well,
and
there's
also
some
plug-ins
for
csi
plug-ins,
for
example,
using
sifs.
It's
very
easy
to
apply
the
the
sips
plug-in.
B
That's
available,
open
source
plug-in
to
do
sift,
storage
on
okd,
so
again,
operators
all
the
way
down,
and
it's
very
easy
to
monitor
that
way.
You
just
look
at
what's
happening
with
the
mod
with
the
operators
read
their
logs
and
you
can
see
what's
happening
in
your
cluster
and
operator.
Hub
is
a
community
source
index
of
opera
of
these
optional
operators.
B
You
know,
there's
a
list
there
of
them.
You
know
argo
cd,
very
popular
kubrt,
etc.
These
are
really
cool.
Now,
if
we
get
a
chance
I'll
show
you
in
a
little
bit
how
okd
connects
to
operator
hub
and
provides
these
for
you
and
there's
an
underlying
system.
The
operator
lifecycle
manager,
the
olm
that
takes
care
of
the
scope
right,
because
you
can
have
operators
that
are
cluster
wide
or
only
in
a
namespace
and
making
sure
that
these
can
be
updated
manually.
B
If
you
so
choose-
and
this
is
something
where
you
know,
if
you
have,
you-
can
update
operators
independently
of
updating
the
cluster
itself
right.
So
these
third-party
operators
can
be
updated
on
their
own
and
that
can
be
managed
very
easily
and,
as
I
mentioned,
the
operator
hovers
integrated
into
the
console.
B
In
that
integration
essentially
fedora
core
os
is
the
underlying
operating
system,
and
when
you
do
an
okd
install
the
core
os
operating
system,
bits
and
pieces
are
downloaded
using
os
tree
technology,
and
these
this
is
rpm.
So
it's
rpmo
street.
It's
basically
like
git
for
your
operating
system
and
you're
pulling
down
a
version.
The
installer
pulls
down
a
version.
Then
it
adds
some
specific
components
for
kubernetes
and
okd
and
then
deploys
that
to
the
nodes.
B
B
There's
multiple
members
of
the
fedora
core
os
working
group
who
attend
the
okd
working
groups
and
vice
versa,
and
so
there's
always
communication
going
back
and
forth
about
how
to
work
together
how
to
how
to
make
changes
that
might
not
overly
complicate
things
for
the
other
group
and
whatnot.
It's
it's.
I
think
it's
a
good
example
of
how
working
groups
can
work
together
to
solve
issues
and
to
move
technology
forward,
and
we
both
groups
are
open
for
people
to
join
and
become
part
of
that
collaboration.
B
Sorry,
this
hasn't
been
updated.
They
are
no
longer
on
free
node.
They
are
now
using
the
new
project
that
was
started
from
the
folks
that
broke
off
from
freenode,
and
I
will
update
that
slide.
I
apologize
that
that's
incorrect,
but
it's.
If
you
go
to
the
website,
it
is
updated
there
and
there's
an
issue
tracker
for
actual
fedora
core
os
issues.
There's
a
discussion
forum
and
there's
also
a
documentation
repo,
that's
not
mentioned
on
here.
B
They
work
on
their
documentation
as
well.
The
fedora
crossworking
group
there's
a
mailing
list
and
weekly
meetings
that
are
three
of
the
meetings
each
month
are
irc
based
and
then
the
first
meeting
of
the
month
generally
is
a
video
meeting
so
that
people
can
see
each
other
face
to
face
and
interact
more
directly,
and
let
me
actually
well
I'm
on
fedora
core
os
neil.
Do
you
want
to
chip
in
a
little
bit
about
the
general
relationship
between
fedora
and
okd
yeah.
D
Sure
so
you
know
with
a
big
complex
technology
like
openshift,
which
you
know
okd
is
the
community
distribution
of
you
have
a
lot
of
moving
parts.
You
know
across
the
stack
you've
got
things
like
security
features
for
filters
and
control
groups
and
supporting
volumes
and
data
access.
You
have
new
container
technologies
around
orchestration.
D
You
have
service
management
interfaces,
you
have
provisioning
interfaces,
you've
got
all
these
other
things,
and
the
goal
of
okd
is
to
be
a
self-healing,
reliable
platform
to
run
and
develop
applications
and
services
on,
and
the
only
way
we
can
continue
to
make
this
better
is
to
be
able
to
consume
the
latest
and
greatest
technologies
and
incorporate
them
into
the
openshift
technology
base.
That
is
kubernetes,
that
is
the
operators
and
all
that
stuff.
D
So,
fundamentally,
the
idea
of
using
fedora
as
our
base
for
okd
aligns
with
our
ability
to
take
advantage
of
these
new
technologies
that
come
in
through
the
innovation
pipeline.
That
is
the
fedora
project.
You
know,
as
with
red
hat
openshift
container
platform,
red
hat
enterprise.
Linux
is
what
underpins
that
for
okd.
D
B
B
So,
let's
now
move
on
here's
a
list
of
the
resources.
By
the
way,
again,
you
can
go
to
okd.io
and
there's
the
repositories
there,
the
various
ones
and
if
you
just
go
to
okd.io,
you
can
find
links
to
all
of
those
and
let's
do
demo
time
for
code
ready
containers
on
okd.
So
here's
the
resources
for
code,
ray
containers
on
okd
and
charo.
Take
it
away.
C
D
A
Right
and
while
he's
he's
blathering
on
about
his
carcass
and
showing
off
all
of
his
carcass
stuff,
I
will
mention
that
if
you
ask
a
question
or
if
you
submit
an
issue,
we
now
have
actual
swag
for
okd
okd
t-shirt.
So
I
encourage
you
highly
to
get
your
okd
t-shirt,
submit
an
issue,
make
a
pull
request
and
we
will
be
able
to
send
you
off
a
a
t-shirt
as
a
thank
you
gift.
C
C
Once
resolved,
you
will
be
able
to
see
them.
We
will
we'll
post
this
link
in
the
chat
and
it's
also
in
the
slides.
So
so
you
guys
will
be
able
to
see
them,
but
where
the
fedora
project
graciously
gave
us
some
disk
space
to
hold
these.
So
when
you
go
to
this
pub
alt
ot
okd
dash
crc,
slash
release,
folder
you'll,
see
folders
for
the
linux
64-bit
mac,
os
64-bit
and
windows
downloads
for
crc.
C
So
the
installation
is
pretty
simple.
You
download
the
executable.
Add
it
to
your
path
and
the
first
thing
you're
going
to
do
is
you're
going
to
run
a
crc
setup.
Now
I've
pre-run
this
because
it
will
take
a
few
minutes.
It
has
to
unpack
what
is
effectively
a
binary
disk
image
of
a
okd
installation
as
a
single
node
cluster
that
has
been
packaged
up
so
that
it
can
run
on
the
hypervisor
of
your
desktop
operating
system,
be
it
linux,
mac,
os
or
windows.
C
C
This
will
also
take
a
couple
of
minutes,
depending
on
the
horsepower
of
your
particular
workstation,
because
it
is
going
to
fire
up
the
open
shift
cluster,
which
means
all
of
the
operators
that
jamie
talked
about
that
are
part
of
the
the
open
shift
install.
They
are
all
going
to
go
through
their
bootstrapping
and
their
validation
processes.
C
So
you
can
see
from
the
from
the
logs
on
my
terminal
output
here
that
you
know
it.
It
gives
you
updates,
as
this
is
progressing
of
of
what
all
of
the
operators
doing
and
then,
when
it's
completed,
you
will
see
some
output
text
here.
That
tells
you
how
to
access
your
now
running
cluster,
so
one
of
the
quickest
ways
to
get
to
it
is
via
a
browser.
C
If
you
run
a
crc
console
this
from
a
terminal,
it
will
pop
open
your
default
browser
and
bring
you
to
the
login.
For
your
now
running
single
node
cluster,
on
your
desktop,
it
will
default
to
logging
you
in
as
the
developer
account.
This
is
configured
to
actually
create
two
accounts
in
this
cluster.
The
default
cube
admin,
which
is
your
administrative
account,
and
it
gives
you
a
randomly
created
password
here
for
your
cube
admin
account,
and
then
you
have
a
developer
account
that
is
developer
developer,
so
extremely
secure
on
the
what
per
se.
C
If
I
log
in
as
developer
developer,
it
will
bring
me
to
the
developer
perspective,
which
starts
with
a
tour.
So
the
first
time
you
log
in
you
can
click
through
the
getting
started
tour
and
it
will
take
you
through
the
various
components
of
the
console
and
how
to
access.
What
you'll
also
have
this
nice
little
disclaimer
up
here
at
the
top,
reminding
you
not
to
use
any
containers
for
anything
in
production.
C
C
Now,
with
a
few
exceptions
of
some
operators
that
have
been
disabled
like
some
of
the
monitoring
and
things
like
that,
this
is
a
a
fully
functioning
cluster,
so
you
can
add
additional
operators
to
it
by
going
to
the
operator
hub
and
selecting
whatever
you
want
to
install.
So
if
say,
you
want
to
try
out
eclipse
che,
there's
an
operator
for
that.
C
If
you,
for
example,
want
to
some
work
with
kafka,
you
can
install
the
strimzy
operator
now
with
all
of
this,
you
need
to
bear
in
mind
that
you
are
running
this
ecosystem
on
your
local
workstation,
and
so
you
are
limited
by
the
resources
available
on
your
local
workstation
can
tune
those
things.
If
you
follow
our
link
to
the
documentation
on
how
to
use
crc,
you
can
configure
the
memory.
You
can
configure
other
things
about
the
virtual
machine
that
underlies
this.
C
So
if
you've
got
a
big
fat
macbook
pro
with
64
giga
ram,
you
can
crank
up
the
memory
available
to
this
cluster
and
do
a
whole
lot
more
with
it.
All
right,
but
that's
basically
a
quick
tour
of
this
little
guy
here.
The
next
thing
I
want
to
show
you
is
is
where
all
of
this
comes
from,
so
in
github,
under
github.com
code
dash
ready,
that's
where
the
source
code
for
code
ready
containers
is
so
if
you
are
so
inclined
and
want
to
build
this
thing
yourself.
C
There
are
a
couple
of
projects
in
here
that
you're
going
to
care
about.
First
one
is
snc,
which
does
what
the
acronym
stands
for.
It
builds
a
limited
single
node
cluster,
and
so,
if
all
you
want
to
do
is
get
a
single
node
cluster
up
and
running,
that
only
has
local
access
to
whatever
station
you're
building
it
on.
You
can
actually
use
this
to
build
and
and
run
a
cluster.
C
If
you
want
to
package
it
up
as
a
crc
bundle.
That's
where
you
switch
to
the
second
project
after
you've
built
the
snc
then
build
the
code.
Ready
containers
bundle
from
this
crc
project,
one
of
these
days
I'll
actually
get
around
to
posting
a
little
blog
entry
about
how
to
do.
How
I
do
this
for
okd,
because
we
don't
yet
have
the
cicd
mechanics
built
in
for
automating
the
build
of
code
ready
containers.
C
So
if
you're
looking
at
the
crc
bundle
that
you
downloaded
from
from
the
site
where
we're
hosting
it
and
it's
a
couple
of
releases
out
of
date,
that's
my
fault,
because
I
haven't
built
and
released
a
new
one.
Yet
one
of
these
days,
we'll
we'll
get
the
time
and
the
community
effort
underway
to
to
get
this
automated
with
ci
cd.
C
I
would
still
encourage
you
to
do
that
because
there's
a
ton
of
free
stuff,
tutorials
and
labs
and
documentation
and
things
that
are
available
with
a
with
a
red
hat,
developer
registration,
but
we're
community
members
too,
and
we're
also
very
sensitive
with
our
privacy
and
our
own
data.
So
we
fully
understand
not
wanting
to
have
to
register
with
a
site
to
use
a
piece
of,
and
thus
we
support
code
ready
containers
for
pd
and
I
could
go
on
all
day
and
talk
about
home
labs
and
single
node
clusters
and
things
like
that.
A
Pause,
let's
see
if
there's
any
questions
out
there.
I
don't
know
chris
and
bobby
who
are
producers
if
there's
any
out
in
twitch
and
youtube
who
are
doing
it,
but
I'm
not
seeing
any
in
the
chat
right
now.
So
I'm
going
to
and
here's
one
now
and
jose.
Thank
you
for
that.
So
jose
is
asking.
Are
there
any
plans
to
add
support
for
arm
architecture.
C
C
I'm
it's
running
under
an
emulation,
though
so
it's
still
an
x86
64
runtime
that
that's
running
on
the
virtual
machine.
I
haven't
yet
had
an
opportunity
to
test
our
okd
crc
on
arm.
My
wife
does
have
an
m1
macbook
pro,
but
she
hasn't.
Let
me
borrow
it
yet
to
subject
it
to
code,
ready
containers
so
by
that
or
I
might
sneak
around
and
see
if
I
can
buy
my
own
one-based
macbook
pro.
C
C
The
the
first
goal
is
to
support
like
data
center
sized
arm
64..
So
you
know
we're
talking
the
big
metal
that
that
you
can
rent
from
aws
or
google,
or
that
you
can
buy
and
deploy
in
your
own
data
center.
That
will
be
running
the
the
arm.
64
architecture,
support
for
things
like
the
the
you
know,
the
new
eight
gigabyte
raspberry
pi
fours.
C
C
B
Yeah
so
actually
vadim
chimed
in
remotely
on
this
and
and
in
essence,
christian
gombek
is
one
of
the
people
working
on
arm
64
in
general,
and
once
it's
working
for
ocp
okd
will
follow
and
it's
looking
like,
hopefully
in
4.9
or
4.10,
no
promises
on
a
pi
4
though,
but
in
general
arm64
coming
in
future
releases.
Again,
the
four
nine
or
four
ten.
A
A
So
one
of
the,
if
you
go
to
docs.okd.io,
I
don't
know
charo.
If
you
want
to
just
pop
over
there
for
a
minute,
there
are
some
decent.
I
will
say
docs
for
okd
that
we
are
currently
working
on
and
you
know,
there's
stuff
for
pretty
much
every
version
and
the
latest
version
is
there,
but
especially
if
you're
a
newbie
to
okd
and
you
are
trying
to
use
the
okd
for
documentation.
A
A
There
you
go,
there
is
a
third
you
just
slide
down
until
you
get
one,
that's
and
looks
there.
So
probably
the
easiest
way
to
to
get
involved
and
in
any
open
source
project
is
to
use
the
docs
and
comment
on
the
docs,
and
here
there's
lots
of
things.
We're
not
perfect.
We
generate
our
our
docs
off
of
the
ocp,
the
openshift
docs
and
so
there's
always
usually
a.
B
A
Reference
to
rel
core
os
as
opposed
to
fedora
core
os,
or
perhaps
our
language,
isn't
as
inclusive
as
it
should
be,
but
there's
lots
of
easy
fixes,
as
well
as
grammar
fixes,
and
if
you
want
to
log
an
issue
in
here.
This
would
be
great
if
you
could
pick
one
and
and
just
show
us
that
we'll
we'll
show
our
appreciation
for
your
finding
it
and
if
even
better,
if
you
can
suggest
the
fix,
we'll
be
happy
to
take
those
as
well.
A
B
Absolutely
and
another
thing
worth
showing
is
charo
if
you
go
go
back
to
the
main
okd.io
real,
quick
and,
let's
show
folks
the
guides,
because
this
is
a
great
thing.
It's
so
there's
the
official
documentation
for
the
install
and
if
you
click
on
the
very
last
hyper,
second
or
third
to
last
hyperlink
guides
there.
B
There
is
a
repo
that
contains
guides
for
installation
for
primarily
what's
called
upi,
so
user
provisioned
infrastructure.
On
all
of
these
platforms,
aws
azure
gcp,
home
lab.
I
wrote
one
that's
in
there
for
vsphere,
and
basically
this
is
instead
of
using
sort
of
the
automated
functionality
of
the
installer.
You
can
use
the
upi
well
that
one's
for
ipi,
yep
there's
a
good
example
there
and
then
there's
also
for
upi,
which
is
your
user
user
provision.
B
And
one
thing
that
comes
out
of
this
is
that
when
you
see
folks
doing
stuff
repeatedly
that
maybe
the
installer
doesn't
provide
for
or
if
you're
doing,
upi
there's
been
a
couple
of
instances
of
folks
coming
up
with
scripts
to
automate
or
terraform,
or
you
know
any
of
your
other
deployment
control
mechanisms
to
simplify
tasks
that
we
see
that
folks
are
doing
over
and
over.
So
it's
it's
a
great
way
to
contribute
to
the
project
as
well
and
do
we
have
any
other
questions
coming
in.
A
B
Yeah,
it
is
the
default,
so
yeah
I
mean.
Essentially
you
have
three
masters
and
three
workers
are
the
default
for
the
ipi
installation
on
any
of
the
platforms,
except
for
doing
sort
of
the
single
node
approach,
so
yeah,
three
masters
and
three
workers,
there's
a
matter
of
fact:
there's
a
switch,
that's
flipped
in
the
installation
configuration
by
default.
That
makes
it
so
that
your
masters
do
not
do
do
not
handle
any
workloads
and
keep
that
separation.
A
B
That
actually
highlights
the
the
really
great
thing
about
okd
is
that
you
can
use
it
in
production
in
a
highly
available
resilient
fashion.
And
then
you
can
also
do
something
small,
with
a
single
node
to
do
development
and
whatnot.
And
it's
it's
very
flexible,
including
all
of
the
tools
that
come
with
it
or
many
of
the
tools
that
come
with
it
by
default,
which
is
really
great.
D
Maybe
you
have
your
master,
your
control,
plane,
kubernetes
term,
meaning
the
masters
that
actually
like
orchestrate
the
setup
have
that
maybe
that
runs
on
a
vps,
a
digital
ocean,
or
you
want
to
run
it
on
on
a
machine
that
you
have
at
home
or
whatever,
and
then
you
could
have
your
a
worker,
you
could
have
workers
in
aws
or
azure
or
gcp
or
on
on
machines
remote
somewhere
else
like
you.
Can
you
know
with
your
home
lab
stuff?
D
D
Is
you
know,
because
user
provision
infrastructure,
which
is
what
upi
stands
for,
is
kind
of
whatever
you
want
it
to
be?
It
is
probably
one
of
the
least
fleshed
out
aspects
of
openshift
deployments
and
okd
deployments
and
using
you
if
you
come
up
with
something
cool-
and
you
know,
you've
you've
come
up
to
some
stumbling
blocks,
so
you
need
you've.
D
A
I
know
this,
this
is
I
I
have
to
say
this
is
the
first
time
we've
had
t-shirts
for
okd.
So
that's
why
we're
flagging
slogging
them
so
much
here,
we're
really
thrilled
that
that
we
actually
have
something
to
give
away.
Besides
our
thank
yous,
and
so
that's
we're
really
thrilled
that
to
get
this
support
and
the
work
that
mike
mccune
and
the
team
have
done
on
these
deployment
configurations
is
amazing.
A
The
biggest
issue
I
think
we
have
is
testing.
You
know
on
upi
on
all
of
this
stuff,
I
mean
we
have
a
regular
cadence
of
releases
that
go
out
and
each
release.
Basically,
we
need
testing
and
if
you
have
some
esoteric
edge
case
deployment
on
some
cloud,
that's
you
know
or
not
so
esoteric,
maybe
it's
alibaba
or
digitalocean,
or
something
like
that,
but
like
testing,
to
make
sure
that
the
fedora
core
os
images
are
available
to
make
sure
that
once
you've
got
you
that
those.
A
There's
so
many
moving
pieces
to
open
source
projects
in
general,
but
this
one
especially
because
it
is
a
collaboration
between
the
fedora
coreos
community
and
the
okd
and
openshift
communities
that
we
really
are
looking
for
people
to
help
us
grow
the
folks
who
have
access
to
these
different
deployment
target
platforms
and
maybe
commit
on
a
regular
basis
to
do
this.
Also,
some
work
could
be
done
on
testing
pipelines
so
that
you
know
we
if
you
could
build
scripts
to
test
so
that
other
people
could
do
them.
A
There's
there's
always
something
else.
If
you're
interested
in
contributing
here
and
that's
you
know,
we've
got
a
great
core
of
folks
that
have
been
working.
You
know,
since
the
early
days
of
origin,
but
especially
since
the
4.0
release
of
okd
came
out,
we've
had
a
pretty
vibrant
community
and
very
active,
but
you
know
we
are
active
normally
in
the
spaces
that
we
are
currently
deploying
to.
A
So
I
am
seeing
someone
screen
they're
popping
up
there,
you
go
just,
but
it
that's
that
the
key
is
if
you
have
platform,
whether
it's
arm
or
alibaba,
or
you
know,
zed
cloud
wherever
that
is,
if
you
want
it
tested
on
that,
and
you
have
access
to
that
and
that's
always
on
a
reoccurring
basis.
Please
reach
out
to
us.
C
C
C
D
Let
me
add
some
color
here
because,
like
I
I've
I've
had
to
make,
I
have
had
this
thought
process
for
my
own.
You
know
personal.
Like
me,
super
personal,
like
I
want
to
you,
know
fuss
around
with
with
kubernetes
and
not
break
the
bank
and
break
my
time
doing
it.
So
the
way
I
I
tend
to
make
this
decision
tree
go
is
if
I'm
learning
about
the
kubernetes
platform.
D
That
kind
of
stuff
wanting
to
really
deep
into
the
guts
okd
on
aws
is
a
fantastic
way
to
do
it
like,
because
then
you
get
access
to
all
the
things
you
get
the
opportunity
to
really
dig
into
the
meat
and
potatoes
of
what
makes
a
stellar
kubernetes
platform
for
container
development,
orchestration
software
delivery,
application
delivery,
and
I'm
not
saying
you
can't,
run
okd
and
do
your
production
workloads
on
that.
I
am
not
saying
that
that
is
totally
fine,
totally
workable
and
totally
a
thing.
D
It
makes
it
magic
and
the
nice-
and
the
nice
thing
is
that
the
pricing
for
those
like
so
you
know,
charo
mentioned
the
subscription
thing.
Rosa
is
pay
per
use,
and
so
that
means
that
you
can
budget
it
based
on
how
much
you're
going
to
use
it,
and
so
that
makes
that
that's
where
I
would
put
the
decision
tree
in
sorry
jamie
now
you
can
say.
B
B
Basically,
and
you
use
a
tool
called
rosa
to
create
worker
nodes
and
interact
with
the
control
plane.
There's
also
a
a
provided
openshift
service
on
aws
and
then
there's
running
okd
in
aws,
doing
an
ipi
or
upi
install.
So
actually
my
day,
job
involves
doing
okd
in
aws
and
we
are
going
that
route
currently
because
of
the
ability,
as
neil
said,
to
have
control
over
the
control
plane
and
to
be
able
to
get
into
the
tofu
and
potatoes
of
this
process
and
be
able
to
control
those
nuance
things
and
integrate
different
components.
B
B
If
you
wanna
pay
for
the
service
of
rosa,
you
can,
but
I
think
you
miss
out
on
some
of
the
nuance
and
some
of
the
controls
basically,
and
it
should
be
pointed
out
that
rosa
just
became
an
official
service
just
in
the
past
couple
months,
there's
also
some
they
they
don't
actually
have
like
gov
ramp
for
rosa,
yet
they're,
not
on
the
gov
ramp
list
and
things
like
that.
That's
not
coming
to
next
year.
C
C
C
You
know,
as
opposed
to
the
community
support
of
the
okd,
like
with,
with
any
of
the
major
open
shift
app
or
not
openshift
open
source
applications
that
are
out
there.
It
comes
down
to
you
know.
How
confident
are
you
being
self-supported
and
community
supported
versus
having
you
know
a
lifeline
on
the
other
side
that.
D
And
to
kind
of
add
a
little
bit
to
what
charles
said
another
advantage
of
doing
the
okd
style
for
an
aws
deployment
is
you
can
actually
make
different
choices
so
that
so
like?
For
example,
let's
say
you,
I'm
gonna
go
a
little
deep
here
and
let's
say
you
want
to
do
psyllium
for
your
networking.
Right.
Psyllium
is
not
included
in
any
red
hat
open
shift
product
to
the
last
last
I
checked,
but
psyllium
is
interesting.
It
uses
ebpf.
D
It's
super
fancy
on
the
filtering
networking
stuff,
actually
fairly
cool,
and
you
cross
my
fingers
someday.
It
will
actually
show
up
in
ocp,
but
I
want
to
use
psyllium
now
in
okd
you
have
the
opportunity
to
to
use
psyllium
instead
of
something
else
like
whatever
is
in
there
by
default.
I
think
it's
open
shift,
sdn
or
open
v
switch
right,
orovian
or
whatever
I
forget.
What
it
is
but
like
helium
is
interesting.
D
I
want
to
use
psyllium,
but
I
like
everything
else
around
okd
and
I
want
to
use
okd
with
psyllium,
and
so
I
can
do
that.
So
that's
where
I
feel
okd
tends
to
be
a
much
more
of
an
interesting
value
proposition
where
you
can.
You
have
the
opportunity
to
be
a
lot
more
flexible
with
how
your
deployment
is
actually
going
to
look,
whereas
with
ocp
you
lose
a
little
bit
of
flexibility
normally
because
you're
you're
operating
on
red
hat,
open
shift
and
then
rosa
even
less
flexibility
because
they're
managing
it.