RFC: Configuration File for Default Pod Flavors Based on Metadata

[dciangot]

Summary

We should implement a configuration file mechanism that allows defining default flavors for pods that match certain metadata criteria. This would enable automatic flavor assignment based on pod labels, annotations, or other metadata without requiring explicit flavor specification in each pod spec.

Use Cases

• Automatically assign CPU/memory flavors based on workload type labels (e.g., workload-type: gpu-intensive). See RFC: Define a policy for requirements to plugins for PVC custom management and defaults interLink#359
• Set default flavors for specific teams/VO

Proposed Implementation

The configuration could include:

• Metadata selectors (annotations, token claim, resource request)
• Corresponding default flavor specifications
• Priority/precedence rules when multiple selectors match
• Fallback behavior when no selectors match

Questions for Discussion

1. What configuration format should we use? (YAML, JSON, TOML?)
2. Where should the configuration file be located and how should it be loaded?
3. Should this be a client-cluster-level or general configuration?
4. How should we handle conflicts when multiple rules match the same pod?
5. What metadata fields should be supported for matching (labels, annotations, namespace, etc.)?

Looking forward to feedback and suggestions on the design approach!