fix: drift nodes on node class edits the server cannot show, cut 0.8.0 #26
No reviewers
Labels
No labels
accessibility
bot
bug
dependencies
docker
documentation
duplicate
enhancement
go
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#25 feat!: move the project to forge.sarak.sh
mikluko/karpenter-provider-hetzner
Reference
mikluko/karpenter-provider-hetzner!26
Loading…
Reference in a new issue
No description provided.
Delete branch "mikluko/nodeclass-hash"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bootstrap, image selector, SSH keys, public IPs and placement group
strategy cannot be read back from a running server, so they are compared
by hash instead, after the AWS provider: each NodeClaim is stamped at
launch with the hash of its node class, and a mismatch drifts it as
NodeClassDrift. Fields drift already checks against the server, and
kubelet, which changes no server, are left out of the hash.
NodeClaims with no hash, or one under another hash version, are stamped
with the node class as it stands rather than drifted, so an upgrade does
not replace every node. Nodes already behind a node class edit when this
lands still have to be replaced by hand.
Closes #24
Stacked on #25; merge that first. 0.8.0 carries both.
2c451b19bbf290258622f2902586223623018f3b3623018f3b74c5b2554074c5b25540bf98fde198bf98fde1981b5dba45931b5dba459351f3a1917a51f3a1917a84c153695fView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.