Deploying Backstage on Kubernetes with the Helm Chart: The Infrastructure-First Guide

The provided YAML configurations and troubleshooting steps are crucial for setting up Backstage, a developer portal framework, in both local development and production environments. Below is an explanation of the key sections:

1. Helm Values Configuration

Startup Probes Timing Issue:

When deploying Backstage using Helm charts, one common issue encountered is related to startup probes timing out before the application starts fully. This can be addressed by adjusting the initialDelaySeconds for the startup probe in your Helm values file.

yaml
 
1backstage:
2  backstage:
3    livenessProbe:
4      initialDelaySeconds: 120 # Adjust based on actual startup time

2. Authentication Configuration

Local Development Mode:

For local development, you can use the guest auth provider to bypass authentication requirements temporarily:

yaml
 
1backstage:
2  backstage:
3    appConfig:
4      auth:
5        providers:
6          guest:
7            dangerouslyAllowOutsideDevelopment: true

This setup allows all users to access Backstage without needing to authenticate.

Production Mode with GitHub OAuth:

In production, it's recommended to set up an OAuth provider like GitHub. This requires storing the client ID and secret securely:

yaml
 
1backstage:
2  backstage
3
4[Read the full article at DEV Community](https://dev.to/sodiqjimoh/deploying-backstage-on-kubernetes-with-the-helm-chart-the-infrastructure-first-guide-mf3)
5
6---
7
8**Want to create content about this topic?** [Use Nemati AI tools](https://nemati.ai) to generate articles, social posts, and more.