From f69e9bf2fafde382ac3a03bb8142e7f49ac4cc42 Mon Sep 17 00:00:00 2001 From: pb Date: Wed, 19 Feb 2025 12:28:48 +0100 Subject: [PATCH] Started the implementation of new routes for admiralty --- README.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/README.md b/README.md index 4e4717e..5d59221 100644 --- a/README.md +++ b/README.md @@ -48,3 +48,21 @@ To set up a target Admiralty needs to associate a `secret` which contains an edi Once the Target is set the remote cluster appears in the output of `kubectl get nodes` under the name `admiralty---*` **TODO** : We might need a way to test if an IP is associated to an admiralty target + +# Docker Kube Settings + +Set up your base64 key from your ~/.kube/config. +Don't forget to set up your external IP in docker_datacenter.json +## 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---*` + +**TODO** : We might need a way to test if an IP is associated to an admiralty target