Special Use

Our cluster combines various hardware resources from multiple universities and other organizations.

All Taints

Here’s the new taint system and their descriptions. To run on a node with a taint, you need to use the node toleration in your pod. Users may only tolerate values they are authorized for by cluster admins.

Examples of taint name changes from old to new system

Observable notebook with taints summary

Reservations

Our cluster contains several sets of nodes dedicated to certain groups.

Users can target ONLY THE GROUP NODES by using nodeAffinity, for example:

spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: nautilus.io/reservation
            operator: In
            values:
            - group1

For large jobs, this helps avoid consuming all shared cluster resources. Optionally, a higher priority can be used (contact the admins before using one).

In addition, groups may request exclusive access to entire nodes if their workloads justify it. Such nodes can be reserved by setting the following taint and corresponding toleration:

• Taint on reserved nodes:
  nautilus.io/reservation=group:NoSchedule

Please fill out the node reservation form if your group has a use case that would benefit from whole-node reservations.

Other taints

Some nodes in the cluster don’t have access to public Internet, and can only access educational network. They still can pull images from Docker Hub using a proxy.

If your workload is not using the public Internet resources, you might tolerate the nautilus.io/science-dmz and get access to additional nodes.