Skip to content

Commit 333dc46

Browse files
Mzhiingerichmao
andauthored
docs: explain why maxCharsInObjectName is 63 characters (argoproj#9915)
Signed-off-by: Mzhiing <[email protected]> Co-authored-by: erichmao <[email protected]>
1 parent 30a6d5e commit 333dc46

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

workflow/validate/validate.go

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,9 @@ const (
8383
anyItemMagicValue = "item.*"
8484
anyWorkflowOutputParameterMagicValue = "workflow.outputs.parameters.*"
8585
anyWorkflowOutputArtifactMagicValue = "workflow.outputs.artifacts.*"
86-
maxCharsInObjectName = 63
86+
// The maximum length of maxCharsInObjectName is 63 characters because of the limitation of Kubernetes label
87+
// For details, please refer to: https://stackoverflow.com/questions/50412837/kubernetes-label-name-63-character-limit
88+
maxCharsInObjectName = 63
8789
// CronWorkflows have fewer max chars allowed in their name because when workflows are created from them, they
8890
// are appended with the unix timestamp (`-1615836720`). This lower character allowance allows for that timestamp
8991
// to still fit within the 63 character maximum.

0 commit comments

Comments
 (0)