Skip to content

[release/0.16] Validate that installed release has desired state - #338

Merged
brandond merged 2 commits into
k3s-io:release/0.16from
brandond:release-hash-check_release-0.16
Jul 15, 2026
Merged

[release/0.16] Validate that installed release has desired state#338
brandond merged 2 commits into
k3s-io:release/0.16from
brandond:release-hash-check_release-0.16

Conversation

@brandond

Copy link
Copy Markdown
Member

Backport #337 to release/0.16 branch

brandond added 2 commits July 15, 2026 21:01
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 0f907a3)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Inject config hash into release labels, and validate that the installed release has the correct hash. If the job is complete but the hash does not match, the job needs to be recreated.

This also updates the hash to cover the job spec.template, so that changes to job configuration or spec.set values modify the hash to trigger a new release.

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit e060287)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
@brandond
brandond merged commit 7b033ef into k3s-io:release/0.16 Jul 15, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants