Skip to main content
Version: v5.0 Stable

Manage Allowed Node Types

Allowed node types control which node types can be referenced by NodeClaims created in a project. Use this to restrict tenants to a subset of the node types available on the platform. For example, you can use this to limit a project to a specific provider or instance class.

Project and tenant allowlists follow different rules

In a tenant's project, a project member reaches only what both the project and the tenant allow. The two layers write "everything" and "nothing" differently.

LayerFieldTo allow everythingTo allow nothing
ProjectallowedNodeTypes, a list of namesLeave the field unsetSet an empty list
Tenantallow.byLabels, a label selectorSet an empty selectorOmit the selector

An empty tenant selector matches every admin-owned node type. An omitted selector grants none by label, but the tenant still reaches any node type assigned to it or shared with every tenant. The tenant layer can also grant each node type by name with allow.byName. The tenant capability must also be enabled. A disabled capability withholds every node type, including ones assigned to the tenant.

A project allowlist can't add inventory the tenant was never granted. See Tenant boundary reference.

Behavior​

The project field is spec.allowedNodeTypes. Each entry has a name that is either an exact node type name (for example, aws.large) or a provider wildcard (such as aws.*, which matches every node type belonging to provider aws).

ValueEffect
Unset (field omitted)All node types are allowed. This is the default.
Empty list (allowedNodeTypes: [])No node types are allowed. NodeClaims in the project are rejected.
One or more entriesOnly allows node types matching any specified entry.

Matching rules:

  • Names are case sensitive.
  • The wildcard is only recognized as the suffix .*. aws.* matches aws.large but does not match awsx.large.
  • The platform rejects a NodeClaim that explicitly references a disallowed node type at creation time.
  • For unbound NodeClaims (no typeRef), the reconciler filters candidate node types against allowedNodeTypes at scheduling time and never assigns a disallowed type to the claim.
  • A NodeClaim that pins a machine with machineRef names no node type, but the platform still checks one. At least one node type that selects the machine has to match allowedNodeTypes. In a tenant project, that node type also has to be granted to the tenant. Otherwise the platform rejects the NodeClaim at creation time with machine "<name>" is not covered by a node type this project may use.

Changing allowedNodeTypes requires permission to update the project's allowedNodeTypes subresource.

Configure allowed node types​

Edit the project and set spec.allowedNodeTypes:

apiVersion: management.loft.sh/v1
kind: Project
metadata:
name: team-a
spec:
allowedNodeTypes:
- name: aws.*
- name: metal3.gpu-h100

This project can use any node type from the aws provider, plus the specific metal3.gpu-h100 type.

To disallow all node types in a project:

spec:
allowedNodeTypes: []