{"id":19291750,"url":"https://github.com/hirosystems/charts","last_synced_at":"2025-11-14T17:11:06.351Z","repository":{"id":50486717,"uuid":"517684010","full_name":"hirosystems/charts","owner":"hirosystems","description":"Hiro Systems Helm Charts","archived":false,"fork":false,"pushed_at":"2025-01-21T21:28:11.000Z","size":416,"stargazers_count":3,"open_issues_count":2,"forks_count":1,"subscribers_count":6,"default_branch":"main","last_synced_at":"2025-02-22T19:50:01.084Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Smarty","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/hirosystems.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-07-25T13:48:12.000Z","updated_at":"2025-01-21T21:28:14.000Z","dependencies_parsed_at":"2023-02-01T06:25:14.517Z","dependency_job_id":"f66cc70b-f5ef-48cc-b356-64fc2ce0e631","html_url":"https://github.com/hirosystems/charts","commit_stats":null,"previous_names":[],"tags_count":135,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hirosystems%2Fcharts","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hirosystems%2Fcharts/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hirosystems%2Fcharts/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hirosystems%2Fcharts/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/hirosystems","download_url":"https://codeload.github.com/hirosystems/charts/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240395747,"owners_count":19794572,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-09T22:27:45.063Z","updated_at":"2025-11-14T17:11:06.346Z","avatar_url":"https://github.com/hirosystems.png","language":"Smarty","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Hiro Systems Helm Charts\n\nThis repository contains Helm charts for deploying Hiro Systems infrastructure components, including the Stacks blockchain node and associated services.\n\n## ⚠️ Important Notice\n\n**These Helm charts are primarily designed and optimized for Hiro's internal infrastructure.** While they are publicly available, they are:\n\n- Highly tailored to Hiro's specific deployment environment\n- Not intended as authoritative guides for running Hiro software\n- Not guaranteed to account for all deployment scenarios\n\n**If you're experiencing performance issues**, it's likely due to using default configurations without proper tuning for your specific environment.\n\n## Available Charts\n\n- **stacks-blockchain** - Deploys a Stacks blockchain node\n- **stacks-blockchain-api** - Deploys the Stacks Blockchain API service\n- Additional supporting services and components\n\n## Prerequisites\n\n- Kubernetes 1.19+\n- Helm 3.x\n- Understanding of Kubernetes resource management and configuration\n- Familiarity with the Stacks blockchain architecture\n\n## Getting Started\n\n### Adding the Repository\n\n```bash\nhelm repo add hirosystems https://hirosystems.github.io/charts\nhelm repo update\n```\n\n### Installing Charts\n\n```bash\n# Install with default values (NOT recommended for production)\nhelm install my-stacks-node hirosystems/stacks-blockchain\n\n# Install with custom values (RECOMMENDED)\nhelm install my-stacks-node hirosystems/stacks-blockchain -f my-values.yaml\n```\n\n## ⚡ Performance Considerations\n\n**Chart configuration does not determine application performance.** Performance depends on:\n\n1. **Resource Allocation**\n   - CPU and memory limits/requests\n   - Storage class and IOPS\n   - Network bandwidth\n\n2. **Application Configuration**\n   - Node settings and parameters\n   - Cache sizes\n   - Connection pools\n   - Indexing strategies\n\n3. **Infrastructure**\n   - Node types and specifications\n   - Cluster networking setup\n   - Storage backend performance\n\n### Tuning for Production\n\nIf you're deploying these charts in production, you **MUST**:\n\n1. **Review and modify resource requests/limits** based on your workload\n2. **Configure application-specific settings** for optimal performance\n3. **Use appropriate storage classes** with sufficient IOPS\n4. **Monitor and adjust** based on actual usage patterns\n\nExample custom values for production:\n\n```yaml\n# my-values.yaml\nresources:\n  requests:\n    memory: \"8Gi\"\n    cpu: \"4\"\n  limits:\n    memory: \"16Gi\"\n    cpu: \"8\"\n\npersistence:\n  size: 500Gi\n  storageClass: fast-ssd\n\nconfig:\n  # Application-specific tuning parameters\n  # Consult Stacks documentation for optimal values\n  cache_size: 4096\n  max_connections: 1000\n  # ... other configuration\n```\n\n## Your Mileage May Vary (YMMV)\n\nSince these charts are optimized for Hiro's infrastructure:\n\n- Network policies may reference internal services\n- Default values assume specific cluster configurations\n- Some features may require Hiro-specific resources\n- Monitoring and observability integrations may not work out-of-the-box\n\n**Experienced Kubernetes operators** can adapt these charts by:\n- Overriding values extensively\n- Modifying templates if necessary\n- Understanding the underlying application requirements\n\n## Troubleshooting\n\n### Common Issues\n\n1. **Poor Performance**\n   - Check resource allocation\n   - Review application logs for bottlenecks\n   - Ensure storage performance meets requirements\n   - Verify network connectivity and latency\n\n2. **Deployment Failures**\n   - Verify all dependencies are met\n   - Check for namespace-specific resources\n   - Review security contexts and permissions\n\n3. **Connection Issues**\n   - Confirm service discovery is working\n   - Check network policies\n   - Verify ingress/load balancer configuration\n\n## Documentation\n\nFor comprehensive information about running Stacks infrastructure:\n\n- [Stacks Documentation](https://docs.stacks.co)\n- [Hiro Developer Docs](https://docs.hiro.so)\n- [Stacks Blockchain Configuration](https://docs.stacks.co/docs/nodes-and-miners)\n\n## Support\n\n- **For Helm chart issues**: Open an issue in this repository\n- **For application-specific questions**: Consult the official documentation\n- **For performance tuning**: Review the Stacks performance tuning guide\n\n## Contributing\n\nWe welcome contributions that:\n- Improve compatibility across different environments\n- Add better documentation and examples\n- Fix bugs or security issues\n\nPlease ensure any changes maintain backward compatibility with Hiro's infrastructure needs.\n\n**Remember**: These charts are tools to help deploy the software, not prescriptive guides on how to run it. Successful deployment requires understanding both Kubernetes and the Stacks blockchain ecosystem.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhirosystems%2Fcharts","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fhirosystems%2Fcharts","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhirosystems%2Fcharts/lists"}