Best way of customizing OAS
During our last meeting we discussed how to properly customize OAS. Concerns were raised that we don't target tech-savy sysadmins as users but organisations with little tech skills or without an admin. However, some of our users might want to add their custom website (or other important resources) into prometheus monitoring i.e. Regarding the above question we could do a(nother?) personas session to come to a better understanding of possible use cases of OAS.
When it comes to customizing there are currently two different things to consider:
- Customizing resources deployed by OAS (i.e. extending/changing the prometheus config)
- Adding custom resources/helmreleases by flux (maybe a configurable second flux installation for custom resources might be useful)
Lets use this issue to discuss the best (and easiest) ways.
Todo
-
Allow custom extra values for helm charts !311 (merged) -
Allow extra_opts to get passed to flux helm install !303 (merged) -
Allow second, custom flux instance !313 (merged)
Edited by Varac