...
Tasks required for Production Deployments:
...
- Test LB prototype with test-drive interfaces/specs - path based for odum
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-239
...
- Update go dependencies/ingress API to current production release of kubernetes -
currently based on 1.2.0-alpha, current 160502 is 1.2.3
...
- , should evaluate diff of 1.2.3 and 1.3.0-alpha and pick appropriately for future
...
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-240
- Update the load balancer build - go build produces a static binary.
...
- Build should produce image from alpine with net-tools and single static binary.
...
Info on golang:onbuilds is here: https://hub.docker.com/_/golang/Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-241
- Addressing startup
- Label the LB node such that LB pod deploys there, and add anti-affinity to label/scheduler/system to avoid scheduling other pods on the LB node.
i.e. The ingress-lb should be the only thing running on the LB node - always -
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-242
- Label the LB node such that LB pod deploys there, and add anti-affinity to label/scheduler/system to avoid scheduling other pods on the LB node.
Background
The NDS Labs "Workbench" service provides NDSC stakeholders with the ability to quickly launch and explore a variety of data management tools. Users select from a list of available services to configure and deploy instances of them. Workbench "services" are composed of a set of integrated Docker containers all deployed on a Kubernetes cluster.
...