1. References
  2. Release Notes

Release note V1.8.0

Release Date: 2023-01-13

StreamNative Platform 1.8.0 is now available. This release includes some major documentation updates for the following topics.

  • StreamNative Platform Upgrade

    StreamNative Platform 1.8.0 brought some breaking changes that deprecated several APIs. Some StreamNative Platform components are affected due to these deprecated APIs. If you installed StreamNative Platform using a custom values.yaml instead of the default values.yaml file that is brought by the sn-platform chart, pay special attention to these affected components when you upgrade StreamNative Platform components from previous releases to StreamNative Platform 1.8.0 or later. For details about how to upgrade StreamNative Platform, see upgrade StreamNative Platform.

  • Authentication

    StreamNative Platform supports Json Web Token (JWT) authentication, which uses a JWT token to authenticate a Pulsar client and associate the Pulsar client with some "role". The "role" determines what actions the Pulsar client is authorized to perform, such as publishing or consuming messages to or from a given topic.

    For details about how to configure JWT authentication on StreamNative Platform, see configure JWT authentication.

  • TLS encryption

    StreamNative Platform supports enabling TLS encryption with cert-manager on StreamNative Platform components. cert-manager supports issuing certificates from an internal issuer or a public issuer. In previous releases, you can use a selfsigning internal issuer or a public issuer to sign a certificate. In this release, StreamNative Platform also supported the secret and custom internal issuer types. For details about how to configure the internal issuer types, see enable TLS encryption with cert-manager.

  • WebSocket service

    StreamNative Platform supports the WebSocket service, which provides a simple way for a Pulsar client to interact with a Pulsar through the WebSocket API. In this release, we add a document about how to enable the WebSocket service. For details, see enable WebSocket service.