diff --git a/src/docs/_media/sn-commits-where-to-find-it.png b/src/docs/_media/sn-commits-where-to-find-it.png new file mode 100644 index 0000000000..a57152665b Binary files /dev/null and b/src/docs/_media/sn-commits-where-to-find-it.png differ diff --git a/src/docs/managed-instance/_media/commitments-certs-and-secrets.png b/src/docs/managed-instance/_media/commitments-certs-and-secrets.png new file mode 100644 index 0000000000..1b513d786c Binary files /dev/null and b/src/docs/managed-instance/_media/commitments-certs-and-secrets.png differ diff --git a/src/docs/managed-instance/_media/commitments-permss-with-reader.png b/src/docs/managed-instance/_media/commitments-permss-with-reader.png new file mode 100644 index 0000000000..294e34744b Binary files /dev/null and b/src/docs/managed-instance/_media/commitments-permss-with-reader.png differ diff --git a/src/docs/managed-instance/_media/commitments-register-new-app.png b/src/docs/managed-instance/_media/commitments-register-new-app.png new file mode 100644 index 0000000000..2c2a1defee Binary files /dev/null and b/src/docs/managed-instance/_media/commitments-register-new-app.png differ diff --git a/src/docs/managed-instance/_media/commitments_register-upgrade-app.png b/src/docs/managed-instance/_media/commitments_register-upgrade-app.png new file mode 100644 index 0000000000..be54f1ad56 Binary files /dev/null and b/src/docs/managed-instance/_media/commitments_register-upgrade-app.png differ diff --git a/src/docs/managed-instance/_media/create-stateful-node-commitments.png b/src/docs/managed-instance/_media/create-stateful-node-commitments.png new file mode 100644 index 0000000000..88c66363a0 Binary files /dev/null and b/src/docs/managed-instance/_media/create-stateful-node-commitments.png differ diff --git a/src/docs/managed-instance/_media/sn-commits-where-to-find-it.png b/src/docs/managed-instance/_media/sn-commits-where-to-find-it.png new file mode 100644 index 0000000000..a57152665b Binary files /dev/null and b/src/docs/managed-instance/_media/sn-commits-where-to-find-it.png differ diff --git a/src/docs/managed-instance/_media/stateful-node-commitment-options.png b/src/docs/managed-instance/_media/stateful-node-commitment-options.png new file mode 100644 index 0000000000..60eaec0d89 Binary files /dev/null and b/src/docs/managed-instance/_media/stateful-node-commitment-options.png differ diff --git a/src/docs/managed-instance/_media/stateful-node-commits-add-perms-in wizard.png b/src/docs/managed-instance/_media/stateful-node-commits-add-perms-in wizard.png new file mode 100644 index 0000000000..f558e8e7b6 Binary files /dev/null and b/src/docs/managed-instance/_media/stateful-node-commits-add-perms-in wizard.png differ diff --git a/src/docs/managed-instance/features/commitments-setup-stateful-aks.md b/src/docs/managed-instance/features/commitments-setup-stateful-aks.md index d2f43dffb8..2ad512ae3a 100644 --- a/src/docs/managed-instance/features/commitments-setup-stateful-aks.md +++ b/src/docs/managed-instance/features/commitments-setup-stateful-aks.md @@ -41,9 +41,9 @@ Follow the instructions below while referring to the [Azure documentation](https 1. Obtain the credentials from your Azure app. Refer to [Get the Azure Credentials Required to Connect Commitments to Spot Products]() 2. Create or edit a stateful node. See [Manage Stateful Nodes](https://docs.spot.io/managed-instance/azure/tutorials/manage?id=manage-stateful-nodes). -3. In the Availability settings area, next to Utilize RIs/SPs, click **Add permission**. - - +3. In the Strategy area, next to Utilize RIs/SPs, click **Add permission**. + +this is where you will find the add permissions link ### Step 1: App Registrations @@ -51,23 +51,22 @@ Follow the instructions below while referring to the [Azure documentation](https Upgrade: - - + New: - - + + -2. Copy the following credentials from your Azure app and paste them into the fields: +3. Copy the following credentials from your Azure app and paste them into the fields: * Application (client) ID. * Directory (tenant) ID. -3. Go to Step 2: Certificates and Secrets +4. Go to Step 2: Certificates and Secrets ### Step 2: Certificates and Secrets - + 1. Copy the following credentials from your Azure app and paste them into the fields: * Application secret expiration date. @@ -77,7 +76,7 @@ Follow the instructions below while referring to the [Azure documentation](https ### Step 3: Permissions Assignment - + >IMPORTANT: > @@ -89,7 +88,7 @@ Follow the instructions below while referring to the [Azure documentation](https 1. Select the custom reader role, and the permissions in accordance with those you purchased from Azure (by default, both RI and SP are selected). -2. Use the following Azure PowerShell script to assign the Reservation Reader role at the tenant level: +2. Use the following Azure PowerShell script to assign the Reservation Reader / Savings Plan Reader roles at the tenant level: ``` Import-Module Az.Accounts @@ -152,5 +151,5 @@ Make sure that the VM attached to the specific stateful node also has `shouldUt Under Spot API > Elastigroup > Elastigroup Azure Stateful >... * [Create Stateful Node](https://docs.spot.io/api/#tag/Elastigroup-Azure-Stateful/operation/azureStatefulNodeCreate) or [Update Stateful Node](https://docs.spot.io/api/#tag/Elastigroup-Azure-Stateful/operation/azureStatefulNodeUpdate) (under statefulNode > strategy) -* [Get Stateful Node Status](https://docs.spot.io/api/#tag/Elastigroup-Azure-Stateful/operation/azureStatefulNodeGetStatus) or [Update Stateful Node Status](https://docs.spot.io/api/#tag/Elastigroup-Azure-Stateful/operation/azureStatefulNodeChangeState) +* [Get Stateful Node Status](https://docs.spot.io/api/#tag/Elastigroup-Azure-Stateful/operation/azureStatefulNodeGetStatus) or [Update Stateful Node Status](https://docs.spot.io/api/#tag/Elastigroup-Azure-Stateful/operation/azureStatefulNodeChangeState) diff --git a/src/docs/managed-instance/features/commitments-stateful-aks.md b/src/docs/managed-instance/features/commitments-stateful-aks.md index 392102cc1c..9e7e67f15e 100644 --- a/src/docs/managed-instance/features/commitments-stateful-aks.md +++ b/src/docs/managed-instance/features/commitments-stateful-aks.md @@ -8,7 +8,7 @@ Cloud service provider relevance: Azure Kubernetes ## Azure Commitments -Azure Commitments are agreements you make to use a certain amount of Azure resources over a specified period, including RIs and Saving Plans. +Azure Commitments are agreements you make to use a certain amount of Azure resources over a specified period, including RIs and SPs. Commitment types are as follows: @@ -20,7 +20,7 @@ You can prioritize available RIs and SPs: Prioritize to prevent their underutili ### Azure Reserved Instances -Azure RIs let you reserve VMs in Azure for a one- or three-year term, providing significant cost savings compared to pay-as-you-go pricing, and provide the following benefits: +Azure RIs let you reserve VMs in Azure for a one, three, or five year term, providing significant cost savings compared to pay-as-you-go pricing, and provide the following benefits: * Cost Savings: Typically offers discounts of up to 72% compared to on-demand prices. * Predictable Billing: Helps budget and forecast costs as you pre-purchase capacity. @@ -28,7 +28,7 @@ Azure RIs let you reserve VMs in Azure for a one- or three-year term, providing ### Azure Savings Plans -Azure SPs offer a flexible pricing model that lets you save up to 65% on your Azure compute costs in exchange for a commitment to spend a specific amount over a one- or three-year period and provide the following benefits: +Azure SPs offer a flexible pricing model that lets you save significantly on your Azure compute costs in exchange for a commitment to spend a specific amount over a one, three, or five year term and provide the following benefits: * Flexibility: Unlike RIs, SPs apply to a broader range of services and can adjust based on your usage patterns. * Automatic Savings: Automatically applies savings to eligible resources, making managing costs across multiple services easier. @@ -37,13 +37,11 @@ Azure SPs offer a flexible pricing model that lets you save up to 65% on your Az ## Commitments Scenarios - - - + ### Launching a VM -As part of the scale-up process, Stateful Node checks if an RI or SP applies to the market selection. If so, utilizes that RI/SP. +As part of the scale-up process, Stateful Node checks if an RI or SP applies to the market selection. If so, prioritizes that RI/SP. ### Running Spot VMs @@ -70,5 +68,5 @@ Stateful Node performs a strategy fix check every **xx (to check)** minutes to d The reversion will not occur if: * There is no alternative commitment or spot VM to revert back to. -* It violates the group's regular VM count request. +* It violates the group's regular VM count request.