This ensures that we can catch certain types of errors from providers and handle accordingly in the core. There is still more to do here to improve that but this resolves an immediate need to know why a Delete failed. vic provider was not updated since I could not figure out where to get this information.
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.