Edit (Deployment)

URL:
https://<root>/system/deployments/<deploymentID>/edit
Methods:
POST
Required Capability:
Access allowed only with the default administrator role
Version Introduced:
10.9

Description

The edit operation sets the scaling (replicas) and resource allocation (resources) for a specific microservice. Starting at ArcGIS Enterprise 11.2 on Kubernetes, the edit operation also allows administrators to set the node affinity and tolerations (podPlacementPolicy) that are applied to a GIS service's pods, as well as include either PersistentVolumeClaim (PVC) volumes or PVC volume templates that provide additional resources to a deployment's pods.

Scaling in ArcGIS Enterprise on Kubernetes

Either manual scaling or autoscaling can be set for a GIS service microservice using the deploymentJson parameter. Introduced at ArcGIS Enterprise on Kubernetes 10.9.1, autoscaling allows administrators to configure and deploy systems that respond to unexpected performance demands with minimal intervention and overhead. The ArcGIS Enterprise on Kubernetes autoscaling capability uses horizontal pod autoscaling, which, in response to an increase in resource usage, deploys additional pods according to the values set by the administrator.

When a specific CPU utilization threshold (averageUtilization) is crossed, ArcGIS Enterprise on Kubernetes scales the number of pods up to the maximum (max) value set in the replicas JSON object. When utilization drops, and the additional resources are no longer needed, the system scales itself back down to no lower than the minimum (min) value set in the replicas JSON object. For more information about enabling autoscaling, see the Editable properties section below.

Request parameters

ParameterDetails

deploymentJson

A JSON object that represents the properties of a microservice.

Example

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
deploymentJson={
  "mode": "Primary",
  "configuredState": "STARTED",
  "provider": "Postgres",
  "deploymentId": "ke84ls9uva6t7fvck8q5p",
  "name": "relational-store-primary",
  "type": "RelationalStore",
  "spec": {
    "replicas": {
      "min": 3,
      "max": 3,
      "scalingMode": "manual" //Added at 11.0
    },
    "containers": [
      {
        "name": "filebeat",
        "resources": {
          "memoryMin": "32Mi",
          "memoryMax": "50Mi",
          "cpuMin": "0.05",
          "cpuMax": "0.25"
        },
        "containerImageUrl": "container.image.com/info:1082",
        "containerImageKey": "FILEBEAT"
      },
      {
        "name": "main-container",
        "resources": {
          "memoryMin": "2Gi",
          "memoryMax": "8Gi",
          "cpuMin": "0.5",
          "cpuMax": "4"
        },
        "containerImageUrl": "container.image.com/info:1082",
        "containerImageKey": "STORE_POSTGRES"
      }
    ]
  },
  "labels": {},
  "revision": 1618223097333
}

async

(Optional)

Introduced at 10.9.1. This parameter specifies whether the operation will run synchronously or asynchronously. If false, the operation is run synchronously. If true, the operation is run asynchronously and the response returns a JSON object containing job information that can be used to track the job's status. The default value is false.

Values: true | false

f

The response format. The default format is html.

Values: html | json | pjson

Microservice properties

The following example demonstrates a full JSON object of a microservice:

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
{
  "mode": "Primary",
  "configuredState": "STARTED",
  "provider": "Postgres",
  "deploymentId": "ke84ls9uva6t7fvck8q5p",
  "name": "relational-store-primary",
  "type": "RelationalStore",
  "spec": {
    "replicas": {
      "min": 3,
      "max": 3,
      "scalingMode": "manual" //Added at 11.0
    },
    "containers": [
      {
        "name": "filebeat",
        "resources": {
          "memoryMin": "32Mi",
          "memoryMax": "50Mi",
          "cpuMin": "0.05",
          "cpuMax": "0.25"
        },
        "containerImageUrl": "container.image.com/info:1082",
        "containerImageKey": "FILEBEAT"
      },
      {
        "name": "main-container",
        "resources": {
          "memoryMin": "2Gi",
          "memoryMax": "8Gi",
          "cpuMin": "0.5",
          "cpuMax": "4"
        },
        "containerImageUrl": "container.image.com/info:1082",
        "containerImageKey": "STORE_POSTGRES"
      }
    ]
  },
  "labels": {},
  "revision": 1618223097333
}

The subsections below describe the individual properties included in the microservice JSON object that can, and cannot, be updated using this operation.

Editable properties

The properties below can be updated using the edit operation.

PropertyDetails

replicas

The number of replicas for the microservice. The default value for manual scaling for min and max is 1. For manual scaling, both the min and max values must be the same.

Example
Use dark colors for code blocksCopy
1
2
3
4
5
"replicas": {
  "min": 3,
  "max": 3,
  "scalingMode": "manual"
},

