Kubernetes Clusters Automation
Kubernetes Container Automation
#340840
Description
Resources
/kubernetes/clusters/<clusterName>/automation
Supported Operations
Table: Kubernetes Container Systems Supported Operations
|
HTTP Method |
Input |
Output |
Description |
|
Path Parameter: |
Collection of:
|
Use this resource to retrieve details of container recommendation for a specific Kubernetes cluster. |
Table: Kubernetes Clusters Path Parameters
|
Parameter Name |
Type |
Description |
|
string |
The unique cluster name obtained from the output of /kubernetes/clusters or from the Kubex UI Connections tab. |
If a property or value is not set or not available, it is not included in the response.
Table: Kubernetes Container Response Schema
|
Element |
Type |
Filter/Sort |
Description |
|
string |
|
The cluster name as specified in the config.yaml files. |
|
|
string |
|
The name of the namespace associated with the selected container. |
|
|
string |
|
This is the name of the controller or pod. You can have one or more containers per pod. |
|
|
string |
|
The controller type that monitors and maintains the state of your cluster. This can be one of DaemonSet, Deployment, ReplicaSet, ReplicationController, StatefulSet, etc. |
|
|
string |
|
This is the name of the container manifest. |
|
|
string |
|
A unique identifier, for the selected cluster assigned by Densify. |
|
|
string |
|
A unique identifier for the listed container. |
|
|
integer |
|
This is the number of containers specified by the selected manifest. The number is determined using an average number of containers, based on the metric, "In Service Instances". |
|
|
integer |
|
The current CPU request value for the listed container. |
|
|
integer |
|
The current CPU limit value for the listed container. |
|
|
integer |
|
The current memory request value for the listed container. |
|
|
integer |
|
The current memory limit value for the listed container. |
|
|
integer |
|
The recommended CPU request value for the listed container. |
|
|
integer |
|
The recommended CPU limit value for the listed container. |
|
|
integer |
|
The recommended memory request value for the listed container. |
|
|
integer |
|
The recommended memory limit value for the selected container. |
|
|
integer |
|
The estimated savings that can be achieved by using the recommended CPU and memory settings for this container. |
|
|
date |
|
The date and time of the most recent analysis refresh, in the format: YYYY-MM-DDTHH:mm:ssZ |
|
|
string |
|
Indicates whether automation has been enabled for this cluster. |
|
|
string |
|
The number of node groups discovered in this cluster. |
|
|
string |
|
Indicates the metric used to trigger autoscaling. |
|
|
string |
|
Indicates the metric threshold value used to trigger autoscaling. |
Table: Kubernetes Container Response Schema - Additional Details
|
Element |
Type |
Filter/Sort |
Description |
|
string |
|
The predicted uptime (%) for the container, is based on the percentage of hours CPU utilization data is present in the historical interval, as specified in the policy settings for the entity. |
|
|
date |
|
A value in this column indicates the instance request/limit values have been changed recently. The date and time are in the format: YYYY-MM-DDTHH:mm:ssZ. The workload for this instance, on which the recommendation is based, includes all historical data for this instance and is not included in the analysis. |
|
|
string |
|
This is the name of the associated node group. |
|
|
string |
|
The number of out of memory (oom) events that occurred in the last 7 days. |
|
|
date |
|
The date and time on which this container was last audited, in the format: YYYY-MM-DDTHH:mm:ssZ. The value is from the workload history instead of the audit history, which may be truncated. |
|
|
date |
|
The date and time on which this container was first audited, in the format: YYYY-MM-DDTHH:mm:ssZ. The value is from the workload history instead of the audit history, which may be truncated. |
Examples
Example: Listing Kubernetes Clusters with Containers Enabled for Automation
The following example shows you how to retrieve cluster details for containers that have been enabled for automation.
Example: Listing Kubernetes Clusters with Containers Enabled for Automation
Request:
GET {{scheme}}://{{host}}{{port}}/api/v2/kubernetes/clusters/eks_oss_dev/containersResponse:
Example: Listing Kubernetes Clusters with Containers Enabled for Automation
{
"checksum": "d8d10f84c2829a3db166064ce2377af984f93254855a9e486633bf4cff1399f3",
"results": [
{
"cluster": "eks_oss_dev",
"namespace": "apps",
"podOwnerName": "nginx-deployment",
"podOwnerKind": "Deployment",
"container": "nginx",
"entityId": "51d4f114-9de5-4639-b810-a6749edb19dc",
"containerId": "d8121526-9757-371b-8bd7-abc3cb83c6b7",
"avgContainerCount": 3,
"recommendedCpuRequestmCores": 10,
"recommendedCpuLimitmCores": 10,
"recommendedMemRequestBytes": 10000000,
"recommendedMemLimitBytes": 10000000,
"estimatedSavingsPerContainer": -0.25,
"analyzedOn": "2025-03-19T04:40:22Z",
"kubexAutomation": "true",
"automationPolicy": "true"
},
{
"cluster": "eks_oss_dev",
"namespace": "kube-system",
"podOwnerName": "ama-metrics-ksm",
"podOwnerKind": "Deployment",
"container": "ama-metrics-ksm",
"entityId": "f06b2383-cf25-4c55-a9b0-ba0782daaf67",
"containerId": "aaef5810-2aed-3729-99f4-0796f3de921e",
"avgContainerCount": 1,
"currentCpuRequestmCores": 5,
"currentCpuLimitmCores": 1000,
"currentMemRequestBytes": 50000000,
"currentMemLimitBytes": 5120000000,
"recommendedCpuRequestmCores": 10,
"recommendedCpuLimitmCores": 110,
"recommendedMemRequestBytes": 40000000,
"recommendedMemLimitBytes": 520000000,
"estimatedSavingsPerContainer": -0.05,
"analyzedOn": "2025-03-19T04:40:22Z",
"kubexAutomation": "true",
"hpaMetricName": "cpu utilization"
},
{
...
}
]