|
| 1 | +# Minikube Registry Aliases Addon |
| 2 | + |
| 3 | +An addon to minikube that can help push and pull from the minikube registry using custom domain names. The custom domain names will be made resolveable from with in cluster and at minikube node. |
| 4 | + |
| 5 | +## How to use ? |
| 6 | + |
| 7 | +### Start minikube |
| 8 | + |
| 9 | +```shell |
| 10 | +minikube start -p demo |
| 11 | +``` |
| 12 | +This addon depends on `registry` addon, it need to be enabled before the alias addon is installed: |
| 13 | + |
| 14 | +### Enable internal registry |
| 15 | + |
| 16 | +```shell |
| 17 | +minikube addons enable registry |
| 18 | +``` |
| 19 | + |
| 20 | +Verifying the registry deployment |
| 21 | + |
| 22 | +```shell |
| 23 | +watch kubectl get pods -n kube-system |
| 24 | +``` |
| 25 | + |
| 26 | +```shell |
| 27 | +NAME READY STATUS RESTARTS AGE |
| 28 | +coredns-6955765f44-kpbzt 1/1 Running 0 16m |
| 29 | +coredns-6955765f44-lzlsv 1/1 Running 0 16m |
| 30 | +etcd-demo 1/1 Running 0 16m |
| 31 | +kube-apiserver-demo 1/1 Running 0 16m |
| 32 | +kube-controller-manager-demo 1/1 Running 0 16m |
| 33 | +kube-proxy-q8rb9 1/1 Running 0 16m |
| 34 | +kube-scheduler-demo 1/1 Running 0 16m |
| 35 | +*registry-4k8zs* 1/1 Running 0 40s |
| 36 | +registry-proxy-vs8jt 1/1 Running 0 40s |
| 37 | +storage-provisioner 1/1 Running 0 16m |
| 38 | +``` |
| 39 | + |
| 40 | +```shell |
| 41 | +kubectl get svc -n kube-system |
| 42 | +``` |
| 43 | + |
| 44 | +```shell |
| 45 | +NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE |
| 46 | +kube-dns ClusterIP 10.96.0.10 <none> 53/UDP,53/TCP,9153/TCP 17m |
| 47 | +registry ClusterIP 10.97.247.75 <none> 80/TCP 94s |
| 48 | +``` |
| 49 | + |
| 50 | +> |
| 51 | +> **NOTE:** |
| 52 | +> Please make a note of the CLUSTER-IP of `registry` service |
| 53 | +
|
| 54 | +### Enable registry aliases addon |
| 55 | + |
| 56 | +```shell |
| 57 | +minikube addons enable registry-aliases |
| 58 | +🌟 The 'registry-aliases' addon is enabled |
| 59 | +``` |
| 60 | + |
| 61 | +You can check the mikikube vm's `/etc/hosts` file for the registry aliases entries: |
| 62 | + |
| 63 | +```shell |
| 64 | +watch minikube ssh -- cat /etc/hosts |
| 65 | +``` |
| 66 | + |
| 67 | +```shell |
| 68 | +127.0.0.1 localhost |
| 69 | +127.0.1.1 demo |
| 70 | +10.97.247.75 example.org |
| 71 | +10.97.247.75 example.com |
| 72 | +10.97.247.75 test.com |
| 73 | +10.97.247.75 test.org |
| 74 | +``` |
| 75 | + |
| 76 | +The above output shows that the Daemonset has added the `registryAliases` from the ConfigMap pointing to the internal registry's __CLUSTER-IP__. |
| 77 | + |
| 78 | +### Update CoreDNS |
| 79 | + |
| 80 | +The coreDNS would have been automatically updated by the patch-coredns. A successful job run will have coredns ConfigMap updated like: |
| 81 | + |
| 82 | +```yaml |
| 83 | +apiVersion: v1 |
| 84 | +data: |
| 85 | + Corefile: |- |
| 86 | + .:53 { |
| 87 | + errors |
| 88 | + health |
| 89 | + rewrite name example.com registry.kube-system.svc.cluster.local |
| 90 | + rewrite name example.org registry.kube-system.svc.cluster.local |
| 91 | + rewrite name test.com registry.kube-system.svc.cluster.local |
| 92 | + rewrite name test.org registry.kube-system.svc.cluster.local |
| 93 | + kubernetes cluster.local in-addr.arpa ip6.arpa { |
| 94 | + pods insecure |
| 95 | + upstream |
| 96 | + fallthrough in-addr.arpa ip6.arpa |
| 97 | + } |
| 98 | + prometheus :9153 |
| 99 | + proxy . /etc/resolv.conf |
| 100 | + cache 30 |
| 101 | + loop |
| 102 | + reload |
| 103 | + loadbalance |
| 104 | + } |
| 105 | +kind: ConfigMap |
| 106 | +metadata: |
| 107 | + name: coredns |
| 108 | +``` |
| 109 | +
|
| 110 | +To verify it run the following command: |
| 111 | +
|
| 112 | +```shell |
| 113 | +kubectl get cm -n kube-system coredns -o yaml |
| 114 | +``` |
| 115 | + |
| 116 | +Once you have successfully patched you can now push and pull from the registry using suffix `example.com`, `example.org`,`test.com` and `test.org`. |
| 117 | + |
| 118 | +The successful run will show the following extra pods (Daemonset, Job) in `kube-system` namespace: |
| 119 | + |
| 120 | +```shell |
| 121 | +NAME READY STATUS RESTARTS AGE |
| 122 | +registry-aliases-hosts-update-995vx 1/1 Running 0 47s |
| 123 | +registry-aliases-patch-core-dns-zsxfc 0/1 Completed 0 47s |
| 124 | +``` |
| 125 | + |
| 126 | +## Verify with sample application |
| 127 | + |
| 128 | +You can verify the deployment end to end using the example [application](https://github.com/kameshsampath/minikube-registry-aliases-demo). |
| 129 | + |
| 130 | +```shell |
| 131 | +git clone https://github.com/kameshsampath/minikube-registry-aliases-demo |
| 132 | +cd minikube-registry-aliases-demo |
| 133 | +``` |
| 134 | + |
| 135 | +Make sure you set the docker context using `eval $(minikube -p demo docker-env)` |
| 136 | + |
| 137 | +Deploy the application using [Skaffold](https://skaffold.dev): |
| 138 | + |
| 139 | +```shell |
| 140 | +skaffold dev --port-forward |
| 141 | +``` |
| 142 | + |
| 143 | +Once the application is running try doing `curl localhost:8080` to see the `Hello World` response |
| 144 | + |
| 145 | +You can also update [skaffold.yaml](./skaffold.yaml) and [app.yaml](.k8s/app.yaml), to use `test.org`, `test.com` or `example.org` as container registry urls, and see all the container image names resolves to internal registry, resulting in successful build and deployment. |
| 146 | + |
| 147 | +> **NOTE**: |
| 148 | +> |
| 149 | +> You can also update [skaffold.yaml](./skaffold.yaml) and [app. yaml](.k8s/app.yaml), to use `test.org`, `test.com` or > `example.org` as container registry urls, and see all the > container image names resolves to internal registry, resulting in successful build and deployment. |
0 commit comments