4b332cf3af
As a step to improve testing capabilities of our gates, this commit enhances DevStack with support for deploying coredns in our K8s cluster. The idea here is to be able to run any tests that are referring to services by <namespace>.<service-name>, in particular upstream K8s tests. The tricky part here is that on gate VM's an instance of unbound DNS is running on 127.0.0.1:53. As in DevStack-deployed Kuryr pods doesn't support IPv6, we couldn't just take IPv6 addresses of upstream DNS from unbound configuration and use them in coredns pods. Instead the coredns instance is running on host networking and binds to $HOST_IP:53, which is also used as value of kubelet's --cluster-dns option, while forwarding any upstream DNS requests to the local unbound instance. This isn't perfectly how it would be set up in production environment, but should be close enough for our purposes. This change only affects DevStack, so it's completely safe from release point of view. coredns gets enabled only on gates running Kubernetes as OpenShift gates run openshift-dns already. Change-Id: Icdab52a6229b2209f58e26e4d885f551883727b5 Partial-Implements: blueprint k8s-upstream-tests |
||
|---|---|---|
| .. | ||
| base.yaml | ||
| multi-vif.yaml | ||
| multinode.yaml | ||
| nodesets.yaml | ||
| octavia.yaml | ||
| project.yaml | ||
| sdn.yaml | ||