Open Bug 1594911 Opened 6 years ago Updated 5 years ago

Lock maxmind image version at deploy time

Categories

(Cloud Services :: Operations: Normandy, task)

task
Not set
normal

Tracking

(Not tracked)

People

(Reporter: brian, Assigned: sven)

Details

We uae a private docker image containing the maxmind geoip database as an initcontainer for Normandy and Classify Client. This image is built weekly. Currently the k8s deployments are configured to use the "latest" tag for this image. This means that as pods are cycled due to node upgrades etc new ones can pull a newer version of this image than the version they were originally deployed with. This could lead to unexpected changes in behavior. We should lock this to a fixed tag. We could use an existing tag other than latest, or we could retag the image with a tag that corresponds to the normandy deploy, similar to the tag used when the normandy image is mirrored.

https://github.com/mozilla-services/cloudops-maxmind-image/blob/master/.circleci/config.yml

Assignee: miles → bpitts
Assignee: bpitts → sven
You need to log in before you can comment on or make changes to this bug.