Kuma
Collaborative and visual infrastructure as design for KumaComponents ( 49 )
The Meshery model for Kuma supports the following components.
circuit-breaker
container-patch
dataplane-insight
dataplane
external-service
fault-injection
health-check
mesh-access-log
mesh-circuit-breaker
mesh
mesh-fault-injection
mesh-gateway-instance
mesh-gateway-route
mesh-gateway
mesh-health-check
mesh-http-route
mesh-insight
mesh-proxy-patch
mesh-rate-limit
mesh-retry
mesh-timeout
mesh-trace
mesh-traffic-permission
proxy-template
rate-limit
retry
service-insight
timeout
traffic-log
traffic-permission
traffic-route
traffic-trace
virtual-outbound
zone-egress
zone-egress-insight
zone-ingress
zone-ingress-insight
zone-insight
zone
mesh-load-balancing-strategy
mesh-tcp-route
mesh-metric
mesh-service
mesh-external-service
mesh-passthrough
hostname-generator
hostname-generator
mesh-multi-zone-service
mesh-tls
What are Meshery Models and Components?
Meshery Models and Components represent the fundamental building blocks of your infrastructure. Use them to define the structure and configuration of your infrastructure and deployments by incorporating their use into a Design. Think of Designs as blueprints or templates that encapsulate everything from network configurations to service definitions.
Learn more about Models, Components, Relationships, and Designs
What is the Meshery Registry
The Meshery Registry is a vital component within Meshery, serving as a centralized repository for managing a diverse range of cloud and cloud native resources. It stores and organizes crucial information such as models, categories, components, and relationships, enabling efficient interaction and utilization of these resources within the Meshery ecosystem. You can conveniently access and manage registry data through Meshery UI, and through Meshery CLI (mesheryctl registry).Learn more about the Registry
Designs containing Kuma
Related Models in Cloud Native Network
- Azure Application Gateway
- Ambassador
- APISIX Ingress Controller
- AWS App Mesh
- AWS API Gateway
- AWS API Gateway v2
- AWS CloudFront
- AWS Load Balancer
- AWS Route 53
- AWS Route 53 Resolver
- AWS Target Group Binding
- AWS VPC CNI
- BFE
- Cilium
- Cloudcore
- CNI Host NIC
- Consul
- Contour
- Contrail Analytics
- Citrix Service Mesh
- Emissary Ingress
- Hybridnet
- Ingress Azure
- Inlets Operator
- Istio
- Istio Operator
- Istio Rate Limit Operator
- Kong Mesh
- Kong API Gateway
- HAProxy Kubernetes Ingress
- Linkerd
- Metallb
- NGINX Ingress Controller
- NGINX Service Mesh
- NGINX
- Open Service Mesh
- OpenELB
- Whereabouts