Summary
All micromize configuration is via CLI flags (--enforce, --verbose). Production deployments need richer configuration options.
What's Needed
Design and implement configuration file support:
Config File Format
YAML config file (e.g., /etc/micromize/config.yaml):
enforce: true
verbose: false
logLevel: info
gadgets:
fs-restrict:
enabled: true
params:
# gadget-specific params
cap-restrict:
enabled: true
ptrace-restrict:
enabled: false
exclusions:
images:
- "monitoring-agent:*"
- "log-collector:*"
namespaces:
- kube-system
Implementation
- Use Viper (already have Cobra) for config file loading
- Support config file path via
--config flag
- CLI flags should override config file values
- Consider ConfigMap mounting in Kubernetes
Files
cmd/micromize/root.go
charts/micromize/templates/daemonset.yaml
Summary
All micromize configuration is via CLI flags (
--enforce,--verbose). Production deployments need richer configuration options.What's Needed
Design and implement configuration file support:
Config File Format
YAML config file (e.g.,
/etc/micromize/config.yaml):Implementation
--configflagFiles
cmd/micromize/root.gocharts/micromize/templates/daemonset.yaml