Skip to content

Latest commit

 

History

History
117 lines (52 loc) · 3.56 KB

setting-your-module-to-the-unmanaged-and-managed-state-c071680.md

File metadata and controls

117 lines (52 loc) · 3.56 KB

Setting Your Module to the Unmanaged and Managed State

In some cases, for example, for testing, you may need to modify your module beyond what is supported by its configuration. By default, when a module is in the managed state, Kyma Control Plane governs its Kubernetes resources, reverting any manual changes during the next reconciliation loop. To modify Kubernetes objects directly without them being reverted, you must set the module to the unmanaged state. In this state, reconciliation is disabled, ensuring your manual changes are preserved.

Use Kyma dashboard to set your module to the unmanaged state.

Context

Follow this procedure to easily set your module to the unmanaged state from the dashboard's Cluster Details view.

Caution:

Setting your module to the unmanaged state may lead to instability and data loss within your cluster. It may also be impossible to revert the changes. In addition, we don't guarantee any service level agreement (SLA) or provide updates and maintenance for the module.

Procedure

  1. Go to Kyma dashboard. The URL is in the Overview section of your subaccount.

  2. Choose Modify Modules, and go to the Edit tab.

  3. In the Form view, uncheck the Managed checkbox under your module.

  4. Save the changes.

In the View tab, you see your module in the Unmanaged state.

To bring your module back to the managed state, go to the Edit tab, check the Managed box under your module, and save changes.

Caution:

Depending on the introduced changes, bringing back the module to the managed state might not be possible.

Use Kyma CLI to set your module to the unmanaged state.

You have Kyma CLI installed. For more information, see Install Kyma CLI.

Context

Set your module to the unmanaged state with a simple Kyma CLI command.

Caution:

Setting your module to the unmanaged state may lead to instability and data loss within your cluster. It may also be impossible to revert the changes. In addition, we don't guarantee any service level agreement (SLA) or provide updates and maintenance for the module.

Procedure

To set a module to the unmanaged state, use the following command:

kyma alpha module unmanage {MODULE-NAME}

Your module is now in the unmanaged state.

To bring your module back to the managed state, use the following command:

kyma alpha module manage {MODULE-NAME}

Even if the module is already in the managed state, you can change its policy by adding the optional flag --policy {POLICY-NAME}. The default policy is CreateAndDelete.

Caution:

Depending on the introduced changes, bringing back the module to the managed state might not be possible.