Multi-tenancy in the Kibana Sever

[spalger]

We should allow creating an arbitrary number of "servers" with different configs.

These "servers" may just be express routers, or middleware functions, but it should allow running different Kibana servers at specific base paths, or via different hostnames on the same server and port.

[xycloud]

mark

[pemontto]

Will likely depend on #5071

[sumancherukuri]

We need this feature. At present, we run multiple instances of Kibana which is not scaling well for us.

[gregwjacobs]

+1

[natebunton]

+1

[rhoboat]

Sometimes developers need to run two or more instances of Kibana while comparing their outputs. These could be connected to the same Elasticsearch server. Normally what people do is start the first server with yarn start and the second with yarn start --no-base-path --server.port 5611 --optimize.watchPort 5613 --kibana.index .kibana-2.

• We should provide this info for people in the contributing doc.
• Maybe it's worth also supporting this kind of server setup with a handy yarn command? yarn start --instance=n for the nth instance, and that would set port, watchPort, and kibana index for you?
• Maybe additionally we could allow multiple Kibana dev servers to be started via node scripts/functional_tests_server --config=multi_instance_config, where the config has something like:

...
  kbnTestServer: {
    // all the same stuff plus...
    instances: n
  },
...

/cc @elastic/kibana-platform @elastic/kibana-operations Thoughts?

[rhoboat]

^ i know that comment reads like i thought of this for the first time, it's because i didn't know about this issue. sorry! :)

[tylersmalley]

This issue is stale and is not consistent with how we're currently discussing multi-tenenacy.