Files
virtual-kubelet/providers
Brian Goff a54753cb82 Move around some packages (#658)
* Move tracing exporter registration

This doesn't belong in the library and should be configured by the
consumer of the opencensus package.

* Rename `vkublet` package to `node`

`vkubelet` does not convey any information to the consumers of the
package.
Really it would be nice to move this package to the root of the repo,
but then you wind up with... interesting... import semantics due to the
repo name... and after thinking about it some, a subpackage is really
not so bad as long as it has a name that convey's some information.

`node` was chosen since this package deals with all the semantics of
operating a node in Kubernetes.
2019-06-12 13:11:49 +01:00
..
2019-06-12 13:11:49 +01:00
2019-06-12 13:11:49 +01:00
2019-06-12 13:11:49 +01:00
2019-06-12 13:11:49 +01:00
2019-06-12 13:11:49 +01:00
2019-06-12 13:11:49 +01:00
2019-06-12 13:11:49 +01:00
2019-06-12 13:11:49 +01:00
2018-01-22 10:57:23 -08:00
2017-12-05 17:53:58 -06:00

Follow these steps to be accepted as a provider within the Virtual Kubelet repo.

  1. Replicate the life-cycle of a pod for example creation and deletion of a pod and how that maps to your service.
  2. Create a new provider folder with a descriptive name and the necessary code.
  3. When committing your code add a README.md, helm chart, dockerfile and specify a maintainer of the provider.
  4. 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.