by a transitive connection (controller -> IngressClass -> Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor...

        ],
        "type": "object",
        "x-kubernetes-map-type": "atomic"
      },
      "io.k8s.api.rbac.v1.Subject": {
        "description": "Subject contains a reference to the object or user identities a role binding applies to.  This can either hold a direct API object reference, or a value for non-objects such as user and group names.",
        "properties": {
          "apiGroup": {

    </magic>
    <glob pattern="*.wq2"/>
    <glob pattern="*.wkq"/>
  </mime-type>
  
  <!-- First Quattro Pro for Windows had major version number 1, which
  was followed by 5. This is confusing, perhaps adding "win" qualifier to version
  field could clear this up (but it's quite ugly as well)   -->
  
  <mime-type type="application/x-quattro-pro;version=1+5">
    <sub-class-of type="application/x-quattro-pro"/>