Skip to content

[META][Kubernetes provider/Kubernetes module] Set watcher options node based on configuration #40246

Description

@constanca-m

We need to do similar work for node as we did for namespace in this issue.

  • [Beats] In beats, check node option is being taken into consideration. For example, the watcher is not using the node option for deployment:
    if metaConf.Deployment {
    replicaSetWatcher, err = kubernetes.NewNamedWatcher("resource_metadata_enricher_rs", client, &kubernetes.ReplicaSet{}, kubernetes.WatchOptions{
    SyncTimeout: config.SyncPeriod,
    Namespace: config.Namespace,
    HonorReSyncs: true,
    }, nil)
  • [Beats] Check add_kubernetes_metadata node option as well
  • [Beats] Update documentation
  • [Elastic Agent] Check the Kubernetes provider uses the node option
  • [Integrations] Put the node option at group level, similar as we did for namespace here.

Activity

  1. botelastic commented on Jul 15, 2024

    @botelastic

    This issue doesn't have a Team:<team> label.

  2. botelastic commented on Jul 15, 2025

    @botelastic

    Hi!
    We just realized that we haven't looked into this issue in a while. We're sorry!

    We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
    Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stalledneeds_teamIndicates that the issue/PR needs a Team:* label

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions