description: Set of ports associated with the endpoint.
                type: object
              serviceAccount:
                description: The service account associated with the workload if a
                  sidecar is present in the workload.
                type: string
              weight:
                description: The load balancing weight associated with the endpoint.

                description: Set of ports associated with the endpoint.
                type: object
              serviceAccount:
                description: The service account associated with the workload if a
                  sidecar is present in the workload.
                type: string
              weight:
                description: The load balancing weight associated with the endpoint.

                    type: object
                  serviceAccount:
                    description: The service account associated with the workload
                      if a sidecar is present in the workload.
                    type: string
                  weight:
                    description: The load balancing weight associated with the endpoint.
                    type: integer

          means that a Gateway is based on the state of the GatewayClass at the time it
          was created and changes to the GatewayClass or associated parameters are not
          propagated down to existing Gateways. This recommendation is intended to
          limit the blast radius of changes to GatewayClass or associated parameters.
          If implementations choose to propagate GatewayClass changes to existing

              }
            ],
            "default": {},
            "description": "A node selector term, associated with the corresponding weight."
          },
          "weight": {
            "default": 0,
            "description": "Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100.",
            "format": "int32",
            "type": "integer"
          }

          },
          "group": {
            "description": "The group attribute of the resource associated with the status StatusReason.",
            "type": "string"
          },
          "kind": {

    Arg<TF_Tensor, [{Values to associate with keys.}]>:$values
  );

  let results = (outs);

  TF_DerivedOperandTypeAttr Tin = TF_DerivedOperandTypeAttr<1>;
  TF_DerivedOperandTypeAttr Tout = TF_DerivedOperandTypeAttr<2>;
}

def TF_LookupTableInsertV2Op : TF_Op<"LookupTableInsertV2", []> {
  let summary = "Updates the table to associates keys with values.";

  let description = [{

the `"mixed_float16"` policy and no loss scale for other policies. In `Model.compile`, if the model's policy had a loss scale, the optimizer would be wrapped with a `LossScaleOptimizer`. With the non-experimental `Policy`, there is no loss scale associated with the `Policy`, and `Model.compile` wraps the optimizer with a `LossScaleOptimizer` if and only if the policy is a `"mixed_float16"` policy. If you previously passed a `LossScale` to the experimental `Policy`, consider just removing it, as the...