Do not perform one-time configuration (e.g., database initialization) inside service containers

Registered by Lars Kellogg-Stedman

Performing one-time config inside the container start scripts makes it difficult to create things like replicationControllers (because they will all attempt to perform the same one-time configuration and you will probably end up with a broken environment).

Instead, isolate one-time configuration tasks in containers dedicated to that purpose. You can use k8s' RestartPolicy to create pods that are run-once, rather than the default reschedule-on-exit behavior.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Not
Drafter:
Lars Kellogg-Stedman
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
Steven Dake

Related branches

Sprints

Whiteboard

We can try this with nova first. I'll take that on this week.

Since we are dropping kubernetes as a deployment architecture and relying upon super-privileged containers (SPC) instead, I'll drop this blueprint.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.