For organizations using ArcGIS Enterprise 11.2 on Kubernetes or later versions, version 2 (v2) of the autoscaling feature can be enabled by passing in the JSON object below and modifying the min, max, scalingMode, and averageUtilization values.

Autoscaling can be enabled by adjusting the scalingMode value to auto. The averageUtilization value will act as the CPU utilization threshold for autoscaling. If the threshold is crossed, ArcGIS Enterprise on Kubernetes scales up to the number of pods specified by the max value, and will return to no lower than the default pod level (the value set for min) once utilization decreases.

Example
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
"replicas": {
  "min": 1,
  "max": 10,
  "scalingMode": "auto",
  "autoscaling": {
    "hpaSpec": {
      "metrics": [
        {
          "resource": {
            "name": "cpu",
            "target": {
              "averageUtilization": "65",
              "type": "Utilization"
            }
          },
          "type": "Resource"
        }
      ],
      "hpaVersion": "autoscaling/v2"
    }
  }
},

Organizations using ArcGIS Enterprise on Kubernetes 10.9.1 can enable version 1 of the autoscaling feature by passing in the JSON object below and modifying the min, max, scalingMode, and targetCPUUtilizationPercentage values:

Example
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
"replicas": {
  "min": 1,
  "max": 5,
  "scalingMode": "auto",
  "autoscaling": {
    "hpaSpec": {
      "targetCPUUtilizationPercentage": 50
    },
    "hpaVersion": "autoscaling/v1"
  }
}

podPlacementPolicy

Introduced at 11.2. Sets the node affinity or tolerations applied that will be applied the pods of a GIS service deployment. For more information on configuring node affinity or tolerations, see the Edit placement policy operation.

nodeAffinity
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
"nodeAffinity": {
  "requiredDuringSchedulingIgnoredDuringExecution": {
    "nodeSelectorTerms": [
      {
        "matchExpressions": [
          {
            "key": "affinity",
            "operator": "In",
            "values": [
              "true"
            ]
          }
        ]
      }
    ]
  }
}
Tolerations
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
"tolerations": [
  {
    "effect": "NoExecute",
    "key": "tolerates",
    "operator": "Equal",
    "value": "true"
  }
]

volumes

Introduced at 11.2. An array that sets additional volumes for the deployment's pods to pull from. Administrators have the option to configure PVC volumes, which create a singular PVC volume that the pods of a deployment can directly request resources from, or configure PVC volume templates with the deployment, which will create separate volumes for each pod to use.

For singular PVC volumes, administrators will only need to provide the volume's ID:

Example
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
...
"volumes": [
  {
    "volumeId": "uadwuaj4pwkjhcst6spxx"
  }
],
...

For PVC volume templates, administrators need to provide the volume template's ID as well as the volume's purpose. The purpose specifies the types of volumes being created. Currently, the only supported purpose is GIS_SERVICE_TEMP, which designates the volumes created from the template as ephemeral volumes:

Example
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
...
"volumes": [
  {
    "purpose": "GIS_SERVICE_TEMP"
    "volumeConfig": "oi72y1m4q2exgzfr9uppg"
  }
],
...

resources

The minimum and maximum resource allocations for the microservice, including the minimum memory (memoryMin) and minimum CPU (cpuMin) resources required for the microservice to start. The default values for memoryMin, cpuMin, memoryMax, and cpuMax are shown in the example below.

Example
Use dark colors for code blocksCopy
1
2
3
4
5
6
"resources": {
  "memoryMin": "500Mi",
  "memoryMax": "2Gi",
  "cpuMin": "0.125",
  "cpuMax": "2"
},

Starting at ArcGIS Enterprise 11.3 on Kubernetes, organizations can implement device plugins to enable GPU nodes in their cluster to optimize workflows for raster analytics and deep learning. Requests and limits for GPU are set using the customResources object.

The following deployments will need to have request and limits values set for GPU:

  • system-rasteranalysistools-gpsyncserver (used for training models)
  • system-rasterprocessinggpu-dpserver (used for processing)

Values for requests and limits only need to be set on main-container.

The example below shows the accepted values for both requests and limits:

Example
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
"resources": {
  "memoryMin": "32Mi",
  "memoryMax": "50Mi",
  "cpuMin": "0.05",
  "cpuMax": "0.25",
  "customResources": {
    "limits": {
      "nvidia.com/gpu": 1
    },
    "requests": {
      "nvidia.com/gpu": 1
    }
  }
}

Uneditable properties

The following properties cannot be edited but are required to be passed through in the deploymentJson object:

PropertyDetails

mode

The microservice mode. A mode type of Undefined is used when the microservice is system related (Admin API, portal sharing, ingress controller, and so on). Only microservices related to an ArcGIS service type return Dedicated or Shared for this property.

Values: Shared | Dedicated | Undefined | Primary | Standby | Coordinator

