- upgrade helm to 2.14, and install the [helm-tiller](https://github.com/rimusz/helm-tiller) plugin to run in "tillerless" mode - with a local tiller instance
- also add support to create RBAC resources in the loadtester chart, because when running in tillerless mode, the pod service account will be used instead of the tiller one - so we need to give him specific permissions
this allow the use of the loadtester to run `helm test` in tillerless mode, with `helm tiller run -- helm test` for example
Copy this file https://github.com/grpc/grpc-proto/blob/master/grpc/health/v1/health.proto into the ghz folder for use when promoting a canary running a grpc service.
This repo describes the file:
> This repository contains common protocol definitions for peripheral services around gRPC such as health checking, load balancing etc..
Any app that chooses to implement this interface (which imo should be any grpc service exposing a health check) will then be able to use this without providing reflection.
I'm not a grpc expert so I'm not sure what the best practices are around allowing reflection on the server but this seems like a simple solution for those who choose not to enable it.
Slack discussion on the weave users slack is here - https://weave-community.slack.com/archives/CGLQLLH9Q/p1566358441123400
You can utilize this file like so
`/ghz --proto=/tmp/health.proto --call=grpc.health.v1.Health/Check ...`
