Q) Is it possible to use python client outside of the k8s cluster now? about kuberay HOT 5 CLOSED

apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2021-09-30T06:19:52Z"
  labels:
    ray.io/cluster: raycluster-mini
    ray.io/identifier: raycluster-mini-head
    ray.io/node-type: head
  name: raycluster-mini-head-svc
  namespace: ray-system
  ownerReferences:
  - apiVersion: ray.io/v1alpha1
    blockOwnerDeletion: true
    controller: true
    kind: RayCluster
    name: raycluster-mini
    uid: 141efbba-65e0-4460-9d20-502320f46252
  resourceVersion: "865"
  selfLink: /api/v1/namespaces/ray-system/services/raycluster-mini-head-svc
  uid: 506e0a71-9e5d-4fd9-8e22-9b0d55bc797f
spec:
  clusterIP: 10.100.96.184
  ports:
  - port: 10001
    protocol: TCP
    targetPort: 10001
  selector:
    ray.io/cluster: raycluster-mini
    ray.io/identifier: raycluster-mini-head
    ray.io/node-type: head
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

apiVersion: ray.io/v1alpha1
kind: RayCluster
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
    # An unique identifier for the head node and workers of this cluster.
  name: raycluster-mini
spec:
  rayVersion: '0.8.6' # should match the Ray version in the image of the containers
  ######################headGroupSpecs#################################
  # head group template and specs, (perhaps 'group' is not needed in the name)
  headGroupSpec:
    # Kubernetes Service Type, valid values are 'ClusterIP', 'NodePort' and 'LoadBalancer'
    serviceType: ClusterIP
    # the pod replicas in this group typed head (assuming there could be more than 1 in the future)
    replicas: 1
    # logical group name, for this called head-group, also can be functional
    # pod type head or worker
    # rayNodeType: head # Not needed since it is under the headgroup
    # the following params are used to complete the ray start: ray start --head --block --redis-port=6379 ...
    rayStartParams:
      port: '6379' # should match headService targetPort
      object-manager-port: '12345'
      node-manager-port: '12346'
      #include_webui: 'true'
      object-store-memory: '100000000'
      redis-password: 'LetMeInRay'
      # webui_host: "10.1.2.60"
      dashboard-host: '0.0.0.0'
      num-cpus: '1' # can be auto-completed from the limits
      node-ip-address: $MY_POD_IP # auto-completed as the head pod IP
    #pod template
    template:
      metadata:
        labels:
          # custom labels. NOTE: do not define custom labels start with `raycluster.`, they may be used in controller.
          # Refer to https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
          rayCluster: raycluster-sample # will be injected if missing
          rayNodeType: head # will be injected if missing, must be head or wroker
          groupName: headgroup # will be injected if missing
        # annotations for pod
        annotations:
          key: value
      spec:
        containers:
        - name: ray-head
          image: rayproject/ray:1.6.0
          #image: rayproject/ray:nightly
          #image: bonsaidev.azurecr.io/bonsai/lazer-0-9-0-cpu:dev
          # you can have any command and args here to run your code. 
          # the below command/args will be appended after the Ray start command and it args, and executed after Ray start.
          command: ["sleep"]
          args:
          - '10000'
          env:
          - name: MY_POD_IP
            valueFrom:
              fieldRef:
                fieldPath: status.podIP
          ports:
          - containerPort: 6379
          - containerPort: 8265 # Ray dashboard
          - containerPort: 10001 #################### this is the only changed ####################

apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2021-09-30T06:29:04Z"
  labels:
    ray.io/cluster: raycluster-mini
    ray.io/identifier: raycluster-mini-head
    ray.io/node-type: head
  name: raycluster-mini-head-svc
  namespace: ray-system
  ownerReferences:
  - apiVersion: ray.io/v1alpha1
    blockOwnerDeletion: true
    controller: true
    kind: RayCluster
    name: raycluster-mini
    uid: 00aebf70-3fb5-4aed-a469-d71531247469
  resourceVersion: "1293"
  selfLink: /api/v1/namespaces/ray-system/services/raycluster-mini-head-svc
  uid: ae39272d-f257-490c-a092-c4fa72268194
spec:
  clusterIP: 10.106.64.226
  ports:
  - name: client
    port: 10001
    protocol: TCP
    targetPort: 10001
  - name: redis
    port: 6379
    protocol: TCP
    targetPort: 6379
  - name: dashboard
    port: 8265
    protocol: TCP
    targetPort: 8265
  selector:
    ray.io/cluster: raycluster-mini
    ray.io/identifier: raycluster-mini-head
    ray.io/node-type: head
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

          ports:
          - containerPort: 6379
          - containerPort: 8265 # Ray dashboard
          - containerPort: 10001

          ports:
          - containerPort: 6379
            name: a
          - containerPort: 8265 # Ray dashboard
            name: b
          - containerPort: 10001
            name: c

apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2021-09-30T08:17:55Z"
  labels:
    ray.io/cluster: raycluster-mini
    ray.io/identifier: raycluster-mini-head
    ray.io/node-type: head
  name: raycluster-mini-head-svc
  namespace: ray-system
  ownerReferences:
  - apiVersion: ray.io/v1alpha1
    blockOwnerDeletion: true
    controller: true
    kind: RayCluster
    name: raycluster-mini
    uid: 29353c10-5127-4fb4-b2a3-94688007dd05
  resourceVersion: "562"
  selfLink: /api/v1/namespaces/ray-system/services/raycluster-mini-head-svc
  uid: bba0da0b-329f-41d3-92c7-28bd8428291d
spec:
  clusterIP: 10.109.63.104
  ports:
  - name: a
    port: 6379
    protocol: TCP
    targetPort: 6379
  - name: b
    port: 8265
    protocol: TCP
    targetPort: 8265
  - name: c
    port: 10001
    protocol: TCP
    targetPort: 10001
  selector:
    ray.io/cluster: raycluster-mini
    ray.io/identifier: raycluster-mini-head
    ray.io/node-type: head
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}