Availability Zones Recommendations (AWS Kubernetes)

Cloud service provider relevance: AWS Kubernetes

Availability Zones scores and recommendations help you make informed decisions when selecting the best Availability Zones for launching instances in your Kubernetes cluster. The data on the Recommendations tab for a cluster is based on the Availability Zones scores calculated by Ocean, considering both Cost and Spot market availability.

The Availability Zones scores data directly relates to the allowed instance types configured in your Virtual Node Group to ensure that customized data is displayed.

To access the Ocean Availability Zones Recommendations:

1. In the left main menu, click Ocean > Cloud Clusters.
2. Select a cluster from the list of clusters.
3. Click the Recommendations tab.
4. Select a Virtual Node Group.

The Recommendations tab consists of a dashboard with two panels:

• RScore Graph

Recommendations Card

The Recommendations Card displays scores ranging from 0 to 100. These scores include various factors, such as the cost of instances within the cluster and the conversion rate (the ratio of the interruptions to the number of instances managed in the same market).

High Score Availability Zones

The Recommendations Card directly recommends Availability Zones that can reduce costs and interruption rates. You can use the information provided to add or expand to more Availability Zones, enhancing your options with a wider range of Spot Markets.

A star symbol next to an Availability Zone indicates it has a higher score than the average Virtual Node Group score for the month. So, although the Availability Zone is not currently configured, it has a higher score, indicating its potential benefits. You can expand or replace your Availability Zone offerings based on the star-marked recommendations. Expanding the options enables you to improve the results by having more choices and achieving a better balance between Spot Markets and ideal costs.

The recommendations are data-driven, considering instance interruptions and machine costs over time.

note

Only infrastructure costs are considered, not network costs.

Average Monthly Score Breakdown

The Average Monthly Score Breakdown is relative to the Spot market’s set within the cluster and is based on data collected from the past month. The scores consider the relevant instance types selected in the group when calculating the recommendation score for the Availability Zones.

tip

Click How is it calculated on the Recommendations Card to view this documentation.

Score Graph

The Availability Zone Score graph summarizes the data from the last 30 days. A straight line represents a configured Availability Zone, while a dashed line represents a non-configured Availability Zone.

Hover over a specific day in the graph to view the scores of the Availability Zones.

To manipulate the score graph:

• Click on a zone indicator in the legend at the top of the score graph, for example, us-east-ia in the example above, to remove the curve from the score graph. Click it again to return the curve to the score graph.

  note

  Scores may differ when navigating between Virtual Node Groups because they are calculated according to the relevant source resource types.

Configure Your Availability Zones Recommendations

To configure your Availability Zones recommendations:

1. In the Availability Zones Recommendations tab, Recommendations Card, click + Add to Configuration.

   The Update Configured AZ(s) dialog box lets you edit, add, and change the configured Availability Zones and subnets based on your configured and recommended Availability Zones.

   

   The currently configured Availability Zones are pre-selected.

   note

   All non-selected Availability Zones are grayed, but for those without subnets, a placeholder displays "This AZ doesn’t include subnets" (not clickable). If you want to configure such an Availability Zone, you must create subnets.

   important

   If the subnets are not set on the Virtual Node Group ('subnets' = null) but are taken from the Virtual Node Group template (default VNG), an information banner will appear in the dialog box to inform you that updating will override the Virtual Node Group Template configuration, and will affect all the custom Virtual Node Groups with ‘subnets’ = null.

2. Edit your Availability Zones and accept your recommendations as required.

   note

   You can replace a single Availability Zone without adding one.

   important

   Make sure that a PVC or any other component can run in the new Availability Zone before replacing the current Availability Zone.

3. Click Update. The updated configuration appears in the Recommendations tab dashboards.