Applying cockroachdb-statefulset-secure.yaml Throws an Error

[russoj88]

https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml does not seem to be valid YAML, at least not for Kubernetes.

Please describe the issue you observed, and any steps we can take to reproduce it: Following the guide to deploy CRDB on kubernetes is not working.

I'm trying to create a CRDB cluster on Kubernetes (Digital Ocean). When I run kubectl apply -f cockroachdb-statefulset-secure.yaml as instructed in the guide, I'm getting this error:

➜  kubernetes-cluster git:(master) ✗ kubectl apply -f cockroachdb-statefulset-secure.yaml
serviceaccount/cockroachdb created
role.rbac.authorization.k8s.io/cockroachdb created
clusterrole.rbac.authorization.k8s.io/cockroachdb created
rolebinding.rbac.authorization.k8s.io/cockroachdb created
clusterrolebinding.rbac.authorization.k8s.io/cockroachdb created
service/cockroachdb-public created
service/cockroachdb created
poddisruptionbudget.policy/cockroachdb-budget created
error: error parsing cockroachdb-statefulset-secure.yaml: error converting YAML to JSON: yaml: line 63: did not find expected key
➜  kubernetes-cluster git:(master) ✗ 

The cluster is v1.16.8-do.0. kubectl is v1.18.3.

https://cockroachdb.slack.com/archives/CRK1K8FFB/p1591582745030800

kubeval also shows the same error.

[blathers-crl[bot]]

Hello, I am Blathers. I am here to help you get the issue triaged.

It looks like you have not filled out the issue in the format of any of our templates. To best assist you, we advise you to use one of these templates.

I have CC'd a few people who may be able to assist you:

• @joshimhoff (found keywords: kubernetes,cloud)

If we have not gotten back to your issue within a few business days, you can try the following:

• Join our community slack channel and ask on #cockroachdb.
• Try find someone from here if you know they worked closely on the area and CC them.

_{:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.}

[russoj88]

Closing... The error was reporting line 63. That was not line 63 in the file, but line 63 in the last section.