Best Practices
While the key to Planeo is iteration, it can be helpful to know some best practices around the design of your Planeo resources
Avoid static port mappings unless you really need them. The more ports you have mapped statically to common numbers, the higher a chance you have of a port conflict
Create multiple Planeo Templates for each Helm chart to fit key use cases. You can define custom static values files with different settings for your Helm charts and expose specific and potentially distinct arguments to the Stack level. This allows your team to minimize Stack level configuration.
Leverage Planeobot to edit values templates. It has context on the default Helm values file and can help you discover and set key parameters.
Last updated