Started the implementation of new routes for admiralty
This commit is contained in:
parent
293b52da4c
commit
f69e9bf2fa
18
README.md
18
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-<namespace>-<target name>-*`
|
||||
|
||||
**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-<namespace>-<target name>-*`
|
||||
|
||||
**TODO** : We might need a way to test if an IP is associated to an admiralty target
|
||||
|
Loading…
Reference in New Issue
Block a user