7391e44b48
CHANGES: - Added an appVersion and icon to helm Chart.yaml - Refactored to use `required` in chart manifests rather than outputting an error message in notes - Namespaced `name` and `fullname` template partials to `vk` - Enabled rbac apiVersion configuration - Removed role-binding and service-account suffixes from resource names - Fixed bug where virtual-kubelet service account would not be bound to cluster role if chart was installed outside the default namespace - Removed hardcoded `azure` provider BREAKING CHANGES: - Virtual-Kubelet specific values previously nested under `env` are now declared at the top level of the values file. - Azure provider configuration values previously nested under `env` are now at `providers.azure`
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.