Configure the controller manager

The LeaderWorkerSet (LWS) controller manager reads its component configuration from the file passed to the --config flag. New configuration files should use the stable config.lws.x-k8s.io/v1 API.

Configuration example

The following configuration enables leader election and internal certificate management. Fields that are not specified use their default values.

apiVersion: config.lws.x-k8s.io/v1
kind: Configuration
leaderElection:
  leaderElect: true
internalCertManagement:
  enable: true

When installing from source or with Kustomize, edit config/manager/controller_manager_config.yaml before building or applying the manifests. The generated controller Deployment mounts this configuration and passes its path with --config.

The Helm chart also renders a v1 controller configuration. Use chart values to configure the settings exposed by the chart, including certificate management, feature gates, and gang scheduling. See the values.yaml file and the Helm chart configuration for the available values.

Migrate from v1alpha1

Existing v1alpha1 configuration files continue to work and are converted to v1 when the controller starts. Loading one emits a deprecation warning because v1alpha1 will be removed in a future release.

To migrate, change the apiVersion; the field names remain unchanged:

-apiVersion: config.lws.x-k8s.io/v1alpha1
+apiVersion: config.lws.x-k8s.io/v1
 kind: Configuration

Redeploy the controller after updating the configuration. For a Kustomize installation, rebuild and apply the manifests. For a Helm installation, upgrade to a chart that renders the v1 configuration.