Ivan Mikheykin
Ivan Mikheykin
Discovery process is now performed statically: it calculates enable state for all modules at once. The better way is to calculate first enabled module and run it, then calculate next...
Allow modules to have a public contract: - create a `public` section with keys named as modules - this section can be patched from global and module hooks Or just...
The module can have no templates directory and have dependencies in Chart.yaml. The problem is that addon-operator construct values for helm in this form: ``` global: globalKey1: ... globalKey2: ......
**Is your feature request related to a problem? Please describe.** - No Helm3 info in MODULES.md, "Tiller" header is misleading. - No info about purge releases at the start. **Describe...
There is a myriad of map[string]string initialized and passed between layers. The upper-level code should know which labels to pass to the lower-level methods and lower-level has no access to...
https://github.com/flant/shell-operator/issues/63
A global hook can change module section in `configmap/addon-operator` and this leads to run an `enabled` script. It is OK when all global `onStartup` and `kubernetes.Synchronization` hooks are already run...
Values are parameters for each module. CRD can be used to define them instead of yaml-strings in a ConfigMap. - validation - each module defines own CRD - addon-operator defines...
All values are now in cm/addon-operator. That is bad for sensitive data. Support Vault or something like this.