Skip to main content
Version: 1.17

Billing Workload ID

Business Critical Plan Feature

This is a Business Critical Plan feature. For more information, see our pricing plans or contact our sales team.

Prerequisites​

To set up a workload-identity, you'll need:

  • A self-hosted Space cluster
  • Administrator access in your cloud provider
  • Helm and kubectl

About the billing component​

The vector.dev component handles billing metrics collection in spaces. It stores account data in your cloud storage. By default, this component runs in each control plane's host namespace.

Configuration​

Verify your configuration​

After you apply the configuration use kubectl to verify the service account has the correct annotation:

kubectl get serviceaccount vector -n ${YOUR_CONTROL_PLANE_NAMESPACE} -o yaml

Verify the vector pod is running:

kubectl get pods -n ${YOUR_CONTROL_PLANE_NAMESPACE} | grep vector

Restart workload​

kubectl rollout restart deployment vector

Use cases​

Using workload identity authentication for billing eliminates the need for static credentials in your cluster as well as the overhead of credential rotation. These benefits are helpful in:

  • Resource usage tracking across teams/projects
  • Cost allocation for multi-tenant environments
  • Financial auditing requirements
  • Capacity billing and resource optimization
  • Automated billing workflows

Next steps​

Now that you have workload identity configured for the billing component, visit the Billing guide for more information.

Other workload identity guides are: