Chef 360 Platform Server, node, and skill requirements

Review the following requirements for Chef 360 Platform Server, nodes, and skills.

Chef 360 Platform Server requirements

Hardware

Chef 360 Platform has the following minimum hardware requirements:

• 16 GB of RAM
• 4 vCPUs
• 80 GB of disk space

For production environments, run a benchmark test to determine your system’s requirements. The benchmark test should include the number of nodes you plan to enroll, the job frequency, output size, job duration, and check-in frequency.

Ports

Open the following ports if you are using default ports.

Ports for inbound connections:

Ports for outbound connections:

FQDN

Chef 360 Platform Server requires an FQDN that’s registered with a DNS and that all nodes can reach.

Node requirements

Nodes can be enrolled using two different methods, with a Chef Infra cookbook or with single-node enrollment from Chef 360 Platform. See the node requirements for those methods in the following sections.

Ports

Open the following default ports for outbound connections.

Cookbook-based enrollment

Nodes enrolled with Chef 360 Platform using a Chef Infra cookbook have the following requirements:

• Nodes must have Chef Infra Client installed.
• Nodes have a public DNS or public IP address.
• Nodes can’t have localhost (127.0.0.1) as an IP address.
• Nodes can’t have a CIDR address in the same range as the Chef 360 Platform services. The default CIDR range for Chef 360 Platform services is 10.244.0.0/16 or 10.96.0.0/12.
• You must have sudo privileges on the node.

Single-node enrollment

Nodes enrolled using single-node enrollment have the following requirements.

Connection requirements:

• Nodes must be accessible with SSH or WinRM.
• Nodes must have a public DNS or public IP address.
• A node IP address can’t be localhost (127.0.0.1)
• A node CIDR address can’t be in the same range as the Chef 360 Platform services. The default CIDR range for Chef 360 Platform services is 10.244.0.0/16 or 10.96.0.0/12.
• The node’s ports for RabbitMQ and the nginx API gateway must be open to Chef 360 Platform. Additionally, the Chef 360 Platform should allow inbound connections to these ports from the node.

Nodes connected to with SSH have the following requirements:

• Port 22 must be open.
• The user must have sudo privileges.
• The user must connect with an ed25519 or RSA(2048) login key without a passphrase.

Nodes connected to with WinRM have the following requirements:

• Ports 5985–5986 must be open.

• Configure WinRM by running the following:

  winrm quickconfig   # select Yes
  winrm set winrm/config/service/Auth '@{Basic="true"}'
  winrm set winrm/config/service '@{AllowUnencrypted="true"}'
  netsh advfirewall firewall add rule name="WinRM-HTTP" dir=in localport=5985 protocol=TCP action=allow
  

Skill requirements

Chef 360 Platform skills are supported on the following platforms.