Create (Volumes Configurations)

URL:
https://<root>/system/volumes/configurations/create
Methods:
POST
Required Capability:
Access allowed with the "Security and infrastructure" privileges
Version Introduced:
11.2

Description

The create operation is used to configure PersistentVolumeClaim (PVC) volume templates that are used to create on-demand volumes for each pod associated with a specific deployment.

Administrators will need to define the name of the volume and define the properties in the spec JSON object. For more information on the configurable properties and their accepted values, see the Spec properties section below.

To configure a GIS service to use a configure PVC template, the template's ID (which is returned by the Configurations resource) and purpose will need to be added to a deployment's JSON. For more information, see the Edit Deployment documentation.

Ephemeral volumes

At ArcGIS Enterprise 11.2 on Kubernetes, the create operation can be used to create PVC volume templates that will generate multiple ephemeral volumes on-demand for the pods of a deployment. Each pod is then able to use its own ephemeral volume, providing each pod with its own resources to draw from. Once the pods are deleted, and the ephemeral volumes are no longer needed, the volumes are also removed.

Ephemeral volumes are ideal for services, such as raster analytics, that do not need to have access to persisted data, but rather perform large analysis jobs that need to load data to a temporary space for processing.

Ephemeral volumes are not useful for cases where data needs to be read by all pods of a particular service or deployment. For those cases, administrators should consider creating persistent volumes.

Request parameters

ParameterDetails

volumeJson

The JSON object that specifies the volume's configuration information. The name property and spec JSON object will need to be updated. All other information should not be modified.

Example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
volumeJson={
  "name": "ephemeral-test",
  "type": "PVC_TEMPLATE",
  "spec": {
    "storageClassName": "managed-premium",
    "resources": {"requests": {"storage": "8Gi"}},
    "accessModes": ["ReadWriteOnce"],
    "volumeMode": "Filesystem",
    "volumeName": "example-name",
    "labels": {
      "label1": "value1",
      "label2": "value2"
    }
  }
}

f

The response format. The default format is html.

Values: html | json | pjson

Spec properties

PropertyDetails

accesModes

Specifies how the volume can be mounted. This property accepts the following values:

  • ReadWriteOnce: The volume can be mounted as read-write to one node. The volume is accessible to all pods scheduled to, and running on, that node.
  • ReadOnlyMany: The volume can be mounted as read-only to multiple nodes.
  • ReadWriteMany: The volume can be mounted as read-write to many nodes.

resources

Specifies the amount of storage the pods can request from the volume.

storageClassName

Reflects the name of a defined StorageClass that the PVC volume is connection to.

volumeMode

Specifies the volume type. This property accepts the following values:

  • Filesystem: The volume is mounted in the pod as a directory in the pod's file system.
  • Block: The volume is inserted as a raw data block into the pod.

volumeName

Specifies the name of the associated PV that the PVC will refer and bind to.

labels

Lists labels that match with the associated PV's labels.

Example usage

The following is a sample POST request for the create operation:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
POST /context/admin/system/volumes/configurations/create HTTP/1.1
Host: organization.domain.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []

volumeJson={
  "name": "ephemeral-test",
  "type": "PVC_TEMPLATE",
  "spec": {
    "storageClassName": "managed-premium",
    "resources": {"requests": {"storage": "8Gi"}},
    "accessModes": ["ReadWriteOnce"],
    "volumeMode": "Filesystem",
    "volumeName": "example-name",
    "labels": {
      "label1": "value1",
      "label2": "value2"
    }
  },
  "revision": 1
}&f=pjson&token= 08_b0sXFBn7UYUmkEwXNiaKY6frp0GZGyxY6JJdEGWenjP0u_rXvr6EGGCwEsiZbcn-Nbhk7B9itJSDGJAOeY1RYFDJp68R6WaU243A7HNMDFzbduAiuonrKStg9AxnhD8xU8gebu0PNJXMPTHO_dCby8v86fiTW_-xsR-yyWrspjdiu8q2rt4qPB0by1Q3jL6I6J540dFNDvP-yfvlrmLRUEvXRQfORXqxKbJrOazLOTnWD5ZWjJNDwQ800vkQK

JSON Response example

1
{"status": "success"}

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

You can no longer sign into this site. Go to your ArcGIS portal or the ArcGIS Location Platform dashboard to perform management tasks.

Your ArcGIS portal

Create, manage, and access API keys and OAuth 2.0 developer credentials, hosted layers, and data services.

Your ArcGIS Location Platform dashboard

Manage billing, monitor service usage, and access additional resources.

Learn more about these changes in the What's new in Esri Developers June 2024 blog post.

Close