Chef 360 Platform cluster configuration

Use the Admin Console configuration page to configure Chef 360 Platform.

Note

The Chef Platform Installer manages the underlying Kubernetes resources, so changes made directly to those resource aren’t permanent.

The Chef 360 Platform installation process supports a wide range of architectures, deployment models, and cluster sizes.

Note

Depending on your Chef 360 Platform license, version, and distribution, some options may not be available.

Configuration options

This section describes the options available and the pre-flight checks performed as part of the configuration updates.

Experimental settings

Experimental settings enable the configuration of preview features or the display of settings/configuration options being considered for future implementation. The use of experimental settings isn’t supported in production environments.

Note

This option is only available to customers with a specific entitlement.

Show add-ons

This option enables add-ons to be displayed or used for optional inclusion into the Chef 360 Platform installation. Note that these add-ons all have unique hardware requirements and must be factored into your cluster sizing. For detailed information on cluster add-ons, refer to the add-on documentation.

Advanced configuration

This option enables advanced configuration settings. Advanced configuration settings are designed to only be required to tune a deployment to meet specific customer needs or address unique configuration requirements for a given customer environment. Consult with your Chef account team or Customer Support before deploying with advanced settings to ensure they’re recorded in your account to assist with future support requests.

Deployment type

Warning

Deployment type is currently an experimental setting.

Note

If installing Chef 360 Platform’s primary node, select principal.

Chef 360 Platform is available in two deployment types:

Principal: The principal deployment type installs the primary server environment. The principal is the source of truth for all data and initiates all actions.
Outpost: The outpost deployment type is designed to facilitate access to Chef 360 Platform into different network segments and regions. An outpost is a small subset of the Chef 360 Platform services that act as an “access point” for nodes to connect to. The Outposts forward those requests to the assigned Principal.

Cluster mode

Single Node clusters are intended for use in non-production, small-scale deployments or evaluations. Use a multi-node cluster for most production use cases.
HA / Multi-Node clusters are intended for production use cases. In addition to selecting this box, external dependencies (such as a load balancer) must be supplied.

Warning

Deploy multi-node clusters with an odd number of nodes unless a dedicated control plane is allocated.

Required configuration options

Required configuration options are as follows:

A Default Tenant configuration must be supplied.
An SMTP server must be selected for the tenant.
A default Tenant administrator must be identified for the tenant.

All additional settings sections are optional. Refer to each section in this document for further details about that specific settings category.

Add-ons

An add-on is a Chef 360 Platform extension or enhancement that adds new features or functionality to the cluster. Add-ons aren’t required to use Chef 360 Platform, but they can…

Tenant configuration

Chef 360 Platform uses a multi-tenant software architecture. A tenant is a group of users that share common access to a software application’s instance. In Chef 360 Platform, a tenant…