Conversation
Adds detection for Kubernetes pods managed by consul-k8s-endpoints-controller (service mesh sidecar) alongside the existing catalog sync method. The new discovery method extracts pod metadata from Consul mesh Service.Meta and Locality fields, and includes additional Kubernetes metadata tags. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
alecrajeev
approved these changes
Jan 22, 2026
duncaan
deleted the
dschulze/sc-184030/support-consul-service-mesh-discovery
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current Behavior
The library currently supports EKS pod discovery through Consul catalog sync, which identifies Kubernetes pods by the
external-source: kubernetesmetadata set by the catalog sync process.Why do we need this change?
We are migrating from Consul catalog sync to Consul service mesh with sidecar injection. Pods with service mesh sidecars are registered differently in Consul:
consul-k8s-endpoints-controllerinstead of catalog syncThis change allows us to gradually migrate services to the mesh while maintaining discovery for both types of pods.
Implementation Details
map_k8s_consul_mesh_endpoint()method to handle Consul mesh pod metadatamanaged-by: consul-k8s-endpoints-controllerin Service.MetaDependencies (if any)
None
📇 [sc-184030]