Layer 7 (Application) Ingress
- Updated2026-04-08
- 1 minute(s) read
Layer 7 (Application) Ingress
Layer 7 ingress provides application-level HTTPS load balancing and routing for web services. SystemLink Enterprise uses Layer 7 ingress to expose HTTP-based services through two separate ingress endpoints: one endpoint for the web UI and one endpoint for API access.
Ingress Endpoints
SystemLink Enterprise requires configuration of two ingress endpoints:
- UI Ingress (global.hosts): Provides access to the SystemLink web UI.
- API Ingress (global.apiHosts): Provides programmatic access to SystemLink REST APIs.
You must configure both endpoints with unique hostnames. For example, systemlink.example.com for the UI and systemlink-api.example.com for the API. Configure these hostnames in the systemlink-values.yaml file under global.hosts and global.apiHosts.
For hostname requirements and security recommendations, refer to DNS and Network Security Considerations.
Ingress Annotations
You can customize ingress behavior through annotations, which are specific to the ingress controller being used. SystemLink Enterprise applies annotations at both global and service-specific levels:
- Global Annotations: Applied to all ingress resources via global.ingress.ui.annotations and global.ingress.api.annotations.
- Service-Specific Annotations: Applied to individual services to handle custom requirements.
Platform-Specific Configuration
The configuration for Layer 7 ingress varies depending on your Kubernetes platform and ingress controller. Refer to the platform-specific guides in this section for detailed configuration instructions.
Related Information
- SystemLink Environment Architecture
SystemLink Enterprise is an application with a service-oriented architecture. Kubernetes hosted microservices compose the architecture. SystemLink Enterprise is scalable, fault-tolerant, and highly available. The following table summarizes the major components of the SystemLink Enterprise architecture.
- Preparing to Host and Operate SystemLink Enterprise
Before installing SystemLink Enterprise, ensure that the following network, compute, storage, and security infrastructure is in place.
- DNS and Network Security Considerations
SystemLink Enterprise is hosted in a Kubernetes cluster. SystemLink Enterprise connects to test systems to aggregate data for monitoring and analysis.
- AWS VPC
A Virtual Private Cloud (VPC) is an isolated network environment within AWS.
- Azure VNet
An Azure Virtual Network (VNet) is an isolated network environment within Azure.
- Internet Facing Clusters
Enter a short description of your concept here (optional).
- Corporate Network Connected Clusters
A corporate network connected cluster deployment integrates SystemLink with your the private network infrastructure of your organization, ensuring secure access and secure integration with on-premises systems.
- systemlink-values.yaml
- SystemLink Enterprise in AWS EKS
Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service that simplifies running Kubernetes on AWS without needing to install and operate your own Kubernetes control plane.
- SystemLink Enterprise in Azure AKS
Azure Kubernetes Service (AKS) is a managed Kubernetes service that simplifies running Kubernetes on Azure without needing to install and operate your own Kubernetes control plane.