Commit Graph

10 Commits (master)

Author SHA1 Message Date
rogermm 431a296858 Fix addon registry: https://github.com/kubernetes/minikube/issues/15567 2023-01-03 06:57:12 -08:00
Ling Samuel 101d39fc51
Addon custom registry:
* fix missing suffix when using global image repo
* support override global image repo
* change all imagePullPolicy to IfNotPresent
* fix empty global image repo suffix

Signed-off-by: Ling Samuel <lingsamuelgrace@gmail.com>
2021-01-27 10:33:08 +08:00
Ling Samuel 52f0e49a1e
Fix docker.io/ prefix
Signed-off-by: Ling Samuel <lingsamuelgrace@gmail.com>
2021-01-27 10:33:07 +08:00
Ling Samuel 76833fd2fa
Make registry configurable
Signed-off-by: Ling Samuel <lingsamuelgrace@gmail.com>
2021-01-27 10:33:07 +08:00
Ling Samuel de3c901c18
Implement all addons
Signed-off-by: Ling Samuel <lingsamuelgrace@gmail.com>
2021-01-27 10:33:07 +08:00
Yehiyam Livneh 40736fe6ab add ImageRepository to addons templayes 2020-11-01 09:05:31 +02:00
Zoltán Reegn 3056ca2d48 Upgrade addons to use apps/v1 instead of extensions/v1beta1
extensions/v1beta1 are deprecated and will not be served with kubernetes 1.16
anymore.

For Deployment,DaemonSet and StatefulSet the apps/v1 api has been present
since kubernetes 1.9.

See following blog post for details:
https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/
2019-08-26 15:00:49 +02:00
Om Kumar d76d874067 Fix regression caused by registry-proxy
This PR addresses #4604 by adding a new selector to concerned svc/rc only.
This also reverts `kubernetes.io/minikube-addons` to `registy` for registry-proxy
so that addon manager can deploy registry-proxy when registry addon is enabled.
2019-07-18 18:28:07 +05:30
Jose Donizetti ad97983d9e # This is a combination of 8 commits.
# This is the 1st commit message:

Fix doc comment version.gitCommitID doc


# This is the commit message #2:

Add hyperkit doc


# This is the commit message #3:

Add commit id to docker-machine-driver-kvm2 version


# This is the commit message #4:

removed label selector for registry-proxy daemonset

# This is the commit message #5:

Add support to custom qemu uri on kvm2 driver


# This is the commit message #6:

Improve hyperkit vm stop


# This is the commit message #7:

Make virtualbox DNS settings configurable 


# This is the commit message #8:

added integration tests for registry addon
2019-06-29 18:27:47 +10:00
Om Kumar ec3e7b5896 Enable registry-proxy
As per [this blog](https://blog.hasura.io/sharing-a-local-registry-for-minikube-37c7240d0615) and [this gist](https://gist.github.com/coco98/b750b3debc6d517308596c248daf3bb1), we need to deploy a registry-proxy
which will expose docker registry on the minikube host.

Once this daemon set is deployed on minikube, one can access registry on `$(minikube ip):5000`.
This has been tested with minikube v1.0.1 with none driver. With this, one will not have to use
`kubectl port-forward`. I was able to push a container image to registry using
```
docker push $(minikube ip):5000/test-img
```
And then ran it in minikube using
```
kubectl run -i -t test-img --image=$(minikube ip):5000/test-img --restart=Never
```
2019-05-24 10:37:14 +05:30