Is there any plans to implement automatic service discovery to identify backend targets?

[tejaswiniVadlamudi]

As mentioned in the subject, does Trickster have plans to implement service discovery, I'm thinking about Kubernetes-based service discovery, Prometheus design can be taken as inspiration (see https://prometheus.io/docs/prometheus/latest/configuration/configuration/#kubernetes_sd_config).

[jranson]

hey @tejaswiniVadlamudi, thanks for requesting this feature! @jakenichols2719 is currently working on implementing it, and has submitted a draft-status PR #615 to allow the community to review the approach while development is ongoing.

Right now, we're supporting kube api queries, but the goal is to eventually support multiple methods of service discovery (e.g., querying etcd, querying a DNS record, etc.) based on the most popular use cases.

Let us know if you have any questions or feedback!

[jnichols-git]

Hello! Just wanted to give an update on how this is going. PR #675 addresses autodiscovery for Kubernetes services (externally) or pods (internally) with specific names or labels. Any discovered backend will be added to the ALB with discovery configured.

[petemounce]

Are there plans to support discovery in the absence of a kubernetes cluster? I'm thinking here of equivalents to prometheus' ec2, gce, and consul SDs.