Repository navigation
fix(imp): tolerate runner taint on operator - #91
Merged
Merged
Conversation
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
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.
Summary
The unraid-lab Imp operator can now schedule on nodes tainted
imp.dev/runner=true:NoSchedule, matching the existing agent/runtime placement contract. Both the chart and CRD sources are pinned to the merged Imp revisionca0e86a1d2490ac0d2c08a2a5151534c8b805224; existing image digests and unrelated values are unchanged.Validation
imp-operator,imp-agent, andimp-runtimecontain the required toleration.python3 scripts/validate.py(Helm render + kubeconform): passed.git diff --check: passed.