|
|
@@ -8,6 +8,8 @@
|
|
|
|
|
|
[Deploy a local registry](#deploy-local-registry)
|
|
|
|
|
|
+[Notas sobre DNS](#notas-sobre-dns)
|
|
|
+
|
|
|
|
|
|
## Install Rancher Desktop
|
|
|
|
|
|
@@ -211,6 +213,10 @@ This will create the provisioner as well as a storage class named ```local-path`
|
|
|
hostpath docker.io/hostpath Delete Immediate false 76m
|
|
|
local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 2m50s
|
|
|
|
|
|
+To make ```local-path``` StorageClass the default:
|
|
|
+
|
|
|
+ kubectl patch storageclass local-path -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
|
|
|
+
|
|
|
Your PVCs either specify to use this storage class or don't specify anything and the default will be used.
|
|
|
|
|
|
Example specifying storageclass
|
|
|
@@ -386,3 +392,12 @@ then, create a namespace, the registry and the ingress:
|
|
|
kubectl create ns docker-registry
|
|
|
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
|
|
|
+
|
