Service Mapping for containerized environments using KVA
Summarize
Summary of Service Mapping for Containerized Environments Using KVA
Service Mapping for containerized environments uses the Kubernetes Visibility Agent (KVA) to automate the discovery and visualization of application dependencies across Kubernetes clusters and related resources. This solution offers complete visibility into both Kubernetes environments and traditional infrastructures, creating detailed topology maps that illustrate service connections and dependencies.
Show less
Key Features
- Seamless Entry Point Discovery: Start mapping from any application endpoint, such as a URL, with KVA identifying the relevant Kubernetes resources serving that endpoint.
- Complete Kubernetes Topology-Mapping: Visualize traffic flows between Kubernetes pods, displaying workloads and services for flexible analysis of container infrastructures.
- External Dependency Tracking: Automatically detect connections from Kubernetes pods to external resources, enhancing visibility beyond cluster boundaries.
- Bidirectional Discovery: Service maps function effectively regardless of whether the entry point leads to Kubernetes resources or external components, ensuring comprehensive monitoring.
Key Outcomes
- Accelerated Incident Resolution: Gain immediate insights into dependencies to quickly identify root causes during incidents.
- Change Impact Analysis: Visualize dependencies prior to making changes to understand potential impacts and plan maintenance efficiently.
- Application Rationalization: Achieve visibility into services that support critical applications, aiding in resource allocation and reducing technical debt.
- Operational Efficiency: Enhance efficiency by automating discovery processes instead of relying on manual documentation.
- Improved Decision-Making: Utilize accurate topology information to reflect actual application behavior for better strategic decisions.
- Simplified Compliance: Streamline compliance and auditing through automated documentation of service dependencies and data flows.
Getting Started
To start discovering and mapping Kubernetes services, install the latest version of the Kubernetes Visibility Agent (KVA) and ensure all Service Mapping requirements are met. Initiate the discovery process by entering an application entry point into Service Mapping, allowing KVA to identify connections and begin comprehensive topology discovery.
Kubernetes Visibility Agent (KVA) and Service Mapping discover and visualize application dependencies across Kubernetes clusters and related resources, providing complete visibility into containerized environments.
Service Mapping for containerized environments provides automated discovery and visualization of application dependencies across your entire technology stack. Whether your applications run entirely within Kubernetes clusters or span multiple environments including cloud databases, API gateways, and traditional servers, Service Mapping creates comprehensive topology maps that show how services connect and depend on each other.
Service Mapping and KVA combined capabilities transform complex architectures into clear, actionable service maps that help teams troubleshoot faster, assess change impact more accurately, and optimize application performance across environments.
Key capabilities
- Seamless entry point discovery and mapping
- Start with any application endpoint such as a URL or hostname and port, and Service Mapping automatically identifies the corresponding Kubernetes resource serving that endpoint. KVA recognizes multiple Kubernetes exposure methods including load balancers, ingress controllers, NodePort services, Gateway API resources, and OpenShift routes.
- Complete Kubernetes topology-mapping
- Discover and visualize traffic flows between pods within your Kubernetes clusters. Service maps display workloads including deployments, stateful sets, daemon sets, jobs, and cron jobs. You can choose to view either workloads or Kubernetes services on your maps, providing flexibility in how you analyze your container infrastructure.
- External dependency tracking
- Automatically detect connections from Kubernetes pods to external resources including cloud databases, third-party APIs, and traditional infrastructure. KVA resolves DNS connections and Kubernetes ExternalName services to be able to map dependencies beyond cluster boundaries.
- Bidirectional discovery
- Service maps work regardless of whether your entry point leads directly to a Kubernetes resource or to an external component with downstream connections into clusters. This flexibility promotes comprehensive visibility across any architecture.
Use Cases
- Accelerated incident resolution
- When incidents occur, Service Mapping provides immediate visibility into all dependencies, helping teams quickly identify root causes and understand the impact across Kubernetes and traditional infrastructure.
- Change impact analysis
- Before changing Kubernetes deployments, APIs, or infrastructure components, visualize all upstream and downstream dependencies to understand potential impacts and plan maintenance accordingly.
- Application rationalization
- Gain complete visibility into which services support critical business applications, enabling data-driven decisions, resource allocation, and technical debt reduction.
Benefits
- Reduced mean time to resolution through comprehensive visibility into service architectures
- Minimized risk from changes by reviewing dependencies before modifying Kubernetes or infrastructure components
- Improved operational efficiency by automating discovery instead of manually documenting complex service relationships
- Better decision-making through accurate, up-to-date topology information that reflects actual application behavior
- Simplified compliance and audit processes with automated documentation of service dependencies and data flows
Getting Started
Create hybrid application service maps
Enter an application entry point into Service Mapping. KVA automatically identifies whether this entry point connects to Kubernetes resources and initiates comprehensive topology discovery.