Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 1. Connectivity Link 1.3 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.3 release notes
Copiar enlace

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 Kuadrant community project. Connectivity Link provides a control plane for configuring and deploying ingress gateways and policies based on the Kubernetes Gateway API standard. Connectivity Link supports OpenShift Service Mesh 3.2 as the Gateway API provider, which is based on the Istio community project.

See the Red Hat Connectivity Link Life Cycle Policy for details about version support and OpenShift Container Platform compatibility.

1.1.1. New features and enhancements
Copiar enlace

You can use the new features and enhancements that are available with Red Hat Connectivity Link 1.3.

CoreDNS integration for on-premise DNS is Generally Available
Connectivity Link 1.3 provides integration with CoreDNS for on-premise DNS as a Generally Available feature. For more information, see About using on-premise DNS with CoreDNS.
Updated Observability documentation is now available
Connectivity Link 1.3 includes enhanced Observability documentation, including configuring access logs, tracing, and request correlation. For more information, see Red Hat Connectivity Link observability.

1.1.2. Known issues
Copiar enlace

Connectivity Link 1.3 has two known issues.

  • When the disk storage option is enabled in the Limitador custom resource (CR), both the initial limitador deployment and Operator update get stuck on a Multi-Attach error because of the persistent volume claim (PVC) volume. As a workaround, you can change the limitador deployment strategy to "Recreate" and the reconcilation process works as expected. (CONNLINK-855)
  • When either the Redis or RedisCached storage option is set in a Limitador CR and the limitador pod gets restarted for any reason, the first request to the gateway is never rate-limited. All http requests after this are rate-limited. (CONNLINK-856)
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red HatVolver arriba