Merge pull request #830 from datawire/docs/0.40-changelog

update for 0.40

CHANGELOG.md

@@ -40,6 +40,24 @@ Format:
 --->
 
 <!--- CueAddReleaseNotes --->
+## [0.40.0] September 25, 2018
+
+### Minor changes:
+
+- Feature: Allow users to override the `STATSD_HOST` value (#810). Thanks to @rsyvarth.
+- Feature: Support LightStep distributed tracing (#796). Thanks to @alexgervais.
+- Feature: Add service label in Helm chart (#778). Thanks to @sarce.
+- Feature: Add support for load balancer IP in Helm chart (#765). Thanks to @sarce.
+- Feature: Support prometheus mapping configurations (#746). Thanks to @bcatcho.
+- Feature: Add support for `loadBalancerSourceRanges` to Helm chart (#764). Thanks to @mtbdeano.
+- Feature: Support for namespaces and Ambassador ID in Helm chart (#588, #643). Thanks to @MichielDeMey and @jstol.
+- Bugfix: Add AMBASSADOR_VERIFY_SSL_FALSE flag (#782, #807). Thanks to @sonrier.
+- Bugfix: Fix Ambassador single namespace in Helm chart (#827). Thanks to @sarce.
+- Bugfix: Fix Helm templates and default values (#826).
+- Bugfix: Add `stats-sink` back to Helm chart (#763).
+- Bugfix: Allow setting `timeout_ms` to 0 for gRPC streaming services (#545). Thanks to @lovers36.
+- Bugfix: Update Flask to 0.12.3 
+
 ## [0.39.0] August 30, 2018
 [0.39.0]: https://github.com/datawire/ambassador/compare/0.38.0...0.39.0
 

docs/reference/running.md

@@ -127,6 +127,10 @@ The list syntax (shown in `mapping_used_2` above) permits including a given obje
 
 If no `AMBASSADOR_ID` is assigned to an Ambassador, it will use the ID `default`. If no `ambassador_id` is present in a YAML object, it will also use the ID `default`.
 
+## `AMBASSADOR_VERIFY_SSL_FALSE`
+
+By default, Ambassador will verify the TLS certificates provided by the Kubernetes API. In some situations, the cluster may be deployed with self-signed certificates. In this case, set `AMBASSADOR_VERIFY_SSL_FALSE` to `true` to disable verifying the TLS certificates.
+
 ## Reconfiguration Timing Configuration
 
 Ambassador is constantly watching for changes to the service annotations. When changes are observed, Ambassador generates a new Envoy configuration and restarts the Envoy handling the heavy lifting of routing. Three environment variables provide control over the timing of this reconfiguration: