This is an automated email from the ASF dual-hosted git repository.

dongjoon pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/spark-kubernetes-operator.git


The following commit(s) were added to refs/heads/main by this push:
     new bfb7cf3  [SPARK-51893] Upgrade CI to test K8s 1.33
bfb7cf3 is described below

commit bfb7cf339094807e68d1fc5b497bf20773616900
Author: Dongjoon Hyun <dongj...@apache.org>
AuthorDate: Thu Apr 24 16:01:46 2025 +0900

    [SPARK-51893] Upgrade CI to test K8s 1.33
    
    ### What changes were proposed in this pull request?
    
    This PR aims to increase the maximum K8s test version to 1.33 from 1.32.
    
    ### Why are the changes needed?
    
    To improve the test coverage because K8s 1.33.0 was released on 2025-04-23.
    - https://kubernetes.io/releases/#release-v1-33
    
    ### Does this PR introduce _any_ user-facing change?
    
    No.
    
    ### How was this patch tested?
    
    Pass the CIs and check the CI log.
    
    ```
    System Info:
    ...
      Kubelet Version:            v1.33.0
    ```
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    No.
    
    Closes #174 from dongjoon-hyun/SPARK-51893.
    
    Authored-by: Dongjoon Hyun <dongj...@apache.org>
    Signed-off-by: Dongjoon Hyun <dongj...@apache.org>
---
 .github/workflows/build_and_test.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/build_and_test.yml 
b/.github/workflows/build_and_test.yml
index 7196e5e..8a84c98 100644
--- a/.github/workflows/build_and_test.yml
+++ b/.github/workflows/build_and_test.yml
@@ -69,7 +69,7 @@ jobs:
       matrix:
         kubernetes-version:
           - "1.30.0"
-          - "1.32.0"
+          - "1.33.0"
         mode:
           - dynamic
           - static


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org

Reply via email to