Availability profiles
An availability profile determines the level of redundancy across pods. The profile you choose determines which pods are automatically replicated during setup. Because some organizations require increased levels of resiliency and availability to others, availability profiles provide flexibility across several known variables such as requirements for hardware, redundancy, and organizational use.
When your create your organization, select an availability profile to suit your requirements for redundancy.
The predefined availability profiles are described below.
|
Availability profile |
Use case |
Hardware requirements |
Predefined redundancy across pods |
|---|---|---|---|
|
Enhanced high availability |
Designed for use in business or mission-critical production environments. This profile is intended for the highest level of availability, as it includes increased and expanded redundancy across critical pods. |
Maximum |
Maximum |
|
Standard high availability |
Designed for use in production environments and for those wanting to minimize unplanned downtime with redundancy across many pods. This is the default profile. |
Moderate |
Moderate |
|
Development and test environments |
Designed for use in nonproduction environments, including those for testing and evaluation. This profile is not supported for production environments. |
Minimal |
Minimal |
When deploying ArcGIS Enterprise on Kubernetes in nonproduction environments, use the development and test environments option. It requires the least amount of hardware and resources. When deploying to production environments, both high-availability profiles provide continued use and availability in the event of a failure. The enhanced high availability profile provides additional resilience compared to the standard high availability profile, but requires additional system resources.
Replicated pods per availability profile
As described above, each availability profile provides a predefined set of replicated pods to support continued workflows in the event of an unexpected failure. An example of a supported workflow for each is provided.
Enhanced high availability—Replicated pods are provided for publishing tools, storage, APIs, and ingress controllers with increased redundancy to support uninterrupted use in the event of unexpected failure or downtime.
Standard high availability—Replicated pods are provided for publishing tools and other essential pods such as storage, APIs, and ingress controllers to support continued use in the event of unexpected failure or downtime.
Development and test environments—Publishing tools are replicated to support multiple publishers in an organization.
A description of each replicated pod-per-availability profile is provided below.
|
Replicated pods |
Enhanced high availability profile |
Standard high availability profile |
Development and test environments profile |
|---|---|---|---|
|
Publishing tools |
4 |
3 |
3 |
|
Relational data store |
2 |
2 |
2 |
|
Private ingress controller |
3 |
2 |
2 |
|
Ingress controller |
3 |
2 |
|
|
Administrator API |
2 |
2 |
|
|
Portal API |
2 |
2 |
|
|
Services API |
2 |
2 |
|
|
JavaScript API |
2 |
||
|
Notebook automation service |
2 |
||
|
Queue store |
2 |
2 |
|
|
Object store: mixed |
3 |
||
|
Object store: metadata |
3 |
||
|
Object store: data server |
5 |
||
|
Spatiotemporal and index store: mixed |
3 |
||
|
Spatiotemporal and index store: coordinator |
3 |
||
|
Spatiotemporal and index store: data |
2 |
||
|
Shared feature service |
2 |
2 |
|
|
Shared image service |
2 |
2 |
|
|
Shared map service |
2 |
2 |
|
|
Shared tile service |
2 |
2 |
|
|
Enterprise portal |
2 |
||
|
Enterprise apps |
2 |
Recommended storage size per availability profile
To ensure sufficient storage, the recommended storage size for each StatefulSet volume depends on the selected availability profile as shown in the table below. The provisioned size must be at least as much as the minimum value specified in the development and test environments profile. You can increase volume size for the object store, relational store, and spatiotemporal and index store after creation if additional storage is required.
|
StatefulSet |
Enhanced high availability profile (GiB) |
Standard high availability profile (GiB) |
Development and test environments profile (GiB) |
|---|---|---|---|
|
Relational store |
300 |
150 |
16 |
|
Object store |
300 |
150 |
64 |
|
In-memory cache |
16 |
16 |
16 |
|
Queue store |
16 |
16 |
16 |
|
Spatiotemporal and index store |
300 |
150 |
32 |
|
Item packages |
32 |
16 |
16 |
|
Prometheus |
120 |
60 |
30 |
The total recommended storage for each availability profile shown in the following table depends on both the size of each volume and the number of replicas:
|
Availability profile |
Total recommended storage size (GiB) |
|---|---|
|
Enhanced high availability profile |
4732 |
|
Standard high availability profile |
1340 |
|
Development and test environments profile |
206 |