Help Center/ Cloud Container Engine/ FAQs/ Permissions/ How Do I Restore a Cluster Agency That Was Deleted by Mistake?
Updated on 2026-02-02 GMT+08:00
View PDF
Share

How Do I Restore a Cluster Agency That Was Deleted by Mistake?

Before restoring an agency, keep the following in mind:

  • CCE uses a credential cache framework. Newly created agencies do not take effect immediately.
  • Allow sufficient time for the configuration to take effect as described in each scenario, or restart the relevant components to accelerate the process.

Scenario 1: CCENodeAgency Was Deleted by Mistake

CCENodeAgency is required for normal cluster node operations. If it was deleted by mistake, restore it as follows:

  1. Log in to the CCE console. In the navigation pane, choose Clusters.
  2. CCE automatically detects that the agency is missing and displays an Authorization dialog box.

  3. In the dialog box displayed, click OK. On the drawer page that appears on the right, click OK again. CCENodeAgency will be created automatically.

Scenario 2: An Add-on Agency Was Deleted by Mistake

The restoration method depends on how an add-on agency was created (automatically created or customized). First, confirm which type of agency your add-on uses.

  • Case 1: The Add-on Uses an Automatically Created Agency.

    If the add-on agency was created automatically, restore it as follows:

    1. Log in to the CCE console and click the cluster name to access the cluster console.
    2. In the navigation pane, choose Add-ons. In the right pane, locate the add-on and click Edit.

    3. In the window that slides out from the right, locate the Agency Settings area, select Create automatically, and click OK. This recreates the default agency for the add-on.

    4. After completing the above steps, choose one of the following methods to make the configuration take effect:
      • (Recommended) Quick validation: Wait about half an hour and manually restart the add-on pods.
      • Automatic: If you do not restart the pods, the change takes effect in approximately 3 hours.
  • Case 2: The Add-on Uses a Custom Agency

    If the add-on uses a custom agency that you manually created in IAM, restore it as follows:

    1. Log in to the IAM console.
    2. Manually create an agency with the same name as the original one and assign the correct permission policies.
    3. Wait for the configuration to take effect.
      • (Recommended) Quick validation: Wait about half an hour and manually restart the add-on pods.
      • Automatic: If you do not restart the pods, the change takes effect in approximately 3 hours.
Parent Topic: Permissions