assumes layers only ever have one positional argument. This assumption
        doesn't hold true before TF 2.4 either, but is more likely to cause
        issues now.
    *   Code that manually enters `keras.backend.get_graph()` before building a
        functional model is no longer needed.
    *   Start enforcing input shape assumptions when calling Functional API

  Beware that the behavior of the IPFamily field is strange and inconsistent and will
  likely be changed before the dual-stack feature goes GA. Users should treat the
  field as "write-only" for now and should not make any assumptions about a service
  based on its current IPFamily value. ([#91400](https://github.com/kubernetes/kubernetes/pull/91400), [@danwinship](https://github.com/danwinship)) [SIG Apps and Network]