Overview
ArcGIS Enterprise on Kubernetes is composed of many microservices that work together to accommodate and support software features and workload. These microservices are implemented as one or more Kubernetes deployments that are instantiated as pods in your organization.
Administrators can use ArcGIS Enterprise Manager or ArcGIS Enterprise Administrator API to manage system deployments. Deployments can be scaled horizontally by adjusting the number of pods as well as vertically by adjusting the memory and CPU available to each pod. Increasing the number of pods increases the resilience of a deployment because the pods will be spread across multiple nodes. Increasing the memory and CPU can enable each pod to handle a greater volume of requests. Scaling system deployments down, either horizontally or vertically, can reduce costs by reducing the compute resources required by these deployments.
The default values for system deployments vary based on the architecture profile that was selected when the organization was configured. The default values for each system deployment were configured with the intent to run multiple pods to improve availability and overall throughput. However, in some cases, a single pod with added resources can be as, or more, efficient. System deployments are flexible, as they allow for adjustment in both dimensions.
From both administrative applications, the deployments described below can be modified with updated resource limits and scaled to increase or decrease pods within the deployment. To use ArcGIS Enterprise Administrator API for these steps, review its documentation.
System deployment types
The following system deployments can be managed from administrative tools:
| Deployment | Description |
|---|---|
Apps | Foundational support for embedded apps in the organization. |
ArcGIS Enterprise Administrator API | APIs for administrative aspects of the ArcGIS Enterprise organization. |
| ArcGIS Enterprise Manager | A setup wizard that creates an ArcGIS Enterprise organization. Once the organization is configured, ArcGIS Enterprise Manager is used to manage, monitor, and secure the organization. |
Help | Documentation for deploying, configuring, and using ArcGIS Enterprise on Kubernetes. |
Ingress controller | A component that routes external web traffic into, and across, the Kubernetes cluster. |
Javascript API | Foundational support for essential apps in the organization. |
Notebook automation service | Manages notebook service deployments to support notebook automation. |
Portal | User experience that supports sharing, item management, and member management workflows. |
Portal API | Portal APIs that support sharing, item management, and member management workflows. Note:Before scaling this deployment or performing an upgrade, additional storage requirements must be met. |
Private ingress controller | A component that proxies web traffic between internal pods in the Kubernetes cluster. |
Service lifecycle manager | Performs life cycle management of GIS service configurations. |
Services API | APIs for GIS, system, and utility services that support publishing, caching, and analysis workflows. |
Usage metrics viewer | Default and custom dashboards that display GIS service usage. |
Usage metrics data | GIS service usage data. |
Web styles | Symbology that supports web styles. |