knative/client v0.16.0

Knative Client release v0.16.0

on GitHub

Release 0.16.0 brings some minor improvements and bug fixes. See the CHANGELOG for full details.

Meta

The compile dependencies have been updated to Knative Serving 0.16.0 and Knative Eventing 0.16.0.
This version of kn is working with Knative Serving backends >= 0.13.0 and Knative Eventing >= 0.14.0.

Incompatible change in Eventing support

For our experimental eventing support, we introduced a mapping syntax for specifying sinks for sources and triggers. This mapping can also be customised in the ~/.config/kn/config.yaml configuration. It turned out that this mapping was to redundant. E.g. a Knative service could be specified with an svc: or a service: prefix or when given without any prefix. To allow users to, e.g. add a Kubernetes service to this mapping, the following change has been introduced in 0.16:

• A Knative service can be specified with ksvc: or when not providing any prefix
• The prefixes svc: and service: have been removed so that a user can use those prefixes in their configuration file.
• Other mappings (broker:, http: and https:) have been left untouched.

New Features

• The list of plugins has been integrated to the help message that you get with kn --help. The name of the plugins and their file path is shown. If you use --help on a deeper level, then you will see nested plugins in the help text. E.g. a plugin kn-service-log is shown in kn service --help.
• kn service describe now supports a -o url option, which allows to print out only the service URL. This additional output format can be quite convenient when used in a scripting context like with curl $(kn service describe mysvc -o url)
• A new option --scale has been introduced for setting --min-scale and --max-scale to the same value. E.g. --scale 1 will set the number of replicas to exactly one (min and max scale are both set to one). Except for the syntax for the scale value to be expanded for more flexibility, see #822 for the discussion about syntax enhancements.
• kn service create and kn service update now support a flag --filename (or -f) so that you can use a resource descriptor in YAML or JSON format to initialise your service. At the moment additional command-line options are ignored, but in a future version the will be merged with the content of the referenced file (#923)
• The new multi-tenant broker can be fully managed with kn broker CRUD commands.
• kn service export has now an own dedicated type Export (group client.knative.dev, version v1alpha1) which contains the service definition and potentially all active revision that service routes to.

As always you find the full list of changes in the CHANGELOG.