►
Description
Deploying a multi-component system like Hyperledger Fabric to production is challenging. In this webinar we lower the threshold by showing how to deploy Hyperledger Fabric onto Kubernetes through the usage of Helm Charts. Rather than using a monolithic Helm Chart for the whole deployment, we provide separate charts for each Hyperledger Fabric component, namely the Certificate Authority, Peer, CouchDB and Orderer. We demonstrate how to enable these charts to work together to provide a working blockchain system.
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
A
B
Everyone
and
thank
you
for
attending
today's
webinar,
a
hitch,
cart
hitchhikers
guide
to
deploying
higher
bludger
fabric
on
kubernetes.
My
name
is
Emily
and
I'm.
A
member
of
the
team
here
at
the
Linux
Foundation
working
on
the
hyper
ledger
project
before
we
begin
I
want
to
cover
a
few
housekeeping
items.
B
First,
this
webinar
is
being
recorded,
so
if
you
need
to
drop
off
at
any
point,
we
will
automatically
send
you
a
link
to
the
recording
via
email
within
a
day
or
two
at
the
bottom
of
your
audience,
console
or
widgets
that
control
the
movable
and
resizable
content
windows.
You
can
click
and
drag
to
the
lower
right
hand,
corner
of
each
widget
to
change
the
size
and
you
can
move
the
windows
around
to
customize
the
layout
to
your
preference,
starting
with
the
icon
on
the
left.
B
The
film
reel
controls
the
audio
for
this
event
or
it
allows
you
to
fast
forward
or
rewind.
If
you're
watching
this
on
demand,
the
Q&A
widget
allows
you
to
submit
questions
at
any
time.
During
the
presentation,
we
will
try
our
best
to
answer
as
many
of
them
Lee
as
we
can.
If
you're
watching
this
on
demand,
you
can
still
submit
questions
and
we
can
respond
to
the
email,
the
chart,
icon
controls
the
slide
viewing
window.
The
document
widget
contains
links
to
resources
mentioned
in
today's
presentation
and
other
resources.
We
think
you
might
find
interesting.
B
You
will
also
have
act
instant
access
to
a
copy
of
today's
slide
deck.
The
person
icon
opens
a
window
where
you
can
learn
more
about
today's
guest
speakers
and
the
clipboard
allows
you
to
access
our
survey
widget,
which
helps
us
collect
valuable
feedback.
Please
take
a
moment
at
the
end
of
the
presentation
to
answer
a
few
questions
about
today's
session
and,
finally,
the
question
mark
opens
a
help
topic
window
in
case
you
experience
issues
with
the
console.
B
If
you're
joining
us
on
a
non
Ubuntu
Linux
machine,
please
keep
in
mind,
you
may
experience
legs
and
site
advancement
and
refreshing.
Your
browser
might
help.
You
can
join
us
on
Twitter,
using
the
hashtag,
LF
webinar
and
don't
forget
to
follow
us
at
hyper
ledger
and
at
Linux
Foundation,
as
I
mentioned,
keep
an
eye
out
from
an
email
from
us
in
the
next
day
or
so
with
a
link
to
today's
recording
that
takes
care
of
our
housekeeping
info
and
please
to
introduce
today's
guest
speakers.
B
Sasha
Grubb
of
etske
and
Nicola
pally
sasha
is
CTO
and
data
scientist
at
aide
technology
and
Nicola
is
lead
blockchain
engineer
also
with
a
tech.
Please
don't
forget
to
read
the
detailed
bios
of
our
speakers
on
your
screen
as
our
work
histories
and
experience
are
absolutely
fascinating.
Thank
you.
So
much
for
joining
us
today,
Sasha
and
Nicola.
C
A
My
cellphone
as
I've,
been
mostly
working
on
happily
a
fabric
again
with
composer,
also
and
I
doubled
a
little
bit
in
the
serum
at
one
point
and
took
a
little
bit
of
a
look
at
photos
in
Iroha,
but
haven't
worked
with
them
directly
and
I
haven't
actually
worked
with
either
quorum
corridor
or
between
itself.
Yet
so
maybe
we
can
see
the
results
we
have
now.
A
A
We're
going
to
ask
you
if
you
are
deploying
hypogea
fabric,
how
do
you
do
it
in
production
and
in
this
case,
we'd
have
a
kind
of
multiple
choice
in
because
you
might
use
multiple
methods
and
I
know
we
do,
and
so
you
we
want
to
know
essentially
how
you
deploy
hybrid
fabric.
Do
you
do
it
on
bare
metal
virtual
machines
on
kubernetes
order,
use
like
a
tool
like
hyper
ledger,
cello
or,
if
you
don't,
we
would
also
like
to
know
that.
C
A
So
I
also
started
to
work
with
virtual
machines
and
then
I
after
working
with
them
for
a
while
and
seeing
how
complicated
these
to
try
and
deploy
a
lot
of
things
with
their
pulling
that
was
available,
I
switched
to
docker
containers
and
cornetist
and
I
haven't
really
looked
back.
I
haven't
yet
worked
with
using
bare
metal
and
I,
don't
really
plan
to
land,
but
I
am
and
I
think
we
are
looking
to
add
some
contribute
to
hydrology
cello
and
see
if
we
can
include
their
hand
charts
there.
A
A
C
Everyone
I'm
Nicola
and
I'm
the
lead,
blockchain
engineer
at
attack
and
I'm
working
on
building
business,
blockchain
applications
using
tools
from
the
hydrology
of
projects
and
I've
submitted
improvements
and
contribution
to
the
hyper
ledger.
Composer
really
such
as
an
API
key
security
feature.
And
what
about
you.
A
C
Okay,
so
we
can
introduce
the
webinar.
We
will
split
this
webinar
into
four
sections.
First,
we
will
describe
the
blockchain
framework,
a
hyper
ledger
fabric.
Then
we
will
give
an
introduction
to
kubernetes,
which
is
a
platform
for
deploying
micro
services.
In
the
third
and
main
section
we
will
walk
to
us.
A
A
A
A
So
the
certificate
authority
manages
the
identities
in
a
nutshell:
it
registers
these
identities
which
are
saved
to
its
database,
and
then
it
teaches
enrollment
certificates
which
allow
the
identity
holder
to
demonstrate
that
they
belong
to
an
organization.
Finally,
the
certificate
authority
can
renew
a
certificate,
making
an
expired
one
valid
or
it
can
revoke
an
existing
certificate,
making
it
in
ballot.
A
The
ordering
service
consists
of
one
or
more
order
notes
that
talk
to
each
other
in
development.
You
typically
use
a
single
order
using
soil
consensus,
which
is
effectively
no
consensus
in
production.
You
should
really
use
a
proper
consensus
algorithm
like,
for
example,
Kafka,
which
depends
on
an
Anna
Patrick
Kafka
cluster,
to
exchange
messages
between
the
orders
and
ensure
crush
tolerant
consensus
on
transactions
and,
finally,
ears
are
the
notes
that
actually
maintain
the
ledger
and
communicate
with
the
client
applications.
C
A
Think
all
of
these
can
be
called
orchestration.
Just
like
a
director
that
ensures
all
the
musicians.
The
next
concept
is
charts.
Charts
are
bundles
of
template.
Is
that
define
and
group
his
components
into
a
neat
package?
They
effectively
act
as
cookie
cutters
for
kubernetes
applications.
You
can
browse
these
guys
at
the
kubernetes
at
the
cube
apps
hub.
A
C
Okay,
so
before
replicating
what
we
do
on
this
webinar,
we
will
need
three
things.
One
is
a
running
kubernetes
cluster,
then
a
cheap
or
free
domain
name
to
connect
to
your
cluster
and
download
the
repository.
So
you
can
get
a
managed
cluster,
a
kubernetes
cluster
from
most
cloud
providers,
especially
given
their
generous
free
credits.
A
A
A
C
C
A
Cool,
so
here
are
the
actual
values
file
that
we
use
for,
deploying
that
poster
SQL
Server
chart.
We
start
by
defining
would
post
press
sequel
image
version
we
want
to
use.
In
this
case
it's
nine
point,
six
dot
two.
We
also
how
to
generate
a
strong
password
using
the
chart,
and
we
specify
that
it
has
a
database
called
fabric
CA.
A
A
Finally,
you
can
see
be
an
ante
affinity
to
the
fact
these
does
not
do
much
when
we
have
a
single
instance.
But
if
you
are
deploying
multiple
databases,
you
will
probably
want
them
to
end
up
on
different
kubernetes
machines
to
decrease
the
chance
that
if
a
single
machine
fails
that
it
would
kill
all
your
databases.
C
Yes,
so
the
next
step,
installs,
the
app
the
actual
fabric,
see
a
chart
that
session
and
I
created.
The
pod
will
take
a
few
minutes
to
get
started
so
be
patient.
We
can
run
the
command
cube,
control,
get
pods
to
get
the
actual
pod
running
the
CA
and
then
run
cube
control
logs
to
check
if
the
CA
server
has
started
running.
A
The
values
file
for
the
C
is
considerably
more
involved.
Firstly,
we
define
the
image
tag
where
we
use
fabric
1.2.
We
also
implement
an
ingress.
This
is
basically
a
way
for
you
to
access
the
certificate
authority
from
outside
the
kubernetes
cluster.
In
this
case
I'm,
using
a
test
domain
that
we
own
to
enable
access
to
our
CA,
we
again
implement
persistence
to
store
the
certificates
permanently,
so
we
don't
lose
them
if
the
polder
starts.
A
Then
we
define
some
configuration,
such
as
a
hyper
laser
tools
version
we
use,
which
customizes
one
of
the
config
Maps
in
the
chart
and
a
config
map
is
basically
a
set
of
values
that
you
store
is
an
essentially
a
kubernetes
abstraction
that
stores
some
values
that
are
a
bit
made
available
to
the
pod
to
read.
Importantly,
we
also
specify
the
certificate
signing
request
and
an
affiliation
list
which
in
this
case
is
something
and
finally,
we
again
add
a
poll
affinity.
A
A
Then
we
can
run
cube
control,
get
ingress
on
our
machine
to
obtain
the
ingress
connected
to
the
fabric
CA
service.
So
this
will
essentially
be
the
domain
name
that
we've
spoke
well
once
you
have
that
set
up.
You
should
be
able
to
use
the
curl
command
to
get
this
CA
info.
Bear
in
mind
that
please
depends
on
the
certificate
manager
setting
up
the
TLS
correctly,
so
you
might
need
to
wait
for
a
little
while
before
this
works.
A
A
C
Okay,
here,
the
key
thing
to
notice
is
that,
when
speaking
with
the
CA,
we
need
to
specify
the
let's
encrypt
authority
certificate
for
the
TLS
connection.
Since
the
fabric
see,
a
client
will
check
that
this
certificate
corresponds
to
the
one
sees
when
connecting
to
the
c8
server
exactly
so
since
our
apps
will
use
the
certificate
and
the
key,
we
need
to
use
a
cube
control,
create
secret
generic.
To
add
this
file
to
the
kubernetes
service,
as
secrets.
A
A
A
A
Then
we
also
define
the
orders
in
the
organization
using
a
very
similar
format
as
before.
We
also
define
all
of
the
Kafka
options.
Importantly,
rather,
rather
than
defining
all
of
the
different
Kafka
nodes
that
we
will
have
in
in
our
case,
we
will
have
for
Kafka
nodes.
Instead
of
that,
we
specify
the
kubernetes
Kafka
service
as
a
single
address,
since
that
will
act
as
a
load
balancer.
To
balance
the
request
to
all
the
different
Kafka
poles
in
this
avoids
reconfiguration.
If
we
decide
to
scale
our
Kafka
up
or
down
so.
C
Having
to
find
the
config.xml
file,
we
can
run
the
config
yes
Jen
tool
that
we
use
it
twice,
pointing
it
to
the
two
profiles.
We
define
it
to
produce
a
Genesis
block
for
the
orders
and
the
channel
transactions
for
the
peers.
So
we
again
have
these
two
kubernetes
secrets
to
store
them
on
our
cluster
and.
A
A
A
A
A
The
configuration
of
the
right
section
contains
several
options
that
are
necessary
to
work
with
fabric
I
stress
that
all
these
options
are
necessary,
but
the
most
important
one
is
the
last
one
called
the
lock
dot
retention
dot
MS,
which
specifies
so
that
we
never
want
to
forget
a
record,
because
by
default,
Kafka
will
forget
records.
After
typically
around
two
weeks,
I've
seen
many
messages
on
the
rocket
chart
of
hype
ledger
from
people
who
forgot
to
implement
this
and
boy.
It's
not
pretty.
Ok,.
C
A
A
We
also
auto
generate
a
one-time
password
to
register
with
a
CA
which
we
will
look
at
a
person.
Then
we
define
some
configuration
to
specify
what
version
of
the
fabric
see
a
client
to
install
on
the
order.
In
this
case,
we
also
installed
the
fabric
C
kind
version
1.2
to
0.
We
also
specify
the
type
of
which,
in
our
case,
is
Kafka
and
the
Ibo,
the
organization
members
membership
service
provider,
which
in
our
case,
is
a
tech
MSP.
A
A
But
finally,
we
can
set
up
the
order
identity
to
do
this.
We
first
get
the
CA
password
from
the
order
s
sacred.
This
is
exactly
the
password
that
was
also
generated
by
the
chart.
It's
a
one-time
password
that
we,
you
will
use
for
enrolling.
We
then
use
we
use
the
cube
control
exec
to
connect
to
the
fabricc
and
register
the
identity.
All
the
order
with
a
CA
specifying
this
environmental
variable.
A
The
order
chart
is
configured
to
periodically
try
to
enroll
with
a
PC.
Once
it
does
this
successfully,
the
order
will
actually
start.
We
can
then
get
the
order
pod
using
Q
control,
get
pods
and
check
that
the
order
has
started
by
running
cube
control
logs
and
the
filtering
for
the
string
completely
initialization
and.
C
C
Installing
the
fabric
peer
involves
five
steps,
but
most
of
these
will
look
very
familiar
by
now.
The
first
step
is
to
install
the
couch
DB
database,
and
this
is
very
similar
to
installing
the
post-grad
PostgreSQL
chart.
So
after
deploying
it,
we
again
use
the
kubernetes
logs
to
check
if
it
is
running.
A
The
values
file
in
this
case
is
really
really
simple,
and
it
mainly
specifies
the
version
of
the
hyper
Letcher
county
be
docker
image,
which
in
this
case
is
0.42
10.
We
also
again
specify
a
persistence
so
that
the
couch
DB
database
holds
the
data
and
an
ante
affinity
so
that
car's
DB
pods
are
actually
deployed
on
different
kubernetes
machines.
A
A
Again
we
note
the
secrets
that
we
need,
such
as
they
see
it
here,
less
secret,
which
we
need
to
communicate
securely
with
the
CA,
the
channel
secret,
specifying
the
channel
transaction
that
will
allow
the
peer
to
create
enjoined
channels
and
the
organization
admins
certificate
and
key,
which
is
also
necessary
to
actually
join
the
channel,
to
essentially
ask
permission
to
the
network
again
to
set
up
the
peer
identity.
We
get
the
C
password,
which
is
again
a
one-time
password
generated
automatically
by
the
chart,
and
we
register
the
peer
with
a
certificate
authority.
A
C
A
Once
the
channel
is
created,
you
will
need
to
fetch
it
and
join
it
on
every
period
that
you
create
by
running
the
peer
tunnel,
fetch
config
command
inside
the
peer
and
then
run
the
peer
channel
join
inside
each
peer
container
as
well.
Once
all
of
that
is
done,
you
can
run
peer
channel
list
to
check
that
the
peer
has
indeed
join
the
channel
and.
C
C
C
A
Finally,
we
are
also
releasing
a
chart
for
hyper
ledger
composer
and
that's
being
reviewed
right
now,
so
it
might
take
a
few
weeks,
but
also
over
the
last
few
days,
I've
been
playing
around
with
hyper
ledger
explorers.
So
if
all
goes
well,
we
will
also
create
a
chart
for
that
as
well.
Just
to
I
guess
remind
you
that
the
hybrid
is
quite
a
logical
system
of
many
many
different
projects
in
this
webinar.
We
mostly
covered
hydrology
fabric,
but
there's
also
a
helmet
art
for
installing
Barrow.
A
A
A
Basically,
you
can
submit
pull
requests
if
you
want
to,
for
example,
change
a
chart.
For
example,
you
might
want
to
expand
one
of
our
charts,
for
example,
their
typical
updates
that
you
might
want
to
do
is
our
current
fabricc
a
chart.
It
actually
only
supports
their
Postgres
sequel
database,
but
you
might
want
to
expand
it
to
be
able
to
work
with
my
sequel
or
some
other
database.
You
can
create
a
pull
request
and
we
will
review
it
as
soon
as
possible,
typically
we're
quite
quick
to
review
and
we're
very,
very
happy
for
contributions.
A
A
A
We
took
this
into
account
by
creating
self-contained
help,
charts
that
each
deploy
is
a
cific
separate
component,
such
as
a
single
peer,
a
single
order,
a
single
certificate
authority
and
rather
than
trying
to
create
a
chart
that
tries
to
deploy
a
whole
network,
and
these,
we
believe,
will
make
it
easier
to
make
customization,
because
you
can
simply
change
your
config
DX
file
to
specify
that
you
have
more
orderers
or
that
you
have
different
anchor
peers
and
simply
deploy
in
a
very,
very
similar
fashion.
As
what
we've
had
in
this
webinar.
But
using
your
own
specifics.
A
Can
I
use
mini
Cube
to
deploy
this?
This
is
the
next
question
we'd
like
to
answer
and
technically
you
can,
and
the
thing
to
bear
in
mind
is
that
one
you
will
need
to
change
the
type
of
storage
that
you
use.
You'll
probably
need
to
specify
that
you're
using
local
storage,
and
importantly,
you
will
also
probably
need
to
get
rid
in
the
values
files
of
their
affinities
and
anti
affinities,
because
you
will
have
a
single,
a
single
node,
essentially
a
single
Kunitz
node.
A
A
Everything
with
students,
so,
for
example,
you
might
want
to
get
rid
of
that
whole
section
from
lines
ten
to
sixteen
for
this
one,
because
you
have
a
single
node,
we
bear
in
mind
that
I
haven't
actually
used
mini
cube
to
deploy
it
I've
typically,
and
you
use
the
real
cluster
because
I
think
that
is
closer
to
being
in
production.
So
I
prefer
to
do
that.
A
A
Nicola
will
check
check
it
out.
Basically,
if
you
search
for
udemy
and
then
blockchain
4,
sorry
Hydra
later
for
blockchain
applications,
you
will
find
it
and
I
think
that
we
can
possibly.
We
can
probably
include
it
after
after
the
webinar,
we
can
add
the
link
to
it
on
the
actual
repository
so
that
it's
easy
to
find
basically
and
via
the
link
is
actually
quite
easy,
is
basically
udemy.com.
A
A
A
In
the
case
of
kubernetes,
you
will
need
to
actually
specify
the
separate
components
using
values-
funds,
as
we
have
in
the
repository
and
as
we
showed
here,
and
you
will
need
to
specify
like
write
your
own.
We
config
the
X
file
or
adapted
and
then
use
these
two
things
basically
to
deploy
your
network.
A
Will
this
to
include
any
integration
deployment
with
hydrology,
jello
or
just
communities
on
its
own?
So
for
now
we
haven't
ourselves
the
absolute
use
chello.
We
are
in
close
contact
with
dead
shell
developers,
and
one
of
our
plans
is
to
actually
help
integrate
the
charge
that
we
developed
into
the
cello
project
to
make
it
even
easier
to
deploy
applications.
A
A
In
production,
tis
suggested
to
use
as
a
next
question
is
in
production,
it
is
suggested
to
use
hyper
laser
fabric
is
supposed
to
use
Kafka
based
ordering,
but
to
run
it
we
need
Kafka
brokers
and
run
Kafka.
We
need
zookeeper
notes
to
support
orders.
We
need
for
zookeepers.
So
now,
in
order
to
keyboard
single
point
of
failure,
we
need
to
have
all
these
nodes
in
different
machines.
How
does
it
affect
the
overall
performance
and
of
fabric?
A
A
You
do
need
four
for
Kafka
notes
to
ensure
some
basic
crash
tolerance
and
the
more
the
merrier.
Of
course,
five
or
six
will
give
you
more
crash
tolerance,
but
human
needs
free
or
potentially,
five
zookeepers,
and
all
these
nodes
need
to
be
on
different
machines
and,
of
course,
that
means
that
they
need
to
be
have
anti
affinities
assigned
to
them
on
the
kafka
value.
So
on
the
on
the
kubernetes
values
files
and,
of
course
this
will
affect
the
performance
of
fabric.
A
The
next
question
is
where,
when
can
I
get
the
helm
chart
repository,
so
actually
our
help
charts
are
all
published
on
open
source
repositories.
One
of
these
repositories
is
the
official
helmet
and
slash
charts,
repository
and
maintained
by
the
hand
foundation,
which
is
closely
affiliated
with
kubernetes,
and
we
also
publish
the
same
charts
on
our
own
open
source
repository
on
a
technology,
/
AP
charts,
and
we
can
also
what
we
will
do
is
we'll
also
add
information
about
this.
On
the
repository
that
we
shared
so
that
you
can
easily
find
these
charts.
A
Can
to
fabric
be
installed
on
different
communities
clusters
communicating
with
each
other
how
to
keep
the
communication
all
the
clusters
private
if
they
are
in
different
clouds.
So
these
are
two
different
questions.
Then
I'll
try
to
answer
them
in
turn.
So,
yes,
in
principle,
fabric
is
indeed
made
so
that
you
can
have
the
nodes
communicating
between
different
machines
right
now,
with
the
parts
don't
have
for
the
peers
and
orders
they
don't
have
ingresses.
This
is
one
of
the
next
things
that
we
want
to
update
them
with
in
order
to
allow
communication
from
they're.
A
A
A
So
basically
one
here
so
basically
all
you
need
to
do
is
to
change
the
image
tag
to
1.0.0
you
may
it
might.
You
might
actually
need
to
specify
slightly
different
tag.
You
will
need
to
check
on
the
docker
hub
because
it
we
might
need
to
specify
the
architecture
of
the
machine
as
well,
but
that's
basically
all
you
need
that
will
essentially
select
a
different
docker
container
when
you're
running
the
chart
to
deploy
to
kubernetes
and
that's
that's
all.
A
A
A
Right
here,
so
it's
related
to
the
previous
question,
and
you
can
also
use
the
see
also
for
user
creation
and
authentication.
So
basically,
you
can
also
enroll
a
client
or
a
user.
This
is
a
bit
more
for
more
advanced
kind
of
fabric
fabric
see,
and
it's
essentially,
the
best
thing
to
do
is
to
go
into
the
fabric
samples
repository,
which
has
a
very
very
detailed
example
of
how
the
fabric
CA
works.
As
I
mentioned,
it
starts
with
a
presentation.
A
A
Okay,
so
this
is
the
multi
host
environment.
This
is
again
so
in
a
sense,
a
kubernetes
is
a
multi
host
environment,
in
the
sense
that
you
are
actually
running
it
on
multiple
machines.
If
you
want
to
have
a
multi,
kubernetes
or
multi
clustered
the
deployment,
then
you
need.
We
need
to
actually
update
the
charts,
as
we
mentioned,
to
have
an
ingress
so
that
you
can
communicate
with
them
from
outside
the
core
needs.
Cluster
Ricky.
A
Have
you
done
any
production
deployments
using
composer
heeis
how's
the
performance
as
compared
to
native
fibers,
your
fabric?
We've
done
a
number
of
kind
of
proof-of-concept
deployments
with
the
using
composer
and
the
performance
was
decent.
It's
a
it's.
Of
course.
You
cannot
yet
handle
thousands
of
transactions,
but
we
haven't
yet
formally
compared
to
native
hydrangea
fabric.
A
A
As
far
as
I'm
aware,
you
can
only
deploy
an
order
with
a
single
organization,
especially
if
you're
using
Kafka,
because
the
actual
notes
they
need
to
be
in
order
to
for
the
ordering
service
to
work
well,
and
you
need
all
the
orders
to
be
more
or
less
full
of
ated
with
the
card
cluster
in
close
proximity
and
don't
take
my
word
for
it,
but
but
from
what
I
read
in
their
documentation,
you
cannot
yet
deploy
orders
movie
in
a
movie
organization.
You
can
deploy
peers
in
multi
organisation,
but
not
the
orders.
A
Communities
that
mean,
if
some
something
will
get
admin
private
key
for
kubernetes
cluster
or
one.
This
person
can
crash
the
whole
organization
Network.
So
here
is
the
yeah.
Here's
again
the
case
where
we
view
the
whole
point
of
the
fabricc
is
to
enable
you
to
revoke
certificates,
which
will
enable
Spacek,
aliy
disabled,
specific
private
key.
A
Okay
ease,
it
is
very
much
required,
but
it
is
part
of
the
Kafka
chart.
We
haven't
shown
it
in
them
in
the
values
file,
because
the
values
file
for
Kafka
is
very
very
longer,
but
it
actually
is
possible
to
either
create
Auto,
creates
a
zookeeper
ensemble
or
to
use
a
separate
zookeeper
ensemble
that
you
might
have
created
in
a
separate
chart.
A
Okay,
this,
this
is
again
one
of
the
multiple
Kafka
cluster
questions.
We've
already
answered
that
before
what
is
the
minimum
number
of
nodes
required
in
fabric
development
and
production
use,
so
the
very
minimum
that
number
of
nodes
that
is
kind
of
required
to
actually
have
a
cluster
is
to
as
if
this,
what
we
demonstrated
here,
we
demonstrated
like
the
simplest
possible
production,
ish
deployment
with
two
orders
and
two
peers.
A
A
Any
chance
we
could
get
access
to
that
chart
on
composer,
yes,
very
much
so
actually
it
is
already
open
source.
It
is
actually
undergoing
review
on
the
open
source.
Elm
slash
child
purple
tree.
So
you
can
actually
see
that
pull
request.
And
if
you
want
you
can
you
can
actually
clone
a
repository
for
charts
and
multicharts
elf
and
potentially
install
like
just
unbolt
it
and
install
it
from
your
local
computer
onto
your
own
kubernetes
cluster,
where
you
can
send
it
to
a
art
museum
that
you
own
or,
and
you
can
deploy
it
that
way.
A
A
A
If
we
change,
they
don't
have
to
be
using
for
strong
tool,
data
got
changed.
What
the
in
the
production
sound
does
the
same,
so
the
cow
GP
is
meant
to
act
as
actually
a
world
state
database.
It
doesn't
maintain
the
ledger
itself.
The
ledger
is
actually
maintained
on
disk
on
the
peers.
Only
so
actually
changing
something
comes
to
me
will
not
change
the
the
blockchain.
A
A
Okay
and
what
are
the
best
online
resources
to
learn,
creating
decentralized
apps
using
hi
pleasure,
so
I
think
the
EDX
course
that
has
been
done
by
the
Linux
Foundation
is
very
good.
As
we
mentioned,
we
have
a
composer
chapter.
There.
I
also
have
a
course
on
udemy
impact
which
we'll
share
again,
we'll
mention
it
on
the
on
day,
repository
and
I.
Think
in
the
links
for
this
also,
they
have
older
course
is
that
they
run
that
are
also
I'm
sure
very
good.
A
When
should
we
use
cello,
and
when
should
we
use
kubernetes
and
they're
not
actually
mutually
exclusive
and
cello
is
able
to
deploy
using,
it
can
have
an
unstable
deployer
and
the
cornet
is
the
player,
so
the
guys
actually
working
with
pronounced
the
blurring.
This
is
why
we've
been
chatting
because
they
help
charge
that
we
use,
might
make
it
easier
for
cello
to
deploy
these
components
so
they're,
actually
not
mutually
exclusive.
A
Ok,
the
next
question
is,
is
having
the
pure
database
inside
the
container.
I
risk
lose
it
how
to
cope
with
that
risk,
so
actually
the
database,
the
actual
blockchain,
is
not
inside
the
container.
It's
actually
on
a
disk,
so
the
container
itself
is
ephemeral
and
if
it
dies,
it
gets
restarted.
Essentially,
you
deploy
new
container,
but
the
actual
data
is
on
a
on
a
hard
disk
somewhere,
potentially
on
the
cloud,
if
you're,
using
a
managed
service
or
on
your
own
computers
using
bare
metal
kubernetes.
A
A
You
know
to
create
Business,
Network
archives
that
you
can
install
in
your
peers
or
you
use
the
native
fabric
system
and,
if
you're
using
native
fabric,
you
typically
will
need
to
sign
the
chain
code
to
actually
demonstrate
that
this
is
valid
chain
code
that
you
are
able
to
develop,
deploy
onto
your
cluster.
If
this
jingle
is
not
signed,
you
will
not
actually
be
able
to
deploy
it.
A
Do
you
work
in
case
use
case
for
auto-scale
the
fabric
nodes
and
automatically
add
peers
to
the
channels?
No,
and
the
reason
is
you
cannot
in
order
to,
we
don't
actually
have
an
auto
scale.
This
is
something
that,
if
you're
interested
in
developing
it
will
be
quite
cool.
I
think
this
is
really
cool
idea,
but
there
is
no
such
system
as
far
as
I
know,
I
I
think
that's
my
answer.
We
have
a
lot
of
questions,
but
if
you
want
to,
if
any
of
your
questions
went
unanswered,
please
feel
free
to
contact
us.