The module lifecycle stage: Preview
If, during the switching process, the image of a module did not reload and the module did not reinstall, use the instructions to resolve the issue.
Switching to the Direct Mode
To switch an already running cluster to Direct mode, follow these steps:
When changing the registry mode or registry parameters, Deckhouse will be restarted.
-
Before switching, perform the migration to use the
registrymodule. -
Make sure the
registrymodule is enabled and running. To do this, execute the following command:d8 k get module registry -o wideExample output:
NAME WEIGHT ... PHASE ENABLED DISABLED MESSAGE READY registry 38 ... Ready True True -
Make sure all master nodes are in the
Readystate and do not have theSchedulingDisabledstatus, using the following command:d8 k get nodesExample output:
NAME STATUS ROLES ... master-0 Ready control-plane,master ... master-1 Ready control-plane,master ... master-2 Ready control-plane,master ...Example of output when the master node (
master-2in the example) is in theSchedulingDisabledstatus:NAME STATUS ROLES ... master-0 Ready control-plane,master ... master-1 Ready control-plane,master ... master-2 Ready,SchedulingDisabled control-plane,master ... -
Ensure the Deckhouse job queue is empty and contains no errors:
d8 system queue listExample output:
Summary: - 'main' queue: empty. - 107 other queues (0 active, 107 empty): 0 tasks. - no tasks to handle. -
Set the
Directmode configuration in the ModuleConfigdeckhouse. If you’re using a registry other thanregistry.deckhouse.io, refer to thedeckhousemodule documentation for correct configuration.Configuration example:
apiVersion: deckhouse.io/v1alpha1 kind: ModuleConfig metadata: name: deckhouse spec: version: 1 enabled: true settings: registry: mode: Direct direct: imagesRepo: registry.deckhouse.io/deckhouse/ee scheme: HTTPS license: <LICENSE_KEY> # Replace with your license key -
Check the registry switch status in the
registry-statesecret using this guide.Example output:
conditions: # ... - lastTransitionTime: "..." message: "" reason: "" status: "True" type: Ready hash: .. mode: Direct target_mode: Direct
Switching to the Unmanaged Mode
To switch an already running cluster to Unmanaged mode, follow these steps:
Changing the registry mode or its parameters will cause Deckhouse to restart.
-
Before switching, perform the migration to use the
registrymodule. -
Make sure the
registrymodule is enabled and running. To do this, execute the following command:d8 k get module registry -o wideExample output:
NAME WEIGHT ... PHASE ENABLED DISABLED MESSAGE READY registry 38 ... Ready True True -
Ensure the Deckhouse job queue is empty and contains no errors:
d8 system queue listExample output:
Summary: - 'main' queue: empty. - 107 other queues (0 active, 107 empty): 0 tasks. - no tasks to handle. -
Set the
Unmanagedmode configuration in the ModuleConfigdeckhouse. If you’re using a registry other thanregistry.deckhouse.io, refer to thedeckhousemodule documentation for correct configuration.Configuration example:
apiVersion: deckhouse.io/v1alpha1 kind: ModuleConfig metadata: name: deckhouse spec: version: 1 enabled: true settings: registry: mode: Unmanaged unmanaged: imagesRepo: registry.deckhouse.io/deckhouse/ee scheme: HTTPS license: <LICENSE_KEY> # Replace with your license key -
Check the registry switch status in the
registry-statesecret using this guide.Example output:
conditions: # ... - lastTransitionTime: "..." message: "" reason: "" status: "True" type: Ready hash: .. mode: Unmanaged target_mode: Unmanaged -
If you need to switch back to the old registry management method, refer to the instruction.
This is a deprecated format for registry management.