Context
Some secrets are generated with a name, ie: user-data-nodepool-xxxx, token-nodepool-xxxx etc
They have an annotation hypershift.openshift.io/nodePool
However there are no labels, no context etc
I understand that using annotations has probably been driven by the characters limit, however we could at least add some
Proposal
The idea would be to add contextual labels, so that troubleshooting can be simplified but also building controller around hypershift
In Argocd they have the argocd.argoproj.io/secret-type: repository|cluster
An idea would be to add label:
hypershift.openshift.io/secret-type: nodepool-user-data|nodepool-token|admin-kubeconfig
If some of you have other contextual labels ideas don't hesitate to propose them
Context
Some secrets are generated with a name, ie: user-data-nodepool-xxxx, token-nodepool-xxxx etc
They have an annotation hypershift.openshift.io/nodePool
However there are no labels, no context etc
I understand that using annotations has probably been driven by the characters limit, however we could at least add some
Proposal
The idea would be to add contextual labels, so that troubleshooting can be simplified but also building controller around hypershift
In Argocd they have the
argocd.argoproj.io/secret-type: repository|clusterAn idea would be to add label:
hypershift.openshift.io/secret-type: nodepool-user-data|nodepool-token|admin-kubeconfigIf some of you have other contextual labels ideas don't hesitate to propose them