Add nop exporter to distributions (#566)

* Add nop exporter to distributions
Fixes #564

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

* add nop exporter as exception to the readme

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

---------

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>

Author: jpkrohling

distributions/otelcol-k8s/README.md

@@ -14,5 +14,5 @@ The full list of components is available in the [manifest](manifest.yaml).
    - Although you could run a Collector in Kubernetes to reach out to any endpoint, this distribution is not targeting that use case. This distribution is for monitoring Kubernetes and the processes it runs. 
  - All components must be vendor-neutral.
  - Only exporters that use OTLP are allowed.
-   - To facilitate troubleshooting, the debug exporter and file exporter are exceptions.
+   - To facilitate troubleshooting, the nop, debug, and file exporters are exceptions.
  - All technologies OTel promised to support will be included as receivers. Specifically this means the `jaegerreceiver`, `zipkinreceiver`, `opencensusreceiver`, and `prometheusreceiver` will be included.

distributions/otelcol-k8s/manifest.yaml

@@ -21,6 +21,7 @@ extensions:
 
 exporters:
   - gomod: go.opentelemetry.io/collector/exporter/debugexporter v0.101.0
+  - gomod: go.opentelemetry.io/collector/exporter/nopexporter v0.101.0
   - gomod: go.opentelemetry.io/collector/exporter/otlpexporter v0.101.0
   - gomod: go.opentelemetry.io/collector/exporter/otlphttpexporter v0.101.0
   - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/fileexporter v0.101.0