Update Documentation (#167)

docs/content/envoy/deploy.en.md

@@ -28,7 +28,32 @@ There are many ways to deploy Envoy and a lot depends on your internal infrastru
 
 ### Using Kubernetes
 
-Coming Soon!
+The easiest way to install Envoy on Kubernetes is to use our [helm chart](https://artifacthub.io/packages/helm/trisacrypto/envoy). A simple one liner for the install would be:
+
+```
+helm install [RELEASE] trisacrypto/envoy \
+    --set isTestnet=true \
+    --set trisa.endpoint=testnet.vaspname.com:443 \
+    --set trisa.web.origin=https://envoy.vaspname.com \
+    --set certificate.name=testnet.vaspname.com.pem
+    --set certificate.data=$(base64 -i ./secrets/testnet.vaspname.com.pem)
+```
+
+The placeholders above are as follows:
+
+- `[RELEASE]`: the name of the release for helm, usually vaspname and vaspname-testnet.
+- `testnet.vaspname.com:443`: the TRISA endpoint for peer-to-peer travel rule information exchanges whose domain matches those issued for your certificates.
+- `https:///envoy.vaspname.com`: the URL where you would like to hose the Envoy UI and API in order to interact with the Envoy node.
+- `testnet.vaspname.com.pem`: by convention, the certificate name is the name of the domain followed by the .pem extension.
+- `./secrets/testnet.vaspname.com.pem`: path to the decrypted certificates issued to you by the Global directory service.
+
+To uninstall the chart:
+
+```
+helm uninstall [RELEASE]
+```
+
+See the [Envoy helm chart documentation](https://artifacthub.io/packages/helm/trisacrypto/envoy) for more on how to use a values file, manage secrets such as certificates, or just see the types of Kubernetes objects being generated by the chart so that you can create your own deployments.
 
 ### Using systemd