In case an SSH public key contains special characters inside a comment, it can be not applied properly via Cloud-init.
This happens because we use a comment as a key name, which is fine in a vast majority of cases when it is something like [email protected], but leads to problems when this is Support Team Key or something more complex.
Technically, we can pass special characters to the name of a tagNode, but it will lead to various troubles in CLI later. I am suggesting generating names for such keys as we do for keys without comments instead of using a comment as a name. This will protect from possible problems later.