Skip to content

Releases: knative/client

Knative Client release v1.1.0

14 Dec 14:10
530841f
Compare
Choose a tag to compare

Meta

The compile dependencies have been updated to Knative Serving v1.1.0, Knative Eventing v1.1.0 (Go module versions are v0.28.0).

Improved traffic split UI

The following improvements have been added for handling traffic splits of Knative Services:

  • You can now specify a tag to the latest revision already when creating a service with kn service create.
  • You can underspecify the traffic targets and leave out one for which the traffic portion will be automatically calculated so that all legs add up to 100%.
  • You can ommit the tag name when using --traffic. In this case @latest will be used for the update.
# Create service and tag the latest revsion with `head`
kn service create random --image rhuss/random:1.0 --tag head

# Update service to next version and create a 10:90 traffic split
kn service update random --image rhuss/random:2.0 --traffic 10

Released plugins

The kn-plugin-event plugin is now included since this release.

The plugins that are released in parallel and aligned with Knative v1.1.0 are:

All those plugins are released separately and are technically not part of this knative/client release, they are aligned however to share the same Knative dependencies and can be targeted for inlining.


You can find the complete list of changes in the CHANGELOG.

Knative Client release v1.0.0

02 Nov 19:38
a1cf5bf
Compare
Choose a tag to compare

Meta

The compile dependencies have been updated to Knative Serving v1.0.0, Knative Eventing v1.0.0 (Go module versions are v0.27.0).

Deprecated options cleanup

Approaching the Knative 1.0.0 milestone several deprecated options were removed.

  • --limits-cpu
  • --limits-cpu
  • --request-memory
  • --request-cpu
  • --min-scale
  • --max-scale
  • --lookup-path

Released plugins

The kn-plugin-quickstart plugin is now included since this release.

The plugins that are released in parallel and aligned with Knative v1.0.0 are:

All those plugins are released separately and are technically not part of this knative/client release, they are aligned however to share the same Knative dependencies and can be targeted for inlining.


You can find the complete list of changes in the CHANGELOG.

Knative Client release v0.26.0

22 Sep 17:19
61b8a75
Compare
Choose a tag to compare

Meta

The compile dependencies have been updated to Knative Serving 0.26.0, Knative Eventing 0.26.0.

Environment variables from file

There's a new flag --env-file that accepts provided file to populate environment variables. It simplify and shorten the resulting command for multiple environment variables entries at once. Accepted format of the file is KEY=VALUE pair per line.

Released plugins

The kn-plugin-source-kamelet plugin is now included since this release.

The plugins that are released in parallel and aligned with Knative 0.26 are:

All those plugins are released separately and are technically not part of this knative/client release, they are aligned however to share the same Knative dependencies and can be targeted for inlining.


You can find the complete list of changes in the CHANGELOG.

Knative Client release v0.25.1

16 Sep 12:06
99e2c92
Compare
Choose a tag to compare

Meta

The compile dependencies have been updated to Knative Serving 0.25.0, Knative Eventing 0.25.0 and Go version to 1.16.

Default plugin lookup in $PATH

The plugin lookup in $PATH has been enabled by default. This changes should improve local plugin development and testing. Furthermore the end user installation experience of plugins though package managers like Homebrew.

As a follow-up configuration property plugin.path-lookup has been deprecated.

Darwin/arm64 support

The native support for Apple's ARM64 chips has been added. All the future release will be published with the corresponding native binary.

Multicontainer support (experimental)

There's been added a new command kn container add to create Container snippets. The add command reuses all existing options flags manipulating Container know from kn service create.

In addition there's a new flag --extra-containers available for kn service create|update|apply that accepts YAML or JSON Containers to pass them to a Knative Service.

The command is marked as experimental and may change in the future releases.

Example

  The 'container add' represents utility command that prints YAML container spec to standard output. It's useful for
  multi-container use cases to create definition with help of standard 'kn' option flags. It accepts all container related
  flag available for 'service create'. The command can be chained through Unix pipes to create multiple containers at once.

  # Add a container 'sidecar' from image 'docker.io/example/sidecar' and print it to standard output
  kn container add sidecar --image docker.io/example/sidecar

  # Add command can be chained by standard Unix pipe symbol '|' and passed to 'service create|update|apply' commands
  kn container add sidecar --image docker.io/example/sidecar:first | \
  kn container add second --image docker.io/example/sidecar:second | \
  kn service create myksvc --image docker.io/example/my-app:latest --extra-containers -


You can find the complete list of changes in the CHANGELOG.

Knative Client release v0.25.0

11 Aug 05:21
035150e
Compare
Choose a tag to compare

Meta

The compile dependencies have been updated to Knative Serving 0.25.0, Knative Eventing 0.25.0 and Go version to 1.16.

Default plugin lookup in $PATH

The plugin lookup in $PATH has been enabled by default. This changes should improve local plugin development and testing. Furthermore the end user installation experience of plugins though package managers like Homebrew.

As a follow-up configuration property plugin.path-lookup has been deprecated.

Multicontainer support (experimental)

There's been added a new command kn container add to create Container snippets. The add command reuses all existing options flags manipulating Container know from kn service create.

