Comments (14)
Is it possible to increase the log verbosity to 3 or 4? (-v command line flag)
from cluster-proportional-autoscaler.
I have temporarily disabled it while we debug other coredns crashing issues but I will get back to you on that.
from cluster-proportional-autoscaler.
/assign
from cluster-proportional-autoscaler.
Can't think of how can cores be doubled while nodes remain the same, unless node's ResourceCPU
was manipulated in some sort:
https://github.com/kubernetes-incubator/cluster-proportional-autoscaler/blob/872b0a4e17b10aa43592e76634b739612483de71/pkg/autoscaler/k8sclient/k8sclient.go#L192-L203
from cluster-proportional-autoscaler.
@eherot What environment (or cloud provider) do you use?
from cluster-proportional-autoscaler.
That would be AWS
from cluster-proportional-autoscaler.
@eherot Is it possible for you to trace/log the # of nodes and cores with timeline to see if it matches what the controller sees? I'm not quite convinced this is specific to the controller yet. Did it happen on lower CPA version (e.g. 1.6.0) as well?
from cluster-proportional-autoscaler.
I wonder would it be related to the k8s client versions --- CPA 1.7.1 uses k8s 1.15.1 where as your cluster uses 1.11.8.
from cluster-proportional-autoscaler.
Is there a CPA/k8s compatibility matrix available somewhere?
from cluster-proportional-autoscaler.
As client-go is the only piece that may be incompatible, I would refer to https://github.com/kubernetes/client-go#compatibility-matrix. The latest CPA uses client-go 12.0, technically it should work with k8s 1.9+.
from cluster-proportional-autoscaler.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
from cluster-proportional-autoscaler.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
from cluster-proportional-autoscaler.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
from cluster-proportional-autoscaler.
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
.
Mark the issue as fresh with/remove-lifecycle rotten
.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from cluster-proportional-autoscaler.
Related Issues (20)
- info: 1.8.7 tag but no release HOT 7
- Deprecation of legacy k8s.gcr.io container image registry HOT 6
- How does the maxReplicas field in HPA affect the algorithm?
- cluster-proportional-autoscaler is not rebalancing after spikes HOT 6
- Metrics endpoint HOT 7
- Facing vulnerability issues with golang , net packages HOT 4
- Request for Inclusion of Compatibility Matrix in README.md HOT 7
- tag for 1.8.8 includes v HOT 2
- Defaults matching PSS restricted HOT 7
- Re-build v1.8.8 to build with latest minor version of go 1.20 to fix CVEs HOT 12
- Changelog outdated HOT 3
- CPA does not support scale based on pod number HOT 4
- Image location in RELEASE.md is wrong HOT 7
- Allow horizontally scaling StatefulSets HOT 4
- [chart] Please support configuring environment variables for the container HOT 4
- Can't start pod issue HOT 4
- Missing 1.8.10 release HOT 4
- Request: Please make FIPS 140-2 compliant images available HOT 2
- Any way to disable when node(s) are being shutdown? HOT 3
- Estimated timeline for a new release with security fixes
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cluster-proportional-autoscaler.