Enhancing the Helm prompt #18
Description
Our current Helm prompt lacks the depth required to generate a complete and robust Helm structure with all necessary template resources. A typical application often requires defining multiple interdependent resources, such as services, persistent storage, environment-specific configuration, secrets, and autoscaling policies. The prompt should first capture specific user requirements, such as expected replica counts, custom environment variables, database configurations, ingress rules, and resource constraints for CPU and memory. This approach ensures that the Helm templates accurately reflect the application’s configuration, dependencies, and deployment preferences