[feat][RayCluster] shorten HeadlessServiceSuffix to have more space for CR names #3101
Conversation
|
can you split this into two PRs, one for headless service and one for RayCluster? |
rueian
force-pushed
the
less-suffix-for-more-resource-name
branch
from
cb99863 to
d67af8c
Compare
rueian
changed the title
rueian
changed the title
…or CR names Signed-off-by: Rueian <[email protected]>
rueian
force-pushed
the
less-suffix-for-more-resource-name
branch
from
d67af8c to
536d17a
Compare
Sure, another PR is here: #3102 |
|
Hi @andrewsykim, We'd like to add a length validation to RayCluster names in the next release to provide non-trimmed service names for a better user experience. But the current headless service suffix for the TPU webhook, Please let me know if you have any concerns about this. Thanks! |
I'll need to change the logic of the webhook here before this change so that |
|
GoogleCloudPlatform/ai-on-gke#1003 is merged. |
3 participants
Why are these changes needed?
Currently, KubeRay adds different suffixes to make different services for a RayCluster. It will also trim these service names if they are too long to fit the 63-character limitation by k8s. However, the silent cut is not user-friendly as users can't easily know the resulting service names beforehand.
As a part of #3076: we are going to add a length validation to RayCluster names in v1.4 to make sure the silent cut does not take place while keeping sufficient room for the names specified by users, this PR shortens the
-headless-worker-svcsuffix to just-headless, saving 11 characters for users to use (63-len("-serve-svc") = 53 characters).Related issue number
#3076
Checks