schema: Added OpenAPI schema for 1.24.0

.github/workflows/e2e-tests.yml

@@ -11,18 +11,19 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        kubernetes: [v1.23.0,v1.12.0]
+        kubernetes: [v1.24.0,v1.12.0]
     env:
       K8S_VERSION: ${{ matrix.kubernetes }}
     steps:
       - name: Checkout
         uses: actions/checkout@v2
       - name: Setup Minikube-Kubernetes
-        uses: manusa/actions-setup-minikube@v2.4.3
+        uses: manusa/actions-setup-minikube@v2.5.0
         with:
-          minikube version: v1.24.0
+          minikube version: v1.25.2
           kubernetes version: ${{ matrix.kubernetes }}
           github token: ${{ secrets.GITHUB_TOKEN }}
+          container runtime: containerd
           start args: '--addons=metrics-server --force'
       - name: Setup Java 17
         uses: actions/setup-java@v2

.github/workflows/publish.yml

@@ -13,11 +13,12 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v2
       - name: Setup Minikube-Kubernetes
-        uses: manusa/actions-setup-minikube@v2.4.3
+        uses: manusa/actions-setup-minikube@v2.5.0
         with:
-          minikube version: v1.24.0
-          kubernetes version: v1.23.0
+          minikube version: v1.25.2
+          kubernetes version: v1.24.0
           github token: ${{ secrets.GITHUB_TOKEN }}
+          container runtime: containerd
           start args: '--addons=metrics-server'
       - name: Setup Java 11
         uses: actions/setup-java@v1

README.md

@@ -96,7 +96,7 @@ Provides the basic interfaces and Exception types to be used across the differen
 
 Kubernetes model objects to be used for REST API serialization/deserialization.
 
-Model types are generated for Kubernetes equivalents in versions ranging from 1.15 to 1.23.
+Model types are generated for Kubernetes equivalents in versions ranging from 1.15 to 1.24.
 
 #### kubernetes-api
 [![Maven Central](https://img.shields.io/maven-central/v/com.marcnuri.yakc/kubernetes-api)
@@ -108,7 +108,7 @@ Model types are generated for Kubernetes equivalents in versions ranging from 1.
 [Kubernetes JSON](https://github.com/kubernetes/kubernetes/blob/master/api/openapi-spec/swagger.json)
 [OpenAPI](https://swagger.io/specification/) schema.
 
-API methods for Kubernetes REST endpoints in versions ranging from 1.15 to 1.23.
+API methods for Kubernetes REST endpoints in versions ranging from 1.15 to 1.24.
 
 #### kubernetes-client
 [![Maven Central](https://img.shields.io/maven-central/v/com.marcnuri.yakc/kubernetes-client)

build.gradle

@@ -19,7 +19,8 @@ def availableSchemaNames = Arrays.asList(
   "kubernetes-1.20.5.json",
   "kubernetes-1.21.0.json",
   "kubernetes-1.22.0.json",
-  "kubernetes-1.23.0.json"
+  "kubernetes-1.23.0.json",
+  "kubernetes-1.24.0.json"
 )
 def availableSchemas = availableSchemaNames.stream()
   .map { s -> new File(schemaDir, s) }

kubernetes-api/src/api/java/com/marcnuri/yakc/api/admissionregistration/v1/AdmissionregistrationV1Api.java

@@ -371,7 +371,7 @@ public CreateMutatingWebhookConfiguration fieldManager(String fieldManager) {
     }
 
     /**
-     * fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.
+     * fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
      */
     public CreateMutatingWebhookConfiguration fieldValidation(String fieldValidation) {
       put("fieldValidation", fieldValidation);
@@ -597,7 +597,7 @@ public PatchMutatingWebhookConfiguration fieldManager(String fieldManager) {
     }
 
     /**
-     * fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.
+     * fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
      */
     public PatchMutatingWebhookConfiguration fieldValidation(String fieldValidation) {
       put("fieldValidation", fieldValidation);
@@ -676,7 +676,7 @@ public ReplaceMutatingWebhookConfiguration fieldManager(String fieldManager) {
     }
 
     /**
-     * fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.
+     * fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
      */
     public ReplaceMutatingWebhookConfiguration fieldValidation(String fieldValidation) {
       put("fieldValidation", fieldValidation);
@@ -1006,7 +1006,7 @@ public CreateValidatingWebhookConfiguration fieldManager(String fieldManager) {
     }
 
     /**
-     * fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.
+     * fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
      */
     public CreateValidatingWebhookConfiguration fieldValidation(String fieldValidation) {
       put("fieldValidation", fieldValidation);
@@ -1232,7 +1232,7 @@ public PatchValidatingWebhookConfiguration fieldManager(String fieldManager) {
     }
 
     /**
-     * fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.
+     * fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
      */
     public PatchValidatingWebhookConfiguration fieldValidation(String fieldValidation) {
       put("fieldValidation", fieldValidation);
@@ -1311,7 +1311,7 @@ public ReplaceValidatingWebhookConfiguration fieldManager(String fieldManager) {
     }
 
     /**
-     * fieldValidation determines how the server should respond to unknown/duplicate fields in the object in the request. Introduced as alpha in 1.23, older servers or servers with the `ServerSideFieldValidation` feature disabled will discard valid values specified in  this param and not perform any server side field validation. Valid values are: - Ignore: ignores unknown/duplicate fields. - Warn: responds with a warning for each unknown/duplicate field, but successfully serves the request. - Strict: fails the request on unknown/duplicate fields.
+     * fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
      */
     public ReplaceValidatingWebhookConfiguration fieldValidation(String fieldValidation) {
       put("fieldValidation", fieldValidation);