Monitor owned datacenter activity
Go to file
2025-02-27 17:01:07 +01:00
conf glory kube conn 2025-02-14 11:09:31 +01:00
controllers Uniformisation and verification of admiralty link with nodes + token 2025-02-27 17:00:36 +01:00
docs First proposition of sequence for admiralty executions/setup 2025-02-27 16:53:39 +01:00
infrastructure Uniformisation and verification of admiralty link with nodes + token 2025-02-27 17:00:36 +01:00
routers add admiralty to routers 2025-02-27 17:01:07 +01:00
swagger glory kube conn 2025-02-14 11:09:31 +01:00
.gitignore licence update and git ignore for binary added 2024-09-05 09:38:18 +02:00
datacenter.json upgrade main.go (oc-lib refactor) 2024-09-04 17:32:30 +02:00
docker_datacenter.json oclib update + controller adjustment 2025-02-18 15:05:47 +01:00
docker-compose.base.yml Init OC-DATACENTER 2024-08-13 11:17:09 +02:00
docker-compose.yml traefik 2025-02-19 12:05:43 +01:00
Dockerfile glory kube conn 2025-02-14 11:09:31 +01:00
go.mod traefik 2025-02-19 12:05:43 +01:00
go.sum go.sum pb 2025-02-19 14:04:32 +01:00
LICENSE.md license update 2024-10-03 09:40:38 +02:00
main.go Merge branch 'feature/namespace' 2025-02-17 09:28:34 +01:00
Makefile modifications for k8s integration 2025-01-10 21:21:58 +01:00
README.md Merge remote-tracking branch 'origin/master' into feature/admiralty 2025-02-19 14:40:56 +01:00

oc-datacenter OpenCloud shared service.

Manages user shared

To build :

bee generate routers
bee run -gendoc=true -downdoc=true

If default Swagger page is displayed instead of tyour api, change url in swagger/index.html file to :

url: "swagger.json"

Note on particular process :

  • 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

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