Add a Kubernetes Cloud Provider Resource
The Kubernetes Cloud Provider 2nd Gen shell enables the deployment of Kubernetes instances on a Kubernetes cluster.
To add a Kubernetes resource:
-
Log in to CloudShell Portal as administrator.
-
Import the Kubernetes shell into CloudShell. For details, see Importing Shells.
-
In the Inventory dashboard, in the Resources tab, click the folder in which you want to create the resource.
-
Click + Add New.
-
In the Create New Resource dialog box, select the Kubernetes Cloud Provider Shell 2G cloud provider template.
-
Enter a Name for the Kubernetes resource.
noteThe resource's name has a limit of 100 characters and can only contain alpha-numeric characters, spaces, and the following characters: | . - _ ] [
-
Click Create.
The Resource dialog box is displayed.
-
Enter the required information.
Attribute | Description |
---|---|
Config File Path | Full path to a standalone kubernetes
|
AWS CP Resource Name | (Optional - EKS only) The CloudShell resource name for the AWS Cloud Provider Resource |
External Service Type | The service type the shell will create for external services. LoadBalancer type should be used when the Kubernetes cluster is hosted on a supported public cloud provider like AWS and Azure. Use NodePort when the cluster is self-hosted. |
Execution Server Selector | (Optional) This attribute points to a pre-defined group of execution servers (grouped by a common Execution Server Selector value). To make the association, enter the same value you specified on the execution server. tip The Execution Server Selector attribute does not come with the shell out-of-the-box. If you want to use it, add it to the shell in the Manage>Shells page and make sure the attribute has the Execution Server Selector rule, in Resource Manager Client's Attributes tab. |
-
Click Start Discovery.
When the discovery process completes, a confirmation message is displayed. The cloud provider resource is displayed in the Inventory dashboard in CloudShell Portal and in Resource Manager Client.
To customize the App deployment types and publish App orchestration parameters, see Customizing App Deployment Types.