PS-11179: Add ARM health probe + durability init scripts to ps3-k8s#101
Merged
Conversation
- Port the two imperative init.groovy.d scripts the in-cluster ps3 controller was missing into the jenkins-ps3-k8s-clouds-init ConfigMap: hetznerArmHealth.groovy (publishes HETZNER_ARM64_HEALTHY that drives resolveArmWorker's arm64 Hetzner-to-Graviton fallback) and durability.groovy (anchors MAX_SURVIVABILITY at boot). - JCasC cannot express a PeriodicWork or setDurabilityHint(), so these stay as init.groovy.d keys beside the now-neutered ec2FleetCloud.groovy. - Without the probe its gen stayed null and the flag was frozen ~4.8d, so the arm64 fallback never engaged on ps3.
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.
Bug
jenkins-ps3-k8scontroller's init ConfigMap held only a neuteredec2FleetCloud.groovy; thehetznerArmHealth.groovyprobe anddurability.groovyfrom the EC2 ps3 set were never ported. TheHETZNER_ARM64_HEALTHYprobe never ran (gen=null, flag frozen ~4.8 days), soresolveArmWorker's arm64 Hetzner-to-Graviton fallback was inert on ps3.Fix
jenkins-ps3-k8s-clouds-initConfigMap; JCasC cannot express aPeriodicWorkorsetDurabilityHint(), so they stay asinit.groovy.dkeys.init.groovy.dis boot-only and this ConfigMap is not sidecar-watched, so it activates on the next controller restart, not via hot-reload; both were restored live via Script Console so the probe is active now.Tickets