KNEL/KNELCloudronPackages
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
6e3f60cd9d3e9e4c4c08892c05e3f45984c72787
KNELCloudronPackages/collab/questions/apisix-v1.md

807 B
Raw Blame History

APISIX Packaging – Clarifying Questions

  1. Which upstream release/tag of Apache APISIX should we target for this first Cloudron package?
  2. Are there existing Cloudron add-ons (e.g., PostgreSQL, Redis, MySQL, etc.) that you want us to prefer or avoid for APISIX, given its components (dashboard, etcd, control plane)?
  3. Do you expect the initial package to ship with the APISIX Dashboard enabled, or should we scope it to the core gateway only?
  4. Are there organization-specific runtime constraints (CPU/memory limits, required domains/subpaths, TLS expectations) that we need to bake into the manifest from the start?
  5. Should we integrate any Known Element branding or default configuration (e.g., custom log formats, auth plugins) as part of the base package, or keep it stock upstream behavior?