Knative developer experience, docs, reference Knative CLI implementation
Go to file
Navid Shaikh ce519b520b
feat: Subscription CRUD (#1013)
* feat: Add subscription CRUD

 - Add kn subscription command group and CRUDL sub-commands
 - create/update uses following flag names for better alignment:
  - --sink for subscriber
  - --sink-reply for reply
  - --sink-dead-letter for dead-letter-sink
 - Add 'subscriptions' and 'sub' aliases
 - Introduce shared library `knative.dev/client/lib/printing`
   to print Sink object in describe output

* Set default channel type messaging.knative.dev/v1beta1:Channel

 i.e. if no prefix is given to `--channel`, consider it of `Channel` type

* Update e2e tests

* Update channel flag description
2020-10-01 09:44:29 -07:00
.github correct typo in pull request template (#826) 2020-05-05 09:11:44 -07:00
cmd/kn Add linting config and fix issues. (#1001) 2020-09-11 05:41:00 -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 feat: Subscription CRUD (#1013) 2020-10-01 09:44:29 -07:00
hack Ping serving and eventing to release-0.18 (#1033) 2020-09-29 22:41:28 -07:00
lib feat: Subscription CRUD (#1013) 2020-10-01 09:44:29 -07:00
pkg feat: Subscription CRUD (#1013) 2020-10-01 09:44:29 -07:00
scripts/test-infra upgrade to latest dependencies (#1028) 2020-09-29 03:32:28 -07:00
test feat: Subscription CRUD (#1013) 2020-10-01 09:44:29 -07:00
third_party/VENDOR-LICENSE [Release-0.18] Pin knative deps to release-0.18 (#1025) 2020-09-23 11:58:41 -07:00
vendor Ping serving and eventing to release-0.18 (#1033) 2020-09-29 22:41:28 -07:00
.gitignore Explicit name for serving client (#537) 2019-12-08 23:42:44 -08:00
.golangci.yaml Add linting config and fix issues. (#1001) 2020-09-11 05:41:00 -07:00
.ko.yaml build test images for e2e (#974) 2020-08-20 04:42:13 -07:00
CHANGELOG.adoc feat: Subscription CRUD (#1013) 2020-10-01 09:44:29 -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 a couple typos in README (#1007) 2020-09-11 14:56:01 -07:00
go.mod Ping serving and eventing to release-0.18 (#1033) 2020-09-29 22:41:28 -07:00
go.sum Ping serving and eventing to release-0.18 (#1033) 2020-09-29 22:41:28 -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 scripts.

kn offers you:

  • Full support for managing all features of Knative Serving (services, revisions, traffic splits)
  • Growing support for 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 with 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 APIs exclusively so that it will work with any Knative installation, even those that are not Kubernetes based. It does not help with 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.