Available in:  CE, BE, SE, SE+, EE

The module lifecycle stage: General Availability
The module has requirements for installation

The module does not require any configuration (it works right out-of-the-box).

How to explicitly enable the module…

You may explicitly enable or disable the module in one of the following ways:

  • Via Deckhouse web UI. In the “System” → “System Management” → “Deckhouse” → “Modules” section, open the pod-reloader module and enable (or disable) the “Module enabled” toggle. Save changes.

    Example:

    Module enable/disable interface

  • Via Deckhouse CLI (d8).

    Use the d8 system module enable command for enabling, or d8 system module disable command for disabling the module (you need Deckhouse CLI (d8), configured to work with the cluster).

    Example of enabling the module:

    d8 system module enable pod-reloader

  • Using ModuleConfig pod-reloader.

    Set spec.enabled to true or false in ModuleConfig pod-reloader (create it if necessary);

    Example of a manifest to enable module pod-reloader:

    apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: pod-reloader
spec:
  enabled: true

How to configure the module…

You can configure the module in one of the following ways:

  • Via Deckhouse web UI.

    In the “System” → “System Management” → “Deckhouse” → “Modules” section, open the pod-reloader module and enable the “Advanced Settings” switch. Fill in the required fields in the “Configuration” tab or specify the module settings in YAML format on the “YAML” tab, excluding the settings section. Save the changes.

    Example:

    Module Setup Interface

    You can also edit the ModuleConfig object pod-reloader on the “YAML” tab in the module settings window (“System” → “System Management” → “Deckhouse” → “Modules”, open the module pod-reloader) by specifying the schema version in the spec.version parameter and the necessary module parameters in the spec.settings section.

  • Via Deckhouse CLI (d8) (requires Deckhouse CLI (d8) configured to work with the cluster).

    Edit the existing ModuleConfig pod-reloader (for more details on configuring Deckhouse, see the documentation) by executing the following command:

    d8 k edit mc pod-reloader

    Make the necessary changes in the spec.settings section. If necessary, specify the schema version in the spec.version parameter. Save the changes.

    You can also create a file with manifest for ModuleConfig pod-reloader using the example below. Fill in the spec.settings section with the required module parameters. If necessary, specify the schema version in the spec.version parameter.

    Apply the manifest using the following command (indicate the manifest file name):

    d8 k apply -f <FILENAME>

    Example of a manifest for ModuleConfig pod-reloader:

    apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: pod-reloader
spec:
  version: 1
  enabled: true
  settings: # Module parameters from the "Parameters" section below.

How to change the module release channel…

To change the module release channel, follow the instruction.

Requirements

To the Deckhouse version: 1.68 and above.

Parameters

Schema version: 1

  • settings
    object
    • settings.nodeSelector
      object

      The same as in the pods’ spec.nodeSelector parameter in Kubernetes.

      If the parameter is omitted or false, it will be determined automatically.

      Example: 


      disktype: ssd
    • settings.reloadOnCreate
      boolean

      Rollout the workload in case of creating a ConfigMap or Secret.

      Enabling the parameter will cause the workload to restart not only when changing the corresponding ConfigMap or Secret, but also when creating it.

      Default: true

      Examples: 


      reloadOnCreate: true

      reloadOnCreate: false
    • settings.reloadOnDelete
      boolean

      Rollout the workload in case of deleting a ConfigMap or Secret.

      Enabling the parameter will cause the workload to restart when deleting the corresponding ConfigMap or Secret.

      Default: false

      Examples: 


      reloadOnDelete: true

      reloadOnDelete: false
    • settings.reloadStrategy
      string

      Strategy to use for triggering reload.

      EnvVars - Adds a dummy environment variable to any container referencing the changed resource (e.g., Deployment, StatefulSet, etc.). This forces Kubernetes to perform a rolling update. Annotations - Adds a pod-reloader.deckhouse.io/last-reloaded-from annotation to the pod template metadata. Ideal for GitOps tools like ArgoCD, as it avoids triggering unwanted sync diffs.

      Default: EnvVars

      Allowed values: EnvVars, Annotations

      Examples: 


      reloadStrategy: EnvVars

      reloadStrategy: Annotations
    • settings.tolerations
      array of objects

      The same as in the pods’ spec.tolerations parameter in Kubernetes;

      If the parameter is omitted or false, it will be determined automatically.

      Example: 


      tolerations:
- effect: NoSchedule
  key: key1
  operator: Equal
  value: value1
- effect: NoSchedule
  key: key1
  operator: Exists
      • settings.tolerations.effect
        string
      • settings.tolerations.key
        string
      • settings.tolerations.operator
        string
      • settings.tolerations.tolerationSeconds
        integer
      • settings.tolerations.value
        string