Rancher is really awesome! We’re in the process of implementing Kubernetes and found Rancher to look compelling to do this. The issue I’m seeing off the bat is while Rancher just sets K8 up for you and makes it really easy, larger companies like to control all the pieces. I don’t think we will get approval to use Rancher and K8 because it just kinda goes off and does it’s thing. For example our company policy is to only pull images from our own registry so we aren’t just going off to the internets and pulling images. Can the K8 setup in Rancher allow us to pull our own K8 images that we have validated/tested and published to our own registry?
[As of 1.1] Kubernetes is deployed from a rancher-catalog entry, so you could:
- Build your own version of the images (in https://github.com/rancher/catalog-dockerfiles). K8s is slightly modified to e.g. include our plugins so you can’t just point at a stock copy.
- Change the image names, test, push,
- Fork the catalog (in https://github.com/rancher/rancher-catalog)
- Turn off our catalog (“Rancher Certified”)
- Add yours as
rancher-catalog = your-url