Bug 1656330
Summary: | [cloud-CA] The node hosting cluster-autoscaler can be scaled down | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | sunzhaohua <zhsun> |
Component: | Cloud Compute | Assignee: | Andrew McDermott <amcdermo> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | sunzhaohua <zhsun> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.0 | CC: | jhou |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-25 11:28:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sunzhaohua
2018-12-05 09:20:41 UTC
Cluster-autoscaler pod is deployed on master node now. $ bin/openshift-install version bin/openshift-install v0.8.0-master-2-g5e7b36d6351c9cc773f1dadc64abf9d7041151b1 $ oc get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE cluster-autoscaler-default-7c88c947bc-mnnrj 1/1 Running 0 49s 10.129.0.20 ip-10-0-40-163.us-east-2.compute.internal <none> cluster-autoscaler-operator-5c467664fb-zb4hk 1/1 Running 0 19m 10.130.0.11 ip-10-0-31-81.us-east-2.compute.internal <none> clusterapi-manager-controllers-7d86667974-hvx4r 4/4 Running 0 16m 10.128.0.4 ip-10-0-8-232.us-east-2.compute.internal <none> machine-api-operator-6c8f7f459c-b8hbk 1/1 Running 0 19m 10.130.0.8 ip-10-0-31-81.us-east-2.compute.internal <none> $ oc get node NAME STATUS ROLES AGE VERSION ip-10-0-132-7.us-east-2.compute.internal Ready worker 15m v1.11.0+85a0623 ip-10-0-146-110.us-east-2.compute.internal Ready worker 15m v1.11.0+85a0623 ip-10-0-175-107.us-east-2.compute.internal Ready worker 15m v1.11.0+85a0623 ip-10-0-31-81.us-east-2.compute.internal Ready master 20m v1.11.0+85a0623 ip-10-0-40-163.us-east-2.compute.internal Ready master 20m v1.11.0+85a0623 ip-10-0-8-232.us-east-2.compute.internal Ready master 20m v1.11.0+85a0623 Verified. According to the comment 1, the autoscaler pod now is deployed on master node. Closing as this was fixed by: https://github.com/openshift/cluster-autoscaler-operator/pull/19 |