e30847e231
Neutron cli is deprecated - replaced neutron cli commands with equivalent openstack cli commands.
45 lines
2.9 KiB
Markdown
45 lines
2.9 KiB
Markdown
OpenStack
|
|
===============
|
|
|
|
To deploy kubespray on [OpenStack](https://www.openstack.org/) uncomment the `cloud_provider` option in `group_vars/all.yml` and set it to `'openstack'`.
|
|
|
|
After that make sure to source in your OpenStack credentials like you would do when using `nova-client` or `neutron-client` by using `source path/to/your/openstack-rc` or `. path/to/your/openstack-rc`.
|
|
|
|
The next step is to make sure the hostnames in your `inventory` file are identical to your instance names in OpenStack.
|
|
Otherwise [cinder](https://wiki.openstack.org/wiki/Cinder) won't work as expected.
|
|
|
|
Unless you are using calico you can now run the playbook.
|
|
|
|
**Additional step needed when using calico:**
|
|
|
|
Calico does not encapsulate all packages with the hosts' ip addresses. Instead the packages will be routed with the PODs ip addresses directly.
|
|
|
|
OpenStack will filter and drop all packages from ips it does not know to prevent spoofing.
|
|
|
|
In order to make calico work on OpenStack you will need to tell OpenStack to allow calico's packages by allowing the network it uses.
|
|
|
|
First you will need the ids of your OpenStack instances that will run kubernetes:
|
|
|
|
openstack server list --project YOUR_PROJECT
|
|
+--------------------------------------+--------+----------------------------------+--------+-------------+
|
|
| ID | Name | Tenant ID | Status | Power State |
|
|
+--------------------------------------+--------+----------------------------------+--------+-------------+
|
|
| e1f48aad-df96-4bce-bf61-62ae12bf3f95 | k8s-1 | fba478440cb2444a9e5cf03717eb5d6f | ACTIVE | Running |
|
|
| 725cd548-6ea3-426b-baaa-e7306d3c8052 | k8s-2 | fba478440cb2444a9e5cf03717eb5d6f | ACTIVE | Running |
|
|
|
|
Then you can use the instance ids to find the connected [neutron](https://wiki.openstack.org/wiki/Neutron) ports (though they are now configured through using OpenStack):
|
|
|
|
openstack port list -c id -c device_id --project YOUR_PROJECT
|
|
+--------------------------------------+--------------------------------------+
|
|
| id | device_id |
|
|
+--------------------------------------+--------------------------------------+
|
|
| 5662a4e0-e646-47f0-bf88-d80fbd2d99ef | e1f48aad-df96-4bce-bf61-62ae12bf3f95 |
|
|
| e5ae2045-a1e1-4e99-9aac-4353889449a7 | 725cd548-6ea3-426b-baaa-e7306d3c8052 |
|
|
|
|
Given the port ids on the left, you can set the two `allowed_address`(es) in OpenStack. Note that you have to allow both `kube_service_addresses` (default `10.233.0.0/18`) and `kube_pods_subnet` (default `10.233.64.0/18`.)
|
|
|
|
# allow kube_service_addresses and kube_pods_subnet network
|
|
openstack port set 5662a4e0-e646-47f0-bf88-d80fbd2d99ef --allowed_address ip_address=10.233.0.0/18,ip_address=10.233.64.0/18
|
|
openstack port set e5ae2045-a1e1-4e99-9aac-4353889449a7 --allowed_address ip_address=10.233.0.0/18,ip_address=10.233.64.0/18
|
|
|
|
Now you can finally run the playbook.
|