Mandatory.yaml fails because of missing Kind statement

[Xycer]

Is this a request for help?: No

What keywords did you search in NGINX Ingress controller issues before filing this one?: all issues both open and closed having to do with mandatory.yaml

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

NGINX Ingress controller version: 0.21.0

Kubernetes version (use kubectl version): v1.12.3

Environment:

• Cloud provider or hardware configuration: Docker-for-Desktop (Docker for Mac)
• OS (e.g. from /etc/os-release): MacOS High Sierra
• Kernel (e.g. uname -a): Darwin
• Install tools: following instructions found at: https://kubernetes.github.io/ingress-nginx/deploy/

What happened: attempted to run command: kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml
and got the response:

error: error validating "https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml": error validating data: kind not set; if you choose to ignore these errors, turn validation off with --validate=false

What you expected to happen: Expected to see:

namespace/ingress-nginx created configmap/nginx-configuration created configmap/tcp-services created configmap/udp-services created serviceaccount/nginx-ingress-serviceaccount created clusterrole.rbac.authorization.k8s.io/nginx-ingress-clusterrole created role.rbac.authorization.k8s.io/nginx-ingress-role created rolebinding.rbac.authorization.k8s.io/nginx-ingress-role-nisa-binding created clusterrolebinding.rbac.authorization.k8s.io/nginx-ingress-clusterrole-nisa-binding created deployment.extensions/nginx-ingress-controller created

How to reproduce it (as minimally and precisely as possible): Run the command

Anything else we need to know: I've updated the mandatory.yaml file with the required field in the commit: https://github.com/kubernetes/ingress-nginx/commit/6f160d9066179ab44b2814c881292111efe191e6 and will be creating a pull request for it.

[aledbf]

Closing. Fixed in master #3516. Apologies for the issue