What’s New
What's new in Red Hat Connectivity Link
Abstract
Chapter 1. Connectivity Link 1.2 release notes
Welcome to the Red Hat Connectivity Link release notes, where you can learn about what is new and what is fixed.
1.1. Red Hat Connectivity Link 1.2 release notes
Red Hat Connectivity Link is a modular and flexible solution for application connectivity, policy management, and API management in multicloud and hybrid cloud environments. You can use Connectivity Link to secure, protect, connect, and observe your APIs, applications, and infrastructure.
Connectivity Link is based on the Content from kuadrant.io is not included.Kuadrant community project. Connectivity Link provides a control plane for configuring and deploying ingress gateways and policies based on the Content from gateway-api.sigs.k8s.io is not included.Kubernetes Gateway API standard. Connectivity Link supports OpenShift Service Mesh 3.1 as the Gateway API provider, which is based on the Content from istio.io is not included.Istio community project.
See the This content is not included.Red Hat Connectivity LInk Life Cycle Policy for details about version support and OpenShift Container Platform compatibility.
1.2. New features and enhancements
You can use the new features and enhancements that are available with Red Hat Connectivity Link 1.2.
New custom policy extensions:
- OIDC policy: Low-code approach to authentication
- Plan policy: Definition of usage plans for API consumers
- Telemetry policy: More extensibility with metrics
Al gateway functionalities:
- Token-based rate limiting policy: Control access to Al services by setting limits based on tokens
- Token metrics: Evaluate the performance, efficiency, and resource consumption of Al models and applications
- New builds of Connectivity Link for operation within ARM infrastructure
- Seamless WASM plugin installation
1.3. Technology Preview features
You can try the Technology Preview features that are available with Red Hat Connectivity Link 1.2.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production.
Technology Preview features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information, see Red Hat Technology Preview Features - Scope of Support.
1.3.1. CoreDNS integration for on-premise DNS
Connectivity Link provides integration with Content from coredns.io is not included.CoreDNS for on-premise DNS as a Technology Preview feature. For more information, see the This content is not included.Configure on-premise DNS with CoreDNS (Technology Preview).
1.4. Developer Preview features
Developer Preview features are included in Connectivity Link 1.2.
Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features give you early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and give feedback during the development process.
Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA. For more information, see This content is not included.Red Hat Developer Preview - Scope of Support.
Red Hat customers can give feedback on Developer Preview features through your account teams. You can also ask questions and give feedback directly by using the Content from docs.google.com is not included.Connectivity Link contact form or by emailing This content is not included.rhcl-contactus@redhat.com.
1.4.1. Extension SDK
The Extension SDK is available as a Developer Preview feature.
The Extension SDK provides a framework for developers to build custom policy extensions that integrate with and extend Connectivity Link capabilities beyond core policies, such as AuthPolicy, RateLimitPolicy, TLSPolicy, and DNSPolicy.
Key features include:
- Building custom policy controllers that follow Gateway API policy attachment patterns.
- Integrating with the Connectivity Link control plane using gRPC over a UNIX socket.
- Using the Common Expression Language (CEL) for dynamic configuration evaluated against the Kuadrant context. For example, topology and request data.
- Publishing data bindings to share computed values or CEL programs with downstream components such as Authorino, Envoy WASM filters, or Limitador.
- Subscribing to cluster events to react to changes. For example, changes to gateways, routes, and policies.
- Accessing helper functions to query the Kuadrant topology within CEL expressions. For example, gateways and attached policies.
Example extensions and a developer guide are available in the Kuadrant community repository to help you get started with building your own extensions. For more information, see Content from github.com is not included.Extension SDK.
1.5. Fixed issues
See the included list for bugs that are fixed in Connectivity Link 1.2.
-
Previously, the TokenRateLimitPolicy status switched indefinitely between Accepted/Enforced and MissingDependency. When in the MissingDependency state, the condition message was as follows:
[token rate limit policy validation has not finished] is not installed, please restart Kuadrant Operator pod once dependency has been installed. Now, the TokenRateLimitPolicy status transitions to Accepted/Enforced and remains in that state, and rate limiting rules are consistently enforced by the Limitador component. This content is not included.CONNLINK-595 - Previously, for token exchange flows where the auth header value must be replaced, the added auth headers were appended instead. Now, the added auth headers replace existing values, instead of appending. This content is not included.CONNLINK-604
1.6. Known issues
Listed are the known issues that apply in Connectivity Link 1.2.
- Connectivity Link allows configuration for non-standard response codes. Connectivity Link should not allow configuration that specifies non-standard custom HTTP response codes such as HTTP 333. This content is not included.CONNLINK-287