Development Cluster Configuration: Difference between revisions
Jump to navigation
Jump to search
DrEdWilliams (talk | contribs) mNo edit summary |
DrEdWilliams (talk | contribs) mNo edit summary |
||
| Line 10: | Line 10: | ||
|- | |- | ||
| NVIDIA device plugin || || https://github.com/NVIDIA/k8s-device-plugin || || | | NVIDIA device plugin || || https://github.com/NVIDIA/k8s-device-plugin || || | ||
|- | |- | ||
| K8Dash Dashboard || k8s-admin || || 10.0.0.200 || | | K8Dash Dashboard || k8s-admin || || 10.0.0.200 || | ||
Revision as of 22:27, 15 August 2021
The Development cluster is deployed using K3s - Kubernetes Simplified.
These packages form the basic functionality of the development cluster. The packages need to preserve the IP address assignments.
Scripts & config files are checked into gitlab under the Kubernetes group project listed.
| activity | gitlab | script/procedures/config | IP | hostname(s) |
|---|---|---|---|---|
| NVIDIA device plugin | https://github.com/NVIDIA/k8s-device-plugin | |||
| K8Dash Dashboard | k8s-admin | 10.0.0.200 | ||
| GitLab - Helm deployment | Kubernetes/gitlab | kubernetes/gitlab/helm | 10.0.0.203 | gitlab.dev.williams.localnet |
Storage
The production cluster uses Rook/Ceph for its persistent storage. The storage components are arranged:
| component | system | location | storage | size |
|---|---|---|---|---|
| Storage Server | storage1 | /work | local 5x4TB drives | 20TB (ceph) |