Welcome
Cloud Native Link
Cloud Native Link refers to the HCL Link product installation on a Kubernetes cluster.
Upgrade and Rollback
Helm is a Kubernetes package manager that uses charts to define, install, and upgrade even the most complex Kubernetes applications.
Helm Rollback Operation
The helm rollback command reverts a release to a previous, successful deployment revision. Every successful install, upgrade, or rollback operation creates a new revision number.

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.
  - Helm Upgrade Operation
    The helm upgrade command updates a release to a new version of a chart, or updates the configuration values of the existing release.
  - Helm Rollback Operation
    The helm rollback command reverts a release to a previous, successful deployment revision. Every successful install, upgrade, or rollback operation creates a new revision number.
  - Link Chart and Product Version Correspondence
  - Data Backup — A Critical Step
  - Link versions
    The following table lists all Link product versions along with their corresponding Helm chart versions for reference.
- 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

Helm Rollback Operation

The helm rollback command reverts a release to a previous, successful deployment revision. Every successful install, upgrade, or rollback operation creates a new revision number.

The following table outlines the steps, descriptions, and corresponding command for Helm Rollback:


Step	Description	Command Example
1. Check Release History	Use helm history to view the revision numbers, statuses, and descriptions of a release to identify the stable revision you want to revert to.	helm history link-release
2. Identify Target Revision	From the history, choose the revision number that was previously marked as DEPLOYED or a known stable state.	Output snippet: REVISION 2 / STATUS FAILED REVISION 1 / STATUS DEPLOYED Target Revision is 1.
3. Perform Rollback	Run the rollback command with the release name and the target revision number.	helm rollback link-release 1
4. Verify Rollback	Check the status and history again to ensure the rollback was successful. The rollback itself will create a new revision.	helm status link-release helm history link-release (A new revision, e.g., 3, is created with the configuration of revision 1)
Error Example	If the revision number is not valid or doesn't exist.	Error: failed to get release... invalid revision number: 99