Skip to content

Commit 55940b8

Browse files
paigecalvertpaigecalvert
authored
Merge pull request #2801 from replicatedhq/115325
Update license docs to reflect install type options
2 parents f41a367 + 2a5f43c commit 55940b8

File tree

5 files changed

+140
-39
lines changed

5 files changed

+140
-39
lines changed

‎docs/vendor/licenses-install-types.mdx‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
# Managing Install Types for a License (Beta)
2+
3+
This topic describes how to manage which installation types and options are enabled for a license.
4+
5+
:::note
6+
The "Install Types" licensing feature described in this topic is in Beta. To get access to this feature, reach out to your Replicated account representative.
7+
:::
8+
9+
## Overview
10+
11+
You can control which installation methods are available to each of your customers by enabling or disabling **Install types** fields in the customer's license.
12+
13+
The following shows an example of the **Install types** field in a license:
14+
15+
![Install types license fields](/images/license-install-types.png)
16+
17+
[View a larger version of this image](/images/license-install-types.png)
18+
19+
The installation types that are enabled or disabled for a license determine the following:
20+
* The Replicated installers ([Replicated KOTS](../intro-kots), [Replicated Embedded Cluster](/vendor/embedded-cluster-overview), [Replicated kURL](/vendor/intro-kurl)) that the customer's license entitles them to use
21+
* The installation assets and/or instructions provided in the Replicated Download Portal for the customer
22+
* The customer's KOTS Admin Console experience
23+
24+
Setting the supported installation types on a per-customer basis gives you greater control over the installation method used by each customer. It also allows you to provide a more curated Download Portal experience, in that customers will only see the installation assets and instructions that are relevant to them.
25+
26+
## Understanding Install Types {#install-types}
27+
28+
In the customer license, under **Install types**, the **Available install types** field allows you to enable and disable different installation methods for the customer.
29+
30+
You can enable one or more installation types for a license.
31+
32+
The following describes each installation type available, as well as the requirements for enabling each type:
33+
34+
<table>
35+
<tr>
36+
<th width="30%">Install Type</th>
37+
<th>Description</th>
38+
<th>Requirements</th>
39+
</tr>
40+
<tr>
41+
<th>Existing Cluster (Helm CLI)</th>
42+
<td><p>The customer does not have access to the Replicated installers.</p><p>When the <strong>Helm CLI Air Gap Instructions (Helm CLI only)</strong> install option is also enabled, the Download Portal displays instructions on how to pull Helm installable images into a local repository. See <a href="#install-options">Understanding Additional Install Options</a> below.</p></td>
43+
<td>The latest release promoted to the channel where the customer is assigned must contain at least one Helm chart.</td>
44+
</tr>
45+
<tr>
46+
<th>Existing Cluster (KOTS install)</th>
47+
<td>Allows the customer to install with Replicated KOTS in an existing cluster.</td>
48+
<td>
49+
<ul>
50+
<li>Your Vendor Portal team must have the KOTS entitlement</li>
51+
<li>The latest release promoted to the channel where the customer is assigned must contain KOTS custom resources</li>
52+
</ul>
53+
</td>
54+
</tr>
55+
<tr>
56+
<th>kURL Embedded Cluster (first generation product)</th>
57+
<td>
58+
<p>Allows the customer to install with Replicated kURL on a VM or bare metal server.</p>
59+
<p><strong>Note:</strong> For new installations, enable Replicated Embedded Cluster (current generation product) instead of Replicated kURL (first generation product).</p>
60+
</td>
61+
<td>
62+
<ul>
63+
<li>Your Vendor Portal team must have the kURL entitlement</li>
64+
<li>A kURL installer spec must be promoted to the channel where the customer is assigned. For more information, see <a href="/vendor/packaging-embedded-kubernetes">Creating a kURL Installer</a>.</li>
65+
</ul>
66+
</td>
67+
</tr>
68+
<tr>
69+
<th>Embedded Cluster (current generation product)</th>
70+
<td>Allows the customer to install with Replicated Embedded Cluster on a VM or bare metal server.</td>
71+
<td>
72+
<ul>
73+
<li>Your Vendor Portal team must have the Embedded Cluster entitlement</li>
74+
<li>The latest release promoted to the channel where the customer is assigned must contain an Embedded Cluster Config custom resource. For more information, see <a href="/reference/embedded-config">Embedded Cluster Config</a>.</li>
75+
</ul>
76+
</td>
77+
</tr>
78+
</table>
79+
80+
## Understanding Additional Install Options {#install-options}
81+
82+
After enabling installation types in the **Available install types** field, you can also enable the following options in the **Additional install options** field:
83+
84+
<table>
85+
<tr>
86+
<th width="30%">Install Type</th>
87+
<th>Description</th>
88+
<th>Requirements</th>
89+
</tr>
90+
<tr>
91+
<th>Helm CLI Air Gap Instructions (Helm CLI only)</th>
92+
<td><p>When enabled, a customer will see instructions on the Download Portal on how to pull Helm installable images into their local repository.</p><p><strong>Helm CLI Air Gap Instructions</strong> is enabled by default when you select the <strong>Existing Cluster (Helm CLI)</strong> install type.</p></td>
93+
<td>The <strong>Existing Cluster (Helm CLI)</strong> install type must be enabled</td>
94+
</tr>
95+
<tr>
96+
<th>Air Gap Installation Option (Replicated Installers only)</th>
97+
<td><p>When enabled, new installations with this license have an option in their Download Portal to install from an air gap package or do a traditional online installation.</p></td>
98+
<td>
99+
<p>At least one of the following Replicated install types must be enabled:</p>
100+
<ul>
101+
<li>Existing Cluster (KOTS install)</li>
102+
<li>kURL Embedded Cluster (first generation product)</li>
103+
<li>Embedded Cluster (current generation product)</li>
104+
</ul>
105+
</td>
106+
</tr>
107+
</table>
108+
109+
## About Migrating Existing Licenses to Use Install Types
110+
111+
By default, when an existing customer license is migrated to include the Beta **Install types** field, the Vendor Portal automatically enables certain install types so that the customer does not experience any interruptions or errors in their deployment.
112+
113+
The Vendor Portal uses the following logic to enable install types for migrated licenses:
114+
115+
If the existing license has the **KOTS Install Enabled** field enabled, then the Vendor Portal enables the following install types in the migrated license by default:
116+
* Existing Cluster (Helm CLI)
117+
* Existing Cluster (KOTS install)
118+
* kURL Embedded Cluster (first generation product)
119+
* Embedded Cluster (current generation product)
120+
121+
Additionally, if the existing **KOTS Install Enabled** license also has the **Airgap Download Enabled** option enabled, then the Vendor Portal enables both of the air gap install options in the migrated license (**Helm CLI Air Gap Instructions (Helm CLI only)** and **Air Gap Installation Option (Replicated Installers only)**).
122+
123+
Otherwise, if the **KOTS Install Enabled** field is disabled for the existing license, then the Vendor Portal enables only the **Existing Cluster (Helm CLI)** install type by default. All other install types will be disabled by default.

