configuration even more robust has been a major focus for this cycle for SIG Cluster Lifecycle (see the May 6, 2019 [Community Update](https://docs.google.com/presentation/d/1QUOsQxfEfHlMq4lPjlK2ewQHsr9peEKymDw5_XwZm8Q/edit?usp=sharing)). Bug fixes across bare metal tooling and production-ready user stories, such as the high availability use cases have been given priority for 1.15.

kubeadm, the cluster lifecycle building block, continues to receive features and stability work required for bootstrapping...

`GetPhysicallyInstalledSystemMemory` to get the physical memory installed on Windows machines and reports it as part of node metrics to heapster. This API call fails for VMware and VirtualBox virtualization environments. This issue is not present in bare metal Windows deployments, in Hyper-V, or on some of the popular public cloud providers.

*   If you run `kubectl get po` while the API server in unreachable, a misleading error is returned: `the server doesn't have a resource type "po"`....

header1,header2,header3 ok1,ok2,ok3 a,"b c"d,e invalid-badstartline2.csv header1,header2,header3 ok1,ok2,ok3 a,b "d e invalid-badtrailingq.csv header1,header2,header3 ok1,ok2,ok3 "a word",b" invalid-crlfquoted.csv header1,header2,header3 ok1,ok2,ok3 "foo"bar" invalid-csv.csv header1,header2,header3 ok1,ok2,ok3 a""b,c invalid-oddquote.csv header1,header2,header3 ok1,ok2,ok3 """"""",b,c endswithhalfsep.csv a,b,c%!a2,b2,c2%...

* Update JWT docs to use Python-jose instead of PyJWT. Initial PR [#1610](https://github.com/tiangolo/fastapi/pull/1610) by [@asheux](https://github.com/asheux).
* Fix/re-enable search bar in docs. PR [#1703](https://github.com/tiangolo/fastapi/pull/1703).
* Auto-generate a "server" in OpenAPI `servers` when there's a `root_path` instead of prefixing all the `paths`: