kubernetes-scheduler | Kubernetes custom scheduler based on Sysdig monitoring | Continuous Deployment library
kandi X-RAY | kubernetes-scheduler Summary
kandi X-RAY | kubernetes-scheduler Summary
This repository covers the use case of creating a custom Kubernetes scheduler written in Go.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- getBestNodeByMetrics returns the best node matching the given metrics
- init initializes the SDK API
- watch starts a new pod
- getMetrics retrieves metric values from sysdig API
- Gets data for a given metric
- Sets a namespace binding
- NodesAvailable returns a list of nodes available to kubeAPI
- bestNodeFromList returns the node from the list
- findDeploymentNameFromPod finds the deployment name for a given pod
- getKubeConfigFileLocation returns the default kubeconfig file
kubernetes-scheduler Key Features
kubernetes-scheduler Examples and Code Snippets
Community Discussions
Trending Discussions on kubernetes-scheduler
QUESTION
This seems like it should be simple enough, but I haven't been able to find an answer.
We have three labeled nodes:
thalia0
thalia1
thalia2
and a Deployment spec, named mm-sa
.
I would simply like to set number of replicas of mm-sa
to 48 and have the scheduler assign 16 pods to each node.
The closest I could find to this, was here, but it looks like this is not yet avaialble: Node affinity for even spread of pods across multiple availability zones. I also found this, why-kubernetes-scheduler-ignores-nodeaffinity, but it says that "According to the documentation, nodeAffinity must exist for each node that can be used for a scheduled pod and the node having the biggest weight sum is chosen."
This seems like such a simple use-case, but I cannot figure out how to achieve it without using a naïve approach, as in defining 3-different Deployments named mm-sa1
, ... mm-sa3
and using a nodeSelector
to assign each accordingly. (NB: I am currently using a nodeSelector
to assign 16-replicas of mm-sa
on a single node).
ANSWER
Answered 2019-Oct-11 at 18:49Kubernetes will automatically spread the pods in a replication controller or service across nodes in a single-zone cluster. So @David Maze's solution should apply if there are no other nodes. However since you mentioned that you have other nodes that you do not want to schedule on, I would recommend using the nodeSelector. By using nodeSelector, as long as the node has the same key-value pair in the YAML, the pod will be able to schedule on the node.
You can read more about nodeSelector here: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
QUESTION
When I submitted WordCountTopology to the Heron Cluster that deployed with Aurora scheduler and Zookeeper, this error happened as follows:
...ANSWER
Answered 2018-Jun-05 at 07:44From the logs:
[2018-06-04 00:56:02 -0700] [INFO] com.twitter.heron.statemgr.zookeeper.curator.CuratorStateManager: Created node for path: /heron/topologies/WordCountTopology
[2018-06-04 00:56:02 -0700] [WARNING] com.twitter.heron.spi.statemgr.SchedulerStateManagerAdaptor: Exception processing future: java.lang.RuntimeException: Could not createNode:
Heron is able to connect to ZK and check node successfully, so ZK cluster seems to be running and readable. However it seems that for some reason curator failed to create the node in ZK: /heron/topologies/WordCountTopology
Heron topology keeps its running data in ZK so it cant start if it failed to create the key nodes. You need to find out the cause for the ZK failure (permission?) and solve it.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install kubernetes-scheduler
Operating system: GNU/Linux MacOS Windows
x86 / x86_64 architecture
Git
g++ (Linux / MacOS) / MinGW (Windows)
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page