Quellcode durchsuchen

Corrijo phpmyadmin en wordpress que no cogia la plataforma correcta

Celestino Rey vor 1 Woche
Ursprung
Commit
20eaa4adc9

+ 3 - 1
HelmCharts/mivida-chart/templates/php-deployment.yaml

@@ -38,7 +38,9 @@ spec:
     spec:
     spec:
       containers:
       containers:
         - name: phpmyadmin
         - name: phpmyadmin
-          image: docker-registry:32000/phpmyadmin:1.0
+          image: phpmyadmin:5.2.3-apache
+          imagePullPolicy: Always
+          #image: docker-registry:32000/phpmyadmin:1.0
           ports:
           ports:
             - containerPort: 80
             - containerPort: 80
               name: phpmyadm
               name: phpmyadm

+ 2 - 2
HelmCharts/wordpress-chart/templates/php-deployment.yaml

@@ -38,8 +38,8 @@ spec:
     spec:
     spec:
       containers:
       containers:
         - name: phpmyadmin
         - name: phpmyadmin
-          image: phpmyadmin
-          #image: docker-registry:32000/phpmyadmin:1.0
+          image: phpmyadmin:5.2.3-apache
+          imagePullPolicy: Always
           ports:
           ports:
             - containerPort: 80
             - containerPort: 80
               name: phpmyadm
               name: phpmyadm

+ 12 - 0
mypdr/README.md

@@ -72,3 +72,15 @@ Once you are done with that, run the garbage-collect:
 docker exec <registry_container_name> registry garbage-collect /etc/docker/registry/config.yml --delete-untagged
 docker exec <registry_container_name> registry garbage-collect /etc/docker/registry/config.yml --delete-untagged
 
 
 Your registry config file may be in some other path, but this is the default. Read more about the garbage collector from docs, but the gist is: the registry binary inside the container includes a garbage-collect command, but you have to run it yourself. Of course you can always let the crontab run it for you.
 Your registry config file may be in some other path, but this is the default. Read more about the garbage collector from docs, but the gist is: the registry binary inside the container includes a garbage-collect command, but you have to run it yourself. Of course you can always let the crontab run it for you.
+
+
+
+# regenerar htpasswd
+
+htpasswd ya está instalado. Para regenerar el fichero con bcrypt (formato compatible con el registry):
+
+   htpasswd -Bbn creylopez 'nuevaContraseña' > registry.password
+
+Y si el fichero ya existe en el hostPath, sobrescribir el que usa el registry:
+
+   htpasswd -Bbn creylopez 'nuevaContraseña' > /mnt/Externo/mypdr/a2auth/registry.password

+ 3 - 3
mypdr/paraTodo.sh

@@ -1,5 +1,5 @@
 kubectl delete -f registry-service.yaml 
 kubectl delete -f registry-service.yaml 
 kubectl delete -f registry-deployment.yaml
 kubectl delete -f registry-deployment.yaml
-kubectl delete -f registry-claim1-persistentvolumeclaim.yaml 
-kubectl delete -f registry-claim0-persistentvolumeclaim.yaml 
-kubectl delete -f pv-local-registry.yaml
+#kubectl delete -f registry-claim1-persistentvolumeclaim.yaml 
+#kubectl delete -f registry-claim0-persistentvolumeclaim.yaml 
+#kubectl delete -f pv-local-registry.yaml

+ 2 - 1
mypdr/registry.password

@@ -1 +1,2 @@
-creylopez:$2y$05$WhvZdhVr.Xwz.j/M61fMTu2ea8yAf5bPjPvQadT12kuzZaJw2Gwri
+creylopez:$2y$05$zpO/e5S2iaoE0YU.Hzg0pukZLPNgVWBqqJHChF9H6HH7ACbmNA82e
+