Add new track for tsdb based on k8s integration

[martijnvg]

This track indexes generated k8s pod and k8s container data based on the k8s integration and then test performance of searches that are based on k8s integration visualisations. See README for more details.

[inqueue]

This is looking good, thank you. I left some README suggestions and have not executed the track yet.

Can you add track parameters for number_of_shards and number_of_replicas, if it makes sense to do so?

[martijnvg]

Thanks for taking a look @inqueue. I updated the track.

Can you add track parameters for number_of_shards and number_of_replicas, if it makes sense to do so?

I think it makes sense and I added the track params.

[dliappis]

This is a great and awesome amount of work, thank you!

I have been able to run this benchmark (it's ongoing, will report when it succeeds).

Left a suggestion to clarify a little about what the touch-... tasks are doing and also clarify some sentences in the readme.

[dliappis]

LGTM

Left two comments, one for a minor typo, and another for a suggestion to move all the variables in track.json for better discoverability. Up to you if you want to implement the suggestion.

[dliappis]

The above two seem to be used also in challenges/default.json; does it make more sense to move them, as well as the variables from challenges/default.json:

{% set search_iterations = 20 %} 
{% set search_warmup_iterations = 50 %}
{% set target_interval = 4 %}

to a centralized place, e.g. at the top of track.json (right after {% import "rally.helpers" as rally with context %}) for better discoverability? If you choose to do that, remember to update the references in README.md.

[martijnvg]

This makes sense to me. I will update this PR.

[dliappis]

This makes sense to me. I will update this PR.

LGTM also after 5ea2206

[inqueue]

LGTM, thanks!