Backstage Kubernetes Plugin No Workload Data

In this tutorial, you'll learn about Backstage Kubernetes Plugin No Workload Data. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

Kubernetes resources for your services are not visible in the Backstage Kubernetes plugin.

Wrong ❌

# app-config.yaml
kubernetes:
  # Missing cluster locator configuration
  serviceLocatorMethod:
    type: 'multiTenant'
  clusterLocatorMethods:
    - type: 'config'
      clusters: []

Wrong Output

Kubernetes plugin in Backstage shows:
"No workloads found. Your clusters may not be configured or accessible."
Entity page shows "Kubernetes" tab with empty list.

Right ✅

# app-config.yaml
kubernetes:
  serviceLocatorMethod:
    type: 'multiTenant'
  clusterLocatorMethods:
    - type: 'config'
      clusters:
        - name: production
          url: https://prod-cluster.example.com:6443
          authProvider: serviceAccount
          serviceAccountToken: ${K8S_SA_TOKEN}
          skipTLSVerify: false
          dashboardUrl: https://k8s-dashboard.example.com
          dashboardApp: standard
    - type: 'catalog'
      # Discovers clusters from catalog entities with kubernetes annotations

Right Output

Kubernetes plugin displays:
Production cluster:
  my-service (Deployment) - 3/3 pods ready
  my-service-db (StatefulSet) - 1/1 pods ready
  CPU: 45% | Memory: 62%

Prevention

• Configure at least one cluster in the Kubernetes.clusterLocatorMethods section.
• Ensure the service account token has permissions to list pods, deployments, and services.
• Add the Kubernetes annotation to catalog entities: backstage.io/Kubernetes-namespace.
• Use the catalog-based locator for dynamic cluster discovery across environments.
• Verify network connectivity from Backstage to the Kubernetes API server endpoint.

DodaTech applies similar defensive patterns across Doda Browser, DodaZIP, and Durga Antivirus Pro infrastructure for production reliability.

Common Mistakes with Kubernetes plugin

1. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
2. Using head and tail instead of pattern matching, causing runtime errors on empty lists
3. Forgetting that lazy evaluation defers computation until the value is forced, causing space leaks with unevaluated thunks

These mistakes appear frequently in real-world BACKSTAGE code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

This quick fix is part of the DodaTech infrastructure engineering series. Learn more at DodaTech tutorials.