Specify which context to use with "KubeConfig" auth type #26665
Labels
Contribfest
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
internal/k8sconfig
priority:p2
Medium
Stale
Comments
overmeulen
added
enhancement
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Sep 19, 2023
This was referenced Oct 3, 2023
hypnoce
added a commit
to hypnoce/opentelemetry-collector-contrib
that referenced
this issue
Oct 6, 2023
…auth_type` (open-telemetry#26665) Signed-off-by: JACQUES Francois <[email protected]>
TylerHelmuth
pushed a commit
that referenced
this issue
Oct 6, 2023
…auth_type` (#26665) (#27240) **Description:** Support specifying context for `kubeConfig` `auth_type` when communicating with a Kubernetes cluster. **Link to tracking Issue:** 26665 **Testing:** unit test added **Documentation:** kubeletstatsreceiver README updated Signed-off-by: JACQUES Francois <[email protected]>
TylerHelmuth
added
priority:p2
jmsnll
pushed a commit
to jmsnll/opentelemetry-collector-contrib
that referenced
this issue
Nov 12, 2023
…auth_type` (open-telemetry#26665) (open-telemetry#27240) **Description:** Support specifying context for `kubeConfig` `auth_type` when communicating with a Kubernetes cluster. **Link to tracking Issue:** 26665 **Testing:** unit test added **Documentation:** kubeletstatsreceiver README updated Signed-off-by: JACQUES Francois <[email protected]>
TylerHelmuth
added
help wanted
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
This seems to be solved by #27240, can this be closed? @dmitryax @TylerHelmuth |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
internal/k8sconfig
Is your feature request related to a problem? Please describe.
I have a kubeconfig with multiple clusters and multiple contexts.
It does not seem possible today to specify which context to use when using "KubeConfig" auth type.
For example if I want to monitor a cluster that is not the one refrerenced in the "current-context" using the kubeletstats receiver.
Describe the solution you'd like
I would like to be able to specify the context I want to use:
receivers:
kubeletstats:
collection_interval: 20s
auth_type: "kubeConfig"
context: "my-secondary-k8s-context"
insecure_skip_verify: true
endpoint: "${env:K8S_NODE_NAME}"
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: