Spot Ocean

As more organizations use containers, especially Kubernetes, it becomes more important to understand the cost of those workloads. To help with this, Flexera One works with Spot Ocean to provide better cost visibility and smart savings recommendations.

Spot Ocean manages cloud infrastructure for containers and works with AWS, Azure, and GCP. It sees how your containers use resources and automatically adjusts compute power to keep things running smoothly. It also picks the best mix of spot, reserved, and on-demand instances to save money and keep performance high.

Flexera One with Spot Ocean provides:

• Cost and usage visibility at cluster, node, namespace, and pod granularity.
• Container request optimization recommendations.
• Automated node management and optimization.
• Cluster node optimization recommendations (Flexera right-size compute).
• Shared namespace cost reallocation across other namespaces.
• Reliably run on spot instances:
  • Market-leading insight into spot market trends.
  • Optional Eco integration considers unused commitments for nodes.
• Automated workload and container optimization:
  • Automated container rightsizing.
  • Ocean proactively identifies underutilized nodes and efficiently bin packs their pods to scale down the nodes and reduce cluster cost.

Available Integration Versions

The Flexera One with Spot Ocean integration supports these versions:

• Free (Read-Only) Version
  Ocean is deployed in read-only mode and does not manage your clusters. Instead, it collects information from your clusters. CCO imports detailed usage and cost data from Ocean, enabling deeper insights. You receive a daily breakdown of your Kubernetes spend by cluster, node, namespace, and pod.

  The table shows the cost and usage data that CCO imports from Ocean:

  Cost visibility by construct	Cost visibility by metadata	Cost visibility by infrastructure resource
  Cluster Namespace Pod	Label	Compute Memory Storage

• Paid Version
  Includes everything in the read-only version plus right-sizing, bin packing, and autoscaling features to further reduce Kubernetes costs.

note

• Pod-level daily granularity is viewable only within CCO.
• For more information, see the Spot Ocean documentation.

Onboard Flexera One with Spot Ocean

Make sure you have:

• A Flexera One account with CCO provisioned
• A Spot account with Ocean clusters

Contact Spot support to enable the Ocean-CCO integration for your Spot organization.

What to do in Flexera One

1. Obtain your Flexera org ID. You can copy the ID after you log in from the URL.

2. Generate a Refresh token.

   note

   If you update this refresh token later on, you should enter the new value with an Update API request.

3. Generate a temporary access token.

4. Create a CBI connector using your temporary access token and Flexera org ID. Put the temporary access token as a Bearer token for authorization.

   You can use the Flexera FinOps Onboarding API reference documentation as an API client:

   1. Update your zone from the Servers list at the top of the page.

   2. Click the lock at top right corner of your endpoint.

   3. Paste your access token in the Value field, and click Authorize.

   4. Click Try it out.

   5. Enter the Flexera org ID.

   6. Use this request body and paste it in.

      note

      Make sure to set the integrationId to cbi-oi-ocean. You should not need to change any other parameters.

      {
      "billIdentifier": "container-cost",
      "integrationId": "cbi-oi-ocean",
      "name": "container-cost",
      "params": {
          "displayName": "Container Cost Visibility",
          "vendorName": "Container Cost Visibility"
        }
      }

   7. Click Execute to initiate the POST request and then note the id in the response and keep it for later. The newly created bill connect should have an ID such as cbi-oi-ocean-{billIdentifier}.

note

You can connect one Flexera organization to one or more Spot organizations. To connect multiple Spot organizations, create a separate Common Bill Ingestion (CBI) connector for each Spot organization. The billIdentifier must be unique for each bill connect.

caution

The CBI connector created for this integration is exclusively managed by the Ocean-CCO integration. Do not manually upload or send data to this connector. Doing so will disrupt the automated data flow and may result in incomplete or inaccurate cost data in CCO.

What to do in Spot Ocean

1. Make sure you have the following information from What to do in Flexera One:

   1. flexeraBillConnectId (this is the ID from the CBI connector)
   2. flexeraOrganizationId
   3. flexeraRefreshToken

2. Make sure to attach the Organization Admin permission policy to your Spot user.

3. Get your Spot API permanent token.

4. Locate and note down your Spot organization ID.

5. Call the API endpoint for onboarding.

   Follow the request format defined in the API.

note

After you complete onboarding, cost and usage data will appear in the Flexera One CCO UI the following day. The most recent data available will always reflect the previous day.

Kubernetes Tag Dimensions in Flexera One CCO UI

Tag Dimensions are used to expose the Kubernetes context from bill data. They can be added in the Flexera One CCO UI as described in Tag Dimensions.

Create these dimensions or add Tag Keys to existing ones.

Display Name	Tag Key
Kubernetes Namespace	oc-namespace
Kubernetes Cluster	oc-cluster
Kubernetes Node Cloud Provider Id	oc-provider-id
Kubernetes Controller	oc-controller
Kubernetes Pod Id	oc-pod
Kubernetes Controller Kind	oc-controller-kind
Kubernetes Node	oc-node