Kubernetes integration with OpenStack networking
Go to file
Michał Dulko 4b332cf3af Add option to deploy coredns
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
2019-03-15 11:01:12 +01:00
.zuul.d Add option to deploy coredns 2019-03-15 11:01:12 +01:00
contrib Change Pod annotations format to o.vo 2018-08-01 15:30:42 +02:00
devstack Add option to deploy coredns 2019-03-15 11:01:12 +01:00
doc Update documentation about NP handlers needed 2019-03-07 11:46:57 +01:00
etc Proceed CNI output in format of version 0.3.1 2018-07-04 13:04:35 +00:00
kubernetes_crds Implement NP SG create/delete actions 2018-09-06 10:10:15 -04:00
kuryr_kubernetes Merge "Switch except statements order" 2019-03-05 12:42:28 +00:00
playbooks Clean up legacy playbooks 2018-04-26 09:38:28 +02:00
releasenotes Merge "Use same pool_driver for different pod_vif_drivers" 2019-02-06 01:04:48 +00:00
tools Clean up Dockerfiles and how we build them 2018-12-17 10:40:50 +01:00
.coveragerc tox: fix coverage 2016-11-18 10:14:56 +03:00
.dockerignore Add support to install Kuryr as a network addon 2017-09-14 13:33:53 +02:00
.gitignore ignore Editor tags 2018-09-25 12:16:08 +02:00
.gitreview Added .gitreview 2016-05-12 09:14:08 +00:00
.pre-commit-config.yaml Add support for pre-commit-hooks 2018-09-27 13:05:43 +02:00
.stestr.conf Switch to using stestr 2018-07-16 15:43:10 +00:00
.testr.conf cookiecutter commit for kuryr-kubernetes 2016-05-22 08:54:07 +03:00
CONTRIBUTING.rst Fix some misspellings within Kuryr-Kubernetes 2019-01-03 07:31:47 -05:00
HACKING.rst Update doc title format 2018-03-01 14:27:13 +08:00
LICENSE cookiecutter commit for kuryr-kubernetes 2016-05-22 08:54:07 +03:00
README.rst Update links in README 2018-08-19 03:47:48 +08:00
babel.cfg cookiecutter commit for kuryr-kubernetes 2016-05-22 08:54:07 +03:00
cni.Dockerfile Clean up Dockerfiles and how we build them 2018-12-17 10:40:50 +01:00
cni_ds_init Remove way of running without kuryr-daemon 2019-02-04 12:53:00 +01:00
cni_py3.Dockerfile Clean up Dockerfiles and how we build them 2018-12-17 10:40:50 +01:00
controller.Dockerfile Clean up Dockerfiles and how we build them 2018-12-17 10:40:50 +01:00
controller_py3.Dockerfile Clean up Dockerfiles and how we build them 2018-12-17 10:40:50 +01:00
lower-constraints.txt Upgrade Flask version due to security concerns 2019-02-14 10:09:40 +01:00
requirements.txt Upgrade Flask version due to security concerns 2019-02-14 10:09:40 +01:00
setup.cfg Skip exception in case kuryrnetpolicy CRD is already deleted 2019-02-19 12:03:39 +01:00
setup.py Updated from global requirements 2017-03-15 12:44:19 +00:00
test-requirements.txt Switch to using stestr 2018-07-16 15:43:10 +00:00
tox.ini Merge "fix tox -e debug target" 2018-10-15 08:54:24 +00:00

README.rst

Team and repository tags

image

Project description

Kubernetes integration with OpenStack networking

The OpenStack Kuryr project enables native Neutron-based networking in Kubernetes. With Kuryr-Kubernetes it's now possible to choose to run both OpenStack VMs and Kubernetes Pods on the same Neutron network if your workloads require it or to use different segments and, for example, route between them.

Contribution guidelines

For the process of new feature addition, refer to the Kuryr Policy