You are investigating issues in your production application that runs on Google Kubernetes Engine (GKE). You determined that the source of the issue is a recently updated container image, although the

Question

Options

• ACreate a new tag called stable that points to the previously working container, and change the
• BAlter the deployment to point to the sha256 digest of the previously working container.
• CBuild a new container from a previous Git tag, and do a rolling update on the deployment to the
• DApply the latest tag to the previous container image, and do a rolling update on the deployment.

• A
  10% (5)
• B
  80% (40)
• C
  6% (3)
• D
  4% (2)

Explanation

A container image's SHA256 digest is an immutable, cryptographically unique identifier for a specific image layer set. Pointing the deployment to the digest of the previously working image guarantees you are running exactly that image version, regardless of any tag mutations. The 'latest' tag is mutable and can be overwritten at any time. Option A (creating a 'stable' tag) introduces a mutable tag and extra steps. Option C (building from a Git tag) adds unnecessary build time and steps when the known-good image already exists in the registry. Option D (re-tagging previous image as 'latest') is risky and confusing.

No community discussion yet for this question.