Kestra Enterprise helm chart

[paulgrainger85]

Feature description

Please add a helm chart that deploys a fully functional Kestra Enterprise instance.

This should deploy Kestra in the following way

• Distributed mode with resources/limits set according to our minimum recommendations: https://kestra.io/docs/performance/sizing-and-scaling-infrastructure#baseline-infrastructure-recommendations
• Deploy a Postgres pod and use this for the datasource. Show the datasource configuration
• Deploy alternative to Minio for internal storage
• OIDC configuration set so customers only need to input the client secret and issuer URL
• Placeholders for Enterprise license ID, key and fingerprint
• Encryption key set with valid encryption key for demonstration
• JDBC secret manager with valid secret key
• Set super admin username and password. if possible can this be shown to use a secret?
• Add mail server placeholder https://kestra.io/docs/configuration#configuring-a-mail-server
• Add AI settings placeholder
• Single worker group (aware that this needs to be configured in Kestra first, but we should show the configuration)
• Setting up Kestra URL
• Add ample livelenss probes and best practices
• Add opinionated placeholder for default roles
• Placeholder for advanced db connection params
• Opinionated JDBC queue cleaner
• SSL setup and trust-all - this needs larger attention
• Placeholder for loggers - important for troubleshooting later
• (optional) plugin default example

---

edit

• primary goal is for PoC use / not production
• t.b.d. if helm chart or simple manifest

[xdatanomad]

Additional requirements:

• Setting up Kestra URL
• Add ample livelenss probes and best practices
• Add opinionated placeholder for default roles
• Placeholder for advanced db connection params
• Opinionated JDBC queue cleaner
• SSL setup and trust-all - this needs larger attention
• Placeholder for loggers - important for troubleshooting later
• (optional) plugin default example

IMPORTNAT: examples of how to use .env or $ENV for loading secrets and config params.

[gperreymond]

are you sure for those points:

• Alternative to minio is discussed here: Replace Minio helm charts that #182

• SSL setup and trust-all - this needs larger attention
  we will deploy in kubernetes, https termination at pod level is at minimum not mandatory, at maximum can cause more problems/use_cases than exeptated.