Authentication:
- Keycloak: deployed using plain YAMLs.
- Admin console URL: https://eucaim-node.i3m.upv.es/auth
- User profile URL: https://eucaim-node.i3m.upv.es/auth/realms/EUCAIM-NODE/account
- OIDC discovery endpoint: https://eucaim-node.i3m.upv.es/auth/realms/EUCAIM-NODE/.well-known/openid-configuration
- Deployment details in the keycloak directory
Security Policy Management System:
- Kyverno: deployed using the Helm Chart. Pod Security Standard Policy: baseline. Other applied policies availables here.
Repository for container images and helm charts:
- Harbor: deployed using the official helm chart.
- Web UI URL: https://harbor.eucaim-node.i3m.upv.es
- Deployment details in the harbor directory
Interact with Kubernetes:
- Kubeapps: deployed using plain YAMLs.
- URL: https://eucaim-node.i3m.upv.es/apps/
- Deployment details in the kubeapps directory
- Kubernetes Dashboard: deployed using the official helm chart.
- URL: https://eucaim-node.i3m.upv.es/apps/k8s-dashboard/
- Deployment details here
Access to interactive applications:
- Guacamole: deployed using the helm chart. URL: https://eucaim-node.i3m.upv.es/guacamole/
Ingestion service and datalake explorer:
- QP-Insights: deployed using the helm chart.
Dataset administration and Traceability System:
- Dataset-service: deployed using plain YAMLs.
- URL: https://eucaim-node.i3m.upv.es/dataset-service
- Deployment details in the dataset-service directory
- Source code: https://github.com/chaimeleon-eu/dataset-service
- DSWS K8s Operator: deployed using the Helm Chart.
- Desktops-cleaner: deployed using the Helm Chart.
- Tracer Service.
Authentication proxy:
- OAuth2-proxy: deployed using the helm chart. URL: https://eucaim-node.i3m.upv.es/oauth2p/
Python packages repository:
- Devpi: deployed using plain YAMLs
- URL (Platform internal only): http://devpi-service.package-repos-proxy:3141
- Deployment details in the devpi directory
Federated Computation:
- FEM client: deployed using plain YAMLs. URL: not publicly accessible
First of all, go to the infrastructure recipes to create the infrastructure (a Kubernetes cluster) in a cloud provider
and deploy some infrastructure core services: infrastructure-recipes
Those are the basic components deployed:
- Kubernetes cluster with cilium network and nvidia GPU operator
- Ceph storage provisioner (ceph-csi)
- Ingress nginx
- Cert-manager
- Kubernetes dashboard
Now the platform core services can be deployed in the following order to properly satisfy dependencies:
| Name | Dependecies (not hard dependency, just required for some function) | Deployment details |
|---|---|---|
| Keycloak | keycloak directory | |
| Harbor | Depends on Keycloak | harbor directory |
| Devpi | Depends on Harbor | devpi directory |
| Kubeapps | Depends on Keycloak, Harbor, (DSWS K8s Operator) | kubeapps directory |
| Access to K8s dashboard with OIDC | Depends on Keycloak, Kubeapps | kubernetes-dashboard-oidc-access directory |
| Tracer-service | Depends on Keycloak, Harbor | |
| Guacamole | Depends on Keycloak, Harbor | guacamole directory |
| Dataset-service | Depends on Keycloak, Harbor, (Tracer), (Kubeapps), (Guacamole) | dataset-service directory |
| QP-Insights | Depends on Keycloak, Harbor, (Dataset-service) | qp-insights directory |
| DSWS K8s Operator | Depends on Keycloak, Harbor, Dataset-service, Guacamole | dsws-operator |
| Jobman-service | Depends on Keycloak, Harbor, DSWS K8s Operator | |
| Desktops-cleaner | Depends on Keycloak, Harbor, Guacamole | desktops-cleaner directory |
| FEM client | Depends on Keycloak, Harbor, Jobman | fem-client |
Finally... extra-configurations