- Kubernetes-agent: https://github.com/rancher/kubernetes-agent
results in rancher/kubernetes-agent:tag image
- Ingress controller: https://github.com/rancher/lb-controller
results in rancher/lb-service-rancher:tag image
- Kubectld: https://github.com/rancher/kubectld
results in rancher/kubectld:tag image
Kubernetes image used for controller/k8s/kubelet/proxy/scheduler services. Source: https://github.com/rancher/kubernetes Packaging: https://github.com/rancher/kubernetes-package
If only packaging changes are required:
- Make changes in kubernetes-package.
- Create and push tag
- Run make, it should generate the image with the new tag.
If kubernetes base got changed - either sync with upstream was performed, or some bug fix went in, do this:
- Build k8s binaries using rancher-k8s-build/build.sh under .
- Create and push tag
- Upload binaries built on step 1 to the release
- Point dockerfile.dapper to a new binary:
https://github.com/rancher/kubernetes-package/blob/master/Dockerfile.dapper#L18
- Commit the changes, create and push tag
- Run make to generate a new image.
- Add remote [email protected]:kubernetes/kubernetes.git, lets call it upstream. Rancher is origin, [email protected]:rancher/kubernetes.git
- Lets say you need to update kubernetes rancher v1.5.1-rancher with k8s upstream v1.5.2. For that:
git checkout -b v1.5.2-rancher v1.5.1-rancher git rebase -i v1.5.2 git push origin v1.5.2-rancher
https://github.com/rancher/rancher-catalog/tree/master/infra-templates/k8s
Review recommended admission controllers and see if they have changed since the last release (https://github.com/kubernetes/kubernetes.github.io/blob/master/docs/admin/admission-controllers.md#is-there-a-recommended-set-of-plug-ins-to-use).