|
@@ -8,6 +8,8 @@
|
|
|
|
|
|
|
|
[Deploy a local registry](#deploy-local-registry)
|
|
[Deploy a local registry](#deploy-local-registry)
|
|
|
|
|
|
|
|
|
|
+[Notas sobre DNS](#notas-sobre-dns)
|
|
|
|
|
+
|
|
|
|
|
|
|
|
## Install Rancher Desktop
|
|
## Install Rancher Desktop
|
|
|
|
|
|
|
@@ -364,3 +366,11 @@ then, create a namespace, the registry and the ingress:
|
|
|
kubectl create ns docker-registry
|
|
kubectl create ns docker-registry
|
|
|
kubectl create -f docker-registry.yaml -f ingress.yaml
|
|
kubectl create -f docker-registry.yaml -f ingress.yaml
|
|
|
|
|
|
|
|
|
|
+
|
|
|
|
|
+## Notas sobre DNS
|
|
|
|
|
+
|
|
|
|
|
+He observado que los pods no pillan la configuración DNS del ordenador host.
|
|
|
|
|
+
|
|
|
|
|
+Buscando en internet, encontré que una solución era reiniciar el servicio ```coredns```
|
|
|
|
|
+
|
|
|
|
|
+ kubectl -n kube-system rollout restart deployment coredns
|
