b2254cbb42
* Update docs to use kubectl long flags * adding back in the --filename flag (lost when manually merged) * notice a few missed * notice a few missed '-f' flags * change -o to --output |
||
|---|---|---|
| .github | ||
| build | ||
| community | ||
| eventing | ||
| hack | ||
| images | ||
| install | ||
| serving | ||
| test | ||
| vendor | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| OWNERS | ||
| README.md | ||
| resources.md | ||
README.md
Welcome, Knative
Knative (pronounced kay-nay-tiv) extends Kubernetes to provide a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center.
Each of the components under the Knative project attempt to identify common patterns and codify the best practices that are shared by successful real-world Kubernetes-based frameworks and applications. Knative components focus on solving many mundane but difficult tasks such as:
- Deploying a container
- Orchestrating source-to-URL workflows on Kubernetes
- Routing and managing traffic with blue/green deployment
- Automatic scaling and sizing workloads based on demand
- Binding running services to eventing ecosystems
Developers on Knative can use familiar idioms, languages, and frameworks to deploy any workload: functions, applications, or containers.
Components
The following Knative components are currently available:
- Build - Source-to-container build orchestration
- Eventing - Management and delivery of events
- Serving - Request-driven compute that can scale to zero
Audience
Knative is designed with different personas in mind:
Developers
Knative components offer developers Kubernetes-native APIs for deploying serverless-style functions, applications, and containers to an auto-scaling runtime.
To join the conversation, head over to the Knative users Google group.
Operators
Knative components are intended to be integrated into more polished products that cloud service providers or in-house teams in large enterprises can then operate.
Any enterprise or cloud provider can adopt Knative components into their own systems and pass the benefits along to their customers.
Contributors
With a clear project scope, lightweight governance model, and clean lines of separation between pluggable components, the Knative project establishes an efficient contributor workflow.
Knative is a diverse, open, and inclusive community. To get involved, see CONTRIBUTING.md and join the Knative community.
Your own path to becoming a Knative contributor can begin anywhere. Bug reports and friction logs from new developers are especially welcome.
Documentation
Follow the links in this section to learn more about Knative.
Getting started
- Installing Knative
- Getting started with app deployment
- Getting started with serving
- Getting started with builds
- Getting started with eventing
Configuration and networking
- Configuring outbound network access
- Using a custom domain
- Assigning a static IP address for Knative on Google Kubernetes Engine
- Configuring HTTPS with a custom certificate
Samples and demos
- Autoscaling
- Source-to-URL deployment
- Binding running services to eventing ecosystems
- Telemetry
- REST API sample
- All samples for serving
- All samples for eventing
Logging and metrics
- Installing logging, metrics and traces
- Accessing logs
- Accessing metrics
- Accessing traces
- Setting up a logging plugin
Debugging
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.