►
From YouTube: CNCF SIG App Delivery 2020-03-18
Description
CNCF SIG App Delivery 2020-03-18
A
B
B
C
D
B
B
E
E
E
E
All
right,
so
it
is
March,
eighteenth
2020,
and
this
is
the
CNCs,
a
gap
delivery
by
weekly
meeting
just
a
little
bit
of
a
reminder.
This
is
recorded
and
it
is
public,
do
not
say
anything
that
you
don't
want
to
be
judged
about
later,
all
right,
so
we
actually
do
not
have
a
large
agenda
today,
but
I
would
like
to
welcome
any
new
members.
Anyone
wants
to
introduce
themselves.
G
Let
me
start
if
you
want
so
my
name
is
fran
mendez.
I
am
the
founder
of
the
async
api
specification
and
a
syncopated
not
sure
if
you've
heard
about
it
but-
and
I
was
joining
here
today,
sister
is
to
familiarize
on
how
you
guys
work
I'm
happy
to
help
on
anything
that
that
you
might
need
and
yeah.
It
will
see
me
very
often,
I
guess.
H
Yes,
the
table
and
probably
donate
so
Michonne,
come
from
ready,
Thank
You
luma
for
helping
out
us
into
organizing
Oktoberfest
at
Delhi.
They
came
in
and
gave
a
really
good
session
on
redness
I've
been
following
the
thickness
since
then.
C
E
D
C
I
I
I
E
A
A
E
F
F
Right,
you
could
see
mr.
Cola
yeah
I
just
wanted
to
give
a
little
bit
of
background
on
this
project
and
where
we
are
with
the
process.
Last
meeting
I
checked
here
and
this
IDI
followed
a
new
sandbox
proposal,
a
process
and
then
create
an
issue
and
a
PR.
So
we
did
create
an
issue
first
and
then
this
is
the
issue
in
T.
Was
the
issues
and
then
Amy
asked
me
to
create
appear
as
well,
so
we
create
a
PR
in
crisis.
It
just
said
we
should
do
a
review
right
this
sake,
so
I'm
here.
F
Thank
you
for
taking
your
time
to
listen
to
this
presentation.
So
what
I'm
trying
to
do
here
is
I
did
present
to
this
group
back
in
October,
a
very
gentle
introduction
of
the
project
when
it
was
newly
formed,
but
now
I
have
a
little
bit
more
detailed
presentation
as
well
details
required
in
the
process.
F
One
question:
even
before
I
start
doing
this
is
we
present
and
I
know
it's
going
to
be
recorded
and
then
would
there
be?
What
would
be
the
next
step
in
general?
What
that
he
was,
he
I
should
go
and
present
to
the
TOC,
or
do
we
wait
for
few
more
meetings
to
happen
in
general,
I'm
and
just
wandering
right?
Yes,.
E
So
what
will
happen
is
after
this
we'll
take
this
conversation
offline,
but
this
is
for
for
sandbox,
so
we
will.
We
will
actually,
we
will
contact
you.
There
is
a
little
questionnaire
that
we
like
people
to
fill
out
and
and
we'll
get
that
to
you
whom
I
sure,
let
you
what
I'll
do
is
get
your
email
and
and
then
we'll
get
it
started
from
there
all
right,
perfect.
F
Thank
you
Brian.
So
with
that,
let
me
start
so
litmus
chaos.
The
project
itself
is
to
provide
an
infrastructure
to
do
cloud
native
chaos.
Engineering
I'll,
just
talk
about
in
a
bit
word
is
cloud
native
chaos,
engineering.
So
a
bit
of
background
and
history
is
this
project.
Was
you
know
it's
not
new,
it's
being
there,
but
almost
wound.
Up
years
now
we
announced
it
in
2018.
F
Cube
Khan
has
open
source
project
for
kubernetes,
and
since
then
it's
been
majorly
sponsored
by
my
data,
but
recently
we
seeing
more
windows
contributing
to
it
and
that's
one
of
the
reasons
why
we'd
want
to
present
here
right
and
originally
as
a
Kaos
engineering,
well
Carlton
ideas.
Kieran's
Nicole
is
the
code
maintainer
of
the
project.
We
were
trying
to
do
chaos,
engineering,
core,
open
ideas
and
we
did
not
really
see
a
proper
tool
that
is
freely
native
and
we
started
writing
it
on
our
own
then
so
on.
F
F
Chaos
has
been
continuously
being
used
for
the
various
negative
chaos
testing
for
open,
BS,
dot
c.
I
platform
it's
well
cooked
and
a
lot
of
feedback.
That's
there
is
coming,
and
sometime
around
last
year,
made
the
Ruhr
feedback
that
it's
not
really
easy
to
use
litmus.
You
have
to
know
ansible
and
in
the
regular
stuff.
So
what
the
community
and
the
team?
F
What
we
did
is,
let's
actually
create
chaos,
Quixote's
and
create
application-specific
chaos,
charts
similar
to
help
charts,
and
then
we
start
putting
them
on
chaos
hub,
and
then
we
really
saw
a
lot
of
other
community
members,
picking
it
and
using
it
for
their
own
applications
and
thats.
That's
really
the
start
of
the
community
growth,
I
would
say,
and
then
right
now
we
have
full-fledged
charts
for
kubernetes
and
open
EBS
and
decent
charts
for
code,
eNOS,
Kafka
and
then
a
lot
more
or
coming
and
in
terms
of
the
project
status.
F
F
It's
not
like
super
specific
to
let
months
alone,
but
in
general,
were
in
need
and
to
do
chaos,
engineering
in
a
kubernetes
native
way
or,
however,
we
do
for
other
applications
and
then
once
the
project
has
received
recent
design,
progress
and
also
chaos
suppose
ready.
We
present
adhere
to
the
delivery
sake
or
in
sometime
in
October,
and
then
we
really
saw
more
charts
coming
in
and
we
also
had
the
intention
to
provide
lateness
as
a
chaos
stage
for
CNC
of
CI
itself.
So
we
did
present
into
that
work
group.
F
The
CI
web
group
of
scenes
here
earlier
this
year
and
we
also
now
have
created
one
of
the
team
members.
It
must
created
a
PR
to
introduce
the
chaos
stage
into
Cody
Ennis
pipeline
and
once
we
go
through
that
there
will
be
definite
progress
towards
doing
the
same
for
other
projects
in
Cincy
FCI.
So
we've
been
here
and
then
of
course,
last
week
we
were
here
as
well
and
just
to
talk
about
that
and
looking
at
our
community,
the
community
is
reasonably
big.
F
I
would
say
we
caught
a,
but
it's
thirty
stores
and
we've
been
contributing
in
October
fest.
So
there
were
a
lot
of
small
contributions
that
received
from
all
over
the
world,
but
measurably
I
would
say
there
are
about
forty
to
fifty
contributors,
and
many
of
the
contributors
are
coming
from
the
following
companies
with
Pro
Intuit
and
as
my
data,
the
primary
sponsors,
and
we
have
hopefully
committed
him
about
10
plus
people
contributing
to
litmus
and
then
we've
been
running
from
the
experience
of
running
opening.
F
Are
quite
good
conversations
that
happen
there
and
that's
a
website
and
Twitter
is
reasonably
active
and
in
terms
of
primary
users,
I
will,
instead
of
you,
well
called
legal
clearance
from
their
side
to
say
that
they
are
using
litmus
publicly
have
a
problem
or
to
other
companies.
In
my
rate,
of
course,
we
have
our
commercial
products
where
we
use
litmus
for
chaos,
testing
and
then,
of
course,
open
ideas,
which
is
a
senior
project
which
is
using
litmus
and
the
genesis
of
litmus
is
really
a
Twitter
towards
open
EPS.
F
Then
I
have
two
other
very
big
companies
that
are
using
litmus
for
their
general
needs.
They're
also
part
of
the
skin
CFO
ecosystem,
but
I
would
need
to
wait
for
their
approval
to
display,
but
I'm
pretty
excited
about
their
contributions
to
the
community
going
forward
and
in
general
to
the
litmus
chaos
project
with
that.
I
would
want
to
really
give
a
top-level
feature
list,
primarily
what
litmus
chaos
is.
It's
an
infrastructure.
F
It's
not
just
about
a
few
ways
to
inject
chaos,
but
in
order
to
do
chaos,
engineering,
you
need
a
lot
of
things.
You
need
to
primarily
do
it
through
the
regular
and
proven
their
warps
practices
way
through
the
tops
right.
So
you
need
to
have
a
well-defined
series
and
you
need
to
know
you
need
to
have
a
chaos
operator
and
then
application-specific
chaos,
experiments
and
that's
what
it
is
and
then
to
do
chaos,
engineering.
F
You
also
need
to
have
very
good
monitoring
and
being
able
to
schedule
this
chaos
in
a
way
that
falls
in
into
your
CD
or
practices
of
DevOps.
So
you
need
a
chaos
scheduler,
so
those
are
also
in
progress.
So,
as
you
can
see,
it
is
actually
a
real
infrastructure
for
chaos,
engineering
and
parts
of
them
or
chaos,
experiments,
and
we
are
actually
very
proud
to
say
that
we
have
a
hub,
very
similar
to
operator
hub
or
C&C
of
how
that's
coming
up
where
we
pull
together.
The
chaos
experiments.
F
The
whole
idea,
which
I'll
talk
it
and
the
presentation
is
the
whole
idea-
is
to
have
readily
available
chaos,
experiments
for
all
the
applications
or
most
of
the
applications
on
kubernetes
environment.
That's
probably
why
I
think
we
are
very
much
applicable
for
this
group,
because
you
name
an
application
and
you
need
to
deliver
that
onto
your
CD
or
in
our
grades.
Delivery.
F
You
need
to
have
chaos.
Engineering
is
part
of
the
process,
so
you
could
use
like
mask
for
that,
and
then
we
are
proud
to
say
that
we
have
about
12
experiments,
including
the
one
that
went
out
today
or
couple
of
days
ago.
It's
a
fully
featured
chaos
experiment
for
native
kubernetes.
You
could
almost
indeed
inject
chaos
into
any
of
the
kubernetes
resources
and
there
are
a
lot
of
applications
specifically
as
experience,
for
example,
open,
EBS,
cadenas
and
and
more
and
the
other
major
feature
is
as
part
of
the
design
goal.
F
We
did
not
want
to
be
the
monopoly
in
a
way
you
to
chaos,
so,
for
example,
this
is
how
you
kill
a
part.
This
is
how
you
kill
an
old,
so
we
didn't
want
to
explicitly
say
that
use
it
much
and
do
it
this
way.
Rather,
we
wanted
to
give
it
as
application,
pluggable
chaos
or,
if
you
know,
a
way
to
kill
a
particular
resource
and
you
have
been
using
it
and
you
just
need
a
chaos
engineering
infrastructure
to
do
your
chaos,
you
can
use
it
much.
F
That
means
the
chaos
should
be
a
pluggable
into
this
infrastructure
and
we
have
well-defined
examples
here.
Example:
Pumbaa
is
reasonably
known
for
injecting
Network
latencies
and
we
wrapped
up
Pumbaa
as
a
plugin
into
lateness
and
powerful
shield
is
another
well-known
chaos
framework
by
Bloomberg
and
it's
been
integrated
into
lateness
and
chaos.
Tollgate
one
of
I
think
it's
recently
merged
into
lateness.
F
Where
include
was
using
careful
kid
for
about
a
year
and
they
found
litmus
as
one
of
good
ways
to
inject
chaos
in
a
cloud
native
aid,
so
they
put
a
wrapper
on
top
of
it
by
using
all
plugins
and
then
now
they're,
using
a
litmus
and
in
fact
now
they're
one
of
the
core
maintenance
of
the
project
itself.
So
this
is
really
the
summary
of
it.
F
Applicate,
plug
ability
hub
and
a
very
generic
operator
based
framework
domain
is
the
life
cycle
of
chaos
itself,
and
let
me
talk
about
the
architecture
itself,
so
the
architecture
here
I
just
want
to
simplify
a
little
bit
so
the
install
time
you
have
a
chaos
operator
and
an
exporter
scheduler
to
do
the
basic
job
of
chaos
lifecycle,
as
well
as
to
monitor
what
exactly
is
happening
and
then
scheduler
to
actually
schedule.
Chaos
require
interval.
F
So
these
are
the
chaos
components
and
primarily
we
install
some
chaos,
schemas
the
CRTs
and
then
the
actual
experiments
will
be
listed
on
a
half
just
like
a
column
chart
and
you
can
pull
in
right
now.
We
have
about
20-25
experiments,
but
we
expect
this
to
go
into
hundreds,
so
you
need
not
to
want
all
those
applications,
the
custom
resources
all
the
time,
so
you
can
pull
whenever
you
want
and
at
the
runtime
you
use
one
all
this
CR
and
the
CR
gates
is
being
watched
by
the
operator
and
the
controller
and
a
chaos.
F
Runner
is
started.
Chaos
runner
through
a
chaos
library
will
actually
inject
chaos
into
a
given
kubernetes
resource.
So
it's
a
loosely
coupled
well-defined
chaos
framework,
but
it
does
the
job
of
end-to-end
chaos,
engineering,
and
this
is
at
a
very
high
level,
and
why
do
we
call
as
littmus
chaos
and
cloud
native
right?
That's
because
the
entire
chaos
management
happens
through
an
operative.
We
are
using
the
operator
framework,
that's
reasonably
popular
I
would
say,
but
it
can
be
rewritten
using
the
other
operator
frameworks
as
well.
F
But
it
has
got
a
complete
lifecycle,
manageability
right
now
and
then
the
entire
chaos
can
be
managed
through
declarative
amell's.
So
you
can
use
your
existing
key
tops
model
and
DevOps
infrastructure
and
inject
chaos,
and
actually
do
it
as
a
process
through
all
the
declarative,
AML's
and
then
the
chaos
runner,
which
is
the
job
that
manages
chaos
when
it
is
in
the
process
of
injecting
chaos
itself,
runs
in
a
container
and
can
survive.
Note
reboots
right
one
of
the
reasons
or
the
definitions
of
cloud
native
is:
it
should
be
highly
scalable
highly
available.
So
what?
F
If
the
guy
who's,
injecting
chaos
that
node
itself
goes
down
and
what
happens
to
the
management
of
the
chaos?
So
because
it
turns
in
a
container
and
being
orchestrated
by
the
operator
and
kubernetes
in
general,
it
survives
node
reboots
and
then
the
chaos
management
continues.
So
that's
why
it's
cloud
native
and
the
other
one
is
plug
ability.
The
entire
cloud
native
ecosystem
can
use
this
infrastructure,
not
necessarily
lateness
core
libraries.
F
So
you
can
examples
that
I
talked
about
all
pumbaa
or
cool
sale
and
chaos
tollgate.
Any
chaos
logic
that
you
have
if
it
is
in
the
form
of
a
docker
image,
you
can
actually
put
it
into
the
litmus
framework.
So
that's
why
we
think,
or
it's
completely
cloud
native
and
how
can
litmus
chaos.
This
is
one
of
the
other
questions
that
that
was
asked
in
in
the
proposal,
but
the
sandbox.
How
do
you
think
your
project
can
be
used
by
other
ciencia
projects?
F
Well,
let
Mascaro
itself
is
a
communities
app
and
it
provides
as
I
described
in
the
previous
slides,
well-defined
I
am
all
declarative
IPS.
So
all
you
need
to
do
is
use
this
your
chaos
engine
and
define
your
experiments,
so
any
project
that
is
on
running
on
kubernetes
can
use
a
litmus
for
their
own
chaos
engine.
So
it's
actually
very
easy
fit
and
well
perfect
fit
about
same
so
now.
Next
I
want
to
talk
about
developer
experience
with
that
much
as
well
as
the
sre
or
admin
experience,
so
for
how
to
use
litmus
chaos.
F
So,
for
example,
the
quality
or
resilience
of
your
application
is
also
dependent
on
the
quality
and
resilience
of
these
micro
services,
which
are
being
managed
by
somebody
else,
but
you're
100%
dependent
on
that.
So
what
you
do
in
general
to
build
the
resiliency
or
the
quality
guidelines
you
build
a
pipeline
and
functional.
It's
it's
up
to
the
developer,
but
we
are
not
talking
about
chaos
or
negative
testing
right.
So
you
need
to
include
negative
scenarios
for
your
application.
F
It
need
not
be
about
your
application
or
your
services
alone,
but
it
may
be
something
that
hey
my
SQL
goes
down.
How
does
my
application
behave
so
you
need
to
actually
kill
my
SQL,
which
is
the
database
underneath
and
then
see
how
how
it
behaves
your
application
behaves.
So
you
need
to
have
a
lot
of
ways
or
experiments
to
inject
chaos
into
the
other
applications,
and
that's
where
chaos
hub
comes
into
the
picture.
F
We
need
not
write
this
ones
they're
already
available,
so
we
just
select
them
and
pull
them
in
and
they
are
available
into
your
pipeline
and
then
the
results
are
already
available
and,
of
course,
for
you,
whatever
the
application
that
you
are,
writing
application
specific
chaos
of
your
application.
You
need
to
write
so
you
develop
them
and
then,
as
a
good
Samaritan,
you
can
actually
push
those
chaos
experiments
back
on
to
the
hub.
So
what
happens
is
once
you
build
this
CA
pipelines
all
done.
Your
product
is
reliable.
F
Now
you
think,
and
then
you
ship
it
out
and
the
users
now
have
a
way
to
test
resiliency
of
your
application
and
it
could
be
another
developer.
Who
is
using
your
application
as
a
part
of
the
green
box
here
or
it
could
be
this
re?
That
is
using
your
application,
so
they
could
use
the
test
that
you
developed
during
your
development.
F
They
could
use
the
scales
test
in
production.
They
turn
to
do
chaos
engineering.
So
that's
the
idea
of
bringing
the
developers
and
SRS
together
and
work
them
in
tandem
in
an
open
way.
No
covenant
is
not
a
way
to
do
chaos,
engineering
and
increase
the
reliability
or
the
entire
delivery
of
the
application
into
productions.
F
So
what
about
a
sari
sari?
It's
actually
pretty
simple.
We
expect
when
chaos
happens
well,
develop.
You
will
have
chaos,
experiments
for
most
of
the
applications,
so
you
have
all
those
suffocation
experiments
out
there
in
the
hub.
You
just
need
to
pull
those
yachts
and
to
those
CRS
and
schedule
the
chaos
engine
see
arts
so
that
the
chaos
experiments
were
run
and
you
observe
the
resiliency
matrix
you
take
appropriate
decision
came
fro
the
resiliency
accumulation
of
your
application
of
the
cluster
or
the
hardware
or
whatever
right,
so
it
becomes
almost
like
from
a
challenging
experiment.
F
This
experiment
with
this
infrastructure
and
aha.
So
what
is
this
chaos
hub?
How
does
it
look?
So
let
me
show
you
that
so
chaos
hub
this
itself
was
I
mean
we
thought
this
is
a
fork
or
operator
hub,
because
it's
open
source
and
Apache
tube.
So
we
have
about
eleven
experiments
or
kubernetes
resources.
F
These
are
the
charts
or
experiments
that
you
can
use.
You
can
almost
kill
any
type
of
you
can
inject
any
type
of
chaos
that
you
need
and
memory
hog.
Cpu
hog
are
the
recent
ones
that
that
we
have
introduced
and,
for
example,
for
network
latency,
underneath
we
use
Pumbaa
right
some
other
chaos,
library
and
using
the
pluggable
mechanism.
F
F
So
when
you
kill
something,
the
application
is
pack
up
and
leave
must
generates
kubernetes
events
for
every
chaos
option.
Action
is
very
important
to
know
what
happened
and
who's
telling.
What
and
type
of
thing
so
I'll
be
looking
at
kubernetes
events
while
I
do
this
killing.
Let
me
just
go
back
so
I
have
a
wordpress
application.
Let
me
refresh
its
slide
and
and
I
have
pods
namespace
called
sec
demo
and
I
have
WordPress
running
and
MySQL
in
WordPress
they're
a
single
pod
with
the
two
containers
in
it.
F
F
Okay-
and
let
me
see
if
the
Sierras
are
installed,
yes,
they
are,
and
let
me
see
what
are
the
pods
running.
You
have
the
operator
and
it's
very
much.
You
know
us
and
now
I'm
going
to
pull
some
experiments
on
to
this
cluster,
so
I
pulled
the
genetic
chart.
So
I
got
a
lot
of
experiments
into
this,
and
let
me
see
what
are
the
COS
that
are
installed
right
is
now
installed.
So
next
is
security
and
I
have
an
hour
back
policies
that
are
setup
quality
into
this
ml
file.
F
It
basically
says
that
a
given
person
has
access
to
inject
chaos,
so
I'm
going
to
apply
in
this
our
backs
and
primarily
before
injecting
chaos.
I
just
want
to
show
you
what
is
to
inject
chaos.
You
need
to
create
chaos,
engine
CR
and
the
spec
releases
that
which
is
the
app
and
which
namespace
and
some
annotations,
and
then
what
are
the
experiments
that
you
are
going
to
do
so
I'm
going
to
do
a
pod
delete
of
an
application
who's,
a
playable
is
given
above
and
then
I'm
going
to
do
a
total
of
10.
Second
chaos.
F
At
the
end,
we
look
10
seconds.
That
means
one
time.
I
am
going
to
do
a
fourth
tail,
so
with
that
I'm
actually
going
to
inject
chaos,
so
once
I
do
that
as
you
can
you
can
see
that
in
that
namespace
the
chaos
container
will
come
up
and
start
chaos?
Runner
is
now
running.
You
can
see
that
there's
an
event
that
said
things
are
happening
here
within
regulated
to
chaos
and
then
the
actual
chaos
that
arose
experiment
portal,
a
itself
is
running
inside
a
container
and
that's
what
I
meant
by
cognitive
in
about
30-40
seconds.
F
F
Yeah
so
it
went
down,
but
we
expect
it
to
come
back
and
the
entire
state
full
application
and
then
the
stateless
application
recovery
happens.
Containers
are
still
fully
not
done.
As
you
can
see.
That
lateness
is
really
waiting.
Is
it's
not
just
a
job
of
injecting
chaos
but
also
the
job
of
making
sure
that
what
is
the
resiliency
of
the
application
and
I
know
once
the
pot
is
up,
I
need
to
wait
for
the
service
to
be
available
in
etc.
F
So,
as
you
can
see
that
because
WordPress
is
looking
for
database,
it's
continuously
going
for
crashing
and
littmus
is
really
waiting
for
it
to
come
back
and
doctor
sometime,
it
doesn't
come
back.
Then
there
is
a
problem
with
your
application,
so
it
will
exit
the
threshold
and
say
that
there
is
a
problem
with
your
application.
If
the
pot
goes
down,
your
application
is
totally
going
down
so
in
about
10
to
15
seconds
it
should
recover.
If
not,
it
must
will
say
that
the
application
has
an
issue
or
the
experiment
has
failed.
F
So
while
we
wait
for
it,
I
think
it's
come
back
up
and
you
will
see
that
the
post
check
of
litmus
says
that
everything
worked
well
and
AUD
is
running
successfully
and
we
are
now
going
to
delete
and
the
chaos
whatever
we
introduce
new
resources.
Everything
is
done
and
back
to
normal
right
and
let
me
show
the
result
as
well.
Yeah
result
is
another
beautiful
thing.
It's
also
CR
and
you
can
use
this
to
collect
from
Matthias
matrix
and
doing
other
source
of
kubernetes
stuff.
F
F
So
that's
the
demo
part
and
just
to
summarize
in
this
few
minutes,
I'm
able
to
actually
define
my
test
and
pull
the
test
case
and
run
it
right
all
in
this
live
demo.
So
it's
very
easy
to
install
once
you
install
you
get
the
operator
libraries,
you
pull
the
charts
and
you
create
those
here
and
to
inject
chaos,
and
then
that
runs
the
chaos
inside
a
container
in
a
cloud
native
way
and
then
the
result
is
this
AR
and
then
you
can
use
it.
So
that's
that's
about
it.
F
That's
how
simple
it
has
become
from
being
very,
very
complex
process
of
chaos
and
shading.
So
what
do
we
think
this
project
should
be
governed
by
C
in
C
F,
or
why
do
we
want
to
donate
this?
Well,
the
idea
itself
is.
It
should
be
useful
for
a
lot
of
other
projects
and
that's
why
we
open
sourced
rate
and
we
architected
in
a
way
that
kubernetes
applications
can
easily
use
it
and
most
of
the
kubernetes
application,
also
resiliency
of
applications
or
projects
or
kubernetes
centric.
F
F
Adopted
lists
as
well
were
using
as
big
companies
as
well
as
individual
users,
and
we
also
have
an
84
litmus,
so
it's
well
defined
platform
of
C
sed
to
deliver
this
before
they
actually
goes
out.
It's
based
on
gauge
lab
followed
very
similar
infrastructure
to
that
of
C
in
C
of
CI,
but
it
has
got
a
well-defined
see
a
and
E
to
e
platform
as
well.
So
with
that
I
would
say.
Thank
you
for
giving
us
an
opportunity
to
present
here.
I
am
very
happy
to
considering
it.
The
questions.
E
Alright,
thank
you
mom
up.
So
before
we
get
started,
there
is
two
questions
from
the
chat
and
I'll
read
them
both
and
just
one
keep
this
part
pretty
fairly
short,
but
I
still
want
to
give
a
chance
to
people
ask
questions.
But
what
is
the
distribution
method
for
these
chaos
charts?
Is
it
using
OCI
or
we
should
rope
the
chaos
hub
into
the
discussions
that
we've
been
having
I?
Guess,
there's
another
conversation
going
on
about
hubs,
and
that
was
the
bride.
Was
it
yeah.
F
I
mean
right:
no,
the
hobbit
is
nothing
but
I'm,
because
we
were
not
part
of
cnc
of
hub.
We
created
a
hub
right
and
if
you
want
to
create
a
new
experiment-
and
you
want
to
give
it
out,
you
need
to
create
a
CR
spec
and
then
just
put
it
out
there.
We
expect
this
half
will
be
merged
into
C
and
say
hub.
For
example,
users
come
in
I
need
an
operator
for
my
application,
so
go
get
it
from
the
hub.
F
E
F
F
Yes,
it
is
totally
customisable
already
and
in
fact
there
is
a
value
in
having
already
customized
experiment
in
the
hub.
It's
not
just
about
doing
a
pod
kill.
For
example,
what
I
showed
right
now
in
the
demo
is
I
kill
the
pod
that
belong
to
MySQL,
right,
that
is
kubernetes
generic
and
then
the
post
check
of
the
chaos
experiment
just
generally
went
in
checked:
hey
is
my
MySQL.
F
Pod
came
up
and
running
right,
that's
all
I
could
do,
but
if
you
have
an
application-specific
chaos
experiment
for
MySQL
MySQL
itself,
then
the
post
check
of
that
experiment
will
go
and
talk
the
language
of
the
application
itself
and
that's
again
totally,
you
know
variety.
You
can
actually
go
and
very
various
parameters
and
that's
the
whole
idea
of
creating
the
hub,
where
you
will
have
updated,
Pacific,
Post
checks
and
rechecks
after
you
inject
chaos,
so
that
that
probably
answered
that
question.
If
not
yeah
I
can
take
detailed
questions
on
the
community.