Currently if you have an autonode cluster and from that guest cluster, you attempt to change some fields in the OpenShiftEC2NodeClass such as the spec.tags field, the karpenter-operator will remove those changes.

e.g.

apiVersion: karpenter.hypershift.openshift.io/v1beta1
  kind: OpenshiftEC2NodeClass
  metadata:
    name: default
  spec:
    securityGroupSelectorTerms:
    - tags:
        karpenter.sh/discovery: macao-karpenter-420-k6plx
    subnetSelectorTerms:
    - tags:
        karpenter.sh/discovery: macao-karpenter-420-k6plx
    tags:
      Name: some-node-name

the karpenter-operator will clobber those changes, even though the point of the oec2nodeclass is that all changes should be reflected in the ec2nodeclass, since that subset of fields are to be owned by the cluster-admin, and not by Red Hat/managed services.