Skip to main content

Chef 360 Platform and node requirements

Review the following requirements for Chef 360 Platform and nodes before starting this guide.

Node requirements

This guide describes two methods of enrolling nodes, either 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.

For more information on these enrollment methods, see the node enrollment guide or the node enrollment documentation.

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
    

Chef 360 Platform Server requirements

Hardware requirements

Chef 360 Platform has the following minimum hardware requirements:

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

Note

If the root directory has space restrictions, mount the following directories before installing:

  • /var/lib/k0s/
  • /run/k0s/
  • /var/lib/embedded-cluster
  • /etc/k0s/

Ports

Open the following ports if you are using default ports.

Ports for inbound connections:

PortDescription
30000Chef 360 Platform Console
31000API Gateway
31050RabbitMQ
31100Mailhog (Optional)
22SSH
5985–5986WinRM

Ports for outbound connections:

PortDescription
443For non-air gapped installations

FQDN

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

Next step

Thank you for your feedback!

×











Search Results