machine-controller-manager-provider-vsphere

machine-controller-manager-provider-vsphere

Out of tree (gRPC based) implementation for Vsphere as a new provider.

About

• This is a sample repository that provides the blueprint required to implement a new (hyperscale) provider. We call the new provider as Vsphere for our ease.
• Each provider (plugin/actuator/driver) is a gRPC server and implements the services defined at machine-spec.

Fundamental Design Principles:

Following are the basic principles kept in mind while developing the external plugin.

• Communication between external plugin and machine-controller is achieved using gRPC mechanism.
• External plugin behaves as gRPC-server and machine-controller behaves as gRPC client.
• Cloud-provider specific contract should be scoped under ProviderSpec field. ProviderSpec field is expected to be raw-bytes at machine-controller-side. External plugin should have pre-defined typed-apis to parse the ProviderSpec to make necessary CP specific calls.
• External plugins do not need to communicate with kubernetes api-server.
  • Kubeconfig may not be available to external-plugins.

Support for a new provider

• Steps to be followed while implementing a new provider are mentioned here