fix: update ingress configuration for Avatar.jpg

- Modify ingress configuration to redirect requests for /Avatar.jpg
  to a specific URL.
- Ensure that the redirection includes query parameters.
- Comment out the old rewrite rule for clarity.

This update addresses the routing for Avatar.jpg, ensuring that
requests are properly directed to the desired image location,
improving accessibility for users.

imagehost/ingress.yaml

@@ -6,10 +6,11 @@ metadata:
   namespace: imagehost
   annotations:                                                
     cert-manager.io/cluster-issuer: "dnspod-cluster-issuer"                                                                  
-    #nginx.ingress.kubernetes.io/configuration-snippet: |
-    #  location ~ ^/([^/]+\.jpg)$ {
-    #    return 301 $scheme://$host/i/$1;
-    #  }
+    nginx.ingress.kubernetes.io/configuration-snippet: |
+      location = /Avatar.jpg {
+        return 301 https://image.frytea.com/i/Avatar.jpg$is_args$args;
+      }
+    #nginx.ingress.kubernetes.io/rewrite-rule: "if ($uri ~ ^/(Avatar\\.jpg)$) { return 301 $scheme://$host/i/$1; }"
 spec:                                                         
   ingressClassName: nginx                                     
   tls: