mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
92 lines
2.9 KiB
Plaintext
92 lines
2.9 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * nodes/nodes-pods-autoscaling.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="nodes-pods-autoscaling-status-viewing_{context}"]
|
|
|
|
= Viewing horizontal pod autoscaler status conditions by using the CLI
|
|
|
|
You can view the status conditions set on a pod by the horizontal pod autoscaler (HPA).
|
|
|
|
[NOTE]
|
|
====
|
|
The horizontal pod autoscaler status conditions are available with the `v2` version of the autoscaling API.
|
|
====
|
|
|
|
.Prerequisites
|
|
|
|
To use horizontal pod autoscalers, your cluster administrator must have properly configured cluster metrics.
|
|
You can use the `oc describe PodMetrics <pod-name>` command to determine if metrics are configured. If metrics are
|
|
configured, the output appears similar to the following, with `Cpu` and `Memory` displayed under `Usage`.
|
|
|
|
[source,terminal]
|
|
----
|
|
$ oc describe PodMetrics openshift-kube-scheduler-ip-10-0-135-131.ec2.internal
|
|
----
|
|
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
Name: openshift-kube-scheduler-ip-10-0-135-131.ec2.internal
|
|
Namespace: openshift-kube-scheduler
|
|
Labels: <none>
|
|
Annotations: <none>
|
|
API Version: metrics.k8s.io/v1beta1
|
|
Containers:
|
|
Name: wait-for-host-port
|
|
Usage:
|
|
Memory: 0
|
|
Name: scheduler
|
|
Usage:
|
|
Cpu: 8m
|
|
Memory: 45440Ki
|
|
Kind: PodMetrics
|
|
Metadata:
|
|
Creation Timestamp: 2019-05-23T18:47:56Z
|
|
Self Link: /apis/metrics.k8s.io/v1beta1/namespaces/openshift-kube-scheduler/pods/openshift-kube-scheduler-ip-10-0-135-131.ec2.internal
|
|
Timestamp: 2019-05-23T18:47:56Z
|
|
Window: 1m0s
|
|
Events: <none>
|
|
----
|
|
|
|
.Procedure
|
|
|
|
To view the status conditions on a pod, use the following command with the name of the pod:
|
|
|
|
[source,terminal]
|
|
----
|
|
$ oc describe hpa <pod-name>
|
|
----
|
|
|
|
For example:
|
|
|
|
[source,terminal]
|
|
----
|
|
$ oc describe hpa cm-test
|
|
----
|
|
|
|
The conditions appear in the `Conditions` field in the output.
|
|
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
Name: cm-test
|
|
Namespace: prom
|
|
Labels: <none>
|
|
Annotations: <none>
|
|
CreationTimestamp: Fri, 16 Jun 2017 18:09:22 +0000
|
|
Reference: ReplicationController/cm-test
|
|
Metrics: ( current / target )
|
|
"http_requests" on pods: 66m / 500m
|
|
Min replicas: 1
|
|
Max replicas: 4
|
|
ReplicationController pods: 1 current / 1 desired
|
|
Conditions: <1>
|
|
Type Status Reason Message
|
|
---- ------ ------ -------
|
|
AbleToScale True ReadyForNewScale the last scale time was sufficiently old as to warrant a new scale
|
|
ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from pods metric http_request
|
|
ScalingLimited False DesiredWithinRange the desired replica count is within the acceptable range
|
|
----
|