Here is my question:

1. Could anyone explain the possible proxy configuration places for error event proxyconnect tcp: dial tcp and how to pass it.

Follow instruction Ray CLuster quickstart:

helm repo add kuberay https://ray-project.github.io/kuberay-helm/
helm repo update

# Install both CRDs and KubeRay operator v1.1.1.
helm install kuberay-operator kuberay/kuberay-operator --version 1.1.1

# Confirm that the operator is running in the namespace `default`.
kubectl get pods
# NAME                                READY   STATUS    RESTARTS   AGE
# kuberay-operator-7fbdbf8c89-pt8bk   1/1     Running   0          27s 

in the step2. I get aErrImagePull status pod, and the real output:

(base) ➜  ~ helm install kuberay-operator kuberay/kuberay-operator --version 1.0.0                                                                                                                     [36/197]
NAME: kuberay-operator                                                                                                                                                                                         
LAST DEPLOYED: Fri Jul 26 08:56:30 2024                                                                                                                                                                        
NAMESPACE: default                                                                                                                                                                                             
STATUS: deployed                                                                                                                                                                                               
REVISION: 1
TEST SUITE: None        
(base) ➜  ~ kubectl get pods                                                                           
NAME                                READY   STATUS         RESTARTS   AGE
kuberay-operator-5d64d88fdb-shrkv   0/1     ErrImagePull   0          10s
(base) ➜  ~ kubectl describe pod kuberay-operator-5d64d88fdb-shrkv 
Name:             kuberay-operator-5d64d88fdb-shrkv 
Namespace:        default              
Priority:         0                
Service Account:  kuberay-operator                                                                     
Node:             kind-control-plane/172.23.0.2                                                        
Start Time:       Fri, 26 Jul 2024 08:56:31 +0800
Labels:           app.kubernetes.io/component=kuberay-operator    
                  app.kubernetes.io/instance=kuberay-operator     
                  app.kubernetes.io/name=kuberay-operator                                                                                                                                                      
                  pod-template-hash=5d64d88fdb         
.....
Events:
  Type     Reason     Age               From               Message
  ----     ------     ----              ----               -------
  Normal   Scheduled  22s               default-scheduler  Successfully assigned default/kuberay-operator-5d64d88fdb-shrkv to kind-control-plane
  Normal   BackOff    21s               kubelet            Back-off pulling image "kuberay/operator:v1.0.0"
  Warning  Failed     21s               kubelet            Error: ImagePullBackOff
  Normal   Pulling    6s (x2 over 21s)  kubelet            Pulling image "kuberay/operator:v1.0.0"
  Warning  Failed     6s (x2 over 21s)  kubelet            Failed to pull image "kuberay/operator:v1.0.0": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/kuberay/operator:v1.0.0"
: failed to resolve reference "docker.io/kuberay/operator:v1.0.0": failed to do request: Head "https://registry-1.docker.io/v2/kuberay/operator/manifests/v1.0.0": proxyconnect tcp: dial tcp 127.0.0.1:1082: connect: connection refused
  Warning  Failed     6s (x2 over 21s)  kubelet            Error: ErrImagePull

The puzzle question is the message: proxyconnect tcp: dial tcp 127.0.0.1:1082: connect: connection refused

I tried following ways but did not find any proxy configuration:

(base) ➜  ~  echo $HTTP_PROXY

(base) ➜  ~  echo $HTTPS_PROXY

(base) ➜  ~ cat /etc/environment                 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
(base) ➜  ~ cat /etc/docker/daemon.json 
{
    "registry-mirrors": [
        "https://5wxalzzb.mirror.aliyuncs.com",    
        "https://hub-mirror.c.163.com",
        "https://mirror.iscas.ac.cn",
        "https://docker.m.daocloud.io"
    ],
    "runtimes": {
        "nvidia": {
            "args": [],
            "path": "nvidia-container-runtime"
        }
    }
}

To mitigate the pod issue, I start local port 1082, which is a HTTP proxy, and then re-install the kuberay/operator again, but the same error event message for proxy.