Deployment files are incompatible with recent Kubernetes (1.16+)

[s1mn]

As outlined in a blog post, deprecated API versions were removed in Kubernetes 1.16. For instance extensions/v1beta1, apps/v1beta1 and apps/v1beta2 are gone.

As a result, mico's Kubernetes YAML files can no longer be deployed on Kubernetes ≥ 1.16 without modification.

In some files, the new API names are noted as comments, in others they aren't. For instance:

mico/install/kubernetes/kube-state-metrics/kube-state-metrics-deployment.yaml

Lines 1 to 3 in 637af25

	apiVersion: apps/v1beta2
	# Kubernetes versions after 1.9.0 should use apps/v1
	# Kubernetes versions before 1.8.0 should use apps/v1beta1 or extensions/v1beta1

mico/install/kubernetes/monitoring/node-directory-size-metrics.yaml

Line 2 in 637af25

apiVersion: extensions/v1beta1

Click to expand the list of files that would need to be changed

install/kubernetes/kube-state-metrics/kube-state-metrics-deployment.yaml
install/kubernetes/monitoring/alertmanager-dep.yaml
install/kubernetes/monitoring/node-directory-size-metrics.yaml
install/kubernetes/monitoring/prometheus-dep.yaml
install/kubernetes/monitoring/prometheus-node-exporter.yaml
install/kubernetes/neo4j.yaml
install/kubernetes/openfaas/faas-idler-dep.yaml
install/kubernetes/openfaas/gateway-dep.yaml
install/kubernetes/redis.yaml

Changing the files to work out-of-the-box on kube ≥ 1.16 would be break compatibility with old kubernetes versions. I can prepare a pull request, but question to the maintainers is:

Would you accept a contribution that fixes this but breaks that compatibility by updating the referenced API versions?