Define validation strategy for provider config

[rsdcastro]

From @rsdcastro on February 22, 2018 21:13

As per comment in #405, "validation is another concern and independent of specifying the cloud provider in the top level object or in the provider specific config. We can't bake provider specific validation logic into the API. That needs to be pluggable somehow through a webhook, admission controller, or some other mechanism. But it's a much larger discussion."

This issue tracks methods we'll allow for validation, including recommendations and examples.

cc @karan

Copied from original issue: kubernetes-retired/kube-deploy#623

[rsdcastro]

From @roberthbailey on March 7, 2018 18:53

This seems to depend on kubernetes-retired/kube-deploy#504

[roberthbailey]

Validation is provider specific, so this is out of scope for this repository.

/close

[k8s-ci-robot]

@roberthbailey: Closing this issue.

In response to this:

Validation is provider specific, so this is out of scope for this repository.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.