Bump firewall image to 2.0.13 (Helm + CloudFormation) - #20
Closed
Eric Hibbs (flowstate) wants to merge 1 commit into
Closed
Bump firewall image to 2.0.13 (Helm + CloudFormation)#20Eric Hibbs (flowstate) wants to merge 1 commit into
Eric Hibbs (flowstate) wants to merge 1 commit into
Conversation
Update the pinned Socket Firewall version from 2.0.11 to 2.0.13 across both deployment paths, and bump the Helm chart version 0.11.0 -> 0.11.1 since a chart change accompanies the appVersion bump. - helm: Chart.yaml appVersion + chart version, values.yaml image.tag, README values table - cloudformation: firewall-eks.yaml ChartVersion + FirewallImageTag defaults, dns-override.values.yaml image.tag, README prose Co-authored-by: Cursor <cursoragent@cursor.com>
Collaborator
Author
|
Superseded by #21, which bumps these same artifacts straight to firewall 2.0.14 (2.0.13 was never deployed and 2.0.14 supersedes it). |
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 & why
Socket Firewall 2.0.13 is published to Docker Hub (multi-arch amd64+arm64,
:latestmoved). This bumps the pinned image version in the deployment manifests from 2.0.11 so chart/CloudFormation installs pull the release that adds the runtime inspection-bypass endpoint (/socket/config).Changes
Helm:
Chart.yaml:appVersion2.0.11 → 2.0.13; chartversion0.11.0 → 0.11.1values.yaml:image.tag2.0.11 → 2.0.13README.md: values-table default forimage.tagCloudFormation (kept in lockstep, matching the #19 bump pattern):
firewall-eks.yaml:FirewallImageTagdefault 2.0.11 → 2.0.13;ChartVersiondefault 0.11.0 → 0.11.1values/dns-override.values.yaml:image.tag2.0.11 → 2.0.13README.md: image-pin and chart-version proseWhat to look at first
Version strings only — no behavioral or config changes.
metrics.minImageVersion(1.1.343 feature gate) and the alpine/openssl init image (3.3.2) are intentionally left as-is.Testing
Image verified live:
docker buildx imagetools inspect socketdev/socket-registry-firewall:2.0.13shows a multi-arch OCI index with amd64 + arm64 manifests and attestations;:latestresolves to the same digest (sha256:cf072f8c…).Made with Cursor