CrowdStrike / CrowdStrike/falcon-operator

Expose tolerations and nodeSelector on operator manager deployment

Open
#802 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
79
Forks
51
Avg merge
6h 46m
Merged PRs (30d)
10

Description

Description:

When deploying the falcon-operator on a cluster with only system node pools tainted with CriticalAddonsOnly:NoSchedule, the operator manager pod cannot be scheduled there because the upstream manifest does not expose tolerations as a configurable value on the falcon-operator-controller-manager deployment.

Environment:
AKS cluster with system node pools carrying the CriticalAddonsOnly:NoSchedule taint. Operator deployed via ArgoCD using the published manifest bundled in a Helm chart.

The Problem:
The operator manager is critical infrastructure and belongs on system nodes. Without a CriticalAddonsOnly toleration it lands on workload nodes which are disposable and scale up and down. Patching the upstream manifest is not an option as it breaks clean upgrades and does not compose with ArgoCD when bundled in a Helm chart.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the published manifest and the falcon-operator-controller-manager deployment, then inspect the Helm chart that bundles them to find how deployment settings are exposed. Done means users can configure tolerations and nodeSelector without patching the upstream manifest, allowing the manager to schedule on tainted system node pools through clean upgrades.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.