For more information on how pod priority works, refer to the .

    Setting Priority Class

    Longhorn system contains user deployed components (e.g, Longhorn manager, Longhorn driver, Longhorn UI) and system managed components (e.g, instance manager, engine image, CSI driver, etc.) You need to set Priority Class for both types of components. See more details below.

    1. Set taint Priority Class for system managed components: follow the to set Priority Class by changing the value for the default setting

    Setting Priority Class After Longhorn Installation

    1. Set taint Priority Class for system managed components: The Priority Class setting can be found in the Longhorn UI by clicking Setting > General > Priority Class.
    2. Set taint Priority Class for user deployed components: modify the Helm chart or deployment YAML file depending on how you deploy Longhorn.

    Users can update or remove the Priority Class here, but note that this will result in recreation of all the Longhorn system components. The Priority Class setting will reject values that appear to be invalid Priority Classes.

    Usage

    Before modifying the Priority Class setting, all Longhorn volumes must be detached.

    Don’t operate the Longhorn system after modifying the Priority Class setting, as the Longhorn components will be restarting.

    Do not delete the Priority Class in use by Longhorn, as this can cause new Longhorn workloads to fail to come online.

    Available since v1.0.1