From 7bf37ef90fb0a86f7d73838db6b82f47686dcd1d Mon Sep 17 00:00:00 2001 From: Paco Xu Date: Wed, 8 Mar 2023 13:15:46 +0800 Subject: [PATCH] cleanup: sync testdata as CronJobTimeZone is GAed Kubernetes-commit: 23a583dc3679111d5aaebf2a87db67e4d7c58739 --- openapi/openapitest/testdata/apis__batch__v1_openapi.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openapi/openapitest/testdata/apis__batch__v1_openapi.json b/openapi/openapitest/testdata/apis__batch__v1_openapi.json index 510e2e09..ffbf070b 100644 --- a/openapi/openapitest/testdata/apis__batch__v1_openapi.json +++ b/openapi/openapitest/testdata/apis__batch__v1_openapi.json @@ -135,7 +135,7 @@ "type": "boolean" }, "timeZone": { - "description": "The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones This is beta field and must be enabled via the `CronJobTimeZone` feature gate.", + "description": "The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones.", "type": "string" } },