<commit_before># Using Helm with Lostromos

In order to make migrating to lostromos easier we support using helm to handle
the templating. This allows you to provide a helm chart to lostromos.

## Tiller

For Lostromos to be able to run commands with Helm it needs access to a tiller.
If you are running inside kubernetes the value for this would look like
`tiller-deploy:44134` if the tiller is in the same namespace as your Lostromos
deployment. If you are in a different namespace you would use
`tiller-deploy.<namespace>:44134`.

## Running outside the cluster

If you are running outside of the kubernetes cluster access to the tiller is a
little more complicated. It is not a good idea to expose the tiller outside of
the cluster since it is not secure by default. Meaning your best option is to
use the `kubectl port-forward` command. This is a simple set of commands you can
run that will setup a port forward for you that will work with the default tiller deployment.

```bash
export TILLER_NS=kube-system
export TILLER_POD=`kubectl -n $TILLER_NS get pods \
       --selector=app=helm,name=tiller \
       -o jsonpath="{range .items[*]}{@.metadata.name}{end}" | head -n1`
kubectl port-forward -n $TILLER_NS $TILLER_POD 44134:44134<commit_msg>Adding helm version to the docs<commit_after># Using Helm with Lostromos

In order to make migrating to lostromos easier we support using helm to handle
the templating. This allows you to provide a helm chart to lostromos.

## Tiller

For Lostromos to be able to run commands with Helm it needs access to a tiller.
If you are running inside kubernetes the value for this would look like
`tiller-deploy:44134` if the tiller is in the same namespace as your Lostromos
deployment. If you are in a different namespace you would use
`tiller-deploy.<namespace>:44134`.

## Version

Helm requires the the tiller and the client be running the same version.
Currently Lostromos uses version v2.7.0 of helm.

## Running outside the cluster

If you are running outside of the kubernetes cluster access to the tiller is a
little more complicated. It is not a good idea to expose the tiller outside of
the cluster since it is not secure by default. Meaning your best option is to
use the `kubectl port-forward` command. This is a simple set of commands you can
run that will setup a port forward for you that will work with the default tiller deployment.

```bash
export TILLER_NS=kube-system
export TILLER_POD=`kubectl -n $TILLER_NS get pods \
       --selector=app=helm,name=tiller \
       -o jsonpath="{range .items[*]}{@.metadata.name}{end}" | head -n1`
kubectl port-forward -n $TILLER_NS $TILLER_POD 44134:44134
{'fraction_non_alphanumeric': 0.05725047080979284, 'fraction_numerical': 0.01694915254237288, 'mean_word_length': 4.24901185770751, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2298864', 'n_tokens_mistral': 817, 'n_tokens_neox': 761, 'n_words': 397}