Skip to content
This repository has been archived by the owner on May 22, 2020. It is now read-only.

Define validation strategy for provider config #623

Closed
rsdcastro opened this issue Feb 22, 2018 · 2 comments
Closed

Define validation strategy for provider config #623

rsdcastro opened this issue Feb 22, 2018 · 2 comments

Comments

@rsdcastro
Copy link

rsdcastro commented Feb 22, 2018

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

@rsdcastro rsdcastro added this to the cluster-api-alpha milestone Feb 22, 2018
@roberthbailey
Copy link
Contributor

This seems to depend on #504

@rsdcastro
Copy link
Author

This issue was moved to kubernetes-sigs/cluster-api#44

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants