Comments (10)
Does this feature look like equivelance class cache
which is removed in v1.23?
from kubernetes.
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
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-sigs/prow repository.
from kubernetes.
/sig node
from kubernetes.
Which component do you want to implement this functionality in, is it the schdeuler? And If podAffinity is present, the distribution of pods in the deployment will be affected.
from kubernetes.
even through same type of pods in same workload, if set volume
or TopologySpreadConstraint
, then pass through the filter of plugins such as resource
, affinity
, feasible nodes should be a big difference
from kubernetes.
/sig scheduling
Sorry, I didn't look into the details. As your purpose is to accelerating predicate, this belongs to sig-scheduling.
I think I can understand some of what you're trying to do.
For example, if we have a deployment with required nodeAffinity.
Then maybe we can store a affinity->node mapping, and then we can skip preFilter
of nodeAffinity
plugin for other pods in the same deployment.
However, the maintaining of this cache will also increase the burden on the scheduler, and brings additional complexity to the framework.
If you have implemented this somewhere, then maybe the results of a benchmark will be very convincing.
from kubernetes.
And If podAffinity is present, the distribution of pods in the deployment will be affected.
all pods in a deployment have same predicate condition, include podAffinity, right?
from kubernetes.
plugins such as
resource
,affinity
, feasible nodes should be a big difference
Resource
should be re-considered, of couse.
from kubernetes.
However, the maintaining of this cache will also increase the burden on the scheduler, and brings additional complexity to the framework.
Yes, it is a heavy work. I just throw out this question and we can discuss it.
If you have implemented this somewhere, then maybe the results of a benchmark will be very convincing.
Some other schedulers based on kubernetes have this feature.
I will try to run a benchmarck if I can.
from kubernetes.
Some other schedulers based on kubernetes have this feature.
Can you paste a reference here? :)
from kubernetes.
Related Issues (20)
- Failed to create the reconcile looper: failed to list all OverLappingIPs: client rate limiter Wait returned an error: context deadline exceeded HOT 4
- Kubernets service not distributing traffic in equally , seeing imbalance in traffic . HOT 14
- Comments that end up in OpenAPI descriptions should be CommonMark HOT 18
- Enhancement: allow to filter what fields to return from the API HOT 9
- [Failing Test] ci-crio-cgroupv1-node-e2e-conformance (Swap Tests) HOT 3
- [Flaking Test] integration-master (goroutine leak detection) HOT 6
- [Flaking Test] ci-node-e2e (Container Lifecycle) HOT 11
- Migrate existing features to versioned feature gate HOT 4
- verification machinery for compatibility version HOT 3
- [Flaking Test] TestLog/stateful_set_logs_with_all_pods HOT 4
- Pod deleted during image pull still starts HOT 10
- ValidatingAdmissionPolicy objects have different runtime type compared to CRDValidationRules HOT 8
- `kube-proxy`'s `--healthz-bind-address` should support IPv4 and IPv6 simultaneously (dual stack) HOT 24
- Bug: securityContext appArmorProfile unconfined not working with containerd HOT 5
- The old pod log file is not deleted from the /var/log/pods/ directory HOT 14
- Job controller reports the count of terminating pods with unnecessary delay HOT 4
- tracking issue; bump pause to 3.10 HOT 4
- kubernetes-sigs / scheduler-plugins go.mod Error HOT 3
- post-kubernetes-push-image-pause failed to publish version 3.10 HOT 15
- Failure cluster [6bc9e9c5...] HOT 8
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 kubernetes.