title: Linking kubernetes namespace to nodes
body: <p>It seems to be good practice to map environments such as dev, qa and production to kubernetes namespaces. To achieve "true" separation, it seems to be a good idea to label nodes exclusively dedicated to one of those namespaces and ensure resources in those environments get scheduled on those nodes only. That's at least our current thinking. There may be manifests one might want to use in those namespaces that should/must not be tampered with. Kubernetes does not seem to support associating namespaces with nodes out of the box. <code>PodNodeSelector</code> admission controller seems close but is not quite what we are looking for. The only option to achieve what we want seems to be a custom mutating admission webhook as documented <a href="https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#admission-webhooks" rel="nofollow noreferrer">here</a>.</p>
  
  <p>I guess other people have been here before and there is a solution to address our primary concern which is that we don't want load on dev or qa environments impacting production performance.</p>
  
  <p>Is there any off the shelf solution linking namespaces to nodes?</p>
  
  <p>If not, are there any alternative approaches ensuring that environments do not interfere in terms of load/performance? </p>