change registration otken and manually delete the file .runner inside the runner pvc

Gitea-webserver.kube.yaml

@@ -104,10 +104,9 @@ spec:
         - name: CONFIG_FILE
           value: /config/config.yaml
         - name: GITEA_INSTANCE_URL
-          value: "https://gitea.tryton.geeraert.eu/"
+          value: "https://gitea.geeraert.eu/"
         - name: GITEA_RUNNER_REGISTRATION_TOKEN
-#          value: "2lLHg3Zt4mqjz04cBVIi6UI11cDOwIrwvNY6FMTH"
-          value: "95NWFriTQnu910SpcbteDybyi9X5LffdLdaTK8lk"
+          value: "rqi4mFW8LXoc5MhIrUD1rjzdmKVY8n9X14BP6sWd"
         - name: GITEA_RUNNER_NAME
           value: "runner"
         - name: GITEA_RUNNER_LABELS
@@ -136,47 +135,6 @@ spec:
           defaultMode: 0555
 
 
----
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: remote-buildkitd
-  namespace: gitea
-spec:
-  replicas: 1
-  selector:
-    matchLabels:
-      app: remote-buildkitd
-  template:
-    metadata:
-      labels:
-        app: remote-buildkitd
-    spec:
-      nodeName: kube-master
-      containers:
-      - name: remote-buildkitd
-        image:  moby/buildkit:latest
-        securityContext:
-          privileged: true
-          runAsUser: 0
-        imagePullPolicy: IfNotPresent
-        ports:
-        - containerPort: 1234
-          name: buildkitd-port
-        volumeMounts:
-        - name: remote-buildkitd-data
-          mountPath: /etc/buildkit/certs
-        resources:
-            limits:
-#              cpu: 500m
-              memory: 1000Mi
-      volumes:
-      - name: gitea-var-docker-sock
-        hostPath:
-           path: /var/run/docker.sock
-      - name: remote-buildkitd-data
-        persistentVolumeClaim:
-          claimName: remote-buildkitd-data
 ---
 apiVersion: v1
 kind: Service