dSSM Database¶

The BIG-IP Next for Kubernetes distributed Session State Management (dSSM) pods provide centralized and persistent storage for the Traffic Management Microkernel (TMM) pods. The dSSM pods are Redis data structure stores that maintain application traffic data. The dSSM pods bind to Kubernetes persistence volumes to persist data in the event of a container restart.

The dSSM pods are now gets deployed in affinity_type.preferred.

Parameter

Setting	Description
preferred	Attempt to schedule pods onto unique nodes, but two dSSM pods may schedule onto a single node when no schedulable nodes exists.

parameter example:

db:
  affinity_type: "preferred"

Sentinel Service¶

After installing dSSM, a dSSM Sentinel Service is created that receives data from TMM on TCP service port 26379, and forwards to the dSSM DB pods using the same service port number. Ensure the Service port is available, and the cluster has CoreDNS enabled. In this example, the BIG-IP Next for Kubernetes components will need to resolve the f5-dssm-sentinel.f5-utils hostname.

Example dSSM Sentinel Service:

Name:              f5-dssm-sentinel
Namespace:         f5-utils
IP:                10.106.99.127
Port:              sentinel  26379/TCP
Endpoints:         10.244.1.15:26379,10.244.1.20:26379,10.244.4.3:26379

Supplemental¶

Previous Next