//  1. Ignored fields.  It includes many fields which are not generally honored.  For instance, ResourceVersion and FieldPath are both very rarely valid in actual usage.
//  2. Invalid usage help.  It is impossible to add specific help for individual usage.  In most embedded usages, there are particular
//     restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".

...

            "format": "int32",
            "type": "integer"

- Fixed a regression in kubectl version `1.29.0` where the `--attach` flag was not honored.
   ([#122447](https://github.com/kubernetes/kubernetes/pull/122447), [@ardaguclu](https://github.com/ardaguclu))

	"schedulingGates":               "SchedulingGates is an opaque list of values that if specified will block scheduling the pod. If schedulingGates is not empty, the pod will stay in...

- [`KT-66692`](https://youtrack.jetbrains.com/issue/KT-66692) SLC: `findAttributeValue` for attribute w/ default value in Java returns `null`
- [`KT-61734`](https://youtrack.jetbrains.com/issue/KT-61734) SLC: wildcard suppression not honored
- [`KT-65112`](https://youtrack.jetbrains.com/issue/KT-65112) Symbol Light Classes don't support annotations on type parameters

  ...

 ...

                      not both. If CACertifcateRefs is empty or unspecified, the configuration for
                      WellKnownCACertificates MUST be honored instead if supported by the implementation.


                      References to a resource in a different namespace are invalid for the
                      moment, although we will revisit this in the future.

            "type": "boolean"
          },
          "hostname": {