Node autoscaling is available on few clouds; you can find details in the relevant cloud section. You can configure the autoscaler option to automatically scale the number of machines in a cluster.
Customers can create and run daemonsets on SAAP. To restrict daemonsets to only run on worker nodes, use the following
... spec: nodeSelector: role: worker ...
Multiple Availability Zone
In a multiple availability zone cluster, control plane nodes are distributed across availability zones and at least one worker node is required in each availability zone.
Custom node labels are created by Stakater during node creation and cannot be changed on SAAP at this time. However, custom labels are supported when creating new machine pools.
SAAP is run as a managed service and is kept up to date with the latest OpenShift Container Platform version, see change management in responsibilities. Upgrade scheduling to the latest version is available.
SAAP runs on OpenShift 4 and uses CRI-O as the only available container engine.
SAAP runs on OpenShift 4 and uses Red Hat CoreOS as the operating system for all control plane and worker nodes.
Upgrades can be done either immediately or be scheduled at a specific date by opening a support ticket.
See the SAAP Update Life Cycle for more information on the upgrade policy and procedures.
Kubernetes Operator Support
All operators listed in the Operator Hub marketplace should be available for installation. These operators are considered customer workloads, and are not monitored by Stakater SRE, see customer applications responsibilities.
Red Hat Operator Support
Red Hat workloads typically refer to Red Hat-provided operators made available through Operator Hub. Red Hat workloads are not managed by the Stakater SRE team, and must be deployed on worker nodes and must be managed by the customer, see customer applications responsibilities.