Skip to content

Commit

Permalink
[chore] remove obsolete note about auth type limitations in `k8sclust…
Browse files Browse the repository at this point in the history
…erreceiver` (#35853)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

This PR removes the note about `serviceAccount` being the only auth type
being supported by the `k8sclusterreceiver`, since in the meantime
support for `kubeConfig` auth type has been added (also verified this
manually to be safe)

<!--Describe the documentation added.-->
#### Documentation

Updated the readme of the `k8sclusterreceiver`

<!--Please delete paragraphs that you did not use before submitting.-->

Signed-off-by: Florian Bacher <[email protected]>
  • Loading branch information
bacherfl authored Oct 28, 2024
1 parent d66daa3 commit 1338779
Showing 1 changed file with 0 additions and 3 deletions.
3 changes: 0 additions & 3 deletions receiver/k8sclusterreceiver/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,6 @@ The Kubernetes Cluster receiver collects cluster-level metrics and entity events
API server. It uses the K8s API to listen for updates. A single instance of this
receiver should be used to monitor a cluster.

Currently, this receiver supports authentication via service accounts only. See [example](#example)
for more information.

## Metrics

Details about the metrics produced by this receiver can be found in [metadata.yaml](./metadata.yaml) and [documentation.md](./documentation.md).
Expand Down

0 comments on commit 1338779

Please sign in to comment.