Skip to content

fix(chart): tolerate dedicated runner taint on operator - #79

Closed
syscod3 wants to merge 1 commit into
mainfrom
fix/operator-runner-taint-toleration
Closed

syscod3 wants to merge 1 commit into
mainfrom
fix/operator-runner-taint-toleration

Conversation

@syscod3

@syscod3 syscod3 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add operator toleration configuration to the Imp chart
  • default it to the dedicated imp.dev/runner=true:NoSchedule taint
  • cover the rendered Deployment with a chart unit assertion

Validation

  • helm template renders the operator toleration
  • helm unittest charts/imp -f tests/operator-deployment_test.yaml: 7 passed; 1 pre-existing failure expects image 0.1.0 while origin/main defaults to 0.9.0
  • git diff --check

Live impact: not deployed; the current unraid-lab GitOps Application pins an older Imp commit.

@syscod3

syscod3 commented Sep 12, 2026

Copy link
Copy Markdown
Contributor Author

Closing as superseded. The chart already exposes operator.tolerations, and unraid-lab already sets the required runner and control-plane tolerations in its GitOps values. Making the runner taint the chart default would unnecessarily schedule operators onto a cluster-specific taint for every installation.

@syscod3 syscod3 closed this Sep 12, 2026
@syscod3
syscod3 deleted the fix/operator-runner-taint-toleration branch September 12, 2026 14:17
@syscod3

syscod3 commented Sep 12, 2026

Copy link
Copy Markdown
Contributor Author

Remaining obsolete: the operator toleration is supplied by the current GitOps values, and the runtime fix merged in PR #99 (867ac97).

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.

1 participant