Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add configuration file support #56

@dorser

Description

@dorser

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestresearchResearch and design decisions needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions