* Update unit test for invalid concurrency target value * Vendor v0.16.0 eventing and serving * Commit the LICENSES generated by hack/update-deps.sh * Spare third_party dir from license check in hack/build.sh * Update eventing and serving version for 'kn version' * Use DeprecatedInjectionAnnotation key for backward compatibility Fixes #918 Use DeprecatedInjectionAnnotation, i.e. "knative-eventing-injection" for reconciling broker via namespace labeling and trigger annotations. From eventing v0.16.0 release, this key is changed to "eventing.knative.dev/injection" however, older eventing installation wont recognize it. So we continue using the deprecated key until the sugar-controller would support reconciling on either keys. * Fix(kn version): Display eventing.knative.dev at v1beta1 version We've been showing 'v1alpha1' in kn version while we actually vendor and refer v1beta1 for eventing.knative.dev * chore(e2e): Run tests against serving/eventing v0.16.0 release * Update test for concurrency-target to expect new error message the new error message for incorrect concurrency-target value contains "should be at least 0.01" * Setup sugar-controller for released eventing version setup - reuse knative_setup util from common lib for latest-release CI setup * Fix typo in YAML URL and add subheader for sugar-controller install |
||
|---|---|---|
| .github | ||
| cmd/kn | ||
| config | ||
| conventions | ||
| docs | ||
| hack | ||
| lib/test | ||
| pkg | ||
| scripts/test-infra | ||
| test | ||
| third_party/VENDOR-LICENSE | ||
| vendor | ||
| .gitignore | ||
| CHANGELOG.adoc | ||
| LICENSE | ||
| OWNERS | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
README.md
Kn
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
kubectlplugins - 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
knin a TektonTask.
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
knand run on your machine - Examples - Use case based examples
- FAQ (to come.)
- Installation - How to install
- 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.