a9ff4fed4a
* adding vnet changes * format error * change * add exec * added sp instructions * adding output * adding link * name change * node selector change * plz be the last change * vnet changes * vnet changes, took out sp variables * Adding more changes * aci subnet * added master uri * fixed stuff * adding master uri again * add /
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.