Skip to main content

Plan your Chef 360 Platform system

Use this page to plan a Chef 360 Platform system before you deploy it. After completing this page, you will have a documented system design that matches your deployment model, workload, platform, and support requirements.

Chef recommends planning the deployment model and capacity before selecting an installation procedure. Use the embedded cluster deployment when Chef manages the underlying Kubernetes environment. Use bring your own Kubernetes (BYOK) when your organization manages the Kubernetes cluster and its supporting infrastructure.

Before you begin

  • Identify whether you are deploying Chef 360 Platform in an on-premises environment or another supported deployment model.
  • Confirm the Chef 360 Platform version you plan to deploy.
  • Identify the workloads, node count, availability requirements, and data retention needs for your environment.
  • Review the system requirements.

Plan your system

  1. Record the Chef 360 Platform version and deployment model for your environment.

  2. Determine the expected node count, workload, and growth rate.

  3. Choose the deployment topology that matches your node count and availability requirements:

    • Hyperconverged Non-HA: a single instance of each platform service, for evaluation, lab, or development environments. No fault tolerance.
    • Hyperconverged HA: three replicas of each platform service across three or more nodes, for small production environments with moderate workload requirements.
    • Tiered-HA: dedicated backend and frontend worker pools for medium production environments that need to scale backend and frontend workloads independently.
    • Hyperscale HA: maximum separation between backend and frontend workloads, for large production environments that need predictable resource allocation and independent scaling.

    If you’re planning an embedded cluster deployment, note that the first (bootstrap) node is always labeled controller and this can’t be changed after installation. Plan your node roles with this constraint in mind.

  4. Select the infrastructure, storage, networking, and security configuration that meets the applicable requirements for your chosen topology.

  5. Confirm that the planned configuration is supported for your platform and entitlement.

  6. Document the design and obtain the required operational approvals before deployment.

Confirm your plan

Verify that your system plan identifies the Chef 360 Platform version, deployment model, topology, platform, capacity, storage, networking, security requirements, and entitlement considerations.

Next steps

After you document your plan, review the system requirements for your chosen deployment model to confirm that your planned deployment meets the applicable server, node, platform, storage, and networking requirements:

For sizing guidance, see capacity planning.

Need access to this capability?

Chef 360 Platform capabilities and deployment options may depend on your product subscription, license, or entitlement. Review the Chef 360 Platform product page to learn more and connect with the marketing or account team about access and deployment options.

Thank you for your feedback!

×