fluid icon indicating copy to clipboard operation
fluid copied to clipboard
verified publisher icon fluid-cloudnative

Fluid can not start runtime if it don't match k8s naming style

Open Nizifan opened this issue 3 years ago • 3 comments

Describe the bug User create alluxio runtime starts with number, the runtime and dataset is created but corresponding config-map is rejected by k8s. Thus Alluxio can not start as it can not read reserved ports from config map.

2022-02-23T18:21:01.053+0800 ERROR alluxioctl.AlluxioRuntime base/setup.go:41 SetupMaster {"alluxioruntime": "ai/220126-bili-videos", "engine": "alluxio", "id": "ai-220126-bili-videos", "error": "can't get enough available ports, only 7 ports are available"

k get alluxioruntime NAME MASTER PHASE WORKER PHASE FUSE PHASE AGE 220126-bili-videos 3h53m

k get cm NAME DATA AGE anime-test-alluxio-values 1 65d

Additional Information

I suggest Alluxio resource take the same naming rule of k8s style resource, this can return user with error when Alluxio runtime emitted to k8s

Nizifan avatar Feb 23 '22 11:02 Nizifan

https://book.kubebuilder.io/reference/markers/crd-validation.html

image

cheyang avatar Feb 23 '22 11:02 cheyang

https://kubernetes.io/zh/docs/concepts/overview/working-with-objects/names/

RFC 1035

Nizifan avatar Feb 23 '22 11:02 Nizifan

I will fix this issue.

Nizifan avatar Feb 23 '22 11:02 Nizifan