Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Kubernetes v1.9.1 cluster/addons/registry to Kubespray #2244

Merged
merged 1 commit into from Feb 6, 2018

Conversation

hswong3i
Copy link
Contributor

@hswong3i hswong3i commented Feb 4, 2018

This patch migrate the original Kubernets addon "registry" into Kubespray as Ansible role.

Due to recent Kubernetes changes (kubernetes/kubernetes#58564 and kubernetes/kubernetes#49213), kube-registry-proxy is being removed from v1.9.2. BTW, a private repository is usually useful for custom deployment, e.g. if we need to build some custom image only exists in our own kubernetes deployment, but not push to any elsewhere.

This simple implementation doesn't handle PV and PVC but just use emptyDir: {}

For testing, change registry_enabled as true under inventory/group_vars/k8s-cluster.yml and deploy with --tags registry.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Feb 4, 2018
@hswong3i hswong3i changed the title Migrate Regisry Addon from https://github.com/kubernetes/kubernetes/tree/v1.9.1/cluster/addons/registry Migrate Regisry Addon from https://github.com/kubernetes/kubernetes/tree/v1.9.1/cluster/addons/registry to Kubespray Feb 4, 2018
@hswong3i hswong3i changed the title Migrate Regisry Addon from https://github.com/kubernetes/kubernetes/tree/v1.9.1/cluster/addons/registry to Kubespray Migrate Kubernetes v1.9.1 cluster/addons/registry to Kubespray Feb 5, 2018
@ant31 ant31 merged commit 0774c83 into kubernetes-sigs:master Feb 6, 2018
woopstar added a commit to woopstar/kubespray that referenced this pull request Feb 6, 2018
In PR kubernetes-sigs#2244 the `registry_enabled` is missing in defaults, causing a deployment to fail, if it is not set in k8s-cluster.yml
@hswong3i hswong3i deleted the registry branch February 13, 2018 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants