►
From YouTube: CNCF TOC Meeting 2019-12-03
Description
Join us for Kubernetes Forums Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
CNCF TOC Meeting 2019-12-03
A
A
We've
got
our
standard
agenda.
We've
got
some
notes
coming
in
from
cube
con,
we've
got
our
sig
updates
and
we'll
have
be
having
some
presentations
from
Juba
an
operator
hub.
I
am
now
playing
the
role
today
of
Liz
race,
who
is
so
yeah.
Some
notes
from
Q
Khan
want
to
be
able
to
highlight
the
be
head
thousand
attendees
here
today
and
big
big
important
thing.
As
Chris
is
noted
over
in
chat
December
4th,
that's
the
deadline
for
our
Amsterdam
pieces.
Again,
of
course,
anything
on
that.
A
Yeah
coming
up,
we've
got
our
keep
cons,
you've
seen
and
for
those
that
are
in
reinvent.
We
want
to
be
able
to
let
you
know
that
we
do
have
a
night
of
networking
details
over
on
the
Twitter
account
as
well
as
the
slides
here.
Please
RSVP,
so
we
know
you're
coming
all
right,
yep
last
pieces
in
here
the
kubernetes
forums
they
are
coming
very
very
soon
and
one
note
we
do
still
have
India
sponsorships
available
as
well
as
the
opportunity
to
be
able
to
do
co-located
days
for
the
India
events
as
well.
A
So
please
reach
out
if
that's
something
you're
interested
in
all
right
other
pieces
in
here.
As
far
as
housekeeping
we
have
current
votes
table,
we've
got
a
vote.
We've
got
a
sick,
Network
vote
and
the
tough
graduation
vote.
So
these
are
all
currently
open.
If
you
want
to
be
able
to
add
both
binding
votes
from
TOC
or
show
us
support,
votes,
non-binding
votes,
please
go
ahead
and
drop
those
into
the
mailing
lists.
D
All
right,
so
hey
update
from
sick
app
delivery.
Here
first,
we
are
out
first
two
sessions
at
cube
con
on
it
like
an
introductory
session
and
a
detailed
session
on
the
app
delivery
model
which
we
have
been
working
on.
This
was
very
well
received
the
feedback
from
the
community.
It
was
very
good
to
have
that
sweat,
chill
approach,
and
we
got
some
additional
questions
around
it
very
notably.
We
also
asked
the
audience
what
they
would
be
mostly
interested
in
learning
more
about.
D
One
key
aspect
really
was
hear
about
communities
for
air-gapped
environments,
as
we
got
some
feedback
a
lot
of
the
telecommunication
industry.
So
the
main
the
main
question
is
basically,
how
can
I
run
my
company
this
environment
and
which
also
obviously
ties
into
the
whole
application
packaging
topic?
D
D
Already,
but
we
will
have
a
first
discussion
tomorrow
and
then
get
back
with
you
see
was
the
working
progress
on
the
project
evaluation,
so
we
have
of
a
couple
of
evaluations
that
are
pending
from
sick
delivery
right
now.
This
is
just
a
friendly
reminder
that
we
would
like
to
have
some
input
on
evaluation,
guidance
and
diligence
documents
which
we
could
use
as
templates
here.
I
think
that's
where
we
kind
of
stuck
somehow
is
what
is
the
ideal
format
to
present
this
back?
D
To
did
you
see
this
is
where
CJ
up
delivery
is
still
looking
for
guidance
and
how
we
should
best
handle
this.
Everything
that
that
you
seek
and
share
with
us
is
is
how
we
appreciate
that
here,
so
whether
it's
also
past
evaluations,
but
that
was
available
during
our
cubicle
meeting.
It
was
mentioned
that
there
is
now
a
template.
It
has
been
or
isn't
the
process
of
being
created.
So
please
please
share
this
with
us,
so
we
can
use
it
also
here,
hello,.
E
D
Thank
you,
I
was
assuming
that,
given
the
whole
Thanksgiving
holidays,
you
might
be
out
but
expect
almost
a
feedback
once
you
have
these
documents
and
can
provide
more
just
on
some
projects.
We
have
that
happen
that
have
presented
some
feedback
here.
Weather
would
also
have
a
more
detailed
discussion
with
stat
you
see
about
the
Argo
project,
which
is
currently
under
review.
The
question
here
is,
or
the
challenge
here
is
that
looking
at
Argo,
you
look
looking
at
our
goal.
Cdi
events
are
Group
fluent
those
projects.
D
It's
actually
had
a
single
project
submission
it's
a
submission
of
multiple
projects
and
also
these
different
projects
have
also
a
different
maturity
and
community
adoption.
So
this
was
more
than
antenna
diversity.
You
see
an
open
discussion.
How
to
handle
situations
like
this,
where
somebody
not
just
propose
like
single
project
but
a
bunch
of
them
all
together
on
the
operate
the
framework.
This
is
actually
a
nice
coincidence
that
we
have
later
on
the
discussion
about
the
operator
hub.
D
There
was
just
a
question
whether
we
should
split
up
the
operators
framework
as
a
project
from
the
operator
hub
discussion.
Simply
because
the
operator
framework
covers
is
this
project
to
build
operators.
The
operator
hub
is
coming
with
its
own
infrastructure
requirements
and
a
lot
more
around
that
the
hub
itself
like
what
it's
accepting
other
operators,
how
to
handle
these
things
and
also
the
costs
obviously
of
running
it.
But
as
we
have
a
presentation
on
operator
hub
today,
I
would
be
for
here
for
the
presentation
later
on.
D
F
D
H
So
sick
storage
was
quite
busy
at
UConn.
We
we
had.
We
had
a
rather
than
a
session
with
a
lot
of
the
a
lot
of
the
leads
and
co-chairs
for
present,
and
it
was
we.
It
was
really
good
to
to
have
a
number
of
people
after
the
session
to
show
interest
in
working
with
us
and
and
contributing
boats
to
use
cases
and
some
of
them
white
papers
that
that
we're
that
we're
building,
which
I'll
talk
about
in
a
second
we
there
was.
H
H
We
we
had
a
good
discussion
between
some
members
of
the
talk
and
the
Sigma
members
discussing
some
of
the
processes
and
workflows.
So
I've
been
in
a
link
for
some
of
the
discussions
we've
been
having
in
the
in
the
sake.
You
know
I'm
sourcing
and
we'll
be
looking
to
integrate,
that
to
document
atlases.
Putting
together
like
slides,
we
buy
I,
noticed
you're,
also
having
the
giraffe
s
presentation
later
on.
So
I
put
this
in
just
for
informational
purposes.
H
I
We
have
the
the
kind
of
the
main
activity
that
we've
been
doing
over
the
last
few
months
is
organizing
ourselves
so
that
at
the
growth
in
our
membership
doesn't
take
all
of
our
attention
and
I
want
to
highlight
the
roles
that
members
have
been
taking
on.
We
have
meeting
facilitators
project
leads
and
new
security
reviewers,
and
so
you
can
check
out
that
link
if
you
want
to
see
how
we're
helping
the
group
self
organize.
One
of
the
outcomes
of
the
in
toto
security
assessment,
which
was
our
first
assessment,
is
the
supply
chain
security
compromised
catalogs.
I
So
there's
a
PR
that
we're
in
toto
Santiago,
Torres
lily
of
the
Antonio
project
has
contributed
their
collection
of
supply,
chain
compromises
and
then
the
next
step.
We
already
have
a
PR
out
for
categorizing
them.
We
want
to
learn
from
these
and
and
help
educate
ourselves
and
the
community
about
the
threat,
the
different
classes
of
threats
of
supply
chain
compromises.
We
also
had
swagway
every
but
also
is
very
excited
about
our
logo.
We
have
a
raccoons
secret-agent,
a
spirit,
animal
for
six
security,
so
Amy.
I
I
So
we
had
cloud
native
security
day
which
was
sold
out
with
a
hundred
and
seventy-five
people.
We
had
lots
of
contributed
talks
with
the
board.
There
was
a
open
spaces
session
which
allowed
for
a
lot
of
discussion,
and
we
got
a
lot
of
positive
feedback
about
the
interaction
between
the
people
who
were
attending
that
we
had
intersession
and
deep
dive,
and
you
can
see
in
the
bottom
right
that
a
lot
of
the
active
members
and
new
members
got
together
for
a
dinner
social
next
slide.
I
I
wanted
to
highlight
a
recent
thing
that
we've
done,
which
it,
which
was
in
preparation
for
coop
con,
where
we
added
templates
for
issues-
and
this
was
we
had
some
of
them
already,
but
particularly
we
added
a
presentation
template.
So
this
allows
anyone
to
contribute
an
issue
that
automatically
gets
tagged,
and
this
really
helps
streamline.
I
Setting
up
cloud
custodian
is
going
to
come
present
to
us
on
December,
11th
and
I
also
wanted
to
announce
that
December
4th
tomorrow,
Melanie
Ruiz
neck
I,
hope
I'm
pronouncing
that
right
from
radical
radically
open
security
will
be
giving
a
talk
to
the
group
and
radically
open
security.
Is
a
not-for-profit
computer
security
consultancy
that
recently
did
open
source
audit
of
Mozilla
through
their
mas
program
and
so
they're
going
to
talk
to
us
about
how
they
do
open
security.
So
we're
really
excited
to
have
Melanie
back
there
and
anybody
is
welcome
to
come,
attend
10
a.m.
J
From
my
part,
it
was
particularly
heartwarming
to
hear
some
network
engineers
there,
some
non
developers
raising
their
hands
actively
interested
in
the
topics
at
hand
and
wanting
to
ensure
that
they
were
that
they
should
be
participating,
that
it
was
going
to
be
that
the
set
of
discussions
were
going
to
be
inclusive
of
non
developers.
If
you
will
ice.
J
J
Just
take
some
Python,
that's
not
just
that!
So
so,
while
on
that
there
was
an
article
written
up
by
Sean,
Michael
Carnot,
the
Kerner
that
was
appreciated
that
describes
some
of
the
discussions
there
I
think
both
you
know
given
reinvent
this
week
and
the
pending
final
binding
vote
for
the
sig.
Our
upcoming
first
Thursday
of
the
month
meeting
will
probably
be
postponed
this
week
pending
those
those
two
items,
Ken
and
Matt
in
anything
that
I
missed
from
our
discussions
at
guca.
K
No
sounds
good
to
me.
I'm
just
gonna.
Add
that
there's
definitely
a
lot
of
interest
in
this
sig
and
so
I
was
I
was
really
encouraged
to
see
that
as
well
as
usually
so
I
think
it's
a
good
sign
that
you
know
seems
he
is
moving
in
the
right
path
by
by
making
this
a
saying
and
there's
gonna
be
a
lot
of.
There
are
a
lot
of
none
like
now.
Work.
Only
type
of
questions
being
asked
like
how
do
how
do
we
kind
of
integrate
this
with
the
experience
of
cloud
native,
Ansari
I?
L
Hello,
everyone
hi
yeah
today,
I
want
to
present
to
the
class
Chewbacca's
is
a
is
a
distributed.
File
system
designed
for
quality
vacations
in
the
targets
are
continuous
and
stateful
services
who
need
persistent
and
reliable
storage
that
can
be
accessible
like
local
file
system.
It's
a
its
production
ready,
which
means
that
they
is
already
being
used
to
support
whatever
160
application
services
ran
around
JD's
Pilates
platform.
L
L
It
supports
Monica
Nancy,
which
means
that
the
different
application
services
can
share
the
same
online
storage
infrastructure.
It's
it
has
a
general
purpose
for
attending
welcome
user
to
store
both
large
and
small
files,
and
it
also
supports
like
different
file.
Access
such
as
conjoined
random
acts,
assets
the
fastest
early
selfies.
That
is
highly
scalable,
because
we
employed
a
separate
method,
a
cluster
to
store
the
file
metadata.
It
provides
politics
compliant
api's
which
comply
with
pausing
semantics
by
the
end
of
December.
L
We
expect
when
these
that
we
combine
declares
as
well,
which
is
an
admixture
for
us
next
yeah.
So
here
user
is
a
general
architecture
of
the
file
system
on
the
upper
portion
is
a
container
platform.
The
different
colors
represent
different
application
services.
Learning
on
the
continent
upon
the
lower
portion
is
the
shared
online
storage
infrastructure,
which
has
like
three
components:
the
data
subsystem,
the
metadata
subsystem
and
elusive
manager.
The
the
Linux
of
system
is
the
place
where
the
file
contains
Artemis
thought.
L
So
card
which
workers
support
the
cumulative
CSI
driver
B,
but
not
zero,
we
we
have
a
superbly
avoid.
We
also
have
I
the
talk
of
compost
to
create
and
started
that
subsystems
and
the
the
resource
manager
visa
with
a
single
command.
That
is.
That
means
the
easy
is
this
way
to
to
try
the
Chewbacca's
on
lappa.
L
So
here
is
a
is
a
brief
history
of
the
project.
We
managed
the
project
on
on
january
2017
and
open
source
of
these
projects
on
March
2019.
We
are
three
months
later.
We
we
did
our
presentation
or
two
story,
c-jun
routes
of
this
year
and
short
of
data.
We
got
our
first,
it's
no
use
I
reckon
over
on
July
force.
We
present
our
industry
paper
on
Sigma
2019
and
right
after
that,
we
got
cut
off
first
mentioned
outside
JD
on
middle
of
August.
We
release
our
support
to
assess
a
driver.
L
We
went
at
zero
and
two
weeks
later,
we
we
speak
out
also
to
since
our
sandbox.
Just
recently,
we
released
the
secod
to
harm
us.
We
so
so
the
project
self
seeking
heart
under
the
Apache
2.0
license
even
received
more
than
a
little
bit
more
than
400
github
stars.
It
has
like
77
github
folks
and
we
we
currently
have
14
minors
from
three
different
companies.
L
So
so
next
I
will
talk
about
the
production
adapters,
so
how
Chewbacca's
has
been
used
in
JD?
The
first
example
the
first
use
case
I
want
to
talk
about
is
the
machine
learning
area.
So
in
jelly
we
have
our
in-house
motion
any
platform
in
a
scope
on
that
era.
I
used
to
store
on
just
on
the
local
disk,
but
as
our
business
grows,
we
cause
a
loss
of
like
training
data
and
the
training
data
size
is
always
mostly
like
on
the
TV
level
and
that
the
content
of
data
keeps
changing.
L
So
this
is
the
use
case
that
aware
to
our
efforts
can
be
a
good
fit
because
it
provides
those
aussies
api's.
So
the
migration
form,
the
lock
is
the
solution
to
swap
affairs
can
just
require
minimum
minimum
joining
efforts
and,
on
the
other
hand,
because
of
these
kind
of
migration.
We
imitates
those
that
the
the
shock
I
say
the
limitations
of
the
local
disk
space.
So
another
example
is:
is
the
merciful
database
backup
so
I'm,
the
official
or
my
circle
documents?
L
The
back
bar
usually
wasn't
OSS
SDK
or
restful
api
s--,
but
it's
kind
of
increasing
the
operation
cost
fuss
and
that
the
backup
files
are
forces
fired,
multiple
layers
of
services,
which
kind
of
cost
performance.
If
the
backup
files
is,
is
this
kind
of
trouble
some
to
to
do
the
troubleshooting
to
do
the
debugging?
So
so
this
another
use
case
that
we
we
switch
to
to
to
to
to
bio
test,
because
by
doing
so
we,
firstly
we
we
just
will
backup
the
files
like
like
we
unlock
ADIZ.
L
We
can
click
on
the
the
page
and
write
cache
to
to
greatly
improve
the
performance
and
by
by
checking
those
log
files
provided
Bachelor
of
us
who
can
easy
check
if
anything
failed
and
between
doing
the
troubleshooting.
So
they
are
more
like
making
use
cases
than
just
the
two
that
I
just
mentioned.
We
can't
find
it
online
from
our
farm.
Our
documents,
next
cartridge
fibers
has
to
external
users.
The
first
one
is
the
drug
know
where
we
are
coming
China.
That
provides
with
your
perception
assumptions.
The
user
PC
is
more
like
using
traffic
to
store.
L
Those
are
large
number
of
small
image
files,
another
in
sponsoring
in
Thai,
which
is
an
infamous
vendor
of
in
the
industry,
supplies
that
to
use
cases
for
them.
Why
is
the
engine
block
storage
for
for,
as
course,
a
settlement
and
the
other
one?
Is
the
product
image
storage
similar
to
your
ANOVA?
Next,
please
so
I
want
to
tell
I
want
to
talk
about
the
scope
of
Travis
the
alternatives
and
as
well
as
how
it
compares
you
to
easy
steam
since
our
projects,
the
wonderful
firm
from
the
distributed
file
system
area.
L
So
one
of
the
famous
one
is
the
file
system
and
its
successors,
the
classes,
which
is
because
in-house
solution
working
together
was
bought
from
the
public
website.
We
have
a
de
brest
EFS
and
many
others.
We
also
have
a
sacrifice,
aghast
FS,
those
kind
of
a
popular
open
source,
sorry,
storage
solutions.
We
have
a
very
comprehensive
comparison
from
the
performance
escapades
aside
with
with
those
open
source
solutions
in
our
paper
next,
so
how
to
manifest
relates
to
other
sins
and
projects.
L
The
first
one
is
a,
but
the
most
employees
of
that
is
because
we
use
superfast
to
support
our
container
platform
in
internally
in
jb
at
in
student
life
scale,
and
we
also
released
the
help
Scott
as
the
caption
manager.
We
use
the
premises
as
a
default
marking
system
in
the
file
system
and
in
the
future
we
plant
you
to
between
integrative
is
root
as
our
story
on
straighter
four
four
qualities.
Next,
so
here
is
a
list
of
got
the
current
system:
storage
pouches.
We
have
ECC
the
opening,
EBS
hooked,
ITV,
withers
and
long
home.
L
The
new
member
of
the
sandbox,
as
you
can
see,
there's
still
a
missing
piece
of
the
district
file
system
there,
and
we
think
that
that's
why
we
think
that
two
FS
can
be
completed
candidate,
so
we
actually
presented
within
a
more
technical
presentation
to
the
story
see
on
June
12
of
this
year.
There's
lots
of
like
discussions
and
feedbacks
to
the
presentation,
pallet
Alex
point:
there's
no
Houston.
Questions
relate
to
the
project,
but
besides
also
like
a
technical
questions
and
feedbacks
that
you
feedback
suite
variable
feedbacks
that
we
want
you
in
out
the
table.
L
The
first
one
is
on
is
the
score
below
two
buffers,
so
the
Travis
is
a
is
designed
to
for
the
photo
services
and
applications
where
most
of
the
right
suspension.
So,
although
we
support
the
random
rice
butter
in
al-qaeda,
now
facing
including
in
JV,
most
offenses
are
still
like
special
and
the
process
himself
is
not
designed
for
the
case
where
we
switch
restricted,
metadata,
consistency
and
ethnicity
are
the
while
such
as
direct
mail,
which
means
that
the
the
user
does
the
bypass.
L
Those
are
OSL,
okay,
she's
and
just
talk
directly
to
to
the
person
itself
on
this
kind
of
person
performance,
and
these
not
recommend
recommended.
The
second
thing
we
want
to
bring
up
is
the
excessive
intubation
in
being
asked
during
the
presentation.
The
assessing
CSI
integration
needs
to
be
up
to
date.
So
so,
with
all
those
suggestions
and
feedbacks,
we
remove
the
CSI
comment
out
components,
and
then
we
go
in
a
loop
people,
fight
for
the
product
for
the
holidays
of
the
sensor
driver.
L
We
also
submit
out
PR
PR
to
the
to
to
the
community
for
the
photo
reviews
next.
So
the
last
slide
I
want
to
talk
about
wise.
Why
why
sales
have
sandbox?
So
there
are
three
reasons:
the
first
one
is
the
neutral
home
I'll
create.
We
will
character
by
entering
the
sandbox.
We
all
have
a
clear
like
caverns,
and
this
is
a
safe
place
to
eat,
or
those
are
problems
with
with
others,
and
the
second
second
reason
is
the
element
with
with
the
since
admission
based
on
our
company
is
Socratic
strategy.
L
We
we
want
to
get
a
better
public
is
ability.
We
want
to
make
a
comment
about
computing
recruiters.
The
the
last
resistor
is
the
the
proton
itself.
The
Chewbacca's
project
has
a
strong
relationship
with
with
other
sensitive
projects,
because
jellies
colonies,
ecosystem
in
production.
So
we
as
an
user.
We
have
the
experience
all
for
all
for
the
Foxes
myself
and
how
to
put
in
into
production,
and
what
kind
of
like
four
deployments
are
this
to
be
is
to
look.
It
looks
like
in
order
to
support
those
clothing.
L
G
We're
gonna
talk
about
the
operator
framework
today.
I
know
that
we
specifically
had
mentioned
operator
hub
earlier.
It's
kind
of
bundled
in
its
current
format,
so
I'm
gonna
talk
about
all
of
them.
I'm
Rob,
Tomsky
I,
come
from
core
OS
was
one
of
the
very
early
employees
there,
so
I'm
presenting
on
behalf
of
Red
Hat,
but
really
we
built
this
community
for
several
years
now,
I
started
with
corliss,
so
the
operator
framework
is
really
about
a
gap
that
we
see
in
the
cube
ecosystem
around
the
next
wave
of
running
applications.
G
These
you
know
really
advanced
distributed
systems
that
need
active
care
and
lifecycle
management.
This
is
what
we
bootstrap
this
operator
concept
and
it's
been
proliferating
all
over,
which
is
great
next,
so
we
really
see
a
gap
in
building
these
things
running
them,
as
well
as
discovering
capabilities
about
them,
and
the
framework
has
a
number
of
projects
sub
projects
to
address
these
needs.
You
can
all
find
them
on
github
probably
heard
of
most
of
these.
So
you
know
I'll
mention
that
these
slides
I'm
gonna
go
through
really
quickly.
G
I
mostly
want
to
have
a
discussion
today,
but
they're
included.
So
if
you
want
to
reference
them
later
on
next,
so
a
quick
history
of
the
concepts
we
invented.
This
is
pretty
early
in
the
cube
ecosystem
in
2016,
with
a
few
bootstrapped
operators
from
coral
s
next
and
then
we
rapidly
progressed
into
a
ton
of
operator
community
building,
along
with
Red
Hat
and
others
that
are
unlocking
kind
of
staple
workloads.
On
kubernetes,
we
have
an
operator
cig
started
under
the
open
shift,
Commons
banner
and
would
love
to
bring
that
into
the
CNC
F.
G
We're
also
involved
in
a
lot
of
the
add-on
discussions
for
kubernetes
and
various
SIG's
cluster
lifecycle.
I
think
that's
since
migrated
to
a
different
sig,
so
we're
kind
of
discussing
things
all
over
the
place
next
and
then,
most
recently,
we
made
a
big
launch
with
operator
hub
I.
Oh,
this
is
a
place
to
discover
these
operators,
most
importantly
addressing
a
gap
where
it's
not
just
popularity,
but
it's.
What
are
the
capabilities
of
these?
How
much
are
these
operators
and
what
exactly
do
they
bring
to
the
table?
G
G
We
have
a
number
of
commercial
products
that
are
delivered
via
operator
number
of
CN
CF,
open
source
projects
that
are
delivered
via
operator,
and
this
is
kind
of
seen
as
the
way
to
bring
this
next
generation
of
workloads
on
in
kubernetes
next
I'm
inferring
this
just
because
I
know
there
was
some
talk
and
chat
of
the
definition
of
an
operator.
This
is
kind
of
our
definition
and
we'd
like
to
continue
to
see
that
evolving
over
time.
That
will
work
with
that
sig.
G
G
The
experts
can
bake
that
knowledge
into
an
operator
next.
So
why
use
the
operator
framework?
We've
really
broken
this
down
into
a
number
of
different
personas.
We
think
that
are
all
equally
important.
We've
got
developers
that
are
want
to
build
an
operator,
and
you
know
don't
want
to
do
all
this
repetitive
scaffolding.
We
can
do
all
that
for
you
and
bacons
and
best
practices.
You've
got
facilities
for
cluster
admins
to
control
which
operators
can
be
installed
on
clusters.
You
know
operators
have
fairly
high
permissions
depending
on
what
they're
doing.
G
That's,
why
they're
so
powerful,
but
there
need
to
be
some
guardrails
in
place,
or
else
you
know
your
cluster
can
run
amuck
and
we
think
you
know
production
use.
Cases
really
need
those
guardrails
and
then
you've
got
the
users
of
your
clusters.
Why
we're
all
here,
while
we're
providing
kubernetes
out
to
our
end
users?
G
So
the
main
tools
that
we
have
for
building
these
operators,
we
think
it's
really
important
to
address
the
entire
spectrum
of
skills
that
folks
have
and
we
want
to
meet
them
in
their
model
of
the
world.
So
to
do
that,
we
have
kind
of
a
no
code
operator
if
you
will,
which
is
building
a
helm
shark
into
an
operator,
and
this
is
a
way
to
get
kind
of
the
human
out
of
the
loop
and
have
a
programmatic
cube
native
interface
to
helm.
Without
using
a
CLI,
we
have
ansible
tools.
G
So
if
you're
more
of
an
Operations
focused
team-
and
you
you
know,
know
how
to
write
ansible
or
have
an
existing
investment
in
Hanceville
playbooks,
you
can
build
those
into
an
operator
and
and
do
a
whole
ton
of
differently
cool
things.
And
then
we've
got
our
go
SDK,
which
builds
on
queue
builder
and
some
other
scenes.
You
have
projects
and
that's
really
the
power
that
you
get
from
all
of
client
go
and
all
that
associated
tooling
and
all
for
all
three
of
these
feed
into
a
testing
framework
which
we
think
is
really
important.
G
This
is
another
gap
that
we
have
where
we
need
to
uplevel
these
operators
so
that
they
are
trusted
by
the
community,
and
we
think
testing
and
validation
is
really
key
to
that,
and
so
we've
got
that
built
into
our
sdk
as
well.
Next,
next
pillar
of
our
framework
is
the
lifecycle
manager.
This
is
a
huge
gap
that
we
see
in
the
ecosystem
so
far,
which
is
you
know
not
just
installing
an
operator
but
managing
it
over
time.
G
You
know
CR
DS
are
cluster
wide
currently,
and
so
you
need
to
have
conflict
with
those
and
if
you
have
operators
that
are
dependent
on
other
CRTs
being
installed
on
the
cluster,
the
lifecycle
manager
has
a
ton
of
dependency,
tooling
involved
to
get
that
done.
So,
if
you
install
like
what
we
call,
you
know
like
a
top
level
operator
that
might
install
you
know
the
from
in
the
caching
layer
in
the
database.
For
example,
all
in
one
go.
B
B
G
Think
this
is
really
key
for
having
a
really
wide
ecosystem
of
operators
that
work
together
and
talk
together.
Next
and
lastly,
I
mentioned
this
earlier-
we've
got
operator
hub
bio.
This
goes
more
past
kind
of
just
popularity
into
actually
looking
at
those
dependencies
that
we
were
talking
about.
Looking
at
the
maturity
and
the
capability
model
that
we
have
that
I
shared
in
chat
earlier,
it's
a
recognition
that
we
want
these
operators
to
be
trusted,
and
you
know
when
they're
running
your
storage
in
your
production,
databases
and
your
important
ecommerce
applications.
G
G
That's
really
quick,
like
I
said
the
10,000
SDK
clones
I
think
you
know
shows
a
ton
of
people
are
using
this.
We've
got.
You
know,
600
folks,
on
our
signaling
list,
and
so
that
that
shows
you
that
there's
a
gap
in
knowledge
here
and
so
we've
got
a
community.
That's
built
up,
sharing
best
practices.
Talking
about
the
next
operator
frameworks
that
we
want
for,
like
a
Java
SDK,
for
example,
so
we've.
G
Engagement
there
we've
got
207
combines
contributors
to
all
of
our
sub
projects
and
a
ton
of
different
unique
organizations
contributing
as
well.
So
we
think
this
is
a
really
vibrant,
healthy
ecosystem.
Next,
here's
just
a
quick
sampling
of
tweets.
You
know
these
come
in
all
the
time,
but
folks
are
seeing
that
the
SDK
is
a
really
easy
way
to
jump
into
this
and
then
other
projects
that
come
afterwards,
like
the
lifecycle
manager
and
operator
hub,
speak
against.
G
You
know
the
different
steps
that
you're
gonna
have,
after
you
start
building
an
operator,
so
we've
got
folks
like
I,
said:
building
commercial
products.
We've
got
really
healthy.
Open-Source
ecosystems
using
these
as
well
as
just
you
know,
regular
end
users,
building
prototypes
and
things
like
that.
Next
I
think
the
most
powerful
kind
of
endorsement
of
an
operator
we've
seen
a
handful
of
these
quotes.
I
just
pulled
off
one
of
them
from
coop
Connie
you
earlier
this
year.
G
Basically,
if
you're
gonna
run,
you
know
a
complex
distributed
system
in
this
case
like
a
staple
storage
and
the
advice
is
really
you
have
to
build
an
operator
to
do
this.
You
need
something
actively
looking
after
something
rebalancing:
data
reacting
to
monitoring
alerts,
doing
anomaly
detection.
These
are
things
that
kind
of
live
that
one
level
above
where
our
queue
resources
are
today.
G
You
know
a
stateful
set,
isn't
gonna
get
you
all
the
way
there,
and
so
we
think
this
is
that's
the
huge
gap
that
operators
fulfilled
in
our
ecosystem
next,
so
here's
a
bunch
of
our
NASCAR
logo
slide
a
bunch
of
these
are
seen.
So
you
have
projects
as
well
as
open
source
communities,
commercial
entities,
we've
got
the
logos
on
the
bottom
of
this
slide
are
companies
that
are
building
internal
operators.
These
are
the
ones
that
at
least
publicly
talked
about
that.
G
We
know
that
there's
a
lot
more
doing
it
and
I
think
that's
the
power
of
you
know:
they're,
building
internal
applications
to
talk
to
these
open-source
operators
and
really
fostering
that
ecosystem
and
all
the
interconnections
there
and
as
we
build
out
more
and
more
of
this
I
think
we're
going
to
see
this
start
to
explode
even
more
than
it
has
today
next.
So
this
is
the
meat
of
it
that
I
really
want
to
talk
about.
G
G
I
wanted
to
address
some
as
we
presented
to
us
a
gap.
Delivery
I
forget
when
it
was
about
a
month
or
two
ago,
and
here's
a
quick
highlight
at
some
of
the
feedback
that
we
got
via
ad
some
emails
and
the
chat
during
the
discussion
before
tchen.
We
ran
out
of
time
that
meeting
so
there
wasn't
a
lot
of
kind
of
live
for
us
to
voice
chat,
but
this
is
a
summary
of
some
of
our
PR
conversations
and
stuff
around
community
governance.
G
So
we
got
a
ton
of
feedback
on
that,
so
we
have
opened
some
PRS
and
some
talks
about
our
community
involvement
in
some
of
those
regular
scheduled
meetings.
It'll,
you
know
very
much
looks
like
any
other
CN
CF
project.
We
don't
want
a
lot
of
stuff
around
packaging
formats
like
did.
We
need
a
new
packaging
format.
Basically
are.
The
short
of
this
is
we're
not
super
init.
Under
this
you
know
there
was
like.
Oh,
is,
is
helmut
packaging
format.
G
We
think
the
lifecycle
manager
and
some
of
the
the
stuff
that's
included
in
that
specification,
go
beyond
just
packaging.
It's
all
about.
You
know
reacting
in
Diane,
dynamic
environments,
registering
those
CR
DS
dependency
model.
How
do
I
enough
valid
upgrade
pass
between
operators
that
are
way
more
powerful
than
just
like
you
know.
The
packaging
format
so
I
think
there's
still
some
discussion
to
go
there,
but
I
think
we
bring
a
lot
to
the
table.
Like
you
know,
late,
binding
of
operators.
It's
there
it's
done
and
said
that
managing
CR
DS
was
another
topic.
G
You
know
question
can
helm.
Do
this,
the
the
important
part
is
not
just
you
know
the
here's.
The
CR
DM
will
go,
throw
it
into
the
cluster.
It's
the
dependency
management,
it's
the
recognition
that
these
are
cluster
wide
and
they
need
to
be.
You
know
it's
a
privileged
operation
to
install
one
of
those,
and
so
it's
it's
a
really
key
thing
that
we
think
the
framework
does
well
and
the
lifecycle
manager
that's
not
addressed
currently
today
and
as
of
now
I
think
the
helm,
3
community
is
saying
that
see.
G
Rd
management
is
currently
out
of
scope,
doesn't
mean
it
won't
be
in
scope
later
on.
So
just
wanted
to
summarize
that
discussion
you
can
follow
those
links
for
more
and
then
last
I
know
there
was
some
mention
of
Kudo
and
other
SDKs,
and
so
we've
been
had
a
great
cube
con
discussion,
but
the
Kudo
team
I
think
there's
a
path
forward.
It
seems
like
it
makes
a
lot
of
sense
for
Kudo
to
come
in
the
operator
framework
as
a
fourth
type
of
operator
and
so
I
think
we've
got
alignment
on
both
sides
for
that.
G
So
we're
really
excited
about
that.
Like
I
said,
we've
been
discussing
kind
of
all
over
the
place
in
different
SIG's
and
hope
to
continue
to
do
that
as
well.
I
think
that
is
all
that
I
had
on
this.
If
you
can
go
to
the
next
slide,
I
think
it
would
you
say,
questions
oh,
never
mind.
One
more
slide
who's
the
biggest
list
of
some
of
the
other
scenes
to
have
projects
that
we've
got.
G
F
So
so,
there's
a
few
things
about
helm,
one
is
with
CRD
management
and-
and
this
actually
gets
complicated,
I
know
that
the
operator
lifecycle
manager
makes
a
number
of
assumptions,
but
as
I
poke
around
the
kubernetes
community,
there
is
no
one
way
to
do.
Crts
and
so
helm
wants
to
provide
a
bunch
of
the
features.
But
the
problem
has
to
do
with
coming
up
with
what
are
the
right
ways
and
the
right
patterns
and
I
know
the
operator.
F
Lifecycle
manager
makes
a
number
of
assumptions
and
that
shuts
out
other
cases
and
it
becomes
a
problem
of
aligning
around
CRTs
and
that's
really
something
that
the
kubernetes
community
needs
to
do
and
so
helm
wants
to
and
has
certain
features
around
CRT
management.
In
fact,
many
people
do
install
operators
with
helm
today
and
and
CRTs
and
everything
at
all,
and
so
I
think.
This
is
something
that
the
kubernetes
community
probably
needs
to
come
together
around.
F
But
it's
not
the
case
that
helm
doesn't
want
to
it's
the
case
that
home
isn't
trying
to
shut
out
certain
assumptions
and
cases,
and
so
we're
conservative
in
what
we
do
with
CR
DS.
Until
we're
able
to
solve
from
any
of
the
cases
out
there
and
I
understand
the
operator,
lifecycle
manager
makes
more
assumptions
even
those
beyond
what
the
kubernetes
community
is
doing.
Right
now
and
I
think
that's
kind
of
the
difference.
F
But
during
the
helm,
3
life
cycle,
we
will
be
adding
more
CRT
features
and
there
are
security
features
in
helm
to
me,
people
do
deploy,
operators
with
helm
and,
and
so
that
even
gets
into
some
of
the
operator
hub
stuff.
I
know.
There's
the
testing
framework
and
I
think
that
requires
the
operator
lifecycle
managers,
all
right,
Foam.
G
E
G
F
But
doesn't
that
make
the
operator
lifecycle
manager
a
hard
dependency
on
an
operator
being
listed
in
the
operator
hub,
so
somebody
could
go,
maybe
write
one
and
rust
and
deliver
it
with
a
helmet
art,
but
it
couldn't
be
listed
in
the
operator
hub
in
the
current
flow
because
it
wouldn't
fit
with
the
current
testing
framework
and
dependencies.
Is
that
right,
yeah
today
that
is
correct
or
is
there
any
road
map
around
opening
it
up
to
operators,
written
and
deployed
and
managed
and
other
methodologies?
So.
G
The
road
map
has
kind
of
been
contingent
on
some
of
these
discussions.
I
think
we're
very
much
open
to
that,
and
we've
got
some
changes
underneath
the
hood,
what
we
call
our
bundle
format,
which
is
a
little
probably
too
low-level
for
this
discussion,
but
that
would
open
up
you
know,
being
able
to
package
things
as
helm,
charts
and
coming
at
kind
of
getting
rid
of
some
of
those
dependencies,
but
I
think
it's
basically
up
to
you.
F
G
G
B
I
appreciate
the
questions.
Matt
I
think
it's
important
that
you
know
we're
completely
transparent
and
that's
what
we
want
out
of
this
process,
and
you
know
we
definitely
want
to
be
able
to
support.
You
know
as
many
formats
as
we
can,
but
to
have
a
way
that
we
can
properly
test
it
as
well,
so
I
mean.
Hence
that's
the
reason
for
the
framework.
I
think
you
can
appreciate
that.
So
you
know
feedback
is
definitely
welcome.
Yes,.
F
D
G
Honestly,
the
it
runs
on
an
open
ship
cluster
today
and
it's
actually
a
fairly
small
one,
there's
not
a
ton
of
resource
requirements.
There
we've
got
some,
you
know,
Jenkins
jobs
that
are
kicked
off,
I,
don't
know
exactly
what
the
costs
of
that
is
today,
but
I.
It's
not
an
astronomical
by
any
means.
D
Yeah,
it
will
be
great
to
get
this
because,
obviously,
eventually,
if
it's
adopted
by
the
CNC
I,
have
to
see,
if
should
be
able,
then
to
run
this
the
hub
as
well-
and
you
mentioned
it's
running
on
open
ship.
So
does
it
have
a
heart
dependency
and
open
shift,
or
would
it
work
on
any
kubernetes
cluster
yeah.
G
B
E
E
I
Had
one
little
announcement,
I
just
sent
a
note
up
to
the
TOC
list:
I
abandoned
did
a
great
flowchart
earlier
this
summer
about
project
process.
There's
been
a
lot
of
questions
and
confusions
about
that.
So
I
made
a
barked
out
version
of
that
which
is
pull
off.
Pr
3:21
I,
set
out
on
the
mailing
list
would
love
some
feedback
I'm,
just
we're
trying
to
scribe
what
is
the
intended
process.
So
you
have
no
attachment
to
the
boxes
and
arrows
they're
just
what
to
help
drive
it
to
documentation.