- [SIG-storage](#sig-storage)
    - [SIG-vmware](#sig-vmware)
    - [SIG-windows](#sig-windows)
  - [Action Required](#action-required-1)
  - [Deprecations and removals](#deprecations-and-removals)
  - [New Features](#new-features)
  - [API Changes](#api-changes)
  - [Other Notable Changes](#other-notable-changes-10)
    - [SIG API Machinery](#sig-api-machinery-1)
    - [SIG Apps](#sig-apps)
    - [SIG Auth](#sig-auth)

	"crypto/sha1": {
		{"BlockSize", Const, 0},
		{"New", Func, 0},
		{"Size", Const, 0},
		{"Sum", Func, 2},
	},
	"crypto/sha256": {
		{"BlockSize", Const, 0},
		{"New", Func, 0},
		{"New224", Func, 0},
		{"Size", Const, 0},
		{"Size224", Const, 0},
		{"Sum224", Func, 2},
		{"Sum256", Func, 2},
	},
	"crypto/sha512": {
		{"BlockSize", Const, 0},
		{"New", Func, 0},
		{"New384", Func, 0},

istio-system. Since the external IP is associated with the Service and bound to the namespace, it is recommended to: 1. Install the new gateway in a new namespace. 2. Copy any TLS certificate to the new namespace, and configure the domains. 3. Checking the new gateway work - for example by overriding the IP in /etc/hosts 4. Modify the DNS server to add the A record of the new namespace 5. Check traffic 6. Delete the A record corresponding to the gateway in istio-system 7. Upgrade istio-system, disabling...