feat: Allow multi-cluster Marketplace deployments

[n0vabyte]

Description 📝

Updates how UDF data cluster_size works in stackscripts. The goal of this PR is to introduce multi-cluster instance types for the Marketplace apps. Most importantly, reflect the correct price for the cluster being created. This PR allows us to match $prefix_cluster_size with $prefix_cluster_type to create a dynamic cluster in a cluster deployment. For example, ELK can have multi-node cluster with different instance types associated with it.

Changes 🔄

• packages/manager/src/features/Linodes/LinodeCreate/Summary/utilities.ts updated to parse cluster data associated with the instance type being created.
• Summary.tsx is updated to reflect that if a cluster is being created with a heterogeneous mix of instance is doesn't display the Linode type. This cleaner to display that a "cluster_name of $n nodes" is being created.
• packages/manager/src/features/Linodes/LinodeCreate/utilities.ts is updated to map the instance Label that the customer is created to a valid instance type. I am using types.json.

Scope 🚢

Upon production release, changes in this PR will be visible to:

• All customers using Stackscript. Customer will be able to use $prefix_cluster_size, $prefix_cluster_type and cluster_name in their stackscripts to extend functionality.

Target release date 🗓️

Next release cycle if possible. No rush on making the changes GA.

Preview 📷

Before	After

How to test 🧪

Step 1: Create a new Stackscript

1. One your Cloud Manager account, click the Stackscripts tab on the left-hand side.
2. Click on the button 'Create Stackscript' on the upper right-hand side
3. Fill out the StackScript Label, Description and Target Images.
4. Past the following in the Script code box:

#!/bin/bash
# ELK PoC

# Cluster Name
#<UDF name="cluster_name" label="Cluster Name">

# This instance (provisioner):
#<UDF name="cluster_size" label="Kinaba Size" oneOf="1,2" default="1">

# Cluster size ($prefix_cluster_size):
#<UDF name="elastic_cluster_size" label="Elasticsearch Cluster Size" oneOf="2,3" default="2">
#<UDF name="logstash_cluster_size" label="Logstash Cluster Size" oneOf="2,4" default="2">

# Instance types($prefix_cluster_type):
#<UDF name="elastic_cluster_type" label="Elasticsearch Instance Type" oneOf="Dedicated 4GB,Dedicated 8GB,Dedicated 16GB,Dedicated 32GB,Dedicated 64GB" default="Dedicated 4GB">
#<UDF name="logstash_cluster_type" label="Logstash Instance Type" oneOf="Dedicated 4GB,Dedicated 8GB,Dedicated 16GB,Dedicated 32GB,Dedicated 64GB" default="Dedicated 4GB">

5. Click on the Create StackScript button.

Step 2: Deploy StackScript

1. From the StackScripts section, select the StackScript that you just created.
2. Click on the Deploy New Linode button on the upper right-hand side
3. Select the cluster sizes and Linode plans that you like
4. Scroll to the bottom of the page to see Summary

From here you will be able to select different cluster size for Kibana, Elasticsearch and Logstash. The Linode plan that is selected for Elasticsearch and Logstash is appropriately added to the total at the bottom of the Summary.

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• [x ] All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[dwiley-akamai]

Hi @n0vabyte, thank you for opening this PR. Where are these changes coming from–a JIRA ticket that outlines the requirements for this work, an independent idea you had and implemented, etc.?

[n0vabyte]

@bnussman-akamai any updates?

[bnussman-akamai]

Will be reviewing today

[bnussman-akamai]

Overall functionality is looking solid! I just think we need to tidy up some things

[n0vabyte]

Any updates?

[bnussman-akamai]

Hoping to rereview soon.

Do we have a testing plan for this?

I think it would ideal if we have some thing in place. Like unit tests, cypress e2e tests, or a QA team responsible for testing this

[dwiley-akamai]

Verification steps ✅

I agree that implementing some more robust unit and/or E2E tests or having a testing plan in place would be best

[bnussman-akamai]

I'm going to push up one more small change, then I'll approve!

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #17 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	812 Passing	11 Skipped	38m 27s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	Cloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"

[bnussman-akamai]

Looks good! I pushed up some changes and unit tests so double check behind me

I think the clone-linode.spec.ts failure can be disregarded