Update main README.md section Installation.

Mention the haproxy container, and the Helm charts folder.

README.md

@@ -26,19 +26,23 @@ valuable at this early stage.
 
 # Installation
 
-Varnish for the purposes of Ingress and the controller that manages it
-are implemented in separate containers -- one controller can be used
-to manage a group of Varnish instances. The Dockerfiles and other
-files needed to build the two images are in the
-[``container/``](/container) folder, together with a Makefile that
-encapsulates the commands for the build.
+Varnish and haproxy for the purposes of Ingress run together in a Pod,
+and the controller that manages them runs in a separate Pod -- one
+controller can be used to manage a group of Pods implementing
+Ingress. The Dockerfiles and other files needed to build the three
+images are in the [``container/``](/container) folder, together with a
+Makefile that encapsulates the commands for the build.
 
 The resulting images must then be pushed to a registry available to
 the Kubernetes cluster.
 
 The Ingress can then be deployed by any of the means that are
 customary for Kubernetes. The [``deploy/``](/deploy) folder contains
-manifests (YAMLs) for some of the ways to deploy an Ingress.
+manifests (YAMLs) for some of the ways to deploy an Ingress, using
+tools such as
+[``kubectl``](https://kubernetes.io/docs/reference/kubectl/overview/). The
+[``charts/``](/charts) folder contains charts for
+[Helm](https://helm.sh/) deployments.
 
 The deployment described in [``deploy/``](/deploy) targets a default
 setup in which the controller runs in the ``kube-system`` namespace