Problem description (if applicable)
Currently, k8s applier code is a part of airshipctl core functionality. However, this implementation is bulky, contains a lot of useless abstractions and imposes on us many restrictions and inconveniences. Among them:
dependencies in airshipctl core functionality
impossible to use or choose different backends for apply
no appropriate log integration with k8s libs (lack of debug information of apply process)
no possibility of granulated upgrade of cli utils dependencies
Problem description (if applicable) Currently, k8s applier code is a part of airshipctl core functionality. However, this implementation is bulky, contains a lot of useless abstractions and imposes on us many restrictions and inconveniences. Among them:
Proposed change Use KRM function for apply process. Proposed change - https://review.opendev.org/c/airship/airshipctl/+/809291
Potential impacts None.