Preview on StormForge Documentation

Configure optimization using CRDs

Mon, 01 Jan 0001 00:00:00 +0000

StormForge’s optimization configuration options ensure consistent right-sizing across workloads and give teams control over their work.

Platform teams can set organization-wide default optimization values
Platform teams can provide different default optimization values for all workloads matching a type or label selector
Development teams can fine-tune settings further for workloads in their namespaces, or for those matching specific label selectors

Optimization configurations are Custom Resource Definitions (CRDs) consisting of rules evaluated and applied to workloads in definition order.

HPA Reconciliation

Mon, 01 Jan 0001 00:00:00 +0000

The applier has a reconciliation mode in which it will watch objects associated with workloads that have recommendations applied, and automatically reconcile changes to keep workload settings in sync with the applied recommendations after events such as helm upgrade.

When using the webhook to apply recommendations, the only resource type that needs reconciliation is the HPA. The latest applier supports enabling reconciliation for individual resource types.

To enable reconciliation for HPA resources only, use the following Helm values when installing or upgrading the applier:

Optimize custom workloads using CRDs

Mon, 01 Jan 0001 00:00:00 +0000

When to use this guide

Use this guide if your organization defines workloads with CRDs, for example:

Custom workloads unique to your organization’s platform.
Third-party operators such as GitHub’s Actions Runner Controller (ARC) or Apache Spark applications.

By default, StormForge supports standard Kubernetes workload types such as Deployments, StatefulSets, and DaemonSets, as well as common third-party workload types, such as Argo Rollouts.

StormForge also supports custom workload types defined by Custom Resource Definitions (CRDs). If your CRD represents the workload itself, you can configure StormForge to recognize and optimize it using the workloadResourceTypes Helm parameter.

Optimize workloads owned by custom operators using CRDs

Mon, 01 Jan 0001 00:00:00 +0000

When to use this guide

Use this guide if your organization manages workloads with custom operators and you want greater control over owner identification and patch application.

In Kubernetes, operators—or custom controllers—can manage workloads. For example, a custom resource might own and manage a Deployment workload. StormForge automatically detects these ownership relationships.

When another resource (an operator) owns a workload, StormForge typically targets this owner for patching rather than the workload. This way, changes persist and aren’t overwritten by the operator’s reconciliation loop.