test: Fix some minor microk8s integration issues #10577
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fact causes problems trying to deploy Cilium properly to microk8s.
to /etc/resolv.conf, but in microk8s environments the resolv.conf will
use coredns to resolve k8s DNS names, so this causes a loop which
triggers havoc. Instead of deploying coredns, just assume that coredns
is already deployed. The check for coredns later on will timeout if
this is not true. At some point we may need to patch up the microk8s
coredns config for cilium test domains, but I'm deferring that for
now since it's not required for minimal CI deployment in microk8s.
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)