Knative developer experience, docs, reference Knative CLI implementation
Go to file
Roland Huß 4691210013
Deprecate `lookup-path` option and updated relevant documentation (#1422)
* Deprecate `lookup-path` option and updated relevant documentation

Lookup in path is now the default for all plugins.
This option will be removed eventually in a future version,
when path lookup is enabled uncoditinally and can't be turned of.

* Review fixes

* remove trailing whitespace

* readd config to make test coverage happy
2021-08-10 03:54:12 -07:00
.github Update actions (#1416) 2021-08-05 00:19:52 -07:00
cmd/kn Fix issue with Windows pathes not being escaped when applying a regexp. (#1395) 2021-07-21 09:22:39 -07:00
config Use ko's strict mode for better errors messages (#706) 2020-03-07 12:11:27 -08:00
conventions Fix various misspellings and linter items (#1057) 2020-10-12 21:24:30 -07:00
docs Deprecate `lookup-path` option and updated relevant documentation (#1422) 2021-08-10 03:54:12 -07:00
hack Add support for multi-containers (#1382) 2021-08-09 12:25:12 -07:00
lib Adding class option to broker create (#1402) 2021-08-06 06:36:20 -07:00
pkg Deprecate `lookup-path` option and updated relevant documentation (#1422) 2021-08-10 03:54:12 -07:00
test Add support for multi-containers (#1382) 2021-08-09 12:25:12 -07:00
third_party/VENDOR-LICENSE upgrade to latest dependencies (#1387) 2021-07-19 16:15:12 -07:00
tools/knb feat: Add knb plugin build tool (#1226) 2021-03-08 00:22:21 -08:00
vendor upgrade to latest dependencies (#1417) 2021-08-09 23:28:12 -07:00
.codecov.yaml add code cov (#1313) 2021-05-17 11:47:31 -07:00
.gitignore feat: Add knb plugin build tool (#1226) 2021-03-08 00:22:21 -08:00
.golangci.yaml Enable gosec linter and fix existing issues (#1228) 2021-02-16 02:17:26 -08:00
.ko.yaml build test images for e2e (#974) 2020-08-20 04:42:13 -07:00
CHANGELOG.adoc Deprecate `lookup-path` option and updated relevant documentation (#1422) 2021-08-10 03:54:12 -07:00
LICENSE Initial commit 2018-12-12 16:45:51 -08:00
OWNERS Add knative-release-leads to OWNERS (#1317) 2021-05-17 09:45:24 -07:00
OWNERS_ALIASES Update community files (#1400) 2021-07-26 11:45:16 -07:00
README.md add code cov (#1313) 2021-05-17 11:47:31 -07:00
go.mod upgrade to latest dependencies (#1417) 2021-08-09 23:28:12 -07:00
go.sum upgrade to latest dependencies (#1417) 2021-08-09 23:28:12 -07:00

README.md

Kn

go.dev reference Go Report Card Releases LICENSE Slack Status codecov

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.