‎docs/vendor/releases-creating-customer.mdx‎

Lines changed: 16 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ This topic describes how to create and manage customers in the Replicated Vendor
88

99
## Create a Customer
1010

11-
This procedure describes how to create a new customer in the Vendor Portal. You can edit customer details at any time in the Vendor Portal.
11+
This procedure describes how to create a new customer in the Vendor Portal. You can edit customer details at any time.
1212

1313
For information about creating a customer with the Replicated CLI, see [customer create](/reference/replicated-cli-customer-create).
1414

@@ -22,58 +22,35 @@ To create a customer:
2222

2323
![Customer a new customer page in the Vendor Portal](/images/create-customer.png)
2424

25+
[View a larger version of this image](/images/create-customer.png)
26+
2527
1. For **Customer name**, enter a name for the customer.
2628

27-
1. For **Customer email**, enter the email address for the customer. The customer email address is required for Helm installations. This email address is never used send emails to customers.
29+
1. For **Customer email**, enter the email address for the customer.
30+
31+
:::note
32+
A customer email address is required for Helm installations. This email address is never used to send emails to customers.
33+
:::
2834

2935
1. For **Assigned channel**, assign the customer to one of your channels. You can select any channel that has at least one release. The channel a customer is assigned to determines the application releases that they can install. For more information, see [Channel Assignment](licenses-about#channel-assignment) in _About Customers_.
3036

3137
:::note
3238
<ChangeChannel/>
3339
:::
3440

35-
1. For **Custom ID**, you can enter a custom ID for the customer. Setting a custom ID allows you to easily tie this Replicated customer record to your own internal customer data systems during data exports. We suggest setting an alphanumeric value such as your Salesforce ID, Hubspot ID, etc for that customer. Replicated does not require the custom ID to be unique. The custom ID is for vendor data reconciliation purposes, and is not used by Replicated for any functionality purposes.
41+
1. For **Custom ID**, you can enter a custom ID for the customer. Setting a custom ID allows you to easily associate this Replicated customer record to your own internal customer data systems during data exports. Replicated recommends using an alphanumeric value such as your Salesforce ID or Hubspot ID.
42+
43+
:::note
44+
Replicated does _not_ require that the custom ID is unique. The custom ID is for vendor data reconciliation purposes, and is not used by Replicated for any functionality purposes.
45+
:::
3646

3747
1. For **Expiration policy**, by default, **Customer's license does not expire** is enabled. To set an expiration date for the license, enable **Customer's license has an expiration date** and specify an expiration date in the **When does this customer expire?** calendar.
3848

3949
1. For **Customer type**, set the customer type. Customer type is used only for reporting purposes. Customer access to your application is not affected by the type you assign to them. By default, **Trial** is selected. For more information, see [About Customer License Types](licenses-about-types).
4050

41-
1. In the **License options** pane, configure any of the built-in KOTS entitlements that you support in your application. For more information, see [Built-in License Fields](licenses-using-builtin-fields).
42-
43-
The available license options are:
44-
45-
<table>
46-
<tr>
47-
<th width="30%">Name</th>
48-
<th width="70%">Description</th>
49-
</tr>
50-
<tr>
51-
<td>KOTS Install Enabled</td>
52-
<td>Enables customers to install with Replicated KOTS.</td>
53-
</tr>
54-
<tr>
55-
<td>Airgap Download Enabled</td>
56-
<td>Enables new installations with this license to install from an air gap package or from an online installation.</td>
57-
</tr>
58-
<tr>
59-
<td>Gitops Enabled</td>
60-
<td> <GitOpsNotRecommended/> Enables customers with a KOTS-managed installation to transition from click-to-deploy to the KOTS Auto-GitOps workflow for deployment. See <a href="/enterprise/gitops-workflow">KOTS Auto-GitOps Workflow</a>. </td>
61-
</tr>
62-
<tr>
63-
<td>Identity Service Enabled</td>
64-
<td>Enables customers to integrate with third-party identity service providers to provision RBAC for authenticating to the admin console.</td>
65-
</tr>
66-
<tr>
67-
<td>Support Bundle Upload Enabled</td>
68-
<td>Enables installations to upload support bundles directly from the admin console.</td>
69-
</tr>
70-
<tr>
71-
<td>Allow Snapshot</td>
72-
<td>Enables customers to create snapshots for backup and restore. Vendors must also add a Backup custom resource. See <a href="/reference/custom-resource-backup">Velero Backup Custom Resource</a>.</td>
73-
</tr>
74-
</table>
75-
76-
1. (Optional) For **Custom fields**, configure any custom fields that are available for your Replicated application. For more information about how to create custom fields for your application, see [Managing Custom License Fields](licenses-adding-custom-fields).
51+
1. Enable any of the available options for the customer. For more information about the license options, see [Built-in License Fields](/vendor/licenses-using-builtin-fields). For more information about enabling install types, see [Managing Install Types for a License (Beta)](/vendor/licenses-install-types).
52+
53+
1. For **Custom fields**, configure any custom fields that you have added for your application. For more information about how to create custom fields for your application, see [Managing Custom License Fields](licenses-adding-custom-fields).
7754

7855
1. Click **Save Changes**.
7956

‎sidebars.js‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -168,6 +168,7 @@ const sidebars = {
168168
'vendor/releases-creating-customer',
169169
'vendor/licenses-adding-custom-fields',
170170
'vendor/licenses-using-builtin-fields',
171+
'vendor/licenses-install-types',
171172
'vendor/licenses-about-types',
172173
'vendor/licenses-download',
173174
{

‎static/images/create-customer.png‎

3.41 KB
Loading

‎static/images/license-install-types.png‎

385 KB
Loading

0 commit comments

Comments
 (0)