New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Repo: autoscaler-keda
#1527
Comments
autoscaler-keda-hpa
custom-metrics-autoscaler
Thanks for raising this, I think this would be a great addition. wrt/ name, why not just |
+1 on Rolands proposal. This also points out that this is our "KEDA-integration". |
Changed to autoscaler-keda. Initially I had it autoscaler-keda-hpa but it is a bit verbose. |
+1 to the It make senses in a greater picture with prefix associations to certain WG as well. |
cc @davidhadas @cardil @upodroid @krsna-m any objections for approving this? |
+1 from me |
hi, |
+1 from me |
+1 !!!!!!!! I have linked to the KServe issue kserve/kserve#3561 |
Hi, knative folks 👋 |
+1 This would be great to have. I left a comment in kserve/kserve#3561 (comment). Feel free to join and discuss how the integration looks like. |
I will start working on this next week. RH Serving folks are off this week. |
+1 |
Use this issue type to request a new repo in
knative-extensions
(orknative
, which may require additional discussion).Repo information
Org:
knative-extensions
Repo:
autoscaler-keda
Go module (Optional):
knative.dev/serving-keda
Purpose (Description): This project targets to be a drop in replacement for the Knative Serving autoscaler-hpa component,
using keda for hpa management. For more details and a demo check https://github.com/skonto/serving-keda/blob/main/README.md.
Sponsoring WG: Serving and Operations.
Related issue: knative/serving#14877
Actions to fulfill
This area is used to track the repo creation process.
The requestor and sponsoring WG lead should perform the steps listed below and cross out the checkmarks when done.
The TOC is involved only in the TOC Gate steps.
You may not be able to use the Projects quick menu on this page. In that case, go to the project board and use the Add cards interface.
/peribolos/knative-extensions.yaml
. Please mind the alphabetical order when adding to a list.Knative Admin
theadmin
privilege.write
privilege.TOC Gate: Once the TOC has approved the above, it will merge and Peribolos will create an empty repository.
(golang) Send a PR to add aliases for
knative.dev/$REPONAME
import paths (sample).Have a lead from the sponsoring WG bootstrap the Git repository by using an
appropriate "template" repository (basic,
sample-controller,
sample-source).
Follow the instructions from Creating a repository from a template
Send a PR adding the repo to knobots. Then run the community files update action to propagate new OWNER_ALIASES.
Add your GitHub Team to the
OWNERS
file for your repo.Set up prow for a new repo
Bootstrap your CI jobs using hack project (look at other extensions repos for reference)
Create a sample PR to verify Prow (e.g., edit the boilerplate README)
Verify that within 24 hours the appropriate branch protections have been applied
requiring
tide
to pass before PRs are merged.(optional) Send a PR adding the repo to CLOMonitor (more information).
The text was updated successfully, but these errors were encountered: