- URL:
- https://<root>/services/<serviceName.serviceType>/placementPolicy
- Methods:
GET- Required Capability:
- Access allowed with the "Security and infrastructure" privilege
- Version Introduced:
- 11.2
Description
The placement resource returns the current node affinity and tolerations that are applied to a GIS service’s pods. By utilizing node affinity and tolerations, administrators can have the pods for a specific service be scheduled to, or repelled from, specific nodes. For example, an administrator could use node affinity and tolerations to ensure that a GIS service’s pods are scheduled to nodes that have higher capacity, nodes that have a specific type of GPU, or prevent pods of other components from being scheduled on specific nodes. The placement resource also provides access to the Edit (Placement Policy) operation, which is used to define or modify the node affinity and toleration values for a specific service.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default format is Values: |
Example usage
The following is a sample request URL used to access the placement resource:
https://organization.domain.com/context/admin/services/CommercialDamageAssessment.FeatureServer/placementPolicy?f=pjsonJSON Response example
The following response example shows a sample configuration for node:
{
"placementPolicy": [
{
"deploymentType": "FeatureServer",
"deploymentId": "krh1vura4livmjy61ibe4",
"podPlacementPolicy": {
"tolerations": [],
"nodeAffinity": {
"requiredDuringSchedulingIgnoredDuringExecution": {
"nodeSelectorTerms": [
{
"matchExpressions": [
{
"key": "sampleLabel",
"operator": "In",
"values": [
"sampleValue"
]
}
]
}
]
}
}
}
}
]
}The following response example shows a sample configuration for tolerations:
{
"placementPolicy": [
{
"deploymentId": "kfnxectieft8iaxn3qka9",
"deploymentType": "FeatureServer",
"podPlacementPolicy":{
"nodeAffinity":{},
"tolerations": [
{
"effect": "NoSchedule",
"key": "label1",
"operator": "Equal",
"value": "test1"
}
]
}
}
]
}