Started the implementation of new routes for admiralty

README.md

@@ -12,4 +12,18 @@ If default Swagger page is displayed instead of tyour api, change url in swagger
     url: "swagger.json"
 
 Note on particular process :
-- set a bookin delete all related workflow booking before creating new ones. (no update of existing ones)
+- set a bookin delete all related workflow booking before creating new ones. (no update of existing ones)
+
+## Admiralty
+
+The routes in /admiralty will trigger actions on the DC's Kubernetes API to retrieve information on Admiralty resources.
+
+### Targets
+
+Remote clusters that can be used by Admiralty to delegate pods.
+
+To set up a target Admiralty needs to associate a `secret` which contains an edited version of the target's `kubeconfig`. 
+
+Once the Target is set the remote cluster appears in the output of `kubectl get nodes` under the name `admiralty-<namespace>-<target name>-*`
+
+**TODO** : We might need a way to test if an IP is associated to an admiralty target