Using UpperCamelCase for Kubernetes resources

[jacobtomlinson]

The Kubernetes documentation style-guide encourages the use of UpperCamelCase (also known as PascalCase) when referring to Kubernetes resources.

It's a little nitpicky but I think it would be good to be consistent with this in our own documentation. For example we regularly writer pods when we should write Pods.

Examples in our docs

deployment/source/platforms/kubeflow.md

Line 132 in 104ebd3

Now you can create `DaskCluster` resources in Kubernetes that will launch all the necessary pods and services for our cluster to work. This can be done in YAML via the Kubernetes API or using the Python API from a notebook session as shown in this section.

deployment/source/tools/kubernetes/dask-helm-chart.md

Line 47 in d1264c7

Note that all scheduler, worker and jupyter pods are required to use the same image.

deployment/source/guides/index.md

Line 57 in d1264c7

Colocate worker pods on Kubernetes

Guidance Examples

Guidance form the style-guide

Do	Don't
The HorizontalPodAutoscaler resource is responsible for ...	The Horizontal pod autoscaler is responsible for ...
A PodList object is a list of pods.	A Pod List object is a list of pods.
The Volume object contains a hostPath field.	The volume object contains a hostPath field.
Every ConfigMap object is part of a namespace.	Every configMap object is part of a namespace.
For managing confidential data, consider using the Secret API.	For managing confidential data, consider using the secret API.

[ncclementi]

I was not aware of this, thanks for bring it up.

Whenever we tackle this, we should also add a reference to this issue in the contributing guidelines.

[ncclementi]

Do things like configMap in yaml files need to be changed for ConfigMap?

[ncclementi]

I'll re-open this, because I'm not sure the fixes I made are indication of completion.

[jacobtomlinson]

I think if we update the README with this style guide info and progressively fix things over time then we could probably close this.