Update dependency go modules for k8s v1.27.0-rc.0

vendor/k8s.io/api/batch/v1/generated.proto

@@ -72,7 +72,6 @@ message CronJobSpec {
   // 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.
   // +optional
   optional string timeZone = 8;
 
@@ -83,6 +82,7 @@ message CronJobSpec {
 
   // Specifies how to treat concurrent executions of a Job.
   // Valid values are:
+  //
   // - "Allow" (default): allows CronJobs to run concurrently;
   // - "Forbid": forbids concurrent runs, skipping next run if previous run hasn't finished yet;
   // - "Replace": cancels currently running job and replaces it with a new one
@@ -189,7 +189,7 @@ message JobSpec {
   optional int32 parallelism = 1;
 
   // Specifies the desired number of successfully finished pods the
-  // job should be run with.  Setting to nil means that the success of any
+  // job should be run with.  Setting to null means that the success of any
   // pod signals the success of all pods, and allows parallelism to have any positive
   // value.  Setting to 1 means that parallelism is limited to 1 and the success of that
   // pod signals the success of the job.
@@ -243,6 +243,7 @@ message JobSpec {
   optional bool manualSelector = 5;
 
   // Describes the pod that will be created when executing a job.
+  // The only allowed template.spec.restartPolicy values are "Never" or "OnFailure".
   // More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
   optional k8s.io.api.core.v1.PodTemplateSpec template = 6;
 
@@ -256,7 +257,7 @@ message JobSpec {
   // +optional
   optional int32 ttlSecondsAfterFinished = 8;
 
-  // CompletionMode specifies how Pod completions are tracked. It can be
+  // completionMode specifies how Pod completions are tracked. It can be
   // `NonIndexed` (default) or `Indexed`.
   //
   // `NonIndexed` means that the Job is considered complete when there have
@@ -281,7 +282,7 @@ message JobSpec {
   // +optional
   optional string completionMode = 9;
 
-  // Suspend specifies whether the Job controller should create Pods or not. If
+  // suspend specifies whether the Job controller should create Pods or not. If
   // a Job is created with suspend set to true, no Pods are created by the Job
   // controller. If a Job is suspended after creation (i.e. the flag goes from
   // false to true), the Job controller will delete all active Pods associated
@@ -334,7 +335,7 @@ message JobStatus {
   // +optional
   optional int32 failed = 6;
 
-  // CompletedIndexes holds the completed indexes when .spec.completionMode =
+  // completedIndexes holds the completed indexes when .spec.completionMode =
   // "Indexed" in a text format. The indexes are represented as decimal integers
   // separated by commas. The numbers are listed in increasing order. Three or
   // more consecutive numbers are compressed and represented by the first and
@@ -344,15 +345,16 @@ message JobStatus {
   // +optional
   optional string completedIndexes = 7;
 
-  // UncountedTerminatedPods holds the UIDs of Pods that have terminated but
+  // uncountedTerminatedPods holds the UIDs of Pods that have terminated but
   // the job controller hasn't yet accounted for in the status counters.
   //
   // The job controller creates pods with a finalizer. When a pod terminates
   // (succeeded or failed), the controller does three steps to account for it
   // in the job status:
-  // (1) Add the pod UID to the arrays in this field.
-  // (2) Remove the pod finalizer.
-  // (3) Remove the pod UID from the arrays while increasing the corresponding
+  //
+  // 1. Add the pod UID to the arrays in this field.
+  // 2. Remove the pod finalizer.
+  // 3. Remove the pod UID from the arrays while increasing the corresponding
   //     counter.
   //
   // Old jobs might not be tracked using this field, in which case the field
@@ -409,6 +411,7 @@ message PodFailurePolicyOnExitCodesRequirement {
   // Represents the relationship between the container exit code(s) and the
   // specified values. Containers completed with success (exit code 0) are
   // excluded from the requirement check. Possible values are:
+  //
   // - In: the requirement is satisfied if at least one container exit code
   //   (might be multiple if there are multiple containers not restricted
   //   by the 'containerName' field) is in the set of specified values.
@@ -442,10 +445,11 @@ message PodFailurePolicyOnPodConditionsPattern {
 }
 
 // PodFailurePolicyRule describes how a pod failure is handled when the requirements are met.
-// One of OnExitCodes and onPodConditions, but not both, can be used in each rule.
+// One of onExitCodes and onPodConditions, but not both, can be used in each rule.
 message PodFailurePolicyRule {
   // Specifies the action taken on a pod failure when the requirements are satisfied.
   // Possible values are:
+  //
   // - FailJob: indicates that the pod's job is marked as Failed and all
   //   running pods are terminated.
   // - Ignore: indicates that the counter towards the .backoffLimit is not
@@ -470,12 +474,12 @@ message PodFailurePolicyRule {
 // UncountedTerminatedPods holds UIDs of Pods that have terminated but haven't
 // been accounted in Job status counters.
 message UncountedTerminatedPods {
-  // Succeeded holds UIDs of succeeded Pods.
+  // succeeded holds UIDs of succeeded Pods.
   // +listType=set
   // +optional
   repeated string succeeded = 1;
 
-  // Failed holds UIDs of failed Pods.
+  // failed holds UIDs of failed Pods.
   // +listType=set
   // +optional
   repeated string failed = 2;