►
From YouTube: /lgtm with Litmus
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
This
is
a
cloud
native
official
live
stream,
part
of
the
cncf
and
as
such,
is
subject
to
the
cncf
code
of
conduct.
So
please
do
not
post
anything
to
the
chat
or
questions
that
would
be
in
violation
of
this
plot
of
conduct,
essentially
just
be
respectful,
be
nice
of
myself
of
my
guest
and
everyone
else
in
the
chat
and
we're
going
to
have
a
good
time.
A
B
A
B
A
Awesome,
thank
you
very
much.
I'm
really
excited
to
have
you
join
us
today.
I
think
litmus
is
such
a
killed
project
and
you
know
there
were
some
massive
news
this
week
with
a
new
release.
Do
you
wanna
well,
first,
actually,
why
don't
you
tell
us
a
little
bit
about
you?
Why
don't
we
learn
about
print
v
and
then
we'll
talk
about
that.
B
B
I
had
a
few
events
here
and
there
kcd
africa
or
bengaluru
and
and
then,
of
course,
in
the
community,
if
you
are
part
of
the
fitness
community
already,
so
you
know
me
as
the
community
manager
for
the
project,
I
started
off
being
a
community
manager
of
this
project,
approximately
one
and
a
half
years
ago
and
at
maya
data,
and
now
I'm
at
chaos
native
working
on
the
project
leading
the
community,
all
the
traction
and
everything
around
it
and
yeah.
It's
been
a
pleasure
alongside
that.
B
Obviously,
in
the
cncf
ecosystem,
I've
been
organizing
chaos,
engineering
meetups
every
last
saturdays
of
the
month,
so
in
case
you
have
ever
joined
in
or
you
look
forward
to
joining.
Then
it's
it's
at
community.cncf.io
the
chaos
engineering
group
and
you
can
join
in
and
learn
a
lot
more
about
chaos
and
litmus
chaos.
So
so
that's
that's
about
me.
A
B
Sure
so,
first
first
I
think
we
can.
We
can
talk
about
the
release,
of
course,
so
litmus
2.0
is
in
ga
right
now
it's
it's
out
there.
We
were
in
beta
for
almost
three
months
and
and
the
idea
behind
beta
was
obviously
getting
community
feedback
community
inputs,
I
mean,
I
think
a
project
is
incomplete
without
the
community.
B
Of
course
I
mean
the
maintainers
and
the
contributors
are
there,
but
it
took
three
months
for
us
to
move
from
beta
to
ga
only
because
there
was
a
lot
of
feedback
that
was
necessary
and
2.0
is
out
now
and
it's
it's
already
receiving
a
lot
of
amazing
feedback,
so
feel
free
to
join
in
the
community.
I
mean
we
will
talk
about
the
community
later
on
the
slack
community,
but
yeah
I
mean
2.0
is
out
there
so
looking
forward
to
for
more
feedback
interviews
and
your
valuable
comments
in
that.
B
A
B
In
indeed,
I
think
the
community
support
has
been
awesome,
siam,
you
yourself,
and
then
there
are
so
many
folks
I
mean,
but
bart
has
been
doing
amazing
job
done,
I
think
yeah,
so
they
they
all
have
been
supportive
to
the
project
and
another
video,
I
think
by
victor
victor
farcich.
Even
he
has
been
doing
an
amazing
job
with
a
devops
toolkit.
So
so
that
is
out
there
talking
about
litmus
2.0
and
argo
workflows
as
well,
so
to
come,
cncf
projects
coming
together
and-
and
that's
that's
awesome.
B
B
B
Yeah
I'll
be
sharing
my
screen,
so
just
give
me
a
second.
A
B
Thanks
thanks
a
lot
so
so,
starting
off
I
mean
people
who
join
in
I
mean
there
have
been
so
many
episodes
talking
about
contributions
to
cncf
projects,
and
I
mean
chaos.
Engineering
is
a
technology
which,
which
was
something
to
look
forward
to
was
mentioned
by
cheryl
or
liz
at
so
many
kubecons
that
have
been
coming
up
that
chaos.
Engineering
is
a
technology,
look
to
look
forward
to,
and
I
mean
cloud
native
chaos.
Engineering
is
something
which
which
is
yet
to
cross
the
adoption
chasm
as
prometheus
or
the
graduating
projects
have
already
done.
B
But
yes,
of
course,
it's
it's
coming
up
in
a
huge
way
and
obviously
you
can
see
with
all
the
projects
out
there
in
the
cncf
ecosystem
I
mean,
and
and
even
with
the
lfx
mentee
projects,
the
gsoc
and
everything
coming
up,
that
contributions
are
increasing
to
them
as
well.
And
of
course
one
of
them
is
litmus.
It's
a
cncf
sandbox
project
and
it's
meant
it.
B
It
was
initially
meant
to
curate
chaos,
engineering
for
just
kubernetes,
but
slowly
it
has
extended
to
even
a
non-communities
cloud
native
scenarios
and
and
so
so
many
other
scenarios,
where
obviously
in
simple
layman
terms,
if
you,
if
you
talk
about
litmus
what
exactly
it's
it
is,
then
it's
it's
a
tool
set
it's
a
framework
to
curate.
I
mean
inject
faults
in
the
systems.
B
Initially
it
was
for
sres
I
mean
only
sres
were
meant
or
practicing
chaos
in
some
form
or
the
other.
But
then
now
we
have
noticed
that
the
developer
persona
is
also
shifting
towards
practicing
chaos,
engineering
for
their
systems,
so
so
that
is
the
gist
of
litmus
and
talking
about
moving
to
contributing
to
litmus.
I
mean
there
are
so
many
folks
who
are
who
are
coming
up
in
the
community
from
various
enterprises,
companies
or
even
from
the
student
part
of
it.
B
I
mean
there's
an
amazing
initiative
that
cncf
has
taken
up
with
the
cloud
native
students,
so
students
are
also
looking
forward
to
contributing
to
it,
so
we'll
be
moving
part
by
part,
of
course,
how
people
can
get
started
with
contributions
and
what
all
are
the
essentials
to
to
contribute
to
the
litmus
project.
So
this
is
the
website,
of
course,
the
new
website,
which,
which
is
pretty
informative.
I
mean
it,
it
gives
you
an
overview
of
the
workflow
diagram
of
how
litmus
is
practice
will
move.
To
that
I
mean
here.
B
You
can
see
that
this
is
the
latest
overview
and
I
mean
adopters
features.
All
of
it
is
here
and
some
statements,
but
first
of
all,
before
I
mean
contributing
to
litmus
what
what
the
most
importantly
is
essential
is
to
understand
what
exactly
is
chaos
engineering
and
how
how
you
can
get
started
with
chaos,
engineering,
and
what
are
you
exactly
contributing
to
so
so?
Firstly,
I'll
be
just
sharing
this
open
source
document.
It
was
curated.
B
Two
years
ago
I
mean
netflix
initially
in
discovered
what
chaos
engineering
is
and
started
off
with
chaos,
monkey
and
then
slowly,
slowly,
everything
turned
out
and
there
there
were
so
many
more
projects
that
came
up
and
even
in
the
cncf
ecosystem.
So
initially
you
understand
what
chaos
is.
Of
course
it's
the
discipline
or
art
of
injecting
a
fault
in
the
system,
deliberately
to
basically
find
out
how.
How
does
the
system
withstand
these
turbulent
conditions
or
vulnerabilities
when
they
happen
in
real
world
scenarios,
and
these
principles
help?
B
B
Then
you
introduce
a
fault
in
the
system
and
and
then
you
know
there
are
so
many
real
world
scenarios
like
your
service,
crashing
your
hardware
or
software
going
down
and
then
eventually
you
would
test
in
production
in
a
controllable
way
to
identify
the
possible
faults
or
vulnerabilities
that
can
happen.
That
is
what
chaos
engineering
is,
and
these
are
the
principles
of
chaos
and
now
moving
on
to
what
litmus
is
and
and
the
litmus
repo
how
you
can
get
involved,
get
started
with
the
project.
Let's,
let's
take
a
sneak
peek.
B
Of
course
I
mean
this
is
the
main
repository
of
fitness,
but
I'll
start
off
with
I
mean
the
the
litmus
github
main
repository,
I
mean
where
you
can
find
the
other
subreports.
So
this
is
the
sub.
I
mean
the
main
repo
where
there's
the
litmus
repository,
and
there
are
so
many
other
repositories.
B
I
mean
the
chaos
operator,
the
chaos
charts,
the
runner,
the
dogs,
so
what
all
you
can
contribute
to
will
be
seeing
later
on,
but
I
mean
if,
if
you
want
to
be
contributing
to
any
of
these
reports,
then
check
out
the
litmus
repository
at
github.comchaos
and
you'll
be
able
to
access
all
these
repos.
So
so,
let's
get
started
with
litmus.
B
So
first
things.
First,
I
mean
before
you
you
get
start
started
with
contributions.
There
are
two
recommendations
that
I'll
have
for
you.
The
the
first
thing
is
going
through
the
readme.
I
mean
the
readme
is
the
most
helpful
document
in,
in
my
opinion,
and
with
all
the
information
out
there
I
mean
it's
there
in
other
languages
as
well:
korean
chinese,
spanish,
and
I
think
there
are
more
languages
I
mean
I'm
sure
there
are
more
languages.
Just
give
me
a
second
translations
yeah.
B
So
so
it's
in
french,
it's
in
german,
it's
in
russian,
it's
in
japanese!
So
so
any
translation
that
that
helps
you
you,
you
can
check
out
the
readme,
the
translation
and
then
obviously
there's
an
overview
and
what
are
the
components
of
litmus?
I
mean,
there's
a
chaos
control
plane.
Where
you
manage
your
cures,
the
chaos
center
is
present
and
then
it
helps
you
construct
and
schedule
and
visualize.
B
Your
chaos
workflows,
so
cure
center
is
something
which
comes
out
with
2.0
and
it's
it's
basically
the
ui
or
main
hub
where
sre's
developers,
they
start
inducing
chaos,
experiments
and
they
can
pull
in
chaos.
Experiments
from
the
chaos
sub,
we'll
move
to
the
hub
later
on,
and
then
they
can
pull
in
the
metrics
and
visualize.
What
exactly
is
happening
and
the
execution
plane
is
basically
where
you
are
executing
your
chaos.
On,
I
mean
it's.
B
It
is
usually
it's
running
on
kubernetes
itself
litmus,
but
then
you
can
use
the
api
to
run
it
on
your
aws,
azure,
vmware
or
gcp,
or
even
you
know
bare
metal
as
well.
So
that's
about
the
execution
plane,
and
these
are
the
definition
of
a
few
resources,
the
kiosk
custom
resources
or
the
crds,
basically
which,
which
can
be,
which
are
essential
for
you
to
run
your
chaos
experiment.
But
what
is
important
is
is
to
understand
this
workflow
I
mean
how
exactly
the
chaos
is
happening.
B
The
operator
pulls
in
the
chaos
experiment
from
the
chaos
hub,
the
engine,
the
chaos
engine
helps
run
the
crs,
and
then
you
know
the
exporter
basically
is
used
to
export
metrics
and
the
chaos
runner
acts
as
a
bridge
between
the
operator
and
and
the
the
chaos
engine
to
to
run
the
chaos
which
runs
in
form
of
a
chaos,
cron
job
or
experiment
job,
as
you
can
see,
and
and
then
these
the
results
which
are
provided
basically
tell
you
that
if
your
experiment
passed
away
so
so
that
is
about
the
readme.
B
I
mean
that
is
where
you
you
get
most
of
the
information
about
each
and
every
resource
of
litmus,
but
we
have
created
some
resources
for
people
who
get
started
contributing
to
litmus.
Are
you
just
out
of
college,
want
to
contribute
to
the
cncf
ecosystem,
specifically
to
the
cloud
native
chaos,
engineering
ecosystem?
We
start
off
with
kubernetes,
and
then
there
are
some
based
resources.
B
But
these
are
the
chaos
engineering
resources
more
to
be
added.
You
feel
free
to
add
them
here
in
the
resources
section.
So
so
that
is
where
you
you
get
started
with.
What
exactly
chaos
engineering
is
and
and
a
little
bit
about
litmus
alongside
the
readme,
and,
of
course,
if,
if
you
want
you,
you
can
always
check
out
the
blogs.
B
So
this
these
are
the
prerequisites
in
terms
of
information
that
that
you
need.
I
mean
what
exactly
has
been
happening
in
the
community
and
what
are
the
experiments
that
are
out
there?
Each
functionality
has
been
defined
in
in
the
docs
as
well.
We
will
move
to
that
later
on,
but
I
mean
the
blogs
read
me
and
the
resources
are
enough
to
give
you
a
gist
of
information
that
is
required
for
you
to
to
get
started
with
litmus
so
so
now.
Moving
on,
we
will
be
talking
about
what
exactly
you
can
contribute
to.
B
What
are
the
steps
to
contribute
and
what
exactly
is
the
model
contributing
to
listeners
how
to
begin
and
how
to
get
started?
So
I
mean
there
are
two
ways.
Of
course
one
of
them
is
creating
an
issue
by
yourself.
In
the
issues
section
I
mean
we
will
move
to
that,
but
either
you
can.
You
can
create
an
issue
that
that
ub
is
already
out
there
with
with
the
knowledge
you
have
had
about
the
the
github
or
you
go
on
and
basically
pick
an
issue.
B
Whichever
has
been
put
up,
and
I
mean
I'll
I'll
be
recommending
good
first
issues.
Of
course
I
mean
if
you
are
just
getting
started,
but
there
are
so
many
issues
specific
to
particular
functionalities,
what
all
to
contribute
to
and
the
docs
observability
that
there
is
so
much
to
features
bug
fixes.
So
so
there
is
so
much
to
contribute
to
that.
You
can
pick
an
issue
and,
and
and
usually
what
happens
is
just
give
me
a
sec
or
david
just
did
my
camera
stop.
A
B
Yes,
I
I
guess
broadcast
is
incomplete
without
technical
issues,
so
yeah.
B
Hope
everything
is
better
now
the
audio
the
video
everything's
fine.
B
Yeah,
so
so
so
moving
back
to
where
we
were,
I
mean
we,
you,
the
that
is
where
you
can
get
started.
Sorry,
sorry
for
that
issue.
So
so
what
are
the
steps
to
to
contribute?
And
what
exactly
you
you
need
to
address
so
so,
first
things.
First,
let's,
let's
just
move
on
to
issues
I
mean
there
are,
there
are
already
approximately
218.
B
I
think
a
few
of
them
is
are
resolved
already,
but
these
are
the
latest
issues
which
have
come
up
since
since
2.0
came
out
so
so,
and
most
of
them
are
bug
fixes,
but
there
are,
there
are
so
many
good
first
issues
that
can
be
taken
up.
So
so,
let's,
let's
just
take
a
look
at
one
of
the
issues
perhaps
created
by
one
of
the
community
members
which,
which
is
a
good
first
issue.
So
I
mean,
as
as
you
can
already
see,
that
there's
an
issue
that
has
been
created.
B
There
are
various
labels
that
are
out
there.
There
are,
I
mean
issues
there
are
bug
fixes.
There
are
front
end
issues.
There
are
good
first
issues,
of
course,
and
you
can.
There
are
area
specific
issues.
I
mean
analytics.
Chaos,
charts
exporters
and
there
are
various
areas
that
you
can
pick
up:
issues
for
artifacts
like
kubernetes
based
dockerfile
and
make
file
that
there
are
artifacts
that
you
can
pick
in
and
then
there
are
level
of
issues.
I
mean
difficult,
easy.
B
The
the
levels
are
also
out
there
and
plus
with
specific
to
gsoc
or
oktoberfest.
These
are
issues
again.
You
can
pick
and
for
kind
as
well.
I
mean
we
have
been
developing
a
lot
around
kind
and
around
the
languages
I
mean
litmus
is
written
in
go,
but
initially
it
was.
The
experiments
were
written
in
ansible
and
python
for
your
information.
B
So
so
now,
if,
if
you
are
good
with
go,
I
mean
if
I
have
to
talk
about
the
prerequisites
that
are
out
there,
if
you're
good
with
go-
and
you
have
got
some
good
knowledge
with
docker
and
kubernetes,
then
then
I
believe
then,
that
contributing
to
litmus
becomes
easier
for
you
and
even
in
python
and
ansible,
the
experiments
have
been
converted
to
python
as
well.
B
So,
if
a
good
with
python
as
well,
you
you
it
can
be
easier
for
you
to
contribute
chaos,
experiments
for
starters,
so
so
these
are
the
labels
that
are
out
there
and
I
mean.
Obviously
there
are
few
issues
that
are
created
by
the
members
or
or
the
the
contributors
to
the
project,
the
the
users
and
adopters
and
also
there
are
a
few
issues
which
are
created
by
the
maintainers.
B
Selena
is
one
of
the
core
contributors,
so
she
she
ended
up
assigning
the
the
issue
to
to
whoever
comments
on
it
and
then
the
maintainers
jump
in
and
and
come
in
to
help
you
so
so.
This
is
what
this
is.
How
you
pick
an
issue,
I
mean
you
pick
an
issue
according
to
what
are
the
requirements
or
what
are
the
details?
I
mean
what
exactly
has
happened,
what
is
expected
to
to
be
mitigated
or
how
how
you
mitigate
it,
what
is
expected
there
and
then
anything
else?
B
You
need
to
know
all
that
is
put
out
in
an
issue
and
you
can
pick
it
according
to
to
the
label
that
is
out
there
to
to
your
understanding
of
the
project.
That
is,
that
is
what
catering
to
issues
are
and
if
you
take
a
look
at
pull
requests
how
how
they
are
merged
or
how?
How
folks
have
come
up
raising
pull
requests
to
the
project
so,
for
example,
that
this
is
a
documentation
update
of
course.
So
so
you,
you
select
the
type
of
change
that
you
are
making
I
mean.
Is
it
a
new
feature?
B
Of
course
we
are
looking
for
new
features
and
chaos
experiments
in
in
like
specially
and
then
is
it
a
bug
fix
or
are
you
fixing
something?
It's
it's
a
it's
a
breaking
change
or
a
feature
that
existed,
but
it
was
not
working
as
expected
by
the
community
or
it's
it's
a
documentation,
update,
documentation,
updates
are
really
usually
updating
the
readme
or
anything
on
the
side
or
anything
related
to
the
dot,
md
files
of
any
particular
feature
or
experiment.
B
So,
of
course
I
mean
you
you
have
to.
I
mean
one.
One
thing
which
we
were
catering
to
is
the
the
amount
of
checks
that
are
required
for
for
the
the
full
request
to
pass
for
merging,
or
I
mean
the
the
idea
behind
it
was
to
have
a
better.
I
mean
better
code
analysis
and
obviously
ensuring
that
the
code
being
merged
leads
to
a
better
code
score
and,
of
course
it.
It
obviously
has
to
be
a
deeper
scan
where
there
are
no
bugs
or
issues
with
the
code.
B
So
we
ended
up
putting
up
all
these
checks
around
it
and
obviously
a
dco
or
developer
certificate
of
origin.
I
mean
this.
This
is
what
helps
you
understand
that,
if,
if
your
contribution
out
there
is
is
done
by
you
or
not,
it
certifies.
That
is
it's
wholly
done
by
you
or
partly
done
by
you.
So
so
we
had
a
dco
check
and
then
a
deep
scan
check
for
for
basically
identifying
any
deeper
issues
that
that
can
be
possibly
mitigated
and
and
then,
of
course,
better
code
hub
which,
which
approves
of
a
better
code.
B
B
So
so
you
you
put
out
the
review
and
then
there
are
a
few
reviews
and
comments
that
are
that
are
put
out
there
and
then
basically,
you
you
are
able
to
to
merge
your
pull
request,
or
I
mean
again
the
reviews
go
on
and
one
of
the
maintainers
jumps
into
to
merge
the
full
request.
So
so
that
is
how
it
usually
functions,
but
you
to
understand:
where
can
you
contribute?
It's,
I
think
the
something
which
is
important
is
to
to
read
the
contributing
documents.
So
first
things.
B
B
Here
are
a
list
of
the
good
first
issues
that
that
I
was
talking
about
the
issues
which
you
should
be
picking
or
the
issues
as
as
a
new
contributor
to
the
project
are
pretty
vital.
So
so,
as
you
can
see,
the
labels
are
already
put
out
there,
and-
and
I
mean
you,
you
can
pick
in
any
issue.
I
think
a
few
issues
have
already
been
picked
with
with
comments
out
there
and
people
who
are
already
assigned.
B
So
I
think
since
last
year
there
are
a
few
issues
that
that
need
to
be
mitigated
and
and
some
recent
issues
with
2.0
coming
up,
and
I
think,
even
if
there
are
issues
that
are
not
put
out
here,
what
one
thing
that
that
can
be
pretty
important
for
you,
or
one
thing
that
you
can
do
is
is
join
the
the
slack
community.
So
I
think
I
can
I
can
share
my
screen
to
the
slack
community.
Just
give
me
a
sec.
B
So
so
perhaps
the
slack
community
is
visible,
so
so
these
are
the
folks
that
are
out
here
and,
as
you
can
see,
they
come
up
with
issues.
What
exactly
the
issues
are
and
then
how
you
look
forward
to
contribute
so
so
on
on
the
slack.
Obviously
it's
on
the
community's
channel,
so
this
is
the
other
channel.
This
is
only
for
prs
or
or
contributed
contribution
related
discussions.
B
So
what
you
can
do
is
joining
the
these
two
channels,
the
litmus
and
the
litmus
dev
channel
you
you
can
come
up
and-
and
you
can
talk
about
your
pr
which
you
have
already
put
in
you-
can
talk
about
the
issue
that
that
can
you
you
want
to,
I
mean,
consider
taking
up
or
you
want
help
around
and
then
the
the
maintainers
are
obviously
out
there
to
help
you
get
assigned
that
sort
of
an
issue
or
you.
You
know
the
maintainers
help.
You
basically
understand
what
is
the
code?
B
What
is
the
code
base
and
where
exactly
a
mitigation
is
required
or
where
exactly
you,
you
can
basically
contribute.
So
so
that's
about
the
slack
channel.
I
think
the
slack
community
is
the
best
place
for
this
for
litmus
community.
At
least
I
mean
over
the
last
few
months.
B
There
have
been
so
many
contributions
from
the
student
community,
especially
so
so
that
makes
it
more
special,
of
course,
but
the
slap
is
is
the
place
to
get
an
issue
assigned
or
get
started
with
your
contributions
meet
the
maintainers
talk
to
the
core
contributors
to
to
get
further
help
around
contributing.
B
So
where
exactly
can
you
contribute
to?
Let's
take
a
look
at
that?
How
how
exactly
you
you
can
contribute
to
and
what
are
the
places
that
exactly
need
contributions.
So,
of
course,
there
are
the
chaos
charts
which,
which
consist
of
the
chaos,
experiments
or
basically
consist
the
charts
for
various
chaos,
experiments
that
are
out
there
and
various
more
to
be
added
the
chaos
workflows.
What
exactly
are
workflows
I
mean
workflows
are
nothing,
but
you
know
various
chaos
pulled
in
together
to
create
a
scenario
which
runs
according
to
a
particular
use
case.
B
I
mean
you
run
them
in
parallel
or
series.
That
is
what
happens
with
clickfunnels.
The
testing
tools
are
nothing
but
I
mean
various
tools,
for
example,
or
applications
which
which
are
used
to
test
litmus
alongside
that
it
can
be
a
stock
shop
application
or
you
can
add
your
new
application.
I
mean
as
of
now
there
are
three
main
applications
that
have
been
added
around
testing.
So
it's
the
sock
shop
application,
which
is
basically
an
ecommerce
website
of
socks.
B
Where,
where
you,
where
you
know
the
stocks
are
being
sold
and
you
use
litmus
to
curate
chaos
there
and
bring
the
website
down
or
a
bank
of
anthous
application,
it's
another
application
where
basically
it's
a
banking
application
where
you,
you
can
actually
use
chaos
to
to
create
chaos
around
various
banking
functionalities,
such
as
withdrawal
or
display
of
balance
or
deposits.
B
So
so,
let's
get
started
one
by
one.
I
mean
let's,
let's
get
started
with
chaos,
charts
so
to
understand
cures,
charts
of
course.
First
of
all
you
you
need
to
understand
how
how
these
charts
are
pulled
in
or
installed,
but
before
that
we
will
just
take
a
look
at
the
chaos
hub.
It's
it's
it's
a
marketplace
for,
for
the
chaos
experiments
it's
only
provided
by
the
liftbox
project.
No
other
project
provides,
I
mean
no
other
chaos.
Engineering
project
provides
a
marketplace
for
you
to
understand.
B
B
I
mean
community
members
have
come
forward
to
to
contribute
experiments
on
aws
or
on
or
on
the
generic
side.
So
what
exactly
is
important
for?
You
is
first
obviously
taking
a
look
at
these
experiments.
What
exactly
they
are
or
what
exactly
is
the
idea
behind
it?
I
mean,
as
you
can
see,
a
pod
delete
experiment.
B
What
what
exactly
it
does
and-
and
I
mean
it,
helps
obviously
disrupt
pod
and
there
are
videos
around
it,
a
lot
of
experiments.
You
can
watch
the
videos
I
mean
if
and
how
exactly
it's
being
deployed.
I
mean
if,
if
I
just
zoom
this
a
little
bit,
not
sure.
B
So
so,
as
you
can
see,
I
mean
what
are
the
platforms
that
that
this
is
feasible
for
and
what
are
the
useful
links.
This
is
the
source
code.
You
can
find
the
source
code
to
each
and
every
experiment,
so
I
mean
by
delete
what
is
the
description?
It
causes
a
part
failure
and
here
you
can
find
the
documentation
link
or
or
oh
I
guess
the
docs
are
changed.
Apologies
I'll
go
to
the
docs,
but
here
you
can
find
the
so
so
here
you
can
find
the
the
code
for
the
experiment.
B
I
mean
it's
it's
written
in,
go
as
you
can
see,
and
basically
that
that
helps
you
I
mean
partly.
It
is
the
basic
experiment
that
that
started.
I
mean
when
liquid
started
off
back
in
2018
it.
It
started
off
as
a
project
to
to
test
open
ebs,
which
is
another
cncf
project
based
on
cloud
native
databases.
B
So
the
pod
delete
experiment
was
written
back
then,
and
you
just
I
mean
import
a
few
packages
and
then
you
create
a
function
of
the
experiment
and
and
basically
this
this
is
something
which
is
done
for
part
delete.
But
this
is
how
you
put
the
idea
or
bring
in
the
idea
of
writing
a
chaos
experiment,
because
I
believe
that
is
the
most
important
contribution
to
litmus.
That
is
an
experiment
and,
and
you
lately
I
mean
there
have
been
contributions
based
on
reduce.
So
what
are
the?
B
What
are
the
experiments
that
can
be
contributed
to
or
how
do
they
align
to
the
future
roadmap?
I
mean
contributing
to
redis
and
contribute
continue,
contributing
radius-based
experiments,
jenkins-based
experiments,
experiments
based
on
mongodb
experiments
based
on
other
projects,
let's
say:
curating
chaos
on
an
application
on
a
particular
application
on
a
particular
project,
for
example,
as
as
you
can
see,
I
think,
in
at
the
chaos
hub,
you
were
able
to
see
that
there
were
experiments
related
to
open
ebs,
the
the
project
it
started
off
testing.
B
So
so
I
mean
if,
if
yes,
as
you
can
see,
there
are
projects
related
to
open
ebs
and
and
similarly
the
the
need
of
the
r
is
to
curate
chaos,
experiments
to
specific
applications.
So
one
of
the
contributors
just
came
out
and
talked
about
creating
chaos
for
sql
mysql,
as
you
say
so
so
even
that
is
a
possibility.
So
that
is
where
you
need
to
understand
by
by
checking
out
the
code
for
one
experiment.
I
think
that
that
gives
out
enough
information
and
then
slowly
you,
you
take
the
look
at
various
functionalities.
B
You
run
a
chaos
experiment.
How
is
it
working?
Is
it
working
fine
or
not,
and
and
then
then
you
basically
start
contributing,
but
there
is
a
specific
contributing
document
for
litmus
go
where,
where
you
understand
how
you
can
contribute
to
to
I
mean
litmus
goer
or
chaos
experiments
I
mean
the
the
steps
are
similar.
What
are
the
steps
to
contribute?
You
find
an
issue
or
create
an
issue.
B
Other
than
this
I
mean
there
are
various
contributions
you
can
make
to
the
other
side
of
things
to
to
to
the
various
other
functionalities
of
litmus.
So
getting
back
to
this
document
now,
moving
on
to
the
chaos
workflows.
Obviously,
a
workflow,
as
I
mentioned,
is
nothing
but
a
set
of
actions
strung
together
to
create
a
chaos
impact
and
how?
How
does
the
workflow
exactly
look?
It
looks
something
like
this.
This
is
an
orgo
workflow,
which
is,
I
mean,
created
in
series
as
well
as
parallel.
B
B
You
install
an
orgo
workflow
infrastructure
by
creating
an
orgo
namespace,
and
then
you
you
create
some
crds
after
you,
you
know
your
workflow
controller
is
deployed
and
obviously
litmus
provides
an
r
back.
I
I
don't
think
any
other
curiosity
provides
one,
but
I
mean
for
security
purposes.
Obviously,
and
our
back
is
provided.
So,
as
you
can
see,
this
is
a
code
or
this
is
the
lines
of
code
used
to
install
a
sample,
nginx
application.
B
So
so
you
refer
to
the
documentation,
of
course,
and
now
moving
on
to
the
documentation.
This
is
the
latest
documentation.
For
litmus
I
mean
this
is
the
documentation
which
comes
out
with
2.0,
so
so
it
helps
you
get
started.
There
are
a
few
tutorials
that
are
out
there
already,
and
one
of
them
is
obviously
getting
started
with
litmus.
How
you
can
install
litmus.
B
You
can
install
it
mess
either
using
helm
or
using
cube,
cuttle,
of
course,
and
and
then
once
you
are
able
to
install
litmus.
You
verify
your
installation
if,
if
your
front
end
and
your
mongodb
and
your
server
is
running
or
not
you,
you
configure
your
project,
you
are
welcome
to
the
chaos
center.
This
is
the
snapshot
of
the
chaos
center.
How
exactly
it
looks
and
you
you
set
a
new
password
and
you
are
welcomed
here
and,
and
this
is
where
you
can
run
your
kiosk
experiments.
B
So
yeah,
once
once,
you
are
obviously
done
identifying
how
how
litmus
is
run.
Then
it
becomes
easier
for
you
to
understand
what
exactly
your
workflows
are
and,
and
obviously
this
is
the
readme
for
that,
and
then
you
move
on
to
the
workflows
that
have
already
been,
I
mean,
contributed.
There
are
organic
if
the
workflow
for
port
delete
has
already
been
contributed
with
orgo
and
I
mean
orgo
workflows.
B
We
chose
orgo
workflows
because
the
idea
was
to
integrate
with
other
cloud
native
projects
and
eventually
the
idea
is
to
integrate
with
more
projects
like
fluently,
cross
plane
and
all
so
even
that
can
be
a
contribution
if
you,
if
you
talk
about
in
contributing
to
an
integration,
so
I
mean
I'll.
Just
take
you
through
one
contribution
as
an
integration,
I
mean
there
are
integrations
with
captain
kubler,
but
as
you
can,
as
you
can
see,
this
is
a
contribution
with
octatocloud.
B
So
so
we
integrated
with
the
octet
of
pipeline
octato
is
a
developer
for
made
for
cloud
native
development,
and
these
sort
of
integrations
were
again
contributed
by
the
community.
Ramiro
he's
been
an
amazing
contributor
to
the
litmus
project
and
similarly
we
we
look
forward
to
contributions
and
where
you
can
contribute
or
how
to
get
started.
B
Let's
say
you
are
a
core
contributor
to
falco
or
let's
say
your
core
contributor
to
cross
plane,
so
so
this
can
also
be
a
possibility
where,
where
you
contribute
to
to
a
project
a
project
integration
with
litmus
and
chaos
can
be
induced
in
that
project
or
there
can
be
a
functionality
behind.
I
mean,
for
example,
there's
a
there's,
a
contribution
that
is
already
going
on
with
litmus.
So
what
exactly
is
that
contribution?
B
That
is
where
you
contribute
litmus
chaos
based
policies
for
kaiver.
No,
so
so
again,
whoever
is
wanting
to
run
litmus
or
whoever
is
wanting
to
run
kaiver
know
they.
They
can,
I
mean
for
litmus,
they
can
use
kyberno
based
policies,
and
then
they
can
use
chaos
tests
alongside
kaivon
also,
so
that
turns
out
to
again
be
an
amazing
contribution.
So
this
is.
B
So
so,
let's,
let's
get
started
with
the
chaos
exporter.
I
mean
I
have
actually
covered
a
lot
in
terms
of
what
exactly
are
the
repo
that
you
can
contribute
to.
But
I
mean
this
is
one
important
thing:
the
the
monitoring
side
of
things
I
mean
folks
need
to.
B
If
you
you
have
knowledge
with
prometheus
and
golang
and
kubernetes,
then
I
think
and
cloud
watch
as
well,
so
you
use
prometheus
as
well
as
the
cloud
watch
exporter
to
export
the
chaos
metrics.
So
so
either
of
it
is
good.
If
you
have
knowledge
with
prometheus,
or
I
mean
you,
you
are
good
with
metrics,
then
you
can
come
ahead
and
contribute
various.
I
mean
dashboards
or
how
the
metrics
are
being
pulled
in
the
experiment,
scope,
metrics
or
application
scope.
B
Metrics
names,
space,
scope,
metrics:
these
are
what
can
can
be
possible
lines
of
contribution,
but
cluster
scope,
metrics
of
course,
so
so
that
is
where
again
you
you
get
started
by
checking
what
what
are
the
contributions
or
issues
that
are
already
out
there.
I
mean
the
the
results
that
I
mean
that
that's
a
very
old
contribution,
but
I
think
with
metrics
and
observability,
improving
the
there
is
already
option
for
observing
chaos
in
the
litmus
portal
itself,
the
2.0
portal.
B
So
so
you
you
can
check
what
is
missing
already
out
there
and
then
I
think
that
that
helps
you
contribute
to
litmus
better.
Perhaps
I
can
take
some
questions
now.
I
think
I
have
covered
so
much
and
it
might
have
been
a
bit
confusing
for
folks
out
here.
So
I
think
david.
Perhaps
if
we
have
any
questions
or
anything,
we
can
take
it
up.
I'll
have
some
water
and
then
we
can
continue.
A
A
You
know,
there's
a
fair
number
of
repositories
there.
I
think
I
also
like
the
availability
of
programming
languages.
Like
you
know,
people
can
bring
their
pies
and
knowledge
or
their
google
knowledge
or
their.
You
know
even
their
database
knowledge,
because
all
this
expertise
that
people
have
and
so
many
surrounding
ecosystems,
chaos
and
contributing
to
the
kiosk
projects,
it's
a
great
way
to
get
involved
like
if
you
have
operational
knowledge
of
mysql
or
mongodb
or
postgres
or
redis
or
nginx.
There's
all
these
things
that
can
have
very
specific.
A
A
Is
really
exciting
because
again
it
doesn't
matter
where
your?
What
your
experience
is,
you
can
bring
it
to
the
litmus
project
and
make
people's
lives
easier
or
better
or
maybe
worse,
for
a
while,
because
you
know
the
first
time
you
deployed
litmus
to
your
production
stack.
You
may
have
some
problems,
but.
A
A
It's
not
something
that
we've
seen
with
some
of
the
other
projects
on
lg
team.
They
all
require
knowledge
of
go
and
they'll
require
knowledge
of
this
very
specific
thing,
and
litmus
is
much
broader
than
that.
Much
ways
of
that.
Much
more
inclusive.
With
regards
to
skills,
which
I
think
is
really
exciting,
but
very
cool.
B
I
mean
the
idea
behind
it
was
actually
making
it
open
for
contributions
and
bringing
in
more
contributions,
and
I
think
one
specific
thing
I
wanted
to
cover
was:
I
mean
the
the
idea
of
special
interest
groups.
I
mean
it
started
from
the
cncf
in
kubernetes
and
we
wanted
to
create
various
special
interest
groups
based
on
deployment
documentation.
The
documentation
group
is
the
most
active
one.
I'm
indivia
she's
a
cncf
ambassador.
She
joins
in
every
mondays.
B
We
we
have
the
the
doc
calls
every
monday,
and
then
we
have
calls
for
each
and
every
special
interest
group.
So
just
taking
you
through,
if
let's
say
a
special
interest
group,
there
are
goals
which
are
set
and
there
are
chairs
and
leads
from
you
know.
Various
companies
I
mean
dvi
is
from
hsbc
it's
from
aws
and
then
there
are
obviously
repositories
which
are
set
up
and
there's
a
meeting
cadence.
So
I
mean
there
are
various
documents
that
that
are
also
helpful.
B
They
started
off
last
year,
but
I
think
it's
it's
important
to
cover
it
here,
because
we
are
talking
about
contributions.
So
there's
a
charter
which
we
have
set
up
and
each
and
every
group
has
a
specific
motto
or
goal
where
we
cover
orchestration:
observability,
ci
cd.
Obviously,
chaos
is
coming
up
in
your
ci
pipelines
and
and
then
testing
how
you
can
test
the
various
kiosk
experiments.
B
How
can
you
check
various
integrations
deployments
so
so
all
of
it
is
out
there
and
obviously
there's
a
community
group
as
well,
where
I
mean
community,
more
or
less
is
is
handled
by
me,
so
obviously,
on
the
on
the
community
side.
If
you
talk
about
contributions,
then
it
can
be
blogs.
If
you
want
to
get
started,
writing
a
blog
or
if
you
want
to
join
an
event
or
curate
a
meetup.
I
mean
that
is
also
one
way
of
a
contribution.
Of
course
that's
that's
also
contribution,
but
other
than
that.
These
six
are
pretty
vital.
B
If
you,
if
you
want
to
get
started
with
with
any
sort
of
contribution
and
other
than
that,
I
I
hope
that
the
the
contributing
doc
helps
and
helps
you
get
started
and
eventually
perhaps
you
you
can
just
join
in
the
slack
channel
you
can.
You
can
put
forward
what
exactly
you
want
to
contribute.
To
I
mean
2.0
is
vast.
There
are
so
many
more
issues
that
are
going
to
come
in
the
next
quarter
or
with
this
quarter
as
well.
B
B
A
Documents
that
you
walked
us
through,
like
those
were
really
great
and
deaf,
everyone
should
go
and
read
them
before
they
start
submitting
to
the
wet
and
pull
request
of
the
olympus
project.
Another
thing
is
that
they're
about
writing
blogs
as
well
like
I.
B
A
Awareness
for.
A
A
All
right,
if
you
are
watching
us
now,
you've
got
about
one
more
minute
to
get
any
questions
into
the
chat.
Is
there
anything
else
you
would
like
to
show
us.
B
Perhaps
I
think
this
this
is
good.
Perhaps
I
can.
I
can
just
take
a
look
at
the
community
section.
That's
that's
how
how
are
you
you
can
get
involved
with
the
community
and
obviously
join
the
slack
channel
check
the
contributing
docs
on
github
and
there
are
meetups
and
see
sync
up
happening.
Sync
ups
happening
so
on
the
third
wednesday
of
every
month,
9
30
a.m,
pst
6,
30,
pm
cest.
We
have
our
community
calls
so
to
get
started
with
contributions.
B
If
you
directly
want
to
meet
the
maintainers
and
have
a
discussion
over
a
meet
up,
then
that's
the
best
place
to
join
or
the
chaos,
engineering,
meetups
and
and
then
you
can
can
check
the
blog
section.
So
I
think
one
one
important
aspect
that
I
would
like
to
cover
is
that
even
the
blogs
are
are
contributed
in
an
open
source
way.
So
so,
if
you
want
to
contribute
a
blog,
what
you
can
do
is
you
can
just
create
a
post,
I
mean
on
dev.2
and
you
can
use
the
tag
hashtag
litmus
chaos.
B
B
So
on
the
blog
front,
even
even
that
is
in
a
way,
you
know
open,
source
or
or
open
for
contributions.
So
I
think
that
is
it.
Take
a
look
at
the
chaos
up.
The
documentation
get
involved
with
the
community,
join
the
slack,
meet
the
maintainers
and
and
obviously
talk
to
them,
get
yourself
an
issue
assigned
or
pick
an
issue
which
is
already
out
there
and
obviously
the
more
you
study
about
litmus,
the
the
better
you
get
with
contributing
chaos,
experiments
and
contributions.
A
A
B
And
I
think
one
last
thing
perhaps
you
can
do
is
take
part
in
discussions
as
well.
This
is
something
I
forgot
to
mention,
but,
as
you
can
see,
there
are
so
many
discussions
that
have
been
created
discussions
around
docs
new
design
for
2.0
docs,
even
the
docs
discussions
were
contributed
by
by
community
members,
and
there
are
so
many
new
discussions
that
have
been
created
alongside
the
release.
B
So
I
mean
2.0
is
out
that's
a
discussion,
the
resources
that
that
you
can
contribute
to
it
becomes
a
discussion
and-
and
even
even
you
know,
if,
if
you
want
to
create
your
own
discussion,
you
can
go
ahead
and
create
a
discussion,
and-
and
you
know
that
can
be
on
the
contributors
point
where
folks
can
understand
where
they
can
contribute
to
what
exactly
what
sort
of
a
contribution
is
required
and
what
sort
of
an
issue
you
can
pick
up.
These
discussions
also
help
to
gauge
the
open
source
community
and
bring
in
contributions
so
yeah.
A
Awesome
all
right
well,
thank
you!
So
much
for
your
time.
I
I
know
it's
getting
late,
so
I'm
going
to
let
you
go
and
enjoy
your
weekend
now,
but
it
was
a
great
session.
Thank
you
for
sharing
all
of
that
knowledge
with
everybody.
I
hope
people
are
excited
and
pumped
and
start
contributing
to
the
litmus
project
is
an
awesome
project
with
some
awesome
people
so
have
a
great
weekend
to
everyone.
That
watched
see
you
all
next
time.