GithubHelp home page GithubHelp logo

kedacore / keda-docs Goto Github PK

View Code? Open in Web Editor NEW
113.0 12.0 419.0 20.78 MB

Documentation and landing page for KEDA

Home Page: https://keda.sh

License: Apache License 2.0

Makefile 1.43% HTML 81.66% Sass 15.07% Dockerfile 1.85%

keda-docs's Introduction

keda-docs's People

Contributors

adarsh-verma-14 avatar ahmelsayed avatar amirschw avatar arapulido avatar arschles avatar balchua avatar chalin avatar csnance avatar dependabot[bot] avatar dttung2905 avatar gauron99 avatar jeffhollan avatar jorturfer avatar lucperkins avatar neelanjan00 avatar ppatierno avatar pragmaticivan avatar ramcohen avatar ritikaa96 avatar robin-wayve avatar robpickerill avatar shubham82 avatar spiritzhou avatar spoplavskiy avatar thisisobate avatar tomkerkhove avatar tsuyoshiushio avatar turbaszek avatar v-shenoy avatar zroubalik avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

keda-docs's Issues

Extend How can I use KEDA in a proxy network? troubleshooting docs

The solution described in How can I use KEDA in a proxy network? troubleshooting docs cannot be used in managed Kubernetes clusters like GKE or EKS: https://keda.sh/docs/troubleshooting/

It would be helpful to extend this section with solution for common cloud providers:

Débug outside cluster

Someone could write a walkthrough on how to debug Keda outside the cluster using vscode.

Provide getting started

Getting started page should walk new folks through the following steps:

  1. Installing KEDA
  2. Deploying deployment
  3. Deploying the trigger auth
  4. Deploying the scaled object
  5. Monitor with KEDA dashboard

Blog post proposal about Strimzi + KEDA

Hi,
would you interested in a blog post talking about using Strimzi for deploying Kafka and leveraging the KEDA scaler for autoscaling Kafka Streams application?

Docs are not versioned

Hi,

I've read through the docs about how to use AWS scalers, and added identityOwner just to find out that this feature was not relased yet.

It could be nice if there will be a version picker in the docs, to make sure the user understand he is reading the latest unreleased versioned docs.

Provide docs on using KEDA with HTTP scaling

Provide docs on using KEDA with HTTP scaling via Osiris.

Current docs we had on kedacore/keda:

HTTP scaling integration
KEDA enables scaling based on event sources where the event resides somewhere to be pulled. For events like HTTP where the event is pushed to the container, KEDA works side by side with HTTP scale-to-zero components like Osiris or Knative serving. By pairing KEDA with an HTTP scale-to-zero component you can provide rich event scaling for both HTTP and non-HTTP.

Provide new scaler template

Provide a template that can be used to document new scalers so that all scalers use a similar doc approach.

The template should come with a brief doc describing what the goal is and what should be documented.

Provide guidance how to build an external scaler

Our current external scaler docs are very basic, we should enrich them in what it requires to be an external scaler.

Things it should cover are:

  • What does it need to expose
  • What are the data contracts that are required
  • ..

Providing an OpenAPI spec for this might be a good option?

Improve Scaling Jobs docs and jobs scaling logic

Current documentation about jobs scaling is incomplete and the jobs scaler does not behave as one would intuitively expect.

The algorithm for spawning of new jobs is not described in detail in the docs. I would expect that:

  1. When a job pulls a new task from the queue, it should dequeue it from the queue on the start.
  2. The value of metric exposed by scaler should be the length of the queue (number of tasks that have not been pulled by any job yet).
  3. After each pollingInterval KEDA spawns new jobs and their number is equal to value of the metric (length of the queue) - number of jobs that don't have running or completed status.
  4. At the same time the number of new jobs is capped by inequality number of new jobs to spawn + number of jobs without running or completed status <= maxReplicaCount.

The 3. point was proposed also in kedacore/keda#525 (comment) to work like this but it still has not been resolved. If there are already jobs in pending status, KEDA does not take them into account and spawns all jobs in the queue again during next polling which can result in huge number of jobs if e.g. the pending jobs cannot be scheduled or are waiting for new nodes to be provisioned.

Further it is not clear, in the context of jobs scaling, what is the meaning of cooldownPeriod, minReplicaCount and threshold in Prometheus trigger (and similar parameters in other triggers).

Should we list who's supporting KEDA?

Should we list who's supporting KEDA?

In the main repo we have listed Microsoft & Red Hat which we might want to list in the community section as well? If other companies, let's say AWS, contribute we can add them as well.

Update KEDA.sh footer to standard LF/CNCF footer

I'd update it to:

© KEDA Authors 2014-2020 | Documentation Distributed under CC-BY-4.0© 2020 The Linux Foundation. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.

Also linking to the trademark usage/policies page, see Prometheus as an example: https://prometheus.io/

Unify contents of Community sections

Community section on the main page is listing supporting companies:
Community - main page

The separate Community page is missing this part:
Community - separate page

Would be great to unify both contents.

Update diagram

Kubernetes store should be Kubernetes API server in the diagram

Move site over

@tomkerkhove I hooked up Netlify to this repo, and pointed https://keda.sh to it. You should be able to stick your code here. In our contributor guide we’ll just enforce people need to open a PR on this repo if there are doc impacting features before they’ll get approved

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.