Welcome
Cloud Native Link
Cloud Native Link refers to the HCL Link product installation on a Kubernetes cluster.
Limitations
This section details the limitations concerning deployment, configuration, and feature support for the Cloud Native Link.
Deployment and Platform

Introduction
Congratulations on your selection of HCL Link as your data integration solution!
What's New
Release Notes
System requirements
A complete desciption of the hardware and software requirements for both Windows and Linux systems.
Installation
Everything you need to know to install HCL Link.
Administration
Here you will find the tasks that are required for administration of your HCL Link product.
Projects
A project is a container for HCL Link artifacts.
Services
Service definitions define REST services and the endpoints of a service. This guide provides step-by-step instructions for creating, importing, and managing services using the system interface, following Microsoft standards.
Connectors
This documentation describes the connectors and how they are used.
Packages
Servers
This documentation contains a description of the server groups and servers.
Variables
The variables described here include Configuration variables, flow variables, and cache variables.
Dashboards
A description of HCL Link dashboards, including the Server dashboard and the Kibana dashboard.
Runtimes
Descriptions of Link runtime services.
Resource Adapters
About the HCL Link Resource Adapters, and how to use them.
Cloud Native Link
Cloud Native Link refers to the HCL Link product installation on a Kubernetes cluster.
- Overview
  HCL Link offers a Helm chart that facilitates its deployment on Kubernetes. This approach, known as Cloud Native Link, signifies the installation of the HCL Link product within a Kubernetes cluster.
- Cloud Native Link Architecture
- Requirements
  This document lists the hardware and software requirements for installing and running Cloud Native Link.
- Limitations
  This section details the limitations concerning deployment, configuration, and feature support for the Cloud Native Link.
- Installation
  This section provides instructions for installing the HCL Cloud Native Link application on a Kubernetes cluster using the official Helm chart.
- Upgrade and Rollback
  Helm is a Kubernetes package manager that uses charts to define, install, and upgrade even the most complex Kubernetes applications.
- Backup
- Compute Resource Allocation
- Networking
- Storage
- Memory Considerations for Cloud native
- Security
  This section describes how security, authentication, and authorization are managed in HCL Link when deployed in a cloud-native environment.
- Scaling
  This section describes the scaling capabilities and limitations of HCL Link components defined in the Helm chart, focusing on replica management, downtime impact, and autoscaling.
- Logging and Monitoring
  This document explains the logs generated by HCL Link and Kubernetes, how to retrieve them, and the built-in monitoring tools in Link.
- Unica Link Integration
  This document explains how HCL Link integrates with the HCL Unica platform. It provides an overview of deployment patterns and key configuration sections in the HCL Link Helm chart.
- Troubleshooting
- FAQ
  This section answers frequently asked questions about deploying and managing HCL Link in a cloud-native environment.
- Link Helm Chart Parameters
- Reference
Reference
This documentation provides HCL Link reference information.
Notices

Deployment and Platform

Storage and Pod Scheduling

The available storage class affects pod scheduling.

RWO (ReadWriteOnce): When only RWO storage is available, the Server, Rest, and Executor pods must run on the same node.
RWX (ReadWriteMany): When RWX storage is available and used (for example, to share custom connector PVs), these pods can run on different nodes.

Deployment Replicas

Only the Executor deployment supports horizontal scaling.

The Client, Server, and Rest deployments do not support multiple replicas.
Only the Executor deployment can be configured with multiple pod replicas.

AWS Platform Support

Deployment on AWS ECS (Elastic Container Service) Fargate is not supported. Link supports only Kubernetes-compliant (EKS) clusters.

AWS EKS Fargate Requirements

When deploying to EKS Fargate, storage must be manually provisioned. This includes creating an EFS (Elastic File System) instance and manually creating the StorageClass, Persistent Volumes (PVs), and Persistent Volume Claims (PVCs) for MongoDB, Redis, and Link file storage before installing the Helm chart.

Ingress Path-Based Routing

When using path-based routing (for example, /client), a specific Ingress configuration is required.

The Ingress path must be defined using a regular expression (for example, /client/(.*)).
The client.inbound.baseRoute value in the Helm chart must match this path (for example, "/client").