Join GitHub today
Calico network support in Rancher cattle #8603
I have updated network-manager, it can be able to support other CNI drivers. So calico network support can be achieved. #8535
For catalog item：
These steps will be added to the auto execute scripts.
Ensure that the Rancher server version is v1.6.0+.
I have built a setup with Calico, it can work fine.
Is it possible to change the rancher-metadata IP address to something else? Might have been hard coded in multiple places.
Looking forward for the testing results.
Calico IPAM can accept the "IP" as a runtime arg.
I just update cniglue, add this "IP" arg.
I will build a setup on AWS, then you can check the results easily.
This was referenced
May 3, 2017
referenced this issue
May 9, 2017
@cjellick Agree with you. In my test results, only the rancher-lb have this problem, because it needs to read the "/self" key.
Overall, considering all of the infrastructure services, I do not have a good way, just want to focus on the document when the users wants to use Calico.
Of course, by updating the go-rancher-metadata to do the overall compatibility is also a way, but also involves a lot of infrastructure services update the dependency package.
Check the Calico NetConf type, cannot see the routes field.
For further verification, I manually add the route to the container's namespace, verify that custom routes are useful.
Add a route for 169.254.169.250/32 to eth0:
Check the metadata problem:
Even if we do custom routes, we can not solve this problem.
I gave the above instructions a go and had two problems