a93415b7bf
This commit does necessary changes to allow using K8s 1.8 in our DevStack plugin. In particular: * Contents of missing setup-files.sh are introduced into the DevStack plugin directly. * Deprecated and removed `--api-servers` option of kubelet is replaced by `--kubeconfig=<path> --require-kubeconfig` * Switches default value of KURYR_HYPERKUBE_VERSION to point to latest 1.8. In long term we should probably move to kubeadm along with splitting the K8s DevStack plugin out of Kuryr repo. This is short term solution to using ancient kubernetes version in upstream testing. Closes-Bug: 1734834 Change-Id: I0598109152cf353b0a23a225bb8f290da0069d96 |
||
|---|---|---|
| contrib | ||
| devstack | ||
| doc | ||
| etc | ||
| hooks | ||
| kuryr_kubernetes | ||
| playbooks | ||
| releasenotes | ||
| scripts | ||
| tools | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| cni.Dockerfile | ||
| cni.spec | ||
| cni_builder | ||
| cni_builder.Dockerfile | ||
| cni_ds_init | ||
| cni_main.patch | ||
| controller.Dockerfile | ||
| k8s_client.patch | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
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.
- Free software: Apache license
- Documentation: https://docs.openstack.org/kuryr-kubernetes/latest
- Source: https://git.openstack.org/cgit/openstack/kuryr-kubernetes
- Bugs: https://bugs.launchpad.net/kuryr-kubernetes
- Overview and demo: http://superuser.openstack.org/articles/networking-kubernetes-kuryr
Contribution guidelines
For the process of new feature addition, refer to the Kuryr Policy