config_meta validation

[joel-bluedata]

This needs to be a "dictionary" (object with arbitrary property names) of string values.

In K8s 1.11 and later, we should be able to do this through schema validation i.e.

config_meta:
  type: object
  additionalProperties:
    type: string

However for supporting earlier K8s versions I guess we need to do it in dynamic validation instead. Or we could move to modeling it as an array of sub-objects with explicit key/value properties.

[joel-bluedata]

For reference, the discussion of the relevant issue (with the commit fix noted near the end): kubernetes/kubernetes#59485

K8s 1.11 is now available in GKE deployments if you request it when doing a create, e.g. with --cluster-version=1.11.2-gke.15. It looks like 1.11 is also available in AKS, IBM Cloud, and Digital Ocean.

EKS is still on 1.10 (according to their FAQ). Suuurrrrely they will make 1.11 available soonish?

I would like to just say that our minimum requirement is K8s 1.11, and then not have to worry about dynamic validation for this sort of thing. But the 0.2.0 release is probably too early to do that.

[joel-bluedata]

EKS now has 1.11 as well.

[joel-bluedata]

Our minimum requirement is now 1.12, so we can move on this now.