/88290), [@tallclair](https://github.com/tallclair)) [SIG API Machinery and Node]

- `kubectl` no longer defaults to `http://localhost:8080`.  If you own one of these legacy clusters, you are *strongly- encouraged to secure your server.   If you cannot secure your server, you can set `KUBERNETES_MASTER` if you were relying on that behavior and you're client-go user. Set `--server`, `--kubeconfig` or `KUBECONFIG` to make it work in `kubectl`. ([#86173](https://github.com/kubernetes/ku...

### Feature

- Kubernetes is now built with Golang 1.16.9 (#105672, @cpanato) [SIG Cloud Provider, Instrumentation, Release and Testing]

### Failing Test

- Backport: e2e.test now uses the secure port to retrieve metrics data to ensure compatibility with 1.21 and 1.22 (for upgrade tests) (#104328, @pohly) [SIG API Machinery, Instrumentation, Storage and Testing]

### Bug or Regression

pkg syscall (freebsd-arm64), const SIGTTIN Signal
pkg syscall (freebsd-arm64), const SIGTTOU = 22
pkg syscall (freebsd-arm64), const SIGTTOU Signal
pkg syscall (freebsd-arm64), const SIGURG = 16
pkg syscall (freebsd-arm64), const SIGURG Signal
pkg syscall (freebsd-arm64), const SIGUSR1 = 30
pkg syscall (freebsd-arm64), const SIGUSR1 Signal
pkg syscall (freebsd-arm64), const SIGUSR2 = 31

pkg syscall (darwin-arm64), const SIGTTIN Signal
pkg syscall (darwin-arm64), const SIGTTOU = 22
pkg syscall (darwin-arm64), const SIGTTOU Signal
pkg syscall (darwin-arm64), const SIGURG = 16
pkg syscall (darwin-arm64), const SIGURG Signal
pkg syscall (darwin-arm64), const SIGUSR1 = 30
pkg syscall (darwin-arm64), const SIGUSR1 Signal
pkg syscall (darwin-arm64), const SIGUSR2 = 31

- Completed pods lose logs across node upgrade ([#32324](https://github.com/kubernetes/kubernetes/issues/32324))
- Pods are deleted across node upgrade ([#32323](https://github.com/kubernetes/kubernetes/issues/32323))
- Secure master -> node communication ([#11816](https://github.com/kubernetes/kubernetes/issues/11816))
- upgrading master doesn't upgrade kubectl ([#32538](https://github.com/kubernetes/kubernetes/issues/32538))

### CVE-2022-3294: Node address isn't always verified when proxying

A security issue was discovered in Kubernetes where users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can to modify Node objects and send requests proxying through them.

pkg syscall (freebsd-riscv64), const SIGTTOU = 22 #53466
pkg syscall (freebsd-riscv64), const SIGTTOU Signal #53466
pkg syscall (freebsd-riscv64), const SIGURG = 16 #53466
pkg syscall (freebsd-riscv64), const SIGURG Signal #53466
pkg syscall (freebsd-riscv64), const SIGUSR1 = 30 #53466
pkg syscall (freebsd-riscv64), const SIGUSR1 Signal #53466
pkg syscall (freebsd-riscv64), const SIGUSR2 = 31 #53466

    t, inverse Gamma) now fully reparameterized.
*   Java: Experimental wrapper classes to make graph generation easier. Thanks
    @karllessard and @kbsriram
*   Build & link in secure gRPC components (switch from the insecure grpc
    dependency to secure grpc dependency).
*   Adding new endpoints for existing tensorflow symbols. These endpoints are
    going to be the preferred endpoints going forward and may replace some of

* Support secure etcd cluster for centos provider. ([#42994](https://github.com/kubernetes/kubernetes/pull/42994), [@Shawyeok](https://github.com/Shawyeok))

pkg net/http, type Cookie struct, Name string
pkg net/http, type Cookie struct, Path string
pkg net/http, type Cookie struct, Raw string
pkg net/http, type Cookie struct, RawExpires string
pkg net/http, type Cookie struct, Secure bool
pkg net/http, type Cookie struct, Unparsed []string
pkg net/http, type Cookie struct, Value string
pkg net/http, type CookieJar interface { Cookies, SetCookies }