propose_cluster_action
Propose a cluster lifecycle action (cordon, add-on, label updates) without applying it. Server-side dry-run validates the request, then stores it pending for human approval.
Instructions
Propose an OCM cluster lifecycle action. Does NOT apply anything.
Args: cluster: target managed cluster name. action: one of 'cordon' (taint out of scheduling), 'uncordon' (undo cordon), 'set_label' (params: {"key","value"}; empty value removes the label), 'accept' (set hubAcceptsClient=true and approve pending join CSRs), 'enable_addon' (params: {"addon","install_namespace"?}; create a ManagedClusterAddOn), 'disable_addon' (params: {"addon"}; delete it). summary: one or two sentences the human approver will read. params_json: JSON object of action parameters (set_label and the addon actions need it; cordon/uncordon/accept do not).
The action is validated with a server-side dry-run, then stored pending. The
human operator must run ocm-mcp approve <id> to mint the approval token.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| cluster | Yes | ||
| summary | Yes | ||
| params_json | No | {} |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |