fix: RayJob submit now uses the API client set via set_api_client()

  The vendored RayjobApi and RayClusterApi were creating their own
  Kubernetes clients by calling config.load_kube_config() directly,
  ignoring the client provided through set_api_client(). This caused
  403 errors when authenticating with a custom token, as the request
  would fall back to the default kubeconfig or in-cluster service account.

  Override the vendored API instances after construction with ones that
  use the SDK's global API client, consistent with how the rest of the
  SDK (Kueue, Cluster) handles authentication.

Signed-off-by: Saad Zaher <szaher@redhat.com>

Author: szaher

src/codeflare_sdk/ray/rayjobs/rayjob.py

@@ -22,6 +22,7 @@
 import warnings
 from typing import Dict, Any, Optional, Tuple, Union
 
+from kubernetes import client
 from ray.runtime_env import RuntimeEnv
 from codeflare_sdk.common.kueue.kueue import (
     get_default_kueue_name,
@@ -39,6 +40,7 @@
     process_runtime_env,
 )
 
+from ...common.kubernetes_cluster.auth import config_check, get_api_client
 from ...common.utils import get_current_namespace
 from ...common.utils.validation import validate_ray_version_compatibility
 
@@ -169,8 +171,13 @@ def __init__(
             self.cluster_name = cluster_name
             logger.info(f"Using existing cluster: {self.cluster_name}")
 
+        config_check()
+        k8s_client = get_api_client()
         self._api = RayjobApi()
+        self._api.api = client.CustomObjectsApi(k8s_client)
         self._cluster_api = RayClusterApi()
+        self._cluster_api.api = client.CustomObjectsApi(k8s_client)
+        self._cluster_api.core_v1_api = client.CoreV1Api(k8s_client)
 
         logger.info(f"Initialized RayJob: {self.name} in namespace: {self.namespace}")