* 3. Maximum of two entries is allowed in `--service-cluster-ip-range` and they are validated to be dual stacked `i.e. --service-cluster-ip-range=<v4>,<v6> or --service-cluster-ip-range=<v6>,<v4>`
    * 4. Max 20 bit for range (min network bits `<v6>/108` or <v4>/12)
    * kube-controller-manager: convert service CIDR to list `--service-cluster-ip-range=<CIDR>,<CIDR>` and make sure `IPv6DualStack` feature flag is turned on. The flag is validated as above.

## Dependencies

### Added
- github.com/bits-and-blooms/bitset: [v1.2.0](https://github.com/bits-and-blooms/bitset/tree/v1.2.0)

### Changed
- github.com/cilium/ebpf: [v0.5.0 → v0.6.2](https://github.com/cilium/ebpf/compare/v0.5.0...v0.6.2)

## Urgent Upgrade Notes
### (No, really, you MUST read this before you upgrade)
#### Cluster Lifecycle

pkg syscall (netbsd-arm64-cgo), type Dirent struct, Reclen uint16
pkg syscall (netbsd-arm64-cgo), type Dirent struct, Type uint8
pkg syscall (netbsd-arm64-cgo), type FdSet struct
pkg syscall (netbsd-arm64-cgo), type FdSet struct, Bits [8]uint32
pkg syscall (netbsd-arm64-cgo), type Flock_t struct
pkg syscall (netbsd-arm64-cgo), type Flock_t struct, Len int64
pkg syscall (netbsd-arm64-cgo), type Flock_t struct, Pid int32

pkg math (freebsd-riscv64-cgo), const MaxUint = 18446744073709551615 #53466
pkg math (freebsd-riscv64-cgo), const MinInt = -9223372036854775808 #53466
pkg math/bits (freebsd-riscv64), const UintSize = 64 #53466
pkg math/bits (freebsd-riscv64-cgo), const UintSize = 64 #53466
pkg os (freebsd-riscv64), const DevNull = "/dev/null" #53466
pkg os (freebsd-riscv64), const O_APPEND = 8 #53466

    String getIndexFieldContent();

    /**
     * Get the value for the key 'index.field.content_minhash_bits'. <br>
     * The value is, e.g. content_minhash_bits <br>
     * comment: Field name for content minhash bits in the index.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getIndexFieldContentMinhashBits();

    /**

### Cluster Autoscaler
* If you are using (or planning to use) Cluster Autoscaler please wait for Kubernetes 1.6.1. In 1.6.0 Cluster Autoscaler
may occasionally increase the size of the cluster a bit more than it is actually needed, when there are
unschedulable pods, scale up is required and cloud provider is slow to set up networking for new nodes.
Anyway, the cluster should get back to the proper size after 10 min.

    * Approved and Issued, or Denied.
* Optimize random string generator to avoid multiple locks & use bit-masking ([#53720](https://github.com/kubernetes/kubernetes/pull/53720), [@shyamjvs](https://github.com/shyamjvs))

- DRA kubelet: recovery from mistakes like scheduling a pod onto a node with the required driver not running is a bit simpler now because the kubelet does not block pod deletion unnecessarily. ([#131968](https://github.com/kubernetes/kubernetes/pull/131968), [@pohly](https://github.com/pohly)) [SIG Node and Testing]

    ...


@app.delete("/items/{item_id}")
def delete_item(*, user: User = Depends(get_current_user), item_id: int):
    ...
```

There's a bit of code duplication for the dependency:

```Python
user: User = Depends(get_current_user)
```

...the bigger the codebase, the more noticeable it is.