invalid service/deployment name passes kubeval about kubeval

[garethr]

Could you include a failing definition file? I'll take a look at where this is failing.

kubeval relies exclusively on the Kubernetes OpenAPI descriptions, which might mean this information is missing from those. Or it could be a different local bug.

[DamonStamper]

Sure. Below is a failing definition file. "CapitalName" and "underscore_name" are the source of the errors in this example.

apiVersion: v1
kind: Service
metadata:
  name: CapitalName
  labels:
    app: CapitalName
spec:
  selector:
    app: Invalid_App
  type: LoadBalancer
---
apiVersion: v1
kind: Service
metadata:
  name: underscore_name
  labels:
    app: underscore_name
spec:
  selector:
    app: underscore_name
  type: LoadBalancer
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: 
  labels:
    app: Invalid_App
spec:
  template:
    metadata:
      labels:
        app: Invalid_App
    spec:
      containers:
      - name: CapitalName
        image: CapitalImage
        imagePullPolicy: Always
      - name: underscore_name
        image: underscore_image
        imagePullPolicy: Always