Currently there is a single shared hypershift "token" for all Karpenter managed nodes. Tokens are able to generate ignition payloads for OpenShift Nodes. This means that all karpenter managed nodes will follow the same openshift node version, which is undesirable if users want separate nodeclasses to have different node versions, or if they want to upgrade nodes separately from each other.

We should allow each openshiftec2nodeclass in the guest cluster to be linked with its own "Token" and hence it's own ignition configuration. See this thread for the discussion of this: https://redhat-internal.slack.com/archives/C088H9VV9UM/p1765410283335709?thread_ts=1765397476.726629&cid=C088H9VV9UM 

Note that this story does not involve actually allowing the user to upgrade the data plane yet. That will be covered in a separate story AUTOSCALE-494. We should design this story with AUTOSCALE-494 and the overall epic in mind.