At this point, the cluster is now fully functional. All that is left is to install Metricbeat and Filebeat onto the other nodes of the cluster to ensure full visibility of the cluster's health and resource usage.
Adding more clients to the cluster is a matter of installing the appropriate Beat, depending on what needs to be monitored and which logs need to be indexed.
If load increases on the cluster, a number of options are available—either adding more nodes to the cluster to load balance requests or increasing the number of available resources for each of the nodes. In certain scenarios, simply adding more resources is a more cost-effective solution as it doesn't require a new node to be configured.
An implementation such as this one can be used to monitor the performance and events of a Kubernetes setup (such as the one described in Chapter 11, Designing...