►
Description
What's New in Operator Framework
Rob Szumski and Diane Mueller (Red Hat)
OpenShift Commons Briefing
June 2020
The Operator Framework is an open source toolkit to manage Kubernetes native applications, called Operators, in an effective, automated, and scalable way.
Speaker(s) – Rob Szumski and Diane Mueller (Red Hat)
A
All
right
everybody
welcome
to
yet
another
open
shift.
Commons
briefing,
and
today
we've
got
Rob,
some
ski
and
some
other
guests
and
we're
gonna
talk
about
what's
going
on
in
the
operator
framework
world,
that's
OLM
and
sdk,
and
lots
of
other
good
bits,
so
Rob
I'm
gonna.
Let
you
introduce
yourself
rocket
or
as
long
as
you
need
and
then
we'll
have
live
Q&A
and
a
conversation
afterwards.
So
take
it
away.
Ralph.
B
All
right
sounds
good
everybody,
I'm,
Rob,
Sam,
ski
I'm,
a
PM
for
open
shifts
and
I've
been
looking
after
the
operator
framework,
since
it
was
announced
as
part
of
core
les
several
years
ago.
Now
so
I'm
here,
to
give
you
guys
an
update
on
some
exciting
news.
What's
going
on
technology
wise
feature
wise
and
when
you
can
expect
certain
things,
so
we'll
jump
right
on
into
it.
B
The
first
big
news
is
I,
think
we've
got
enough
votes
and
I,
don't
think
it's
official
yet,
but
the
operator
framework
is
gonna,
be
joining
the
CN
CF
as
an
incubating
project.
This
includes
both
the
SDK
and
a
lifecycle
manager,
and
so
we're
gonna
break
down
what
each
of
those
are
and
why
they're
important,
but
we're
super
excited
this
kind
of
builds
on
all
the
momentum
and
open
source
work
that
we've
been
doing
being
part
of
the
CN
CF
will
be
hopefully
a
big
win
for
the
project,
get
more
users
more
contributors.
B
You
solidify
this
as
the
framework
for
managing
operators
across
the
coop
ecosystem.
So
we're
super
excited
about
that.
So,
thanks
to
everybody
that
either
commented
were
voted
and
was
involved
in
this
process,
it
was
took
a
little
bit
longer
than
we
thought,
but
that's
always
the
case
with
these
things.
B
So
yeah
we're
excited
about
that,
and
so
that's
that
the
first
big
news,
let's
go
jump
in
really
quick,
but
I
just
always
want
to
start
with
what
is
an
operator
just
in
case
you're,
watching
this
stream,
and
you
don't
you're
not
as
familiar
with
this
and
so
a
core.
Really
an
operator
is
a
piece
of
technology
that
sits
in
the
middle
between
users
and
a
cluster,
and
it
runs
software.
B
For
that
specific
application,
you
build
that
into
a
piece
of
software
that
then
outputs
kubernetes
on
the
other
side
of
it,
so
making
all
the
objects
that
need
to
happen.
Wiring
them
all
up,
generating
secrets,
storing
those
in
in
the
secrets
in
kubernetes,
managing
the
are
back
knowing
how
to
upgrade
certain
parts
of
the
components
in
the
correct
order
using
staple
sets
when
they
need
to
be
storing
staple
data
using
deployments
when
they're,
stateless,
etc,
etc.
B
It's
providing
that
cloud
like
experience,
but
then
interfacing
with
coop,
so
you
get
this
hybrid
cloud
experience
at
the
same
time.
So
that's
a
world
we're
going
after.
So
let's
dig
in
a
little
bit
further,
so
we
see
operators
kind
of
taking
off
across
every
different
kind
of
vertical
you
can
have
in
software,
because
you
want
that
SAS
experience
and
all
of
these
categories
that
you
see
on
the
screen
here
are
just
getting
more
complicated.
As
software,
it
gets
more
complicated.
B
B
We've
got
all
these
big
data
stacks,
where
you're
scaling
out
different
parts
of
the
application
related
to
load
and
how
much
you're,
storing
monitoring
solutions
that
you
need
to
react
as
containers
are
coming
and
going
in
milliseconds,
and
so
but
throughput
there
is
really
high
and
also
that
how
dynamic
the
system
in
is
is
very
high,
and
so
you
need
different
ways
of
running
that
type
of
software
to
you
know,
keep
up
with
kubernetes.
This
is
modern
software.
You
know.
B
Messaging
services
are
super
popular
and
financial
services
and
all
these
different
systems
that
need
to
talk
to
each
other,
and
so
those
become
critical.
Can
you
scale
those?
Can
you
monitor
them?
Do
you
know
what's
going
on?
Are
you
setting
them
up
in
the
most
secure
way?
All
that
really
matters,
and
then
lastly,
I
think
storage
is
a
really
interesting
one,
because
if
you
think
about
it,
we
don't
want
to
be
tied
to
a
single
local
disk
anymore,
but
in
our
coop
clusters
we
actually
have
tons
of
local
disks.
B
As
you
have
a
hundred
nodes,
you've
got
a
hundred
or
more
disks,
so
what
some
of
these
storage
providers
do
is
plus
up
those
disks
into
network
addressable
storage,
but
the
coop
cluster
understands
through
its
PV
and
PVC
mechanisms,
and
so
you
kind
of
run
storage
on
the
cluster
for
the
cluster,
which
is
really
exciting
and
that's
a
whole
distributed
system
to
set
cluster
a
bunch
of
other
technologies
are
used
there
as
well.
So
that's
where
operators
play
I'm,
not
gonna,
throw
up
the
logos
of
any
of
these,
but
every
major
vendor
I.
B
Think
in
all
these
categories
has
an
operator
at
this
point,
so
take
a
look
out
our
place.
We're
discovering
those
is
operator
hubs
I.
Oh,
this
is
a
listing
of
a
bunch
of
open
source
and
community
operators.
Red
Hat
also
certifies
operators,
and
so
you
can
find
those
inside
of
your
openshift
store
as
well,
alongside
all
those
community
offerings
and
Red
Hat
products.
B
So
breaking
down
what
the
operator
framework
is.
It's
really
these
three
main
pieces,
the
operator
SDK
for
building
operators.
So
this
is
a
new
style
of
building
software.
You
know
interacting
with
kubernetes
api
is
and
how
to
best
do
that
as
well
as
hooking
up
a
distributed
system
into
you
know
operational
knowledge
embedded
in
code,
and
so
what
the
SDK
allows
you
to
do
is
start
with
a
bunch
of
scaffolding
for
code,
where
you
just
have
to
bring
the
knowledge
of
your
application.
B
If
you're
a
Postgres
admin,
you
kind
of
know
how
to
administer
Postgres,
so
we're
gonna
help
you
express
that
in
either
go
code,
ansible
code
or
in
a
helm
chart,
and
so
that's
how
we
help
you
build
an
operator,
and
so
we'll
talk
about
some
of
the
new
features
coming
in
these
SDKs,
but
they're
pretty
robust
right
now
and
we've
got
a
ton
of
folks
that
are
really
interesting
things
with
them.
Next
is
the
lifecycle
manager.
B
This
is
the
thing
that
helps
you
once
you
built
this
operator
and
it's
you
know
it's
packaged
up
how
to
get
it
out
to
all
your
customers.
How
do
a
hundred
different
people
go
install
this
on
their
coop
clusters?
How
do
they
manage
it?
How
do
they
make
sure
that
all
the
correct
permissions
and
security
is
set
up
correctly?
The
lifecycle
manager
helps
you
do
this
and
then
I
already
mentioned
operator
hub
I/o
for
discovering
operators
that
have
been
published
by
different
authors
out
there
on
the
internet.
B
So
I
talked
about
the
SDK
and
how
we
have
these
three
different
flavors
of
it,
there's
helm,
ansible
and
go.
There
are
also
other
open
source
frameworks
for
creating
operators
out
of
Java,
some
other
things
like
that.
So
if
you're
interested
in
your
favorite
language,
there's
probably
something
out
there
for
you,
and
somebody
has
already
started
doing
that
you
can
people
have
written
these
and
all
kinds
of
things.
So
a
different
part
of
the
SDK
than
just
dealing
with
writing
code
is
all
the
other
important
stuff
that
comes
along
with
it.
B
So
how
do
I
package
this
up
so
that
I
can
go
run
it
through
a
CI
pipeline?
But
testing
is
really
key
here,
because,
if
you
think
about
it,
this
operator
is
gonna,
be
managing
really
important
and
really
complex
distributed
systems,
and
that's
why
you're
expressing
it
in
code,
but
you
want
to
validate
that
that
code
is
correct,
and
so
we
have
some
tools
that
are
built
into
the
SDK
and
the
operators
are
instrumented
to
help.
You
do
things
like
when
I
kill
an
important
part
of
this.
B
Does
the
operator
resurrect
it
or
if
I
go
mess
with
some
important
configuration
variables
that
I
you
know,
I
need
to
ensure
remain
in
place?
Does
the
operator
go
replace
those
back
to
what
they
should
be
when
I
send
a
bunch
more
requests
into
my
distributed
system?
Does
the
operator
scale
up
the
correct
component?
Accordingly,
those
are
all
things
that
you
know.
B
We
want
to
express
in
testing
pipelines
and
so
that
people
can
really
test
the
code
that
they're
writing
and
then
your
customers
can
all
just
depend
that,
yes,
you
are
orchestrating
my
sequel
and
Kafka
correctly,
so
you
can
check
this
out
there
on
github
under
the
operator
framework
org
and
we've
got
like
I
set
these
three
flavors.
You
see
these
arrows
that
go
from
left
to
right.
That
is
talking
about
what
we
have.
B
We
call
it
maturity
model
and
the
maturity
model
is
just
how
smart
is
this
operator
basically,
and
it
depends
on
each
application
kind
of
where
you
need
to
fall
on
this,
but
installing
and
upgrading
is
kind
of
you
mentioned
on
all
of
them,
and
that's
really
the
bare
minimum
I
need
to
be
able
to
install
whatever
this
application
is
and
then
update
all
the
components
of
whatever
the
application
is
installing.
So
this
is
for
a
traditional
like
scale
out
database.
B
This
might
be
you
know
the
my
sequel
and
post
guess
processes
themselves,
any
authentication
and
rate
limiting
proxies
you
might
have
in
there.
If
you
have
read
replicas,
updating
and
orchestrating
how
those
are
all
connected
together,
all
kind
of
falls
into
that,
and
so
all
of
our
SDKs
help
you
with
that
part
of
your
application
lifecycle.
B
Now
you
see
the
day
two
operations
term
mentioned
for
ansible
and
go
that
refers
to
all
of
the
other
dynamic
reconfiguration
that
you
would
do
for
any
sort
of
application.
So
in
the
database
example,
we
just
talked
about
what,
if
you
started
with
a
single
node
and
you
installed,
and
you
could
upgrade
that
and
that's
awesome.
But
then
your
app
actually
gets
start
getting.
B
B
B
Actually,
a
lot
of
different
needs
here
related
to
running
and
installing
these
operators,
because
you've
got
different
personas
that
are
involved
so
I've
got
that
the
three
kind
of
main
ones
here
at
the
top
I've
got
an
operator
developer,
who
might
be
building
an
operator
either
internal
to
your
organization
or
is
tweaking
something
about
an
operator
and
they
have
very
specific
needs
where
they
need
to.
You
know
they
want
to
test
against
a
live
cluster,
and
so
you've
got
some
things
that
they
can
do
there,
especially
if
you
want
to
register
it
with
a
catalog.
B
You
go
to
a
cluster
admin
who
is
looking
after
the
whole
cluster
themselves.
They're,
probably
not
experts
in
all
the
applications
that
are
running
on
the
cluster,
but
they
do
want
to
ensure
that
if
there
are
certain
sea
bees
in
some
of
the
software
that's
running
on
there,
the
cluster
that
that
stuff
stays
up-to-date
and
you
know
managing
dependencies
between
some
of
the
teams
may
be
at
a
very
high
level.
So
you
need
to
update
all
these
operators
and
get
a
good
sense
of
how
healthy
they
are.
What's
going
into
those
updates.
B
You
know
if
there
is
any
security
content
in
there,
etc,
etc.
So
that's
kind
of
the
purview
of
the
cluster
admin
and
then
the
cluster
user
really
just
wants
to
run
databases
and
messaging
queues
and
storage
services
or
whatever
it
is,
so
they
just
needed
a
mechanism
for
discovering
which
operators
are
installed
on
the
cluster
and
then
interacting
with
them.
B
You
know,
hey
give
me
a
my
sequel
database
and
this
namespace
and
call
it
test
and
then
I
want
a
different
one,
with
a
different
configuration
in
prod
and
give
me
some
graphs,
for
you
know
all
the
monitoring
that
the
operator
sets
up.
You
know
that's
the
purview
of
the
actual
user
there.
So
when
you
dig
into
it
at
the
very
bottom
here
you
see:
there's
bubbles
for
dependency
resolution,
CRD
life
cycle
and
collision
detection.
This
is
where
you
start
to.
B
That's
you
know,
running
Kay
native,
which
is
a
server
list
framework,
for
you
know,
writing
functions
and
having
event-driven
application,
but
that
actually
needs
a
Kafka
queue
for
it
to
consume
its
messages,
and
so
it
might
depend
on
a
Kafka
operator
and
remember
you,
as
a
cluster
user,
don't
want
to
be
an
expert
in
either
one
of
those
things
because
you
just
you
know,
want
to
write
your
event-driven
application.
So
you
install
these
two
operators.
B
They
actually
depend
on
each
other,
and
so
the
cluster
admin
can
help
manage
some
of
those
dependencies
for
you
and
open
ship.
Has
this
dependency
resolution
built
in
based
on
the
lifecycle
manager
and
then
what
these
use
at
the
core
is
the
CR
D,
which
is
a
custom
resource
definition,
and
that
is
the
ability
to
plug
in
to
the
kubernetes
hole
model
for
doing
our
back
and
extensions
to
the
core
and
those
need
to
be
life
cycled.
B
So
they
have
versions
just
like
a
deployment
and
a
staple
set
and
a
pod
have
an
API
group
version
and
kind.
Cr
DS
have
the
same
thing,
and
so
they
need
to
be
upgraded
and
managed,
as
they
might
go
from
alpha
to
beta
to
stable
or
as
new
features
in
kubernetes
come
in
like
some
of
the
new
validation
logic
that
was
just
shipped
where
you
can
say
you
know
this
is
a
field
as
an
integer
and
I
want
you
to
enforce
that
upgrading
into
all
of
those
new
capabilities
as
well,
then.
B
Lastly,
you
don't
want
two
operators
colliding
over
trying
to
manage
the
same
type
of
resource.
So
if
you
know,
if
there
were
two
kafka
operators
out
there,
you
don't
want
them
both
trying
to
operate
on
the
same
Kafka
cluster.
So
there's
some
collision
detection,
that's
built
into
the
lifecycle
manager
and
that's
really
just
to
protect
the
cluster
from
itself.
It
really
kind
of
happens
all
under
the
hood
without
you
really
have
any
to
notice
it.
B
B
We
are
first
introducing
a
new
bundle
format
for
operators
and
this
the
bundle
is
really
all
the
metadata
that
those
two
systems
create
in
order
to
install
and
upgrade
and
manage
operators.
So
this
is
really
on
an
operator
author.
Is
the
person
that's
really
going
to
interact
with
this
and
the
exciting
thing
about
this?
B
Cluster
wide
or
I
only
work
in
a
namespace.
All
that
metadata
about
how
it
works
is
bundled
up
into
a
container
image,
and
then
you
can
just
mirror
that
and
to
whatever
container
registry
you
want
so
open
ship
will
have.
You
know
some
bigger
bundles
of
these
operators.
You
know
that
represent
our
certified
and
our
community
operators,
but
you
can
also
just
build
you
know
your
own
and
distribute
them.
B
So
one
of
our
partners
might
want
to
do
that,
for
example,
and
so
all
you
do,
is
you
pull
this
container
and
you
say
you
register
it
in
the
cluster
and
say
hey.
This
is
a
new
operator
that
I
want
to
use
it's
represented
by
this
container
image,
make
it
available
on
my
cluster,
and
it
goes.
You
can
see
this
new
operator
object
on
the
right
hand.
Side
makes
that
happen.
We're
also
gonna
be
using
this
new
format
on
operator
hub
and
kind
of
build
it
into
all
the
tools.
B
B
The
next
is
new
capabilities
inside
of
our
package
manager,
tool
OPM
to
start
building,
customized
versions
of
all
these.
So,
instead
of
just
you
know
a
one-off
operator,
ships
version
1
and
then
version
2,
you
at
a
big
banker,
insurance
company
or
something
like
that-
might
want
to
curate
your
own
set
of
catalogs.
These
are
the
operators
that
we
have
tested
and
we
know,
are
high
quality
and
work.
Well,
so
I
want
to.
You
know,
allow
folks
to
have
access
to
these.
B
We
have
a
new
tool
called
OPM
that
can
help
you
build
and
push
those
to
a
central
place.
So
you
can
say
instead
of
registering
operators.
One
by
one
here
is
my
entire
private
catalog
of
operators
that
I
want
to
use
in
my
cluster.
This
is
really
important
for
clusters
that
are
in
disconnected
environment,
so
sometimes
government,
agencies
and
financial
services.
B
You
know
things
that
are
running
like
a
stock
exchange
aren't
connected
to
the
internet,
and
so
you
want
to
be
able
to
use
operators
in
that
environment
just
like
any
other,
so
these
catalog
can
be
built.
You
can
mirror
all
of
the
containers
that
are
required
in
to
you
know
that
specialized
environment,
and
then
they
can
use
operators
all
the
same.
So
we're
really
excited
about
that
tools.
B
So
the
cluster
service
version,
the
CSV,
is
typically
the
main
piece
of
metadata
that
we
have
and
that
would
describe
you
know
all
of
the
the
CR
DS
that
this
operator
uses
under
the
hood
and
how
to
install
them
and
the
permissions
and
things
like
that.
But
then
it
was
a
little
bit
detached
from
the
subscription
information,
which
is
how
do
you
upgrade
this
operator?
Does
it
happen
automatically,
or
does
it
happen
manually
and
then
some
other
things
about
how
that
actually
gets
installed
on
the
cluster?
B
We're
gonna
go
unify
that
all
into
a
new
operator
concept,
so
this
is
gonna,
be
really
exciting,
because
you
know,
then
you
would
just
say
OC
or
coop
code
will
get
operators
instead
of
having
to
go.
Look
at
all
these
different
objects
and
kind
of
piece
it
together,
yourself,
it'll
all
just
be
right.
There
work
just
like
you
know
you
would
say,
get
pods.
You
know
you're
not
going
to
go,
hunt
around
to
four
different
objects
to
try
to
figure
out
what's
going
on
with
your
pod,
so
we're
pretty
excited
about
that.
B
So
this
a
custom
object
that
an
operator
uses
that
doesn't
have
two
different
required
pieces
of
settings
in
there.
You
might
want
to
say,
hey,
go
reject
that
and
somebody
needs
to
go
resubmit,
that
with
the
valid
settings-
and
this
might
not
just
be
that
you
know
both
of
those
exists,
but
the
values
of
them
can
be
compared
with
custom
logic,
so
that
you
know
that
it
is
actually
truly
valid.
B
An
example
of
this
is
jet
stacks,
really
popular
cert
manager
for
doing
let's
encrypt
certificates
for
PK
I
validate
some
of
the
settings
against
other
things
that
you
pass
in.
So
they
didn't
know
that
you're
gonna
get
a
valid
sort
out
and
that
your
environment
and
the
settings
that
you're
passing
in
are
actually
able
to
create
a
certificate
that
they
can
issue.
B
So
that's
really
exciting.
So
we,
what
we
do
is
we
scaffold
all
these
web
hooks
and,
if
you
have
to
imagine
you
know,
these
have
to
have
TLS
and
they're
secured
and
they're
sitting
in
the
critical
path
of
Kubb
operating,
because
it's
gonna
ask
for
every
object.
You
know
it's
listening
for,
hey,
go,
send
offer
to
this
web
hook
and
give
it
a
yay
or
nay.
B
If
the
web
hook
is
down
you're,
not
making
any
objects
because
it
can't
make
it
yeah
or
a
negative
Susan,
and
so
what
we
do
is
we
use
the
platform
olam
and
openshift
to
scaffold
all
of
that
for
you,
so
we
rotate
your
TLS
certificates.
We
generate
them
the
first
place.
We
set
up
all
the
routes
and
ingress
for
it
to
work.
We
run
the
pod
that
runs
the
web
hook
and
all
that
kind
of
stuff,
so
really
really
easy.
All
you
do
is
write
your
logic
for
the
web
book
itself.
B
Mutating
web
hooks
work
the
same
way:
you're,
basically
mutating
things
instead
of
blocking
admission
of
them.
So
if
you
wanted
to
parameter
on
every
single
object
that
go
to
the
system
for
like
auditing,
or
so
you
know
all
kinds
of
things
like
that,
you
can
do
that
and
you
can
also
block
mutation
if
somebody
were
to
enter
into
a
bad
state
for
that
operator.
Just
like
the
settings
you
wanted
to
block
on
create,
you
can
also
do
that
on
edit.
So
a
good
example
of
this
is
coop.
B
Db
is
an
operator
that
helps
you
run,
DB
zon
cube
and
it
actually
prevents
accidental
deletions.
So
it
can
look
at
the
cluster
and
figure
out.
If
it
thinks
that
you
didn't
clean
up,
you
know
you
didn't
delete
all
the
objects.
You
just
happened.
Delete
this
one
critical
one:
did
you
really
mean
it
delete
that
are
some
behaviors,
that
it
can
power
I'm
such
really
exciting
and
then
the
last
part
of
this
is
going
to
be
in
later.
B
You
might
need
to
mutate
existing
CRTs
that
are
already
in
the
cluster,
for
them
to
you,
know,
meet
that
new
standard
and
so
you'll
be
able
to
do
those
in
the
same
manner
and
a
success
of
open
ship
release
all
right.
So
that's
all
in
four
five
now
I
just
want
to
touch
a
little
bit
more
on
the
future
and
what's
coming
in
the
next
year
or
so,
and
one
of
the
things
that
we've
been
working
on
is
an
easier
update
graph.
B
So
if
you
picture
when
you're
updating
from
version
1
to
2
to
3
to
4,
some
of
those
versions
might
be
able
to
be
skipped.
Some
of
them
might
not.
Some
of
them
might
not
work
with
each
other.
Some
of
them
might
have
a
bug
later
on
that
you
want
to
revoke
that
update.
So
all
the
typical
tools
that
you
would
use
to
like
run
a
SAS
or
to
you
know,
manage
packages
on
a
system
we're
bringing
in
to
OLM,
and
so
we
have
a
lot
of
that
today.
B
But
what
we
don't
really
have
is
just
an
easy
way
to
say:
hey,
follow,
just
semantic
versioning
and
just
kind
of
make
it
work.
You
know
how
it
should
so.
You
can
see
some
examples
here
on
the
left.
So
if
you
have
auto
updates
on
going
from
1
1
1
2
1
1,
2,
2,
1,
1
3
just
kind
of
works,
the
way
you
would
think
so,
those
make
it
easier
for
teams
that
are
building
operators
to
just
get
things
updated
and
then
for
teams
that
are
consuming
them.
B
You
know
admins
just
to
get
the
updates
as
they
would
expect
and
then,
if
you
did
have
you
know
automatic
updates
on
it
works.
If
you
want
to
have
a
manual
approval,
you
know
this
thing
would
wait
for
you
to
say
yes,
I
want
to
update
to
that
version,
so
you've
got
both
flows
that
you
can
unlock
all
this
is
without
building
an
explicit
graph,
which
is
behavior
that
we
had
before.
Where
you
could
say,
this
version
replaces
that
version,
and
then
you
know
the
next
version
I
would
replace
that
one
etc.
B
That's
exciting!
That's
gonna
be
coming
soon
and
we're
laying
some
of
the
disk
Appling
for
that
today,
on
the
STK
side,
we've
been
integrating
for
several
months
now,
with
upstream
project
in
kubernetes
called
cube
builder.
This
is
a
very
low-level
framework
for
building
go
based.
Operators,
it's
kind
of
what
a
lot
of
the
tooling
inside
of
kubernetes
itself
uses
to
build
operators,
or
you
know
their
their
controllers.
B
So
if
you
think
of
COO
builder
is
just
it's
literally
just
some
code
and
some
scaffolding,
but
you
don't
get
the
functional
testing
and
all
the
packaging,
our
CLI
for
doing
all
the
different
workflows.
You
need
a
better
user
experience,
that's
what
you'll
get
from
using
the
SDK,
even
though
the
bits
on
under
the
hood
are
some
of
that
same
coop
builder
goodness.
So
this
also
aligns
us
with
the
upstream
group,
and
you
know
we
can
all
work
together
towards
a
common
goal.
B
Next
I've
talked
about
testing
a
few
times,
we're
moving
to
embrace
another
open-source
project
called
cuddle,
kayuu
TTL
for
our
scorecard
test,
so
our
scorecard
is
a
way
to
both
do
validating
and
functional
testing
of
an
operator
and
cuddle
has
a
really
powerful
way
of
doing
assertion
based
testing.
So
you
know
you
install
a
version
of
the
operator,
and
you
know
you
change.
So
you
start
three
replicas
and
it'll
go
make
sure
that
you
have
three
pods
running
or
whatever
it
needs
to
be
running.
B
Then,
if
you
change
that
to
four
that
it
actually
changed
a
four
etc.
So
you
can
test
out
in
a
fairly
light
touch
way
your
operators
behavior
and
so
we're
going
to
integrate
this
into
the
SDK,
and
we
hope
this
will
make
for
a
lot
more
mature
operators,
and
so
that
folks
can
then
you
know
even
test
these
on
their
own.
B
If
you
are
at
one
of
these
big
organizations-
and
you
do
extensive
validation,
a
software
before
it
gets
in
your
environment,
you
can
use
these
tests
to
validate
it,
that
it
works
exactly
correctly
in
your
environment
as
well.
This
is
important
as
some
operators.
You
know
may
call
out
to
hosted
services
like
a
lot
of
monitoring
tools
will
run
an
agent
on
your
cluster,
but
then
go
talk
to
one
of
their
SAS
services
and,
if
you're
in
a
disconnected
environment
that
might
not
work.
So
some
of
these
testing
tools
can
help.
B
B
So
just
to
sum
it
up.
This
is
all
the
the
new
stuff
that
we
are
talking
about.
Csv
list
bundles.
This
is
that
new
bundle
format
we
are
talking
about
the
Sim
Sim
verb
based
upgrade
logic,
so
not
having
to
build
this
extensive
graph
being
able
to
bundle
functional
tasks
with
your
operator,
building
catalogs
with
kubernetes
tooling,
so
that
you
can
register
a
set
of
operators
onto
a
cluster
at
the
same
time,
more
integrated
packaging.
B
So
direct
ties
between
the
SDK
and
OLM,
especially
around
that
new
bundle,
format
and
then
bringing
coop
builder
style
operators
into
the
framework
and
then
on
the
cluster
admin
side,
some
of
more
advanced
dependency
resolution
and
being
able
to
disable
that
the
Opium
tool
for
offline,
mirroring
of
all
the
containers
needed
for
an
operator,
the
new
operator,
API
and
then
web
hooks
and
something
we
didn't
talk
about,
which
is
the
ability
to
choose
a
more
fine-grained
version
of
an
operator.
Instead
of
pulling
off
the
latest
one
of
a
channel.
You
can
choose.
B
So
that's
all
coming
and
we're
pretty
excited
about
that
kind
of
meets
everybody's
needs
from
cluster
admins
to
operator
developers
to
operate
our
users,
and
so
that's,
basically,
all
of
the
goodness
we
have
coming
in
roughly
the
next
year.
Ish,
so
you'll
have
to
pay
attention
to
the
github
and
mailing
list
and
all
that
to
stay
up
to
date
on
that,
and
we
can
always
do
another
briefing,
of
course,
and
we'd
love
to
have
your
interaction
in
those
communities.
B
So
if
you've
got
new
features,
you
want
to
see
us
go
in
a
different
direction
for
something
or
adopt
a
use
case
that
you
think
maybe
is
not
unique
to
you
and
that
we
should
address
with
the
entire
community.
We
would
love
to
have
you
on
our
different
community
calls
mailing
list.
Github,
please
interact
with
us,
and
so
that's
all.
I
have
I
think
we're
gonna,
take
some
questions
and
just
have
some
open
discussion
about
the
operator
framework
in
general.
Yeah.
A
Well,
thank
you
rob,
and
that
was
a
pretty
good
tour
de
force
and
there
was
a
lot
in
that
packed
into
that
little
half
an
hour.
So
one
thing
that
would
be
really
great.
There's
a
couple
of
other
folks
that
are
on
the
call
here.
I
know
who's
here,
I'm
just
going
to
put
you
on
on
on
view,
there's
the
the
announcement
should
come
shortly
around
the
operator
work
and
incubation
status
for
the
CNC
F.
The
boat
went
through
the
day
before
yesterday.
A
More
came
in
so
that's
great
huge
shout
out
to
the
TOC
for
making
this
happen
and
working
with
us
and
getting
all
the
jumping
through
all
the
hoops
was
was
actually
worth
the
effort
and
we're
really
pleased
to
be
there,
though,
and
Austin
is
one
of
the
organizers
for
the
SDK
working
group,
so
the
sub
working
group
of
the
operator
framework
so
to
say
hi
Austin,
and
if
you
wanted
to
get
involved
right
now,
where
would
you
ask
them?
Where
would
you
send
people.
C
Yeah
the
best
place,
the
the
central
hub
for
where
to
get
in
contact
with
us
is
the
community
repo
in
the
operator
framework
github,
and
that
will
point
you
to
the
other
places.
But
just
to
give
you
a
preview
of
what
you
might
see,
you'll
see
three
working
group
meetings,
the
operator
framework
meeting,
which
is
the
third
Tuesday
of
the
month,
the
operator
SDK
community
meeting,
which
is
monthly
on
the
first
Wednesday
and
the
operator
framework
OLM
working
group,
which
is
every
two
weeks
on
Thursday.
C
A
And
I'm
sure
there'll
be
some
more
infrastructure
and
scaffolding
created
as
we
move
over
to
the
CNC
F
and
all
of
the
other,
SIG's
and
stuff
like
that.
So
watch
for
some
transitioning
news
and
information
coming
out
in
the
upcoming
days
and
we'll
probably
have
another
chat
about
that
sometime
online
as
well.
So
there
are
a
couple
of
questions
and
I
thought
the
first
one
was
kind
of
pretty
good.
A
B
Sure
yeah
I'll
start
with
that
one,
so
Coulomb
works
against
any
coupe
and
so
a
lot
of
the
features
that
we
talked
about.
You
know
the
SDK
runs
on
your
laptop
for
the
most
part,
and
so
anything
cluster
related
is
going
to
be
om
and
you
can
use
that
against
any
coupe.
So
we
do
some
testing
on
upstream
and
of
course,
it's
built
into
OpenShift
and
hopefully
with
the
CN
CF
adoption
we'll
see
that
get
built
into
other
Kubb
distres
as
well.
B
So
you
get
all
of
that
kind
of
no
matter
where
you're
running,
depending
on
which
version
of
olam
you
have
so
in
openshift,
four,
four,
five,
the
new
operator
api
is
going
to
be:
it's
not
GA.
Yet
because
it's
going
to
be
read-only,
and
so
you
can
optionally
enable
a
feature
flag
to
use
that
new
api,
but
it
will
only
be
reading.
If
you
want
to
mutate
those
objects,
you
will
use
the
old.
B
You
know
interacting
with
a
CSV
directly
or
a
subscription
or
install
plan,
and
then,
if
you,
you
know
over
successive
releases
will
have
kind
of
the
two-way
binding
on
those
objects
and
then
eventually
deprecated.
The
old
objects,
but
that
will
happen
over
a
long
period
of
time
as
we
start
testing
it
out.
So
this
is
really
a
preview
for
folks
is
to
check
out
that
new
API
we'd
love
feedback,
we'd
love!
Any
of
that
that
you
have
so
that
yeah
you
can
treat
it
more
as
a
tech
preview,
not
a
GA.
Yet.
A
I
think
maybe
because
we
said
having
so
many
conversations
in
different
working
groups
about
disconnected
stuff
wool
leads
got
a
question
about
if
meat
not
really
a
question,
but
if
you
could
elaborate
a
little
bit
more
on
disconnected
restricted
environment
enhancements
and
how
they
could
people
can
overcome
any
possible
constraints
on
how
operators
are
built
in
the
first
place,
assuming
internet
access
and
he's
also
not
quite
sure.
What
is
that
CSV
sure.
B
The
CSV
is
a
cluster
service
version,
which
is
just
the
metadata
around
an
operator,
and
so
it's
you
know
the
operator
is
a
container.
So
where
do
I
go
get
that
container?
How
does
it
need
to
run?
Does
it
need
a
special
service
account
when
I
do
need
a
service
account?
What
auerbach
does
that
need
to
have,
and
so
the
the
CSV
holds
all
that
information
just
about
how
to
how
to
run
and
manage
this
thing?
So
that's
what
that
is
now
for
disconnected
and
restricted
environments.
B
What
you
need
to
do
is
for
every
mention
of
an
operators
container
or
containers
that
it's
going
to
spawn,
so
we
call
those
the
operands.
So
if
you
have
a
mice
equal
operator,
then
you
would
have
operand
pods
of
my
sequel
running
on
your
cluster.
So
you
need
to
basically
tell
that
operator
hey
instead
of
going
to
get
those
from
Quay
or
from
docker
hub
or
from
this
online
registry.
I
actually
need
you
to
get
them
from
my
private,
disconnected
registry.
Over
here,
that's
available.
B
You
know
in
my
restricted
environment,
and
so
that's
what
all
the
features
are
about.
Is
scaffolding
the
code
of
the
operator
such
that
swapping
out
those
images?
You
know
that's
going
to
be
the
same
digest
and
so
you're
getting
the
same
container,
but
it
needs
to
come
from
a
different
place,
and
so
that's
where
a
lot
of
the
the
scaffolding
for
disconnected
is
happening
is
moving.
Those
container
images
around
inside
of
the
CSV
there's
a
special
metadata
field
for
related
images,
and
this
is
all
the
operand
images
that
this
operator
is
going
to
stamp
out.
B
We
need
to
know
what
those
are,
because
you
can
embed
them
if
you're
familiar
with
helm,
charts
you'll,
see
that
you
know
they're
basically
built
as
strings,
and
you
know
sometimes
you'll
take
in
a
tag,
and
so,
if
we
don't
know
the
exact,
explicit
image,
we
can't
mirror
them.
We
can't
iterate
every
single
tag
that
exists
on
this,
this
repo
and
sometimes
there's
not
even
a
way
to
find
that
out
and
so
there's
a
bunch
of
scaffolding
to
help
you
do
that
and
then
that
OPM
tool
will
help
you.
B
And
so
that
that
represents
that
those
folks
need
to
embrace
that
a
little
bit
of
indirection
versus
like
explicitly
calling
out
specific
operator
images,
they
need
to
support
folks,
mirroring
it
and
then
referencing
that
other
image.
Sometimes
when
you
have
hard
coded
references,
you
know
what
your
hands
are
kind
of
tied
there.
That's
what
that
that
article
is
most
likely
about,
as
a
listing
of
which
ones
are
hard
coded
and
which
ones
aren't
I'm.
B
B
So
that's
something
that
we're
we're
looking
to
do
for
both
operator
hub
and
inside
of
open.
Shipped
itself
is
when
you
have
that
related
images
section
filled
out,
we
can
reasonably
assume
that
this
operator
has
been
tested
in
a
disconnected
environment,
and
so
hopefully
over
time
as
more
operators
are
embracing.
This
is
that
we
can,
then
you
know
maybe
put
that
in
our
certification
pipeline
is
actually
checking.
You
know
that
this
does
work
in
a
disconnected
environment,
that
guy
thing.
A
B
A
B
Having
olam
accessible
to
you
as
a
developer's
as
an
operator
developer
is
interesting
because
that's
how
you
can
start
testing
all
those
upgrade
paths
yourself
so
and
you
know
tests
that
somebody
can
go
from
a
single
node
of
your
application
to
a
multi
node
version
of
it
to
maybe
test
out,
backup
and
restore
x'
and
that
they
can,
you
know,
restore
to
a
disaster
recovery
environment.
All
that
stuff
could
be
orchestrated
locally
as
well.
So
that's
important
yeah.
A
So
I'm
not
gonna,
ask
you
the
question:
I,
think
that
everybody
wants
to
know
is
really
is.
When
is
4.5
actually
coming
out
the
door
and
there's
like
yeah,
we
all
get
shot
for
that
saving
any
dates
in
science,
but
it
should
be
all
of
what
we're
talking
about
here
should
be
available
in
the
not-too-distant
future
and
because
it's
all
in
timing
and
then
in
four
six,
which
is
open,
shift
four
six.
A
B
The
main
things
for
that
are
going
to
be
getting
that
operator
API
into
a
reading
and
write
mode,
and
so
that
will
kind
of
have
both
of
those
living
side
by
side
and
four
six
and
then
some
more
extensive
dependency
management,
and
so
this
is
something
that
we've
been
exploring
as
operators
are
starting
to
get
more
intertwined,
as
people
are
building
products
that
you
know,
you
have
your
application
and
you
need
a
database
or
you
need.
You
know
like
a
Kafka
for
that
event.
B
Stream
like
we're
talking
about,
but
you
might
want
to
depend
not
just
on
the
latest
version
of
a
Kafka
operator,
but
maybe
a
very
specific
version
or
a
range
of
versions
or
it's
an
optional
dependency,
not
a
required
dependency.
So
bringing
all
that
type
of
fidelity
to
the
dependency
management
is
something
that
we're
going
to
be
exploring
in
four
six
and
beyond.
You
know
it's
not
an
overnight
thing,
but
you
know
getting
new
features
in
four
six
and
someone
for
seven,
seven,
forty,
eight
etc.
A
Oh
and
we
have
a
number
of
SDKs
already,
are
there
any
we've
talked
about
Python
SDKs
other
SDKs.
Are
there
any
other
SDKs
in
the
works
at
the
moment,
and
is
there
anything
that
from
Austin
or
others
that
that
we're
looking
at
building
out,
because
we
always
talk
about
helm
and
ansible
and
go
and
now
the
COO
builder
stuff,
and
that
why
do
we?
Maybe
how
do
we
get
more
languages
and
more
approaches
into
this
into
this
mix
or
other
plans
for
that.
C
So
the
helm
and
the
ansible
operators
are
not
that
they're
a
language
of
themselves,
but
they
are
actually
under
the
hood.
They
are
go
operators
as
well,
and
so
you
can
kind
of
think
of
them
as
more
like
a
shim
operator
that
allows
operators
in
those
respective
languages.
If
you
wanted
something
in
Python
or
any
other
language,
it's
going
to
be
it's
going
to
require
the
creation
of
controller
runtime
and
detling.
So
we're
not
there.
C
A
B
What
I
was
gonna
say:
Python
is
probably
one
of
the
ones
but
and
if
you
think
about
it,
developers
that
are
building
against
a
stack
know
their
stack.
So
if
you
run,
if
you're
a
big
investment
bank
or
something
and
you
write
Python,
you
probably
want
to
build
an
operator
in
Python
makes
sense.
You
know.
So
that's
where
folks
are
kind
of
demanding
that
that
wide
swath
of
stuff
and
so
and
there's
like
a
Java
framework,
that's
outside
of
our
SDK
that
people
use
to
build
operators
in
Java
and
that
kind
of
thing
look.
D
If
anyone
is
interested
in
helping
contribute
to
develop
some
of
those
underlying
libraries
that
are
so
critical
to
having
making
it
easy
to
develop
the
right
primitives
for
operators,
we're
definitely
interested
in
collaborating.
So
if
you're
out
there
and
you're
you've
got
a
Python
operator
and
you've
written
a
lot
of
primitives,
definitely
add
a
cephalus,
no
I.
D
Think
probably
one
of
the
big
hurdles
is
just
having
the
expertise
in
those
languages
and
knowing
how
to
basically
duplicate
the
equivalent
of
a
scaffolding
tool
that
can
lay
down
files
for
a
project
in
your
language
and
also
have
the
underlying
libraries
that
make
it
really
easy
to
basically
give
developers
a
reconcile
method
to
implement.
But
I
think.
The
kind
of
the
first
thing
that
we're
looking
for
is
those
kind
of
two
building
blocks.
D
A
Think
that
part
part
of
what
my
hope
is
with
the
the
CNC
F
incubation
project,
that
we'll
get
more
visibility
and
get
more
get
more
resources
and
experts
to
help
us
build
out
some
of
the
other
pieces.
That
will
be
helpful
to
continue
to
grow
the
adoption
of
operators
and
another.
You
mentioned
Rob,
also
the
the
certified
program
for
operators
and
wondering
if
you
could
talk
a
little
bit
about
how
people
get
involved
in
that
or
bring
their
bring
their
wares
to
the
operator
certification.
That
Red
Hat
has
sure.
B
Yes,
those
are
the
two
main
flavors
of
operators.
We
have
community
listening
and
opera
bio
and
then
we
have
vendors
that
are
building
commercially
supported
operators
or
building
operators
around
their
commercially
supported
software,
and
they
want
a
way
to
kind
of
get
like
the
stamp
of
approval
from
Red
Hat
that
this
software
works
well
and
integrates
well
with
the
openshift,
and
so
that's
our
certification
program.
And
basically
you
can
take
your
same
codebase
and
we
run
it
through
a
you
know
some
testing
and
we
want
to
make
sure
that
we
can
jointly
support.
B
Customers
is
a
big
part
of
this
program.
So
it's
not
just
technical.
It's
that
we
have
agreements
in
place
for
how
we
can
both
support
customer
tickets
and
escalations
and
bugs
and
things
like
that
and
a
you
know,
a
reasonable
time
frame.
So
that's
all
about
the
kind
of
wrapped
up
into
that
program.
We
have
a
web
page
I,
don't
have
it
off
the
top
of
my
head,
but
if
you
search
for
Red
Hat
operator,
certification,
you'll
find
it
and
that's
where
you
can
go
and
get
in
touch
with
some
of
our
engineers.
B
We
can
start
looking
at
your
operator
and
make
sure
that
it
works
well,
get
it
through
our
testing
pipeline
and
do
some
of
the
other.
You
know
business
side
of
things
to
get
that
certification
to
happen,
then
we've
got
like
probably
over
a
hundred
now
I
think
certified.
So
it's
a
well-oiled
machine-
and
you
know
across
all
the
categories
that
we
talked
about.
We've
got
storage
vendors.
We
got
all
the
major
databases,
we've
got
a
bunch
of
machine
learning
stuff
and
some
monitoring
services
and
all
kinds
of
things.
So
we
to
have
your
product
listed.
A
There
as
well
yeah-
and
you
know
this
is
from
the
community
side
of
things.
If
you
go
to
operator
hub,
do
there's
a
whole
set
of
documentation
in
there
to
step
you
through.
If
you
have
an
operator
how
to
get
it
in
there
and
there's
also,
the
I
think
the
interesting
thing
about
the
hubs,
and
that
is
that
they're
really
kind
of
based
on
a
catalog
and
what
you
could
resurface
and
rebuild
your
own
operator
hub
or
whatever,
using
the
the
underpinnings
as
well
and,
and
that
is
out
there
in
the
open-source
land
as
well.
A
So
for
those
of
you
who
are
standing
up
your
own
operator
hubs
there,
there
is
a
way,
there's
a
an
easy
way
for
you
to
do
that
as
well,
so
interesting
to
see,
see
that
I
think
there's
about
just
under
140
community
operators
in
operator
hub
do
at
the
moment,
and
it's
a
pretty
pretty
interesting
group
of
folks
who
have
come
in.
You
know
not
not
quite
randomly,
but
and
a
lot
of
them
are
done
in
conjunction
with
this.
They
do
a
certified
operator
and
they
also
put
one
in
the
community
as
well.
A
A
B
Yeah,
we
can
touch
on
it,
really
quick
if
you
want
so
just
understand
that
and
open
shifts.
We
have
a
new
model
where
we're
doing
these
over-the-air
upgrades
with
open
ship
4
and
that's
to
keep
you
kind
of
up
to
date
with
kubernetes
as
its
changing
as
it's
being
updated
for
new
features,
bugs
security,
enhancements,
etc,
and
so
we
encourage
folks
to
upgrade
often
as
often
as
we
release.
So
you
know
getting
from
4
3
to
4
4
to
4.
5
is
really
important
for
staying
on
top
of
the
you
know,
security.
B
If
your
class
and
remember
that's
the
version
of
the
operating
system
as
well
as
all
being
managed
with
that
version
and
the
guarantee
in
all
of
our
API
versioning
is
that
we
will
not
break
your
workloads
and
that's
including
over
that
upgrade.
You
should
not
experience
downtime
for
your
applications
and
if
you
do
that's
a
bug
and
we
want
to
fix
it,
and
so
you
know
we
have
these
tools
in
place
to
do
these
over.
B
They
are
upgrades
so
that,
when
you're
managing
a
fleet
of
clusters,
it's
not
any
harder
to
manage
one
cluster
as
it
is
a
hundred,
and
so
hopefully
you
know
you
don't
have
too
many
excuses
to
not
go
from
version
to
version
to
version.
You
can
also
skip
versions
if
you
want
and
migrate
your
applications
as
well,
but
all
of
the
workloads
that
we
have
you
know
we're
guaranteeing
did
not
break
that
compatibility
with
the
the
Kubb
api
version.
So
the
group
version
in
kind
looks
like
Waleed
wants
to
be
unmuted.
Yes,.
E
Hi
I
am
asking
this
question
because,
for
example,
when
you
talk
about
vendor
operators
like
port
works,
NSX
from
VMware,
they
are
certified
on
a
certain
release
that
most
of
them
they
certify
on
4.3
and
some
of
RedHat
consultants.
It
gives
us
this
advice
that
they
say
stay
on
this
table
for
three
latest
GA:
don't
move
to
4.4
and
actually
that's
what
I'm
trying
to
do
today,
I'm
trying
to
downgrade
to
4.3
but
I'm
wondering
if
this
is
like
the
good
trusted
advice
or,
as
you
say
that
we
should
move
forward.
E
B
I
mean
always
like
if
port
works,
our
VMware
or
whatever
is
a
hard
dependency
on.
You,
of
course,
listen
to
the
the
guidance
of
where
that's
supported,
but
I
know
we're
constantly
talking
to
both
of
those
vendors
on
getting
them
testing
the
latest
versions
as
soon
as
possible
and
certifying
those
on
their
side
as
fast
as
possible,
and
so
we
want
everybody
to
kind
of
move
forward
together.
B
So
you
know
that
we
stay
up-to-date
with
all
the
the
work
going
on
in
coop
the
feature
set
going
on
an
open
shift
and
then
the
features
inside
of
their
product
as
well,
and
keeping
that
all
moving
in
quick
succession
and
so
yeah
it's
a
sometimes.
This
is
a
new
model
for
some
of
those
vendors
and
so
we're
working
with
them.
A
Yeah
I'd
also
think
that
everybody
recognizes
the
complexity
of
the
ecosystem
that
were
in
at
the
moment
the
interdependencies
of
kubernetes
operators
brings
more
to
the
table.
Openshift
release
cycles.
You
know
this
is
this
is
a
very
complex
world
and
we
are,
you
know,
we're
all
in
conversations
constantly
with
the
partners
with
the
upstream
folks
and
trying
you
know,
that's
that's
part
I'm
not
going
to
keep
going
back.
That's
part
of
the
wonderful
part
about
being
included
in
the
kubrik.
A
The
CN
CF
incubation
process
is
hopefully
we'll
get
more
visibility
of
what
the
other
pieces
and
parts
of
the
universe
of
cloud
native
ecosystem
looks
like
and
can
have
more
conversations
with
these
other
folks,
not
that,
like
with
COO
builder,
and
was
it
cuddle
that
took
me.
There
are
a
lot
of
these
conversations
that
have
already
been
going
on
with
helm,
3
and
lots
of
other
folks
in
the
background,
but
I
think
that's
just
you
know.
A
This
is
one
of
the
complexities
of
such
a
big
ecosystem
is
managing
all
those
relationships,
and
you
know
we
the
more
we
can
do
it
out
in
the
open
and
the
more.
We
can
do
it
transparently,
with
lots
of
sunlight
on
it
and
lots
of
eyeballs
on
it.
The
easier
it'll
be
and
I
think
port
works,
and
the
other
folks
that
you
mentioned
will
lead
they're
all
they're,
all
in
this
community
with
us
together
and
we're
all
learning
together.
So
it's
getting
alignment
with
release
cycles
features,
that's
the
more.
A
We
talk
about
it,
the
better
off
we
all
are
so
yeah
touch
touch
base
with
your
your
operator,
vendor
partners-
and
you
know
there
I
know
there
are
those
ones
that
you
mentioned
are
definitely
in
conversations
with
us
quite
a
bit.
So
hopefully
we
can
get
there.
So
I'm
wondering
if
there's
any
questions,
let's
see,
there's
a
couple
more
chatting
here
coming
in
Dan
is
asking:
is
there
a
roadmap
for
the
Red
Hat
operators
that
will
be
released
to
the
operator
hub
ie?
Will
there
be
advanced
cluster
management?
Well,
that
was
yesterday's
topic,
but
Wilton.
B
Know
if
there's
a
specific
roadmap,
it's
kind
of
up
to
each
team
I
know
that
the
ACM,
the
advanced
cluster
management
team,
does
have
an
open-source
version
that
has
classic
with
Red
Hat
I,
don't
know
if
they
package
that
and
since
you're
asking
the
question
I'm
going
to
go
ahead
and
assume.
No,
so
I
can't
comment
on
what
that
team
is
gonna
do
there,
but
we
want
that
team
to
have
ownership
over
that
the
packaging
and
management
of
that
operator
just
like
we
want
any
of
the
other
open-source
projects
to
do
that.
A
That
would
be
great
and
I
know:
we've
had
an
ACM
talk
yesterday,
we'll
have
a
few
more
top,
so
you
have
opportunities
to
nudge
them
in
that
direction
as
well.
So
stay
tuned
and
we'll,
let
us
know,
are
there
other
operators
that
people
who
are
on
this
call
that
are
missing
or
that
we
that
you're
looking
for
besides
ACM
I,
think
ACM
is
top
of
brain
for
everybody.
A
Yes,
there
is
one
I
have
someone's
asking.
The
ACM
recording
from
yesterday
has
not
been
uploaded
to
YouTube,
but
if
you
look
on
the
twitch
stream,
the
raw
one
is
available
on
Twitch,
unfortunately
for
the
ACM
one.
Yesterday
the
demo
went
south.
The
demo
gods
were
not
with
them,
so
we
will
be
redoing
that
again
and
there's
another
one
next
week.
So
when
we
said
the
most
important
one
to
them,
is
the
open
data
hub
one
good
one
for
open
data
hub,
yet
I
thought.
F
A
Done
lots
of
briefings
I'm
like
I,
don't
think
there
could
be
an
operator
for
open
data
hub
open
data.
Hub
is
a
thing
he
yeah
bird
did
a
great
demo,
but
I
don't
like
oh
and
I,
and
actually
this
is
a
good
segue
we're
having
an
AMA
in
a
couple
of
weeks
on
a
Monday.
If
you
look
at
the
calendar
with
the
open
data
hub
team
at
noon,
Eastern
9
a.m.
Pacific
in
a
second,
but
you
can
ask
them
that,
but
open
data
hub
per
se
is
not
is
not
something
that
is.
A
A
A
And
there
we
go
so
this.
This
is
the
github
repo
and
that's
okay,
the
github
repo
and
the
Google.
Groups
are
really.
If
you
go
to
the
community
page
under
here,
I
think
there
should
be
one
size
community.
This
is
really
where
you
can
find
out
how
to
get
a
hold
of
us
to
participate
in
this,
and,
as
I
said
at
the
very
beginning,
this
too
will
change.
A
There
will
be
a
little
probably
cleanup
migration
over
to
and
we've
done
a
lot
of,
work,
getting
ready
for
the
CN,
CF
donation
and
the
being
incubated
by
the
CN
CF,
so
even
not
drastic
changes,
but
you
should
see
some
other
pieces
and
parts
of
this
pop-up
and
then
in
the
coming
weeks
or
so
so
what
I
wanted
to
really
do
is
just
Rob.
Do
you
have
any
final
words
that
you
want
to
add
to
here.
B
I'll
just
say
that
we're
really
excited
about
the
CNC
up
news
and
we're
excited
to
get
an
even
stronger
community
than
we
already
have
together
through
that
organization.
So
we'd
love
to
hear
from
you
how
you're
building
operators
like
I
said
we
want
to
certify
operators.
We
want
community
operators
being
listed.
We
just
want
to
make
this
as
big
and
as
powerful
as
possible
and
meet
everybody's
needs.
So
please
get
involved
slack
mailing
lists
finance
at
conferences
whatever
it
is.
We'd
love
to
hear
from
you.
A
Yeah,
that's
the
other
thing,
but
you
know
we
will
be
around,
especially
for
the
CNC
F
koukin.
That's
coming
up
in
Fort
Lee
a
few
weeks
once,
whatever
soon
so,
you
know
look
for
us
there.
We
should
have
a
bit
of
a
splash
there
with
the
announcement
and
well.
A
lot
of
us
will
be
online
in
the
chats
for
the
different
than
many
operator
related
conversations
and
talks
there.
So
you
can
definitely
find
us
there
and
we're
looking
for
you
and
your
participation
in
this
community.