Strip data streams from test Kubernetes (#474)

* Strip data streams from test kubernetes

* Remove other defs

Author: mtojek

test/packages/kubernetes/_dev/build/docs/README.md

@@ -1,84 +1,4 @@
 # Kubernetes integration
 
 This integration is used to collect metrics from 
-[Kubernetes clusters](https://kubernetes.io/).
-
-As one of the main pieces provided for Kubernetes monitoring, this integration is capable of fetching metrics from several components:
-
-- [kubelet](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/)
-- [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics)
-- [apiserver](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/)
-- [controller-manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/)
-- [scheduler](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/)
-- [proxy](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/)
-
-Some of the previous components are running on each of the Kubernetes nodes (like `kubelet` or `proxy`) while others provide
-a single cluster-wide endpoint. This is important to determine the optimal configuration and running strategy
-for the different datasets included in the integration.
-
-For a complete reference on how to configure and run this package on Kubernetes as part of a `DaemonSet` and a `Deployment`,
-there's a complete [example manifest](https://github.com/elastic/beats/blob/master/deploy/kubernetes/elastic-agent-kubernetes.yaml)
-available.
-
-#### Kubernetes endpoints and metricsets
-
-Kubernetes module is a bit complex as its internal datasets require access to a wide variety of endpoints.
-
-This section highlights and introduces some groups of datasets with similar endpoint access needs. 
-For more details on the datasets see `configuration example` and the `datasets` sections below.
-
-
-#### node / system / pod / container / module / volume
-
-The datasets `container`, `node`, `pod`, `system` and `volume` require access to the `kubelet endpoint` in each of
-the Kubernetes nodes, hence it's recommended to include them as part
-of an `Agent DaemonSet` or standalone Agents running on the hosts.
-
-Depending on the version and configuration of Kubernetes nodes, `kubelet` might provide a read only http port (typically 10255),
-which is used in some configuration examples. But in general, and lately, this endpoint requires SSL (`https`) access
-(to port 10250 by default) and token based authentication.
-
-
-##### state_* and event
-
-All datasets with the `state_` prefix require `hosts` field pointing to `kube-state-metrics`
-service within the cluster. As the service provides cluster-wide metrics, there's no need to fetch them per node,
-hence the recommendation is to run these datasets as part of an `Agent Deployment` with one only replica.
-
-Note: Kube-state-metrics is not deployed by default in Kubernetes. For these cases the instructions for its
-deployment are available [here](https://github.com/kubernetes/kube-state-metrics#kubernetes-deployment). 
-Generally `kube-state-metrics` runs a `Deployment` and is accessible via a service called `kube-state-metrics` on
-`kube-system` namespace, which will be the service to use in our configuration.
-
-state_* datasets are not enabled by default.
-
-#### apiserver
-
-The apiserver dataset requires access to the Kubernetes API, which should be easily available in all Kubernetes
-environments. Depending on the Kubernetes configuration, the API access might require SSL (`https`) and token
-based authentication.
-
-#### proxy
-
-The proxy dataset requires access to the proxy endpoint in each of Kubernetes nodes, hence it's recommended
-to configure it as a part of an `Agent DaemonSet`.
-
-#### scheduler and controllermanager
-
-These datasets require access to the Kubernetes `controller-manager` and `scheduler` endpoints. By default, these pods
-run only on master nodes, and they are not exposed via a Service, but there are different strategies
-available for its configuration:
-
-- Create `Kubernetes Services` to make `kube-controller-manager` and `kube-scheduler` available and configure
- the datasets to point to these services as part of an `Agent Deployment`.
-- Run these datasets as part an `Agent Daemonset` (with HostNetwork setting) with a `nodeSelector` to only run on Master nodes.
-
-These datasets are not enabled by default.
-
-Note: In some "As a Service" Kubernetes implementations, like `GKE`, the master nodes or even the pods running on
-the masters won't be visible. In these cases it won't be possible to use `scheduler` and `controllermanager` metricsets.
-
-## Compatibility
-
-The Kubernetes package is tested with Kubernetes 1.13.x, 1.14.x, 1.15.x, 1.16.x, 1.17.x, and 1.18.x
-
+[Kubernetes clusters](https://kubernetes.io/).