From 860f3fa4ca2d185ad30e8c7b0c590785f011d118 Mon Sep 17 00:00:00 2001 From: rickshar <159915991+rickshar@users.noreply.github.com> Date: Mon, 25 Aug 2025 11:31:46 +0300 Subject: [PATCH 1/4] Update ocean-cluster-right-sizing-tab.md --- .../ocean-cluster-right-sizing-tab.md | 137 +----------------- 1 file changed, 1 insertion(+), 136 deletions(-) diff --git a/src/docs/ocean/features/ocean-cluster-right-sizing-tab.md b/src/docs/ocean/features/ocean-cluster-right-sizing-tab.md index 5924ce250..56bd1220e 100644 --- a/src/docs/ocean/features/ocean-cluster-right-sizing-tab.md +++ b/src/docs/ocean/features/ocean-cluster-right-sizing-tab.md @@ -1,138 +1,3 @@ # Ocean Cluster Automatic Right Sizing -Cloud service provider relevance: EKS, AKS, and GKE - -To help you improve the efficiency and performance of your cloud environments, Ocean’s rightsizing capabilities provide recommendations that target over-provisioning and underutilization. - -Container resource requests, defined in a Kubernetes cluster, determine a pod’s allocation to a node. Incorrect CPU and memory requirements assumptions can incur unnecessary and costly cloud infrastructure waste. Ocean lets you access detailed right-sizing recommendations that fine-tune these resource requests based on the actual resource utilization of any running application over time. This way, you can define better resource requirements based on actual consumption to avoid over-provisioning or underutilizing a cluster and increase the cluster's efficiency. - -Ocean provides container-level right-sizing recommendations so you can focus on improving specific application resource requests and make impactful changes to resource utilization. - -All Ocean customers have a minimal version for automatic right-sizing that supports up to 10 workloads. - - - -To opt-in and turn on the full capabilities of this powerful feature, [Contact Support in the Spot console online chat or by email](https://spot.io/support/) - -## Prerequisites - -Before you attempt to fine-tune your cluster resources according to Ocean's recommendation, you will need: - -* A Spot account. -* [Ocean Controller Version 2.0.52 and above](https://docs.spot.io/ocean/tutorials/ocean-controller-v2/) installed and running. - * Make sure to install the [Metrics Server](https://github.com/kubernetes-incubator/metrics-server#deployment). -* Vertical Pod Autoscaler project (VPA) Version 1.0.0 and above installed on your cluster. If the VPA is not already running on your cluster, run the following helm commands: - -```sh - -helm repo add spot https://charts.spot.io -helm repo update -helm install spot/ocean-vpa -``` ->**Note**: To turn on automatic right-sizing, contact your [support](https://spot.io/support/) team via email or chat. - -## How It Works - -For Ocean Kubernetes clusters, Right-sizing utilizes the Metrics Server and initializes recommendations after one hour of initial data collection. - -Once every 15 seconds, the Ocean Controller queries the Metrics Server for pod utilization (the equivalent of kubectl top pods). Based on the last 14 days of collected metrics, Ocean calculates relevant consumption metrics for each resource, such as CPU and Memory, and bases its recommendations on these calculated metrics. - -![features-rightsizing-01a](https://github.com/spotinst/help/assets/159915991/4ded53db-21ff-4a17-82b2-77b32c598351) - -The output produces a single point-in-time data point for each pod. Ocean then aggregates the pods' data per workload container. - -Using the per-workload container aggregated data points, Ocean makes recommendations based on a mechanism that attempts to even out peaks and troughs in resource demand. The Right-Sizing engine runs every hour to generate new recommendations and update existing ones. - -Recommendations for decreasing and increasing memory or CPU requests are based on the percentile defined for the cluster (the default is the 85th percentile). - -Ocean handles the right-sizing workload limits as follows: - -* Automatic tuning for up-sizing recommendations: Ocean automatically adjusts the workload's limit values for up-sizing based on the recommended resource allocations while maintaining the same ratio between the requests and the limit. -* Automatic tuning for down-sizing recommendations: Ocean keeps the existing limits. - -You view the right-sizing recommendations via: - -* Ocean console, under the Cloud Cluster Right Sizing [Advanced Optimization](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab) tab. -* [Spot API](https://docs.spot.io/api/#tag/Ocean-AWS/operation/oceanAwsFilterRightSizingWithFilter). - -## View Right Sizing for a Cluster - -Ocean provides resource recommendations to assist in adjusting deployment requests based on actual CPU and memory consumption. - -These recommendations can help optimize resource allocation and ensure that the requested resources align with the actual CPU and memory consumption, improving efficiency and cost-effectiveness in managing your deployments. - -To view right-sizing for a cluster: - -1. In the left main menu, click **Ocean** > **Cloud Clusters**. -2. Select a cluster from the list of clusters. -3. Click the **Right Sizing** tab. - -The Right-Sizing tab displays a Dashboard divided into the following panels: - -* The Right-Sizing Savings panel summarizes your potential maximum savings from right-sizing, vCPU, and memory usage and recommendations for a selected namespace, workload, and container. -* Right-sizing Resource Usage panel: This panel graphically displays your vCPU and memory resource usage in the last two weeks. - -If the Right Sizing tab does not display any data: - -* Make sure that your metrics server is installed and functioning correctly. -* The initial one-hour data collection period may not have elapsed. - ->**Note**: You can filter your data according to namespaces, workloads/containers, or labels from the provided drop-down menus. - -### Right Sizing Savings Panel - -The Right-Sizing Savings panel contains a set of savings widgets, which show your potential savings from Ocean cluster right sizing, derived from data collected in the last two weeks: - -![saving-right-sizing](https://github.com/user-attachments/assets/0be792e0-0a94-42ac-aea1-42e1acce8f5f) - -The workload status widget (on the left) shows one of the following statuses: -* Optimization maximized status: All workloads are optimized. -* Limited optimization status: All workloads have limited optimization. Hover over the widget and click the link to access the [Right Sizing Optimization list](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab?id=workloads-optimization-list). -* No optimization status: No workloads are optimized, and the total Potential Monthly Maximum Savings are shown. -* Pending optimization status: All pending workloads will be optimized according to the configured [schedule](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab?id=work-with-right-sizing-rules). - -If you have workloads with differing statuses, the workload status widget shows a status according to the following logic: -* The potential savings are shown if at least one workload has potential savings. -* The limited optimization status is shown if at least one workload is pending, but none have potential savings. -* The pending status is shown if at least one workload is pending, but there are neither workloads with limited optimization nor workloads with potential savings. - -> **Note**: The status changes according to the filters applied in this panel and the Workloads Optimization list in the [Advanced Optimization tab](ocean/features/ocean-cluster-right-sizing-recom-tab?id=automatic-right-sizing-recommendations-and-rules) - -vCPU and memory usage widgets: -* vCPU Usage: Used and allocated vCPU resources, recommended increase or decrease of vCPU resources, and over-provisioning. -* Memory Usage: Used and allocated memory resources, a recommendation to increase or decrease the memory resources, and the overprovisioning. - -### Right Sizing Resource Usage Panel - -This panel contains two widgets: - -* vCPU usage in the last 2 weeks: Displays graphs for used, allocated, and recommended vCPU usage based on data from the last 2 weeks. -* Memory usage in the last 2 weeks: Displays graphs for used, allocated, and recommended memory usage based on data from the last 2 weeks. - - - -Hover over a data point in the **vCPU usage in the last 2 weeks** widget to view usage details: ->**Note**: The default **85th percentile vCPU usage** and **Maximum memory usage** options are used to calculate the right-sizing recommendations for all usage parameters. -* Allocated vCPU usage based on data from the last 2 weeks. -* Actual vCPU usage based on data from the last 2 weeks (you can change the default from the **Usage drop-down menu**). - * 85th percentile vCPU usage (**default**) - * 99th percentile vCPU usage - * 95th percentile vCPU usage - * 90th percentile vCPU usage - * Average vCPU usage -* Suggested vCPU usage based on data from the last 2 weeks. -Hover over a data point in the **Memory usage in the last 2 weeks** widget to view: -* Allocated memory usage in GiB based on data from the last 2 weeks. -* Actual memory usage in GiB based on data from the last 2 weeks (you can change the default from the **Usage drop-down menu**). - * Maximum memory usage in GiB (**default**) - * Average memory usage in GiB -* Suggested memory usage in GiB based on data from the last 2 weeks. - -## Related Topics - -* [Right-Sizing Troubleshooting](https://docs.spot.io/ocean/features/troubleshoot-right-sizing) -* [Right-Sizing Rules and Reommendations](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab) - - - - +This feature has moved to the new [Flexera documentation portal]( https://docs-spot.flexera.com/ocean/features/ocean-cluster-right-sizing-tab). From 564c92c06a84eb96eb18f78dddbb158c11ec3981 Mon Sep 17 00:00:00 2001 From: rickshar <159915991+rickshar@users.noreply.github.com> Date: Mon, 25 Aug 2025 11:32:54 +0300 Subject: [PATCH 2/4] Update ocean-cluster-right-sizing-recom-tab.md --- .../ocean-cluster-right-sizing-recom-tab.md | 210 +----------------- 1 file changed, 1 insertion(+), 209 deletions(-) diff --git a/src/docs/ocean/features/ocean-cluster-right-sizing-recom-tab.md b/src/docs/ocean/features/ocean-cluster-right-sizing-recom-tab.md index eca0edfe3..2e8cd68f1 100644 --- a/src/docs/ocean/features/ocean-cluster-right-sizing-recom-tab.md +++ b/src/docs/ocean/features/ocean-cluster-right-sizing-recom-tab.md @@ -1,212 +1,4 @@ # Automatic Right-Sizing Recommendations and Rules -Cloud service provider relevance: EKS, AKS, and GKE - -This topic shows you how to view right-sizing recommendations for workloads and containers and work with right-sizing rules. - -Before you begin, see [Ocean Cluster Automatic Right-Sizing](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-tab) for a full description of this Ocean feature. - -To view your right-sizing recommendations and rules: - -1. In the left main menu, click **Ocean** > **Cloud Clusters**. -2. Select a cluster from the list of clusters. -3. Click **Right Sizing > Advanced Optimization**. - -The Advanced Optimization tab contains these lists: - -* Workloads Optimization List. -* Automation Rules List. - -Your workload optimization activities impact the status of the workloads in the [Right Sizing Savings panel](ocean/features/ocean-cluster-right-sizing-tab?id=right-sizing-savings-panel) - -## Workloads Optimization List - - - -This list displays your right-sizing recommendations per workload and lets you drill down per container. -* [Right Sizing rules](ocean/features/ocean-cluster-right-sizing-recom-tab?id=automation-rules-list) that are attached to specific workloads. -* Workload optimization status: If the workload is [attached](ocean/features/ocean-cluster-right-sizing-recom-tab?id=attach-a-right-sizing-rule-to-one-or-more-workloads) to a right-sizing rule, the name of the rule appears under the **Rules** column. The rule can have one of the following workload (colored) optimization statuses: - * Green (Optimized): Workload is fully optimized, and no action is required. - * Orange (Limited): Ocean applied recommendations to the workload, but there are limitations due to overhead, HPA, etc. - * Blue (Pending): Rule has been attached to the workload but is out of schedule. - * Red (Not Optimized): Issues due to user configuration, for example, thresholds or exclude preliminary recommendations. - * Gray (Rollback): Ocean rolled back to the original deployment request and suspended the workload's attachment to the rule. - * Brown (Not Attached): The Workload is not optimized. -* Workload type and names. -* vCPU and memory right sizing recommendations per deployment. Recommended increases are shown with a green up arrow, and recommended decreases are shown with a red Down arrow. -* HPA: If the workload is configured with HPA, **ON** is displayed under HPA. Hover over the entry for information about the specific HPA trigger (CPU/Memory/other). -* Potential monthly maximums savings if you adopt the recommendations. - -> **Notes**: -> - Hover over the Limited and Not optimized statuses to view more details in a tooltip. -> - There are no vCPU / memory recommendations or Potential monthly max if a workload is fully optimized. Savings are displayed for the workload because Ocean is already optimizing it. -> -> - If the button appears on the right of the screen, workloads were moved to rollback status. See [Acknowledge a Workload Rollback](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab?id=acknowledge-a-workload-rollback) - -> If a message about VPA not reporting is displayed: -> - You cannot attach rules to workloads. -> - If at least 1 rule was previously attached to a workload, the workload is not optimized due to the missing VPA installation in the cluster. - -The graphical display above the list shows the breakdown of these workload optimization statuses. - -To view a list of your potential savings and recommendations per container: - -* Click on the down arrow to the left of a workload to drill down to the containers. For each container, you can then view the following: - - * vCPU Request: showing current and average utilization and a recommended increase or decrease for this resource (in vCPU units). If no changes are required, a Keep icon is displayed. - * Memory Request: This shows current and Average utilization and a recommended increase or decrease for this resource (in MiB units). If no changes are required, a Keep icon is displayed. - * Right-Sizing Recommendations: Show the recommended changes in vCPU and memory. Click on the Copy icon to save these changes for later. - -## Automation Rules List - -![automation-rules-e](https://github.com/user-attachments/assets/f128606b-a91d-4935-a36a-c3c4984287b8) - -This list displays your existing right-sizing rules. -Each rule entry shows relevant information about the parameters that trigger the rule and its scheduling plan. - -## Work with Right Sizing Rules - -You can create right-sizing rules to trigger immediately after a specific set of requirements is met or at a specific time after the requirements are met. - -### Create or Edit a Right-Sizing Rule - -To create/edit a right-sizing rule: - -1. Click the **Advanced Optimization** tab if not already displayed. -2. To create a new rule, click **+ Add new rule** above the Automation Rules list (or to edit an existing rule, click the pencil icon in the rule). - - - -3. In the Configure Automation Rule dialog box, enter/edit the unique rule name. -4. Select when to apply the recommendation by selecting one of the following options: - - * **Once available**: The recommendation is applied immediately after it becomes available. - * **Specific time**: You select when to apply the recommendation after it becomes available. - -![rule-when-to-apply-3](https://github.com/user-attachments/assets/5cb76163-9f33-477e-95d6-b99b36f0f200) - -5. Turn on **Exclude preliminary recommendation** if you want to suppress recommendations as long as the workload has preliminary status (4 days). -6. Select one of the **Restart replicas** options: - * All manifests. - * Manifests with more than 1 replica only. - * No restart. -7. Click the **Set the resources percentage change** down arrow to apply the recommendation, and set the CPU and Memory percentage thresholds. This is the minimum percentage change from the current request for applying a recommendation. If the right-sizing recommendation exceeds the percentage threshold for either resource (CPU or Memory), it will be applied to both resources, and the resulting status will be **fully optimized**. We do this because the original purpose of the threshold is to prevent unnecessary pod deletion. However, if we need to delete a pod and relaunch a new one for one resource, we do the same for the other. -8. Click the **Set recommendation ranges for resources** down arrow and enter the upper and lower boundary values for CPU (millicpu) and Memory (MiB) requests to apply a recommendation. By default, the minimum values are 10 millicpu for CPU and 32 MiB for memory; no lower values will be accepted. - * If a recommendation is above the set boundaries, automatic right-sizing will apply the recommendation using the maximum value configured in the rule. - * If a recommendation is below the set boundaries, automatic right-sizing will apply the recommendation using the minimum value configured in the rule. -9. Click the **Set overhead for resources** down arrow and set the CPU and memory percentage overheads. An overhead specifies the percentage of extra resources to add to the new request recommendation. -10. Ocean supports automatic right-sizing for HPA-associated workloads. To enable, click **Apply HPA on associated workload**. - -11. Turn on **Auto-attach** if you want to automatically attach rules to workloads based on selected criteria. - * In the Auto-attach area, select required namespaces / labels. - - - -12. After you save the rule, it appears in the area under the [Workloads Optimization list](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab?id=workloads-optimization-list). - - > **Notes**: - > - Default values for Overhead and Automation Threshold are **10%** and **5%** respectively. - > - The **10%** default overhead is calculated within the recommendation itself. - > - Threshold value is only used for down-sizing cases - -### Attach a Right-Sizing Rule to One or More Workloads - -Options: - -* Auto-attach: Turn on auto-attach and let Ocean automatically attach rules to workloads based on selected criteria. See [Create or Edit a Right-Sizing Rule](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab?id=create-or-edit-a-right-sizing-rule). ->**Note**: Auto-attach attaches rules to existing and newly-added workloads. - -* Manual attach: Manually attach a specific right-sizing rule to one or more workloads. - - -To manually attach a rule: - -1. Select one or more workloads in the Workloads Optimization list. -2. From the Actions drop-down menu above the table, click **Attach Rule**. - -![attach-rule-to-workload](https://github.com/user-attachments/assets/be315afa-0ef8-4d30-b1f3-422e8caf8633) - -3. You can either attach an existing or new rule you create from scratch (a new rule will be attached to the workload(s) you selected earlier): - - * Click the **Select from existing rule** drop-down menu and then select a rule. - * Click **Create new rule from scratch** (see [Create or Edit a Right-Sizing Rule](ocean/features/ocean-cluster-right-sizing-recom-tab?id=create-or-edit-a-right-sizing-rule)) - -4. Save and apply the rule. - -### Detach a Right-Sizing Rule from One or More Workloads - -To detach a rule from one or more workloads: - -1. Select workloads in the Workloads Optimization list. -2. From the Actions drop-down menu above the list, click **Detach Rule**. - ->**Important**: If you encounter Kubernetes issues, we recommend detaching workloads from rules and rolling them in your cluster. - -### Delete a Right-Sizing Rule - -To delete a right sizing rule: - -1. To the right of the row for the rule in the list, click the wastebasket icon. -2. When the confirmation message appears, Click **Delete**, or **Cancel** (if you are unsure). - ->**Important**: You cannot restore a deleted right-sizing rule. In addition, a rule may be deleted only if it is no longer attached to a workload. - -### Acknowledge a Workload Rollback - -If a workload encounters an OOM error, Ocean rolls back to the original deployment request and suspends the workload's attachment to the rule. The workload moves to **rollback** status. When at least one workload has rollback status, the button appears at the top-right of the screen. - -To acknowledge a workload rollback: - -1. Click **Acknowledge Rollback** to view all the workloads with the rollback status. - -![right-sozomg-rollback-dialog](https://github.com/user-attachments/assets/4bb206f5-73e3-4b26-b7fb-19e5e519505f) - -* The rollback drill-down list contains the following information: - * Workload Name. - * Namespace. - * CPU Update in vCPUs (before and after rollback). - * Memory Update in MiBs (before and after update). - * Rollback Time: In format MM/DD/YYYY HH:MM:SS AM/PM - -2. Select the checkboxes for the required workloads. -3. Click **I Acknowledge the Rollback**. - -The workloads are displayed in the [Workloads Optimization List](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab?id=workloads-optimization-list) without any attached rules. Before attaching a rule to a rolled-back workload, first fix the issue. - -### Set the vCPU/Memory Percentile - -You can select the right-sizing percentile settings to calculate the vCPU and memory recommendations. -The lower the percentile, the stronger the recommendations. - -By default: - -* vCPU: Right-sizing uses the 85th percentile. -* Memory: Right-sizing uses the maximum value. - ->**Important:** Changing the percentile setting will impact the recommendations that were already applied (this may take a few minutes to update). - -To change settings: - -1. Click **Settings** above the [workloads optimization list](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-recom-tab?id=workloads-optimization-list). - - - -2. Click the arrow on the right for **vCPU** or **Memory** as required (vCPU shown in the example). - - - -3. Change the current value(s) and save. - -## Best Practices - -These are the Right-Sizing Best Practices: - -* Workload limits should not have the same values as requests. -* If you set overheads for resources, start with a relatively high overhead (20%) and decrease it with time. -* If you set boundaries (recommendation ranges for resources), avoid applying the specific rule to all workloads. All services have different purposes. - -## Related Topics - -* [Right-Sizing Troubleshooting](https://docs.spot.io/ocean/features/troubleshoot-right-sizing) -* [Automatic Right-Sizing -Introduction](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-tab) +This feature has moved to the new [Flexera documentation portal]( https://docs-spot.flexera.com/ocean/features/ocean-cluster-right-sizing-tab). From cf14576b4632d3975d318878ec3fbd4b5acc9933 Mon Sep 17 00:00:00 2001 From: rickshar <159915991+rickshar@users.noreply.github.com> Date: Mon, 25 Aug 2025 11:33:18 +0300 Subject: [PATCH 3/4] Update ocean-cluster-right-sizing-savings-tab.md --- .../ocean-cluster-right-sizing-savings-tab.md | 56 +------------------ 1 file changed, 1 insertion(+), 55 deletions(-) diff --git a/src/docs/ocean/features/ocean-cluster-right-sizing-savings-tab.md b/src/docs/ocean/features/ocean-cluster-right-sizing-savings-tab.md index e2ef1d86f..3e9a723f7 100644 --- a/src/docs/ocean/features/ocean-cluster-right-sizing-savings-tab.md +++ b/src/docs/ocean/features/ocean-cluster-right-sizing-savings-tab.md @@ -1,57 +1,3 @@ # Automatic Right-Sizing Actual Savings -Cloud service provider relevance: EKS, AKS, and GKE - -This topic shows you how to view your (actual) right-sizing savings from applying down-sizing recommendations to your workloads. - -Before you begin, see [Ocean Cluster Automatic Right-Sizing](https://docs.spot.io/ocean/features/ocean-cluster-right-sizing-tab) for a full description of this Ocean feature. - -To view your right-sizing savings: - -1. In the left main menu, click **Ocean** > **Cloud Clusters**. -2. Select a cluster from the list of clusters. -3. Click **Right Sizing > Savings**. - -The Savings tab contains the following: - -* Right-sizing savings panel -* Workload savings list. - - - -At the top of the actual savings overview, you can filter according to: - -* Time - * Last 30 days. - * Last 7 days. - * This month (from the first day of the month until today). - -* Workloads (optimized workloads only). -* Namespaces. - -The right-sizing savings panel shows the following: -* Savings in dollars. -* Selected time frame. -* Pie chart together with the savings per namespaces (that affected the most savings). - -The workload savings list shows your actual right-sizing savings per workload. -These are the workloads that were optimized automatically based on Ocean's recommendations. - ->Note: Only down-sizing recommendations apply. - -* Workload Name. -* Namespace. -* Workload Type: (if the workload was deleted, it is marked as Deleted). -* CPU: - * With Ocean (green color): The sum of all the CPU requests that Ocean recommended and applied automatically. - * Without Ocean: The sum of all CPU requests in your original workloads. -* Memory: - * With Ocean (green color): The sum of all of the memory requests that Ocean recommended and applied automatically. - * Without Ocean: The sum of all the memory requests in your original workloads. -* Right-sizing savings (dollars) for the workload. - - - - - - +This feature has moved to the new [Flexera documentation portal]( https://docs-spot.flexera.com/ocean/features/ocean-cluster-right-sizing-tab). From 0ec483985e421282d030eb7a430e0be0e6c5fb0a Mon Sep 17 00:00:00 2001 From: rickshar <159915991+rickshar@users.noreply.github.com> Date: Mon, 25 Aug 2025 11:33:46 +0300 Subject: [PATCH 4/4] Update troubleshoot-right-sizing.md --- .../features/troubleshoot-right-sizing.md | 21 +------------------ 1 file changed, 1 insertion(+), 20 deletions(-) diff --git a/src/docs/ocean/features/troubleshoot-right-sizing.md b/src/docs/ocean/features/troubleshoot-right-sizing.md index 47283bc8a..f457c4921 100644 --- a/src/docs/ocean/features/troubleshoot-right-sizing.md +++ b/src/docs/ocean/features/troubleshoot-right-sizing.md @@ -1,22 +1,3 @@ # Automatic Right-Sizing-Troubleshooting -Cloud service provider relevance: EKS, AKS, and GKE - -## VPA not reporting message appears at the top of the right-sizing page - -![vpa-not-reporting](https://github.com/user-attachments/assets/ca3ca20c-afcc-484a-9462-0b86f43e9a57) - -This may indicate that the VPA updater and admission controller pods are not reporting. - -In this case, the right-sizing recommendations cannot be injected when a pod is launched, and you will not be able to attach a rule to a workload, which will move to the **Limited** status. - ->**Note**: -> - Spot checks the health of the VPA pods belonging to the Spot Ocean VPA Project. -> - For the Native VPA project, health checks are performed as long as the deployment's name is not changed. - -## Security Group not correctly configured - -In this case, your pod may not be launched according to the values defined on the VPA. - -To avoid this issue, ensure that your inbound rule for your node group's security group allows traffic to the Spot webhook listening port. This ensures smooth communication between the Kubernetes Server API and the webhook. -See [Create a security group for your Amazon EC2 instance - Amazon Elastic Compute Cloud](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-security-group.html). +This feature has moved to the new [Flexera documentation portal]( https://docs-spot.flexera.com/ocean/features/ocean-cluster-right-sizing-tab).