In addition there's a new flag --extra-containers available for kn service create|update|apply that accepts YAML or JSON Containers to pass them to a Knative Service.

The command is marked as experimental and may change in the future releases.

Example

  The 'container add' represents utility command that prints YAML container spec to standard output. It's useful for
  multi-container use cases to create definition with help of standard 'kn' option flags. It accepts all container related
  flag available for 'service create'. The command can be chained through Unix pipes to create multiple containers at once.

  # Add a container 'sidecar' from image 'docker.io/example/sidecar' and print it to standard output
  kn container add sidecar --image docker.io/example/sidecar

  # Add command can be chained by standard Unix pipe symbol '|' and passed to 'service create|update|apply' commands
  kn container add sidecar --image docker.io/example/sidecar:first | \
  kn container add second --image docker.io/example/sidecar:second | \
  kn service create myksvc --image docker.io/example/my-app:latest --extra-containers -


You can find the complete list of changes in the CHANGELOG.

Knative Client release v0.23.2

06 Jul 10:07
2b78b83
Compare
Choose a tag to compare

kn 0.23.0 comes with bug fixes and API updates only.

Meta

The compile dependencies have been updated to Knative Serving 0.23.0 and Knative Eventing 0.23.0. There are no changes in the used API version for communicating with the backend. Eventing Sources APIServerSource, ContainerSource and SinkBinding are now accessed with their v1 API version (which implies, that you can manage those sources only for Knative installations that offer these sources in a v1 version, for older clusters you need to use kn <= 0.22). PingSource API access has been updated to v1beta2.


You can find the complete list of changes in the CHANGELOG

Knative Client release v0.24.0

29 Jun 20:59
0bbb3ec
Compare
Choose a tag to compare

Meta

The compile dependencies have been updated to Knative Serving 0.24.0 and Knative Eventing 0.24.0.

Improvement for configuring environment variables

A new option --env-value-from option has been added to kn service create and kn service update to allow referencing values from secrets and config maps. The order of environment variables are now kept according to the order --env related options are provided on the command line.


You can find the complete list of changes in the CHANGELOG

Knative Client release v0.23.1

15 Jun 10:09
1a2cfe3
Compare
Choose a tag to compare

kn 0.23.0 comes with bug fixes and API updates only.

Meta

The compile dependencies have been updated to Knative Serving 0.23.0 and Knative Eventing 0.23.0. There are no changes in the used API version for communicating with the backend. Eventing Sources APIServerSource, ContainerSource and SinkBinding are now accessed with their v1 API version (which implies, that you can manage those sources only for Knative installations that offer these sources in a v1 version, for older clusters you need to use kn <= 0.22). PingSource API access has been updated to v1beta2.


You can find the complete list of changes in the CHANGELOG

Knative Client release v0.23.0

19 May 07:53
3cc608f
Compare
Choose a tag to compare

kn 0.23.0 comes with bug fixes and API updates only.

Meta

The compile dependencies have been updated to Knative Serving 0.23.0 and Knative Eventing 0.23.0. There are no changes in the used API version for communicating with the backend. Eventing Sources APIServerSource, ContainerSource and SinkBinding are now accessed with their v1 API version (which implies, that you can manage those sources only for Knative installations that offer these sources in a v1 version, for older clusters you need to use kn <= 0.22). PingSource API access has been updated to v1beta2.


You can find the complete list of changes in the CHANGELOG

Knative Client release v0.22.0

07 Apr 01:27
33e2c9f
Compare
Choose a tag to compare

kn 0.22.0 comes with some bug fixes and minor feature enhancements. It's mostly a polishing release. If you are using the client API, there is a breaking change that was needed to align with Kubernetes client API's

Meta

The compile dependencies have been updated to Knative Serving 0.22.0 and Knative Eventing 0.22.0. There are no changes in the used API version for communicating with the backend.

Managing custom domain mappings

This release adds support for CRUD management of domain mappings. I.e. you can use kn domain along with its sub-commands create, update, describe, list and delete to fully manage DomainMapping resources for the installation of custom domains for Knative services.

# Create a domain mappings 'hello.example.com' for Knative service 'hello'
kn domain create hello.example.com --ref hello

# Update a domain mappings 'hello.example.com' for Knative service 'hello'
kn domain create hello.example.com --refFlags hello

# List all domain mappings
kn domain list

# Delete domain mappings 'hello.example.com'
kn domain delete hello.example.com

See kn domain help for more information.

Client API signature change

A context.Context object is added as the first argument to every Client API method to align with Kubernetes' client API signatures. This change does not affect any client's CLI usage, only if the client-specific Golang API is used for communicating with the Knative backend has changed. The migration is straight forward, either pass an already existing context down to the call or leverage one of the available standard contexts (like context.TODO()).

This change does not affect any CLI usage of the client.

Released plugins

The plugins that are released aligned with 0.22 are:

Minor updates

  • Fix kn export uses the Export format as the default
  • Added S column to specify built-in sources in kn source list-types
  • Added support for namespaces for all commands that takes a --sink option

You can find the complete list of changes in the CHANGELOG.