Embedded cluster deployment overview

The embedded cluster deployment installs Chef 360 Platform Server together with a Kubernetes environment that Chef provisions and manages. Choose this model when you need a self-managed deployment but don’t want to operate Kubernetes yourself.

Deployment stages

Review the system requirements, requirements reference, networking requirements, runtime configuration, and SELinux configuration.
Size your environment with capacity planning.
Install the platform using the embedded installation procedure.
Complete the post deployment verification.

Configure SELinux for Chef 360 Platform

This guide explains how to enable SELinux in the Kubernetes environment provided by Chef 360 Platform (k0s) on CentOS and Red Hat Enterprise Linux (RHEL). SELinux enforces mandatory access control policies…

Deploy Embedded Cluster

Deploy Chef 360 Platform Server with the Chef-managed embedded Kubernetes cluster.

Embedded cluster requirements

Chef 360 Platform has the following system requirements. Licensing A valid Chef 360 Platform license is required to install and run Chef 360 Platform. Hardware requirements Chef 360 Platform supports single-node and…

Embedded System Requirements

Review the requirements for deploying Chef 360 Platform with an embedded Kubernetes cluster.

Networking requirements

In-cluster networking Chef 360 Platform’s embedded cluster built-in network provider is Calico. Calico is a layer 3 container networking solution that routes packets to pods. For more information on in-cluster networking,…

Runtime configuration

Chef 360 Platform’s k0s comes bundled with containerd as the default container runtime interface (CRI) and runc as the default low-level runtime. Usually they don’t require any configuration changes, but…