fix(validators): reject dots in helm release names

Helm itself permits dots in release names but generated resource
names like `<release>-<chart>-<hash>` must be valid DNS-1123
labels (no dots). A dotted release like `my.app` passes Helm's
validation, then K8s rejects the resource apply server-side
with an opaque 422.

Switch validateHelmReleaseName to delegate to validateRFC1123Label
so the dot is caught with clear inline feedback before submit.

Cursor bugbot finding (validators.ts:126).

Author: eliran-mic

packages/k8s-ui/src/utils/validators.test.ts

@@ -135,6 +135,14 @@ describe('validateHelmReleaseName', () => {
     if (r.valid) throw new Error('expected invalid')
     expect(r.error.endsWith('.')).toBe(false)
   })
+
+  it('rejects dotted names (generated resource names must be DNS-1123 labels)', () => {
+    // Helm itself permits dots, but generated resource names like
+    // `<release>-<chart>-<hash>` must be valid labels. Catch the dot
+    // up front instead of letting K8s reject the apply server-side.
+    expect(validateHelmReleaseName('my.app').valid).toBe(false)
+    expect(validateHelmReleaseName('foo.bar.baz').valid).toBe(false)
+  })
 })
 
 describe('validatePort', () => {

packages/k8s-ui/src/utils/validators.ts

@@ -106,9 +106,17 @@ export function validateRFC1123Subdomain(input: string): ValidationResult {
 }
 
 /**
- * Validates a Helm release name. Same shape as an RFC 1123 subdomain
- * but capped at 53 chars (Helm's hard limit; longer names produce
- * resources that exceed K8s' 63-char label limit).
+ * Validates a Helm release name. Same shape as an RFC 1123 label
+ * (no dots) capped at 53 chars (Helm's hard limit; longer names
+ * produce resources that exceed K8s' 63-char label limit).
+ *
+ * Why label and not subdomain: Helm itself permits dots in release
+ * names, but most charts compose resource names as
+ * `<release>-<chart>-<hash>` which must be valid DNS-1123 labels.
+ * A dotted release name like `my.app` produces resources whose
+ * names fail K8s label validation server-side. Reject the dot up
+ * front so the user sees a clear inline error instead of a server
+ * 422 after submit.
  */
 export function validateHelmReleaseName(input: string): ValidationResult {
   if (input.length === 0) {
@@ -123,7 +131,7 @@ export function validateHelmReleaseName(input: string): ValidationResult {
       error: `must be at most ${HELM_RELEASE_NAME_MAX} characters (got ${input.length}); Helm caps release names so derived resource names fit under K8s' 63-char limit`,
     }
   }
-  return validateRFC1123Subdomain(input)
+  return validateRFC1123Label(input)
 }
 
 /**