Knative/KEDA deprecation: tell us when you have migrated (or what blocks you)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 1/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- kubernetes, typescript
- Domain
- devops
Research direction
Read ADR-0041 and the migration guide at docs/migrating-from-knative.md, then identify whether your deployment uses Knative/KEDA or one of the listed P6 paths. Comment with your migration status, expected timing, or blocker; the issue is complete when users’ remaining dependencies and blockers are reported.
Written by the indexing model from the issue text.
Description
The Knative + KEDA deployment path is deprecated (ADR-0041, 2026-10-11). It receives security and breakage fixes only. Removal comes no earlier than the end of October 2026, and only once its remaining users have migrated. The guide is Migrating off the Knative/KEDA deployment.
Please comment with one of:
- I have moved to P6 (
deploy/k8s,deploy/vmordeploy/compose), or I never used the Knative path. - I am still on Knative and plan to move; say roughly when.
- I depend on async fan-out (
async: trueleaves drained by KEDAleaf-workerpods, Archetype A). There is no P6 equivalent yet. - I depend on the scheduled CronJob on-ramp (
cron-dispatch, Archetype C). There is no P6 equivalent yet. - Something else blocks me. Describe it.
Reports of the last three kinds move the earliest removal date.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 9
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 139
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/moca
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rossoctl/moca#421 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
braintrustdata/braintrust-sdk-javascript#2659 ·
Maintainers usually reply within 1 day
-
body-parser 2.3.0 in the published ai-dial-chat-bff image is vulnerable (CVE-2026-111181, HIGH)Possibly taken @illya-havsiyevych claimed this today. Openbug
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
epam/ai-dial-chat#9566 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
はさみアイコンを修正するOpenbug
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
area: core
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day