https://docs.google.com/document/d/1ID_IhXPpYY4K3G_wa1MYJxOb3yz5FYoOj3ONSkEDsZs/edit?tab=t.0#heading=h.yvv1wy2g0utk

Goal

• Define and implement the mechanism for disabling Karpenter/AutoNode support in ROSA HCP clusters.

Why is this important?

• This will allows users to opt out of AutoNode as a day 2 operation, without any clusterbreaking changes between enablement and disablement.

Scenarios

• A cluster admin decides to revert to the standard compute management, and wants to disable AutoNode without any disruption to the cluster or its existing workloads.
  • karpenter components must be removed from control-plane
  • existing karpenter nodes + nodeclaims must be removed from worker plane
  • karpenter crds (ec2nodeclass, openshiftec2nodeclass, nodepool, etc.) must be uninstalled from worker place
  • existing HCP functionality must stay intact after disablement

Acceptance Criteria

• Dev - Has a valid enhancement if necessary
• CI -

• • test to make sure that autonode can be disabled, and removes the karpenter-provisioned compute nodes, along with the HCP karpenter components + CRDs (karpenter, karpenter-operator deployments, etc.)
• ...