Blog
6 minn read

Introducing StreamNative Platform 1.5

streamnative platform

We are pleased to announce the release of StreamNative Platform 1.5. StreamNative Platform provides an easy way to build mission-critical messaging, streaming applications, and real-time data pipelines. It integrates data from multiple sources into a centralized messaging and event streaming platform. With release 1.5, we have further simplified management tasks for Pulsar traffic with the integration with Istio, providing a visualized way for you to create and manage connectors on the StreamNative Console.

This release features the following major enhancements:

  • Provides a deeper integration with Istio
  • Supports deployment on OpenShift
  • Simplifies the use of Function Mesh and Connectors

Deeper integration with Istio

StreamNative Platform began supporting integration with Istio in release 1.3. It creates VirualService and Gateway resources when Istio-related configurations are enabled on StreamNative Platform. In release 1.5, we provide more improvements to simplify the traffic proxy for Pulsar Protocol, Kafka Protocol, and MQTT Protocol.

Integrate cert-manager with Istio Ingress Gateway: On StreamNative Platform 1.3, we had to manually create the TLS secret in the Istio root namespace. With release 1.5, we have added support for cert-manager, which enables the Istio TLS secret to be automatically created and managed by cert-manager.

Expose MoP on the Istio Gateway: StreamNative Platform supported MoP in release 1.4. In release 1.5, we added MoP-related VirualService and Gateway resources support. Now, StreamNative Platform can expose Pulsar Protocol, Kafka Protocol, and Mqtt Protocol through the Istio Gateway in a unified way.

Support deployment on OpenShift

OpenShift is one of the most popular enterprise-ready Kubernetes container platforms. As such, adding support for OpenShift gives you more options and flexibility when you deploy StreamNative Platform 1.5 on the container platform. To enable OpenShift, set the following configurations in the Helm chart values.yaml file.

<script>
# Support deployment on OpenShift
openshift:
  enabled: true
  ssc:
    enabled: true

vault:
  securityContext:
    runAsUser: 0

zookeeper:
  securityContext:
    runAsUser: 0

bookkeeper:
  securityContext:
    runAsUser: 0

autorecovery:
  securityContext:
    runAsUser: 0

broker:
  securityContext:
    runAsUser: 0

proxy:
  securityContext:
    runAsUser: 0

toolset:
  securityContext:
    runAsUser: 0

streamnative_console:
  securityContext:
    runAsUser: 0
<script> 

Simplify the use of Function Mesh and Connectors

StreamNative Platform 1.5 adds support for the Function Mesh Worker service. You can enable Function Mesh by setting functionmesh.enabled to true in the Helm chart values.yaml file.

<script>
broker:
  functionmesh:
    enabled: true
<script> 

With release 1.5, you can leverage Function Mesh while still using the pulsar-admin or pulsarctl tools to manage Pulsar functions and connectors.

Simplify the use of Function Mesh and Connectors

To simplify the use and management of connectors on StreamNative Platform, the Connector page is now available on the StreamNative Console. This new page enhances the user experience by providing a visualized way for you to create and manage connector-related resources. For example, now you can create source/sink connector jobs, update connector job configurations, and review connector job exception logs on the StreamNative Console.

streamnative platform

For more information, refer to the StreamNative Platform 1.5 Release Notes.

Eric Shen
Eric Shen is the Solution Engineer of StreamNative. He previously worked at Microsoft & Qiniu & PingCAP & Hikvision mainly focusing on Cloud, Storage, Database. He is quietly interested in open source software and distributed systems.

Newsletter

Our strategies and tactics delivered right to your inbox

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.