...
- Decide on cluster size. How many of each type of node?
- kubernetes etcd
- kubernetes master
- kubernetes compute
- kubernetes ingress
- gluster storage
- Allocate desired nodes with Ansible playbook. Nodes should now be online with Kubernetes running.Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-243
- Label all nodes with their associated role/type from aboveJira server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-251 - kubectl label nodes <nodeName> ndslabs-role=<nodeType>
- Deploy GlusterFS server Kubernetes service on nodes with ndslabs-role=storageJira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-223
- Deploy GlusterFS client Kubernetes service on nodes with ndslabs-role=computeJira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-223
- Deploy "default" Kubernetes LoadBalancer / Ingress rules for UI / API / cluster-wide services (i.e. TERRA toolserver)Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-214
- Deploy kube-system Kubernetes servicesJira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-244 - Grafana, dashboard, ELK, etc
- Depoy NDS Labs Kubernetes servicesJira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-238 - UI / API
- TERRA toolserver?
- Create Create any necessary NDS Labs projects using the APIDo we need a script to create these in bulk?Jira server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-252 - Each project needs:
- Public IP / CNAME
- We need to get ours hands on these IPs soon if we want them in time for the Odum event
- a storage volume (limited by the above quota)
- Ansible task? Script? What is the process for this?
- resource limits/quotas
Jira server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-202 Jira server JIRA columns
- Kubernetes Namespace
- Kubernetes LoadBalancer
key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-205
- Project in etcd under /ndslabs/projects
- Existing script
- Kubernetes Namespace / Secret / LoadBalancer / Ingress ruleset
- API Server creates namespace
- I don't think we use per-project secrets yet
- each project may need its own LoadBalancer and ingress rules (they are namespace-specific)
- Public IP / CNAME
- Each project needs:
- Decide on cluster size. How many of each type of node?
2016-04-29
Completed?:
- Console Access
...