"in": "query",
                        }
                    ],
                    "responses": {
                        "200": {
                            "description": "Successful Response",
                            "content": {"application/x-level-1": {"schema": {}}},
                        },
                        "400": {"description": "Client error level 0"},

                      description: "AttachedRoutes represents the total number of
                        Routes that have been successfully attached to this Listener.
                        \n Successful attachment of a Route to a Listener is based
                        solely on the combination of the AllowedRoutes field on the
                        corresponding Listener and the Route's ParentRefs field. A

								"x-kubernetes-list-type": "atomic",
							},
						},
						SchemaProps: spec.SchemaProps{

  // Started indicates whether the container has finished its postStart lifecycle hook
  // and passed its startup probe.
  // Initialized as false, becomes true after startupProbe is considered
  // successful. Resets to false when the container is restarted, or if kubelet
  // loses state temporarily. In both cases, startup probes will run again.
  // Is always true when no startupProbe is defined and container is running and

	// +optional
	TimeoutSeconds int32
	// How often (in seconds) to perform the probe.
	// +optional
	PeriodSeconds int32
	// Minimum consecutive successes for the probe to be considered successful after having failed.
	// Must be 1 for liveness and startup.
	// +optional
	SuccessThreshold int32
	// Minimum consecutive failures for the probe to be considered failed after having succeeded.
	// +optional

	"started":            "Started indicates whether the container has finished its postStart lifecycle hook and passed its startup probe. Initialized as false, becomes true after startupProbe is considered successful. Resets to false when the container is restarted, or if kubelet loses state temporarily. In both cases, startup probes will run again. Is always true when no startupProbe is defined and container is running and has passed the postStart lifecycle...

- Upon successful authorization check, an impersonated user is added to the system:authenticated group.

  // Started indicates whether the container has finished its postStart lifecycle hook
  // and passed its startup probe.
  // Initialized as false, becomes true after startupProbe is considered
  // successful. Resets to false when the container is restarted, or if kubelet
  // loses state temporarily. In both cases, startup probes will run again.
  // Is always true when no startupProbe is defined and container is running and

    * try to only update vm if detach a non-existing disk when got <200, error> after detach disk operation
* This adds some useful metrics around pending changes and last successful ([#78602](https://github.com/kubernetes/kubernetes/pull/78602), [@paulgmiller](https://github.com/paulgmiller))
    * sync time.
 
    * The goal is for administrators to be able to alert on proxies that, for

            "format": "int64",
            "type": "integer"
          },
          "successfulJobsHistoryLimit": {
            "description": "The number of successful finished jobs to retain. Value must be non-negative integer. Defaults to 3.",
            "format": "int32",
            "type": "integer"
          },
          "suspend": {