chore: add stats app values

[baktun14]

Summary by CodeRabbit

• New Features
  • Added stats-web application to the deployment pipeline, now available in production (stats.akash.network) and staging (stats-beta.akash.network) environments.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request adds support for deploying a new "stats-web" application through the reusable Kubernetes deployment workflow in GitHub Actions, along with environment-specific Helm configuration files for production and staging deployments.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/reusable-deploy-k8s.yml	Added "stats-web" to the list of deployable app options in the workflow_dispatch inputs
Helm Configuration Files .helm/stats-web-prod-values.yaml, .helm/stats-web-staging-values.yaml	Created two environment-specific Helm values files: production configuration with stats.akash.network hostname and staging configuration with stats-beta.akash.network hostname

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A stats-web takes flight on Helm's gentle wings,
Through workflows that dance and configurations that sing,
Production and staging both ready to gleam,
Akash's metrics now shine like a dream! ✨

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: add stats app values' is concise and directly relates to the main changes in the PR, which add Helm values files and configuration for the stats-web app.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c3ee8f0 and 11b3114.

📒 Files selected for processing (3)

• .github/workflows/reusable-deploy-k8s.yml
• .helm/stats-web-prod-values.yaml
• .helm/stats-web-staging-values.yaml

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-08-12T13:52:38.708Z

Learnt from: stalniy
Repo: akash-network/console PR: 1800
File: apps/deploy-web/next.config.js:163-165
Timestamp: 2025-08-12T13:52:38.708Z
Learning: In the Akash Console project, akashnetwork/env-loader is used at the top of next.config.js files to automatically load environment variables from env/.env files into process.env. SENTRY_ORG and SENTRY_PROJECT are stored as public configuration values in apps/deploy-web/env/.env and are loaded this way, while only SENTRY_AUTH_TOKEN is handled as a GitHub secret in workflows.

Applied to files:

• .helm/stats-web-prod-values.yaml
• .helm/stats-web-staging-values.yaml

📚 Learning: 2025-08-12T13:52:38.708Z

Learnt from: stalniy
Repo: akash-network/console PR: 1800
File: apps/deploy-web/next.config.js:163-165
Timestamp: 2025-08-12T13:52:38.708Z
Learning: In the Akash Console project, SENTRY_ORG and SENTRY_PROJECT are stored as public configuration values in apps/deploy-web/env/.env file and loaded by akashnetwork/env-loader, not as GitHub secrets. Only SENTRY_AUTH_TOKEN should be handled as a secret.

Applied to files:

• .helm/stats-web-prod-values.yaml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (3)

.github/workflows/reusable-deploy-k8s.yml (1)

27-27: LGTM! stats-web successfully added to deployable apps.

The addition integrates correctly with the existing workflow logic, which will:

• Construct the values file path as .helm/stats-web-{environment}-values.yaml
• Reference the Helm chart as akash/stats-web
• Apply the deployment to the specified environment

.helm/stats-web-prod-values.yaml (1)

1-3: Verify production infrastructure readiness.

The production Helm values configuration is consistent with the staging configuration. Please confirm:

• DNS record for stats.akash.network is configured with appropriate production-grade ingress/certificate setup
• The minimal configuration is appropriate for production workloads (no additional resource limits, replica counts, or environment-specific settings needed)
• Production deployment has been tested in staging environment first

.helm/stats-web-staging-values.yaml (1)

1-3: Infrastructure is properly configured for stats-web staging deployment.

The Helm chart akash/stats-web is available in the akash-network/helm-charts repository and is used via the Helm deployment workflow. The staging values with deploymentEnv: staging and hostName: stats-beta.akash.network are correctly configured. The minimal values configuration is sufficient as the deployment process automatically supplies the appVersion parameter during the Helm upgrade command.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}