feat(chart): proxy to the API

[technosophos]

This feat adds two things:

1. It exposes the nginx config file via a config map. This is useful for tweaking the way Kashti gets served (and could be used for adding auth)
2. It proxies the API calls (anything to /v1/ into the Brigade API server, thus eliminating the need to expose the API server publicly

To test:

Install:

$ helm install -n kashti charts/kashti --set brigade.apiServer="http://brigade-brigade-api.default.svc.cluster.local:7745"

(where the apiServer URL is the in-cluster domain name or IP address to your brigade API server)

Run brig proxy and open the URL in your browser. It should load the full dashboard.

In your browswer's developer tools, load the network view. Then reload the page. You should see the API calls go over localhost:8081/v1 instead of directly against the API server.

[radu-matei]

Manually tested, all API requests are proxied to v1

[radu-matei]

This can also be tested by manually starting the port forward only to the Kashti pod, then making requests to /v1:

$ kubectl port-forward <kashti-pod> 8081:80

$ curl localhost:8081/v1/projects-build
<response from API>