Deploy Tungsten Fabric¶

Deployment of Tungsten Fabric (TF) is managed by the tungstenfabric-operator Helm resource in a respective MOS ClusterRelease.

To deploy TF:

Optional. Configure the ASN and encapsulation settings if you need custom values for these parameters. For configuration details, see Autonomous System Number (ASN).
Verify that you have completed all prerequisite steps as described in Tungsten Fabric deployment prerequisites.
Create the tungstenfabric.yaml file with the TF resource configuration. For example:
```
apiVersion: operator.tf.mirantis.com/v1alpha1
kind: TFOperator
metadata:
  name: openstack-tf
  namespace: tf
spec:
  settings:
    orchestrator: openstack
```
If you do not specify tfVersion, MOSK deploys TF 2011.

Note

The TF 21.4 version is available for deployment as technical preview only.
Configure the TFOperator custom resource according to the needs of your deployment. For the configuration details, refer to TFOperator custom resource and API Reference.
Trigger the TF deployment:
```
kubectl apply -f tungstenfabric.yaml
```
Verify that TF has been successfully deployed:
```
kubectl get pods -n tf
```
The successfully deployed TF services should appear in the Running status in the system response.
If you have enabled StackLight, enable Tungsten Fabric monitoring by setting tungstenFabricMonitoring.enabled to true as described in StackLight configuration procedure.

Since MOSK 23.1, tungstenFabricMonitoring.enabled is enabled by default during the TF deployment. Therefore, skip this step.