Repository navigation
[epic] ClusterExtension parameters passed through to templating engine #381
Description
Activity
- converted this from a draft issue
on Aug 31, 2023 - changed the title
[-]Operator parameters passed through to BundleDeployment[/-][+]Extension parameters passed through to App[/+]on Jan 24, 2024 See #612
In order to keep watch namespace configuration out of the Extension API as a first class field, I think we should define our own schema/values that account for watch namespaces and subscription config, and put that in scope for the initial registry+v1 bundle support in Extension+App
- changed the title
[-]Extension parameters passed through to App[/-][+][epic] Extension parameters passed through to templating engine[/+]on Apr 4, 2024 - changed the title
[-][epic] Extension parameters passed through to templating engine[/-][+][epic] ClusterExtension parameters passed through to templating engine[/+]on Apr 4, 2024 - added and removed
on Oct 29, 2024 4 remaining items
Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.
This issue has been closed due to inactivity.
Fyi we have an RFC now for this: https://docs.google.com/document/d/18O4qBvu5I4WIJgo5KU1opyUKcrfgk64xsI3tyXxmVEU/edit?tab=t.0#heading=h.x3tfh25grvnv
the work for which has started #2454.
The upcoming work is not being tracked in issues but I'm hoping to remember to come back here and update when the work is completed and the feature is available for anyone who's interested in this feature.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Define a way for the content author to specify what parameters are user-facing, along with a way to plumb them through from the ClusterExtension spec the templating engine
Example use case: I publish a bundle for my Widget app, and the only knobs I want users to be able to tweak are replica count and logging verbosity.
This either needs to accommodate v0 subscription config settings (e.g. env vars, node selector, etc.), or we need a different mechanism for that.
RFC: Doc