provider

The microservice provider. Only microservices related to an ArcGIS service type have a provider type. A provider type of Undefined is used for microservices that are not service related (Admin API, portal sharing, ingress controller, and so on).

Values: SDS | ArcObjects11 | DMaps | Undefined | Postgres | Tiles | Ignite | MinIO | Elasticsearch | RabbitMQ | ArcObjectsRasterRendering

id

The template ID.

Example
Use dark colors for code blocksCopy
1
"id": "9375dd81-30d1-41c0-a802-cabb425159a9",

type

The microservice type. For example, if the microservice is a shared feature server containing feature services, FeatureServer is returned. For microservices that are not service related, System is returned.

Values: FeatureServer | GeometryServer | GPServer | GPSyncServer | MapServer | TileServer | System | InMemoryStore | ObjectStore | SpatiotemporalIndexStore | QueueServer | RelationalStore | WebhookProcessor (Added at 11.0)

spec

The JSON object representation of the template's specifications, including replicas and container resources.

Example
Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
"spec": {
  "replicas": {
    "min": 3,
    "max": 3,
    "scalingMode": "manual" //Added at 11.0
  },
  "containers": [
    {
      "name": "main-container",
      "resources": {
        "memoryMin": "1.5Gi",
        "memoryMax": "4Gi",
        "cpuMin": "0.125",
        "cpuMax": "2"
      },
      "containerImageKey": "GP_SERVER"
    },
    {
      "name": "filebeat",
      "resources": {
        "memoryMin": "32Mi",
        "memoryMax": "50Mi",
        "cpuMin": "0.05",
        "cpuMax": "0.25"
      },
      "containerImageKey": "FILEBEAT"
    }
  ]
},

revision

The date, in milliseconds from epoch format, of the latest revision to the template.

Example
Use dark colors for code blocksCopy
1
"revision": 1598217421474

Example usage

The following is a sample POST request for the edit operation that demonstrates autoscaling:

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
POST /context/admin/system/deployments/d23ae35d2-e81a-4e79-93de-90fcf1388908/edit HTTP/1.1
Host: organization.domain.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []

deploymentJson={
  "mode": "Primary",
  "configuredState": "STARTED",
  "provider": "Postgres",
  "deploymentId": "ke84ls9uva6t7fvck8q5p",
  "name": "relational-store-primary",
  "type": "RelationalStore",
  "spec": {
    "replicas": {
      "min": 1,
      "max": 10,
      "scalingMode": "auto",
      "autoscaling": {
        "hpaSpec": {
          "metrics": [
            {
              "resource": {
                "name": "cpu",
                "target": {
                  "averageUtilization": "65",
                  "type": "Utilization"
                }
              },
              "type": "Resource"
            }
          ],
          "hpaVersion": "autoscaling/v2"
        }
      }
    },
    "containers": [
      {
        "name": "filebeat",
        "resources": {
          "memoryMin": "32Mi",
          "memoryMax": "50Mi",
          "cpuMin": "0.05",
          "cpuMax": "0.25"
        },
        "containerImageUrl": "container.image.com/info:1082",
        "containerImageKey": "FILEBEAT"
      },
      {
        "name": "main-container",
        "resources": {
          "memoryMin": "2Gi",
          "memoryMax": "8Gi",
          "cpuMin": "0.5",
          "cpuMax": "4"
        },
        "containerImageUrl": "container.image.com/info:1082",
        "containerImageKey": "STORE_POSTGRES"
      }
    ]
  },
  "labels": {},
  "revision": 1618223097333
}&f=pjson&token=B4SGXu8PifZbfOJxpbr-i3X66FvpOuDtp4UdaBqmodRHAxxI-El280UH26TsC9YBct-6TJ_6wYH8iJB39SCwJIB6Vl8_DXmhvROZxjWMk_boLq6J-hurAvVdsOwYLlE7uy7j5t7lpQBAOqvnXS1lxGCy1vwnr3OPLoKmOWY8S8dxP1ZNrRx_SlTSfshlnMP7yoYIArLIylO0Gga9gcyDa3DYsDeTKU8uKbkUQ6LEwo93g1cU9zAxFnxhlBdHw-9U

JSON Response examples

If async is false, the following response is returned:

Use dark colors for code blocksCopy
1
{"status": "success"}

If async is true, the following response is returned. The value returned for jobsUrl can be used to access the job resource to track a job's status after it's been submitted. For more information, see the Job resource topic.

Use dark colors for code blocksCopy
1
2
3
4
5
{
  "jobsUrl": "https://organization.domain.com/context/admin/jobs/ja2ca1a35-881c-400c-a49a-b26883002d6c",
  "jobID": "ja2ca1a35-881c-400c-a49a-b26883002d6c",
  "jobStatus": "SUBMITTED"
}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.