Priority

(Medium) I'm annoyed but I'll live

User Story

As a user I want to use greenhousectl validate the clusterName so that, I do not run into problems with bootstrapping a cluster with invalid name

Description

With #611 the Cluster webhook enforces a max length of 40 character for the name of the cluster and ensures that no -- may be included in the cluster name.

The greenhousectl should perform these validations as well, since the secret it will create is not validated. This means an invalid cluster name will result in the bootstrap controller failing to create the cluster.

The same validation should be added for the name of the kubeconfig secret, so that it ensures that a Cluster onboarded via greenhousectl or manually via secret has a valid name and can actually be created.

Acceptance Criteria

• Validation of the 40 Char and no -- in the ClusterName
  • greenhousectl cluster boostrap enforces this
  • secret webhook for type greenhouse.sap/kubeconfig enforces this

Reference Issues

No response