Knative developer experience, docs, reference Knative CLI implementation
Go to file
Murugappan Chetty 4ea31c444a
build test images for e2e (#974)
* build test images before e2e

* build test images before e2e

* build test images for e2e

* build test images for e2e

* build test images for e2e

* build test images for e2e

* use built test image in smoke test

* use built test image in smoke test

* change tests to use built test image

* change tests to use built test image

* change tests to use built test image

* change tests to use built test image

* add common base image for all purpose

* build images for e2e

* rebase with master

* add non root base image

* add non root base image
2020-08-20 04:42:13 -07:00
.github correct typo in pull request template (#826) 2020-05-05 09:11:44 -07:00
cmd/kn Deprecates --max-scale/--min-scale for more consistent naming (#958) 2020-08-03 16:58:27 -07:00
config Use ko's strict mode for better errors messages (#706) 2020-03-07 12:11:27 -08:00
conventions Revisit sink prefixes: Support only 'ksvc' prefix and drop 'svc', 'service' support for knative service (#896) 2020-07-14 00:46:18 -07:00
docs Deprecates --max-scale/--min-scale for more consistent naming (#958) 2020-08-03 16:58:27 -07:00
hack Pin knative/pkg to release-0.17 (#976) 2020-08-11 12:23:05 -07:00
lib/test build test images for e2e (#974) 2020-08-20 04:42:13 -07:00
pkg Vendor serving and eventing at v0.17.0 (#984) 2020-08-20 03:22:13 -07:00
scripts/test-infra Sync knative/test-infra to latest in its release-0.17 branch (#977) 2020-08-11 23:12:05 -07:00
test build test images for e2e (#974) 2020-08-20 04:42:13 -07:00
third_party/VENDOR-LICENSE Pin knative/pkg to release-0.17 (#976) 2020-08-11 12:23:05 -07:00
vendor build test images for e2e (#974) 2020-08-20 04:42:13 -07:00
.gitignore Explicit name for serving client (#537) 2019-12-08 23:42:44 -08:00
.ko.yaml build test images for e2e (#974) 2020-08-20 04:42:13 -07:00
CHANGELOG.adoc build test images for e2e (#974) 2020-08-20 04:42:13 -07:00
LICENSE Initial commit 2018-12-12 16:45:51 -08:00
OWNERS Adds Navid (@navidshaikh) to approvers list (#321) 2019-07-31 13:59:43 -07:00
README.md fix(docs): Fix tekton task link in README (#934) 2020-07-15 05:59:32 -07:00
go.mod Vendor serving and eventing at v0.17.0 (#984) 2020-08-20 03:22:13 -07:00
go.sum Vendor serving and eventing at v0.17.0 (#984) 2020-08-20 03:22:13 -07:00

README.md

Kn

go.dev reference Go Report Card Releases LICENSE Slack Status

The Knative client kn is your door to the Knative world. It allows you to create Knative resources interactively from the command line or from within Shell scripts.

kn offers you:

  • Full support for managing all features of Knative Serving (services, revisions, traffic splits)
  • Growing support Knative eventing, closely following its development (managing of sources & triggers)
  • A plugin architecture similar to that of kubectl plugins
  • A thin client-specific API in golang which helps in tasks like synchronously waiting on Knative service write operations.
  • An easy integration of Knative into Tekton Pipelines by using kn in a Tekton Task.

This client uses the Knative Serving and Knative Eventing API exclusively so that it will work with any Knative installation, even those that are not Kubernetes based. It does not help in installing Knative itself though. Please refer to the various Knative installation options for how to install Knative with its prerequisites.

Documentation

Start with the user's guide to learn more. You can read about common use cases, get detailed documentation on each command, and learn how to extend the kn CLI. For more information, have a look at:

  • User guide
    • Installation - How to install kn and run on your machine
    • Examples - Use case based examples
    • FAQ (to come.)
  • Reference Manual - all possible commands and options with usage examples

Developers

We love contributions! Please refer to CONTRIBUTING for more information on how to best contributed to contribute to Knative.

For code contributions it as easy as picking an issue (look out for "kind/good-first-issue"), briefly comment that you would like to work on it, code, test, code and finally submit a PR which will trigger the review process.

More details on how to build and test can be found in the Developer guide.