Bahriya Tersane

Sipar

The gateway and service mesh for Kubernetes.

Sipar is the traffic layer of the cluster. Sipar Gateway receives HTTP, TCP and TLS traffic and routes it to your applications, applying your rules before a request reaches them. Sipar Mesh gives every workload an identity and encrypts the traffic between services with mutual TLS.

Sipar is included with every Bahriya Kubernetes Engine licence. On any other conformant Kubernetes distribution, Sipar is part of the Tersane licence, at no extra price.

Two parts

At the edge of the cluster, and between its services.

Sipar Gateway

  • Routing by standard. HTTP, TCP and TLS routes are written in the Kubernetes Gateway API.
  • Rate limits and authentication. Per route and per path, counted once across every gateway replica, with basic authentication and address rules beside them.
  • A response cache. In Memcached or Valkey, after the access checks, so a refused client is refused on a cached response too.
  • Access by address for TCP. A refused client is disconnected before the backend is reached, and receives nothing.
  • Traceable requests. A request identifier on every response, and one JSON log line per request, with no credentials or query strings.

Sipar Mesh

  • Workload identity. Every workload in an enrolled namespace receives a cryptographic identity.
  • Mutual TLS. Traffic between enrolled services is encrypted and authenticated in both directions.
  • No change to applications. No proxy runs beside each application; enrolment is a property of the namespace.
  • Opt in, and opt out. Off until the cluster enables it, and removable without reinstalling applications. With the Bahriya Kubernetes Engine.

How it is built

Open projects, used unmodified.

Sipar Gateway is built on Envoy Gateway and the Kubernetes Gateway API, and Sipar Mesh on Istio's ambient mode. All three are projects of the Cloud Native Computing Foundation. Sipar does not modify them: its own code runs only at the extension points they publish, an extension server for TCP access and an external processor for the cache. An upstream security release therefore reaches Sipar without a modified copy to bring up to date.

The gateway is installed once per cluster by the sipar-gateway chart. Each application declares its own routes and policies with the sipar-route library chart, in its own namespace, so the platform team owns the gateway and each application team owns only its routes.

Availability

Sipar is included with every Bahriya Kubernetes Engine licence, and is installed and upgraded with the cluster. On another conformant distribution, Sipar Gateway is installed from the Tersane chart repository under a Tersane licence. Its images are private, and are pulled with the image token the licence provides, as described in Gaining access.

Read the documentation

How Sipar is obtained and installed, and every setting of its two charts.

Sipar documentation