Red Hat Connectivity Link

Connect, secure, and protect your distributed Kubernetes services with lightweight policy attachments.

Next generation multicluster application connectivity and traffic policy management

Gateway API, the next generation of Kubernetes Ingress, simplifies managing ingress traffic into Kubernetes clusters. It introduces resources and components designed with specific roles in mind, aligning with organizational teams such as infrastructure, platform engineering, and application development. Each team interacts with Kubernetes networking and traffic in different ways, and the Gateway API is structured to meet those varying needs.

Red Hat Connectivity Link attaches policies to gateways, enabling features like DNS connectivity, automatic TLS integration, authorization, and rate limiting for ingress traffic. This Kubernetes-native solution ensures seamless traffic management and policy enforcement in a single cluster or across multiple clusters.

Connectivity Link features

Dynamic DNS and multi-cluster routing with failover

Leverage common cloud DNS providers like Route53, Azure, Google DNS, and CoreDNS (coming soon). Auto-populate DNS records and enable multi-cluster connectivity and routing options, such as GEO and weighted responses.

TLS for secure gateway traffic

Provision certificates for gateway listener-hosts through integration with cert-manager and secure traffic to gateways with ACME-based TLS integration, supporting major ACME providers like Let's Encrypt. Manage the entire lifecycle of TLS certificates.

Comprehensive, flexible authorization controls

Target Gateway API networking resources such as HTTP Routes and Gateways, leveraging contextual traffic data (e.g., HTTP attributes, hostnames, user attributes) to enforce authentication rules. Apply auth rules to specific sections of a network resource that allow platform engineers to set default policies that apply until overridden by more specific rules.

Granular rate-limiting control

Enforce rate limits targeting Gateway API resources, such as HTTP Routes and Gateways. Apply limits to specific sections of a network resource that abstracts away the complexity of the underlying rate limit protocols. Cluster operators can define default policies to govern behavior across the network until more specific limits are applied

Observability

Role-based dashboards are featured. Platform engineers see policy compliance, resource usage, error rates, latency, throughput, and multi-cluster insights. Developers focus on API-specific metrics including latency, throughput, requests, and errors. Line of business users view usage trends, requests per second, and SLO metrics.

API design and governance (In Developer Preview)

Apicurio Studio and Apicurio Registry encompass workflow automation, enabling users to efficiently create, validate, and manage API schemas.

Connectivity Link use cases

Multi-cloud and multi-cluster connectivity

Integrate with multiple cloud DNS Providers. Balance and distribute traffic across your different gateways. With multi-cluster gateway support, platform engineers can manage cross-cluster connectivity and policies through a single interface. They can configure ingress gateways that can handle high traffic load balancing and failover across multiple Kubernetes clusters.

Kubernetes-native, standardized Ingress policy management

As organizations scale across multiple teams, clusters, clouds, and VMs, maintaining consistent security and compliance for the ingress traffic becomes crucial. With standardized ingress policy management, teams can enforce uniform policies, role-based access control (RBAC), and compliance measures across their entire infrastructure.

Location-based traffic routing

As application developers build distributed services, they often need to optimize response times and comply with regional regulatory requirements. With location-based routing, they can leverage advanced DNS strategies to direct traffic based on user location, ensuring faster response times and adherence to local regulations.

Developer self-service

Dev teams can handle authentication, rate limiting, and define routing based on paths and headers. By implementing authentication and rate limiting policies as code and automating it through GitOps, streamline API governance, ensuring consistency and scalability across services.

Upstream Connectivity Link community projects

Kuadrant

Kuadrant combines Gateway API and Istio-based gateway controllers to enhance application connectivity. It enables platform engineers and application developers to easily connect, secure, and protect their services and infrastructure across multiple clusters with policies for TLS, DNS, application authentication & authorization, and rate limiting. Additionally, Kuadrant offers observability templates to further support infrastructure management.

Explore Kuadrant.io

Report a website issue