kubernetes-scheduler | Kubernetes custom scheduler based on Sysdig monitoring | Continuous Deployment library

 by   draios Go Version: Current License: Apache-2.0

kandi X-RAY | kubernetes-scheduler Summary

kandi X-RAY | kubernetes-scheduler Summary

kubernetes-scheduler is a Go library typically used in Devops, Continuous Deployment applications. kubernetes-scheduler has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This repository covers the use case of creating a custom Kubernetes scheduler written in Go.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              kubernetes-scheduler has a low active ecosystem.
              It has 31 star(s) with 18 fork(s). There are 14 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              kubernetes-scheduler has no issues reported. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of kubernetes-scheduler is current.

            kandi-Quality Quality

              kubernetes-scheduler has 0 bugs and 0 code smells.

            kandi-Security Security

              kubernetes-scheduler has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              kubernetes-scheduler code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              kubernetes-scheduler is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              kubernetes-scheduler releases are not available. You will need to build from source code and install.
              Installation instructions, examples and code snippets are available.
              It has 1010 lines of code, 29 functions and 14 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed kubernetes-scheduler and discovered the below as its top functions. This is intended to give you an instant insight into kubernetes-scheduler implemented functionality, and help decide if they suit your requirements.
            • 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
            Get all kandi verified functions for this library.

            kubernetes-scheduler Key Features

            No Key Features are available at this moment for kubernetes-scheduler.

            kubernetes-scheduler Examples and Code Snippets

            No Code Snippets are available at this moment for kubernetes-scheduler.

            Community Discussions

            QUESTION

            How to assign equal deployments across multiple nodes
            Asked 2019-Oct-11 at 18:59

            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:49

            Kubernetes 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

            Source https://stackoverflow.com/questions/58345021

            QUESTION

            Heron Failed to set packing plan for topology 'WordCountTopology'
            Asked 2018-Jun-05 at 07:44

            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:44

            From 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.

            Source https://stackoverflow.com/questions/50675906

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install kubernetes-scheduler

            Golang for compilation
            Operating system: GNU/Linux MacOS Windows
            x86 / x86_64 architecture
            Git
            g++ (Linux / MacOS) / MinGW (Windows)

            Support

            Kubernetes - Configure multiple schedulersSysdig WebpageSysdig Custom Scheduler BlogSysdig Custom Scheduler KubeCon EU 2018 Talk
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/draios/kubernetes-scheduler.git

          • CLI

            gh repo clone draios/kubernetes-scheduler

          • sshUrl

            git@github.com:draios/kubernetes-scheduler.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link