Introduce data inputs concept

[mikouaj]

Community Note

• Please vote on this issue by adding a 👍 reaction
  to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do
  not help prioritise the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

The goal is to introduce modularised inputs in a similar fashion as current outputs.
This will make the tool more extensible and configurable, especially that the number of inputs has a tendency to grow (we already have 3 different data sources). It will also make code architecture cleaner.

• Data Inputs: core #137
  • Introduce inputs interface in a dedicated package
  • Introduce inputs in a configuration / CLI
  • Extend cluster data model with a map[string]interface{} for input data storing
  • Introduce function to get data from all inputs for all clusters in a concurrent way and return extended cluster model
• Data inputs: Input aware policies #139
  • Enhance policy model with inputs
  • Add inputs to the existing policies
  • Filter policies based on configured inputs. This should happen on early stage, before inputs are fetched and policies evaluated
• Add simple REST input for demo purposes #145
• Migrate GKE GCP API client to the new input structure #142
• Migrate Kubernetes API client to the new input structure #143
• Migrate metrics GCP API to the new input structure #146
• Replace existing clients with new inputs
• Update the documentation

References

N/A