[BUG] cluster naming cannot start with a number

apecloud / kubeblocks

KubeBlocks is an open-source control plane software that runs and manages databases, message queues and other stateful applications on K8s.

https://kubeblocks.io

GNU Affero General Public License v3.0

2.06k stars 167 forks source link

[BUG] cluster naming cannot start with a number #6312

Open wuxxfree opened 8 months ago

wuxxfree commented 8 months ago

When I create a cluster named after a number, rsm (ReplicatedStateMachine) cannot be fully tuned: c61d8b41abd1c28fe8155966cb49e7f

wuxxfree commented 8 months ago

Kubernetes: v1.23.4 KubeBlocks: 0.7.0 kbcli: 0.7.0

github-actions[bot] commented 7 months ago

This issue has been marked as stale because it has been open for 30 days with no activity

dingshun-cmss commented 5 months ago

To resolve this issue, it appears we may need to impose naming constraints on the Cluster object to ensure the successful generation of Service names. Alternatively, we could introduce a prefix for the names of the generated Services. However, the latter approach would extend the length of all the service names originating from the Clusters, potentially surpassing the maximum character limit for K8S objects.