serving
https://github.com/knative/serving
Go
Kubernetes-based, scale-to-zero, request-driven compute
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
Go not yet supported1 Subscribers
Add a CodeTriage badge to serving
Help out
- Issues
- All hops encrypted amongst internal and external services in Knative
- minScale treatment races reachability check
- Define (or document) appropriate NetworkPolicy/AuthorizationPolicy to prevent user access to autoscaler
- Don't scrape pods via HTTP if the activator in path.
- ResourceQuota error isn't reflected in kservice status
- [multi-container] How should Revision[CPU|Memory]Request defaults apply to revisions with multiple containers
- Failing pod never times out
- Should upgrade test run with all KIngress?
- Decouple autoscaling configuration from KSvc/Revisions/ConfigMap
- targetBurstCapacity does not behave correctly when there is more than one activator pod
- Docs
- Go not yet supported