Collaborative and visual infrastructure as design for Hybridnet
Components (16)
The Meshery model for Hybridnet supports the following components.
remote-cluster
remote-endpoint-slice
remote-subnet
remote-vtep
ip-instance
network
node-info
subnet
bgp-configuration
cluster-information
felix-configuration
global-network-policy
global-network-set
host-endpoint
ip-pool
network-policy
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 Hybridnet
Related Tutorials for Hybridnet
Related Models in Cloud Native Network
- Ambassador
- APISIX Ingress Controller
- AWS API Gateway
- AWS API Gateway v2
- AWS App Mesh
- AWS CloudFront
- AWS Load Balancer
- AWS Route 53
- AWS Route 53 Resolver
- AWS Target Group Binding
- AWS VPC CNI
- Azure Application Gateway
- Azure Entra
- Azure Network
- Azure Network Front Door
- BFE
- Cilium
- Citrix Service Mesh
- Cloudcore
- CNI Host NIC
- Consul
- Contour
- Contrail Analytics
- Emissary Ingress
- HAProxy Kubernetes Ingress
- Ingress Azure
- Inlets Operator
- Istio
- Istio Operator
- Istio Rate Limit Operator
- Kong API Gateway
- Kong Mesh
- Kuma
- Linkerd
- LoxiLB
- Metallb
- NGINX
- NGINX Ingress Controller
- NGINX Service Mesh
- Open Service Mesh
- OpenELB
- Whereabouts