Research Feasibility to Remove the Lieutenant API Completely

[tobru]

Context

A discussion came up if the Lieutenant API is actually an added value to Project Syn. All information needed could also be acquired by directly accessing the Kubernetes API and the CRDs of Lieutenant Operator. The API adds some additional features and does not only do data conversion from one into another format, this needs to be taken in to consideration while working on this issue.

Task

1. Create a list of additional functionality the API adds on top of CRUD to Lieutenant Operator CRDs and list options to replace this functionality by other means.
2. List changes needed to Commodore and other tools currently using the Lieutenant API.
3. Write down other implications of removing the API: What would we have to do?

[tobru]

Fleet Manager is a bit similar and they write:

The Fleet manager is a set of Kubernetes controllers running in any standard Kubernetes cluster. The only API exposed by the Fleet manages is the Kubernetes API, there is no custom API for the fleet controller.

And also

The only requirement is the cluster agent needs to be able to communicate with the Kubernetes API of the cluster running the Fleet manager.

[srueg]

Interesting to see how fleet solves the problem of having a "bootstrap token": https://fleet.rancher.io/cluster-tokens/