Skip to content

fix(imp): tolerate control-plane taint on operator - #92

Merged
syscod3 merged 1 commit into
mainfrom
fix/imp-operator-control-plane-toleration
Sep 9, 2026
Merged

syscod3 merged 1 commit into
mainfrom
fix/imp-operator-control-plane-toleration

Conversation

@syscod3

@syscod3 syscod3 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Summary

The Imp operator can now schedule on both ordinary control-plane nodes and the dedicated runner node while retaining its existing runner taint tolerance. This removes the scheduling gap that left the second operator replica Pending when only the non-runner control-plane nodes were eligible.

The change adds the exact node-role.kubernetes.io/control-plane / Exists / NoSchedule toleration to the operator values only. Agent and runtime placement, image digests, and both pinned Imp source revisions are unchanged.

Validation

  • Focused Helm render using Imp ca0e86a1d2490ac0d2c08a2a5151534c8b805224: operator renders both tolerations; agent/runtime pod specs and all rendered image references are unchanged.
  • python3 scripts/validate.py — passed (canonical validator; local environment noted that kubeconform was unavailable).
  • python3 scripts/check-version-drift.py --selftest — passed.
  • python3 scripts/check-version-drift.py — passed.
  • Pre-commit hooks: yamllint and gitleaks passed.

@syscod3
syscod3 merged commit 5a19750 into main Sep 9, 2026
5 checks passed
@syscod3
syscod3 deleted the fix/imp-operator-control-plane-toleration branch September 9, 2026 02:30
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