centralize apiVersion for CAPI resources

Summary

We use some CAPI resources both in sylva-core (for healthchecks) and in sylva-capi-cluster:

  • Cluster
  • MachineDeployment
  • COntrolPlane
  • MachineTemplate
  • DataTemplate
  • ...

The improvement consists to store in the new sylva-library those apiVersions and define a named template to provide the apiVersion based on the kind of the desired resource

Benefits:

  • keep apiVersions consistent between Helm Chart
  • easier maintenance, if upgrade needed

related references

Assignee Loading
Time tracking Loading