* => IPv6 BackendPool name == <clusterName>-IPv6
    * This result into:
    * - clusters moving from IPv4 to duakstack will require no changes
    * - clusters moving from IPv6 (while not seen in the wild, we can not rule out their existence) to dualstack will require deleting backend pools (the reconciler will take care of creating correct backendpools)

background-color: $body-bg; // 2\n}\n\n// Future-proof rule: in browsers that support :focus-visible, suppress the focus outline\n// on elements that programmatically receive focus but wouldn't normally show a visible\n// focus outline. In general, this would mean that the outline is only applied if the\n// interaction that led to the element receiving programmatic focus was a keyboard interaction,\n// or the browser has somehow determined that the user is primarily a keyboard user and/or\n// wants focus outlines...

- Fixes a `cannot convert int64 to float64` error seen using server-side apply with certain CRDs in 1.19.10+ ([#103105](https://github.com/kubernetes/kubernetes/pull/103105), [@liggitt](https://github.com/liggitt)) [SIG API Machinery]

* 📝 Add external link to article: How-to deploy FastAPI app to Heroku. PR [#3241](https://github.com/tiangolo/fastapi/pull/3241) by [@Jarmos-san](https://github.com/Jarmos-san).
* ✏ Fix typo (mistranslation) in `docs/en/docs/advanced/templates.md`. PR [#3211](https://github.com/tiangolo/fastapi/pull/3211) by [@oerpli](https://github.com/oerpli).

pkg crypto/cipher, type AEAD interface { NonceSize, Open, Overhead, Seal }
pkg crypto/cipher, type AEAD interface, NonceSize() int
pkg crypto/cipher, type AEAD interface, Open([]uint8, []uint8, []uint8, []uint8) ([]uint8, error)
pkg crypto/cipher, type AEAD interface, Overhead() int
pkg crypto/cipher, type AEAD interface, Seal([]uint8, []uint8, []uint8, []uint8) []uint8
pkg crypto/md5, func Sum([]uint8) [16]uint8

background-color: $body-bg; // 2\n}\n\n// Future-proof rule: in browsers that support :focus-visible, suppress the focus outline\n// on elements that programmatically receive focus but wouldn't normally show a visible\n// focus outline. In general, this would mean that the outline is only applied if the\n// interaction that led to the element receiving programmatic focus was a keyboard interaction,\n// or the browser has somehow determined that the user is primarily a keyboard user and/or\n// wants focus outlines...

pkg bufio, method (*Reader) WriteTo(io.Writer) (int64, error)
pkg bufio, method (*Scanner) Bytes() []uint8
pkg bufio, method (*Scanner) Err() error
pkg bufio, method (*Scanner) Scan() bool
pkg bufio, method (*Scanner) Split(SplitFunc)
pkg bufio, method (*Scanner) Text() string
pkg bufio, method (*Writer) ReadFrom(io.Reader) (int64, error)
pkg bufio, method (ReadWriter) ReadFrom(io.Reader) (int64, error)

}\n}\n\n.nav-sidebar .nav-link > .right,\n.nav-sidebar .nav-link > p > .right {\n  position: absolute;\n  right: 1rem;\n  top: .7rem;\n}\n\n.nav-sidebar .nav-link > .right i,\n.nav-sidebar .nav-link > .right span,\n.nav-sidebar .nav-link > p > .right i,\n.nav-sidebar .nav-link > p > .right span {\n  margin-left: .5rem;\n}\n\n.nav-sidebar .nav-link > .right:nth-child(2),\n.nav-sidebar .nav-link > p > .right:nth-child(2) {\n  right: 2.2rem;\n}\n\n.nav-sidebar .menu-open > .nav-treeview {\n  display:...