chore(registry): add registry push test

Author: duanhongyi

charts/registry/templates/registry-deployment.yaml

@@ -71,6 +71,7 @@ spec:
           failureThreshold: 5
         ports:
         - containerPort: 5000
+          name: http
         volumeMounts:
         - name: registry-storage
           mountPath: /var/lib/registry

charts/registry/templates/registry-service.yaml

@@ -13,5 +13,9 @@ spec:
   clusterIP: None
   selector:
     app: drycc-registry
+  ports:
+  - name: http
+    port: 5000
+    targetPort: 5000
   sessionAffinity: ClientIP  
 {{- end }}

contrib/ci/s3.json

@@ -0,0 +1,10 @@
+{
+	"identities": [{
+		"name": "drycc",
+		"credentials": [{
+			"accessKey": "$DRYCC_STORAGE_ACCESSKEY",
+			"secretKey": "$DRYCC_STORAGE_SECRETKEY"
+		}],
+		"actions": ["Admin", "Read", "List", "Tagging", "Write"]
+	}]
+}

contrib/ci/start-s3.sh

@@ -0,0 +1,7 @@
+#!/usr/bin/env bash
+eval "cat <<EOF >/etc/seaweedfs/s3.json
+$( cat /tmp/weed/s3.json )
+EOF
+" 2> /dev/null
+
+weed server -dir=/data -s3 -s3.config=/etc/seaweedfs/s3.json

contrib/ci/test.sh

@@ -47,5 +47,6 @@ echo -e "\\033[32m---> Waitting for ${REGISTRY_IP}:5000\\033[0m"
 wait-for-port --host="${REGISTRY_IP}" 5000
 echo -e "\\033[32m---> S3 service ${REGISTRY_IP}:5000 ready...\\033[0m"
 # check that the registry is still up
-podman logs "${JOB}"
-podman ps -q --no-trunc=true | grep "${JOB}"
+podman tag "$1" "${REGISTRY_IP}:5000/registry:canary"
+echo admin | podman login "${REGISTRY_IP}:5000" --tls-verify=false --username admin --password-stdin > /dev/null 2>&1
+podman push "${REGISTRY_IP}:5000/registry:canary" --tls-verify=false