Noelantogerorge opened a new issue, #7928:
URL: https://github.com/apache/cloudstack/issues/7928
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
Kubernetes UI
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
4.18
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advance Networking
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
All runnig on Ubuntu 22.04
##### SUMMARY
<!-- Explain the problem/feature briefly -->
My kubernetes cluster was configured for autoscale and when I deployed some
40 pods on the cluster it when to Alert state due to some resources. So I
removed all pods from the cluster and restarted the cluster. Now cluster state
is in Running status but all new nodes it spinned up is still running and scale
down is not triggered.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
Create a cluster with small compute resource and enable auto scale of
5nodes.
Add some pods to the kubernetes cluster so that it should requires more than
5 nodes.
Kubernetes cluster will goes to Alert state. Once it is in Alert state login
to kubernetes and clear the pods and restart the cluster.
Cluster will restart and state changes to running. All 5 nodes will be in
running state and scale down will not be triggered
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
Expected scale down has to be triggered and cluster should move to old state
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
