node pool to namespace with exclusivity

[Fran-Rg]

New to this.

What I'm looking to achieve is to have a Node Pool exclusive to a namespace, e.g. pods in namespace X should requests nodes on node-pool NX. Pods from any other namespace shouldn't be able to be scheduled on NX.

I've read: https://karpenter.sh/docs/concepts/#scheduling and the Application Developer part.

Am I right to say it's not possible to set the node pool to be matching a namespace. It must be the pod in that namespace to use node selector to select that node pool?
If that's true, how do I prevent other pods from having NodeSelector using that same Node Pool?

[FernandoMiguel]

you select nodes based on nodeselector , taints and tolerations

[Fran-Rg]

nodeselector, taints and toleration, that's defined on the deployment, right? Can't be the node-pool
How do I prevent pod schedulings from other namespaces to use that node pool?

I'm coming from fargate profiles where I assigned profiles to namespaces. Then resources would be linked to a profile by selecting their namespace.
Not possible with karpenter?

[FernandoMiguel]

taints are in the nodes.
tolerations on the jobs

[Fran-Rg]

Could you share an example to achieve that on the node? Via node-pool?

[FernandoMiguel]

@Fran-Rg from the docs

karpenter/designs/static-capacity.md

Lines 161 to 163 in 6cd6c9d

	taints:
	- key: example.com/special-taint
	effect: NoSchedule