Add helm chart (#110)

* Add helm chart

* Fix config map indent

.gitignore

@@ -59,6 +59,13 @@ coverage.txt
 #Goland
 .idea/
 
+# helm 
+deploy/k8s/talaria/rendered.*
+
 # binaries
 talaria
 .ignore
+
+# keep talaria directory
+!deploy/helm/talaria
+

README.md

@@ -133,7 +133,10 @@ then replace `local` in the `docker build` command.
 
 ### Kubernetes
 
-WIP. TODO: add info
+A helm chart can be used to deploy talaria to kubernetes
+```
+helm install xmidt-talaria deploy/helm/talaria/
+```
 
 ## Deploy
 

deploy/helm/talaria/.helmignore

@@ -0,0 +1,21 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj

deploy/helm/talaria/Chart.yaml

@@ -0,0 +1,23 @@
+apiVersion: v2
+name: talaria
+description: A Helm chart to deploy talaria to Kubernetes
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+version: 0.1.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application.
+appVersion: 1.16.0
+
+dependencies: