Add helm chart guide #1751
Add helm chart guide #1751
Conversation
Enhance the EKS deployment documentation with a comprehensive production deployment section using Helm charts. This addition provides: - Production-ready deployment approach with high availability - Integration with AWS services (RDS, S3, Route53, ACM) - Quick start guide with installation steps - Helm-specific uninstall instructions - Reference to detailed Helm chart documentation This complements the existing basic deployment guide by offering an enterprise-grade option for production environments. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Add Helm Chart deployment guide for EKS
There was a problem hiding this comment.
Pull request overview
This PR adds comprehensive Helm chart deployment documentation to the AWS EKS guide, providing production-ready deployment instructions as an alternative to the basic manifest-based deployment. The addition includes a new major section covering Helm-based deployments with detailed prerequisites, installation steps, and references to full documentation in the docker-zoo repository.
Key changes:
- Added "Production Deployment with Helm Chart" section with benefits, prerequisites, and step-by-step installation instructions
- Updated uninstall section to distinguish between basic and Helm-based deployments
- Included reference link to the complete Helm chart documentation in the docker-zoo repository
| - `admin-role.aclpolicy` - Admin ACL permissions | ||
| - `realm.properties` - Local user accounts | ||
|
|
There was a problem hiding this comment.
The instructions reference configuration files 'admin-role.aclpolicy' and 'realm.properties' that need to be prepared, but provide no guidance on what these files should contain, where to obtain templates, or examples. Users following this guide will not know how to create these required files. Consider adding links to example files in the docker-zoo repository or providing minimal working examples.
| - `admin-role.aclpolicy` - Admin ACL permissions | |
| - `realm.properties` - Local user accounts | |
| - `admin-role.aclpolicy` - Admin ACL permissions. Save a file named `admin-role.aclpolicy` with at least the following minimal content (suitable for a basic admin user in a test environment): | |
| ```yaml | |
| description: Admin role with full access | |
| context: | |
| project: '.*' | |
| for: | |
| resource: | |
| - equals: | |
| kind: job | |
| allow: [read, create, update, delete, run, kill] | |
| job: | |
| - match: | |
| name: '.*' | |
| allow: [read, run, kill, create, update, delete] | |
| adhoc: | |
| - allow: [read, run, kill] | |
| by: | |
| group: admin | |
| ``` | |
| For additional or more restrictive ACL examples, see the Helm chart configuration in the docker-zoo repository: | |
| https://github.com/rundeck/docker-zoo/tree/master/kubernetes/helm/rundeckpro | |
| - `realm.properties` - Local user accounts. Save a file named `realm.properties` with at least one admin user, for example: | |
| ```properties | |
| admin:admin,user,admin | |
| ``` | |
| In this example, the username is `admin`, the password is `admin`, and the user belongs to the `user` and `admin` groups. Change the password and groups to match your security requirements. |
There was a problem hiding this comment.
It is preferable to use a link to the documentation, to avoid cluttering this guide with other examples, making it more confusing.
1 participant
Add helm chart guide
Add link to the full instructions available in the docker-zoo