Tungsten Fabric cluster
All Tungsten Fabric services are delivered as separate containers deployed by
the Tungsten Fabric Operator (TFO). Each container generates its INI-based
configuration file at startup from environment variables. The Operator provides
these variables through Kubernetes ConfigMaps and Secrets. Service logs are
written to the host under /var/log/tf/<service>.
The Tungsten Fabric control plane, configuration, vRouter, and web UI services run as DaemonSets with the host network, without using the Kubernetes networking layer. These services listen directly on the host network interfaces. The backing data stores, which include Cassandra, ZooKeeper, RabbitMQ, and Redis, are managed by dedicated operators that the TFO deploys and run on the Kubernetes pod network.
The following diagram describes the minimum production installation of Tungsten Fabric with a Mirantis OpenStack for Kubernetes (MOSK) deployment.
For the details about the Tungsten Fabric services included in MOSK deployments and the types of traffic and traffic flow directions, see the subsections below.