How to fix Friendly Name Duplicate in Kubernetes

kubectl get <resource-type> -A | grep <name>
kubectl get <resource-type> --all-namespaces

# Find exact duplicates:
kubectl get <resource-type> -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | sort | uniq -d

# Describe both resources:
kubectl describe <resource-type> <name> -n <ns1>
kubectl describe <resource-type> <name> -n <ns2>

kubectl patch <resource> <old-name> -p '{"metadata":{"name":"<new-name>"}}'
# Or:
kubectl delete <resource> <old-name>
kubectl create -f updated-manifest.yaml  # With new name

kubectl delete <resource> <old-name> -n <namespace>

# Move resource to different namespace:
kubectl create ns team-a
kubectl apply -f resource.yaml -n team-a

# Cluster-scoped (names unique across entire cluster):
kubectl api-resources | grep "<none>"  # <none> = cluster scope

# Namespace-scoped (names unique per namespace):
kubectl api-resources | grep "true"  # true = namespaced

# For custom resources:
kubectl get crd <name>.yaml -o jsonpath='{.spec.scope}'

# Two resources can have same name if in different namespaces (if namespaced)
kubectl get pods default/myapp  # Namespace 1
kubectl get pods other/myapp    # Namespace 2 (OK)

apiVersion: myapi.example.com/v1
kind: MyResource
metadata:
  name: shared-name  # Can be duplicated across namespaces
  namespace: team-a
  labels:
    team: team-a
    environment: prod
  annotations:
    owner: [email protected]
spec:
  # ...

kubectl get <resource> -l team=team-a
kubectl get <resource> -l environment=prod

# Convention: <team>-<service>-<environment>
app-api-prod
app-api-staging
app-worker-prod

# Or: <project>-<component>-<version>
myapp-web-v1
myapp-web-v2
myapp-db-v1

# Enforce via kube-linter or similar:
kube-lint --allowed-registry my-registry  # Custom rules

# Or via validation in CRD:
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: myresources.example.com
spec:
  names:
    kind: MyResource
  validation:
    openAPIV3Schema:
      properties:
        metadata:
          properties:
            name:
              pattern: "^[a-z0-9]([-a-z0-9]*[a-z0-9])$"  # Regex validation

# Get CRD definition:
kubectl get crd <resource>.example.com -o yaml

# Look for validation rules:
validation:
  openAPIV3Schema:
    properties:
      spec:
        properties:
          friendlyName:
            type: string
            description: "Must be unique"

# If validation exists but isn't working, check controller logs:
kubectl logs -n <controller-ns> deployment/<controller> | grep -i "friendly\|unique"

# Try creating duplicate:
kubectl apply -f duplicate.yaml
# Should fail with error about duplicate name

# Check what the error message says:
kubectl apply -f duplicate.yaml 2>&1 | head -20

# If no error, enforcement might be missing
# Add validation to CRD:
kubectl patch crd <resource> --type merge -p \
  '{"spec":{"validation":{"openAPIV3Schema":{"properties":{"metadata":{"properties":{"name":{"pattern\":"^unique-pattern$"}}}}}}}}'

# Document in ConfigMap or wiki:
kubectl create configmap naming-standards \
  --from-literal=convention="<team>-<service>-<env>" \
  --from-literal=forbidden-prefixes="system-,kube-" \
  -n kube-system

# Or in comments in manifests:
# NAMING: Resources must follow pattern: {team}-{service}-{env}
# EXAMPLE: platform-api-prod, platform-worker-staging