713fe23d03
This eliminates all the one-off calls to for specific things like `Capacity` and other things. Instead we configure defaults in the CLI and then pass the full node object to the provider to change as needed. This makes sure the provider can change whatever they need to without having to add tons of methods to the provider interface.
Follow these steps to be accepted as a provider within the Virtual Kubelet repo.
- Replicate the life-cycle of a pod for example creation and deletion of a pod and how that maps to your service.
- Create a new provider folder with a descriptive name and the necessary code.
- When committing your code add a README.md, helm chart, dockerfile and specify a maintainer of the provider.
- Within the PR itself add a justification for why the provider should be accepted, as well as customer use cases if applicable.
Some providers are translations of Virtual Kubelet to allow others to adapt their service or applications that are written in other languages.