Label TMM nodes

Introduction

The data-plane component of a CNE instance is the F5 Traffic Management Microkernel (TMM) workload. When installing using Helm, you can optionally restrict TMM pods to specific nodes (for example, to ensure those nodes have the appropriate resources for the TMM pods scheduled on them).

Note

Regardless of whether you restrict TMM pods to specific nodes, nodes that don’t otherwise prevent TMM from being scheduled must meet additional requirements. For example, the combined total of those nodes must have enough 2 mebibyte hugepages (hugepages-2Mi) to accommodate the needs of all TMM pods that will be scheduled.

How you restrict TMM pods for a CNE instance (optional)

Restricting TMM pods to specific nodes requires that you do the following:

  • Label each node on which you want Kubernetes to be able to schedule TMM pods.

  • When you later install a CNE instance, specify that same label as the node selector.

Note

If you don’t want to restrict TMM pods, don’t label TMM nodes, and eliminate the node selector, so Kubernetes may schedule TMM pods on any node that doesn’t otherwise prevent TMM from being scheduled.

For more information, see Assigning Pods to Nodes.

Label TMM nodes

Note

Perform this task only if you want to restrict TMM pods to specific nodes.

  1. List all the nodes in your cluster:

    kubectl get nodes

  2. Choose the node you want to label.

  3. Label the node so Kubernetes can schedule TMM pods on it:

    kubectl label node <NODE> f5.com/can-schedule-tmm=true

  4. If you want to label another node, go to step 2.

  5. Verify that the label was applied to all the nodes you labeled:

    kubectl get nodes -l f5.com/can-schedule-tmm=true

Next steps