Publish steampipe image by gitsha only, stop pushing :latest#7
Merged
Conversation
The dev and prod workflows now push only steampipe:<gitsha> instead of also tagging :latest. Consumers pin to a specific gitsha, so :latest is no longer needed. Remove the rollout-restart of extractor-steampipe (it only deployed a new image because the deployment tracked :latest) and the Set kubecontext for EKS step that existed solely for it. Rename the local docker-build tag to local/steampipe:local.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
dev.yml/prod.yml: push onlysteampipe:<gitsha>; drop the:latesttag.Restart the extractor-steampipe deploymentstep and theSet kubecontext for EKSstep it depended on — with consumers pinned to a fixed gitsha, restarting no longer picks up a new image.Makefile: rename the local build taglocal/steampipe:latest→local/steampipe:local.Why
Consumers (
extractor-steampipe,catiopipe) now pin the steampipe image to a specific gitsha rather than tracking:latest. Publishing:latestserved no purpose, and the auto-restart became a no-op against a pinned tag.Deploy flow after this change
steampipe:<gitsha>.<gitsha>to roll it out.Related
catio-tech/extractor-steampipe: pin steampipe sidecar image to224ede2catio-tech/catiopipe: pin steampipe image to224ede2