AuthenticationPolicies{}, NetworkManager{}, sidecarIndex{}, Telemetries{}, ProxyConfigs{}, ConsolidatedDestRule{},
			ClusterLocalHosts{}),
		// These are not feasible/worth comparing
		cmpopts.IgnoreTypes(sync.RWMutex{}, localServiceDiscovery{}, FakeStore{}, atomic.Bool{}, sync.Mutex{}),
		cmpopts.IgnoreUnexported(IstioEndpoint{}),
		cmpopts.IgnoreInterfaces(struct{ mesh.Holder }{}),

// * 1 IP address. This is managed, with IP explicit
// * Nothing. This is managed, with IP auto assigned
//
// Not supported:
// Multiple hostname/IP - It is feasible but preference is to create multiple Gateways. This would also break the 1:1 mapping of GW:Service
// Mixed hostname and IP - doesn't make sense; user should define the IP in service

reason the blue and violet being much darker Colours than these, and much more rarified, may be neglected. For the dense and bright Light of the Circle, will obscure the rare and weak Light of these dark Colours round about it, and render them almost insensible. The sensible Image of a lucid Point is therefore scarce broader than a Circle, whose Diameter is the 250th Part of the Diameter of the Aperture of the Object-glass of a good Telescope, or not much broader, if you except a faint and dark misty Light...

If a task in your build relied on the previous behavior, you can instead use the entire
`SourceSetOutput` as an input, which contains all classes and resources.

If that is not feasible, you can restore the previous behavior by adding more task dependencies to `classesDirs`:
```groovy
java {
    sourceSets {
        main {
            output.classesDirs.builtBy(output)
        }
    }
}

much darker Colours than these, and much more rarified, may be
neglected. For the dense and bright Light of the Circle, will obscure
the rare and weak Light of these dark Colours round about it, and
render them almost insensible. The sensible Image of a lucid Point is
therefore scarce broader than a Circle, whose Diameter is the 250th Part
of the Diameter of the Aperture of the Object-glass of a good Telescope,

	memRequests := resource.GetResourceRequest(podCopy, v1.ResourceMemory)
	if cpuRequests > cpuAvailable || memRequests > memAvailable {
		klog.V(3).InfoS("Resize is not feasible as request exceeds allocatable node resources", "pod", podCopy.Name)
		return false, podCopy, v1.PodResizeStatusInfeasible
	}

	// Treat the existing pod needing resize as a new pod with desired resources seeking admit.

### OpenStack

In this cycle, SIG OpenStack focused on configuration simplification through smarter defaults and the use of auto-detection wherever feasible (Block Storage API versions, Security Groups) as well as updating API support, including:

*   Block Storage (Cinder) V3 is now supported.
*   Load Balancer (Octavia) V2 is now supported, in addition to Neutron LBaaS V2.