Avoid having multiple coredns replicas in the same node

[juanluisvaladas]

Description

Coredns were scheduled in the same node sometimes, often causing a SPOF

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[jnummelin]

Maybe we could also add a check to say check-basic smoke that this actually behaves as expected?

[juanluisvaladas]

Maybe we could also add a check to say check-basic smoke that this actually behaves as expected?

Good idea. Added now. The commit is amended but there aren't modifications outside inttest/basic/basic_test.go