Prepare stable applications for Kubernetes v1.16 compatability

[Mansalu]

I am vetting each application in our stable catalog for compatibility with the new Kubernetes v1.16 requirements. Additionally, I am checking backwards compatibility with the older versions of Kubernetes, to be sure that these applications do not break on older clusters.

The primary change we are currently aware of is that Deployment specs must now implement labelSelection.

Example:

  selector:
    matchLabels:
      app: {{ template "faucet.name" . }}
      instance: {{ .Values.Instance }}

[Mansalu]

Faucet has been updated and checked for compatibility on v1.14 clusters.

[Mansalu]

Globus v4 Connect already implements deployment selection. This has been tested for compatibility with older clusters already.

[Mansalu]

Grafana is already compatible.

[Mansalu]

Gridftp has been updated. It seems to be compatable with v1.14 clusters.

[Mansalu]

HTCondor already implements deployment selection. This has been tested for compatibility with older clusters already.

[Mansalu]

nginx already implements deployment selection. This has been tested for compatibility with older clusters already.

[Mansalu]

osg-frontier-squid already implements deployment selection. This has been tested for compatibility with older clusters already.

[Mansalu]

perfsonar-testpoint has been updated and checked for compatibility on v1.14 clusters.

[Mansalu]

stashcache already implements deployment selection. This has been tested for compatibility with older clusters already.

[Mansalu]

xcache already implements deployment selection. This has been tested for compatibility with older clusters already.