Service Providers can use the controller to provide regional or global Kubernetes as a Service for end customer's applications.
Bare Metal Provider¶
Some customers want their clusters to operate on bare-metal. Providers that currently provide bare metal compute infrastructure can leverage the controller to provide higher value service where their customers can consume "clusters on bare metal" for their applications.
Although the large public cloud providers provide a large footprint, they may not be present in certain geographies that may be required for the customer's application. For example, countries such as Turkey, Israel and Saudi Arabia do not have public cloud footprint yet. A number of providers focus on these locations.
Many service providers offer a remotely managed compute platform that are deployed in customer premises where end customer applications can be deployed and managed. For example, a retailer may have 1,000s of stores and the in-store employees may require access to a store inventory application. Once containerized, these can be operated on the in-store CPE platform.
Every partner can be optionally white labeled. Service Providers can acquire, manage and support their end customers and may wish to provide a branded experience for their customers.
Partner Ops Console¶
Service Provider partners will use the Partner Ops Console to add/update/delete end customer orgs that they acquire and support. They will also use this console to manage the lifecycle of the clusters they operate.
The business relationship is between the provider and their customers. Service Providers are expected to provide Tier-1 and 2 support for their customers and leverage support behind the scenes.
In order to provide a white-labeled experience, a partner needs to provide us with the following items.
|Name||Name of the Provider's Service|
|Logo||The Provider's official logo that will be displayed to end users|
|Notification Email Address||The email address that will be used for notifications from the Controller|
|Helpdesk Email Address||The email address that will be shown to customers|
|Host Name for App Console||The hostname that will be used for the Application Console that end customers will use. For example, "app-console.provider.com"|
|Host Name for Ops Console||The hostname that will be used for the Ops Console that end customers will access. For example, "ops-console.provider.com"|
|TLS Info for Domain||The Certificate, Private Key and CA Certificate Chain for the provider's domain. For example, "provider.com"|
|TLS Info for Application Console||The Certificate, Private Key and CA Certificate Chain for the Application Console. For example, "https://app-console.provider.com"|
|TLS Info for Ops Console||The Certificate, Private Key and CA Certificate Chain for the Ops Console. For example, "https://ops-console.provider.com"|
Providers can also completely embed the controller directly into their platforms/customer portals and drive it programmatically via REST APIs supported by the controller.
Click for more information on the APIs.